|
I run the following reg file on all our images with the same
effect. I'm not real clear why MS changed the default. It seems to
me that it has the potential of circumventing system security. If I've set
something in GP, I want it applied before any user can use the system.
Windows Registry Editor
Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon] "SyncForegroundPolicy"=dword:00000001 From: [EMAIL PROTECTED] on behalf of Rick Kingslan Sent: Tue 5/10/2005 7:33 PM To: [email protected] Subject: RE: [ActiveDir] Computer Configuration GP applying to W2K but not WinXP And, from personal experience in our Enterprise, I can absolutely guarantee that what Darren says is true. I, too, had a problem where policy parts and pieces were getting applied. Looking into it, if I ran GPResult/RSoP, I could see that more and more was being applied on each reboot (again – this was XP… Win2k worked fine). Turned off ‘Fast Logon Optimization, and it immediately resolved the problem.
And, to that – not one user has complained that it takes too long to boot up, either. Wouldn’t have mattered if they had, anyway. J
-rtk
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Darren
Mar-Elia
Yes, this is expected because Fast Logon Optimization is enabled, which essentially says don't wait for the network before presenting the logon screen. This screws with certain policy. Try enabling the following policy on those XP machines:
Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Brenda
Casey The computer configuration policy will apply after several reboots and a gpupdate /force (but not just a gpupdate). I didn't think that it should take several reboots to apply this policy. Thanks for your help.
Thanks, Brenda
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Darren
Mar-Elia Brenda- Is Fast Logon Optimization enabled (on by default) on the XP machines? Does the situation change after the 2nd or 3rd reboot (i.e. the computer policy is finally delivered on XP)?
From:
[EMAIL PROTECTED] on behalf of Brenda Casey I have applied a startup script (to change a local admin password) to the computer configuration in a GP. I have also configured several user configuration items in this policy. This policy applies successfully to all W2K workstations, but only the User Configurations are applied on a WinXP workstation. Any thoughts on what I am missing? Any and all help is appreciated!
Thanks, Brenda
|
