Hacked Mark's Facebook Account
Registered: 1451567414 Posts: 273
Reply with quote
Strange thing happened this wee.
A friend emailed me and said that his Azure VM was in trouble, running out of space. Lots of unnecessary leftovers from updates were in his Side by Side (SxS) in Windows. How, he asked, can I clean it out? My standard advice, and something I do now and then on my servers, is an elevated command prompt and dism /online /cleanup-image /analyzecomponentstore DISM /online /Cleanup-Image /StartComponentCleanup DISM/online /Cleanup-Image /StartComponentCleanup /ResetBase Heck, I even tested it on my on-prem Hyper-V server. My buddy says, "it don't work." So I try it on my shiny new Azure VM that's running my Web server. Sunovagun: Error: 87 The cleanup-image option is unknown. For more information, refer to the help by running DISM.exe /?.
Stunningly, the DISM log contains no information at all on the matter. (Think Claude Rains in Casablanca: "Gambling here? I'm shocked, I tell you.")
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Also weird... So, when you open up a command prompt, your default is your Users folder normally. But open an elevated command prompt, and your default folder is windows\system32. Not in Azure. And here's the super-funky part. My Azure VM is just a 2012R2 VM created on my Hyper-V server a couple of years ago. I have SEEN that thing put me in System32 a million times. But now that it's i Azure, no more. I mean, I expected Integration Services, but not major kernel surgery. They whack the SxS commands... why? Very odd. __________________ May I ask that everyone please populate the first name and last name in your user account profile. Thanks!