Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: make additions as per KB-64 plus additional formatting updates

...

The requirements are different depending on whether you are using a 32-bit or a 64-bit application for Enterprise Tester.

Installing 32-bit TFS Client

For 32-bit TFS Client, more information on the installation process can be found here: http://blogs.msdn.com/b/jimlamb/archive/2010/04/06/installing-just-the-server-components-of-tfs-2010.aspxFor 64-bit TFS Client, please refer to “Installing 64-bit TFS Client” below

If using a 32 bit version of TFS you will need to ensure that the Enterprise Tester Application Pool has the Advanced Setting Enable 32-Bit Applications set to True. This setting can be found in the General section of the Advanced Settings.

Additional Configuration

Once you have installed the TFS Client, ensure that the user defined in the Enterprise Tester Application Pool (by default this is Network Service) has full access to the Team Foundation Cache Folder.

Default Path: "C:\ProgramData\Microsoft\Team Foundation\3.0\Cache"

Note: On some servers you will need to assign permissions to both the 3.0 and the Cache folders.

To do this right click on the Cache folder, view properties, and then edit the permissions.

Give the defined user (as discussed above) full access to the Cache folder.

Restart IIS.

Installing 64-bit TFS Client

If you are using a 64bit-only application for Enterprise Tester, you will find that the 32bit TFS client installs do not work. To get around this you must install some component from the TFS 2010 server installation DVD/ISO image.

The installation process for 63-bit TFS Client is outlined below.

Checking if this applies to you

This guide only applies if you have your application pool configured for 64-bit only. If not, you should be OK installing the 32-bit TFS client (or if the machine already has Visual Studio 2010 installed, for example, you may find the files are already there).

...

Expand the application pools node, and select the application pool being used by enterprise tester - it's Enterprise Tester. It is normally called "Default App Pool".

Once selected, to the right click "Advanced Settings".

If "Enable 32-bit applications" is  is set to "False" - , then you are using a 64-bit application pool.

...

TFS 2010 server is distributed either as an ISO image (via an msdn or technet subscription) or on DVD.

If you have an ISO file - , you can either install a tool such as Virtual Clone Drive, to allow mounting the ISO image as a virtual drive, or alternatively if you are hosting Enterprise Tester in a virtual machine, your virtualization administrator should be able to mount the ISO image on the virtual machine for you.

In this case we are going to mount an ISO image using Virtual Clone Drive, and the image file is named "en_visual_studio_team_foundation_server_2010_x86_x64_dvd_559671.iso" (obtained from the Microsoft site, requires a technet/msdn subscription)

...

Then navigate to the folder "TFS-x64" and locate the executable file "setup.exe", and double-click to execute it.

...

On the third step, select "Team Foundation Components" - this . This will select everything, then un-tick "Team Foundation Server", "Team Foundation Server Proxy" and "Team Foundation Build Service" - this . This will just install the necessary components to connect a TFS server , without actually installing the TFS server.

Continue to the next step to start the installation.

Additional Configuration

Once installation has completed, you can then create TFS connections on your Enterprise Tester server.you have installed the TFS Client, ensure that the user defined in the Enterprise Tester Application Pool (by default this is Network Service) has full access to the Team Foundation Cache Folder.

Default Path: "C:\ProgramData\Microsoft\Team Foundation\3.0\Cache"

Note: On some servers you will need to assign permissions to both the 3.0 and the Cache folders.

To do this right click on the "Cache" folder, view properties, and then edit the permissions.

Give the defined user (as discussed above) full access to the "Cache" folder.

Restart IIS