Monday 5 November 2012

IRM, AD RMS and Microsoft Office Considerations

Information Rights Management (IRM) allows individuals and administrators to specify access permissions to documents, workbooks, and presentations.

AD RMS-aware applications implement IRM to help prevent sensitive information from being printed, forwarded, or copied by unauthorized individuals.

The following document provides guidance about the various Microsoft® Office suites and the supported Active Directory Rights Management Services (AD RMS) features.

AD RMS and Microsoft Office Deployment Considerations

TechNet Webcast AD RMS Overview

TechNet Webcast- Microsoft Active Directory Rights Management Services Overview (Level 300)

AD-RMS-webcast

Information protection is one of the key security concerns for companies. This presentation provides an overview of how Microsoft Active Directory Rights Management (AD RMS) Services can help you mitigate the risks inside and outside the enterprise providing end-to-end solutions that protect documents and e-mails.

This presentation covers all different client-side and server-side applications that support AD RMS (IRM) and provides an overview of how to securely collaborate with people outside your organization. Demos will be provided in the session.

AD RMS Team Blog

AD RMS Client Requirements

The Active Directory Rights Management Services (AD RMS) client is included with the Windows Vista®, Windows® 7, Windows Server® 2008, and Windows Server® 2008 R2 operating systems. If you are using Windows XP, Windows 2000, or Windows Server 2003 as your client operating system, a compatible version of the AD RMS client is available for download from the Microsoft Download Center Web site.

The AD RMS client can be used with the AD RMS server role included in Windows Server 2008 and Windows Server 2008 R2 or with previous versions of RMS running on Windows Server 2003.

Microsoft Windows Rights Management Services Client with Service Pack 2 – x86

The client support almost everything for Windows 2000 server/workstation SP4 onwards and includes 32/64 bit support.

SharePoint Content Management Interoperability Standard (CMIS)

Content Management Interoperability Standard

The above article describes the Content Management Interoperability Services (CMIS) connector for Microsoft SharePoint Server 2010, which enables SharePoint users to interact with content that is stored in any repository that has implemented the CMIS standard. The connector also makes SharePoint Server 2010 content available to any application that has implemented the CMIS standard.

The CMIS connector is available as part of the SharePoint 2010 Administration Toolkit.

SharePoint 2010 Administration Toolkit (SharePoint Server 2010).

I have found comment that this is incorporating with SharePoint Server 2007. I do not have the time to research this further but include links to an MSDN article and the MOSS 2007 Administration Toolkit.

Integrating External Document Repositories with SharePoint Server 2007

SharePoint 2007 Administration Toolkit

Saturday 3 November 2012

SharePoint 2007 File Sizes and Limitations

A user performing an upload to SharePoint is limited to 50mb per upload. This could be a single file of 50mb or a multi-file upload of 10 5mb files. 

The largest single file that can be stored in SharePoint was 2gb, due to SQL 2005 limitations.

A blob in SQL 2005 cannot be larger that 2gb. Each file is stored as a blob in the SQL Server content database for the site collection.

SQL 2008 can handle files larger than 2gb.

SharePoint 2007 hard limitations

SharePoint 2007 Database Maintenance

Here are a series of useful TechNet articles on  Database maintenance for Microsoft Office SharePoint Server 2007 MOSS

Add, split, and merge content databases

Database maintenance (Office SharePoint Server 2007)
Database maintenance for Office SharePoint Server 2007 (white paper)
Planning and Monitoring SQL Server Storage for Office SharePoint Server: Performance Recommendations and Best Practices (white paper)
Move content databases (Office SharePoint Server 2007)
Move all databases (Office SharePoint Server 2007)

SharePoint 2007 split a content database

I want to be able to split the content database in SharePoint (MOSS) for backup purposes much the same as you can do with Exchange data stores.

I was aware of file share/backup bloat that was caused by several of my clients dumping the contents of their digital cameras to their servers while preparing quotes etc.

Here is a link to a TechNet Article explaining how to split a content database.

Move site collections to a new database (split a content database) (Office SharePoint Server 2007)

It is part of the larger:

Add, split, and merge content databases