VMware Horizon Community
mlind
Contributor
Contributor

QuickPrep not joining VM to domain properly

I am having an issue with my Evaluation View joining my Domain properly using View Composer Linked Clones and QuickPrep.

The computer account is created properly in the Domain under any OU I specify. However, upon logging in with View Client I am presented with a login box, and no DOMAIN options.

I then have to join the machine manually which causes other issues if the Computer Account is not properly removed from the Domain first.

Thanks

0 Kudos
10 Replies
Linjo
Leadership
Leadership

A few things to check:

Is the View Agent the last software installed?

Is the master VM joined to the domain?

Did you do a ipconfig /release before closing down the master VM?

Did you take a snapshot with the master VM turned off?

Does the quick-prep user have priviliges to join machines to the OU?

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
mlind
Contributor
Contributor

Answers in-line:

Is the View Agent the last software installed?

View Agent Software was last to be installed and is on the ParentVM Snapshot.

Is the master VM joined to the domain?

No. Does it have to be? I figured it would be better not to have the Master on the domain.

Did you do a ipconfig /release before closing down the master VM?

No. Again does this matter? The master is set to DHCP.

Did you take a snapshot with the master VM turned off?

No. Master was on.

Does the quick-prep user have priviliges to join machines to the OU?

Yes.

0 Kudos
Linjo
Leadership
Leadership

Ok, then its easy, On all the answers that said "No" you need to make it a "Yes". Smiley Happy

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
mlind
Contributor
Contributor

Ok. That does work.

Can someone either explain to me why these steps are required? Or at least to the document that says they are required? As far as I could read no VMWare doc states that the parent must already be joined, a releases IP address, a snapshot taken from a powered off Parent, or View Agent software needs to be "last" application installed.

Thanks

0 Kudos
kjb007
Immortal
Immortal

Check the View 4 Deployment Guide and the view xp deployment guide

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
0 Kudos
patrcho
Contributor
Contributor

I did all the above as you are mentioned. But I still get error

8/24/10 7:40:45 AM EDT: View Composer agent initialization state error (18):

Failed to join the domain (waited 570 seconds).

Do you have any idea?

0 Kudos
mlind
Contributor
Contributor

Here are my steps:

1. Parent VM has to be joined to domain

2. ipconfig /release on parent VM and shutdown Parent VM.

3. Create Snapshot

4. Ensure that QuickPrep user has the ability to join PCs/VMs to domain

5. Ensure that DNS is working properly and I can ping domain by name

If all the above are good I have had no issues with QuickPrep joining to the domain.

0 Kudos
morrisosu
Contributor
Contributor

I'm having the same exact issue with a Windows XP Pro SP3 image, I have followed these steps exactly and I am still getting a "failed to join to the domain".

error in the View Admin console.

Its interesting, the desktop makes it to AD in the proper container after being provisioned, but you cannot log into domain on the VM (cannot connect to the domain error, etc..) and after a lengthy wait in a customizing state, the status will eventually change to an error state in the view admin console.

I have verified network connectivity to the VM, I can ping via computer name and I have verified the View Agent was installed last.

Note, we do not have this issue with View 4.0.1 and it is running on identical hardware in our AD environment.

Any ideas?

Thanks for the help,

Shane

0 Kudos
eeg3
Commander
Commander

Install this Microsoft patch and it should fix your issue.

Blog: http://blog.eeg3.net
0 Kudos
morrisosu
Contributor
Contributor

This patch has made my day!

Note, we are still on a 2003 functional level but we have 2008 R1 domain controllers and the patch worked great!

Here are the steps I took, adding what you guys did:

1. Set vDS for VDI to Ephemeral - no binding (I tried Dynamic, but I was getting "Invalid configuration for device 'x") on master image.

2. Parent VM has to be joined to domain

3. Install http://support.microsoft.com/kb/944043/en-us on base image.

4. ipconfig /release on parent VM and shutdown Parent VM.

5. Create Snapshot

6. Ensure that QuickPrep user has the ability to join PCs/VMs to domain

7. Ensure that DNS is working properly and I can ping domain by name

Thanks again for everyone's help.

0 Kudos