Category Archives: Office 365 Grid

Office 365 Grid

Set the RetentionPolicyTag for Deleted Items in #Office365

To change the Retention policy for the deleted items from the default 30 days to lets say 90 days follow this guide

First connected with PowerShell to Exchange Online Service.

a. Install and configure Windows PowerShell.
b. Connect PowerShell to Exchange Online service.

To change the default RetentionPolicyTag for all users run.

Set-RetentionPolicyTag -Identity “Deleted Items” -AgeLimitForRetention 90

To verify all retention policy that are applied to a specific mailbox , please take the following steps.

c. Disable the current RPT applied to the Deleted Item Folders, by running the following  cmdlet using PowerShell.
Set-RetentionPolicyTag “Deleted Items” -RetentionEnabled $false

d. Create a new retention policy tag for the default folder “Deleted Items” by using the following command:

New-RetentionPolicyTag “Exec -Default” -Type All -RetentionEnabled $true -AgeLimitForRetention 90 -RetentionAction DeleteandAllowRecovery

This example creates a retention policy tag for the default folder Deleted Items. When the tag is applied to a mailbox, items in the Deleted Items folder are deleted after 90 day.

After that, create a new retention policy or set up a current policy to link to the newly created retention policy tag.

e. Use PowerShell to apply the retention policy to Deleted Items

Set-Mailbox ” Deleted Items” -RetentionPolicy Execs

The following command applies the retention policy named Execs to Deleted Items:

How I use #Lync and #Office365 as a power user – When I travel

I´we just came back from a one months holiday in Thailand. Or actually I worked for 2 weeks so I only have to use two of those five weeks paid holiday we get as Swedes. But I could stay for double that time, I could work from the beach and 5 star hotels.
And just some weeks before Thailand I were one and a half week in the states for the Microsoft MVP summit and all this time, my customers could reach me without a thought of playing phone tennis trying to find different phone numbers or OOF responses. And the best thing about it, I could work as I was at home in my office but with the view bellow.


This series of posts will tell you all about how to use Office 365, Lync and Enterprise voice when you are traveling international. And some other stuff to about hereworking –working from where you do it the best.

The thing is, thanks to Lync and Office 365 I was able to be as productive as I am when im in my Office. Or I would rather say that I got more done these weeks than if i´d be back home.
I would like to back that up with this article. Tell Your Boss: Unlimited Vacation Actually Increases Productivity.

Working remote or hereworking as I would like to call it, is something that is really easy now with the technology from Microsoft. I got all my documents and notebooks in the cloud stored in Office 365 and SharePoint online. I do note taking in OneNote and that notebook is automatically synced to my personal SharePoint site. Also available from my Windows Phone 7 or iPad. I do some syncing of files between all my devices with Skydrive. My email is in Exchange Online and i use both Lync Online and Lync on-premises.

So how did my setup look like.


I have a Asus Zenbook and a Samsung Series 7 slate with Windows 8 on as my computers (and a iPad2 that I only used 5-10 minutes thanks to the Slate), depending on where I were going to sit and work I did choose the computer that best fit the needs, All files and OneNote were synced via Office 365. I use VPN and Remote Desktop Connection manager and the connection file of course also syncs between the computers.



For my communication I have a unlocked HTC Titan, Plantronics Voyager Pro UC2 and a Jabra UC Voice 250 MS Lync Optimized USB headset.
Thats what I used for phone calls and meetings. Both my PC´s has built in cameras for the video meetings I had in Lync.

Well that’s it for the hardware. Now some tips on how to find a good office for some hours of work.

To start with, there is always coffee shops, Starbucks and they are generally great in the morning, I’m tiered and like to have a coffee to start the day, not so many noisy people in the mornings either, but around lunch and especially after when the moms invade with their kids its usually time to switch place. Plus it don’t feel so good to sit in one coffee shop for eight hours only ordering a coffee.
The great things with many of the coffee shops though is that they have electrical outlets where you can borrow some power, so when you see an outlet rush over there and use it cause you will need it for the afternoon.

After lunch I usually hit the hotels, and preferably the “high so” ones, 5 stars where a coffee is 3 times more expensive than where I had the morning shot. Normally theses places are gorgeous to and have great chairs to work from, but not all has electric…

Some hotels can start playing some music around 3-4pm and have some after work bar or something that could get loud, so its usually time to finish work at this time, or switch seating to some seat away from the people/music. Here is a collection of other tips when hereworking at coffee shops.

However the firsts weeks of my trip where spent in Isaan in the northeast part of Thailand, planting rise Winking smile 


But with great 3G connection I even had some meetings from these fields in the middle of nowhere. And yes, with good quality of voice and video and I couldn’t hear that much latency either, when calling Sweden.

View Larger Map


And I would like to end this post with a link to 9 Tips for Overcoming Jet Lag

The next part will be a bit more technical, showing what settings I did to make this possible.

Migrating Calendar & Contacts for #Office365 kiosk accounts

This weekend is spent with a Office 365 and Exchange Online migration.

And I’m migrating from Kerio Connect to Exchange Online, since this is a IMAP migration I had to find a solution for the calendar and contacts since they are not migrated with the built in IMAP migration tools.

So I found someone in a forum that recommended Transend. And its been ok. I cant say its been a great migration experience but Transend does work if everything else works to 100% and well this is IT, things just never work 100%….

Anyway, I have 50 users on kiosk accounts, and after some digging I found out that Transend uses EWS when it upload the contacts, and guess what? Kiosk accounts don’t allow that, so there wont be any contacts or calendar for the Kiosk users if you are migrating from anything else than Exchange.

And I cant export them to PST and connect Outlook and migrate them that way.

Does anyone out there know of a smart way to migrate the calendar and contacts for kiosk users?

Troubleshoot IM in OWA – #Lync #Office365

This is a great article with some troubleshooting steps and instructions on how to check your settings for the Lync instant messaging feature in Exchange Online OWA.

Some of these steps can also be applied to the on-premises versions since its basically the same PowerShell commands.

View the Outlook Web App policies available to your organization

Run the following command:

Get-OwaMailboxPolicy | Format-Table Identity

The command returns a list of the Outlook Web App policies that you can change. In the list of results, notice that each mailbox plan has an associated Outlook Web App policy. This means that users who are assigned different mailbox plans can also have different Outlook Web App settings. For example, you can disable instant messaging for users assigned the GalDisabledMailboxPlan, and enable instant messaging for the default mailbox plan.

View or verify instant messaging settings

Run the following command:

Get-OwaMailboxPolicy OwaMailboxPolicy-DefaultMailboxPlan | Format-List *instant*

Using the wildcard character * returns all settings that contain the term “instant“.

Swedish #Office365 user group meeting this Friday

Hi, just a quick reminder that we will host a Office365 user group meeting this Friday (09-13) at Microsoft in Akalla. We will also set up a Lync online session for the folks that cant join us Live.

Please see the LinkedIn group for the details

Troubleshooting dirsync and UPN #Office 365

One of my customers added a new group of users that used their own domain suffix which was not intended to be used in Office 365 from the start. And when we first enabled dirsync it was probably not even possible to have multiple domains but now we wanted these users enabled for Office 365 as well.

And it worked just fine for all but two users and I think that these two users was probably syned before we enabled –SupportMulitpleDomain ( to enable support for multiple domains after you have already enabled dirsync see: )

So when we looked at the user object one had the domain and the other had But they both really should be on the suffix.

And yes of course, we had double and triple checked the AD and ran through manual synchronizations and forced a full re-syncs by changing the registry as seen below.

Open the Registry Editor and browse to the key:
Search for the FullSyncNeeded value and set it to 1

And then launch the:
%programfiles%\Microsoft Online Directory Sync\DirSyncConfigShell.psc1

And run the following command to start a full resync:

So after a quick chat with the support in a service request we decided to stop dirsync and remove the account from the Office 365 tenant manually and then do a full resync.

So to disable dirsync follow these steps from

  1. Install the local Windows PowerShell cmdlets. To do this, visit the following Microsoft website:Use Windows PowerShell to manage Office 365
  2. Start the Microsoft Office Online Services Module for Windows PowerShell.
  3. Disable directory synchronization. To do this, type the following cmdlet, and then press Enter:Set-MsolDirSyncEnabled -EnableDirSync $false
  4. Verify that directory synchronization is fully disabled by using Windows PowerShell. To do this, run the following cmdlet periodically:(Get-MSOLCompanyInformation).DirectorySynchronizationEnabled

    This command will return True or False. Continue to run this cmdlet periodically until it returns False, and then go to step 5.
    Note It may take 72 hours for the deactivation to be completed. The actual time depends on the number of objects that are in your Office 365 subscription account.


  5. Try to update an object to verify that you can delete the object.
  6. Delete the object by using Windows PowerShell or by using the Office 365 portal. To view the cmdlet documentation, visit the following Microsoft website:Windows PowerShell cmdlets for Office 365 (
  7. To re-enable directory synchronization, run the following cmdlet:Set-MsolDirSyncEnabled -EnableDirSync $true

But I actually had some troubles with step 7.So I had to enable dirsync manually from the admin portal and wait for some time and after that all was fine again.




When I deactivated dirsync I was able to run the following command on the user that was in the

Set-MsolUserPrincipalName -UserPrincipalName -NewUserPrincipalName

And that command changed the upn on the first user.

But I when I tried on a user that was in a ADFS federated domain I was not able to run the same command on her account? So what I did was to simply delete it and when I later turned Dirsync back on it was synced back up as a “new” account and all is now back to normal operations again.



Just a reminder to myself, if you just want to change the UPN name, you always have to go via the domain first, you cant just change from one Federated domain to the other. So try to remember this next time ok…


Dirsync for x64 servers in #Office365

Ok so put on your party hats and lets celebrate


Because it looks like 64 bit support for Dirsync just sneaked out from the farm.


Upgrading from 32-bit directory synchronization tool

(From )

To upgrade your 32-bit installation of the directory synchronization tool, you must first uninstall it, and then install the 64-bit tool on a new computer.

Although the 32-bit instance of the directory synchronization tool is removed, the overall state of the objects in your on-premises and cloud directories, respectively, is preserved. When you install and configure your 64-bit instance of the directory synchronization tool, it finds and matches objects in the cloud with on-premises objects. However, the 64-bit instance of the tool will not find and match objects in the cloud if on-premises object deletions occurred when the 32-bit instance of the directory synchronization tool was offline.

Therefore, you must minimize changes to your on-premises objects during the upgrade to the 64-bit instance of the directory synchronization tool.

  1. On the computer on which the Directory Synchronization tool is installed, open the Control Panel, select Add and Remove Programs, and then uninstall the Directory Synchronization tool.


    If a synchronization session is in progress, a warning message appears when you try to remove the Directory Synchronization tool. If you receive this warning, wait until synchronization is complete, and then repeat this step.

  2. Install the 64-bit version of the Directory Synchronization tool installation file on another computer. To do this, sign in to the Office 365 portal, click Admin in the header, click Users under Management in the left pane, click Set up in the Users pane, select Windows 64-bit version, and then click the Download button for step 4: Install and configure the Directory Synchronization tool.
  3. On the last page of the installation program, select Start Configuration Wizard now, and then click Finish.
    The Microsoft Online Services Directory Configuration Wizard starts.