If you’re a site owner, it’s a good idea to create a governance model, often referred to as ‘Best Practices’ – that is, a model to address your site’s policies, processes, roles, and responsibilities. Naturally, commercial or professional procedures that are accepted or prescribed as being correct or most effective, are considered the best to follow.
As Best Practice is a method or technique that has been generally accepted as superior to any alternatives, usually it produces results that are superior to those achieved by other means.
Therefore, this category is full of useful tips, practical examples and advise. With How To videos, eBooks, Webinars, Blogs to help you learn and become more productive in implementing Best Practices.
In the last week I’ve been asked for this information a few times, so I decided to go ahead and blog it. I’ve been hesitant to put out an official blog post on this, because I don’t think it’s ready for prime time. But, it keeps coming up, so here it is, the steps I follow when I install SharePoint 2010.
The processes surrounding a database driven website like SharePoint can so different than those of a static site, that if you don’t understand it and fail to make the leap, you will be missing out on a lot of ROI.
Static web sites operate on a similar process as files on file shares that most of us are very used to.
There are many uses for having a number of SharePoint farms within your organization; Geo-replication is the most common distributed enterprise SharePoint solution scenario. Geo-replication refers to the replication and synchronization of SharePoint structure, content, metadata, security, workflows and decisions from a SharePoint environment running in one part of the world (headquarters or a central command) to one or more SharePoint environments operating in several different locations around the world
You may have deployed SharePoint and had a complaint from a mobile user, by default the experience isn’t great. A legacy design decision was made for SharePoint 2010’s that creates a poor default mobile smart phone experience. In my mind if they would have kept the capability for mobile as an alternative and left the default experience alone things would be much better. Instead, by default, an iPad or iPhone, Windows Phone 7, Android, and even Blackberry… yes essentially all your rich mobile phones have a degraded user experience. SharePoint 2010 inherited the mobile interface that was built in SharePoint 2007, and it was improved slightly for publishing sites in SharePoint 2010, and a whole SDK was built for mobile. Was it a waste?
SharePoint Integration
In the past, integrating multifunctional devices with SharePoint had been significantly difficult to achieve especially when the integration needed to take place not only on one Multifunctional device but on a heterogeneous fleet of devices. No wonder you can find all kinds of technical forums that have “SharePoint integration” as the topic of discussion and desperate administrators searching for help.
It is still a hard nut to crack for many IT specialists all around the world. Getting a fleet of multifunctional devices integrated with SharePoint and continuously maintaining and updating all of the configurations needed for a smooth documents workflow (just think of all the different user rights for specific folders, sites etc.), is a daunting task to be sure.
Most large companies running on SAP are increasingly deploying SharePoint as an enterprise-wide business productivity and collaboration platform. With a growing number of business users feeling comfortable in the SharePoint environment, there is an opportunity to leverage SharePoint as a platform for accelerating SAP transactions. But exactly which business processes does it make sense to automate with an SAP/SharePoint integrated approach?
