Intune will power the new MDM feature in Office 365

Today at Teched Europe, Microsoft announced a new feature in Office 365 – built-in mobile device management for Office 365. What cool about this is that you will actually be using the Intune backed and if you want to get more feature there will be an easy way to “upgrade” to Intune

To get a better understanding on what will be included in the Office 365 SKUs and what will be included in EMS/Intune, please visit 

To see some of the feature in action, below you have a short video explaining the features.


Which hotfixes should I apply to get the most of EMS

Hotfixes includes as we all know fixes to things that doesn’t work as expected but it also sometimes includes improvements and this is why I decided to write this blog post. This list is nothing official, I will list the updates that will/can impact EMS products (stability and improvements)

Note! This post will be updated as soon as I find any new hotfixes.

System Center 2012 R2 + Intune (also called Intune UDM)






In Microsoft SystemCenter 2012 R2 Configuration Manager, when a user becomes a cloud-managed user, a settings policy may not target the assignment for the user.

The original fix for this was included in CU2+CU3 but was broken by the installer process (script was overwritten and function reverted back to original state).

The effect of this is that users that are included in an collection will get the "fast download of a polices" but for any users added after applying CU2 or CU3 will not get the policies. 
Note 1 -There is one version of the fix for a CU2 installation and one for CU3.
Note 2 – If you installed the CU2 version and then install CU3 you need to install the CU3 version of this fix
Note 3 – After installing the hotfix, please run the script (that you can copy from the KB), this script will fix all existing deployments



Greatly reduces the time that’s required to execute a successful retire or wipe of a Mobile Device Management (MDM) device. These operations now run on the device in a matter of seconds, assuming the device is reachable by Windows Intune.

To apply this hotfix, you must have Cumulative Update 3

( )


KB2994331 (CU3)

A lot of things, please look at KB to see the hole list.

All CU’s are cumulative so all fixes that were in CU1 +CU2 is also included

This update replaces Cumulative Update 2 for System Center 2012 R2 Configuration Manager

( )


Kb2970177 (CU2)

The main improvement in this update is Speed. If you been working with device enrollment you probably noticed that it can take a wile for the device to receive all the profiles/policies you deployed to it.With the CU2 for SCCM 2012 R2 and the May update for the Intune backend, this has been improved a lot.

See for more information and step by step how to install it

This update replaces Cumulative Update 1

( )

for System Center 2012 R2 Configuration Manager.


Enrolling an Android device in both Exchange Active Sync (EAS) and Mobile Device Management causes a duplicate device to be created in the Administrator Console.


Windows Server 2012 R2 WAP Server role






Changing the MaxFieldLength and MaxRequestBytes  for http.sys doesn’t work as expected

For more information on how to use WAP in front of a NDES server se


CU2 for SCCM 2012 R2 is now released–Does it improve/impact Intune customers?

The CU2 update for System Center Configuration Manager 2012 R2 was just release. As with all CU’s, they include both fixes and improvements. With this blog post I want to highlight the things that are included in CU2 and will improve/impact Intune customers.

If you read the Kb2970177 you will se the following:

Mobile device management / Intune
  • Policies that apply to devices that are used together with Windows Intune may take 10 minutes or more to apply. Additionally, policies that are created before enrollment may not appear on the new device.
  • The Policy Request and Management Point fields for mobile devices may be missing from the Client Activity Details tab on the summary page for a given device.

Except for the two bug fixes it also includes one other major thing and that’s – Speed. If you been working with device enrollment you probably noticed that it can take a wile for the device to receive all the profiles/policies you deployed to it.With the CU2 for SCCM 2012 R2 and the May update for the Intune backend, this has been improved a lot.

So, if you use User Collection targeted Polices and Profiles they will be delivered to the User’s devices immediately after enrolling the devices.

The start benefit from this feature, install SCCM 2012 R2 CU 2 and test to enroll. Below you see a demonstration on the steps and the result.

  1. Install SCCM 2012 CU2

  2. Verify that your profiles/policy’s is deployed to a user collection

  3. Enroll a device and validate that the profiles/policy’s is deployed immediately

Important links from the videos:

Update 1 – If you have an existing SCEP profile you need to “manually” update it so it can be deployed during enrollment. Easiest way is to open the profile and just change the name or any other “cosmetic” change will also work. This will add a new revision on the profile and it will now work. Note that all SCEP profiles added after you applied CU2 is not affected by this issue

Windows Intune + Samsung KNOX = True

Last week Samsung announced that Samsung KNOX will support Windows Intune. Except for this, they also announced that they will add “Workplace Join” functionality into the Samsung Androids devices so the will be able to workplace join an Active Directory (this can be done on IOS and Windows 8.x today).

This is very good news for all Windows Intune customers that uses Samsung Android devices, really looking forward to the update

Read the full Samsung Press Release

What’s new in the Jan/Feb 2014 Intune update

The Jan/Feb 2014 update to Windows Intune has now been out for a couple of weeks. This was the first  update that was released through the SCCM “Extensions for Windows Intune”


So what did the update actually include:

  • Ability for the administrator to configure email profiles, which can automatically configure (IOS and WP8) the device with the appropriate email server information and related policies, as well as the ability to remove the profile along with the email itself via a remote wipe if needed (Only IOS).
  • Support for new configuration settings in iOS 7, including the "Managed open in" capability to protect corporate data by controlling which apps and accounts are used to open documents and attachments, and disabling the fingerprint unlock feature.
  • Ability for the administrator to remotely lock the device if it is lost or stolen, and reset the password if the user forgets it (as of now, this this feature only exist in the Intune standalone cloud service).

If you would like to see a good demo of some of the new features, please look at the interview on Channel9 with Martin Booth

Updated version of the Support Tool for Windows Intune Trial Management of Window Phone 8 is now avalable

Today a revision to the Support Tool for Windows Intune Trial Management of Window Phone 8 has been released. This tool facilitates Microsoft System Center 2012 Configuration Manager admins and Windows Intune standalone admins to try out Windows Phone 8 enrollment and software distribution scenarios during the Trial period.

The new revisions include:

· The new Windows Intune Company Portal for Windows Phone 8 released on Oct 18.

· A bug fix to address the ‘UBound’ error in the vbscript. [This script is needed only for Configuration Manager and not Intune standalone]

Download Support Tool for Windows Intune Trial Management of Window Phone 8

Windows Intune Company Portals now available for Windows, IOS and Android

Company Portal Downloads

Company Portal


Installation Method

Windows Intune Company Portal

Windows 8.x (x86/x64 and RT)

Windows Store

Microsoft Download Center

Direct User Installation




IT Deployment

System Center Configuration Manager Company Portal

Windows 8.x

(x86/x64 only)

Microsoft Download Center Only

IT Deployment

Windows Intune Company Portal for Windows Phone 8

Microsoft Download Center Only

IT Deployment

Windows Intune Company Portal for iOS

App Store

Direct User Installation


Windows Intune Company Portal for Android

Google Play

Direct User Installation


Support Tool for Windows Intune is now avalable for both SCCM+Intune AND Intune Standalone service

If you are a Windows Intune user you probably know that to be able to test managing Windows Phone 8 you need a special certificate from Symantec and to get this you also need to have a special Windows Phone developer account. This has been a lot of hassle for people that just want to test the functionally or to demo it. In May Microsoft released a “Support tool” that included a presigned Company Portal that you could install and upload in SCCM and you were all set to start testing enrolling Windows Phones. The problem were that this support tool only worked if you used SCCM+Intune, not if you were a user of the Standalone Window Intune service. The good news is that from today, the Support Tools also work for everyone that want to test Windows Phone 8 management in Windows Intune Standalone service.

Update 2013-12-10 – New version of the “Support Tool for Windows Intune Trial Management of Window Phone 8

Here is the basic steps

  • Log in to your Windows Intune Trial account via
  • Install the MSI that you download from Microsoft Download Center It will extract the sample SSP.xap and other sample xap files included in the MSI. The default location for the files is “C:\Program Files (x86)\Microsoft\Support Tool for Windows Intune Trial management of Windows Phone 8\” Note: The support tool included in the package is not needed for Windows Intune administrators. It is required for only Microsoft System Center 2012 Configuration Manager Administrators.
  • Navigate to "Administration -> Mobile Device Management -> Windows Phone 8". As stated in the text (see below, go directly to step 5


  • Upload the SSP.xap. Windows Intune Software Publisher will be launched.


  • In Software Setup page, leave the checkbox “Use the Company Portal App file signed by the sample Symantec code-signing certificate” checked.


  • Specify the location of software setup files by pointing to the SSP.xap that you’ve downloaded and extracted on your local machine
  • Click on next to complete the rest of the steps to publish the app
  • After completion of the steps above, Windows Intune Windows Phone Trial account enrollment is enabled and you should be able to start enrolling your Windows Phone devices through your trial account.
  • Deploy the sample apps provided in this package as appropriate


  • Users will now be able to enroll their WP8 device and could browse the deployed sample apps in their SSP.

To  enroll a Windows Phone 8, follow the below steps

  • On the Phone, go to Settings and select “Company Portal”
  • Click “Add account”


  • Add your account name and password


  • If everything works you should get a confirmation that the account has been added. Make sure to select to install the company portal


  • Your device is now added and can be managed from Windows Intune (can take a couple of minutes until you can see it in the console


MVP renewal – 2013

Today I got my MVP renewal letter that informed me that I was re-awarded as Most Valuable Professional and therefore receiving the Microsoft MVP – System Center Cloud and Datacenter Management award for the 7th year in a row for doing a great job in serving the community by helping out the community.