PENDING Migrating current config manager client to new site

[CodyB]

Hello,

I've got a new Configuration Manager v. 2006 and trying to push the client from the console to Window servers 2012R2's and 2016's. I've got the Client Push configured with the options set. Note: the current SCCM environment version is 2012.


I'm able to successfully push the clients a good portion to our Windows Servers. But, some Servers, the clients are not installing. Here's what I'm seeing when trying to push the client to a single Windows Server client, ccm.log.
Again, the client push fails to about 20 machines. Help is greatly appreciated.

 

[Garth]

That install log shows that the client install fine. So what exactly is the problem.

 

[CodyB]

Yes, But, looking at the Config Mgr console, it shows client does not have the client. Logging into the Windows Server (client) and looking at the Control Panel, Configuration Manager Properties, the general tab still shows the current 2012 Config Mgr and it's site code. It does not have the new 2006 Config Mgr and the new site code. Besides ccm.log on the Config Mgr server log, are there any other log that I can check and see what maybe causing the issue? Installing the client manually also seems to be installing but not showing on the CM console.

 

[Garth]

Have you looked at the local client log files to see what is happening?

 

[CodyB]

Looking at the \\server.fqdn\admin$ share for ccmsetup.log, I see a lot of REDs. I also noticed that it's using port 80. I thought I've setup it up to use https or http. Shouldn't it try use https/443?

Any thoughts on those failed error codes?

 

[Garth]

The log is telling you that you have a networking/firewall error then it tries to get to the MP/DP

 

[Prajwal Desai]

Logging into the Windows Server (client) and looking at the Control Panel, Configuration Manager Properties, the general tab still shows the current 2012 Config Mgr and it's site code.

Just a test - Try changing the site code to new one and see if the client updates. I know during the client push you are uninstalling the old agent and installing new one but that's not working. Also on one of these server, uninstall the agent and manually install it. Let me know if it installs fine or throws same errors.

 

[CodyB]

Yes! That's the conclusion I'm coming up with. But, using telnet / test-netconnection for ports seems to check out. SCCM

 

[CodyB]

Hi,

Sorry for the delay on response, been busy. It's on going and on hold. It turns out that the network contractor may have misconfigured connection to re remote office switch. Waiting on contractor to finish working/troubleshooting the issue. I'll will try client deployment then.

 

[CodyB]

Thanks for the assist, Garth & Prajwal Desai. Once the contractor upgrade/swapped a faulty switch, I reconfigured the firewall to allow ports 135, 445 and 443 on the subnets I able to successfully deploy the clients to the Windows Servers. I'm good to go with client deployment.

Thanks again.