medea61
Enthusiast
Enthusiast

customizing forever?

Jump to solution

Hello All

I am installing an vdi-eval-environment for a customer. VI itself seems ok, building the desktop-VMs (XP SP2 with latest patches) from the template with customization looks nice as well but when VDM creates a VM it hangs forever in status "Customizing" from VDMs point of view.

Ever seen such a situation? I am thankfu for every hint as I am pretty much stuck here...

Best regards

Roman

Tags (4)
0 Kudos
1 Solution

Accepted Solutions
jfberdyck
Contributor
Contributor

Straight from VMware support on this: at a command prompt on the machine in question, run "sc delete bootrun" (w/o quotes). I our case I didnt' even need to reboot the machine - it popped us as ready in the VDM console, and we were able to log right in. We did this with persistent pools and individually-deployed machines. The individual machines would read "ready" in the VDM, however they still would not allow login.

Apparently this is a known bug in the sysprep process.

View solution in original post

0 Kudos
26 Replies
admin
Immortal
Immortal

Hi Roman,

is it possible to connect to one of the provisioned desktops via the VDM client? If not, please login to the desktop through the VC Clients console and check if the desktop has an IP address, if it is in the domain you selected before. Possibly, you have anuser/password mismatch in the customization specification where you configure the username and password for joining a domain. What I've seen yesterday was an DNS issue which prevented the customization from joining the domain. In thiscase the VDMAdministrator website will show Cutomization.

Thanks,

Christoph

Was this answer helpful for you? Please use the correct/helpful buttons!

0 Kudos
medea61
Enthusiast
Enthusiast

Hello Christoph

is it possible to connect to one of the provisioned desktops via the

VDM client?

No. As none of them come up as "Ready". Smiley Sad

If not, please login to the desktop through the VC

Clients console and check if the desktop has an IP address,

Yes, they have.

if it is in the domain you selected before.

Yes to this too. I can login with Domain credentials as well.

> Possibly, you have anuser/password

mismatch in the customization specification where you configure the

username and password for joining a domain.

Does not look like it.

What I've seen yesterday

was an DNS issue which prevented the customization from joining the

domain. In thiscase the VDMAdministrator website will show

Cutomization.

No, DNS seems to be OK as well.

The only error I see in the eventlog of the VDI-VM is an error-message

that "VMware Boot Run" was unable to be started as the path was not

found. As the path shows something about "vmware_guestcust" I assume the

customization process is not removing this service after it's run. Not

very nice but this should not be a showstopper. All other processes

(incl. VDM-Agent) are running nicely.

Is there a way to debug this stuff?

--

Best regards,

Roman Hochuli

Operations Manager

nexellent ag

Saegereistrasse 29

CH-8152 Glattbrugg

Phone: +41 44 562 30 40

Fax: +41 44 562 30 41

URL: www.nexellent.ch

X-NCC-RegID: ch.nexellent

Imagination is the one weapon in the war

against reality.

-- Jules de Gaultier

0 Kudos
mittim12
Immortal
Immortal

On top of everything Christoph said I have also seen firewalls cause this type of behavior. Just for testing I would make sure I disable the windows firewall and any third party firewalls. This may clear up your problem.

If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points

0 Kudos
medea61
Enthusiast
Enthusiast

Hello mittim12

On top of everything Christoph said I have also seen firewalls cause

this type of behavior. Just for testing I would make sure I disable

the windows firewall and any third party firewalls. This may clear

up your problem.

At the moment there is no firewall between the VM-NIC and the customers

LAN. Windows-Firewall is/will be disabled in Grouppolicy.

--

Best regards,

Roman Hochuli

0 Kudos
maltic
Contributor
Contributor

Hi,

I have the same problem - did you find any solution for this?

Regards,

Malte

0 Kudos
medea61
Enthusiast
Enthusiast

Hello Malte

I have the same problem - did you find any solution for this?

Unfortunatley not. Smiley Sad

--

Best regards,

Roman Hochuli

0 Kudos
maltic
Contributor
Contributor

Crap, I already opened a ticket for this - but it takes ages for them to answer Smiley Sad

0 Kudos
admin
Immortal
Immortal

Customizing means, that the VC is still customizing the desktop or that it haven't finished sucessful. This could happens in various cases. Mostly something is wrong with the VC's customization specification. (Network/Firewall/License Key for Windows)

I've also seen, that when a GPO prohibits the execution of Windows FW, it was still running. Please check this directly on the NIC.

Do oyu have any information from the logfiles or Windows eventlog? Logfiles can be found on Client / Agent and Server. Is there something in the VC log?

0 Kudos
maltic
Contributor
Contributor

So what do you think should I check? I can access the VM using RDP and login ... no problem. No firewwall is installed on the client. The licenses key is ok (obviously).

0 Kudos
admin
Immortal
Immortal

So, you can directly connect via RDP to the virtual desktop?

This could mean:

You are using VDM 2.0

or

The VDM 2.1 Agent isn't running within the Virtual Desktop

Are you working with 2.1?

Thanks,

Christoph

0 Kudos
medea61
Enthusiast
Enthusiast

Crap, I already opened a ticket for this - but it takes ages

> for them to answer Smiley Sad

I am quite interested to hear the outcome of that when you have a reply...

So what do you think should I check? I can access the VM using RDP

and login ... no problem.

Same here. I can run the deployment with customization by hand without a

problem.

--

Best regards,

Roman Hochuli

0 Kudos
maltic
Contributor
Contributor

2.1

I can connect with RDP, Agent version 2.1.0.596 is installed.

Regards,

Malte

0 Kudos
admin
Immortal
Immortal

That's interesting. Normally the Agent should prohibit the direct access. Did you use the registry key to allow the access?

Can you find any information in the logs?

Thanks

Christoph

0 Kudos
maltic
Contributor
Contributor

No, I did not set anything in the registry, however I did an update from 2.0 to 2.1. Is there any log content you are interested in?

0 Kudos
admin
Immortal
Immortal

maltic,

maybe you could try to search the files for customizaton. In the VC you will find the logfiles in: %SYSTEMROOT%\temp\vpx

medea61,

have you also done an update from 2.0 to 2.1?

Thanks,

Christoph

0 Kudos
medea61
Enthusiast
Enthusiast

Hello Christoph

have you also done an update from 2.0 to 2.1?

No, this was a fresh install of 2.1.

--

Best regards,

Roman Hochuli

0 Kudos
maltic
Contributor
Contributor

Unfortunately there is no C:\Windows\Temp\Vpx directory on the VC server ...

0 Kudos
medea61
Enthusiast
Enthusiast

All

Just for fun I tried two things:

- Changing the name of the customization to not contain spaces

- Install XP SP3 on the VDI-Template

And magic it worked for the first vdi-client. The others (at the

moment two) are still hanging in 'Customizing' state.

--

Best regards,

Roman Hochuli

0 Kudos
maltic
Contributor
Contributor

Hm - I do not have spaces in the customization name - it´s vdi_xp_us ...

0 Kudos