1

For TFS 2010 application tier. data tier and build server, What should be the best practice for IP address. Shall we give static IP available or we should use DHCP forthis.

4

Use DHCP and a proper named.

That will make the network you place TFS on flexible, dynamic and future-friendly

  • Do you mean "configure DHCP to allocate a static address"? Thus allowing central management of IPs (and backup) while avoiding IP changes. – Richard Jun 16 '10 at 7:23
  • 1
    Giving both of you an upvote because you're both correct - it really comes down to what your organisation is already doing. – Mark Henderson Jun 17 '10 at 3:04
  • I second Farseeker. We used to do all static on the server; but we now only use static on infrastructure servers, and DHCP on everything else. But it really depends on what you're used to. – Chris S Jun 17 '10 at 3:16
  • Thanks all. In our infrastructure we also use static for all infrastructure server and DHCP for others. Since we have done a test installation of TFS 2010 on three virtual server (one each for data, app and build tier) which uses DHCP for IP. We are having issues in TFS 2010 sharepoint Dashboard ..we tried to fix it by using second method give here davidrbrown.com/tag/rsinvalidreportparameter . This gives a error which says SQL is not able to communicate...That's why i thought is it because of IP by DHCP. Any suggestion is most welcome. – Kabir Rao Jun 17 '10 at 6:56
3

Personally I use static ip addresses on all "fixed" hosts\nodes such as servers, printers, etc.

  • Giving both of you an upvote because you're both correct - it really comes down to what your organisation is already doing. – Mark Henderson Jun 17 '10 at 3:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.