Win XP logon optimization and Group Policy

From: ShawnT (ShawnT_at_discussions.microsoft.com)
Date: 07/19/04


Date: Mon, 19 Jul 2004 15:13:02 -0700

We have a Windows 2000 Active Directory domain with approx 160 clients, most of which are Windows XP. I have configured Software Installation through Group Policy and it works fine except the clients have to reboot twice (because of the logon optimization in Windows XP) before the package is successfully delivered. I know how to fix this on the client through the local group policy by enabling 'Always wait for the network...' (Computer Configuration -> Administrative Templates -> System -> Logon). However, that would require me "touching" every client on the network.

Is there a way that I can enable this local policy on the Domain level or OU level? The only options that I have found at the Domain or OU level are to allow logon and startup scripts to run synchronously...this doesn't seem to fix the problem.

Thanks,
Shawn



Relevant Pages

  • Re: Logging on to TS with a local account
    ... The policy is being set at the domain level, that is why it is disabled in the local policy. ... You should also notice that the icon is the two computers with a paper scroll in front of it, instead of the blue and white icon. ... an administrator, my "add users or groups" option is grayed out. ...
    (microsoft.public.windows.terminal_services)
  • Re: Disabling "Access this computer from the Network"
    ... > Disabling Local Policy Settings is not enough because, ... > the line on the Tap page says, "If domain level policies ... only local group policy will apply. ...
    (microsoft.public.win2000.security)
  • Re: Cant logon to local machine (this computer) as administrator
    ... yes there was a difference between local setting and effective setting. ... I had to fix it at the domain level by taking out my settings there. ... >> can not log into thier local accounts anymore. ...
    (microsoft.public.win2000.security)
  • Re: Problems renaming a domain
    ... I have already raised the domain level in AD ... computers & trusts and it still gives this error. ... >> How do I fix this? ...
    (microsoft.public.windows.server.general)