This is a continuation of my post Using Blogs to Drive Product Direction and is an experiment in getting customer feedback on product decisions through blogs. I’d like you to keep two things in mind. 1) Anything I post here is likely to change before we ship. 2) Please provide some context for your feedback, the reason why you, your clients, and/or your company feel a change is important.
In this post, we will deal with Visual Studio Team System Operating System Requirements. I am assuming you are already familiar with Visual Studio Team System, if not start here.
Client Side
Visual Studio Team System Clients will run on the following operating systems and require the following service packs:
Windows 2000 (SP4 or greater)
Windows XP Home (SP2 or greater)
Windows XP Professional (SP2 or greater)
Windows Server 2003 (RTM or greater)
Windows Server 2003 64-bit (SP1 or greater) (WOW mode only)
Windows XP 64 bit (Second Release, no code name yet) (WOW mode only)
VSTS clients will not be support on Windows 95, Windows NT 4.0, Windows 98, Windows 98 SE, or Windows ME.
Server Side
The Team Foundation Server may only be installed on a Windows 2003 operating system. The following table outlines our POR for operating system support. Note: Dates on future releases of Win2k3 are outside my project’s immediate control, more information can be found here.
| Versions\Flavors | WebEdition | Standard | Enterprise | Datacenter | 64-bit Std | 64-bit Ent | 64-bit DC |
| Current RTM | no | yes | Yes | yes | n/a | yes | yes |
| SP1 (March 2005) | no | yes | Yes | yes | n/a | n/a | n/a |
| 64-bit (1st half 2005) | n/a | n/a | n/a | n/a | Yes | yes | yes |
| R2 (end of 2005) | no | yes | Yes | yes | Yes | yes | yes |
This posting is provided "AS IS" with no warranties, and confers no rights.