I love the technical diagrams that the Office/SharePoint teams release… if you have access to a plotter (or Kinko’s), you can print them out and hang them on your wall. Why wouldn’t you? ;)
All of the diagrams are available in PDF, XPS, and VSD (Visio) format in case you want to edit the diagram yourself to add your own logo or reflect a specific environment before presenting it to your manager/stakeholder/client.
Deployment Options for Microsoft Office 2010
Download (http://go.microsoft.com/fwlink/?LinkID=168621)
Describes and illustrates the client deployment methods for Office 2010. Deployment options include network share, Group Policy startup scripts, managed deployment, and virtualization. Use this model with the following article: Choose an option for deploying Office 2010.
Deploy Multilanguage Packs for Microsoft Office 2010
Download (http://go.microsoft.com/fwlink/?LinkID=168622)
Describes and illustrates how to deploy multilanguage packs for Office 2010. Elements include evaluation criteria, planning considerations, and deployment tasks. Use this model with the following article: Plan for multilanguage deployment of Office 2010.
64-bit Client Installation of Microsoft Office 2010
Download (http://go.microsoft.com/fwlink/?LinkID=168620)
Describes and illustrates the 64-bit client installation of Office 2010. Elements include setup overview, processes, requirements, deployment considerations, and supported scenarios. Use this model with the following article: 64-bit editions of Office 2010.
Virtualization Overview - Architecture
Download (http://go.microsoft.com/fwlink/?LinkID=168624)
Describes and illustrates the architectural overview of virtualization technology and the different models that are possible. Use this model with the following article: Plan for virtualization for Office 2010.
Application Virtualization - Delivery Methods
Describes and illustrates delivery methods of virtualization, focused on sequencing. Use this model with the following article: Plan for virtualization for Office 2010.
Application Virtualization for the Mobile User
Describes and illustrates stand-alone delivery method of virtualized applications for mobile users. Use this model with the following article: Plan for virtualization for Office 2010.
Volume Activation of Microsoft Office 2010
Download (http://go.microsoft.com/fwlink/?LinkID=188811)
Describes the volume activation methods for Office 2010 and illustrates typical network scenarios. Use this model with the following article: Plan volume activation of Office 2010.
I had a co-worker recently ask me about some of the incredibly long URL’s now used in SharePoint 2010. In SharePoint 2007, the URL to a document hosted in a document library looked something like http://sharepoint/sites/teamsite/project%20documents/mydoc.xls. Great for cutting and pasting into an e-mail. After upgrading the SharePoint 2007 farm to SharePoint 2010, right-clicking on that same document and copying the URL would result in something that looked like
http://sharepoint/sites/teamsite/_layouts/xlviewer.aspx?id=/sites/teamsite/project%20documents/mydoc.xls&Source=http%3A%2F%2Fsharepoint%2Fsites%2Fteamsite%2Fproject%20documents%2FForms%2FAllItems%2Easpx%3FRootFolder%3D%252Fsharepoint%252Fsites%252Fteamsite%252Fproject%documents%26View%3D%7B391E5EDC%2DAA9C%2D4F64%2D9E8D%2D401965CFC83A%7D&DefaultItemOpen=1
Not so good for cutting and pasting into an e-mail, right? Why did the URL length grow so long when referring to the same document for which SharePoint 2007 had such a nice short URL?
SharePoint 2010 is not the only place with long names. Picture by Bree Bailey
PowerPoint in the browser, courtesy of Office Web Apps
What if you just want to link directly to the document itself? Some e-mail programs limit the length of URLs, as do places within SharePoint itself (Document Link content types can only be 260 characters, and links within “Current Navigation” are also limited). The link to the open-in-web-apps-view is usually too long.
Let’s deconstruct the long url:
Pretty sure your eyes are crossed at this point… this is way more than you wanted to know. Anyhoo… the point I was trying to make is… out of that ginormous URL, it is relatively easy to extract the path to the document itself. That source parameter is only necessary for Web Apps, and it takes up a lot of spac. Just combine the protocol with the server name with the parameter saying where the document is (in our example above, http://sharepoint/sites/teamsite/project%documents/mydoc.xls. It’s easier done than said
The other way to change the behavior away from long URLs (and back to the way SharePoint 2007 worked) is to change the default document opening behavior. You must be a Site Collection Administrator to do so, and simply go to:
Now you will notice that right-clicking on a document and selecting the URL will leave you with a nice short URL. Hope this helps someone!
Just a quick solution in case you ever get the following message when trying to open a SharePoint Document Library in explorer view from Windows Server 2008
Your client does not support opening this list with Windows Explorer.
This is due to the fact that Explorer view uses the WebDav protocol to connect to SharePoint from the client. As Windows Server is not designed to be a client, the WebDav client is not installed or enabled by default.
In order to enable the WebDav client (along with other client features such as Windows Media Player and Desktop Themes) on a server (you’re not doing this on a production server, right?), simply enable the Desktop Experience feature.
(thanks to Troy on the SharePoint team for this tip!)
Update: This can also happen if you are using Internet Explorer 6 and the URL to the Document Library is longer than 100 characters (covered in KB 923906), but you're not using IE 6 are you? It's time to upgrade! http://www.microsoft.com/windows/internet-explorer/default.aspx