RE: The SharePoint + Domain Controller situation
I had a client who had SharePoint on a prod DC and I had to go through the process of getting it off. This old post has some nuggets from the experience and perhaps offers some insights into problems it can cause. Despite the post being about a prod install, it's probably handy info to know... http://www.cleverworkarounds.com/2008/09/16/sometimes-microsoft-bashing-is-j ustified/ -Original Message- From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Michael Nemtsev Sent: Friday, 5 February 2010 4:06 PM To: 'ozMOSS' Subject: RE: The SharePoint + Domain Controller situation There is nothing bad, except that DC role turns off HDD caching to protect AD data. It leads to the performance degradation to work with the HDD. It's not an issue for the SharePoint because it's not drive intensive system and it uses SQL server (RAM) most of the time The bad situation is when you consider using DC + SharePoint on development station (VS and other tools) - performance degrade is very visible in this case WBR, Michael Nemtsev, Microsoft MVP http://www.sharepoint-sandbox.com http://msmvps.com/blogs/laflour -Original Message- From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Joseph Clark Sent: Friday, 5 February 2010 4: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 ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
RE: The SharePoint + Domain Controller situation
I didn't have a lot issues with SP on DC server. Maybe SP2 did work quite well. But definitely SP should be off the DC Server WBR, Michael Nemtsev, Microsoft MVP http://www.sharepoint-sandbox.com http://msmvps.com/blogs/laflour -Original Message- From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Culmsee Sent: Friday, 5 February 2010 7:15 PM To: 'ozMOSS' Subject: RE: The SharePoint + Domain Controller situation I had a client who had SharePoint on a prod DC and I had to go through the process of getting it off. This old post has some nuggets from the experience and perhaps offers some insights into problems it can cause. Despite the post being about a prod install, it's probably handy info to know... http://www.cleverworkarounds.com/2008/09/16/sometimes-microsoft-bashing-is-j ustified/ -Original Message- From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Michael Nemtsev Sent: Friday, 5 February 2010 4:06 PM To: 'ozMOSS' Subject: RE: The SharePoint + Domain Controller situation There is nothing bad, except that DC role turns off HDD caching to protect AD data. It leads to the performance degradation to work with the HDD. It's not an issue for the SharePoint because it's not drive intensive system and it uses SQL server (RAM) most of the time The bad situation is when you consider using DC + SharePoint on development station (VS and other tools) - performance degrade is very visible in this case WBR, Michael Nemtsev, Microsoft MVP http://www.sharepoint-sandbox.com http://msmvps.com/blogs/laflour -Original Message- From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Joseph Clark Sent: Friday, 5 February 2010 4: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 ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
Re: The SharePoint + Domain Controller situation
I've seen quite a lot of SBS Server + DC + Exchange + WSS 3.0 with http://companyweb deployed in the SMB market :( they then want to scale out to support more content and users, oh the pain. DC + SharePoint in prod makes administering SharePoint tougher than usual. On Fri, Feb 5, 2010 at 5:07 PM, Michael Nemtsev nemt...@msn.com wrote: I didn't have a lot issues with SP on DC server. Maybe SP2 did work quite well. But definitely SP should be off the DC Server WBR, Michael Nemtsev, Microsoft MVP http://www.sharepoint-sandbox.com http://msmvps.com/blogs/laflour -Original Message- From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Culmsee Sent: Friday, 5 February 2010 7:15 PM To: 'ozMOSS' Subject: RE: The SharePoint + Domain Controller situation I had a client who had SharePoint on a prod DC and I had to go through the process of getting it off. This old post has some nuggets from the experience and perhaps offers some insights into problems it can cause. Despite the post being about a prod install, it's probably handy info to know... http://www.cleverworkarounds.com/2008/09/16/sometimes-microsoft-bashing-is-j ustified/ -Original Message- From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Michael Nemtsev Sent: Friday, 5 February 2010 4:06 PM To: 'ozMOSS' Subject: RE: The SharePoint + Domain Controller situation There is nothing bad, except that DC role turns off HDD caching to protect AD data. It leads to the performance degradation to work with the HDD. It's not an issue for the SharePoint because it's not drive intensive system and it uses SQL server (RAM) most of the time The bad situation is when you consider using DC + SharePoint on development station (VS and other tools) - performance degrade is very visible in this case WBR, Michael Nemtsev, Microsoft MVP http://www.sharepoint-sandbox.com http://msmvps.com/blogs/laflour -Original Message- From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Joseph Clark Sent: Friday, 5 February 2010 4: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 ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ___ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
