speckytecky Posted October 30, 2013 Posted October 30, 2013 We have a Windows Server 2008 Standard 32 bit as DC with a Windows Server 2008 R2 64 bit which also has a DC role. Recently setting up imaged refurbished Windows 7 32 bit clients with IE 9 and also some out of the box Fujitsus running Windows 7 64 bit with IE 10 preinstalled I'm finding that the SWGfL proxy isn't getting picked up by default. Checking the settings on the clients I can see that the proxy box is getting ticked but the proxy details aren't getting populated. Port 80 is being populated when it should be 8080. I'm pretty sure that the correct proxy and port details are set. Where should I be looking to correct this.
computer_expert Posted October 30, 2013 Posted October 30, 2013 (edited) For IE10 you will need a Win8 or Server 2012 box with the RSAT bits installed to manage the GPPs (I don't think the IE maintenance settings work with IE10). I think there is a way of editing the GPP xml files for server 2008r2/IE10 if you don't have W8/2012, but haven't tested it myself. Additionally i have seen the following relating to GPP & IE10: IE 10 Group Policy Help needed - I think I've found a bug - Spiceworks In group policy preferences make sure that the settings you need have a green line underneath them (press F6 to enable a setting, and F7 to disable) Edited October 30, 2013 by computer_expert 1
speckytecky Posted October 31, 2013 Author Posted October 31, 2013 Star posting thanks very much @ computer_expert I have the IE 10 blocker set in Group Policy Settings currently and need to put it's sister for IE11 on in the very near future methinks. Removing IE10 from those new clients and replacing it with IE9 is going to be a priority for next time I'm at work then as is looking for that green line in settings for IE9.
SovietRussia Posted October 31, 2013 Posted October 31, 2013 IEM (Internet Explorer Maintenance) was removed for IE10 and IE11, you must now use GPP to manage these settings. We got it to work in GPP by editing a few policy INI files and adding in version numbers etc. But we had to do this, on a Server 2012 machine. @computer_expert is 100% correct, you must use Win8/Server 2012 to edit the appropriate XML files, as they do not show for 08R2/Win7 2
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now