Solved

Group Policy and Fast Logon Optimization Feature

Posted on 2010-09-01
2
2,061 Views
Last Modified: 2012-05-10
I am attempting to push out an MSI client via group policy. On some workstations, the software installs just fine. On others, it appears the policy applies but does not install the software during synchronus startup. As a test I modified the Fast Logon Optimization feature to be enabled so it would behave as a Windows 2000 client. The referenced policy path is here:

Computer Configuration\Administrative Templates\System\Logon\ Always wait for the network at computer startup and logon

http://support.microsoft.com/kb/305293

I've tested the same 2 machines with the issue and did not notice a change. I've rebooted more than the 2 required. I've receive a reboot response when i run a gpupdate /force.

So now I'm left with more questions than answers. At the default domain policy level, the setting is set to "not configured". I am curious as to whether or not the default domain policy is overriding the ou applied GPO of "enabled".

Anybody have any ideas on some things I can test or verify?
0
Comment
Question by:AxiomEmp123
2 Comments
 
LVL 57

Expert Comment

by:Mike Kline
ID: 33577877
You can run an RSoP report to see what is applying.  The only way the domain policy would win is if enforced is set on it....otherwise the OU policy will win/take precedence

Any events in the logs of the machines that are failing?

Thanks

Mike
0
 

Accepted Solution

by:
AxiomEmp123 earned 0 total points
ID: 33578107
User "entcee" had a solution posted for a seemingly related problem which I just tested and it worked.

"I found this on Miscrosoft site. These changes do exaclty what I am looking for. Now the computer actually waits for the DC and applies the GP (machine) settings before the logon screen is displayed.

Here are the changes:
Windows XP Service Pack 2
After you apply Windows XP Service Pack 2, you must add the GpNetworkStartTimeoutPolicyValue registry entry. This entry defines the number of seconds to wait before trying to run the Group Policy startup script again. To find the value that will work for your configuration, define a decimal value of 60, and then increase the value until the problem is resolved. To add the registry entry and to define the value, follow these steps:1. Click Start, click Run, type regedit, and then click OK.
2. Expand the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
3. Right-click Winlogon, point to New, and then click DWORD Value.
4. To name the new entry, type GpNetworkStartTimeoutPolicyValue, and then press ENTER.
5. Right-click GpNetworkStartTimeoutPolicyValue, and then click Modify.
6. Under Base, click Decimal.
7. In the Value data box, type 60, and then click OK.
8. Exit Registry Editor, and then restart the computer.
9. If the Group Policy startup script does not run, increase the value of the GpNetworkStartTimeoutPolicyValue registry entry.

Back to the top

Creating a Group Policy network start timeout policy
The GpNetworkStartTimeoutPolicyValue policy timeout can be specified in the registry in two locations:" HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\Winlogon
" HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System
You can do this by adding a DWORD value of GpNetworkStartTimeoutPolicyValue with a number of seconds between 30 and 600.

Windows reads the Winlogon subkey first. Then, Windows reads the Policies subkey. The value in the Policies subkey supersedes any value in the Winlogon subkey. There is no user interface that you can use to set this Group Policy object (GPO). Therefore, you have to deploy a custom ADM file in order to set the GPO.

The value specified should be of sufficient duration to make sure that the connection is made. During the timeout period, Windows examines the connection status every two seconds and continues with system startup as soon as the connection is confirmed. Therefore, setting the value larger than the minimum value of 30 is recommended. However, be advised that if the system is legitimately disconnected, Windows will stall for the whole timeout period. "
0

Featured Post

Backup Your Microsoft Windows Server®

Backup all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Join & Write a Comment

Mapping Drives using Group policy preferences Are you still using old scripts to map your network drives if so this article will show you how to get away for old scripts and move toward Group Policy Preference for mapping them. First things f…
When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup". After a while, you have entered a loop for Auto repair which does not fix anything and you will be in a  panic as all your work w…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

707 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

19 Experts available now in Live!

Get 1:1 Help Now