Can't login to Virtual desktop after reboot

[ckboon]

Hi,

I am testing VDI on a VMware server, WinXP & a HP thin client. Every time I reboot the WinXP VM, I need to login via the console 1st before I can get a RDP connection. After I have login to the VM and logout, I can start a RDP connection. Is there some WinXP service I need to start automatically?

Thanks for the help.

[williambishop]

Have you tried to build another to see if it is just "that" session? I have had some bizarre things happen in some vm's. I generally just delete them and build a new one.

[ckboon]

Yeah I did. I build 2 "master" WinXP images and then clone 1 of them. They have the same problem. I suspect it's one of the WinXP services that is not started automatically but I don't know which one.

[paramd]

Did you check the usual suspects?

1) Make sure Remote connections are allowed. They are for "administrator" by default.

2) Make sure the user you are login as is added to list of "Remote Desktop Users" group

3) Under the "services" console make sure Terminal Services is started and is set to automatic. It sometimes gets set to manual and doesn't start when you reboot. (In a Vista mage I was testing, this was the case)

4) If you have a firewall, try disabling it or enable RDP port 3389 is in the allowed exceptions.

-Param

[ckboon]

Hi,

It turned out to be "Terminal Services". I had to switch it to automatic.

I thought it was "Remote Desktop Help Session Manager" but that didn't help.

2) Make sure the user you are login as is added to

list of "Remote Desktop Users" group

I did that under the Local Users group. Do I have to do it under the Active Directory side as well?

Thanks for the help.

[TomHowarth]

next time you post a question, mark it as such. it is a little reward for those that reply.

[Blithespirit]

You say you cloned the first XP HD, did you try a clean build of XP to see if suffered the same?

I created an XP template in ACE checked it worked, then used importer to bring it into my ESX server. I had the chance to cut down on what could cause and issue and manage the issues compartmentally. may help.

[williambishop]

Here's a little entry that works wonders with this problem. Download autohotkey( a very rich scripting program), and create a new script with the following text:

; <COMPILER: v1.0.46.7>

#notrayicon

regwrite,REG_DWORD,HKLM,SYSTEM\CurrentControlSet\Services\TermService,Start,2

save the file, then compile it with autohotkey, your problems are solved. Add in the following line and you'll up your timeout for your disks so a brief disconnect from the san doesn't affect you. You can put it in a login script, or push the script as you like....It's silent by the way, no user intervention required.

regwrite,REG_DWORD,HKLM,SYSTEM\CurrentControlSet\Services\Disk,TimeOutValue,60