View 4.5 Issues

[suri123]

Currently we are trying to deploy View 4.5 and we are having issues with deployed VM's. VM's have joined the domain and the machine accounts reside in AD , Domain users are entitled to the pool and they are not able to able to log into the domain. We are using the right agent.

Errors" View Composer agent initialization failed"

Error" Provisioning error occurred on Pool Comp-0 because of a configuration problem"

Error"Provisioning error occurred for Machine TComp-01: View Composer agent initialization failed"

Thanks for the help!

[w00005414]

Just as a follow up, I recreated our XP golden image and installed the KB944043 fix in it and rebuilt the pool and so far we haven't seen this error message

"Windows cannot connect to the domain, either because the domain  controller is down or otherwise unavailable, or because your computer  account was not found. Please try again later."

but last time we tried a different fix and recomposed the pool it seemed to take about 4 or 5 days before the problem crept up again so I am not 100% sure I am out of the woods yet.

One question though, in the virtual desktops I connect to I am still seeing the following 2 entries in the Application event viewer log around the time the virtual desktop is coming up with its new name.

------------------------------------------------------------------------------------------------

Automatic certificate enrollment for local system failed to contact the active directory (0x8007052b).  Unable to update the password. The value provided as the current password is incorrect.
  Enrollment will not be performed.

------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------

Windows cannot determine the user or computer name. (Access is denied. ). Group Policy processing aborted.

------------------------------------------------------------------------------------------------

Are these a normal result of the Quickprep process?

[wlftech]

I fixed it by adding the parent to the domain before cloning and making sure my Sophos firewall had the correct policy allowing the correct traffic. The admin guide tells you that you don’t have to have the parent joined to the domain prior to creating the linked clone pool but I have had better luck having it on the domain.

Thanks,

Michael

[w00005414]

Thanks Michael, I too have my master image joined to the domain so I can test domain related policies on it first. I don't have any extra firewalls installed, or even antivirus, just the Windows firewall with the appropriate ports open.

[wlftech]

What happens when you disable the Windows Firewall completely?

[w00005414]

Hmmm, I hadn't tried shutting off the firewall. Here are the ports that I open in the firewall along with the standard ones the vm agent install does like Remote Desktop

TCP Port 32111 (US Redirection) <- this one was already added by the Agent install
TCP Port 9427 (MMR - MultiMedia Redirection)
TCP Port 50002 (PCoIP)
UDP Port 50002 (PCoIP)
TCP port 4172 (PCoIP AES 128-bit encryption between View Client and View Agent on Virtual Desktop)
Allow ping requests

If the domain problem ends up creeping up again I'll investigate shutting off the firewall but I would rather not do that if I do not have to.

[wlftech]

I found through the Sophos firewall log that the PCoIP executable was being blocked as well. It was using a bunch of different ports so I just allowed the executable. C:\Program Files\Common Files\VMware\Teradici PCoIP Server\pcoip_server_win32.exe

That isn’t related to your domain issue, more a PCoIP connection thing.

Michael

These are the ones I have allowed:

RDP

4001

4172

8009

9427

32111

50002

51281

[mberthia0130]

Thanks for the information in this thread. As an FYI, I found the same issues on a Windows XP SP3 running the 4.6 version of the View Agent on a machine in a Windows 2003 AD environment (with no Windows 2008 DCs).  The patch listed in the thread ( http://support.microsoft.com/kb/944043/en-us) resolves the issue even in a Windows 2003 domain.

-Mike

[Peter_Grant]

The patch mentioned above http://support.microsoft.com/kb/944043/en-us also applies to Windows 2003 domains.

I know the KB say's it's to do with 2008 Read-Only DCs but it does resolve domain join issues with XP on Windwos 2003 domains as well with no 2008 DCs

[Peter_Grant]

I had this issue and found that setting the service to manual start up worked (and it was started once I checked). Saved me from having to write the script code.