
46
Troubleshooting
A few things can go wrong along the way here are some we’ve seen
DC Build stalls
If the NAS is not accessible from the DC then the build will stall after Windows and AD are installed. The VM
will autologon but not start the second phase build, there will be no PowerShell shortcut on the desktop.
Make sure that the NAS VM is running and accessible from the DC. Make sure the Build share is fully populated
and then rebuilt the DC.
There may be a message on screen about populating the build share then do as instructed.
Validate complains about not being run as administrator
The validate script must be Run as Administrator, right click the shortcut and select this from the popup menu.
DC fails Validate, databases missing
If the validate script reports that the databases are missing then the VC build will fail. Search in c:\Buildlog.txt
for the status “* Create vCentre Database” and look for errors below. If you see a “Shared memory provider:
Timeout error [258]” then the error was one of timing.
To create the databases locate the file b:\Unattend\DC\Phase2.cmd and edit it with notepad. Locate the text
“* Create vCentre Database” and look a little below for the SQLCMD command line. Paste the command line
into an elevated command prompt.
VC Build Fails to create vCenter Repository
This is the result of the DC failing to create the databases, see the above error. Once the databases exist then
completely rebuild the VC.
Error installing PowerCLI on VC
Sometimes a runtime error shows on the VC VM during install, wait a few minutes and click Retry.
Host1 build fails
If the VC build script cannot identify the version of ESXi in your B:\ESXi50 folder then it won’t setup the PXE
environment correctly. On the Build share in B:\Automate\DC there are folders of ESXi5_0_RTM and
ESXi5_0_U1 copy the contents of the appropriate folder into C:\TFTP-Root\ESXi50 on your DC and retry the
build.
Commenti su questo manuale