Hi Joe, What I normally do in this situation is to create a domain control in a VM and my SharePoint dev in another. I like to keep them separate as this kind of simulates a real world setup. I allocate say 1GB ram for the DC and about 4-6GB ram for my sharepoint VM.
My advice is to keep them separate. Hope that this helps Regards, Aaron Saikovski Aaron Saikovski | Senior Consultant | Microsoft Australia Tel: +61 2 8817 9280 | Mob: +61 410 480 971 | Fax: +61 2 9870 2499 | Email: [email protected] | Blog: http://blogs.msdn.com/aaronsaikovski -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Joseph Clark Sent: Friday, 5 February 2010 3:40 PM To: ozMOSS Subject: The SharePoint + Domain Controller situation Hi List! As a fairly new SharePoint developer, I've seen anecdotal references all over the Internet about how installing SharePoint and the Domain Controller server role on the same server is a one-way ticket to disaster town. What I am yet to discover is *why* this is bad? What problems does it cause? I'm trying to setup some nice clean virtual machine images for my development environment and was wondering what's the ideal setup? Should I run my dev environment SharePoint server just using local accounts? Is it OK to have the DC on the same computer in a controlled development environment? Should I run an additional virtual machine to act as the domain controller? All advice/suggestions appreciated :-) Cheers, Joe. -- Register now for Atlassian Summit 2010, June 9-11 http://summit.atlassian.com Joseph Clark .NET Developer Atlassian +61 422 812 044 mobile 173-185 Sussex St. Sydney, NSW Australia _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
