SCCM Client Not Finding Correct MP (Doesn't Even Exist!)

[scottpowers82]

Hello,

 

Ok, I am trying to figure out a somewhat wierd issue that I've been having for sometime now that I think I finally have a handle on as to what is causing my issues. I'll try to be breif...

 

Several months ago, we moved from SCCM 2012 to current branch (on 1710 now). During that move, I was also asked to migrate the server from one host to another with a new server name (old one was just "SCCM", new one is "WCSSCCMS01") along with a new IP address. I did a fresh install of Windows Server 2016 along with the CB of SCCM and migrated the data over from the old server using the Migration tool built into SCCM (under the Administration tab on left in the console). Since then though, I've seemed to have "odd" issues that I never could explain. Task sequences that worked flawlessly before now had issues sometimes finishing or taking much much longer than before. Some deployments of software would never seem to get to machines. Things of that nature. I had noticed that many of my migrated objects stilll had the Package ID of the old server as well and, thinking that may have been part of the problem, I proceeded to recreate my task sequnces entirely on the new server thinking it would help. However, I have noticed that, while a machine will finish imaging and boot to Windows, the client seems to be corrupt. In fact, when I go into the Control Panel, the Configuration Manager isn't even listed! My fix has been to reinstall the client from the SCCM console and force to uninstall/install the client with the option to specify the site checked. This does some to work 85-90% of the time.

 

Now for the strange part...I had to image a fresh machine today out of the box and realizd that I hadn't given it the right name during imaging and, upon booting into Windows, I proceeded to change the name. Since the config client hadn't installed and I just renamed it, I knew it wouldn't show up in SCCM just yet to push the client to it, I thought I'd just go into the SCCM folder on teh server and install the client from there by double-clicking the ccmsetup.exe file as I had done before in my old setup. It went ahead and installed "some" of the client. It only listed 6 tabs at the top (General, Components, Actions, Site, Cache, and Network). Additonally, the only actions available were "Machine Policy Retreival" and "User Policy Reteival." Odd I know...but the oddest part was that, under the General tab, it shows my assigned management point as being my old server! It even shows the site code of the old setup as well. That old server doesn't even exist anymore and has been deleted from AD completly at this point as well as it's DNS entries.

 

My guess is that when it goes to install the client during a task sequence, it is somehow trying to pull MP of the old server and that is likely causing my wierd issues with sequnces not finishing and software not depoying correctly as I likely have several corrup installs out there. Anyone out there have a clue on how I can fix this? I don't even know where to start looking on this one...

 

Thanks in advance for anyone who can assist...

Edited April 11, 2018 by scottpowers82

[clareq]

When we did the same upgrade I was advised to build the new SCCM instance with a different site code, and configured the computer GPO Admin templates, configuration manager, configuration manager client.

 

I also have a setting in the Task Sequence - Set up Windows and Configuration Manager, under Installation Properties, which sets the MP to the correct server - have you changed this?

[scottpowers82]

Clareq,

 

Thanks for the reply! Actaully, I think we may have found the possible issue as I also posted this over on Windows Noob. One thing I didn't think of checking was my System Management container within ADSI on the server. When I setup the new server, I had forgotten to give the new server full permissions over the container. In fact, the container still had references to my old server, which likely explains why some of my clients were defaulting to that instead. I just now deleted all of the old references to the old server in the container and gave my new server full permissions over it, so we'll see if that does the trick.

[scottpowers82]

So, it looks like my clients that are pointing to the old system won't automatically pick up the new one from wha tI have seen so far on a machine I am testing. In fact, when I got into "Site" tab on my test machine that didn't even have an entry for the "currently assigned site code", I tried hitting the Find Site button and it didn't seem to find my site automatically. Once I manually typed in my site code though and applied the settings, the correct information populated in the General tab. At least now it is pointing to the right site code and I can get access to the machine from within the config console. Does anyone know of a script or something I could use that would re-assign my client computers to insure they are pointing to the correct site code?

[clareq]

Look at the GPO setting I mentioned earlier - works a treat here.

[scottpowers82]

Clareq,

 

You had mentioned that you used admin templates...is this something you downloaded to add into your GPO similar to how you can download Office ADMX files for templates? Or was it a setting already available in a normal GPO? I pretty well versed in GPOs, but never have used them to configure SCCM. I normally push out my client from the console using the automatic site wide push, so I typically don't use GPO to push out...or is that how you push out your client and you attach those extra properties to it?

Edited April 12, 2018 by scottpowers82

[clareq]

If you go to your Configuration manager install directory on the server and go to tools, you'll find the adm files you need

[scottpowers82]

Thanks Clareq! Found them under the tools folder in the install path. Just put in the GPO, so we'll see how that works out. Thank again!