VMware SOFTWARE REPOSITORY FOR WINDOWS 1.1 Instrukcja Użytkownika Pobierz pdf (Strona 64)

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. There may be a message on screen about populating the build share, make sure

you have put the required files in the right places. Make sure the Build share is fully

populated and then rebuilt the DC.

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 vCenter 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 vCenter 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

A “runtime error 1618” shows on the VC VM during install. This is a purely cosmetic error;

either ignore it or wait a few minutes and click Retry.

1 2 ... 59 60 61 62 63 64 65 66 67 68

Brak uwag

VMware SOFTWARE REPOSITORY FOR WINDOWS 1.1 Instrukcja Użytkownika Strona 64