Tuesday, October 1, 2013

What’s Next for MMS

Excerpts from Brad Anderson's comments on the future of MMS:

http://blogs.technet.com/b/in_the_cloud/archive/2013/10/01/what-s-next-for-mms.aspx


Starting this year we are merging MMS with TechEd.

objective is simple: Provide attendees a better opportunity for knowledge gathering and technical growth. By drawing together a larger community to this combined event, every attendee will have a dramatically wider range of experts and luminaries (both from the industry and within Microsoft) to learn from and engage.

TechEd 2014 will be your single best source for the latest news, trends, resources and deep technical education. Also, the System Center team is already preparing to teach the deep 300- and 400-level content you’ve come to expect at MMS. There will also be expanded Early Bird pricing options, dedicated Management Meet & Geek opportunities, dedicated Management Instructor-Led Labs and Hands-on Labs, structured and unstructured networking opportunities tuned to the Management community and broader communities, and other unique MMS experiences.

The next step is to mark your calendars for May 12-15, 2014 for TechEd 2014 in Houston, Texas. Registration opens on November 5, 2013, and if you register by December 31, 2013, you’ll get the aforementioned early bird pricing.
If you haven’t already, take a minute to sign up for the TechEd Insiders newsletter to get the latest TechEd information.
I’m looking forward to seeing everyone in Houston.

Friday, September 27, 2013

Local cached package 'C:\WINDOWS\Installer\xxxxxx.msi' is missing.

Evern seen the error the in the client.msi.log file that a local package is missing when trying to install the client.  This could be because a dependence has been removed or badly corrupted, but what file is missing?

Looking in the client.msi.log you might see this line:

MSI (s) (D0:F4) [17:45:28:546]: Warning: Local cached package 'C:\WINDOWS\Installer\6363739.msi' is missing.

Ccmsetup.log:

An MP does not exist on this machine.
Failed with error code 0x8007064c.
Installing version 4.00.6487.2700 of the client with product code {CAE5379F-5C3D-4D0D-AA57-DC1134125BA5}
MSI PROPERTIES are  .....................
IsFileMicrosoftTrusted Verified file 'C:\Windows\ccmsetup\{18173E5E-0E79-4447-A4DC-2CEEAA239871}\client.msi' is MS signed.
Installation failed with error code 1612

Client.msi.log

MSI (s) (84:78) [14:53:58:896]: ******* RunEngine:
           ******* Product: C:\Windows\ccmsetup\{18173E5E-0E79-4447-A4DC-2CEEAA239871}\client.msi
           ******* Action:
           ******* CommandLine: **********

MSI (s) (84:78) [14:53:58:927]: Warning: Local cached package 'C:\Windows\Installer\723298.msi' is missing.
MSI (s) (84:78) [14:53:58:927]: SOURCEMGMT: Looking for sourcelist for product {CAE5379F-5C3D-4D0D-AA57-DC1134125BA5}
MSI (s) (84:78) [14:53:58:942]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (84:78) [14:53:58:942]: SOURCEMGMT: Failed to resolve source



Solution:
these all point to a possible missing file.  Indeed if you look in the installer folder you will be missing a file.  The problem is that these files are random and you can't just look up the file on another machine. 

So how do you find what you need?

for ConfigMgr 2007 you can look here
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\F9735EACD3C5D0D4AA75CD114321B55A

But the best thing is to stop at the Products node

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\

and search the entire node to look up the XXXx.msi you are missing to see which product is missing.  From there you can then go to another machine and copy the XXXX.msi to the broken machine.

You must look at the InstalledProperties\LocalPackage to see the file name
C:\Windows\Installer\129227f.msi

From here you can either rename the msi file or modify the key to match the file name.

Next restart your install, is this a supported method.  No but it should work.  With all unsupported process, please use at your own risk and test in a lab enviroment first.





Wednesday, August 7, 2013

Native 2007 client fails to start. "Failed to load CryptInfo."

Scenerio:  Secondary client will not start it appears to be damagaed.  check the CCMExec.log and you see the following.


CCMExec.Log

Entering Certificate Maintenance
Client SSL is enabled. The current state is 0x31.
IsCertficateExportable(0x7ee388) skipping check on an MP.
Failed to load CryptInfo.
CCMValidateEncryptionCert failed. (0x80070002)
Creating Encryption Certificate...
Successfully created certifcate

Updating MP mirror key
Phase 0 initialization failed (0x80070002).
Service initialization failed (0x80070002).
Shutting down CCMEXEC...
UninitCommandExec failed (0x800401fb).
Waiting up to 2 seconds for active tasks to complete...
Finished shutting down CCMEXEC.


If you compare this to a working native machine you will see the security data is missing.

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\CCM\Security

Here you can then export the SingingCertificate and other security information such as "AllowRootCAHashcode".

Export fom a working client and import it to the new client, making sure they are the same. 
Win 7 to Win7 or Secondary to Secondary.

Restart the Service.  It should all now work...