RTM Version of Visual Studio 2013 ALM Virtual Machine

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: https://aka.ms/ALMVMs.

Enjoy!

Comments

• Anonymous
  November 26, 2013
  Thank you Brian for this new release! It's getting unpacked in Europe right now :-)

• Anonymous
  November 26, 2013
  The comment has been removed

• Anonymous
  November 27, 2013
  The comment has been removed

• Anonymous
  November 29, 2013
  Thanks Brian

• Anonymous
  November 30, 2013
  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.

• Anonymous
  December 01, 2013
  Tks Brian, amazing work like ever!

• Anonymous
  December 03, 2013
  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...

• Anonymous
  December 04, 2013
  Hi Brian, 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!

• Anonymous
  December 06, 2013
  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.

• Anonymous
  December 09, 2013
  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.

• Anonymous
  December 09, 2013
  Norbert, 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.

• Anonymous
  December 10, 2013
  Hi Brian, 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? Thanks

• Anonymous
  December 10, 2013
  M.Radawan, Did you import the VM per the instructions in the "Working with..." document?

• Anonymous
  December 11, 2013
  Yes, so you are not configured it to do that...then I will re-import it maybe I missed something. Thanks Brian

• Anonymous
  December 11, 2013
  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? Thanks Wayne

• Anonymous
  December 12, 2013
  Wayne, Please ensure that you are following the instructions in the "Working with..." document for importing this VM. The most likely cause for what you are seeing is that you did not IMPORT the VM, but instead that you created a new virtual machine and pointed to the existing VHD file. If you are still having this problem after following these instructions on a fresh extract of the VM please let me know.

• Anonymous
  January 05, 2014
  I am also having issues trying to Activate the OS. I followed the instruction in the "Working with ..." document and tried to activate but I am getting the error "The activation server reported that new time based activation not available". Date is set to today and the machine has internet connectivity so not sure what's wrong. BR Andrea

• Anonymous
  January 06, 2014
  Hi all, It turns out that the activation problems people are hitting are due to something going on with the service at Microsoft responsible for unlocking activations. I'm really sorry for everybody who hit this but we only recently confirmed this is a problem. We're still trying to find a solution to the activation problem, although keep in mind that you do NOT need to activate to use this VM. I just wrote a blog post which details this along with the implications: blogs.msdn.com/.../errors-activating-the-alm-virtual-machines.aspx

• Anonymous
  January 08, 2014
  Thanks Brian! Only it looks like you forgot to add the following links on (http://aka.ms/vs13almvm): download.microsoft.com/.../VisualStudio2013.RTM.ALM.part18.rar download.microsoft.com/.../VisualStudio2013.RTM.ALM.part19.rar download.microsoft.com/.../VisualStudio2013.RTM.ALM.part20.rar download.microsoft.com/.../VisualStudio2013.RTM.ALM.part21.rar download.microsoft.com/.../VisualStudio2013.RTM.ALM.part22.rar    

• Anonymous
  January 09, 2014
  biiipy2, Sorry about that, you caught me mid-upgrade. :-) The blog post has been updated now with all of the files in the fileset along with a set of 20 additional hands-on-labs / demo scripts which were upgraded from 2010/2012.