Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Production and Development Farms in Separate Domains

  Asked By: Ami    Date: Mar 01    Category: Sharepoint    Views: 1959

There has been a lot of discussion in my organization on whether it is "best
practices" to have your development and production SharePoint Farms in the same
Domain or in separate Domains. I'm leaning towards the same Domain as to
eliminate a possible external issue to the SharePoint, any thoughts?



5 Answers Found

Answer #1    Answered By: Kabeer Karkare     Answered On: Mar 01

Separate, and no trusts between your production  and development. Keeps the
developers honest for the most part.

Answer #2    Answered By: Nathaniel Davis     Answered On: Mar 01

Agreed - though having your pre-production/staging farm (you are using
one - right?) on the production  domain is fine and should take care of
your concerns about issues external  to SharePoint.

Answer #3    Answered By: Zoe Cotton     Answered On: Mar 01

However, we decided to take it a step further and keep production  / Development
/ Test (or pre-production) separate. A little more work on our end ....but
that's the way we like it. We're also leveraging Hyper-V to take care of
Development and Test.

I just built our Hyper-V cluster today ...which will host our SharePoint farm
when it goes live at the end of the month!

Answer #4    Answered By: Alexander Scott     Answered On: Mar 01

It actually depends on what is being developed in the development  farm. If you
are trying to develop content or sites in development and then migrate them to
production you are in for a challenge no matter which way you do it. If you are
actually doing development (ie. web parts, VS workflows, event handlers,
features etc.) then it won't make a lot  of difference whether its the same
domain or a separate  domain. It should however be a completely separate farm.
The only time separate domains  would be an issue  would be if you are hard coding
connection strings in your code and I wouldn't recommend that anyway. Having
separate domains will help you discover those kinds of issues.

Answer #5    Answered By: Benito Carey     Answered On: Mar 01

We have a development  server on Hyper-V, 'pre-prod' on hyper-V and production  on
ESX, all in the same domain. The biggest problem we have are the 'SUPER' users
who think they can make changes to production on the fly because that's the way
SharePoint is designed to work. We don't have a 'real' test domain, but if you
do , and you apply your patches to the DC in the test domain  first, you want a
test SP server there, just to make sure that any changes in test won't effect
production. If patches are applied directly to production, then it doesn't make
a difference.

Didn't find what you were looking for? Find more on Production and Development Farms in Separate Domains Or get search suggestion and latest updates.