HDas
Contributor
Contributor

Sysprep doesn't work using Orchestrator

Hello There,

I have been working on this issue for a long time now but couldn't fix it.
Please help me

When I use a template to clone and use Customization option , Sysprep runs fine and I am able to join the machine to the AD domain without any issue.
This tells me that the template is good and the files on the vcenter server are fine.

But When I use Orchestrator to sysprep the same template and join the machine to the domain , it fails.
It does the clone part fine but doesn't join the machine to the domain.

I am given to understand that Orchestrator will use the mini setup answer file to Sysprep.


I created it. Looks Like :


;SetupMgrTag
[Unattended]
    OemSkipEula=Yes
    InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
    AdminPassword="howru$%#"
    EncryptedAdminPassword=NO
    OEMSkipRegional=1
    TimeZone=190
    OemSkipWelcome=1

[UserData]
    ProductKey=#$%-56$-6$%^-J#$@T-*&^$
    FullName="Admin"
    OrgName="System"
    ComputerName=*

[TapiLocation]
    CountryCode=91

[SetupMgr]
    DistFolder=C:\sysprep\i386
    DistShare=windist

[Identification]
    JoinDomain=bruaah.co.in
    DomainAdmin=custo
    DomainAdminPassword=yeahrite$%^

[Networking]
    InstallDefaultComponents=Yes

The Workflow I use is  "Clone, Windows Sysprep with single NIC and credential"

It clones the machine fine but Sysprep doesn't seem to work and it doesn't bring the machine to the AD Domain.

I have changed the resource path to point to the correct inf file.

It fails when it is at :
Wait for a given name in the DNS guest informations (Vmware Tools)

And Eventually says
[2012-05-21 11:08:43.018] [I] Timeout: Unable to get a DNS name for the VM before reaching the Timeout (Dynamic Script Module name : vim3WaitDnsNameInTools#38)

I have ESX 4.1 Version

Thanx in advance

0 Kudos
1 Reply
tschoergez
Leadership
Leadership

Hi!

In which way do you provide the sysprep answer file to this workflow?

For further troubleshooting: Can you watch the console of the new VM to see what goes wrong?

See this thread and the links there are some more ideas...

http://communities.vmware.com/thread/311899

http://communities.vmware.com/message/1869711

To save some time: You can also try to separate the clone and the customize task in your workflows... See an "Customize only" example here:

http://www.vcoportal.de/2011/04/customize-a-virtual-machine/

Cheers,

Joerg

0 Kudos