locked
Client Upgrade from 2007 to 2012 requiring a reboot 100% of the time RRS feed

  • Question

  • As part if an acquisition, I inherited an SCCM 2007 environment, and I want to migrate their clients to my 2012 (soon t be CB) environment. The version of the 2007 environment is really old as they never upgraded it past the first SP (v4.00.6221.1000). What I am seeing is that when I run CCMEXEC from command line to upgrade to a 2012 client, it successfully removes the 2007 client, starts the 2012 client install, but then halts with an error indicating that the service is pending deletion (I am assuming SMS Agent Host).  If I reboot, then the 2012 client installs fine and the it connects to the new environment without issue.  All of the machines that I need to migrate are Windows 7. 

    Does anyone have any experience migrating such an old environment to 2012 or CB, and did they see this behavior as well?  I know when I did my own 2007 to 2012 migration (with Windows 7), the clients never needed a reboot for the upgrade.  The main different being when I did that migration, my 2007 was on the latest version. 

     

    Hold your breath, I'll be right back.

    Friday, April 21, 2017 10:28 PM

All replies

  • Have you reviewed ccmsetup.log for details?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Saturday, April 22, 2017 3:39 AM
  • Yes I have.

    Here is the relevant snippet:

    MSI: Action 17:49:17: InstallServices. Installing new services ccmsetup 4/21/2017 5:49:17 PM 3940 (0x0F64)
    MSI: Service 'SMS Agent Host' (CcmExec) could not be installed.  Verify that you have sufficient privileges to install system services. ccmsetup 4/21/2017 5:49:17 PM 3940 (0x0F64)
    MSI: Action 17:49:17: WriteEnvironmentStrings. Updating environment strings ccmsetup 4/21/2017 5:49:17 PM 3940 (0x0F64)
    MSI: Action 17:49:17: CcmSetServiceConfig. Sets WMI ServiceRootDir and configures CCMEXEC service. ccmsetup 4/21/2017 5:49:17 PM 3940 (0x0F64)
    MSI: Setup was unable to update the service configuration
    The error code is 80070430 ccmsetup 4/21/2017 5:49:17 PM 3940 (0x0F64)
    MSI: Action 17:49:17: Rollback. Rolling back action: ccmsetup 4/21/2017 5:49:17 PM 3940 (0x0F64)
    File C:\windows\ccmsetup\{72875A95-4007-4DAC-88D8-66366F9A5045}\client.msi installation failed. Error text: ExitCode: 1603
    Action: CcmSetServiceConfig.
    ErrorMessages:
    Service 'SMS Agent Host' (CcmExec) could not be installed.  Verify that you have sufficient privileges to install system services.
    Setup was unable to update the service configuration
    The error code is 80070430
     ccmsetup 4/21/2017 5:49:27 PM 3940 (0x0F64)
    Next retry in 120 minute(s)... ccmsetup 4/21/2017 5:49:27 PM 3940 (0x0F64)
    ccmsetup is shutting down ccmsetup 4/21/2017 5:53:00 PM 1576 (0x0628)
    Shutdown has been requested ccmsetup 4/21/2017 5:53:02 PM 3940 (0x0F64)
    InstallFromManifest failed 0x80004004 ccmsetup 4/21/2017 5:53:02 PM 3940 (0x0F64)
    Params to send '5.0.8239.1403 Deployment Error 0x80004004.' ccmsetup 4/21/2017 5:53:02 PM 3940 (0x0F64)
    A Fallback Status Point has not been specified and no client was installed.  Message with STATEID='313' will not be sent. ccmsetup 4/21/2017 5:53:02 PM 3940 (0x0F64)
    Failed to send status 313. Error (87D00215) ccmsetup 4/21/2017 5:53:02 PM 3940 (0x0F64)

    The main error is 80070430, which is The specified service has been marked for deletion.


    Hold your breath, I'll be right back.

    Monday, April 24, 2017 12:32 PM
  • Is there a section before that in the log that shows the service being marked for deletion?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, April 24, 2017 3:05 PM
  • I did not find any entry about marking the service for deletion in ccmsetup.log.  I looked in the Client.MSI_uninstall.log as well, and did not find any reference for marking a service for deletion.  I did, however, find this at the end:

    MSI (s) (0C:10) [11:46:53:031]: Note: 1: 1724
    MSI (s) (0C:10) [11:46:53:031]: Product: Configuration Manager Client -- Removal completed successfully.
    MSI (s) (0C:10) [11:46:53:032]: Windows Installer removed the product. Product Name: Configuration Manager Client. Product Version: 4.00.6221.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Removal success or error status: 0.
    MSI (s) (0C:10) [11:46:53:032]: Value of RebootAction property is
    MSI (s) (0C:10) [11:46:53:032]: Windows Installer requires a system restart. Product Name: Configuration Manager Client. Product Version: 4.00.6221.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Type of System Restart: 2. Reason for Restart: 1.
    MSI (s) (0C:10) [11:46:53:033]: Product: Configuration Manager Client. Restart required. The installation or update for the product required a restart for all changes to take effect.  The restart was deferred to a later time.
    MSI (s) (0C:10) [11:46:53:034]: Deferring clean up of packages/files, if any exist
    MSI (s) (0C:10) [11:46:53:035]: MainEngineThread is returning 3010
    MSI (s) (0C:90) [11:46:53:037]: RESTART MANAGER: Session closed.
    MSI (s) (0C:90) [11:46:53:037]: No System Restore sequence number for this installation.

    So it does seem that the removal is asking for a reboot.  The question I guess is why.  I don't ever recall an SCCM 2007 or an SMS 2.0/2003 client asking for a reboot after it is removed. 


    Hold your breath, I'll be right back.

    Monday, April 24, 2017 4:02 PM
  • "Reason for Restart: 1" should tell us why, but I don't know what restart reason/code 1 means. Based on https://msdn.microsoft.com/en-us/library/windows/desktop/aa373675(v=vs.85).aspx this means permission denied by I suspect that it's a not an actual permissions issue but a file in use issue. You may be able to dig into this more with procmon.

    One off the wall guess is that your AV is getting in the way. Trend Micro does a lot of weird things -- not saying that's you issue, just, as noted, an off the wall guess.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, April 24, 2017 5:01 PM