Hope this doesn't happen soon enough to effect MMS! Well, I hope it doesn't happen at all.
From latimesblogs:
Shares of Las Vegas Sands Corp., owner of the Venetian hotel and casino, are plummeting today after the company warned that it could face bankruptcy.
The firm, controlled by billionaire Sheldon Adelson, is deep in debt and strapped for new capital, at a time when casino traffic is dwindling as consumers slash their spending.
Clickthrough for more.
And here.
In our Citrix environment we've long redirected the Local System drive letters from "C: and D:" to "M: and N:". Other than some basic user education this rarely proves to be an issue.
Then came the SMS client, and the dreaded "MSI: Invalid Drive: C:\" error. Then "Installation failed with error code 1603" in the ccmsetup.log. While it doesn't happen on every Citrix machine, it happens often enough to be a huge pain.
Generally a quick ccmclean.exe /removehistory takes care of the issue. However there have been die-hard cases where nothing seems to work.
Finally I stumbled across the KB Article 893652. While not specific to my issue, it does detail an SMS client repair that utilizes the client.msi that is already present in the local CCMSetup folder. My assumption has long been that the client gets pushed to the Citrix server before the drives get renamed, thus making it unable to do an auto-repair, eventually causing client failure. Repairing the client with the source where we want it to be (M:) seemed like a good idea.
I modified the command string to fit my environment:
MSIEXEC.exe /I M:\WINDOWS\system32\ccmsetup\{2FBB7E06-7665-442B-98E3-189CB634C5CC}\client.msi
and after a successful execution the client was in working order.
Note that this points to the default CCMSETUP folder, which in my case is on M: on our Citrix servers. The GUID may be different depending on your version of client. Note also I left off the /qn to watch it run.
I've only tried this on one machine (so far, I'm sure it will rear it's ugly head again). YMMV.