Welcome: Guest!

MOSS Forum

 
Home » Forum » MOSS       Ask a questionRSS Feeds

Cloning a developer VM

  Asked By: Marvin Mccoy         Date: May 08, 2007      Category: MOSS      Views: 283
 

We are trying to develop a process to stamp out Sharepoint 2007 VMs
for developers. We built a "master" VM server (VMware) with Windows
2003, Visual Studio, and a Standalone install of Sharepoint 2007
(using SQL Express). When we copy this VM and create another VM,
Sharepoint will not come up (even CA), giving the error that it can
not connect to the cofiguration database.

I believe SQL Express or something else in the install is sensitive to
the server name or IP address, and that may be the problem...but I am
not sure where to fix it.

Any ideas?

Tagged:      

 

3 Answers Found

 
Answer #1       Answered By: Vinay Thakur          Answered On: May 08, 2007       

SharePoint is certainly trying to load its Configuration database by
using the SQL servername for the Instance. Renaming the server after
SQL is installed isn't going to work very well. I haven't done it yet,
but it should be trivial to script the install of SharePoint. Run that
after you rename the machine. Use Sysprep too if the VMs will be on a
network where they can see each other.

 
Answer #2       Answered By: Shameka Rich          Answered On: May 08, 2007       

I would not use SSEE to develop  on, for any reason. I assume your Devs
have MSDN? I would simply run a full copy of SQL Server Standard edition
in EACH VM and build the farm on that.

You still do not want to rename the VM and re-use, however. That will
break SQL Server. And, if you fix SQL Server by renaming, SharePoint
will fail and it is a real pain to fix...

Every dev should load the VM in a private subnet, or you will get
naming/browsing conflicts.

 
Answer #3       Answered By: Royce Orr          Answered On: May 08, 2007       

What you need to do is to

1. Install SQL without starting it up at all

2. Install SharePoint without running the configuration wizard

3. Sysprep it

then you can duplicate it all you want, rename it all you want, but once you
start the sql, do not rename it any more.

Been using this since b2 days, and I've duplicated so many vms without any
problems.

 
Didn't find what you were looking for? Find more on Cloning a developer VM Or get search suggestion and latest updates.


Your Answer
  • Answer should be atleast 30 Characters.
  • Please put code inside [Code] your code [/Code].

 
Hall of Fame  |  Facebook  |  Twitter  |  LinkedIn  |  Terms of Use  |  Privacy Policy  |  Contact us
RSS Feeds: Articles |  Forum |  New Users |  Activities |  Interview FAQ |  Poll |  Hotlinks


Go4Sharepoint, is a Microsoft Featured Community. Microsoft, Windows, Sharepoint, Sharepoint logo, Windows logo, etc are trademarks of the Microsoft Corporation. All product names, logos, copyrights, and trademarks mentioned are acknowledged as the registered intellectual property of their respective owners. This site is not in any way affiliated with, nor has it been authorized, sponsored, or otherwise approved by, Microsoft Corporation.

Copyright © 2008-2011