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

We are under process of clone on QA environments to new environments. machines and urls will changes. How we can configure these changes in central admin level in new environment?

Please advice me.

share|improve this question

migrated from Dec 17 '11 at 16:40

This question came from our site for professional and enthusiast programmers.

which sharepoint version? – Paul Dec 7 '11 at 17:17
SharePoint 2007 and MOSS SP1 – James123 Dec 7 '11 at 17:22
up vote 1 down vote accepted

I recommend going about it differently. You can put all your customizations into a SharePoint Solution in Visual Studio, setup a separate brand new SharePoint Server, then Deploy all your Customizations to the new Environment using WSP Installer / Deployment. If you try to clone an existing environment you will spend a lot of unnecessary time trying to reconfigure the old environment to work on the new Server, and it will be an ongoing recurring headache to try and keep them in sync that way.

If you setup your solution correctly, you should be able to include all your changes that way easily, which will then allow you to install updates to the second environment with one Power Shell Command and you are done!

share|improve this answer

Short of buying a 3-rd party tool, your best bet is to do a backup-and-restore into the new environment. It's not easy to keep them in sync after that, so you'll want to develop and enforce some kind of workflow that requires the new stuff going through your qa env. Here's a great article about using CA for backup-and-restore in various scenarios>

share|improve this answer

I maintain pre-production and development environments that are as close to a mirror of production as possible. With this setup, I use one forest per pre-production environment in order to be able to reuse hostnames for Web Applications.

share|improve this answer

Your Answer


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

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