The RTM version of the Visual Studio 2013 ALM virtual machine and hands-on-labs / demo scripts are now available!
You can also find a consolidated list of all of the ALM virtual machines here: http://aka.ms/ALMVMs.
Thank you Brian for this new release! It's getting unpacked in Europe right now :-)
Quick question. Are these images Azure friendly out-of-the-box. I recall that there was a remote desktop setting that had to be adjusted before uploading to Azure, potentially among some other things as well (I have hardware limitations with running Hyper-V locally, and placing it in Azure helps out a lot). Thanks for putting this together, it is a great resource.
I should start by saying that I don't do any special testing of my images on Azure IaaS before I ship them. With that said, one of the things we started doing in the last couple of iterations was exporting fixed-size disks which is the format IaaS expects you to upload. Beyond that, I would welcome your feedback if the remote desktop option is not working properly for you. I would also strongly encourage you to change the passwords of all accounts in the image prior to uploading them. Since we publish passwords for this VM, somebody with the right IP address for your machine could hack into your VM if you weren't careful. Finally, because IaaS doesn't provide snapshotting capabilities, the hands-on-labs / demo scripts may not be repeatable and the sample data will start to look different over time as the VM moves forward in time. But I understand for you this may be your only option. As a workaround you could create a copy of your VHD in Azure after you upload it and use that to manually roll back to.
I have got these running on Azure IaaS without issues so far. On taking snapshots, this here may be for you: msdn.microsoft.com/.../hh488361.aspx
I am happy to kick-off an asyn copy job of the vanila vhd blob of Brian's most recent VM to a given azure storage account, as long that is okay you, Brian. I am hopeful for this not to be an impropriate proposal.
Tks Brian, amazing work like ever!
If you have trouble with releases getting "stuck" for the Release Management scenario as configured in the VM (doesn't appear to move past first step of deployment to 'Remove Web Site'), try the following workaround to re-activate the server:
1) Log into VM as Brian Keller
2) In RM client app, go to Configure Paths | Servers
3) Open VSALM server
4) Go to Environments tab (middle of screen)
5) Remove links to all 3 environments
6) Click Save
7) Click Deactivate button for VSALM server
8) Re-add links to environments (use Link Existing button)
9) Click Activate button
10) Click Close to return to Configure Paths | Servers
11) Should only take a minute or so until IP Address column for VSALM server shows an updated value (may need to click Refresh a few times)
12) Try release again...
Thanks a lot for making these VMs available to the community!
Hi Norbert: Would you please point me to any help document in hosting these VMs on Windows Azure?
Thanks a lot in advance!
Norbert, sorry for the delay.
Unfortunately per the terms of the license agreement you are not permitted to redistribute the VM.
My understanding is that although you can snapshot the VHD, you won't be able to capture the running state of the VM. Let me know if I am mistaken.
Hey Brian, understood regarding the distribution of the VM. My apologies here on being so bold. And you are absolutely correct about Azure not offering a function to capture the machine running state. :-(
What does work is snapshooting blob used for the VHD. Like this you can at least freeze the data, work with the VM an revert it to the point in time when the snapshot was taken.
No worries at all - bold proposals are how great things happen. :-) Sorry in this case that due to our licensing restrictions it just isn't possible.
When I left the new virtual machine (Visual Studio 2013 ALM RTM) it's turning-off so I just want to know if it's configured to do that or maybe I have an issue?
Did you import the VM per the instructions in the "Working with..." document?
Yes, so you are not configured it to do that...then I will re-import it maybe I missed something.
Not sure if anyone else has had this sort of problem, but when I booted up the 2013 RTM release VM for the first time (within a Hyper-V environment), at first I didnt understand why the VM was shutting down automatically (roughly around 1 hour), and later learnt about the shutdown every hour if OS license has expired. Thats when I had the environment trashed and reloaded from the original download. I noticed straight away that the OS license had expired upon log in, and followed the procedure of setting the date to the current date and time, and then activating for the 180 day trial, which was successful. I then rebooted the VM so to reset the date / time to 09 Jul which was fine, but noticed after a few minutes that the OS became expired again, and reverted back to shutting down after 1 hour.
My question here is: Due to the VM still having access to the internet (after the reboot) would this cause the OS license to become expired again, since date and time had been reverted back to 09 Jul??
I then went down another route in trying to disable the task on boot up for resetting the date and time, then activating windows for 180 days, and while date and time is set at current date and time, to try and use MTM and VS, but they report back that license has expired, which didnt help me much.
Brian K: I see that within the "Working with VM document..", you make mention that the VM should be available for 10 days (if requiring it for longer to then activate), but this is not the case, as the OS is expired as soon as I boot it up from the original extracted compressed fileset?