Dom Cosgrove Blog

Found this useful CSS Reference for SharePoint 2010:

http://sharepointexperience.com/csschart/csschart.html

If you’re looking for a one stop shop for examples of Web Publishing sites using SharePoint as a Web Content Management solution, then check out this site:

http://www.topsharepoint.com/

Nice thing is they are categorised and ranked!

When you try to put your VMware virtual image into full screen on Windows 7 you may find that you get a blank black screen. Even if you change the screen resolution on the guest OS, to match that of your host OS you still get a blank screen.

The issue is that the VMware display drive has not been configured for Accelerated 3D Graphics. To resolve this issue, shut down the VM, then under VM > Virtual Machine Settings > Display check the Accelerate 3D Graphics check box and select OK. You should now be able to restart your VM and go into full screen mode.

So in the past I’ve download Virtual Machines that have a US keyboard as the input type or when I built the windows instance I forgot to change the keyboard settings. As a result when I have passwords with the ampersand symbol (@) in them, I need to use the Shift + 2 (“) keyboard stroke. So hey you can live with this setting, but I quite like having my keyboard and regional settings configured correct on the server. So this is easy enough through Control Panel > Region and Language settings. So you change your Format to English (Ireland) so that the date time is correct. You change your location for your locale setting to Ireland. You then change your Keyboard and Languages to English (Ireland) – Irish. You test typing your password in notepad and are happy that changes have been made. You then log off your computer or reboot and go to log back on… wait a minute you try your new keyboard settings and you still have to use Shift + 2 to log in. You go and open notepad again and hey presto your keyboard settings are still in English (Ireland) – Irish. What gives!?!

The solution is actually under the Region and Language > Administrative tab. There is a section for the Welcome screen and new user accounts, click the Copy Settings… button, you’ll notice that the Input Language for the Welcome Screen and the New User Accounts is still English (United States) – US. This is not what we want. Select both the check boxes to copy your current settings to the Welcome Screen and New User Accounts and click OK. Log off and back on and there you have it you can log on using the expected keyboard behaviour.

The following steps may help if you get an error when opening Office documents through MS Office Web Applications from a SharePoint Document library.

Word Web App cannot open this document for viewing because of an unexpected error. To view this document, open it in Microsoft Word.

Error Id: 68d8674b-53ac-407c-bfd7-9ef2a2c16611, 201116105124532

1. If you are running the SharePoint / Office Web Apps on a VM that also has the domain controller, you’ll get this error. This is not a supported configuration for a production environment. As this is typical for a demo / development VM, then you can run the following PowerShell:

   $e = Get-SPServiceApplication | where {$_.TypeName.Equals(“Word Viewing Service Application”)}
   $e.WordServerIsSandboxed = $false
   $e.WordServerIsSandboxed
   

   #(Please use the below script for PowerPointServiceApplication – You need to enter “Y” for the answer of each cmd)
   Get-SPPowerPointServiceApplication | Set-SPPowerPointServiceApplication -EnableSandboxedViewing $false
   Get-SPPowerPointServiceApplication | Set-SPPowerPointServiceApplication -EnableSandboxedEditing $false
   

   In the server’s c:\windows\system32\inetsrv\config\applicationHost.config
   Add the line below in the end of the dynamicTypes.
   <add mimeType=”application/zip” enabled=”false” />
   

   IISRESET
   

2. If you are seeing events with an ID of 3760 (shown below), you have not given the service account running the Office Web Application Services sufficient access. Ensure that the account has the required permissions.

Reference:

http://blogs.msdn.com/b/opal/archive/2009/11/16/installation-notice-for-sharepoint-2010-public-beta.aspx

This should be your one stop shop for all updates related to SharePoint 2010.

http://technet.microsoft.com/en-us/sharepoint/ff800847

If you want to be alerted or aware of updates then you can subscribe to the SharePoint Team Blog.

Found this web site which checks how accessible web sites are. If your site is not on the internet, then you can save your html and upload it to the site. There is also a tool bar for FireFox.

WAVE is a free web accessibility evaluation tool provided by WebAIM. It is used to aid humans in the web accessibility evaluation process. Rather than providing a complex technical report, WAVE shows the original web page with embedded icons and indicators that reveal the accessibility of that page.

http://wave.webaim.org/

This is a useful list of SharePoint 2010 features per version / edition. Better than some of the comparisons charts out there.

http://sharepoint-sandbox.com/files/sharepoint2010features.mht

This is definitely worth a look at. MatchPoint seems to have a very strong, metadata / taxonomy system that surpasses what both SharePoint 2007 & 2010 offer OOTB. It has some very nice WebPart for rolling up content based on the taxonomy and for creating views of your data. I can definitely see the business benefit of implementing MatchPoint.

http://www.getmatchpoint.com/

Don’t use service account names with more than 20 characters! Why… read on!

Recently, I was working on updating the Windows SharePoint Service Help Search Accounts. The issue was that when the DEV, UAT and production farms where originally built the same service accounts were used for each environment. This is NOT best practice, so I went about changing DEV and UAT, leaving Production using the original accounts. The process of updating the service accounts is simple enough using STSADM:

stsadm –o spsearch –farmserviceaccount [domain\serviceaccount] –farmservicepassword [password]

stsadm –o spsearch –farmcontentaccessaccount [domain\serviceaccount] –farmcontentaccesspassword [password]

An issue arose where we used the original service account post-fixed with the environment e.g.

When trying to update the service accounts I kept getting the following message:

Basically, saying that the account being provided is not valid. If I did the same update through the Central Administration I got the following message:

The username and password entered are not valid.

After several rounds of changing the password, recreating the account and trying manually set the service account, it was discovered that SharePoint uses the sAMAccountName rather than the UPN when it passes credentials. The sAMAccountName has a 20 character limit for backward compatibility.

The work around is simple keep the service account names to less than 20 characters. An alternative approach, one that I’ve not tested yet is to use the following format for the account [service account]@[domain.com]. Anyway I hope that this will save you some time, I wish I had known this limitation before I embarked on updating the accounts.