If you’re considering upgrading or using existing Windows 2008 (any Service pack) Servers as Pull Distribution Points, make sure the’re 64-bit, and not 32-bit. If you do, they will not be able to pull large files (over 4 GB) from their assigned source Distribution Points. All other files will Transfer without issue.
You’ll see the following error in the debug eventlog for the Bits-Client: Continue reading Do not use Windows 2008 x86 as Pull Distribution Point
Version 1.9 of OneDriveMapper now supports a feature you’ve all been requesting a lot: builtin support for mapping Sharepoint Document Libraries!
It also has greatly enhanced session handling and full support for devices that have been Workplace Joined instead of domain joined.
Get the new version here
Have you ever wondered what company data your users are sharing outside the company?
Here’s a quick Compliance Search keyword you can use to identify publicly shared documents in Onedrive for Business:
ViewableByExternalUsers=TRUE
Use this as a keyword in a new Compliance Search in Office 365 to search through all Onedrive for Business and Sharepoint Online libraries.
If you’ve been administering or enrolling tenants for Office 365, you’ve dealt with Licenses.
In Office 365 (or Azure and Intune!), various licensing plans are available and can be upgraded or downgraded at will quite flexibly.
However, the user interface for this is extremely limited when you start working with large numbers of users or start working with non O365 specific licenses such as EMS and there is no place or method to keep an amdministration or rulebase of who should have what license.
I’m writing a series of scripts to bulk automate user licensing in Continue reading Office 365 automated license management part 1
During a migration for a customer from an Exchange 2007 environment, to Office 365, I ran into some issues that I’d like to share, as I could not find any material on this subject elsewhere.
Our plan was easy, update the Exchange 2007 servers to the latest Servicepack and CU to allow coexistence with an Exchange 2013 server as detailed on technet. I’d then build up the Hybrid relationship on the 2013 machine, move the mailboxes and phase out the 2007 machines. The 2013 machine would remain for on-premises Lync connectivity, which needs a CAS to talk to.
Once the Exchange 2013 server was installed, I prepared the machine for Hybrid connectivity, added the relevant domains to Office 365 and started the Hybrid setup wizard from the Exchange 2013 ECP.
I received the following error:
[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory
An IIS directory entry couldn't be created. The error message is Access is denied.
. HResult = -2147024891
+ CategoryInfo : NotInstalled: (EXCH2007-1\EWS (Default Web Site):ADObjectId) [Get-WebServicesVirtualDirect
ory], IISGeneralCOMException
+ FullyQualifiedErrorId : [Server=EXCH2013,RequestId=f962a8dd-2d39-4b36-85c3-a16a15fc3252,TimeStamp=9-6-201
5 07:50:59] [FailureCategory=Cmdlet-IISGeneralCOMException] 18EA544C,Microsoft.Exchange.Management.SystemConfigura
tionTasks.GetWebServicesVirtualDirectory
+ PSComputerName : exch2013.fqdn
An IIS directory entry couldn't be created. The error message is Access is denied.
. HResult = -2147024891
+ CategoryInfo : NotInstalled: (EXCH2007-2\EWS (Default Web Site):ADObjectId) [Get-WebServicesVirtualDirect
ory], IISGeneralCOMException
+ FullyQualifiedErrorId : [Server=EXCH2013,RequestId=f962a8dd-2d39-4b36-85c3-a16a15fc3252,TimeStamp=9-6-201
5 07:50:59] [FailureCategory=Cmdlet-IISGeneralCOMException] 18EA544C,Microsoft.Exchange.Management.SystemConfigura
tionTasks.GetWebServicesVirtualDirectory
+ PSComputerName : exch2013.fqdn
The hybrid wizard aborted, and could not continue.
The Get-WebServicesVirtualDirectory command checks all Continue reading Exchange 2007 Hybrid Migration to Office 365 with Exchange 2013 Coexistence