September 17 2012

VMWare ESX support for Windows Server 2012

I found it quite hard to find this information so I figured I would share it. I was looking for an official line from VMWare on the versions of ESX that would Windows Server 2012 as a guest operating system.

Directly quoted from http://blogs.vmware.com/guestosguide/2012/09/windows-server-2012.html :

The release of vSphere 5.1 introduces support for Windows Server 2012 on ESXi 5.1, with the following support considerations:

  • Installation instruction can be found here http://partnerweb.vmware.com/GOSIG/Windows_Server_2012.html
  • Snapshots, checkpoints and VMotion actions for virtual machines with Windows 8 or Windows Server 2012 are incompatible between hosts running ESXi 5.0 Update 1 or ESXi 5.0 P03 with host running later versions of ESXi ( ESXi 5.0 Update 2, ESXi 5.1, etc.). Please refer to KB-2033723 for more information.
  • The Guest OS Customization feature in vCenter does not support Windows 8 or Windows Server 2012 in vSphere 5.1.
  • vSphere client will use EFI BIOS for VMs configured for Windows 8 or Windows Server 2012 with hardware version 9, however, EFI BIOS is not compatible with the Fault Tolerance feature. Therefore to use Fault Tolerance feature, it is recommended to use Legacy BIOS instead of EFI BIOS.

For more information about software support, please check the VMware Compatibility Guide

Also from http://kb.vmware.com/selfservice/microsites/microsite.do?cmd=displayKC&docType=kc&externalId=2006859&sliceId=2&docTypeID=DT_KB_1_1  I have extracted this one liner:

Windows 8 / Windows Server 2012 will not be supported on ESXi/ESX 4.0 or 4.1.

And finally, from http://partnerweb.vmware.com/comp_guide2/pdf/VMware_GOS_Compatibility_Guide.pdf (page 103) I read that supported releases are ESXi 5.1 or ESXi 5.0 U1.

More information:



----------------------------------------------------------------------------
I use a maximum of one Google Ad per post to help offset some of my blog hosting costs.

----------------------------------------------------------------------------

Category: Windows | LEAVE A COMMENT
July 31 2012

Windows Server 2012 Editions

Microsoft have released details on the different editions that will be available for Windows Server 2012. It looks like Enterprise Edition has been dropped:

More info here – http://www.microsoft.com/en-us/server-cloud/windows-server/2012-editions.aspx

 

 

Category: Windows | LEAVE A COMMENT
August 18 2011

SCCM report – count Windows Server versions on physical hardware only

I had a requirement to count the different versions of Windows Server but only on physical hardware. This SCCM report does this by excluding VMWare and Hyper-V machines:

SELECT OPSYS.Caption0 as C054, COUNT(*) AS 'Count'
FROM v_GS_OPERATING_SYSTEM OPSYS
full Join v_GS_COMPUTER_SYSTEM On v_GS_COMPUTER_SYSTEM.ResourceID = OPSYS.ResourceID
inner join v_R_System sys on OPSYS.ResourceID=sys.ResourceID
where OPSYS.Caption0 LIKE '%server%'
and (v_GS_COMPUTER_SYSTEM.Manufacturer0 NOT LIKE '%Microsoft Corporation%')
and (v_GS_COMPUTER_SYSTEM.Manufacturer0 NOT LIKE '%VMware, Inc.%')
GROUP BY OPSYS.Caption0
ORDER BY OPSYS.Caption0

 
 

October 27 2009

Clarification on Windows time stamps

There is an old but good reference on the Microsoft support site that givea some clarification on how Windows presents time stamps (eg event logs, NTFS times) to the user.

Of particular note is this paragraph:

If you are viewing another machine remotely across one or more time zones through Event Viewer, the times for events on the remote system appear relative to your local time. In other words, if you are viewing an event remotely that actually occurred at 8:00 PM Central Daylight Time, the time displayed for the event on your computer will be 6:00 PM when you view the event from the Pacific Daylight Time zone.

Link is http://support.microsoft.com/kb/129574

Category: Windows | LEAVE A COMMENT
October 8 2009

Time sync using w32tm on Windows clients

As we know, in a domain environment, domain controllers sync with the PDCEmluator and then workstations and member servers choose one available DC in the domain for the time sync.

If something does not work and you have errors in the event viewer about time sync, make sure that port 123 udp is openend on firewalls, then if the domain machine time is still out of sync, run the below command:

w32tm /config /syncfromflags:domhier /update

This does two things.  First, it sets the HKLMSYSTEMCurrentControlSetServicesW32TimeParameters Type value to “NT5DS.”  Second, it notifies the w32time service that settings have changed.

In the majority of cases, you will see the clock adjust immediately. If not, restart the service using:

net stop w32time
net start w32time

This will resync and fix your incorrect time in the majority of cases.