Here is the list of frequently required tasks to perform on newly installed WS 2012 box. I know that some of them could be not in line with best practices or your environment requirements but anyway those are frequent tasks.
Check UAC status
\nUse following PowerShell code:\n\nGet-ItemProperty -Path HKLM:SoftwareMicrosoftWindowsCurrentVersionpoliciessystem -Name EnableLUA\n\n0 – disabled, 1 enabled\n
\nUse following PowerShell code:\n\nSet-ItemProperty -Path HKLM:SoftwareMicrosoftWindowsCurrentVersionpoliciessystem -Name EnableLUA -Value 0\n\nReboot is required. Use shutdown -r -t 0 command for immediate restart.\n
Install full GUI
\nUse following PowerShell code:\n\nAdd-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra\n\n(this is is an alias for Install-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra)\n\nReboot is required. Use shutdown -r -t 0 command for immediate restart.\n
\nUse following PowerShell code:\n\nRename-Computer NEWCOMPUTERNAME\n\nReboot is required. Use shutdown -r -t 0 command for immediate restart.\n
\nUse following PowerShell code:\n\nAdd-Computer -domainname YOURDOMAINNAME -cred YOURDOMAINNAMEUSERNAME -passthru\n\nReboot is required. Use shutdown -r -t 0 command for immediate restart.
While trying to move VM in Hyper-V 2012 I’ve noticed that it’s really slow process on my machine. One of possible solutions to it may be enabling of SR-IOV for your Hyper-V virtual switch (see screenshot for corresponding option in GUI).
SR-IOV stands for Single Root I/O Virtualization and it’s a technology introduced by PCI SIG which allows a PCIe device to appear to be multiple separate physical PCIe devices. This technology needs to be supported by your hardware BIOS as well as in the operating system instance or hypervisor that is running on the hardware.
But my attempt to enable SR-IOV for virtual switch (it requires creating a new virtual switch and checking corresponding check-box in Connection type section of virtual switch properties) lead to server crash… So it could be a good idea to ensure whether you have hardware support for SR-IOV before enabling it 🙂
Just type following in PowerShell:
In my case it returns following:
SR-IOV cannot be used on this system as the PCI Express hardware does not support Access Control Services (ACS) at any root port. Contact your system vendor for further information.
You may also receive more optimistic output from this command informing you that you probably need to enable SR-IOV in BIOS or update your BIOS.
Though most powerful capabilities of latest Windows Server 2012 release to my mind are related with its accomplished feature set and new usage scenarios I should admit that we people like to look at numeric metrics and increased figures. Incidentally, some of new things/scenarios available in Windows Server 2012 wouldn’t have been possible without significant scaling up of possible workloads and used resources. So you may find comparative table of scaling for nodes and workloads for WS2008R2 & WS2012RC below (sorry if you are cyrillically challenged, but only Russian version of table was available at my disposal).