I’ve just started a project at a large software vendor that specialises in Virtualisation products. There are trillions of servers both physical and virtual everywhere including numerous test servers with leftover instances of various versions of operating systems. Consequently the test environment resembles a kind of Operating System graveyard. When you are assigned a server for your testing it could have the decaying corpse of almost any OS installed on it.
Learning Curve Approaching
I am a software guy so haven’t had overmuch to do with the installation, configuration and provision of virtual machines or virtualised apps, so its very much a learning curve for me to have to test Virtualisation products. Today I was required to install the necessary software for the test harness, part of which included Powershell 1.0
Powershell duly failed to install, giving the error message ‘Not enough storage is available to process this command.’
Who Ate My Disk ?
Well, my test server had a 34GB disk with only 1GB free. Powershell only requires 1.5MB to install so it didn’t really look like a disk space problem. Nevertheless with 97% utilisation I decided to free up space but oddly, by using ‘Properties’ on the folders could only identify about 16GB of actual usage.
A colleague then showed me that two .sys files were consuming 17GB between them; one belonging to the Page file and one belonging to the Hibernate process. So now I knew where my disk space was going. I freed up about 100 MB by deleting unneeded apps, but still Powershell wouldn’t install ‘Not Enough Storage’. My liver started to ache.
Which Powershell ?
Disk space was not really a good fit for a suspect anyway, so I checked that the Powershell version I was installing was compatible with the Operating System. Checking Control Panel -> System I found I had been bequeathed ‘Windows Server Enterprise Copyright 2007’ which I assumed to be Windows Server 2003 since 2007 < 2008. WRONG WRONG WRONG. ‘Windows Server Enterprise Copyright 2007’ is actually Windows Server 2008 and that already has Powershell integrated into the Operating System. You just need to enable it.
So, making that perfectly clear, you will get the Powershell Installation error ‘Not Enough Storage Is Available To Process This Command’ when you try to install Powershell on Windows Server 2008 because it already comes provisioned as a feature of the Operating System.
But seriously, what a numbskull of an error message: ‘Not Enough Storage’. How about something like ‘Feature already installed but requires enabling’ guys? That would have made my garden path significantly shorter.
Windows Server 2008 can be identified by the line of text ‘Windows Server 2008’ written vertically along the Windows Start menu.