VMware Cloud Community
khughes
Virtuoso
Virtuoso

Template Deploy Customization Times Out

Yesterday I had to deploy out all new Citrix servers. I didn't get around to the last one now everything seems to be going sideways. I thought that maybe last nights bulk backup affected the unfinished deployment so I started fresh but it looks like the same thing is happening. It does the initial customization but once it gets to the IP settings / Domain, it times out. I had no issues yesterday in regards to the template or deploying them using the customizations. Double checked the customization settings 2-3x over.

The only thing that is different, in my mind shouldn't matter, is the template was made off of the name of machine I'm trying to deploy. Even so the customization should take care of that right? IE- Weeks ago I made a template off of Citrix6 and now I want to deploy to Citrix6.

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
5 Replies
Troy_Clavell
Immortal
Immortal

was/is Citrix6 a member of the domain? If so, remove it from the domain and redeploy

Reply
0 Kudos
khughes
Virtuoso
Virtuoso

It was, but that is part of my process pre-deployment. Shut down Citrix**, delete old VM from disk, login to AD, delete from OU - Then deploy.

When it timed out, I logged into the machine using the local admin account and the Sysprep files were sitting on the desktop (assume VC copied them over to run), so I just ran the Sysprep program and went through the process manually and it seemed to work / VM looks to be up and running like it should.

Could VMware's process run into issues if the template name is the same as the deployment name (like vmware's sysprep has issues trying to rename the machine to the same name?) It seems unlikely but I think that's the only difference.

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

so before you sealed the image, you removed it from the domain, correct? Even if the computer OU was removed from AD, i think having the VM still joined to the domain and not a workgroup would cause it not to join the domain during the deployment process.

Could VMware's process run into issues if the template name is the same as the deployment name (like vmware's sysprep has issues trying to rename the machine to the same name?) It seems unlikely but I think that's the only difference.

That could also be it as well. I would be curious to find out if you change the name to something other than Citrix6 and deployed again what would happen.

Reply
0 Kudos
khughes
Virtuoso
Virtuoso

To go through the whole process, we had an issue where something was installed on all of our Citrix servers, which caused a massive printing issue. Over the past couple months someone in the department had been doing Windows updates to the server, but not updating our template, so our template was about 4-5 months old. I had to restore on of our Citrix servers from backup (citrix6), then clone it to template. At that point, the VM I restored was still joined to the domain, no changes were made to it.

I was able to deploy that template, and use customization to join the deployed machines to the domain without any issue. The problem came up when I tried to deploy the new version of the same machine (citrix6) the template was made off of.

A different co-worker is going through our DR drill, so I'll copy the template over there when he's up and running and change the name and try the test again.

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

The problem came up when I tried to deploy the new version of the same machine (citrix6) the template was made off of.

If I were a betting man, I would say this is why you had the problem. Maybe your DR test will confirm.

Reply
0 Kudos