Terminal Server taking long time to log on for regular users

Posted on 2005-04-14
Medium Priority
Last Modified: 2010-04-18
Server 2003 Standard, Running as a terminal server as well as the domain/AD controller.  everything was working fine when I started today... I was trying to get some things working with ACT! 2000 (version 5) and their support docs said to make some reg changes to HKey_classes_root 's security I deviated from their suggested Everyone group to a group I created called ACT_Term_Serv_users.  The changes were only to the security settings giving the group access to Query, Set Value, Create Subkey, Enumerate Subkeys, Notify, Delete, and Read Control.  

After I added these changes to the registry I decided to try it out and logged off the one user in the group and logged back in as her... to my surprise I was confronted immediately with an error of "Cannot find Script engine "VBScript" for Script ...\logon.vbs"  I hit okay and continued... I waited.. and waited.... became impatient and went over to the administrator's Remote Desktop, poked around and looked at all the users using term serv.

At this point I had remembered hearing about this error with large amounts of open handles, so I resolved an issue of handles but the problem remains after a couple of tries and reboots.

Consequently, no one is able to log in under terminal services, and the only three processes listed for each user is csrss.exe, winlogon.exe, rdpclip.exe ......... after a while I'll see userinit.exe pop up, stay a couple minutes and go away... but nothing else.

I've tried taking the registry changes back out but with no luck.

What is going on? how do I fix it?

Question by:adubla
LVL 20

Expert Comment

ID: 13787892
Did you reboot after your REG changes?

Accepted Solution

jeroenlemaire earned 1500 total points
ID: 13842909
did you make your reg changes with your users live?
that's defintely causing problems.

You should first clear your server of all users before applying registry changes.
Then you need to set your server in install mode.
take a dos box and type the command
change user / install

now make your registry changes

than go to the dos box again and use the command
chage user /execute

This last one distributes the regchanges for all users...
You should always make regchanges in install mode...

Hope this helps...


Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Many of us need to configure DHCP server(s) in their environment. We can do that simply via DHCP console on server or using MMC snap-in on each computer with Administrative Tools installed in a network. But what if we have to configure many DHCP ser…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
With just a little bit of  SQL and VBA, many doors open to cool things like synchronize a list box to display data relevant to other information on a form.  If you have never written code or looked at an SQL statement before, no problem! ...  give i…
The Relationships Diagram is a good way to get an overall view of what a database is keeping track of. It is also where relationships are defined. A relationship specifies how two tables connect to each other. As you build tables in Microsoft Ac…

578 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question