wow 25 votes ! https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/801937/mvp-dcr-easy-way-to-verify-if-cu1-cu2-cu3-is-installed-on-site-server
On Thu, Oct 10, 2013 at 9:14 PM, s kissel <[email protected]> wrote: > Here's the resolution that worked... It's almost too simple, don't laugh :) > > ccmsetup.exe SMSSITECODE=Auto > PATCH=\\SERVERNAME\FOLDER\configmgr2012ac-sp1-kb2882125-x64.msp > > -S > > ------------------------------ > From: [email protected] > > To: [email protected] > Subject: RE: [mssms] CU3, agent installation issue > Date: Thu, 3 Oct 2013 16:38:13 -0500 > > > That's great if it's a primary. :) However, the Remove Role option is > greyed out for the Management Point on Secondary site servers. I haven't > yet found a way to make it work. > > -S > > ------------------------------ > From: [email protected] > To: [email protected] > Subject: RE: [mssms] CU3, agent installation issue > Date: Thu, 3 Oct 2013 19:56:51 +0000 > > We are seeing this as well in our test environment and have opened a > case with Microsoft. Our initial findings are that this occurs when you > attempt to install the SCCM client on a server which also host the > management point role. We were able to work around the issue (as proof of > concept) by first removing the management point role from a server, then > installing the client and reinstalling the management point role. > > > > I still have another MP that is broken awaiting a fix from Microsoft and > will update the list with the resolution. > > > > Thanks, > > > > -Andrew > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Roland Janus > *Sent:* Wednesday, October 2, 2013 5:06 PM > *To:* [email protected] > *Subject:* RE: [mssms] CU3, agent installation issue > > > > So busted you’re saying and waiting for a fix J > > > > Good to know, tell us when you get something. I’m not opening a case now. > > > > -roland > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *s kissel > *Sent:* Mittwoch, 2. Oktober 2013 22:47 > *To:* [email protected] > *Subject:* RE: [mssms] CU3, agent installation issue > > > > Contacted Premier and there was another case with the same issue opened > before me. For them, the solution was to uninstall CU3, install the client, > then install CU3 Site Server hotfix. Did you get that to work for you by > chance? They will need to build a lab and test for me, which may take some > time. > > > > In my case, Server 2012, CU3 appears in "View Installed Updates", but the > Uninstall icon/link is missing. The icon/link appears for other updates, > however. So I attempted to uninstall it by doing msiexec > /x CM12-SP1CU3-KB2882125-X64-ENU.msi, and while that removed it from the > list of installed updates, the error was still occurring when attempting to > install the client. At this point, it may be easier to rebuild the server, > but it would be nice to get a resolution out in the CM community as there > appears to only be a handful of users experiencing this at the moment. > > > > Scott > ------------------------------ > > From: [email protected] > To: [email protected] > Subject: RE: [mssms] CU3, agent installation issue > Date: Wed, 2 Oct 2013 21:57:31 +0200 > > Yeap, premier is likely what you need now, you can’t go back. > > We haven’t anything in prod (that means CM12 in general J ), so I’ve just > delayed CU3 for now. > > > > -Roland > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *s kissel > *Sent:* Mittwoch, 2. Oktober 2013 15:33 > *To:* [email protected] > *Subject:* RE: [mssms] CU3, agent installation issue > > > > I'm not sure not using CU3 is a solution at this point since it is > deployed across the CAS, three primaries, and multiple secondary sites in > the hierarchy already. Only the CAS and three primaries and one secondary > don't have the client installed at this time, and it was on that single > secondary that I discovered the issue. I generally like to have everything > on the same version as much as possible, so that there is less chance of > database anomalies or corruption later on down the line. :) > > > > Is the best course of action at this point to contact Premier Support, or > are there resources on this mailing list who can submit this is a DCR? > > > > Thanks, > > Scott > ------------------------------ > > From: [email protected] > To: [email protected] > Subject: RE: [mssms] CU3, agent installation issue > Date: Wed, 2 Oct 2013 09:30:58 +0200 > > That is the issue I’ve seen and what Daniel wanted to test to confirm > > You just confirmed the bug J > > > > My only solution was to not use CU3 at all > > > > -R > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *s kissel > *Sent:* Mittwoch, 2. Oktober 2013 05:57 > *To:* [email protected] > *Subject:* RE: [mssms] CU3, agent installation issue > > > > Hi – Sorry to just be jumping in this conversation and pasting the archive > thread below (new subscriber). However, I too am experiencing the issue and > am wondering what solution, if any, there is currently. > > > > Ccmsetup.log: > > [snip] > > File C:\Windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi > installation failed. Error text: ExitCode: 1603 > > Action: CcmRegisterHostingConfiguration. > > ErrorMessages: > > Setup was unable to register the CCM_Service_HostingConfiguration endpoint > > The error code is 80041002 > > > > Pertinent client.msi.log: > > [snip] > > MSI (s) (34:2C) [04:38:19:759]: Executing op: > CustomActionSchedule(Action=CcmRegisterHostingConfiguration,ActionType=3073,Source=BinaryData,Target=CcmRegisterHostingConfiguration,CustomActionData=5.00.7000.0000 > > 5.00.9000.0000 > > ) > > MSI (s) (34:2C) [04:38:19:759]: Creating MSIHANDLE (10971) of type 790536 > for thread 5932 > > MSI (s) (34:30) [04:38:19:775]: Invoking remote custom action. DLL: > C:\Windows\Installer\MSI10AE.tmp, Entrypoint: > CcmRegisterHostingConfiguration > > MSI (s) (34!10) [04:38:19:775]: Creating MSIHANDLE (10972) of type 790531 > for thread 4368 > > MSI (s) (34!10) [04:38:19:775]: Closing MSIHANDLE (10972) of type 790531 > for thread 4368 > > MSI (s) (34!10) [04:38:19:775]: Creating MSIHANDLE (10973) of type 790531 > for thread 4368 > > MSI (s) (34!10) [04:38:19:775]: Creating MSIHANDLE (10974) of type 790531 > for thread 4368 > > MSI (s) (34!10) [04:38:19:775]: Closing MSIHANDLE (10974) of type 790531 > for thread 4368 > > MSI (s) (34!10) [04:38:19:775]: Creating MSIHANDLE (10975) of type 790531 > for thread 4368 > > [4:38:19] Registering Hosting Configuration. > > MSI (s) (34!10) [04:38:19:775]: Closing MSIHANDLE (10975) of type 790531 > for thread 4368 > > [4:38:19] @@ERR:25150 > > MSI (s) (34!10) [04:38:19:775]: Product: Configuration Manager Client -- > Error 25150. Setup was unable to register the > CCM_Service_HostingConfiguration endpoint > > The error code is 80041002 > > MSI (s) (34!10) [04:38:19:775]: Closing MSIHANDLE (10973) of type 790531 > for thread 4368 > > Error 25150. Setup was unable to register the > CCM_Service_HostingConfiguration endpoint > > The error code is 80041002 > > [snip] > > > > > > Restating in summary what is below, as well as my own findings, this > occurs when attempting to install the ConfigMgr 2012 client on a ConfigMgr > 2012 Site Server that already has the CU3 hotfix KB2882125 installed. > However, if the client is installed on the site server before the CU3 Site > Server hotfix is installed, there are no issues. I’ve uninstalled the CU3 > Site Server hotfix and tried to install the client, but the same errors > occur. I’ve also tried to install the CU2 Site Server hotfix, but it > indicated that the CU3 hotfix was already installed (even though it no > longer appears in “View Installed Updates”), presumably because the > uninstall didn’t properly clean out the database. > > > > Any thoughts? > > Thanks! > > > > > > > > > > > > > > > > > > >
