Nunzi0 Posted March 25, 2016 Report post Posted March 25, 2016 I've been building the OSD procedures for our company here and have had decent success getting it to work. I've gotten the ConfigMgr Client to install on several device models, but I've run into a problem with a particular one. I'm not sure why the same client install package, and the same installation account used on multiple machines would not work on this device. Has anyone seen this before? I couldn't find much on the net. Here is the ccmsetup.log errors i am seeing. MSI: Action 11:10:38: CreateFolders. Creating folders ccmsetup 3/25/2016 11:10:38 AM 2332 (0x091C) MSI: Action 11:10:38: CcmDetectFilesInUseRollback. Rolls back files moved by CcmDetectFilesInUse. ccmsetup 3/25/2016 11:10:38 AM 2332 (0x091C) MSI: Action 11:10:38: CcmDetectFilesInUseCommit. Commits action of CcmDetectFileInUse. After this we cannot rollback. ccmsetup 3/25/2016 11:10:38 AM 2332 (0x091C) MSI: Action 11:10:38: InstallFiles. Copying new files ccmsetup 3/25/2016 11:10:38 AM 2332 (0x091C) MSI: Action 11:10:40: RegisterExtensionInfo. Registering extension servers ccmsetup 3/25/2016 11:10:40 AM 2332 (0x091C) MSI: Action 11:10:40: WriteRegistryValues. Writing system registry values ccmsetup 3/25/2016 11:10:40 AM 2332 (0x091C) MSI: Could not write value LastMsgSerialNum to key \SOFTWARE\Microsoft\CCM\StateSystem. Verify that you have sufficient access to that key, or contact your support personnel. ccmsetup 3/25/2016 11:10:40 AM 2332 (0x091C) MSI: Action 11:10:40: Rollback. Rolling back action: ccmsetup 3/25/2016 11:10:40 AM 2332 (0x091C) File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1603 Action: WriteRegistryValues. ErrorMessages: Could not write value LastMsgSerialNum to key \SOFTWARE\Microsoft\CCM\StateSystem. Verify that you have sufficient access to that key, or contact your support personnel. ccmsetup 3/25/2016 11:10:43 AM 2332 (0x091C) Client installation has failed too many times. Ccmsetup will now abort. ccmsetup 3/25/2016 11:10:43 AM 2332 (0x091C) A Fallback Status Point has not been specified. Message with STATEID='313' will not be sent. ccmsetup 3/25/2016 11:10:43 AM 2332 (0x091C) InstallFromManifest failed 0x80070643 ccmsetup 3/25/2016 11:10:43 AM 2332 (0x091C) Deleted file C:\WINDOWS\ccmsetup\ccmsetup.cab.download ccmsetup 3/25/2016 11:10:43 AM 2332 (0x091C) Deleted file C:\WINDOWS\ccmsetup\ccmsetup.xml ccmsetup 3/25/2016 11:10:43 AM 2332 (0x091C) CcmSetup failed with error code 0x80070643 ccmsetup 3/25/2016 11:10:43 AM 2332 (0x091C) Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted March 25, 2016 Report post Posted March 25, 2016 Have a look at the client.msi.log for more details. Quote Share this post Link to post Share on other sites More sharing options...
Nunzi0 Posted March 29, 2016 Report post Posted March 29, 2016 My problem ended up being that i was using a .wim file that i got from the build and capture process. I started using the install.wim from the Windows 7 CD and it worked fine afterwards. I suspect something went awry during the capture Quote Share this post Link to post Share on other sites More sharing options...
ryguy25 Posted June 2, 2016 Report post Posted June 2, 2016 I'm going to add this here because it was one of the top-most search results from Google. I've found that the "LastMsgSerialNum" error usually results from having KB3139923 installed without KB3072630. Removing KB3139923 has resolved the error in all of the cases I've experienced. https://social.technet.microsoft.com/Forums/en-US/7109081b-a82a-46e4-b6fe-f19b7d56e431/problem-with-some-msi-installs-after-kb3139923?forum=w7itproinstall Quote Share this post Link to post Share on other sites More sharing options...
