I'm creating a minimalist Win2008 server VM in Azure so I can run cmdlets apparently not available via the Node.js CLI tools for Mac and Linux.
I log into the system as the only user (administrator) via RDP and proceed to install additional software (Azure Powershell and cmdlets, Azure Python SDK, Chrome and WinSCP). I switch from IE to Chrome, create some bookmarks, and download and import
my Azure subscription data.
Finally, I execute sysprep (OOBE + Generalize + shutdown) so I can capture a customized VM image.
I go back to the Preview Portal, verify the VM has stopped, and run Capture on the VM, saving the image as "AzureSDK" to my storage account.
Later, I instantiate a new VM (with a new name) from my AzureSDK image.
Once I've logged in again as administrator over RDP, I note the system no longer has Chrome installed, has reset my desktop contents (probably due to the OOBE setting), but still has WinSCP and some (but not all) of the Azure SDK pieces.
Is this because I'm doing the installs as Administrator, which sysprep/OOBE then undoes? And the WinSCP sticks because the install defaults to be for all users and not just Administrator?
Moved byJiang YunThursday, September 27, 2012 1:46 PM (From:Windows Azure Development)