SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to get an idea of infrastructure layouts that others are using. In our current 2007 environment we have 3 farms:

Dev Model Prod

All VMs 2500 users between 100 and 150GB total content less than 5 devs at this time, hoping to attrack more use from other development groups

We are migrating to 2010 in the next few months and I am reassessing. I have spoken with some admins who have suggested individual VMs for each developer as needed. The devs test on their VMs and promote to Model and on to Production.

Do any of you use this method? If not, what is the general setup in your organization?

NTLM vs Kerberos? Also, looking for any opinions on ntlm vs kerberos for LAN only environment.

share|improve this question

I agree with Alex that your dev process is commonly used and is fine.

A lot of people come across the double hop problem when using BI within SharePoint. If your organization is likely to use BI at some stage then I would suggest doing Kerberos up front - it shouldn't require much extra work and if you aren't using SharePoint for BI then why not? - It's great! ;-)

The extra work required to get Kerberos working should be minimal and for the small amount of extra effort I would recommend installing Kerberos by default.

share|improve this answer

Dev process seems to be fine. Many people do it that way. You might want to have a look at the new TFS<->SharePoint integration and its automations feaures.

NTLM vs. Kerberos: You are fine with NTML as long you dont come to the "double hopp" problem. You can read here about it:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.