G
Guest
Have used GPO OK for a while with W2K and Xp SP1 wkstns, but do not pretend
to be an expert. New XP Sp2 wkstns do not pick up IE Maintenance settings.
Server is W2K SP4.
Have upgraded GPO templates with Xp SP2 versions on XP SP2 admin wkstn.
If a user only logs in to XP SP2 then IE does not set proxy, or title or
home page url etc. If they log in to XP Sp1 first then it is set. We have
2000 student users, so getting each to login in this way is not an option.
(login script and autodetect are not preferred options for setting proxy for
various reasons)
Have also noticed that user setting of active desktop .jpg wallpaper is not
retained (setting shows in control panel, but picture is not shown), but is
reapplied if user selects to customise desktop (but does not need to change
anything). Do not know if this is connected (given active desktop is web
based).
Suspect answer may lie in 600+ new IE settings of SP2 GPO templates - but
where? Our expertise and time does not extend to trial and error.
This is now driving me mad. Perhaps we have missed something obvious.
Any contructive suggestions welcome.
TIA
to be an expert. New XP Sp2 wkstns do not pick up IE Maintenance settings.
Server is W2K SP4.
Have upgraded GPO templates with Xp SP2 versions on XP SP2 admin wkstn.
If a user only logs in to XP SP2 then IE does not set proxy, or title or
home page url etc. If they log in to XP Sp1 first then it is set. We have
2000 student users, so getting each to login in this way is not an option.
(login script and autodetect are not preferred options for setting proxy for
various reasons)
Have also noticed that user setting of active desktop .jpg wallpaper is not
retained (setting shows in control panel, but picture is not shown), but is
reapplied if user selects to customise desktop (but does not need to change
anything). Do not know if this is connected (given active desktop is web
based).
Suspect answer may lie in 600+ new IE settings of SP2 GPO templates - but
where? Our expertise and time does not extend to trial and error.
This is now driving me mad. Perhaps we have missed something obvious.
Any contructive suggestions welcome.
TIA