Quantcast
Channel: Small Business Server forum
Viewing all articles
Browse latest Browse all 8539

Connect SBS 2011 to existing SharePoint Farm

$
0
0

I've just recently migrated from SBS 2003 to SBS 2011.  (And incidentally, let me give a shout-out / plug to Jeff Middleton. I'd used his swing migration kit in the past for SBS 2003 > SBS 2003 projects, and his SBS 2003 > SBS 2011 project didn't disappoint!)

Some years ago, we parted ways with WSS hosted on the SBS box and deployed our own separate SharePoint Farm.  Our SharePoint Foundation 2010 intranet is currently hosted on a Web front-end and a DB back-end.  I was hoping to customize the link in RWA to point to my existing site collection vs. the one hosted on SBS.  The closest match I've come across so far is via the suggestion made by Henricus in this link: (http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/bb4b15b9-8cfc-4db0-a7a0-dc8e07bc9eaf/). However, it's not a good fit for various reasons related to firewall and routing complications.  

It occurred to me today that I might be able to simply turn the SBS 2011 box into an additional Web/Application Server for the existing SharePoint farm.  In theory, it would connect to the same content database on the DB server in the same way that my production Sharepoint Web/Application server already does.  But since the user would still be logging into RWA and accessing the Sharepoint Web Application on the SBS 2011 box, it ought to just...work!  At least that's my hope.

Before I go running the SharePoint 2010 Product Configuration Wizard on the SBS 2011 box and jacking with the settings in an attempt to connect it to my existing farm, I wanted to throw the idea out to the group here.  If you have any cogent thoughts about why this ought to (or ought NOT to) work, I'd love to hear them and dive into a discussion about it.

Thanks in advance!

BJ



Viewing all articles
Browse latest Browse all 8539

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>