Another quick “How To” from Geoff!
I needed to quickly find a way to enable multiple file upload (not Drag / Drop); because I was demonstrating the capabilities of a SharePoint site to clients, and was doing this on a VM with Office 2013 on the same box as the server – so I needed a lot of files! When using SharePoint 2013 and Office 2013 on a Windows 2012 sandbox, you may find that using Windows Explorer View, or using Drag Drop to add multiple files to a document library will not work. You will find strange messages appearing asking you to add the site to Trusted Sites in IE (when it is already displayed in the list), and you may also find that when searching for information on how to resolve this that people will say “Hey installing the WebClient / Restarting the WebClient works”.
Well in the past it has worked – however, specific information concerning how to deploy the service is not altogether available for Server 2012 – there are some minor differences. And, in Windows Server 2012 the Web Client is not installed by default. This means deploying the Desktop Experience feature to the server.
This article describes how to install the Web Client Service in Windows Server 2012 which will resolve how to have the Windows Explorer View operational in SharePoint Sites on the Server.
- Log into your Windows Server 2012 sandbox. Install the Web Client Service. Start the Server Manager, and select Role Based or feature based installation, then click NEXT.

- On the Add Roles and Features Wizard, select ‘Select a server from the server pool’, highlight the relevant server, then click NEXT.

- On the Select Features dialog, click FEATURES from the left hand menu. Scroll the features list till you see User Interfaces and Infrastructure, then check the Desktop Experience option.

- When you select Desktop Experience you will be asked also to confirm the installation of the Ink and Handwriting Services option. Include the management tools. Click Add Features at the foot of the dialog.

- This then confirms the components required to install the Desktop Experience. Click install to proceed.

- You will be asked whether you want an auto restart. Note that when deploying the Desktop Experience a reboot is required. You can either elect to go manual, or automatic. In this example, the server is a sandbox, with no current users so I elected automatic reboot as fine by me by clicking YES.

- The installation proceeds of the Desktop Experience. Process takes around 10 minutes to complete. When it is completed, click CLOSE at the foot of the dialog.

- Note that Machine will restart during the installation process. At the end, check Services and ensure the WebClient service is deployed and started.


Once done, go back into the Team Site and try using Windows Explorer View

Yippee ! All works – hope this helps you out if you run into the same problem…
Microsoft Outlook provides a Task management feature so that users can create and manage personal tasks. These tasks can be assigned to one or more people, and can be linked into their personal Calendars in Outlook. Whilst the same functionality exists in SharePoint, the integration of Tasks in SharePoint with Outlook leads to some compelling benefits.
(more…)
When getting an organization to make an investment into using SharePoint (irrespective of premise i.e. on-off, or SharePoint version), a SharePoint Feasibility Study should be carried out for them. A Feasibility Study identifies the following:
- What are the current information and management challenges? What needs to be put right?
- What are the alternatives (including ways to achieve those objectives), including costs and benefits of each?
- What is the recommended solution, which not only gives reasons for choosing the option but also discusses its feasibility? (how difficult will it be to carry out?, and will the recommended solution meet all the requirements).
(more…)
Using SharePoint, organizations should be leveraging every asset which makes them more productive out of the platform, and as effectively as they can. This means investing time and resources to make sure users are fully utilizing the functions made available to them; especially the capabilities that can help them more productive and meets their objectives.
(more…)
User Adoption of SharePoint is based on meeting the goals and requirements of the business sponsor. To do that, there is an importance in ensuring that the correct features are applied to the relevant solutions to meet their goals. Platform Governance is key; since there would need to be knowledge of the relevant features and an understanding therefore in how they would be implemented, supported, maintained in an evolving SharePoint landscape. This is particularly important in deciding on the migration path of SharePoint 2010 to 2013, since quite a few features have been enhanced.
(more…)
One of the most difficult migration paths for SharePoint is from version 2007 to 2010. Not so much due to the technical requirements concerning things like content database shift, Web Application shift, Site Collection review, Third Party review. But more on the actual sequence of events, which if not worked out completely could leave people attempting to go this in a pickle! To help, I’ve provided a map which I have used with several customers which allows me to produce key documentation and at the same time keep them involved in the process.
To assist the map, there are two project plans attached in 2007 / 2010 / 2013 formats, which allows you to set time-frames against each of the sections.
Note that these are generic. You must use your own judgement concerning things like Third party products (and what you wish to do with them), what must happen to content on the document lifecycle trail (i.e. old sites, archived content), and what must happen to any control processes surrounding things like security (who should have access to the new world).
This is particularly related to testing, and again, you should adopt a generic approach first then tailour it to your own requirements. Read through my Verification and Validation article to give you ideas of what should be in your testing plans (which will encompass technical and non-technical concerns).
The outline below is in collapsed state. Click the + icons to expand each section, and – icons to compress. if the view of the map outline is too small, you can view the full screen by
going here
A major important milestone in the step to get information workers creditations in the use of Office products. Just last year I completed the SharePoint Study guide for Microsoft Office, and now in not the too distant future (in fact in late August to be precise), Office 365 will get an exam study guide. In fact, the author happens to be my co-author for the brilliant study guide for Office 2010 (including SharePoint of course!).
This is I think a major move on the part of Microsoft who are keen to ensure that educational establishments, armed with the free offer of Office 365 will now also be able to offer courses, examinations and creditations for information workers to place on their CVs, and shout to the world they are proficient in the use of Office 365! (more…)
Am working on my forthcoming book concerning the delivery of user adoption and platform governance, and thought that I would share a summarised section which concerns the creation of SharePoint support. a crucial area that relates to how SharePoint services will be managed.
Nb. Am also working on an article which goes into further detail looking at SharePoint support and what are the necessary items to put in place to guarantee success (rather like my Ten Steps for SharePoint implementation article :D). This will be available soon…
Please read on though – hope the summary is useful!
(more…)
I’ve published to TechNET UK an article concerning the use of some great Microsoft Word functionality called Research. This provides individuals with the ability to customize options to suit their research needs. This feature can be used to expose SharePoint search, meaning that individuals can locate information they have access to on SharePoint within Microsoft Office Word, without having to go to the SharePoint site.
To read the summarised blog go here.
A full article is here
Enjoy !
Am in the land of setting up quite a few 2013 environments to demo and test. Some using VMware, HyperV, Cloudshare to name a few. Ran into a ‘gotcha’ starring SQL which I thought I would share. In this scenario I’m setting up a Dev / POC environment which is a single server SharePoint 2013 environment and not set as a Domain Controller. SQL is also deployed to that box. Using the UI it’s not possible to create a new farm due to the fact I’m using a local account as farm admin, therefore, had to use the wonderful New-SPConfigurationDatabase Powershell command to create the SharePoint config database).
(more…)