Montag, 13. September 2010 20:23
Our organization of 5000+ internal users and 1000 external vendors wants to integrate SharePoint 2010. We are are being mandated to use an offering of SharePoint 2010 in the cloud. All peer organizations are also being told to use this service, and we are all going to be on a single SP farm.
We want to have several internal site collections, customization of MySites, an extranet, and a public facing site.
We will not have the ability to access central administration ourselves, we have to go through a centralized state IT department and have them make changes for us. We will only have admin abilities for our own site collections. Installing 3rd party web parts will be a nightmare process as well as making small changes to central admin resources as we are dependent on their time-line to test and integrate these for us.
What issues are we likely to see because of this, and is this even a feasible option for us?
BTW, they do not uphold SLA agreements and currently they sometimes take days or weeks to fix issues, where our people would take care of it in hours if possible.
Mittwoch, 22. September 2010 16:21Umm, was your reply to this thread? As it doesn't seem to be. Or am I not understanding?
Donnerstag, 23. September 2010 02:40ModeratorSorry, it's the answer to this thread:
http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/88848eea-29e2-433f-8ed3-a66d1cf8c852/, i had pasted to the wrong place.
As to your question, i think it is really your organization's decision to deploy SharePoint in one farm or multiple farm based on location.
If you feel the centralized IT is slow, you can, for example, setup your local testing farm, deploy all the web parts you want, create the site and business process, then show them how good and quick you have done.
- Als Antwort markiert GuYumingMicrosoft Contingent Staff, Moderator Montag, 11. Oktober 2010 11:10