Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

OPEN SCCM 1606, client failing to refresh to get the new site code

  • Thread starter Thread starter Jessie
  • Start date Start date
  • Replies Replies 1
  • Views Views 8K

Jessie

New Member
Messages
1
Reaction score
0
Points
1
I am having challenges with installing the client agent on most of the machines. on some of the machines the client is installed but its failing to get the site code.

We initially had SCCM 2012, when we tried to upgrade we encountered some errors so we decided to do a fresh install of SCCM 1606. everything installed fine but when I decided to install the client on the machines, tried using both client push and group policy I only have 84 out of 844 discovered machines registered in the console.
When I try to check on some machines, I can see the client has been installed, when I open the agent on the site code its showing blank.
upload_2017-10-3_11-44-2.png

When I check the logs I am seeing the following error message showing:


<![LOG[RegTask: Failed to refresh site code. Error: 0x8000ffff]LOG]!><time="11:29:15.580-120" date="10-03-2017" component="ClientIDManagerStartup" context="" type="2" thread="3148" file="regtask.cpp:218">

How do i ensure that the machines with old client get a fresh installation of the client or refreshes it to get the new side code and registers so that they can be managed.
 
This is a bit old, but I wanted somewhere to post the results of a couple days of research:
Main problem: Client would not connect with MP, it had problems finding MP, getting certificate etc...

* DNS returned error 10060 in LocationsService.log - Issue was that we had UDP but not TCP 53 enabled to our DNS servers, DNS resolution to find SRV worked after this

* Consistently saw RegTask: Failed to refresh MP. Error: 0x8000ffff
Tried so many things: Certs, with/without PKI.
Ultimately, I believe that I had some issues with my MP installation and potentially IIS. I was able to get the specific client working by installing the MP role on another server. This led me to the belief that I had an issue with my primary MP. So I uninstalled/reinstalled.

Hope this helps someone.
 

Forum statistics

Threads
7,144
Messages
27,895
Members
18,190
Latest member
escdarck

Trending content

Back
Top