Tag Archives: SharePoint Administrator

Remove SharePoint 2010 Social Tags Ribbon Control

In recent weeks, SharePoint 2010 deployments have kicked off and I am collecting as much information as possible and will be sharing them here as time permits.

Just saw this on the MSDN Forums today and I think this one ‘trick’ I must make a note of such, just in case.

This is an unusual request, but a valid one, since I strongly believe and advise (since SharePoint 2007 days – geez sounds antiquated!) that social aspects aka My Sites should be the last thing to be switched on in a SharePoint roll out… especially when the organisation and IW’s are just embarking on their SharePoint journey. That’s my opinion based on my experience here.

Well to track back to this forum thread, the requirement was to Remove "I like It" , "Tags & Notes" none



From Central Administration

Navigate to System Settings

Manage Farm Features (_admin/ManageFarmFeatures.aspx)

Deactivate the Social Tags and Note Board Ribbon Controls





From SharePoint 2010 Management Shell

Disable-SPFeature –Identity SocialRibbonControl


That’s it!

HowTo: Set Permissions for Comments on SharePoint Blog

If you want to allow your blog visitors to comment on blog posts you will need to explicitly allow them to do so. To achieve this, you will need to setup unique permissions on your blog.
Here is the procedure:
1. Open http://your_blog_url/Lists/Comments/AllComments.aspx
2. Select Settings > List settings
3. Select Permissions and Management > Permissions for this list
4. Open Actions >Edit permissions (confirm this action when dialog pops-up)

Now you can setup unique permissions for this list. From this step forward you can add permissions for a specific user. The best approach is to give the Visitors group “Contribute” rights for this entire list.

You will also need to limit user’s ability to edit and delete only his comments.
The procedure is as follows:
1. Open http://your_blog_url/Lists/Comments/AllComments.aspx
2. Select Settings > List settings
3. General Settings> Advanced Settings
4. Choose “Only their own? for Edit access option


MOSS 2007 Infrastructure Updates

Microsoft have released Infrastructure Update for MOSS 2007.
The Infrastructure Update for Microsoft Office Servers (KB951297) includes several new Enterprise Search features for SharePoint Server 2007 and the latest performance updates and fixes for the Microsoft Office Servers listed in the system requirements section below.

Key updates for SharePoint Server 2007 include:

  • New Search features such as federated search and a unified search administration dashboard.
  • Several core fixes to Search to improve performance and scale.
  • Platform performance improvements and fixes.
  • Several core fixes to the publishing Content Deployment features to improve reliability.
Download 32 bit version | 64 bit version

The update will install properly if either of the following are true:

It is recommended that you install 2007 Office servers Service Pack 1 (SP1) and the Microsoft Windows SharePoint Services 3.0 Infrastructure Update before you install this update.

Download the 32-bit version of the Windows SharePoint Services infrastructure update together with installation instructions and deployment strategies.

Download the 64-bit version of the Windows SharePoint Services infrastructure update together with installation instructions and deployment strategies.

Howto configure client alias for SQL Server

This post will show you how to configure client aliases for SQL Server. One of the security hardening measures is configuring non-standard port for SQL Server instances.

A default instance of SQL Server listens for connections on TCP port 1433. If a client computer is unable to connect to the database on TCP port 1433, it queries the SQL Server Resolution Service on UDP port 1434.

To protect the database server, you can block the standard ports used by SQL Server and configure your SQL Server instances to listen on a nonstandard port.

Configuring client aliases for SQL Server

0. Open SQL Server Configuration Manager, and expand the SQL Native Client Configuration node.

1. Right-click Aliases, and then click New Alias.

2. In the Alias Name box, type the alias you wish to use when connecting to the database server.

3. In the Port No field, type the port number that you assigned to your SQL Server instance.

4. In the Server field, type the name of your database server.

5. Click Apply, and then click OK.


Start, Run, clicnfg

Enable TCP/IP protocol


Select properties

Select Alias Tab

Configure client aliases on your WFE servers and application servers using the above steps. You must install SQL Native Client and SQL Server Configuration Manager on each server.

Scripts to backup and restore SharePoint 2007

I can add this to my arsenal of SharePoint Scripts. Just perfect.

FULL_BACKUP.BAT – Use Control Panel – Scheduler to run once a week. Don’t forget the ‘Run As’ account also needs write access to the backup location, in addition to the Central Admin app pool identity, and the SQL Server Machine account. This command will backup the entire farm to the following file share. Don’t use drive:\directory format.


“c:\program files\common files\microsoft shared\web server extensions\12\bin\stsadm.exe” -o backup -directory \\servername\backupshare -backupmethod full


DIFF_BACKUP.BAT – Use Control Panel -Scheduler to run when you want differential backups. Remember the same security as above, but also it will fail if you add a content DB or Web App since the last FULL backup.


“c:\program files\common files\microsoft shared\web server extensions\12\bin\stsadm.exe” -o backup -directory \\servername\sharename -backupmethod differential


IIS_MetaBase_Backup.BAT – This is used to backup your IIS Configs to each IIS server, in their respective ‘metaback’ directories. Just add an additional line for each server you want to backup. It will create a backup of the metabase called ‘WeeklyBackup’ with a version appended. The password doesn’t matter, it just makes the backup portable.


cscript.exe %systemroot%\system32\iisback.vbs /s servername /u domain\username  /p userpassword /backup /b WeeklyBackup /v NEXT_VERSION /e password

cscript.exe %systemroot%\system32\iisback.vbs /s servername2 /u domain\username  /p userpassword /backup /b WeeklyBackup /v NEXT_VERSION /e password

cscript.exe %systemroot%\system32\iisback.vbs /s servername3 /u domain\username  /p userpassword /backup /b WeeklyBackup /v NEXT_VERSION /e password


As Ben says, use at your own risk.

Stay tuned, subscribe via email