I'm Robert Marshall, director and principle consultant at SMSMarshall Ltd, who's specialism is in the Microsoft System Center 2012 Configuration Manager product and all of its dependent products, covering all aspects from Architecture, Implementation, Migration to Break-Fix.
I've been in front of computers for over 30 years now, with my roots in programming 8 bit computers, I've taken an often exciting journey which has led to becoming an expert in an enterprise product. I consider my career as starting 17 years ago, when I began my first serious role as a deployment engineer. I've seen 8 bit through to 64 bit, the rise and refinement of the interface we take for granted now, the rise of the Internet from land-line based modem access for the few, to the powerful broadband connections we have today for the masses, I saw mobile phones come into existence, and I've seen Microsoft evolve from more than a handful of employees to the company it is now, while pretty much tinkering with every OS they have released, as well as seeing an industry that has evolved around those humble beginnings to become what we have today. I'm a keen technical puzzle solver, I love to solve gnarly problems around my area of specialism. And, I love to share when I have time. I hope you enjoy the blog.
Seen an interesting issue where the CCMSETUP parameters incorrectly specify MP as SMSMP, resulting in failure and exotic errors appearing in the CLIENT.MSI and CCMSETUP logs:
Just need to fire up CLIENT.MSI in SMSTRACE, find Return value 3 and you'll possibly see the following:
WARNING: The path passed for the TRK file is empty.SMSMP cannot be specified without SMSSITECODE@@ERR:25001MSI (s) (1C!94) [10:10:37:046]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstancesThe error code is 80004005
Error 25001. Setup failed due to unexpected circumstancesThe error code is 80004005MSI (s) (1C:0C) [10:10:37:046]: Machine policy value 'DisableRollback' is 0MSI (s) (1C:0C) [10:10:37:093]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 10:10:37: SmsSetClientConfigInit. Return value 3.MSI (s) (1C:0C) [10:10:37:093]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (1C:0C) [10:10:37:093]: No System Restore sequence number for this installation.MSI (s) (1C:0C) [10:10:37:093]: Unlocking ServerAction ended 10:10:37: INSTALL. Return value 3.
At the tail-end of the CLIENT.MSI log file:
MSI (s) (1C:0C) [10:10:37:328]: Note: 1: 1708 MSI (s) (1C:0C) [10:10:37:328]: Product: Configuration Manager Client -- Installation operation failed.
MSI (s) (1C:0C) [10:10:37:390]: Cleaning up uninstalled install packages, if any existMSI (s) (1C:0C) [10:10:37:390]: MainEngineThread is returning 1603MSI (s) (1C:54) [10:10:37:500]: Destroying RemoteAPI object.MSI (s) (1C:D0) [10:10:37:500]: Custom Action Manager thread ending.=== Logging stopped: 20-08-2008 10:10:37 ===MSI (c) (1C:20) [10:10:37:500]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1MSI (c) (1C:20) [10:10:37:500]: MainEngineThread is returning 1603=== Verbose logging stopped: 20-08-2008 10:10:37 ===
CCMSETUP log file drops out at the following section: SmsSetClientConfigInit
MSI: Action 13:55:32: SmsSetClientConfigInit. Setting SMS configuration ccmsetupMSI: Setup failed due to unexpected circumstancesThe error code is 80004005 ccmsetupInstallation failed with error code 1603 ccmsetup
It's a classic mistake, easily overlooked.
CCMSETUP should be saying "Command line parameters for CCMSETUP incorrectly specified, unknown parameter SMSMP identified", but it doesn't as you can see above