For me, Ive got it all scripted though Windows Deployment Services, I select what I want and it deploys and installs everything needed, up to a 5 server farm (dev/uat/prod versions), took about 2 weeks to get going on and off (part time at home at night).
For other situations, Ive just got a virtual machine where everything is installed and configured and then sysprepd, with the exception of SharePoint. SP is just installed, but Config Wizard has not been run.. why... bad idea to sysprep a machine with SharePoint installed due to the various SIDs and ids in the config/content databases. Virtual Machines also have the ability of Undo Disks & Snap Shots,. For me, I snapshot a new virtual machine install (once everything is done) and should anything go wrong, I just roll back to the point in time, prior to any custom code touched the hdd of the virtual machine, making recovery a lot quicker and so much less painful. For development reasons, I dont see any use of having 1 shared SQL Server, unless resources on developer PCs/Laptops are an issue. In which case Id say get better resources for the devs but thats not always an option. A shared SQL can work, although it would have X number of SharePoint farms on it. Cheers, Daniel Brown MACS MCP MCTS - SharePoint <https://mvp.support.microsoft.com/profile/Daniel.Brown> MVP cid:[email protected] South Australia's first SharePoint MVP Blog: http://www.danielbrown.id.au <http://www.danielbrown.id.au/> Mobile: 0419-804-099 ý Please consider your Environment before printing this email. From: [email protected] [mailto:[email protected]] On Behalf Of Nathan Rhodes Sent: Tuesday, 26 May 2009 11:32 AM To: [email protected] Subject: Development Environments in SharePoint Hi Guys I am trying to determine what is the best approach to setting up a development environment in terms of easy management, deployment and regeneration if something goes wrong. At the moment we have a VM running for each developer. This has MOSS and SQL configured running its own instance using local services accounts and all there dev apps installed. At this stage the VMs are still running fine but I can see its only a matter of time till one breaks or I have to create one. The process to get them back up and running is to basically grab a fresh Server image and reinstall SQL and MOSS and configure which is very time consuming. The reason for this is SQL as we all know does not like to be Syspreped and imaged it just doesnt work using either named or default instances. I understand there is a way of scripting out a whole install of the OS through to SharePoint and configuring but I imagine this would be painful. I would like to get some ideas on how other people are setting up there development environments? Does anyone use a centralised SQL server where they can all develop and deploy to or does this cause issues from the development front? Any thought or info would be much appreciated. Regards, Nathan_R _____ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: <http://www.codify.com/lists/ozmoss> http://www.codify.com/lists/ozmoss Other lists you might want to join: <http://www.codify.com/lists> http://www.codify.com/lists -------------------------------------------------------------------------------- Support procedure: http://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
<<image001.gif>>
<<image002.jpg>>
