If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
runas takes a long time for certain users
I have an autologin script that I wrote using TCL that launches Internet
Explorer on shared devices with a specific user context. To do this I launch cmd.exe from runas and perform some file operations in the user shell and then launch IE from cmd. The script works great for about 95% of users in a 10,000+ user environment, but I've noticed that for some users, cmd.exe takes around 20-25 seconds to initialize and bring me to the command prompt. Typical behavior for the 95% that works is that this happens in around 1 second. When this pause happens I get: "Attempting to start c:\windows\system32\cmd.exe as user "domain\user" ..." This prompt persists for 20-30 seconds and then I get the prompt and life is good again. I'm trying to nail down why I may get this pause for only a small fraction of the users as this launch is somewhat time sensitive. This problem is also not machine specific, but user specific. Thanks in advance, Kris |
Ads |
#2
|
|||
|
|||
runas takes a long time for certain users
Nevermind...found out that this was due to an invalid path setting in the
Profile Path of their AD profile. FYI in case anyone else (doubtfully) ever runs into this. "franzpaniero" wrote: I have an autologin script that I wrote using TCL that launches Internet Explorer on shared devices with a specific user context. To do this I launch cmd.exe from runas and perform some file operations in the user shell and then launch IE from cmd. The script works great for about 95% of users in a 10,000+ user environment, but I've noticed that for some users, cmd.exe takes around 20-25 seconds to initialize and bring me to the command prompt. Typical behavior for the 95% that works is that this happens in around 1 second. When this pause happens I get: "Attempting to start c:\windows\system32\cmd.exe as user "domain\user" ..." This prompt persists for 20-30 seconds and then I get the prompt and life is good again. I'm trying to nail down why I may get this pause for only a small fraction of the users as this launch is somewhat time sensitive. This problem is also not machine specific, but user specific. Thanks in advance, Kris |
Thread Tools | |
Display Modes | |
|
|