| Author | Messages | |
kcnychief
Posts:0
 | | 01/04/2010 3:20 PM |
| Not saying it will help you specifically but these are also good references for this type of problem -
http://blogs.technet.com/askds/archive/2009/09/23/so-you-have-a-slow-logon-part-1.aspx
http://blogs.technet.com/askds/archive/2009/09/24/so-you-have-a-slow-logon-part-2.aspx
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Nelson, Jamie
Sent: Tuesday, December 22, 2009 4:15 PM
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] troubleshooting group policy when machine off the domain
Best bet is to turn on verbose logging and correlate the delay the user is experiencing to the timestamps in the log.
Jamie Nelson | Sr. Administrator | BI&T Infrastructure-Intel | Devon Energy Corporation | Work: 405.552.8054 | Mobile: 405.248.7963 | http://www.dvn.com
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Dave Sharples
Sent: Tuesday, December 22, 2009 3:07 PM
To: xxxxxxxxxxxxxxxx
Subject: Re: [gptalk] troubleshooting group policy when machine off the domain
Hi, thanks for the reply.
In our cases the scripts are all stored centrally on the network, nothing on the machine locally which references network resources. Our script timeout is 2 hours (we use scripts for some software installations), but this machine times out after one hour and goes to the login prompt. The machines are Windows 7 (could be vista).
I was guessing that if there is no network connectivity it wouldn't try and run the scripts.
It isn't consistent though, i.e some laptops are ok I think but some do weird stuff so kinda stuck how to troubleshoot it to see what it is doing for that hour
Thanks
On 22 Dec 2009, at 20:59, Darren Mar-Elia wrote:
> Dave-
> One thing that always comes to mind when off the network and using scripts is the script timeout. I would think that normally, if the scripts are stored remotely, this would fail immediately, but if you had scripts running locally that were trying to connect to resources or perform tasks that hang when not on the network, then the script timeout could come into play. By default its only 10 minutes but I wonder if you've adjusted that? Just a possible avenue of exploration. Also, if this is XP, you could have them enable userenv logging and see if that doesn't point the way.
>
> Darren
>
> -----Original Message-----
> From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Dave Sharples
> Sent: Tuesday, December 22, 2009 12:55 PM
> To: xxxxxxxxxxxxxxxx
> Subject: [gptalk] troubleshooting group policy when machine off the domain
>
> Hi, probably a vague question, but whats the easiest way to troubleshoot domain joined laptops which when off the domain (and network) take an hour to boot up before timing out and giving a login prompt.
>
> I guess the machine could be connected to any random wireless network at the time
>
> Does having startup scripts as part of the machine startup in group policy impact this (didn't think it does).
>
> kinda stuck where to start with why it takes so long.
>
> Thanks
>
> Dave
Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged.
If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of all or any portion of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system.
CONFIDENTIALITY NOTICE: This e-mail message (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorized review, use, disclosure, dissemination, copying, forwarding or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient but do not wish to receive communication through this medium, please so advise the sender immediately.
| | | |
|
|