• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2980
  • Last Modified:

SCCM client trying to connect to wrong site

Hi,

We have a new secondary site and for some reason the clients are attempting to connect to the Primary site management point despite there being a management point on the secondary.

The site boundaries are defined by AD site. The subnet that the client resides on and the subnet that the secondary site server resides in are the only ones in the AD site. I have checked for overlapping boundaries.

For some reason, the SCCM client is attempting to connect to the Primary site management point which it is unable to do so due to a firewall restriction.

Can anyone advise why this could be happening?
0
aideb
Asked:
aideb
1 Solution
 
TarekIsmailCommented:
Hi ,

if a proxy management point is installed at a secondary site, clients located within the secondary site's boundaries send information such as software distribution package content location requests, inventory data, discovery data, and status messages to the proxy management point.

The proxy management point forwards the client information to the secondary site server's inboxes and the client data is compressed and sent to the primary site as part of normal site to site communication.

When a proxy management point is not installed at a secondary site, all client information is sent uncompressed directly to the default management point at the primary site.

Proxy management points do not directly respond to client policy requests. All client policy requests are sent to the default management point at the primary site. However, proxy management points do cache policy bodies downloaded by clients. If the policy body for a requested client policy has already been downloaded by a secondary site client, the policy body will be sent from the proxy management point to the secondary site client. Otherwise, the client will download the policy body from the default management point at the primary site and the proxy management point will cache it for future client policy body requests.

so it is a must to allow the firewall between your clients and default management point at the primary site.

good Luck !
Tarek Ismail
0
 
aidebAuthor Commented:
Thanks Tarek.

I found article
http://technet.microsoft.com/en-us/library/bb693472.aspx

which seemed to say the same.

Thanks for confirming!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now