There are two new capabilities in the Microsoft 365 Business suite that significantly enhance the end-user and device management experience. More information also in this blogpost. The first is that it is now possible to use Azure AD Connect, so you can synchronize your users, groups and password hashes to the cloud. This way you can have a single-sign on experience and additional capabilities such as self service password reset. All the capabilities that are in Microsoft 365 Business compared to Enterprise can be found in the Microsoft 365 Business Service Description.

The second is that it is now possible to register your Windows 10 devices with Azure AD (called Azure AD Hybrid Join). This makes it possible to do co-management on these devices. Co-management enables you to concurrently manage Windows 10 devices by using both Configuration Manager and Intune. It’s a solution that provides a bridge from traditional to modern management and gives you a path to make the transition using a phased approach. More information can be found here: https://docs.microsoft.com/en-us/sccm/core/clients/manage/co-management-overview

Note that the words Azure AD Hybrid joined imply that you are both joined to on-premises AD and Azure AD, but technically you are actually still joined only to on-premises AD. Instead your device will be registered (and not joined) in Azure AD. More information here: https://docs.microsoft.com/en-us/azure/active-directory/device-management-introduction

Setting it all up

You can set this all up by first synchronizing your Active Directory with Azure Active Directory, followed by registering the Windows 10 devices within Azure AD. After registering you can enable these devices for mobile device management in Intune.

In my steps below I made the following assumptions:

• First off, your devices needs to be joined to your on-premises Active Directory.
• Secondly, all your devices are running the latest versions of Windows 10.
• Finally, you already have configured and set up Azure AD Connect with password hash sync enabled, so your on-premises users will also exist in Azure AD (see screenshot below).

Note that if you are doing OU filtering, don't forget to include the computer accounts as well, as these are required for Hybrid Azure AD Join.

Once that has been set up, you go back to Azure AD Connect and configure it to setup Hybrid Azure AD Join as outlined in this article:

https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-azure-ad-connect-device-options

Select Configure Hybrid Azure AD join.

Select your Authentication Service and enter your Enterprise Admin credentials.

Select Windows 10 or later domain-joined devices.

Once finished, you should check some of the post configuration tasks that might be required as outlined in this article: https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-azure-ad-connect-hybrid-azure-ad-join-post-config-tasks

From this point onwards:

• All domain-joined devices running Windows 10 Anniversary Update and Windows Server 2016 automatically register with Azure AD at device restart or user sign-in.
• New devices register with Azure AD when the device restarts after the domain join operation is completed.
• Devices that were previously Azure AD registered (for example, for Intune) transition to “Domain Joined, AAD Registered”; however it takes some time for this process to complete across all devices due to the normal flow of domain and user activity.

Verify Joined Devices

Make sure you have installed the PowerShell module for Azure AD as outlined here: https://docs.microsoft.com/en-us/powershell/azure/install-msonlinev1?view=azureadps-2.0

Connect to the tenant using PowerShell, follow by the commandlet Get-MsolDevice. This should list all de devices that are registered in Azure AD.

If it doesn't, please check this troubleshooting guide for tips: https://docs.microsoft.com/en-us/azure/active-directory/device-management-troubleshoot-hybrid-join-windows-current

Summary

With Microsoft 365 Business it is now possible to use Azure AD Connect to synchronize your local Active Directory information into Azure and is a great way to enhance the end-user experience. This capability also unlocks Hybrid Azure AD Join, which will provide a bridge from traditional to modern device management with Microsoft Intune.

If you find any errors in this article, please let me know. Hope this helps!

-Andre

When to use the OneDrive for Business client

So when should you use the OneDrive for business client then? I could come up with the following reasons:

• You are working regularly without an internet connection and need to be able to view and/or edit documents while offline.
  
  
• You are using very large files, so having these files offline speeds up the process for opening and/or editing them.

Sometimes I also get the argument that people want to be able to work the way as they did before by just browsing through files and folders and don't want to go to the browser for finding, reading and editing their documents. I can understand this way of thinking, as people have been working with file shares for 15-20 years. But let me try to explain why I think they are arguable (and I'll show you more info in the sections below):

• You actually can browse, open and save documents through folders without using the browser and without having the content synchronized locally.
  
  
• You actually can open up documents that you opened up before, with just two clicks.
  
  
• If people really want to remain working exactly the way they worked before, it probably also means that they don’t see the value of changing some of their habits. Showing the end-users “what’s in it for me?” really helps them to understand why change is sometimes inevitable in order to improve things. Like Frederick Douglass once said: “If there is no struggle, there is no progress”.

Below are some tips that can help those users be more productive while keeping the end-user experience similar to the one they are used to.

Browsing through folders

Let's start off by talking about browsing through folders without having to use your browser.

1. In a document library, click on the button Open in Explorer in the Library menu of the Ribbon
   
   
   
2. Now you will see the content so the document library in your windows explorer. The means you can actually create folders here, copy/paste and drag and drop files, just as you would on a normal network share.
    
   
   
3. Now you can actually drag and drop the folder icon (left mouse button) from the address bar onto the favorites section on the left hand side of the windows explorer. This way you can instantly open the location in your windows explorer, but also from within the office “Save as” and “Open” dialog to quickly open and save documents.
   
   
   
   
   
   
   Note that you can you can also drag and drop the folder icon from the address bar onto the desktop is that has your preference or map a network drive as outlined in this kb article.

Open documents with two clicks

As mentioned before it is actually possible to quickly open up document that you have been working on before. Below are the steps on how to accomplish that:

1. Make sure you have pinned your frequently used Office applications onto the Windows taskbar.
    
   
   
2. Now, just right click on one of the pinned Office applications. In this instance Word and notice that you will see the 10 last saved documents. Click on any of the documents to instantly open it without having to open any browser windows.
    
   
   
3. By default, you will only see the last 10 presentations, but you can increase this by right clicking on the Windows taskbar and choosing Properties. Here go to the tab Jump Lists and increase the amount to a higher number (20 or 30 might be sufficient).
    
   
   
4. I have to say, I use this feature all the time and is a real time-saver for me. No more figuring out where my documents are located as I can instantly continue with the files I’ve been working on before.

Using the browser

For basic operations such as opening and saving Office files, the above methods can come in real handy, but ultimately the browser will give you a much richer experience. In the browser you can:

• Instantly preview Office documents without having to open them in the client. This will give you a much faster and more relevant experience without leaving the context of what you were doing.
   
  
  
• Use multiple views of Office documents, e.g. grouped by author, or filtered by date. Using views will increase the speed of finding and opening relevant information.
   
  
  
• Use metadata which will enrich and classify your documents. By using metadata you will increase relevancy of Office documents and make sure your Office documents can be found more easily.
   
  
  
• You can open and edit Office documents in the browser. This will increase the speed of opening Office documents as no download is required and the data is purely rendered in the browser. This method of opening Office documents will also make sure that if someone does not have office installed, they can still open and edit the Office documents in the browser. This browser can be browsers like Safari, Firefox, Chrome, Opera and of course Internet Explorer. So this will also work on IPads, Android tablets and Chromebooks.
   
  
  
• You can view, compare and restore versions of Office Documents. If you have the appropriate permissions you can view the different versions of an Office document, compare it with other version and even restore to an earlier version of the document.
   
  
  
• Search and find document very easily. When searching in the browser, you will get results back from all Office documents within your organization, results will be very relevant due to a highly intelligent search engine and the search results can be easily filtered on metadata such as the author of a document, the modified date. On the left hand side you see that filters have been set on the type of file (PowerPoint) and on the Author of the file (Paul Vermeulen). If you hover over the result, you instantly see the preview of the deck, so you can instantly determine if this is the correct file your are looking for.
  

There are definitely more advantages of having the browser experience over the file share experience, but these are just some of most obvious ones.

Summary

You can work with Office documents in SharePoint or OneDrive without using of the OneDrive for Business client. A common misconception is that you require the client to be installed, but without the client you can still be very productive and have a similar file share experience that users have been using for decades. For basic operations such as opening and saving Office files, the methods described in this article can come in real handy, but ultimately the browser will give you the best experience.

---

Still I often receive questions from partners around the differences between OneDrive and OneDrive for Business. As I had some time left during the holidays (and wanted to activate the right side of my brain :)), I figured to create the video below.

[View:https://youtu.be/Fww5uP-x6hY:550:0]

* Update 4-6-2015: Added link to blog/tool from Bill Baer

* Update 15-4-2015: Added MigrationWiz tool and fixed max amount of docs in library from 5 to 30 million

* Update 9-12-2014: Added O365Uploader tool (thx Jos)

* Update 3-12-2014: Added LepideMigrator tool (thx Tom)

* Update: Changed naming from SkyDrive Pro to OneDrive for Business

* Update: Removed "Note that this functionality is only available in SharePoint on-prem", as this is in Online as well.

* Update: Changed 100 Gig to 1000 Gig (1 TerraByte)

* Update: Added The Fullsuite 3rd party migration tool (thx Menno)

* Update: Added additional 3rd party tools and made some small corrections

---

It has been a while since I created a blog post, but recently I received a lot of questions and requests for advice on how to migrate file shares to SharePoint and use OneDrive for Business (ODFB). So I figured to create a blog post with the things you need to consider as a Small and Medium Business (SMB) partner when you are planning to migrate file share content into SharePoint and want to make use of ODFB for synchronizing the SharePoint content offline.

Note: that these steps are both valid for SharePoint 2013 on-premises (on-prem) and SharePoint Online (SPO).

Step 1 – Analyze your File Shares

As a first step, try to understand the data that resides on the file shares. Ask yourself the following questions:

• What is the total size of the file share data that the customer wants to migrate?
• How many files are there in total?
• What are the largest file sizes?
• How deep are the folder structures nested?
• Is there any content that is not being used anymore?
• What file types are there?

Let me try to explain why you should ask yourself these questions.

Total Size

If the total size of the file shares are more that the storage capacity that you have on SharePoint, you need to buy additional storage (SPO) or increase your disk capacity (on-prem). To determine how much storage you will have in SPO, please check the Total available tenant storage in the tables in this article. Another issues that may arise is that in SharePoint is that you reach the capacity per site collection. For SPO that is 1000 Gigabyte (changed from 100 GB to 1 TB), for on-premises the recommended size per site collection is still around 200 Gigabyte.

So, what should I do when my customer has more than 1000 Gigabyte?

• Try to divide the file share content over multiple site collections when it concerns content which needs to be shared with others.
• If certain content is just for personal use, try to migrate that specific content into the personal site of the user.

How Many Files

The total amount of files on the file shares is important as there are some limits in both SharePoint as well as ODFB that can result in an unusable state of the library or list within SharePoint but you also might end up with missing files when using the ODFB client.

First, in SPO we have a fixed limit of 5000 items per view, folder or query. Reasoning behind this 5000 limit boils all the way down to how SQL works under the hood. If you would like to know more about it, please read this article. In on-prem there is a way to boost this up, but it is not something we recommend as the performance can significantly decrease when you increase this limit.

Secondly for ODFB there is also a 5000 limit for synchronizing team sites and 20000 for synchronizing personal sites. This means that if you have a document library that contains more that 5000 items, the rest of the items will not be synchronized locally.

There is also a limit of 30 million items within a document library, but I guess that most customer in SMB won’t reach that limit very easily.

So, what should I do if my data that I want to migrate to a document library contains more than 5000 items in one folder?

• Try to divide that amount over multiple subfolders or create additional views that will limit the amount of documents displayed.

But wait! If I already have 5000 items in one folder, doesn’t that mean that the rest of the other document won’t get synchronized when I use ODFB?

Yes, that is correct. So if you would like to use ODFB to synchronize document offline, make sure that the total amount of documents per library in a team site, does not exceed 5000 documents in total.

So, how do I fix that?

• Look at the folder structure of the file share content and see if you can divide that data across multiple sites and/or libraries. So if there is a folder marketing for example, it might make more sense to migrate that data into a separate site anyway, as this department probably wants to store additional information besides just documents (e.g. calendar, general info about the marketing team, site mailbox etc). An additional benefit of spreading the data over multiple sites/libraries is that it will give the ODFB users more granularity about what data they can take offline using ODFB. If you would migrate everything into one big document library (not recommended), it would mean that all users will need to synchronize everything which can have a severe impact on your network bandwidth.

Largest File Sizes

Another limit that exists in SPO and on-prem is the maximum file size. For both the maximum size per file is 2 Gigabyte. In on-prem the default is 250 MB, but can be increased to a maximum of 2 Gigabyte.

So, what if I have files that exceed this size?

• Well, it won’t fit in SharePoint, so you can’t migrate these. So, see what type of files they are and determine what they are used for in the organization. Examples could be software distribution images, large media files, training courses or other materials. If these are still being used and not highly confidential, it is not a bad thing to keep these on alternative storage like a SAN, NAS or DVDs. If it concerns data that just needs to be kept for legal reasons and don’t require to be retrieved instantly, you might just put these on DVD or an external hard drive and store them in a safe for example.

Folder Structures

Another important aspect to look at on your file shares is the depth of nested folders and file length. The recommended total length of a URL in SharePoint is around 260 characters. You would think that 260 characters is pretty lengthy, but remember that URLs in SharePoint often has encoding applied to it, which takes up additional space. E.g. a space is one character but in Unicode this a %20, which takes up three characters. The problem is that you can run into issues when the URL becomes to large. More details about the exact limits can be found here, but as a best practice try to keep the URL length of a document under 260 characters.

So, what if I have files that will have more than 260 characters in total URL length?

• Make sure you keep your site URLs short (the site title name can be long though). E.g. don’t call the URL Human Resources, but call it HR. If you land on the site, you would still see the full name Human Resources as Site Title and URL are separate things in SharePoint.
• Shorten the document name (e.g. strip of …v.1.2, or …modified by Andre), as SharePoint has versioning build in. More information about versioning can be found here.

Idle Content

When migrating file shares into SharePoint is often also a good momentum to clean up some of the information that the organization has been collecting over the years. If you find there is a lot of content which is not been accessed for a couple of years, what would be the point of migrating that data it to SharePoint?

So, what should I do when I come across such content?

• Discuss this with the customer and determine if it is really necessary to keep this data.
• If the data cannot be purged, you might consider storing it on a DVD or external hard drive and keep it in a safe.
• If the content has multiple versions, such as proposal 1.0.docx, proposal 1.1.docx, proposal final.docx, proposal modified by Andre.docx, you might consider just moving the latest version instead of migrating them all. This manual process might be time consuming, but can safe you lots of storage space in SharePoint. Versioning is also something that is build into the SharePoint system and is optimized to store multiple versions of the same document. For example, SharePoint only stores the delta of the next version, saving more storage space that way. This functionality is called Shredded Storage.

Types of Files

Determine what kind of files the customer is having. Are they mainly Office documents? If so, then SharePoint is the best place to store such content. However, if you come across developers code for example, it is not a good idea to move that into SharePoint. There are also other file extensions that are not allowed in SPO and/or on-prem. A complete list of blocked file types for both SPO and on-prem can be found here.

So, what if I come across such file extensions?

• Well, you can’t move them into SharePoint, so you should either ask yourself, do I still need these files? And if so, is there an alternative storage facility such as a NAS, I can store these files on? If it concerns developer code, you might want to store such code on a Team Foundation Service Server instead.

Tools for analyzing and fixing file share data

In order to determine if you have large files or exceed the 5000 limit for example, you need to have some kind of tooling. There are a couple of approaches here.

• First off, there is a PowerShell script that has been pimped up by a German colleague Hans Brender, which checks for blocked file types, bad characters in files and folders and finally for the maximum URL length. The script will even allow you to fix invalid characters and file extensions for you. It is a great script, but requires you to have some knowledge about PowerShell. Another alternative I was pointed at is a tool called SharePrep. This tool does a scan for URL length and invalid characters. There is also another great tool from colleage Bill Baer which is called filechecker.exe and can be found on his blog.
• Secondly there are other 3rd party tools that can do a scan of your file share content such as Treesize. However such tools do not necessarily check for the SharePoint limitations we talked about in the earlier paragraphs, but at least they will give you a lot more insight about the size of the file share content.
• Finally there are actual 3rd party migration tools that will move the file share content into SharePoint, but will check for invalid characters, extensions and URL length upfront. We will dig into these tools in Step 2 – Migrating your data.

Step 2 – Migrating your data

So, now that we have analyzed our file share content, it is time to move them into SharePoint. There are a couple of approaches here.

Open with Explorer

If you are in a document library you can open up the library in the Windows Explorer. That way you can just do a copy and paste from the files into SharePoint.

But, there are some drawbacks using this scenario. First of all, I’ve seen lots of issues trying to open up the library in the Windows Explorer. Secondly, the technology that is used for copying the data into SharePoint is not very reliable, so keep that in mind when copying larger chunks of data. Finally there is also drag & drop you can use, but this is only limited to files (no folders) and only does a maximum of 100 files per drag. So this would mean if you have 1000 files, you need to drag them 10 times in 10 chunks. More information can be found in this article. Checking for invalid characters, extensions and URL length upfront are also not addressed when using the Open with Explorer method.

Pros: Free, easy to use, works fine for smaller amounts of data

Cons: Not always reliable, no metadata preservations, no detection upfront for things like invalid characters, file type restrictions, path lengths etc.

OneDrive for Business

You could also use ODFB to upload the data into a library. This is fine as long as you don’t sync more than 5000 items per library. Remember though that ODFB is not a migration tool, but a sync tool, so it is not optimized for large chunks of data to be copied into SharePoint. Things like character and file type restrictions, path length etc. is on the list of the ODFB team to address, but they are currently not there.

The main drawbacks of using either the Open in Explorer option or using ODFB is that when you use these tools, they don’t preserve the metadata of the files and folder that are on the file shares. By this I mean, things like the modified date or owner field are not migrated into SharePoint. The owner will become the user that is copying the data and the modified date will be the timestamp of the when the copy operation was executed. So if this metadata on the files shares is important, don’t use any of the methods mentioned earlier, but use one of the third party tools below.

Pros: Free, easy to use, works fine for smaller amounts of data (max 5000 per team site library or 20000 per personal site)

Cons: No metadata preservations, no detection upfront for things like invalid characters, file type restrictions, path lengths etc.

PowerShell

A new migration API has been released back in May. The new API allows you to migrate content much quicker as it first uploads the content to Azure storage and from there imports it into SharePoint Online without being subject to CSOM throttling. With the new API we also released a preview of some PowerShell commandlets that will allow you to migrate content from fileshares into SharePoint Online using the new API. You can sign up for the preview via https://aka.ms/spomigrationpreview.

More details about the commandles can be found in this session on the Ignite 2015 event:
https://channel9.msdn.com/Events/Ignite/2015/BRK3153

3rd party tools

Here are some of the 3rd party tools that will provide additional detection, fixing and migration capabilities that we mentioned earlier:

• http://www.thinkscape.com/SharePoint-Online-File-Migration-Tool
• http://en.share-gate.com
• http://www.metalogix.com/Products/Content-Matrix.aspx
• http://www.syntergy.com/products/sharepoint/more/bulkloader (now Metalogics)
• http://axceler.com/products/controlpoint-sharepoint-products/sharepoint-migration/index
• http://www.avepoint.com/file-system-to-sharepoint-migration-docave
• http://www.sharepointmigrator.com/office365-migration.html
• http://www.quest.com/migrator-for-sharepoint-online
• http://www.metavistech.com/product/office-365-suite
• http://www.metavistech.com/product/information-manager-power-user-edition
• http://www.tzunami.com/products/td-office-365-migration
• http://store.bamboosolutions.com/pc-36-1-list-bulk-import-release-15.aspx
• http://www.vyapin.com/products/sharepoint-migration/dockit/sharepoint-migration-tools.htm
• http://www.layer2.de/en/products/Pages/Cloud-Connector-for-SharePoint-2010-Office365.aspx
• http://www.proventeq.com/migration-to-sharepoint-2013
• http://www.xavor.com/it-services/sharepoint/migrator-for-sharepoint-online
• http://www.messageops.com/software/office-365-tools-and-utilities/office-365-sharepoint-migrator
• http://www.thefullsuite.com/
• http://www.lepide.com/lepidemigratordocuments
• http://www.lieben.nu/numb3rs/?page_id=51
• http://software.dell.com/products/migration-suite-for-sharepoint
• https://www.bittitan.com/products/migrationwiz/document-migration
  

The list above is in random order, where some have a focus on SMB, while other more focused on the enterprise segment. We can’t speak out any preference for one tool or the other, but most of the tools will have a free trial version available, so you can try them out yourself.

Summary

So, when should I use what approach?

Here is a short summary of capabilities:

¹This depends on the capabilities of the 3rd party tool.
Note that in the table above, I have not included the new PowerShell commandlets yet as they are still in preview and am not sure about it's final capabilities.

Troubleshooting

ODFB gives me issues when synchronizing data
Please check if you have the latest version of ODFB installed. There have been stability issues in earlier released builds of the tool, but most of the issues should be fixed by now. You can check if you are running the latest version, by opening up Word-> File-> Account and click on Update Options-> View Updates. If your current version number is lower than the one you have, click on the Disable Updates button (click yes if prompted), then click Enable updates (click yes if prompted). This will force downloading the latest version of Office and thus the latest version of the ODFB tool.

If you are running the stand-alone version of ODFB, make sure you have downloaded the latest version from here.

Why is the upload taking so long?
This really depends on a lot of things. It can depend on:

• The method or tool that is used to upload the data
• The available bandwidth for uploading the data.
• The amount of throttling that is applied on our end.

Tips:

• Check your upload speed at http://www.speedtest.net and do a test for your nearest Office 365 data center. This will give you an indication of the maximum upload speed.
• Often companies have less available upload bandwidth then people at home. If you have the chance, uploading from a home location might be faster.
• Schedule the upload at times when there is much more bandwidth for uploading the data (usually at night)
• Test your upload speed upfront by uploading maybe 1% of the data. Multiply it by 100 and you have a rough estimate of the total upload time.
• The computers used for uploading the data. A slow laptop can become a bottle neck while uploading the data.
• Make sure you are using a tool that is utilizing the new migration API (either PowerShell or 3rd party)

If you feel that there are things missing here, please let me know and I’ll try to add them to this blog post.

-Andre

· https://microsoft.sharepoint.com/teams/sptech

· https://microsoft.sharepoint.com/teams/spdisc

· https://microsoft.sharepoint.com/teams/spsales

Training

MSDN & TechNet Articles

· Changes from SharePoint 2010 to SharePoint 2013 Preview

· SharePoint 2013 Technical Library in Compiled Help

· Test lab guides for SharePoint Server 2013

· Start building apps for Office and SharePoint

· What's new in authentication for SharePoint 2013 Preview

· What's new for Business Connectivity Services in SharePoint 2013 Preview

· What's new in eDiscovery in SharePoint Server 2013 Preview

· What's new for mobile devices in SharePoint 2013 Preview

· What's new in records management and compliance in SharePoint 2013 Preview

· What's new in business intelligence in SharePoint Server 2013 Preview

· What's new in social computing in SharePoint Server 2013 Preview

· What's new in web content management for SharePoint 2013 Preview publishing sites

· SharePoint 2013 Preview

Architecture  

· Topologies for SharePoint 2013 Preview

· Databases that support SharePoint 2013 Preview

· Design Sample: Corporate Portal with Host-named Sites for SharePoint Server 2013 Preview

· SharePoint 2013 Preview: App Overview for IT Pro

· Design Sample: Extranet with Dedicated Zones for Authentication for SharePoint 2013 Preview

· Search architectures for SharePoint Server 2013 Preview

· Enterprise search architectures for SharePoint Server 2013 Preview

· Design Sample: Corporate Portal with Path-based Sites for SharePoint Server 2013 Preview

Upgrades

· SharePoint 2013 Preview Upgrade Process

· SharePoint 2013 Preview: How to Test Upgrade

· Upgrade worksheet for SharePoint 2013 Preview

Books 

· Deployment guide for SharePoint 2013 Preview

Backup and Restore

· Backup and restore: SharePoint Server 2013 Preview

· Back up and restore planning worksheet

Samples

· Apps for Office and SharePoint Samples

Trainings

· SharePoint 2013 training for IT pros и SharePoint 2013: presentation: IT pro training

· SharePoint 2013 Developer Training

-Andre

IT Pro - http://technet.microsoft.com/en-us/sharepoint/fp123606
Developer - http://msdn.microsoft.com/en-US/office/apps/fp123626

-Andre

De oorzaak van dit probleem is vrij eenvoudig en het heeft te maken met het feit dat de SharePoint URL niet is toevoegd aan de “Trusted sites” zone van IE.

Dus voeg het eerste stuk van de URL van jou site verzameling toe aan de zone en open opnieuw de browser.

-Andre

De volledige details zullen volgende week worden verwerkt in de Office 365 Service Descriptions.

Office 365 for Enterprise Service Descriptions
http://www.microsoft.com/en-us/download/details.aspx?id=13602

Office 365 for professionals and small businesses Service Description
http://www.microsoft.com/en-us/download/details.aspx?id=13779

-Andre

Meer informatie:
https://skydrive.live.com/redir.aspx?cid=f42c90319800c034&resid=F42C90319800C034!167&parid=F42C90319800C034!145

De volgende data zijn nu nog beschikbaar:

• Vrijdag 11 mei
• Vrijdag 1 juni
• Vrijdag 15 juni
• Vrijdag 29 juni

Inschrijven kan hier:
https://training.partner.microsoft.com/learning/app/management/registrationex/LMS_Registration.aspx?UserMode=0&Mode=0&ActivityID=791085

-Andre

De tool kan hier worden gedownload.

De eerste stap is om een Distributie groep aan te maken via de UI in Exchange Online en hier de juiste mensen aan toe te voegen.

Zorg er wel voor dat de groep een security group wordt.

De tweede stap is om de batch file uit de zip file te draaien. Mocht je hier tegen problemen aanlopen waarbij de foutmelding wordt weergegeven over dat SharedMailboxTool.ps1 niet digitaal ondertekend is, dan kan het zijn eerst nog het volgende commando vanuit powershell gedraaid moet worden:

Set-ExecutionPolicy RemoteSigned

Als de batchfile de ps1 file goed kan aanroepen, krijg je het volgende scherm te zien:

Hierna krijg je een formulier te zien waarin de nieuwe gegevens van de gedeelde mailbox moeten worden ingevuld. Click hierna op Create.

Dan volgt de melding dat de mailbox succesvol is aangemaakt.

Op het tweede tabblad is het mogelijk om de permissies op een gedeelde mailbox te bekijken.

Om te testen of alles naar behoren werkt, kun je ofwel de mailbox direct openen of opnemen als additionele mailbox. Zie ook deze blogpost van collega Jesper:

http://blogs.technet.com/b/lystavlen/archive/2012/03/24/user-friendly-shared-mailboxes-in-office-365.aspx

-Andre