This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: TFS/Win2K3 Server Part 3 - It's a Bust
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
I found when I installed Virtual Server and tried to get my TFS-APP application server instance to join my domain, that I missed a couple of steps in the AD Config:
14.
Click OK to acknowledge the warning of having a dynamically assigned IP address for a DNS server.
15.
If you have more than one network interface, select the 10.0.0.0 network interface from the Choose Connection drop-down list, and then click Properties.
16.
Under the This connection uses the following items section, click InternetProtocol(TCP/IP), and then click Properties.
17.
Select Use the following IP address, and then type 10.0.0.2 for the IP address. Press the Tab key twice, and then type 10.0.0.1 for the Default gateway. Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click Close to continue.
So, now I have a useless Win2K3 server with Yukon and Team Foundation Server installed that can't work with anything. I don't know if I can fix up my AD and domain or even if I want to try at this point. This marks three months I have been trying to get this thing to install. For their credit, this is supposed to be an Enterprise product and installed on 3 different physical boxes in a “real” company with static IPs and real Win2K3 System Admins but I don't see how regular guys and gals are going to ever get this thing installed.
Previous Topic
