jfarmer Posted April 1, 2016 Report post Posted April 1, 2016 (edited) Hi there, Just upgraded our site to 1602 and all our current PCs and Servers have picked up the new Client. Just spun up a new server a couple of days ago and have just realised the client hasn't installed on it. I tried pushing the client from the SCCM Console, but just getting this error "Product: Configuration Manager Client -- Error 1406. Could not write value LastMsgSerialNum to key \SOFTWARE\Microsoft\CCM\StateSystem. System error . Verify that you have sufficient access to that key, or contact your support personnel." Thanks in advance for any help, James Edited December 1, 2016 by jfarmer Quote Share this post Link to post Share on other sites More sharing options...
Apexes Posted April 1, 2016 Report post Posted April 1, 2016 Does your client push account in SCCM have access to this server to install the client? Quote Share this post Link to post Share on other sites More sharing options...
jfarmer Posted April 4, 2016 Report post Posted April 4, 2016 (edited) Hi Apexes, *How do I find that out?* I don't see why it wouldn't, haven't had this issue before when spinning up new servers and I haven't had to do anything to configure them to get the client to install. *Edit* - Yes it does, they're in a local admin group on the Server. Edited April 4, 2016 by jfarmer Quote Share this post Link to post Share on other sites More sharing options...
brianlaudi Posted April 20, 2016 Report post Posted April 20, 2016 (edited) Hi, I have the same issue but after upgrading my SCCM envoirement from SCCM 2012 R2 SP1 to CU3. Did you manage to find a solution please? Edited April 20, 2016 by brianlaudi Quote Share this post Link to post Share on other sites More sharing options...
Tefty Posted April 25, 2016 Report post Posted April 25, 2016 Chiming in to say I also have this issue, what more annoying is its happening during my PC task sequences and therefore I end up with a useless machines due to no apps being installed. Quote Share this post Link to post Share on other sites More sharing options...
Tefty Posted April 25, 2016 Report post Posted April 25, 2016 Here's the fix:- https://social.technet.microsoft.com/Forums/windows/en-US/7109081b-a82a-46e4-b6fe-f19b7d56e431/problem-with-some-msi-installs-after-kb3139923?forum=w7itproinstall Its not SCCM itself thats the issue or the client its a bl**dy Windows patch. I had KB3139923 serviced into my Windows images as I do with all new updates but it breaks the Windows installer process unless KB3072630 is installed with it. In short - I downloaded the update, inserted into my images and deployed to all live machines. Quote Share this post Link to post Share on other sites More sharing options...
