| Subscribe via RSS

Showing newest 4 of 7 posts from May 2009. Show older posts
Showing newest 4 of 7 posts from May 2009. Show older posts

May 29, 2009

SharePoint and Information Management Policies

| 0 comments |

Did you know you can create policies within SharePoint that will dictate how long a document will reside in a library before it’s automatically disposed of?  Did you know you can enable barcodes on documents for physical asset recording?  Did you know you can achieve all of this without writing a single piece code?  Information Management Policies within SharePoint is a key and usually under utilised SharePoint feature  that will assist any organisation with the lifecycle management of document  libraries, plus a whole lot more.  These policies can be created at the document library level and even set for each unique content type or you can create site collection level templates that can then be re-used throughout your SharePoint sites.  I will go through each of the components that can be configured within Information Management Policies below.

Firstly, to create a site collection policy, navigate to your top level site and select Site Actions / Site Settings / Modify All Site Settings / Site Collection Administration and click on Site collection policies. 

site collection administration SharePoint site collection policies 

The below screen will then appear allowing you to create or import an information management policy.  In our case we will click on Create.

site collection policies sharepoint

To create a policy at the document library level, click on Settings / Document Library Settings, within the document library itself and then click on Information management policy settings.

information management policy settings permissions and management sharepoint

Click on Define a policy …

define a policy sharepoint site collection policy

Regardless of where you create your information management policy, the following screen will then appear after clicking on the OK button which allows us to name our policy and also provide a thorough explanation to our end users explaining and making them aware of the policy that is being applied to the content  via the Policy Statement .  The Administrative Description area is specifically for administrators or policy writers in the event that a policy is required to be altered.

 

SharePoint Information Management Policy 

You will notice that SharePoint  includes four information management policy features to help you manage your content.  They are; Expiration, Auditing, Document Labels and Document Bar Codes.  I will go through each of these below with examples to assist in determining when and why you should use information management policy within SharePoint.

Enable Expiration

Enabling expiration on a document library provides you with a basic Information Life Cycle Management (ILM) strategy for your documents and or emails with email enabled document libraries. Expiration options provided allow you to create a consistent retention period for your documents based on create or modified date.  In my case I have specified that items located in the document library that are older than 6 months are automatically deleted.  You also have the option to control how the information is routed, such as creating a workflow that would archive rather than delete the item. 

By implementing expiration policies in your document libraries you will reduce unnecessary redundant content and reduce noise in search results.

Expiration ILM SharePoint Policy Statement enable expiration 

Enable Labels 

This option or feature allows us to uniform the creation of labels in documents ensuring that document properties such as file name, author creation dates etc can be included in the label when a document is printed.

In my example I have created two additional columns in my Document Library, “Project Name” and “Manager” which can now be used in the label format.

Project {Project Name}\n Managed By: {Manager}

(Please note that “\n” creates a new line)

enable labels label format sharepoint

Microsoft Word Document Management Panel SharePoint

Properties item sharepoint

Enable Barcodes

This allows you to generate Code 39 standard barcodes and apply them to your document properties that can also be displayed in the header area of your document.  This is useful when managing physical records such as computer equipment.  By enabling barcodes you are primarily using this feature to track hard copies of documents, i.e. documents that are outside your SharePoint Site.

Barcode SharePoint Information Management Policy 

Enable Auditing

This option allows your to create specific audit trails for specific document libraries.  Please note that you can also enable Site Collection Audit Settings that applies to all items within a site collection.  This can be achieved via, Site Actions / Site Settings / Modify All Site Settings / Site Collection Administration, Site collection audit settings. 

In summary, auditing provides you with the ability to track specific events (listed in the screen capture below) with regards to the life cycle of a document.

Auditing SharePoint

This information can be accessed via the Excel based Audit Log reports that are also located under Site Settings.  Reports showing the audit trail can be run by site collection administrators.

View Auditing Reports Excel SharePoint

Exemption from Policy

You also have the ability to exempt an individual item from a policy that is being applied to a document library.  Simply navigate to the item that you want to exempt from the policy being applied and click on View Properties.  The below screen will then appear providing you with the ability to click on Exempt from policy …

exempt from policy no exemption sharepoint

A warning will then appear in which you will have the option to click on Exempt to continue or cancel to go back.

Set policy exemption SharePoint

If I now view the properties of the same item, you will notice that the exemption has been applied and also providing you with the ability to reverse the exemption.

The item is exempt from policy.  This item will not be expired until the exemption is removed.

As you can see, setting up Information Management Polices is an easy task and I would be interested to know how many SharePoint Implementations out there are actually using this feature and why?

May 22, 2009

Stream media from your SharePoint Site with Windows 2008 Media Services

| 0 comments |

Wouldn’t it be great if you could deliver digital media content including Windows Media Audio (WMA) and Windows Media Video (WMV) from your SharePoint site without buffering issues and poor viewing experience.  We must admit that SharePoint itself isn’t great in handling and storing digital media in particular large Video files and we can blame SQL for that!  Even though you can host WMV’s in document libraries just like any other file, features such as fast streaming capabilities effectively eliminating buffering time, and reducing the likelihood of playback interruptions due to network conditions is non existent.  However, this is where Windows 2008 Media Services complements SharePoint well, when in need of delivering rich video and audio content.

Some of the notable features of Window Media Services include;

  • * Cache/Proxy Management providing a better viewing experience for users by conserving network bandwidth.
    * Advanced Fast Start delivers instant on playback, again eliminating buffering time
    * Advanced Fast forward and rewind functionality
    * Broadcast AutoStart in the event of power failure or other interruptions.

More details on Windows Media Services 2008 can be found on the Microsoft Site here 

I have setup a dedicated server core installation of Windows 2008 (you got to love server core for these type of roles) and have installed the Media Services component. Detailed instructions in setting up Server core can be found on the Microsoft TechNet Site.

After installing server core you will need to then install the Streaming Media Services role.  For some reason the Media services role isn’t on the Windows 2008 DVD and you will need to download it first from the Microsoft download site here 

After downloading the file from another machine, copy it your Server Core installation and run the downloaded msu file.  At the command prompt, type the following commands in order;

start /w wusa /quiet Windows6.0-KB934518-x86-ServerCore.msu (32 bit editions)

start /w wusa /quiet Windows6.0-KB934518-x64-ServerCore.msu (64 bit editions)

start /w ocsetup MediaServer

net start wmserver

Once the installation is complete, you will need to use the Streaming Media Services MMC snap-in to remotely configure Streaming Media Services.  You can install Remote Server Administration Tools (RSAT) for the Streaming Media Services role on a computer that is running Windows Vista.  You can download the installation for the MMC Snap in from here.

To start the snap-in, click Start, click Run, and then type wmsadmin. If you run into any issues when connecting to the media server check out Microsoft’s release notes for known issues.

The following Windows Media Services console launches;

Windows 2008 Media Services SharePoint

Right click on Window Media Services node and select Add Server and type the Server name or IP address of your Media Services Server Core machine.  The following screen will then appear in which you can then add a publishing point to store your media files.

 Windows 2008 Media Services SharePoint

Right clicking on Publishing Point  will provide you with 2 options, a wizard option and an advanced option.  Let’s keep it simple and select Wizard.  The following welcome screen will then appear.

Windows 2008 Media Services SharePoint

Click Next.

Enter a descriptive Publishing Point Name. 

Windows 2008 Media Services SharePoint

Click Next.

Select your Content Type.  In our case we only need an area for storage of media files to be played back effortlessly from our SharePoint server so we are selecting Files as our option.

Windows 2008 Media Services SharePoint

Click Next.

Select your Publishing Point Type.  In our case, we want each user to be able to control the stream for each individual video that we publish on SharePoint so we will select On-demand publishing point.

Windows 2008 Media Services SharePoint

Click Next.

  1. Specify your directory location where you will be storing the video files (Note, you will need to create this folder in advance).  Your video and audio files will also need to be copied into this location manually, i.e. via Windows Explorer.

Windows 2008 Media Services SharePoint

Click Next.

Specify your content playback settings.

Windows 2008 Media Services SharePoint

Click Next.

Specify whether to enable or disable logging.

Windows 2008 Media Services SharePoint

You are then displayed with a summary screen outlining the settings chosen. Click Next and then click on finish.  Specify whether you want to publish an announcement, in our case it’s not necessary as we will be creating links from our SharePoint server to the video files located on our Media Server.

You will now notice our newly created Publishing Point “Georges Videos” listed in the MMC snap in.  Clicking on the source tab will list the videos that are located under the directory that we specified earlier.  In my case, I have copied a video file titled “Movie Stars.wmv”. 

Windows 2008 Media Services SharePoint

You can right click on the file and click on test.  This will run a test on the file uploaded to the media server and provide you with some statistics with regards to network performance.  The URL to the media file is also displayed.  This is the URL that is required to create your links in SharePoint.

Windows 2008 Media Services SharePoint

I took a graphical fancy option and designed a web page in SharePoint Designer with thumbnail pictures that once clicked on will launch the file in Windows Media Player (assuming that is your default player for WMV and WMA files).  Reminder, these are not http:// links but mms:// links.

Windows 2008 Media Services SharePoint 

That’s all that is to it!  Hopefully you can now enjoy many hours of enjoyable video and audio streaming, minus the buffering issues!

May 18, 2009

Exchange 2010 Beta, So what’s new? – Part 3/3

| 2 comments |

We have arrived at the final article of this series on Exchange 2010 Beta, with this post focusing on the new features and technology enhancements.  Today is all about the reasons why we are all going to migrate to this latest product offering when released to the public, right? 

Okay, so let’s begin with everyone’s favourite, Outlook Web Access (OWA) and focus on some of it’s new features.   OWA has come along way since the days I first used it as an end user in Exchange 5.5.  From the outset you will notice that Exchange 2010 OWA adopts the Windows Live theme, see below screenshots, and by default displays your messages in conversation view.  The OWA premium client experience can now be accessed from Firefox and Safari and not limited to Internet Explorer, a welcome by all who don’t necessarily run Internet Explorer as their primary browser or don’t run a PC for that matter and because I run OS X at home it was the first enhancement I tried out.  Check out the screen shots below of OWA premium running through Firefox.  Some of the notable features and enhancements of OWA in 2010 are captured in the below screenshots.

Outlook Web Access Features

OWA Premium running on Mozilla Firefox.

OWA Exchange 2010

Messages are arranged by conversation view by default.

conversation view owa exchange 2010

You now have the ability to view Calendars side by side just like you can in Outlook 2007.

calendar exchange 2010 owa

Here’s another enhancement with OWA displaying user’s mailbox usage and quota limit imposed.

Mailbox space used owa 

Also a nice touch is the ability to open up other user’s mailboxes and have them displayed in the same window as your own.

OWA Exchange 2010

opening other users mailbox owa exchange 2010

Other notable enhancements with regards to OWA are listed in the following TechNet article and include;

  • *Favourites in the Navigation Pane
    *Search folders
    *Message filtering
    *The ability to set categories in the message list
    *Options in the Web management interface for Outlook Web Access
    *The ability to attach messages to messages
    *Expanded right-click capabilities
    *Integration with Office Communicator, including presence, chat, and a contact list
    *The ability to send and receive text (SMS) messages from Outlook Web Access

The trend with OWA throughout the years is to try and get closer and closer to its fully fledged desktop client Microsoft Outlook, and with the advances of web technology over recent years the gap is closing with each new version released and Exchange 2010’s OWA offering is no exception.

Next on the list of changes are the enhancements made to the Exchange 2010 Management Console (EMC).  Some of these are listed as follows.

Organisational Health Tab

This tab provides you with a quick view of how Exchange is operating in your environment.  We touched upon this in the first article of this series and can be located by clicking on the Microsoft Exchange On-Premises node and running the Gather Organizational Information utility under Actions.  Upon completion you will be provided with the below summary screen;

Organization Summary Exchange 2010

Community and Feedback Tab

The Community and Feedback tab provides links to Exchange-related topics on Microsoft TechNet and new postings from the Exchange team blogs.

Exchange Community and Feedback Exchange 2010

Exchange Help Client (EHC) and PowerShell

This small enhancement provides you with help information directly from TechNet by clicking F1.  A PowerShell command log also records the PowerShell command when you perform a task through the EMC.  A Property dialog box command exposure is also a new feature that displays PowerShell commands including parameters when changing properties of an object.

Role Based Access Control and Exchange Control Panel

For large Exchange Organisations with multiple messaging administrators, Role Based Access Control (RBAC) and  Exchange Control Panel (ECP) are a welcome addition to Exchange 2010.   RBAC allows you to associate permissions against various roles which is also mapped to various tasks in Exchange such as adding mailboxes etc. The ECP console is an administrative web based  tool for delegated administrators such as department administrators and help desk personnel. The ECP console enables these administrators to perform tasks that are delegated to them. These tasks include creating and managing users and groups, defining Unified Messaging and retention policies, changing passwords, and modifying encryption settings.  You can access ECP by browsing to the following URL https://server/ecp and is part of the Client Access role.

ECP Exchange 2010 Exchange Control Panel

With the latest Exchange 2010 Management Architecture, you can now use a single machine and management console to manage multiple 2010 organisations both online and on premises.

Exchange 2010 Storage Architecture

Microsoft continues to improve Exchange’s performance marketing it as an enterprise messaging solution that can easily scale out.  Exchange 2007 went a long way in providing us with enterprise scalability with the introduction of 64 bit only computing breaking the 4GB memory barrier and lowering disk I/O by increasing the page size from 4KB to 8KB.  It also introduced Exchange roles (Hub/Mailbox/CAS/Unified Messaging and Edge) all which could run on separate machines with multiple instances for redundancy and load balancing depending on the role.  So how has Exchange 2010 improved on what Exchange 2007 has to offer?  Below are some of the notable enhancements with regards to Exchange 2010 architecture;

  • *Increased page size from 8KB to 32KB
    *The Store compresses attachments
    *Header data for all mailbox items is stored in a single database table making it more efficient
    *The Store updates Outlook Client views (indexes) only when they're accessed reducing constant background processing

The other notable change with regards to Exchange’s architecture is the removal of storage groups!? What do you mean? No more storage groups? Yep!  and without going into too much detail, below are some of the changes around Exchange 2010, storage and clustering. 

  • *The concept of storage groups is eliminated
    * Single copy clusters and Local Continuous Replication are eliminated and not supported in Exchange 2010
    * Exchange 2010 introduces Database Availability Groups (DAGs), which are groupings of up to 16 servers in which some or all of the databases are marked for replication to one or more other servers.

More detailed technical information can be found in the following TechNet article http://technet.microsoft.com/en-us/library/dd335211%28EXCHG.140%29.aspx.

As you can see there are a plethora of changes and enhancements to Exchange 2010, bringing some valuable functionality to any organisation who chooses to adopt it.  Exchange 2010 improves on Exchange 2007 when it comes to  providing  resiliency, cheaper storage solutions, high availability, improvement in mailbox sizes and increase in performance which will assist any organisation in reducing cost, a welcome in these tough economic times.

Finally, TechNet has some great pre-release documentation that outlines What’s new which can be accessed from here (http://technet.microsoft.com/en-us/library/dd298136(EXCHG.140).aspx). 

Microsoft is also providing a free one year subscription to a number of Exchange 2010 clinics that is invaluable to any Messaging Administrator who wants to learn more about the upcoming release.  You can access these from the Microsoft eLearning Site.  https://www.microsoftelearning.com.

Hope you have enjoyed the 3 part series introducing Exchange 2010.  So what are you waiting for?  Get your hands on the beta which can be downloaded from the Microsoft Download Site and happy testing!  http://www.microsoft.com/DOWNLOADS/details.aspx?familyid=1898ED2C-2F88-48AC-824E-D3D20FAD77D7&displaylang=en

May 13, 2009

Exchange 2010 Beta, Configuration – Part 2/3

| 0 comments |

In our previous post we successfully completed our first Exchange 2010 Install, and after looking back the most difficult part was ensuring all the prerequisites were met for a new Exchange environment .  In today’s post we will continue with our installation with a focus on basic configuration to get mail flowing for internal and external clients, configuring our Anti-Spam agents on the Hub Transport Server (remember we are not utilising the Edge Role in our dev environment) and testing all of this using the brand spanking new Outlook Web Access (OWA).  Just a reminder, the next and last article in this series will scrutinise some of the new features of  Exchange 2010 with OWA being one of them, so stay tuned!

You will notice when you launch Exchange Management Console that  Exchange 2010 has an organizational summary screen which will need to get refreshed when changes are made. To do so, Right Click on Microsoft Exchange On-Premises and select "Gather Organizational Information", this will go ahead and run a couple of scripts and then provide you with an updated summary screen.

Exchange 2010

The quickest method in verifying a successful install (apart from checking the installation logs) is to navigate to the various nodes and ensure that your Mailbox Database is mounted, your OWA site is setup (navigate to the site via /OWA">https://<servername>/OWA) and finally check your Hub Transport Server configuration.  You should notice that the Client and Default Receive connectors have been setup by default.

(Default Mailbox Database in a “Mounted” Status)

Mailbox Database

(Default OWA Web Site)

OWA Default Web Site

(Hub Transport Server Configuration with client and default receive connectors)

Receive Connectors

Let’s now proceed by creating a second Active Directory Account so we can test mail flow between two user accounts (note that the Administrator user has already been created).  To do so, you can create the Active Directory account first in Active Directory Users and Computers and then run the “New Mailbox” wizard or you could create the Active Directory User and Mailbox in the one step using the same “New Mailbox” Wizard.  The "New Mailbox" Wizard is located under Recipient Configuration / Mailbox.

New Mailbox Wizard

Upon completing the wizard you will be presented with 2 users listed under Recipient Configuration / Mailbox.

Recipient configuration

Login using your newly created User Account and Mailbox through OWA and send a test message to the administrator account and CC yourself (this will test the Hub Transport internal routing)

Exchange 2010 OWA

Okay! We have now confirmed that internal traffic is being routed successfully, now for external.  We need to ensure that we have setup our External Domain as an Accepted Domain.  To do so, navigate to the "Organization Configuration / Hub Transport node and click on the Accepted Domains Tab.  Run the New Accepted Domain Wizard under Actions.

Exchange 2010 New Accepted Domain

Your Exchange Server is now authoritative for that domain and you should now be able to receive external emails to that domain.

Let’s now setup an Email Address Policy for our external domain.  Note that a Default Policy is already setup for your internal domain.

Under Organization Configuration / Hub Transport / Email Address Policies Tab, click on New E-Mail Address Policy under Actions.

Exchange 2010 New E-Mail Address Policy

Click Next and specify any conditions, in my case I left the default for all recipient types, click Next, then select Add SMTP, and fill out your Email address naming convention and the specified accepted domain we just created earlier.

Exchange 2010 SMTP Email Address

Exchange 2010

Click Next to apply the policy immediately, and then click New.

Exchange 2010 %g %s

Our newly created Email Address Policy is now listed with a higher priority.

Hub Transport Exchange 2010 

We are now making some good progress and should soon be able to send email to the outside world.  Because we have not setup an Edge Server to handle smtp routing externally, we will need to manually setup a send connector to send directly to the Internet.  Obviously this isn't best practice and one should always setup a separate Edge Server with its notable advantages such as dedicated messaging hygiene especially when run in conjunction with a compatible Virus Scanning API (VSAPI) such as Forefront for Exchange, but for our dev environment this will suffice.  In order to setup a send connector, navigate to, Organization configuration / Hub Transport / Send Connectors and click on New Send Connector under Actions.  Type in a Name and select Internet as the intended use for this send connector and then click Next.

New Send Connector Exchange 2010

Specify your address space, Select Add SMTP Address Space and type * to be able to send to all external domains.

Capture28

Select your preferred Network Settings, Click Next.

Exchange 2010 Send Connector 

Your source server should then automatically populate, click Next.

Exchange 2010 Source Server

That's it, you should now be able to send to external remote domains.  Now I mentioned earlier that we were not going to setup an Edge Role in our dev environment but having said that we can still utilise the Anti-Spam functionality on our multi-role virtual machine, specifically on the Hub Transport Server Role.  TechNet has a great article on enabling this functionality and can be found here.  In summary, the process is as follows;

Launch the Exchange Management Shell and browse to where the Install-AntispamAgents.ps1 is located which by default is under

%system drive%/Program Files\Microsoft\Exchange Server\v14\Scripts folder

install-antispamagents

Type the following command ./install-AntispamAgents.ps1

After the command has successfully run you will need to restart the Microsoft Exchange Transport Service by running the following command;

Restart-Service MSExchangeTransport

You will now notice that there is an Anti-spam tab located under Organization Configuration / Hub Transport with the Anti-spam features listed and enabled.

Exchange Anti Spam Content Filtering

Well, that’s all that is to it.  Basic configuration for an Exchange 2010 server is pretty much identical to Exchange 2007 which is great for Messaging Administrators who have already adopted Exchange 2007.  The last article in this series will outline some of the new Exchange 2010 features with nice pretty pictures outlining these, so stay tuned.

About me..

An IT Pro and Social Media Enthusiast, I became an MCP in 2001 after studying Accounting at University. I have over 10 years experience in designing and implementing systems using Microsoft Technologies with a keen interest in SharePoint, Exchange and Windows.

Blog Archive