Search the Community

The issue I'm describing is VERY FRUSTRATING. We are decommissioning a proxy server yet our firewall is still showing windows 7 computers hitting the proxy server. Here are the steps that I've taken and what I've looked at on one of the computers in question. DESELECTED "Automatically Detect Settings" Set "Use automatic configuration script" to reference the CORRECT proxy server that is currently in use DESELECTED AND CLEARED the entry under the "Proxy Server" entry for "Use a proxy server for your LAN......" Fields are blank and UNCHECKED Edited the registry and removed ALL references to the proxy server that we DO NOT want to reference (the one being decommissioned) both IP address and the hostname that references the proxy server. Changed the one installed application to point to the correct proxy server. Flushed the DNS cache on the workstation. With ALL these steps taken, can someone tell me where to look or tell me why the machine is still trying to reach out to the proxy that we're decommissioning?

Hi, all. Got a weird one, here... We have two separate organizations that work closely together. Call them A and B. A's remote sites connect to each other in a datacenter. A's servers live in the datacenter. A's offices are connected to that datacenter. B's remote sites connect to each other in a datacenter. B's servers live in the datacenter. B's offices are connected to that datacenter. A's and B's networks converge in shared office space. A's remote sites <--> A's Datacenter <--> A's offices <-->B's offices <--> B's datacenter <--> B's remote sites A's network policies don't allow traffic to/from the remote sites to get past the datacenter for most remote endpoints. E.g. one of A's central office computers has zero connectivity to a domain controller or workstation at remote site A1. A's and B's network policies do allow traffic from as far away as B's datacenter and a couple of B's remote sites to get to A's datacenter. These connectivity restrictions are not routing issues, but something akin to ACLs (I'm a cisco guy, and A's gear isn't cisco, they have some other name for essentially the same sort of thing). We have users in A's offices that require CMRC access to workstations in A's remote sites. We may soon have users in B's offices and/or remote sites that will need CMRC access to workstations in A's remote sites. To this date, Config Manager users have worked around this by simply using RDP to connect to the Config Manager server (which lives in A's datacenter) and launching the remote control from there. The additional remote control users that are or may soon be coming online are not ones that A would like to have logging into their Config Manager server, for various reasons. Changing network configs to pass the traffic is not an option at this time. Anyone know of a way to work around this? I know I could throw up a VM or two in A's datacenter with cmrc on them and have the new remote control users connect to that with RDP and go from there, but I'm wondering if there's a better way. RemoteApp server in A's datacenter? Anyone know of some way to proxy *just* the cmrc traffic for these users' workstations, so that as far as the network gear is concerned, the endpoint lives in A's datacenter, and therefor can talk to A's remote sites? Doesn't seem to be any way to have the cmrc client bounce traffic off the Config Manager server, or anything along those lines.

You can manually turn on Agent Proxy for all agents using PowerShell: get-SCOMagent | where {$_.ProxyingEnabled -match "False"} | Enable-SCOMAgentProxy How about making it the default setting? Any new agent deployed would automatically have proxy enabled? add-pssnapin "Microsoft.EnterpriseManagement.OperationsManager.Client"; new-managementGroupConnection -ConnectionString:scomserver.domain.com; set-location "OperationsManagerMonitoring::"; Set-DefaultSetting -Name HealthService\ProxyingEnabled -Value True Thank you Kevin Holman for posting this. View article... Connect with Mobieus Solutions: Sign Up Now: Infinity Connected™ Full Feature 30 Day Trial Read our Blog: http://blog.mobieus.com Follow on Twitter: http://www.twitter.com/MobieusLLC Visit the Support Center: Infinity Connected™ Support Center Let's Talk Shop: 1-800-691-6774 / support@mobieus.com

I am very limited in my scripting abilities. I need a script that will change proxy settings per location. Example: Setting at this location the IP of the machine is 172.xx.xxx.xx (DHCP) and the proxy setting is 192.xxx.xxx.xxx port xxxx. I travel to another location the IP of the machine is 164.xx.xxx.xx (DHCP) and the proxy setting is 192.xxx.xxx.xxx port xxx. The proxy servers and the ports are different. Right now when someone travels to the offsite location we have to move them from one OU to another in order for the proxy to be set correctly. Could anyone be of help or point in the right direction. Thanks in advance. Kathy