Over on the Uptime blog there are some interesting posts concerning SRM 4.0. It’s kinda odd really – you get SRM post on the Uptime blog but different posts also SRM related on the viops.com blog – both run by VMware. I guess its the old age problem of how delimitate content and categorize it. Sometimes the Uptime blog is very er, operational – and other times the viops blog is very much about uptime issues!
The first post concerns support for Windows 2008 and SRM 4.0
In nutshell you can install SRM to Windows 2008 but it must be the 32-bit edition, SRM 4.0 is not supported on 64-bit. However, the plug-in which installs to the vSphere4 Client the 64-bit version is supported. The blogpost explains how this has caused some confusion. Mmm, no surprises there then.
Of course, Windows 2008 is supported as target for recovery – but if you use guest customization to re-IP the VM (I wouldn’t recommend doing that), then that’s only supported on the 1st release, there isn’t support for R2 and re-IPing.
Phew. Glad that’s all clear then!
The other blog post concerns a change to licensing if you are running on vSphere 4 UPDATE 1. [Note: Doesn’t apply if you haven’t moved up to U1 yet]. Put simply the license key is now held along side all the other license keys in the vSphere4 client – and you alllocate the SRM license to the “solution’ which is SRM.
This blog article references KB article – http://kb.vmware.com/kb/1016111
Something I experienced during the roll-out of vSphere4 U1 was having to repair the SRM installation afterwards…