I can't say no.. but I don't know what would. I can open the registry editor, run a gpupdate /force and the changes are not there.
So, I base it off that fact alone. This is just proxy/autoconfig settings too.. nothing fancy at all. From: Sam Cayze [mailto:[email protected]] Sent: Wednesday, December 31, 2008 4:13 PM To: NT System Admin Issues Subject: RE: gpupdate/GPO I would think IE settings wouldn't need a reboot... Many programs can try to adjust IE settings. AV programs, Spybot, Desktop Search, etc... could anything be overwriting the settings you are trying to adjust? From: Jason Gauthier [mailto:[email protected]] Sent: Wednesday, December 31, 2008 2:29 PM To: NT System Admin Issues Subject: RE: gpupdate/GPO When you say "the NIC has not come active" are you talking about the PC/drivers, etc.. or are you talking about the time it might take the switch to bring the link up? I know some switches take longer than XP to boot due to STP. If it's the latter, it can be mitigated with switch config changes. If it's the prior, then you're right. I will need to employ some other trickiness.. which I should have ready to go anyway. Thanks! From: [email protected] [mailto:[email protected]] Sent: Wednesday, December 31, 2008 3:26 PM To: NT System Admin Issues Subject: RE: gpupdate/GPO Not all GPO's are applied in a background refresh. Many do require a reboot to take effect, Offline files being one for example. The GPO would not apply in the initial reboot because the computer does not get the update since the NIC has not come active yet. Then it pulls down the update and it requires a 2nd reboot to actually make the changes happen. We pretty much now only require a reboot to make all our GPO's take effect when enabling the Wait on Network option. From: Jason Gauthier [mailto:[email protected]] Sent: Wednesday, December 31, 2008 3:19 PM To: NT System Admin Issues Subject: RE: gpupdate/GPO Wouldn't that group policy not get applied under that theory though? Or any new GP at all? Furthermore, the GPO should be reset every 15 minutes, however some settings are not actually applied until the force+reboot. From: [email protected] [mailto:[email protected]] Sent: Wednesday, December 31, 2008 3:16 PM To: NT System Admin Issues Subject: RE: gpupdate/GPO On occasion it takes 2 reboot cycles for GPO's to be applied. You can help mitigate that by making the computer wait for network on startup under the computer section, System/Group Policy ADM's. Some computers do not get the NIC started before GP settings would be applied hence requiring a 2nd reboot to get the gp settings to take effect. From: Jason Gauthier [mailto:[email protected]] Sent: Wednesday, December 31, 2008 3:07 PM To: NT System Admin Issues Subject: gpupdate/GPO All, I have one, or many, GPOs that are not apparently being applied on workstations. Through some testing, I have specifically found that IE settings are not really taking effect. That is, until, I manually run a gpupdate /force, and the reboot or logoff. Obviously, this is not really desired. Does anyone know why this would be happening, and how I can solve it? A GPO should be applied appropriately, without me mandating a forced update and reboot. Thanks, Jason ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
