Do not use Windows 2008 x86 as Pull Distribution Point

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

OneDriveMapper v1.9 released

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

Identifying publicly shared documents in OneDrive for Business and Sharepoint Online

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.

Office 365 automated license management part 1

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

Exchange 2007 Hybrid Migration to Office 365 with Exchange 2013 Coexistence

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

Installing a Windows 2003 Distribution Point

Ideally, when deploying Distribution Points, you really want to use Windows 2008 R2 or higher, as this OS supports autoconfiguration of WDS, IIS, etc.

But of course, in some situations this isn’t feasible.

First, install all Service packs, the machine should be fully up to date.

Then, add the SCCM Server or install account to the local Administrators on the Windows 2003 machine

Then, install IIS and WDS (if using PXE).

Then, install the Windows Server 2003 Service Pack 2 Support Tools

Reboot

Add the Server to the hierarchy in sccm and Monitor dismgr.log Continue reading Installing a Windows 2003 Distribution Point

Limit your OneDrive for Business accounts to domain PC’s only

Today, Microsoft announced an exciting feature which is still rather limited, but a start of something nice.

Administrators can enforce security on OneDrive for Business, ensuring that their licensed business users can only sync their OneDrive account on a domain joined computer. Users will be unable to sync their OneDrive library on their personal, unsecured and unmanaged device.

Let’s hope this is soon extended to Windows 10 Azure Workplace Joined devices and any other devices that have been WorkPlace joined (Android, Apple, Windows 7+, Windows Phone).

For details on configuring this, check this technet article.

SCCM Updated for Intune and Windows 10

If you’re using System Center Configuration Manager 2012 and have integrated it with Intune or are planning to pilot Windows 10, this is the time to update your hierarchy!

I’ve been stumped and irritated several times by the flimsy integration between SCCM and Intune, seems I wasn’t the only one. Both products have such a huge potential! With the service pack that was just released, this seems to be changing, read all about it in this blogpost by Microsoft’s Brad Anderson.

And for the techies, this article has a list of all the new features.

OneDriveMapper V1.8 released

Version 1.8 of OneDriveMapper will now automatically detect your OneDrive URL, instead of using your login name. This is useful in scenario’s where someone’s username changes. Microsoft does not change the OneDrive for business URL when the username changes, which would cause mappings made based on the login to fail. This often happened when IT staff changed a usename because a user got married.

The login detection and process has also been made more efficient, and broken driveletters are now automatically deleted.

Get the new version here