GPO for screensaver not working for XP clients on SBS 2008
|
Prev: Reinstalling CompanyWeb Intranet Site on SBS 2003
Next: I cannot copy files from sharepoint explorer view to local disk, W
From: Leythos on 11 May 2010 07:13 I've migrated most of my clients to SBS 08 and am finding that the one GPO setting for Screen Saver and Screen Saver password settings are not migrating to the XP client workstations - everything is updated, all SP, and it worked when they were on SBS 03...... Anyone else seen this? -- You can't trust your best friends, your five senses, only the little voice inside you that most civilians don't even hear -- Listen to that. Trust yourself. spam999free(a)rrohio.com (remove 999 for proper email address)
From: Jim Behning SBS MVP on 11 May 2010 09:02 Silly question by me. Is client side extension installed onthe XP boxes? I have no clue if that policy is in CSE on a 2008 GP. CSE bites me every time for drive mapping. On Tue, 11 May 2010 07:13:39 -0400, Leythos <spam999free(a)rrohio.com> wrote: >I've migrated most of my clients to SBS 08 and am finding that the one >GPO setting for Screen Saver and Screen Saver password settings are not >migrating to the XP client workstations - everything is updated, all SP, >and it worked when they were on SBS 03...... > >Anyone else seen this? See what SBS support is working on http://blogs.technet.com/sbs/default.aspx Check your SBS with the SBS Best Practices Analyzer http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx
From: Cliff Galiher - MVP on 11 May 2010 09:45 One of the more common misconceptions I've seen about group policy is how the client and server interact. The client is responsible for reading group policies from a domain controller (via the sysvol share) and enforces those policies as part of the windows security model. In other words, you could take a Win7 client, install the RSAT tools, and manage Win7 specific group policy settings on an old Win2000 domain controller. In other words, the upgrade to 2008 is not the cause of this issue (directly), but is a sign that something during the upgrade wasn't done properly. Could be a permissions issue on sysvol (as alluded to, sysvol is how clients get group policies) or could be a WMI filter, OU link, or security filter that is causing the problem. In rare cases, group policy files themselves get corrupt. Deleting the group policy and recreating it will resolve the issue in these instances. -Cliff "Leythos" <spam999free(a)rrohio.com> wrote in message news:MPG.265305e9c54b61c798a347(a)us.news.astraweb.com... > I've migrated most of my clients to SBS 08 and am finding that the one > GPO setting for Screen Saver and Screen Saver password settings are not > migrating to the XP client workstations - everything is updated, all SP, > and it worked when they were on SBS 03...... > > Anyone else seen this? > > > -- > You can't trust your best friends, your five senses, only the little > voice inside you that most civilians don't even hear -- Listen to that. > Trust yourself. > spam999free(a)rrohio.com (remove 999 for proper email address)
From: chill earl on 12 May 2010 11:21 you also can try other options in this corresponding group policy in order to isolate that if just this option cannot be applied or all settings cannot be deployed in your XP clients. PS: I dont think there is any CSE error in the client so far because the clients have been installed during the join domain phase. "Cliff Galiher - MVP" wrote: > One of the more common misconceptions I've seen about group policy is how > the client and server interact. The client is responsible for reading group > policies from a domain controller (via the sysvol share) and enforces those > policies as part of the windows security model. > > In other words, you could take a Win7 client, install the RSAT tools, and > manage Win7 specific group policy settings on an old Win2000 domain > controller. > > In other words, the upgrade to 2008 is not the cause of this issue > (directly), but is a sign that something during the upgrade wasn't done > properly. Could be a permissions issue on sysvol (as alluded to, sysvol is > how clients get group policies) or could be a WMI filter, OU link, or > security filter that is causing the problem. > > In rare cases, group policy files themselves get corrupt. Deleting the > group policy and recreating it will resolve the issue in these instances. > > -Cliff > > > "Leythos" <spam999free(a)rrohio.com> wrote in message > news:MPG.265305e9c54b61c798a347(a)us.news.astraweb.com... > > I've migrated most of my clients to SBS 08 and am finding that the one > > GPO setting for Screen Saver and Screen Saver password settings are not > > migrating to the XP client workstations - everything is updated, all SP, > > and it worked when they were on SBS 03...... > > > > Anyone else seen this? > > > > > > -- > > You can't trust your best friends, your five senses, only the little > > voice inside you that most civilians don't even hear -- Listen to that. > > Trust yourself. > > spam999free(a)rrohio.com (remove 999 for proper email address) > > . >
From: Leythos on 12 May 2010 15:48
In article <f8liu5tnge514t18oskqg0krqahi8d0e5v(a)4ax.com>, jimbehning(a)doesthisblockpork.mindspring.com says... > Silly question by me. Is client side extension installed onthe XP > boxes? I have no clue if that policy is in CSE on a 2008 GP. CSE bites > me every time for drive mapping. > Yep, but drive mapping, native in SBS 08, doesn't work for the XP clients even with it - I have to resort to a logon.bat file or a separate GPO for mapping drives, the wizard doesn't cut it. -- You can't trust your best friends, your five senses, only the little voice inside you that most civilians don't even hear -- Listen to that. Trust yourself. spam999free(a)rrohio.com (remove 999 for proper email address) |