Implementing Microsoft Office SharePoint Server brings pitfalls around every turn.
One of the biggest decisions that can determine your ultimate success or failure in implementing Microsoft Office SharePoint Server is how you distribute the deployment. Luckily, our sister site SearchWinIT.com is offering some guidance from SharePoint expert Joel Oleson, who just published a tip about the three distribution models for implementing Microsoft Office SharePoint Server: centralized, regional and distributed.
Oleson’s tip is aimed at IT admins who are planning SharePoint deployments, but his advice works just as well for the solutions providers these admins often hire.
You may be thinking that centralized SharePoint deployments — where one site hosts all the SharePoint services, and users access them over the WAN — are the way to go with all of your customers, because they’re the easiest to manage. But when you factor in how network latency and bandwidth utilization can affect performance, as Oleson points out, you may want to consider another option.
Or you might want to go with the distributed approach — where every branch office has its own SharePoint deployment — because it’s the most simple to implement. But when you consider the inefficiency of having separate storage and maintenance at each site, that may not be the way to go either.
Oleson takes you through the questions you and your customers should be asking before implementing Microsoft Office SharePoint Server, so you’re not stuck wishing you had asked them later. Check out his tip, and while you’re at it, take our SharePoint quiz and read about the best practices for implementing Microsoft Office SharePoint Server.