I am pleased to announce the availability of a new virtual machine which demonstrates the integration of Team Foundation Server 2012 with Project Server 2013. This integration scenario was first introduced with Team Foundation Server 2010 and Project Server 2010, but this virtual machine was updated to showcase this integration scenario using the latest software releases.
This integration enables the Project Management Office (PMO) to see a consolidated view of the progress and resource availability across all software development projects in Team Foundation Server. Software teams using Team Foundation Server can choose to manage their projects using a formal process or an agile process and flow their status and schedule updates into Project Server and Project Managers can preview changes as they flow in, track the work at a high-level and provide live updates to their stakeholders.
This virtual machine is pre-configured with this integration along with sample data and several walkthroughs (which can either be used as self-paced hands-on-labs, or demo scripts to present these capabilities to others). The following instructions should make it easier for you to batch download all of the files required for this release.
Downloading the virtual machine and associated files: I suggest using a download manager for these files since they are very large. My download manager of choice is Free Download Manager. You can use your own favorite download manager, but you may need to adapt the instructions below as appropriate.
Once you have downloaded the release, extract it to a directory by running the EXE. The document “Working with the Project Server 2012 and Team Foundation Server 2012 Integration Virtual Machine.docx” provides more details about how to load this virtual machine within Hyper-V, and how to activate the operating system to get a full 180 days of usage from this virtual machine. After 180 days from the time you first boot the virtual machine it will expire. If you need additional time you can re-extract a fresh copy of the virtual machine, or restore to a Hyper-V snapshot if you took one at a time prior to booting it up for the first time.
After you have successfully setup this virtual machine within your Hyper-V environment you can begin using the walkthroughs to learn more about the scenarios enabled by this integration. Those walkthroughs are also included in the list of files above as Word documents, and are numbered 1-4. It is recommended, though not required, that you complete these labs in the order they are numbered. You should also consider using Hyper-V snapshots prior to following the steps in a walkthrough so that you can roll back to an earlier snapshot if you would like to complete a walkthrough multiple times, or if you make a mistake. DemoMates If you want to learn about this integration but don’t have time to download the virtual machine, you can use the following DemoMates. DemoMates are useful for being able to “click through” the scenarios above without needing to download and run the virtual machine. Online DemoMates:
Offline DemoMates: (installed locally on your computer)
I hope you enjoy this content. If you have suggestions for how to improve this virtual machine and set of demos / hands-on-labs please let me know.
We are using VMware and so have converted the disk from a VHD -> VMDK an successfully imported into VMware. I have activated windows after the import, however Office is asking to be activated and the synchronisation between Project Server and TFS doesn't seem to be firing. Is this due to Office needing activation?
In your previous blog (blogs.msdn.com/.../team-foundation-server-2012-and-project-server-2013-integration-virtual-machine-and-hands-on-labs-demo-scripts.aspx) you have said to import the VM and not to attach VHD. But I am not sure this is an option for us on VMware.
Any tips or help would be much appreciated.
Sorry bad link there, I was referring to the discussion in this previous blog (blogs.msdn.com/.../getting-started-with-the-team-foundation-server-2010-and-project-server-2010-integration-virtual-machine.aspx)
Andrew, This is a side effect of moving your VM to VMWare. The process you went through changes the hardware identifiers in the VM and triggers the piracy detection logic in Office. Hyper-V is the only format supported for this VM.