VSTS 2010 CTP, Hyper-V, and January 1st, 2009

For those of you folks who have converted the VSTS 2010 CTP ( see Grant’s post ) to take advantage of the performance improvements in hyper-v, here’s a manual way to get around the fact that VSTS will expire Jan. 1st 2009. ( If you’re using the CTP with VPC, see Brian’s post for a similar workaround ).

1) The first thing to do is snapshot your current image ( if you followed Grant’s steps, that should have been the last thing you did while you converted your image to hyper-v ). You’ll need this to rollback as needed.

2) Next, you need to turn off the Time Synchronization feature that the Integration Services of Hyper-v do for you. Do this by going into your Hyper-V Manager, right click on your VSTS 2010 CTP image, select “Settings…”. This will prevent the guest image from automatically synching its system time with the host machine while the guest is running. If you don’t do this first, steps 4+ won’t work at all.


3) Now start the CTP image.

4)  In the bottom right hand corner of the CTP image, click on the time display in the status bar, which brings up the clock settings. Click “Change date and time settings…”


5) In the “Date and Time” dialog, click on the “Internet Time” tab, click the “Change settings…” button, which gives you the dialog below. Uncheck the “Synchronize with an Internet time server” check box. Hit OK.


6) Now back in the “Date and Time” dialog, change the date to something like October 20th, 2008 by first clicking on “Change date and time…” button. You can’t go back too far, otherwise you’ll get the dreaded “Eval has expired” dialog. Hit OK on that dialog, and then OK again to close the “Date and Time” dialog.

7) Now fire up VSTS, you’re good to go!

Since this is such a manual process, I would recommend going through the steps above, and then Pause then Save the image each time you want to regain the memory being used up by the image.

Hope that helps,


Comments (9)

  1. If you’ve been using the Team System 2010 Community Tech Preview VPC , you’ve probably noticed that the

  2. If you are running the Visual Studio 2010 and .NET Framework 4.0 CTP under Virtual PC or Hyper-V, you

  3. Charles Sterling on Team Test Special Interest group December 15th in Redmond Shai Raiten on How To:…

  4. Erik Cox says:

    About the Date and Time..when you say that we should not set it too far back…well what’s the <a href="http://www.notionsolutions.com">maximum</a&gt; that we can go back without getting Eval expired message!?

    Thanks in advance!

  5. I’m actually not sure. My first try was to just push it back a year and I experience the time out. Didn’t experiment anymore than that.

  6. Morgan says:

    I’ve tried this several times attempting to get the CTP image to work, and it doesn’t seem that the Host Time Synchronization setting actually has any effect.  Everything works correctly with VPC, but in Hyper-V the time is always synchronized.

  7. Mezzrow says:

    I’ve heard there’s a way of setting the time in Hyper-V, much like the time_bytes nodes in Virtual Server, however, I have not yet found it.

    Anyone know of a configuration means of stopping host time synchronization on guest reboot?

  8. To all the customs trying our CTP – the timebomp is activated and you probably getting the following

  9. The VSTS 2010 CTP uses quite a bit of horsepower, and had been really sluggish under Virtual PC or Virtual