Jump to content


Sign in to follow this  
bighoppa

Unable to setup Client Push on secondary site

Recommended Posts

I've got an instance of ConfigMgr 1703 running to replace our old 2012R2 site, and we have six offices in other locations we need secondary sites for so we don't have a lot of MP and DP traffic across the WAN. I successfully provisioned the first secondary site this morning, but now I am trying to set the Client Push installation settings and when attempting to specify the service account, I get the attached error message. Once this pops up it crashes my ConfigMgr console, and it happens on my local workstation, my primary site server or the remote MP.

Any ideas where to start troubleshooting this issue? I used the same account on the Primary site server for client push installation and it worked fine. Push works within the local site, but obviously fails at the remote site.

 

accounterror.JPG

Share this post


Link to post
Share on other sites

Possibly unrelated, but 4022 wasn't enabled in the local firewall of the secondary site server. Database replication also had not completed, so maybe that was a cause. Regardless, this morning the secondary site is allowing me to add credentials to push the client, and machines are getting client installs properly.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...