Component Minimum requirement Processor 64-bit, four cores for small deployments 64-bit, eight cores for medium deployments RAM 8 GB for small deployments 16 GB for medium deployments These values are higher than those recommended as the minimum values for SQL Server because of the distribution of data required for a SharePoint Products 2010 environment
1 Comment - Can we run user profile full sync and db full backup simultaneously in SharePoint 2010?
It may be initially appealing, but without the organization’s Information Technology executives completely owning the environment and its governance, customization, and federation strategy it will be a long-term failure and future migration project (from the external cloud into an internally hosted Private Cloud). An enterprise SharePoint Server 2010 platform implemented in a Private Cloud, an environment internal to the organization with total control of its servers, permissions \ security, customization and deployment policies, and federation between line-of-business systems and various data sources is the only deployment platform global and large enterprise organization should focus on. There is a place for a cloud-based SharePoint 2010 deployment in small to medium sized businesses who only mostly require out-of-the-box features and functionality and siloed \ departmental permission strategies
I have a piece out this week in KMWorld where I interview John Mongell , an IT consultant with Boston-based RSM McGladrey and well acquainted with the initial tire-kicking and eventual blocking/tackling connected to SharePoint deployments
In Christian’s post (in terms of how I understood it, which may result in a response from Christian in terms of a misunderstanding) he outlines that SharePoint beats "traditional" ECM solutions because it is easier to deploy and cheaper... and it is easier to deploy and cheaper because it does not have as much technology/functionality
1 Comment - Dave, I agree with just about everything here, except your mischaracterization of my point that SharePoint "beats "traditional" ECM solutions because it is easier to deploy and cheaper." Not my point at all, but closer to your comments. SharePoint is just a tool. Part of the reasoning behind my post was a response to other article beating up on SharePoint for everything it doesn't do, but I may not have articulated it very well
There is no reason you have to call your SharePoint 2010 or SharePoint 2013 implementation “SharePoint&rdquo
By marting@conceptsearching.com on June 4, 2013 in We’ve got quite a bit of experience solving challenges in SharePoint. One of them is Records Management
I'm sitting in the New Zealand Air lounge in Auckland on my way back to the States after a couple weeks on the road presenting at the Australian and New Zealand SharePoint Conferences, thinking about a recurring theme from both conferences: is it necessary to upgrade to the latest version? Obviously, this is not a question that is unique to the SharePoint realm, but is certainly a topic that is popping up more and more as software developers are moving to an online deployment model
These solutions include forward looking and virtual services like Microsoft SharePoint and SalesForce . If you are unfamiliar with these, SharePoint is a multi-purpose web platform that allows organizations to easily and effectively manage, share and publish documents and information
They have also released a product for Microsoft SharePoint. SharePoint has some unique advantages in that SharePoint is Ubiquitous. See my post about The SharePoint Headroom Myth for details, but the gist is … SharePoint is everywhere
SharePoint's most availing attribute has nothing to do with its features, functions, or custom sleights of hand
8403 Colesville Rd #1100Silver Spring, MD 20910USA
Phone: (301) 587-8202Toll free: (800) 477-2446Fax: (301) 587-2711Email: hello@aiim.org
JoinBenefitsLearn More
About UsTerms of Use