Figure 1: Finally, the v Center installer cannot handle the database requirements directly, so I found myself using the /passive switch to silent install the Microsoft SQL Native Drivers.
And then, using the ODBC Manager, I created a System DSN connect to the database.
It’s also part of another of my projects to fully automate the build out process of a VMware management layer.
In my environment, the Microsoft SQL Server is always an external machine regardless of whether it is physical or virtual.
That’s why I was pleased to see VMware finally support Windows Authentication to the Microsoft SQL Server as this is more secure and more desirable than the older, less secure and legacy SQL Authentication.
Normally, that would be automatically granted during a manual install but not when it is scripted.
Sadly, Windows 2008 no longer ships with the old utility that would allow you to script this portion of the prerequisites, so you may be forced to use the “Local Policy” snap-in instead (see Figure 1).
But if you’re getting errors and general weirdness when getting the scripted install to work, you’re caught in a “don’t call us” situation.
In my deployment, for instance, I’ve never used free database engines such as SQL Express with v Center.
This way you are covered and have a backup that is easily restored to get you back to a working state.
However, even though I had the backup, fortunately I did not have to roll back to it and was able to safely delete after verifying everything had been upgraded successfully and was working.
There’s precious little written right now, on the cusp of the general availability of v Sphere5, about how to automate the installation of v Center and VUM.