Two standalone SharePoint 2010 servers with domain controller
I want to set up an environment that has two standalone SharePoint 2010 servers that both belong to the same domain. I want to use a separate machine for the domain controller. Looking in the showcase, I could a solution that meets these needs. In addition, I believe it is bad to try to change the domain of a server after installing SQL server and/or SharePoint.
If my assumptions are correct, I pretty much needs to build the environments from the ground up starting with Windows Server 2008 R2 and just adding SQL Server and SharePoint manually.
Am I wrong, or is there a shortcut for me?
Comments
2 comments
Hey Kirk, yes - we do have a shortcut for you. Try using the SP2010 'server bits only' or 'unconfigured' templates. This will allow you to have multiple SP2010 machines in the same domain.
If you're looking for a pre-built environment from our Showcase, try the Ultimate SP Developer farm. This has a separate:
AD
SQL
SP WFE
SP Apps
Thanks, Scott! That is great news. I was only looking in the showcase, but I think what I need is too specific. However, it looks like you have templates that can do what I want. Because I need at least 4 machines in this environment. I'm trying to create a hybrid SharePoint 2010 on-prem (in CloudShare) with O365 SharePoint 2013. In my CloudShare environment, I think I need:
So I think my question is mainly around the "SharePoint 2010 Additional Server Bits Only" and "SharePoint 2010 Enterprise - No Configuration" templates. It looks like the "no configuration" one has SQL server which I would want. What concerns me is joining the domain after SQL server is installed. Maybe that's OK. Based on the "no configuration" name of the template, I assume that the SharePoint bits are physically on the machine, but the configuration wizard has not been run and therefore I can join the machine to the domain before configuring SharePoint. So, I don't foresee any problems there.
Any comments?
Please sign in to leave a comment.