Partager via

Virtual Server/PC Rocks VS2005 Team Foundation!

  • Article

Ok, well I've been consumed recently with getting an installation of VS2005 Team System working without having to go out and buy a couple of extra servers. And I got it working!

It wasn't exactly falling-off-a-log-easy so I thought I'd share my methods, mwah-ha-ha!

I've got a system with plenty of memory (2Gb) and so I created 3 virtual PC environments, 2 Win2K3 and 1 WinXP-SP2. Let's call them VSTF-DB (128Mb) , VSTF-App (128Mb) and VSTF-Client (512Mb) respectively.

I set them up on a private "internal" network and used a "virtual CD" tool to mount the Beta1-CTP "Refresh" DVD image on my "host" machine. This is because VPC can't handle virtual CD's bigger than 2.2gb (for some reason I don't get ... but that IS rather larger than a CD but smaller than most DVDs).

Then I did the following:

  1. Installed the Data tier on VSTF-DB (this means installing IIS 6 and the latest Yukon (SQL Server 2005) beta).
  2. Note: I decided (since I was on a "private" network) just to use static IP addresses which made DNS issues easier. So I called the VSTF-DB machine 10.1.1.1, the VSTF-App machine 10.1.1.2 and the VSTF-Client machine 10.1.1.3
  3. Then, using DCPROMO I made VSTF-DB a domain controller and installed DNS so that I could create "mysample.com" private domain.
  4. Next, I created a domain account (this is why I created my own domain controller!) MYSAMPLE\TFSIdentity and made it a member of the domain Administrators group
  5. Now, on to the application tier (VSTF-App) this is a 6 step process
  6. First, I joined this machine to the MYSAMPLE domain and put it into the DNS.
  7. Then, install IIS 6 but do not install Front Page extentions
  8. Then installation of Windows SharePoint Services (not this is not SharePoint portal!)
  9. After that Application Directory Application Mode (aka ADAM)
  10. And then .Net Framework 2.0 Beta
  11. and finally... install the VSTF Application server software (whew!)
  12. Next, I joined the VSTF-Client machine to the MYSAMPLE domain
  13. And then installed the Whidbey Beta 1 CTP (aka VS2005) client code on VSTF-Client
  14. And very important... follow the instructions on how to connect to VSTF-App (it's not yet intuitive!)

And now.... drumroll please.... I was able to create my first Project workspace!!!

And then I backed up all the VPCs !!!!!

NB: I was also then able to use this trio of images to work with Virtual Server 2005!

Enjoy... your mileage may vary, please let me know if you succeed and/or fail so I can update these instructions if necessary.

Comments

  • Anonymous
    September 09, 2004
    Yep, I managed to install them on 1Gb machine :-) with the same memory configuration.
  • Anonymous
    September 09, 2004
    Did you not have any problems with the gssutil /g commands?

    Did you do anything special in ADAM to get the permissions to work correctly?
  • Anonymous
    September 10, 2004
    No, I did not have to do anything (beyond following the installation directions) to get the ADAM stuff working.
  • Anonymous
    September 21, 2004
    Which Virtual CD tool did you use to get the DVD into an ISO format so it is available to Virtual Server.
  • Anonymous
    September 21, 2004
    I got this from MSDN Subscriber downloads. "Virtual CD-ROM Control Panel for
    Windows XP"

    The trick is to mount it on the virtual CD on your host machine and then (after installing VM additions) share this "folder" so that it's available to the VM as a virtual drive.
  • Anonymous
    September 27, 2004
    Error "The is no unique domain in the registry" when i run gsstuil /g

    ：（
  • Anonymous
    November 28, 2004
    I've got Team System Working. Now what?
  • Anonymous
    June 13, 2008
    PingBack from http://blogs.southworks.net/mwoloski/2004/09/20/visual-studio-team-system-vsts-important-resources-up-to-20049/