MECM clinet upgrade issue from 1802 to 1910

Question

Hi Team,

 

My Environment: This is Test Environment 1 Primary site and 1 Remote DP.

Last week we have upgraded it successfully from 1802 to MEMC 1910.

 

On couple of client machines when I try to upgrade the client by manually and through Config Manager.

The update is not happens( No progress in CCMSetup.log)  I am able to get the attached strange Error messages . Even unable to launch ccmtrace on the client machine (Which server 2012).

 

Solutions applied:

1.Reboot the client machine.

2. Try to start ccmsetup service manually but it throws attached error.

3. https://support.threattracksecurity.com/support/solutions/articles/1000071019.

 

CMTrace unable to launch - How To Manage Devices Community Forum - Welcome to the world of Device Management! This is community build by Device Management Admins for Device Management Admins❤️ Ask your questions!! We are here to help you! - MECM clinet upgrade issue from 1802 to 1910 CCM Setup Error - How To Manage Devices Community Forum - Welcome to the world of Device Management! This is community build by Device Management Admins for Device Management Admins❤️ Ask your questions!! We are here to help you! - MECM clinet upgrade issue from 1802 to 1910

solved 0
Satish Thota 4 months 2 Answers 98 views Beginner 0

Answers ( 2 )

  1. You said you upgraded from 1802 to 1910 so i am assuming those clients were active in 1802 and now in-place upgrade to 1910 for SCCM Agent is giving you that problem.

    1. Make sure there are no ccmsetup instances running on the client.
    2. You said you already rebooted the client. Did you see ccmsetup.exe still running in task manager? What’s the current state of the client? it says no client or inactive in console?
    3. How many clients like this?
    4. Did you validate all the components were reinstalled after successful upgrade to 1910? This is known that if you upgrade infrastructure it kicks off the reinstallation of all roles available in your infra.
    5. As Guru asked this above are you able to access admin$ on those clients?
    6. I am assuming all the supporting services related to SCCM Agent are running fine. Like BITS, Distributed Tr Coordinator, WMI service, etc.
    7. Did you try “ccmclean.exe”? Can you try to run ccmclean.exe on one client and try to install the agent after that? — Not Recommended by MS anymore but doesn’t harm anything as the client is already broken in our case.
    8. Did you try deleting the service? If not please do once and let me know how it goes.

    Open an elevated command prompt and type in:

    sc queryex servicename

    Kill the PID

    From the same command prompt type in:

    taskkill /f /pid [PID]

    Best answer
  2. For how many machines you are facing this issue

    looking at screen shot , it appears more system related issue

    Can you try on other test machine, if you are using client push, make sure the ports are opened, Admin$ is accessible , client push account is part of local admin group on the target machine.

Leave an answer

Sorry, you do not have a permission to answer to this question .