Allow me to maintain drive letter for the temp drive in virtual machine.
Customers have been asking for this every since IAAS went into preview. There are many customer migrating their on premise applications to Azure IAAS. Some of these applications have hard references to D: drive. It is possible to manually move temp drive from D: to another drive letter but it is hard to automate this. A simple fix for this is to move this temp drive to a Z: drive. A better fix may be to allow Azure Portal and PowerShell to select the drive letter for the temp drive during VM creation process.
This will simplify migrations.
The temp disk drive letter will still default to the first drive letter that is available (which is the Windows default behavior); However, if you change the drive letter for the temp disk it will be maintained through VM stop/start/redeploy operations.
Justin King commented
Don't stop at the temp drive, the randomly populated floppy and DVD drives should follow the same logic. In the ARM template we simply need a removableDisk to match the oSDisk and dataDisk categories. Let us pick drive letters, and give us much needed flexibility
@bdcoder2 has opened an azure-powershell issue on this:
the first URL is not working, results in 404
Is there any progress to be reported on this? Since the letter can be changed post-deployment (in an awkward way) it looks like this should not be too difficult to implement as an option during deployment?
Samir FARHAT (MVP) commented
I know it's a limitation, but if you change the ephemeral disk letter after deploying the VM, it will stay this way, even if you deallocate the VM.
We made this part of the VM deployments on Azure, change the ephemeral disk letter to another letter
Rob Plank commented
What about moving the page file to a mount point on the C drive so no drive letters are used.
Walter Myers commented
I agree 100%, having encountered this on a SharePoint project. This may be a small thing, but is a pain for our customers that want to change their disk configuration.