+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 25 of 25
Windows Thread, GPO Processing -Allways wait for the network at computer startup - What do you choose in Technical; Originally Posted by Cools I will run a test to see what ones takes the longest i cant remember off ...
  1. #16
    TheLibrarian
    Guest
    Quote Originally Posted by Cools View Post
    I will run a test to see what ones takes the longest i cant remember off hand..
    Good place to start, then you can rebuild that one first and see if there's any improvement.

  2. #17
    ricki's Avatar
    Join Date
    Jul 2005
    Location
    uk
    Posts
    1,475
    Thank Post
    20
    Thanked 164 Times in 157 Posts
    Rep Power
    52
    Hi

    I dont know if this will help but I have come across a couple of things in the last 12 months that will cause this.

    When I have a server go off line we get this because either a script or a group policy is looking for a server that is not accessible. The machine then spends ages looking for the server and eventually gives up. This does have the cause that startup and log on times can be huge, but it also causes the problem that group policies dont apply correctly.

    Have a look at all your group policies and scipts and look for things pointing at the wrong place.

    Have a look in the event viewer and see if it has anything. This can lead you to shares being pointed at the correct place but permissions on files and shares set wrong.

    Do you point redirects and paths through DFS if so point them directly at the share. DFS can be broke and cause all sorts of hastle.

    Have a look at DNS and dhcp and check all the entries are correct. For example say you replaced a server in the past and did not set the DNS ips to the new server it will have to wait a bit for the computer to try the next one.

    Have a look at replication on the servers and check its all working.

    Try dcdiag and netdiag and see if errors come up.

    Good luck with this one.

    Richard

  3. #18
    Cools's Avatar
    Join Date
    Jan 2009
    Location
    Bedfordshire
    Posts
    498
    Thank Post
    24
    Thanked 62 Times in 57 Posts
    Rep Power
    25
    I disabled student user GPO and and reset it up from Base line GPO now its 3 min from boot.. that's better..
    I did not enable all the GOP settings as some are not needed any more..

    I did migrate from 2003 to 2008 so it must have picked up a BUG.. Well I was rushing last yr to get it up and running.

    see if can get it faster..
    I got my students roaming profile down to only 1.43mb

  4. #19
    ricki's Avatar
    Join Date
    Jul 2005
    Location
    uk
    Posts
    1,475
    Thank Post
    20
    Thanked 164 Times in 157 Posts
    Rep Power
    52
    Hi
    Sorry I forgot is this on all of the network or just part or just one. I have had it in the past where a switch is wonki and needs rebooting or replacing.

    Richard

  5. #20
    TheLibrarian
    Guest
    Quote Originally Posted by Cools View Post
    I disabled student user GPO and and reset it up from Base line GPO now its 3 min from boot.. that's better..
    That's a nice improvement.

  6. #21
    Mr.Ben's Avatar
    Join Date
    Jan 2008
    Location
    A Pirate Ship
    Posts
    942
    Thank Post
    182
    Thanked 158 Times in 126 Posts
    Blog Entries
    2
    Rep Power
    65
    Have you looked at the policy that allows sycronous or asyncronous GPO processing?

    As I understand it, the wait for network GPO literally waits until it has confirmed it's IP then gets on with it.

    If you process the policies async, The GPO processing can occur after login (although software installation before login still works), giving the users the impression that logon is quick. Once the GPO's have been processed once they will stick around until you change them.

  7. #22

    Join Date
    Jul 2010
    Posts
    1
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Hi Guys,

    The first thing I would check is which DC is authenticating the workstation. To check which Server has authenticated the workstation you can use the LOGONSERVER environment variable. To list the environment variables use the SET command from DOS prompt (CMD).

    e.g. LOGONSERVER=SERVER1

    If this DC in not the local machine you will need to check that all your subnets are configured correctly in sites and services.

    Option 2
    --------
    Mark Russinovich has a good blog entry which details how to use Process Explorer to identify processes that might be taking excessive amounts of time to execute. (The Case of the Slow Logons)

    Sorry I cant post links because this is my first post

    Good luck.

  8. #23

    SpuffMonkey's Avatar
    Join Date
    Jul 2005
    Posts
    2,249
    Thank Post
    55
    Thanked 280 Times in 187 Posts
    Rep Power
    134
    There's a patch for XP SP3 that fixes a login problem (usually after a password change) that really slows down logins - sorry - can't remember the link at the mo

  9. #24
    Cools's Avatar
    Join Date
    Jan 2009
    Location
    Bedfordshire
    Posts
    498
    Thank Post
    24
    Thanked 62 Times in 57 Posts
    Rep Power
    25
    Netdiag.exe tool has been deprecated in Vista and Windows Server 2008. It's not supported.




    Directory Server Diagnosis


    Performing initial setup:

    Trying to find home server...

    Home Server = DARKSTAR

    * Identified AD Forest.
    Done gathering initial info.


    Doing initial required tests


    Testing server: Default-First-Site-Name\DARKSTAR

    Starting test: Connectivity

    ......................... DARKSTAR passed test Connectivity



    Doing primary tests


    Testing server: Default-First-Site-Name\DARKSTAR

    Starting test: Advertising

    ......................... DARKSTAR passed test Advertising

    Starting test: FrsEvent

    ......................... DARKSTAR passed test FrsEvent

    Starting test: DFSREvent

    ......................... DARKSTAR passed test DFSREvent

    Starting test: SysVolCheck

    ......................... DARKSTAR passed test SysVolCheck

    Starting test: KccEvent

    ......................... DARKSTAR passed test KccEvent

    Starting test: KnowsOfRoleHolders

    ......................... DARKSTAR passed test KnowsOfRoleHolders

    Starting test: MachineAccount

    ......................... DARKSTAR passed test MachineAccount

    Starting test: NCSecDesc

    ......................... DARKSTAR passed test NCSecDesc

    Starting test: NetLogons

    ......................... DARKSTAR passed test NetLogons

    Starting test: ObjectsReplicated

    ......................... DARKSTAR passed test ObjectsReplicated

    Starting test: Replications

    ......................... DARKSTAR passed test Replications

    Starting test: RidManager

    ......................... DARKSTAR passed test RidManager

    Starting test: Services

    ......................... DARKSTAR passed test Services

    Starting test: SystemLog

    An Warning Event occurred. EventID: 0x800007DC

    Time Generated: 07/22/2010 14:36:09

    EvtFormatMessage failed, error 15100 Win32 Error 15100.
    (Event String (event log = System) could not be retrieved, error

    0x3afc)

    An Error Event occurred. EventID: 0xC0000010

    Time Generated: 07/22/2010 15:09:58

    EvtFormatMessage failed, error 15100 Win32 Error 15100.
    (Event String (event log = System) could not be retrieved, error

    0x3afc)

    ......................... DARKSTAR failed test SystemLog

    Starting test: VerifyReferences

    ......................... DARKSTAR passed test VerifyReferences



    Running partition tests on : ForestDnsZones

    Starting test: CheckSDRefDom

    ......................... ForestDnsZones passed test CheckSDRefDom

    Starting test: CrossRefValidation

    ......................... ForestDnsZones passed test

    CrossRefValidation


    Running partition tests on : DomainDnsZones

    Starting test: CheckSDRefDom

    ......................... DomainDnsZones passed test CheckSDRefDom

    Starting test: CrossRefValidation

    ......................... DomainDnsZones passed test

    CrossRefValidation


    Running partition tests on : Schema

    Starting test: CheckSDRefDom

    ......................... Schema passed test CheckSDRefDom

    Starting test: CrossRefValidation

    ......................... Schema passed test CrossRefValidation


    Running partition tests on : Configuration

    Starting test: CheckSDRefDom

    ......................... Configuration passed test CheckSDRefDom

    Starting test: CrossRefValidation

    ......................... Configuration passed test CrossRefValidation


    Running partition tests on : edwardpeake

    Starting test: CheckSDRefDom

    ......................... edwardpeake passed test CheckSDRefDom

    Starting test: CrossRefValidation

    ......................... edwardpeake passed test CrossRefValidation


    Running enterprise tests on : edwardpeake.local

    Starting test: LocatorCheck

    ......................... edwardpeake.local passed test LocatorCheck

    Starting test: Intersite

    ......................... edwardpeake.local passed test Intersite

  10. #25
    Cools's Avatar
    Join Date
    Jan 2009
    Location
    Bedfordshire
    Posts
    498
    Thank Post
    24
    Thanked 62 Times in 57 Posts
    Rep Power
    25
    Quote Originally Posted by Whiterussian View Post
    Hi Guys,

    The first thing I would check is which DC is authenticating the workstation. To check which Server has authenticated the workstation you can use the LOGONSERVER environment variable. To list the environment variables use the SET command from DOS prompt (CMD).

    e.g. LOGONSERVER=SERVER1

    If this DC in not the local machine you will need to check that all your subnets are configured correctly in sites and services.

    Option 2
    --------
    Mark Russinovich has a good blog entry which details how to use Process Explorer to identify processes that might be taking excessive amounts of time to execute. (The Case of the Slow Logons)

    Sorry I cant post links because this is my first post

    Good luck.

    Only have 1 DC for 129 PC's

SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. A RunOnce that works at computer startup?
    By PiqueABoo in forum Coding
    Replies: 8
    Last Post: 22nd July 2010, 09:11 PM
  2. Replies: 1
    Last Post: 6th July 2010, 03:23 PM
  3. Replies: 5
    Last Post: 25th January 2007, 11:22 PM
  4. Replies: 7
    Last Post: 27th November 2006, 11:26 AM
  5. Computer Startup Scripts
    By Spot in forum Windows
    Replies: 18
    Last Post: 16th November 2005, 11:06 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •