Microsoft provides a new way to activate VMs hosted in Hyper-V, named Automatic Virtual Machine Activation (AVMA). It makes the activation step of VMs much easier.
- Hypervisor: Windows Server 2012 R2 Datacenter with Hyper-V role. Other versions are not supported. Dedicated Hyper-V Server is not supported.
- VM: Windows Server 2012 R2 Datacenter, Standard and Essentials.
- Prepare and activate your Hypervisor;
- Install supported OS as VM with the key listed below, or change the key of an installed VM with command “slmgr /ipk <key>”.
- Windows Server 2012 R2 Datacenter: Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW
- Windows Server 2012 R2 Standard: DBGBW-NPF86-BJVTX-K3WKJ-MTB6V
- Windows Server 2012 R2 Essentials: K2XGM-NMBT3-2R6Q8-WF2FK-P36R2
These keys are supported to being used in any unattend.exe setup file also.
This document is about upgrading vSphere 5.1 to 5.1 Update 1.
Phase 1: Preparation
You need these listed below:
- vCenter Installation Disc (iso): VMware-VIMSetup-all-5.1.0-1065152.iso;
- ESXi update package (zip, optional, will be used in Update Manager): update-from-esxi5.1-5.1_update01.zip;
- SSO admin password;
- vCenter service account password;
- An account within local administrators group of vCenter server; and,
- If you have Update Manager Client Plug-in installed on the same server of vCenter, it should be uninstalled before upgrading.
Phase 2: Upgrading vCenter and additions
- Insert vCenter Installation disc or mount iso.
- You cannot perform an upgrading installation by VMware vCenter Simple Install. It is required to upgrade all components manually as the same sequence as items listed in VMware vCenter Installer: vCenter Single Sign On, VMware vCenter Inventory Service, VMware vCenter Server, VMware vSphere Client (optional), VMware vSphere Web Client (optional) and VMware vSphere Update Manager.
- While upgrading the SSO (vCenter Single Sign On), you will be notified to enter the SSO admin password. A restart is required after performing SSO upgrading.
- Nothing more information is required while upgrading Inventory Service.
- Password of vCenter service account is required while upgrading vCenter Server. It is possible but highly not recommended to change service address or port while upgrading.
- All other 3 upgrading tasks are easy to perform. All you need is press Next button after starting the processes.
- (Optional) Check the server status by logging on from vSphere Client.
- (Optional) Install the Update Manager Client Plug-in now.
Phase 3: Upgrading ESXi
- Log on vSphere Client with Update Manager Client Plug-in.
- (Optional) Uploading ESXi upgrading package
- In the Update Manager Tab of the top level of vCenter Hosts and Clusters (top item from the left panel), select Admin View.
- In the Patch Repository tab, click Import Patches and upload update-from-esxi5.1-5.1_update01.zip. It will save downloading time of ESXi upgrading process.
- Go back to Compliance View.
- Scan your ESXi server.
- (Optional) Stage. You may want to stage one server first to test your patch repository before staging all servers.
- Remediate. You may need to set the servers in maintenance mode but not necessary. ESXi servers will be rebooted automatically after remediation.
Phase 4: VMtool upgrading
Upgrade VMtool on each virtual machine.
Phase 5: vSphere Client upgrading
Upgrade vSphere Client on all installed computer.
Phase 6: Troubleshooting
If there are some templates in your vSphere, you may need to convert them to virtual machine to upgrading VMtool. If this function is grayed out, you can re-enabled it by removing the related template from inventory and adding it back.
After deployment of Hyper-V Server, I trapped in trouble of linking Hyper-V Server to SCVMM.
Finally, I find a way to shutdown firewall of Hyper-V Server, which helps me resolved the problem.
- Log on to Hyper-V Server;
- Type this into cmd window:
netsh advfirewall set allprofiles state off
I have some hyper-v servers with broadcom NICs. Due to lack of UI (device manager and property window of NIC), it’s not easy to enable Jumbo Frame (MTU9000) setting.
After a google dig and some experiment, I find a way to achieve that.
- Install BACS (Broadcom Advanced Control Suite). You may want to use this tool for creating team also. Remember the 4-digit number within brackets before the NIC you want to change MTU.
- Open regedit, expand HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Class\4D36E972-E325-11CE-BFC1-08002BE10318}\(4-digit-number-of-NIC) on the left panel, you will get a value named “*JumboMTU” on the right. Change it to 9014 or any other value you need.
- Type this command “netsh int ipv4 sh int” to list all network. Remember the Name of the connection you want to change MTU.
- Type this command to change it to 9000 or any other value. The value should be the value you’ve set in step 2, minus 14:
netsh interface ipv4 set subinterface “Connection Name” mtu=9000 store=persistent
- Reboot to apply.
We changed our domain controllers of our company these days. Of course, we did that by SOP:
- use dcpromo to promote new servers as domain controllers;
- migrate PDC and other critical roles to the new domain controllers;
- use dcpromo to depromote the old domain controllers.
After these steps, all Windows servers works great.
But we can use neither vSphere Client nor vSphere Web Client to login vCenter with a domain account any more.
By asking VMware support, we realize we have to adjust Single Sign On for this change.
- Open vSphere Web Client, using admin@system-Domain to login;
- Select Sign-On and Discovery – Configuration from the left panel;
- You will the a record related to your domain on the right;
- Select the record and make a screen capture of all information;
(You cannot edit it directly, cos it won’t save successfully.)
- Delete that record and create a new one, with the same setting and new LDAP address;
(For Authentication Type, the existed one may set to Reuse Session, but you have to change it Password and leave an account with password below. I don’t know the reason.)
- Save it.
A small tool for deploying VMware ESXi from another computer running with Microsoft Windows.
DotNet framework runtime 4.o is required.