Skip to main content

Configuring Proxy Using GPO in Microsoft Server 2008

Configuring Machine as the Default Proxy Using GPO in Windows® Server 2008

To configure the Proxy Settings on all client machines to use GFI WebMonitor as a proxy server through Windows® Server 2008 GPO:
1. In command prompt, key in mmc.exe and press Enter.
2. In the Console Root window, navigate to File > Add/Remove Snap-in… to open the Add or Remove Snap-ins window.
Screenshot 14: Add/Remove Snap-ins window
3. Select Group Policy Management from the Available snap-ins list, and click Add.
4. Click OK.
Screenshot 15: Console Root domain window
5. Expand Group Policy Management > Forest > Domains and <domain>, then select the organizational unit where you wish to apply the group policy.
NOTE
To apply the group policy to all domain computers , select the domain node directly.
6. Right-click Default Domain Policy and click Edit to open the Group Policy Management Editor.
Screenshot 16: GPO Editor window
7. Expand User Configuration > Policies > Windows Settings > Internet Explorer Maintenance > Connection and double-click Proxy Settings to open the Proxy Settings dialog.
Screenshot 17: Proxy Settings dialog
8. Check Enable proxy settings checkbox.
9. Uncheck Use the same proxy server for all addresses checkbox.
10. In the HTTP and FTP text boxes key in the proxy server IP address and the port used (Default 8080).
11. Click OK to apply changes
12. Close Proxy Settings dialog.
13. Close Group Policy Management Editor dialog and save the management console.
IMPORTANT
When using Active Directory, the administrator can disable the Internet connection settings tab from the client machines. For more information refer to Disabling Internet Connection Settings On Client Machines.

Comments

Popular posts from this blog

Duplicate IP Address has been Detected Rule

A duplicate IP address has been detected on the network Rule Knowledgebase Summary This rule generates an alert when Windows® detects that he local machine’s IP address is in conflict with one or more identical IP addresses on the network. Until the IP address conflict is resolved, remote clients and applications may have difficulty accessing resources on any of the effected computers. Additionally, the local computer may not be able to access network resources. Related Events This rule generates an alert whenever the following events occur and are recorded in the System Event Log: The system detected an address conflict for IP address %2 with the system having network hardware address %3. The local interface has been disabled. Source: TCPIP; Event ID: 4198; The system detected an address conflict for IP address %2 with the system having network hardware address %3. The local interface has been disabled. Source: TCP...

Schedule Automatic backup config in Cisco Nexus

Schedule Automatic backup config in Cisco Nexus Nexus-Sw1(config)#feature scheduler   //Enable scheduler service in Nexus Nexus-Sw1(config)#scheduler job name backup-daily      // Job Name Nexus-Sw1(config)#scheduler aaa-authentication username abcd password abcd@123     // AAA - Authentication for Job created above (If AAA configured) Nexus-Sw1(config)#scheduler job name backup-daily copy running-config tftp://192.168.1.23/$(SWITCHNAME)-cfg.$(TIMESTAMP)         //IP of TFTP SERVER , file will saved with switch name and timestamp exit Nexus-Sw1(config)#scheduler schedule name backup-daily   // Setup Schedule to run for the JOB Nexus-Sw1(config-schedule)# time ?   daily    Specify a daily schedule   monthly  Specify a monthly schedule   start    Specify a future time schedule   weekly   Specify a weekly schedule...

VMware CPU and Memory Reservations: Fixing Insufficient resources to satisfy configured failover level for HA

Source Knowledge From :-  http://geekswing.com/geek/vmware-cpu-and-ram-reservations-fixing-insufficient-resources-to-satisfy-configured-failover-level-for-ha/ VMware CPU and Memory Reservations: Fixing Insufficient resources to satisfy configured failover level for HA This post comes from a few days of poring over manuals as well as some technical support. This is a good one. The error came from trying to power on a VM in our VMware cluster and we would get these errors: “Insufficient resources to satisfy configured failover level for HA” And this alert on our cluster “Insufficient resources to satisfy HA failover level on cluster vmCluster in vmTST” Our way of thinking was we had to power one off to power another one on. But that didn’t work. Here we is the actual solution. (p.s. Great VMware HA education for me on this one!) PROBLEM SOURCE: VMware HA is turned on and you are violating constraints VMware HA is turned on, and you have i...