locked
Upgrading Clients - Reporting fail when they succeeded RRS feed

  • Question

  • I recently upgraded my site to R2 SP2 CU2 and I’m in the process of upgrading my clients.  Right now on a test of 17 systems I have 9 fails and 8 successes, but when you check out the failures they are actually upgraded and reporting correctly to the system.

    When checking out the logs I did the following errors in the logs..

    Execmgr.log

    Request in running or report status found for program Configuration Manager agent silent upgrade package MMG0061E                execmgr              2/4/2016 10:21:53 AM    720 (0x02D0)

    Service stopped while program Configuration Manager agent silent upgrade is running  execmgr              2/4/2016 10:21:53 AM         720 (0x02D0)

    OpenProcess failed for process 3236, error 80070057      execmgr              2/4/2016 10:21:53 AM    720 (0x02D0)

    Can not continue monitoring the program after service restart because the process exited.  Assume failed          execmgr                2/4/2016 10:21:53 AM    720 (0x02D0)

    Looking for MIF file to get program status            execmgr              2/4/2016 10:21:55 AM    720 (0x02D0)

    Raising event:

    [SMS_CodePage(437), SMS_LocaleID(1033)]

    instance of SoftDistProgramUnexpectedRebootEvent

    {

                    AdvertisementId = "MMG20681";

                    ClientID = "GUID:20afe182-c4a4-4624-84a9-40b23fee4588";

                    DateTime = "20160204152155.623000+000";

                    MachineName = "xxxxxx";

                    PackageName = "MMG0061E";

                    ProcessID = 2576;

                    ProgramName = "Configuration Manager agent silent upgrade";

                    SiteCode = "MMG";

                    ThreadID = 720;

    };

                    execmgr              2/4/2016 10:21:55 AM    720 (0x02D0)

    Successfully submitted event to the Status Agent.           execmgr              2/4/2016 10:21:55 AM    720 (0x02D0)

    Raised Program Unexpected Reboot Event for Ad:MMG20681, Package:MMG0061E, Program: Configuration Manager agent silent upgrade      execmgr              2/4/2016 10:21:55 AM    720 (0x02D0)

    Requesting MTC to delete task with id: {23E46FFF-095E-4160-B8D5-F0AE069D51BC}         execmgr              2/4/2016 10:21:55 AM         720 (0x02D0)

    MTC task with id: {23E46FFF-095E-4160-B8D5-F0AE069D51BC} deleted successfully.         execmgr              2/4/2016 10:21:55 AM         720 (0x02D0)

    CServiceWindowEventHandler::Execute - Received SERVICEWINDOWEVENT : START Event         execmgr              2/4/2016 10:00:00 PM       2244 (0x08C4)

    CExecutionRequestManager::OnServiceWindowEvent for START             execmgr              2/4/2016 10:00:00 PM    2244 (0x08C4)

    Auto Install is set to false. Do Nothing.   execmgr              2/4/2016 10:00:00 PM    2244 (0x08C4)

    From the Cas.log

    ===== CacheManager: Cache state initialization completed =====           ContentAccess  2/4/2016 10:21:54 AM    720 (0x02D0)

    GetLogonUserSid failed at GetTokenSids 0x800703f0      ContentAccess  2/4/2016 10:21:55 AM    720 (0x02D0)

    CacheManager: SetCachedContentInUseFlag no change. Value : false    ContentAccess  2/4/2016 10:21:55 AM    720 (0x02D0)

    Releasing content request {8E9E6AA6-9CD7-4EC8-A29B-8D5F3DA3149D}               ContentAccess  2/4/2016 10:21:55 AM    720 (0x02D0)

    CacheManager: All references to cached Content MMG0061E.2 have been removed, content is tombstoned and may be removed during future grooming operations.     ContentAccess  2/4/2016 10:21:55 AM    720 (0x02D0)

    Saved Content ID Mapping MMG0061E.2, C:\Windows\ccmcache\16      ContentAccess  2/4/2016 10:21:55 AM    720 (0x02D0)

    From my research this seems very logical, but it’s going to cause me issues in that I can’t use reporting to tell me how my upgrade of 20k clients is progressing.  Is there some way around this or a change in the package/program settings that will work around this issue?

    Command line in my program is: CCMSETUP.EXE /noservice (more switches with FP, MP and Sitecode)_

    Tuesday, February 9, 2016 7:27 PM

Answers

  • What did you upgrade from?

    Why aren't you using the built-in client auto-upgrade?

    Using a package causing a chicken-egg scenario because the upgrade causes the client agent to stop and be uninstalled. This often causes bad return results. Thus, if using a package to perform the upgrade, don't rely on the result of the program run, instead monitor the client agent version. Better yet, use auto-upgrade.


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

    Tuesday, February 9, 2016 7:42 PM

All replies

  • What did you upgrade from?

    Why aren't you using the built-in client auto-upgrade?

    Using a package causing a chicken-egg scenario because the upgrade causes the client agent to stop and be uninstalled. This often causes bad return results. Thus, if using a package to perform the upgrade, don't rely on the result of the program run, instead monitor the client agent version. Better yet, use auto-upgrade.


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

    Tuesday, February 9, 2016 7:42 PM
  • What did you upgrade from?

    Why aren't you using the built-in client auto-upgrade?

    Using a package causing a chicken-egg scenario because the upgrade causes the client agent to stop and be uninstalled. This often causes bad return results. Thus, if using a package to perform the upgrade, don't rely on the result of the program run, instead monitor the client agent version. Better yet, use auto-upgrade.


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

    From version 5.00.7958.1000

    Why am I not using the built-in, well guess because I didn't know there was one.  

    Currently we don't have auto-updates on, not patching as of yet so maybe that is why I don't know about it.  Basically we'd like to deploy the client to our systems in a controlled manner to select Collections as we go.


    Thanks

    Wednesday, February 10, 2016 1:56 PM