While prepping for one of my sessions @ TechEd Berlin on managing and administering Exchange 2010, I was looking for a demo to illustrate the changes introduced with Remote Powershell  when importing and exporting files. That's when I stumbled into the Exchange Management Shell cmdlet Import-RecipientDataProperty, which is described in the following TechNet article: Import-RecipientDataProperty.

So here are the steps to get a picture uploaded into Active Directory, in this example my user Ilse doesn't have a picture yet

Step 1. Get a picture

You need a JPEG file, limited in size to 10 kilobytes!

Step 2. Run the Exchange Management Shell cmdlet Import-RecipientDataProperty

Run the Exchange Management Shell cmdlet to upload the picture. Running it will populate Active Directory with the picture, more specifically the attribute called thumbnailPhoto will be populated. Make sure this attribute is replicated to the Global Catalog (big thank you to Astrid for helping me out with this one :-)) .

Before running the cmdlet, the attribute doesn't have a value:

 Check if the attribute is replicated to the Global Catalog, by using for example the Schema Snap-In:

Run the following cmdlet:

Few remarks:

- there is no need to refer to a UNC path, you can locate the file anywhere

- remember the limit of 10KB!!

After running this, Active Directory will be populated:

And after restarting Outlook, the picture will be there :-)

-Ilse

Follow-up: If you want to know if this will work with Exchange 2003-Exchange 2007, click this link:

http://blogs.technet.com/ilvancri/archive/2010/01/08/follow-up-import-recipientdataproperty.aspx

So many new features have been included in Exchange 2010, that it would indeed take me more than days to talk about all of these, but there are so many very nice features that you should keep in mind when thinking about Exchange 2010, and one is these is the new built-in cmdlet "Add-MailboxFolderPermission".

What's this: Add-MailboxFolderPermission

Looking at the description posted on TechNet this cmdlet enables you to "manage folder-level permissions for all folders within a user's mailbox",  meaning you can use this cmdlet to delegate any of the following roles to any mailbox folder for any mailbox-enabled user in your organization, given you have sufficient permissions :-)

(Source = Add-MailboxFolderPermission)

• ReadItems   The user has the right to read items within the specified folder.
  
• CreateItems   The user has the right to create items within the specified folder.
  
• EditOwnedItems   The user has the right to edit the items that the user owns in the specified folder.
  
• DeleteOwnedItems   The user has the right to delete items that the user owns in the specified folder.
  
• EditAllItems   The user has the right to edit all items in the specified folder.
  
• DeleteAllItems   The user has the right to delete all items in the specified folder.
  
• CreateSubfolders   The user has the right to create subfolders in the specified folder.
  
• FolderOwner   The user is the owner of the specified folder. The user has the right to view and move the folder and create subfolders. The user can't read items, edit items, delete items, or create items.
  
• FolderContact   The user is the contact for the specified public folder.
  
• FolderVisible   The user can view the specified folder, but can't read or edit items within the specified public folder.
  

The AccessRights parameter also specifies the permissions for the user with the following roles, which are a combination of the rights listed previously:

• None   FolderVisible
  
• Owner   CreateItems, ReadItems, CreateSubfolders, FolderOwner, FolderContact, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
  
• PublishingEditor   CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
  
• Editor   CreateItems, ReadItems, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
  
• PublishingAuthor   CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, DeleteOwnedItems
  
• Author   CreateItems, ReadItems, FolderVisible, EditOwnedItems, DeleteOwnedItems
  
• NonEditingAuthor   CreateItems, ReadItems, FolderVisible
  
• Reviewer   ReadItems, FolderVisible
  
• Contributor   CreateItems, FolderVisible
  

The following roles apply specifically to calendar folders:

• AvailabilityOnly   View only availability data
  
• LimitedDetails   View availability data with subject and location
  

The permissions you need in order to be able to do so, are any of the followin built-in management roles (as stated here), there is no need to have been granted full mailbox access prior to being able to change those folder permissions (!): Organization Management, Recipient Management, Help Desk.

Let's have a look at an example. Here are the permission settings for my test mailbox Ilse, and as you can see, these are the default settings, without previous changes:

Can we get this information using the power of the (Remote) Exchange Management Shell? Yes, by using the cmdlet Get-MailboxFolderPermission, as can be seen in the example below, when running Get-MailboxFolderPermission ilsevancriekinge@exchange.local:\Calendar

And then we can run the following cmdlet to add User7 with the permission of Editor:

Add-MailboxFolderPermission -Identity ilsevancriekinge@exchange.local :\Calendar -User user7@exchange.local -AccessRights editor

And when checking with Microsoft Office Outlook, it's clear the permissions have been set:

-Ilse

Only two days after being able to download the newest release of Exchange 2010, here is the Exchange 2010 Storage Calculator :-)

For more information, one place, the Ms Exchange Team blog site! Here's the link:

Exchange 2010 Mailbox Server Role Requirements Calculator

Happy calculating ;-)

-Ilse

Agenda

13:00 - 13:30 Registration and Welcome

13:30 - 14:00 Introduction in Exchange 2010

In a time, when your organization requires its communication tools to be cost-effective and flexible, Microsoft Exchange Server 2010 enables you to achieve new levels of reliability and performance by delivering features that can simplify your administration help, protect your communications, and delight your users by meeting their demands for greater business mobility.

In this presentation, we will introduce you to Exchange Server 2010 -- the cornerstone of Microsoft’s Unified Communications solution -- and highlight how this latest release can help you realize the new efficiency, by enabling you, with less, to do more.

14:00 - 15:00 Flexible and Reliable Messaging Infrastructure with Exchange 2010

IT organizations are looking for ways to provide a more reliable messaging infrastructure, while reducing their costs and streamlining administration. Using Exchange 2010 is a great way to achieve those goals. In this presentation,  We will explore in more details how Exchange 2010 gives you the flexibility to provide a Reliable Messaging Infrastructure which meets the needs of your organization at a lower cost.

15:00 - 15:15 Break

15:15 - 16:15 Information Protection and Control

Based on customer feedback, we focused on e-mail protection and compliance as one our 4 key investment areas in Exchange 2010.  In this session we will show you how Exchange 2010 can help reduce the complexity of this increasingly important workload.  You will get acquainted with using the improved Transport Rules, Moderated Mailboxes, MailTips, and how Information Rights Management is done in Exchange 2010.

16:15 - 17:30 Migration & BPOS

We will walk you through the process for introducing Exchange 2010 servers into an Exchange 2003/2007 organization.  You will learn about the prerequisites, steps required, and the impact to client access for MAPI, Outlook Anywhere, OWA, ActiveSync, and POP/IMAP clients after the upgrade has occurred. In addition, we will introduce you the features provided for Exchange in the cloud, as part of BPOS.

Speaker: me

08/12/2009 - Brussels: http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032434076&Culture=en-US

09/12/2009 - Gent: http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032434077&Culture=nl-BE

10/12/2009 - Mons: http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032434079&Culture=fr-BE

-Ilse 

There are a lot of question going around when it comes to OCS 2007 R2 and licensing. In this post I'll try to give an overview of which licenses are required :-)

In the end, it all boils down to three things, meaning, you may need a license for:

1. Using a client software to gain access to a service provided by the Office Communications Server (= clientsoftware license)

2. Gaining access to the service provided by the Office Communications Server (= client access license)

3. The sever offering the Office Communications Server services (= server license)

So let's have a look at these three different licenses you need...

1. Client Software License

You need a license for using Microsft Office Communicator, which is available as both a stand-alone product, and is also included in Microsoft Office Pro Plus 2007 and Microsoft Office Enterprise 2007.

If you have a valid Server License, you are allowed to use the following Client Software (you don't need to buy a Client Software license for using these Client Software programs)

• Office Communicator Web Access 2007 R2
• Office Communicator Mobile for Java 2007 R2
• Office Communicator Mobile for Windows 2007 R2
• Office Communications Server 2007 R2 Group Chat Conolse
• Office Communications Server 2007 R2 Attendant Console
• Office Live Meeting Console

2. Client Access License

You need a license for every user or every device using any of the services provided by Office Communications Server. There are two type of Client Access Licenses (CAL), being Standard and Enterprise. The choice of standard/enterprise CAL will depend on which features you want to use:

Office Communications Server 2007 R2 STANDARD CAL =

• IM/Presence/Chat 
• IM/Presence
• Group IM
• Peer-to-Peer Voice and Video
• File Transfer
• Group Chat

Office Communications Server 2007 R2 ENTERPRISE CAL = STANDARD CAL +

• Conferencing 
• Web Conferencing
• Multiparty collaboration
• Application sharing
• Desktop Sharing
• Audio Conferencing
• Voice
• Call Routing
• User Call Management
• Remote Call Control
• Voice Media on Softphone
• Team Call
• Delegation
• Response Group
• Single-Number Reach

 In OCS 2007 R2, you do NOT need to provide a CAL for:

• An external (anonymous) user attending an OCS 2007 R2 Web conference
• Users receiving a call from an extension hosted on the OCS 2007 R2 server
• Non OCS 2007 R2 users placing a call to an extension hosted on the OCS 2007 R2 server

3. Server License

There are two types of Server licenses in OCS 2007 R2, being Standard and Enterprise.

The following OCS 2007 R2 OCS Server Roles require a server license

• OCS 2007 R2 Front End Server: Standard or Enterprise (Using Enterprise you can introduce High Availability (!))
• OCS 2007 R2 Edge Server role: Standard or Enterprise

The following OCS 2007 R2 OCS Server Roles, Standard Edition, can be installed without requiring a Server license for the role itself, BUT requiring a valid Front-End Server license (Standard or Enterprise) in your OCS 2007 R2 environment:

• Monitoring Server role
• Director Server role
• Mediation Server role
• Archiving Server role
• Web Components Server role (including Communicator Web Access)
• Group Chat Server role

Other Offerings

• Public IM Connectivity
1. A PIC License is no longer required for federation with Windows Live. Customers qualify for federation with Windows Live if they have Office Communications Server 2007 R2 Standard CAL or active SA on their current LCS/OCS license
2. A PIC License will no longer be required for federation with American Online (AOL).  Customers qualify for federation with AOL if they have Office Communications Server 2007 R2 Standard CAL or active Software Assurance on their current LCS/OCS license. 
3. Customers who want Yahoo! federation will continue to purchase PIC licenses.  The price of PIC will be reduced by 50%, effective October 1, 2009, to reflect this change. 
• Microsoft Office Communications Server 2007 R2 XMPP is available at no cost

Need additional information?

Have a look at one of these links:

• http://blogs.technet.com/ucedsg/archive/2009/07/01/windows-live-msn-hotmail-pic-licensing-no-longer-needed-for-federation.aspx
• http://blogs.technet.com/ucedsg/archive/2009/04/08/licensing-change-for-ocs-r2.aspx
• http://communicationsserverteam.com/archive/2009/10/01/588.aspx
• http://www.microsoft.com/communicationsserver/en/us/pricing-licensing.aspx
• http://www.microsoftvolumelicensing.com/ProductPage.aspx?pid=354

-Ilse