SOLVED Unable to connect SCCM 2012 R2 SP1 from other Site

[sirjeee]

Scenario:
SCCM 2012 R2 SP1 (I have only Primary Site)
Helpdesk users successfully connect SCCM admin 2012 R2 SP1 console but same user is login from different AD site then he gets the error “Configuration Manager cannot connect to the site”.
I have multiple AD sites where users connect and working fine on other applications only SCCM admin 2012 R2 SP1 console produce error.
Please specify steps in detail becasue, I am new for SCCM 2012 R2 SP1

 

[Youssef Saad]

Do you try to access with RDP or from a remote console admin CfgMgr ?

 

[Prajwal Desai]

It's basically a firewall related issue. The issue might be firewall related with outbound traffic inspection. The network team has to check this.

 

[sirjeee]

Dear Sir,
I applied SCCM client push from SCCM 2012 R2 SP1, but after doing this bandwidth is choked, please specify how i removed this applied client installation and what is the best method / practice of applying client push installation.

 

[Prajwal Desai]

Did you manage to fix the SCCM console issue ?.

 

[sirjeee]

Yes, only changing the IP it is fixed, after reverting the IP issue is same no sccm console connect, I also check your attached blog link, and found DNS entry in the DNS and there is no impact found on edit host file.

right now i want to remove remaining client push installation client from SCCM to avoid the bandwidth choking and required a design document to eliminate this problem in future.

 

[Youssef Saad]

If you have multiple sites, I suggest to you to put on each AD site a distribution point.

 

[sirjeee]

Well youssef Thanks. Please share design document if you have, and how i removed remaining sccm clients from queue.

 

[Youssef Saad]

Perform the following bulleted steps on the Site server that you want the Client Push to cease on:

• Stop the SMS_EXECUTIVE
• Stop the SMS_SITE_COMPONENT_MANAGER
• Go to <CONFIGMGR PATH>\INBOXES\CCR.BOX and delete all CCR files
• Go to <CONFIGMGR PATH>\INBOXES\CCR.BOX\INPROC and delete all CCR files
• Go to <CONFIGMGR PATH>\INBOXES\CCRRETRY.BOX and delete all CCR files
• Start the SMS_SITE_COMPONENT_MANAGER (wait a few moments, it'll start the SMS_EXECUTIVE automagically)
• Monitor the CCM.LOG in <CONFIGMGR PATH>\LOGS and you'll see the activity has died off.

And do not forget to disable the client's Push installation option in the hierarchy settings.