Terminal Server taking long time to log on for regular users

Posted on 2005-04-14
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

    Did you reboot after your REG changes?
    LVL 3

    Accepted Solution

    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...


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Enabling OSINT in Activity Based Intelligence

    Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

    I have never ceased to be amazed how many problems you can encounter on a fresh install of a Windows operating system.  This is certainly case in point& Unable to complete ANY MSI installation.  This means Windows Updates are failing and I can't …
    ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
    Internet Business Fax to Email Made Easy - With eFax Corporate (, you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, fr…
    In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…

    794 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

    Need Help in Real-Time?

    Connect with top rated Experts

    17 Experts available now in Live!

    Get 1:1 Help Now