Windows Server 2016 Published!


This week Microsoft has published the last version of Windows Server, Windows Server 2016 and with a lot of improvements.

On the below link you can read more about!

And here a link to a free book.


Update Rollup 1 for System Center Configuration Manager current branch, version 1606 available


Our folks of ConfigMgr Product Team relased an Update Rollup for the 1606 version of Current Branch.

Here is the announcement:

And here the specifications of what improve/fix:


Federation with ADFS 3.0 and SNI Support


Some times I found problems with mobile devices trying to authenticate to ADFS when these are managed by Intune+ConfigMgr.

The problem is that exists a problem with the SNI.

Below I put a link where is well explained.


Available Update 1606 for System Center Configuration Manager


Good news! yesterday was announced the availability of ConfigMgr Current Branch 1606. This is not a minor update and comes with a lot of improvements focused on Security, Device Management, ConfigMgr Monitoring, Service and Updates Node options, Application management, etc…

Some of new features are:

  • Windows Information Protection (formerly EDP) features allow you to create and deploy information protection policy, including the ability to choose your protected apps and define your EDP-protection level.


  • Windows Defender Advanced Threat Protection features enable the ability to on-board and off-board Windows 10 clients to the cloud service and view agent health in the monitoring dashboard (requires a Windows Defender ATP tenant in Azure).


  • Windows Store for Business Integration allows you to manage and deploy applications purchased through the Windows Store for Business portal for both online and offline licensed apps.


  • Windows Hello for Business policies for domain-joined Windows 10 devices managed by the Configuration Manager client.


More info about Current Branch:


Windows 10 upgrade ending soon!

Hi all,

As you know, Windows 10 has a free upgrade if you have Windows 7 or 8.1 deployed… but not forever. The free upgrade offer to Windows 10 will end on July 29, 2016!

Check that page:

FAQ for Windows 10 upgrade:


Allowing mobile devices on Exchange Online with a bulk script

Hi guys,

In my last exchange migration to O365 my customer had the requirement to block all BYOD because for security reasons email department verify and manage all mobile devices. How? as always, asigning IMEI device ID to the user mailbox in O365.

Steps to acomplish that:

First of all you need to go to Exchange Online and there go to mobile section. Push on Edit.



On the window select Block access and push on save


After that action, you can use the below command to asign devices to usermailboxes:

Set-CASMailbox -ActiveSyncAllowedDeviceIDs “ID”

To check some user use:

Get-CasMailbox username | fl ActiveSyncAllowedDeviceIDs

If you have a large correlation of users – devices you can use my script. It’s very useful!!

  1.  You need a csv file with a list of users called migration.csv. Save it on C:\migration folder.


2. You need a file called Device_Info.csv where you have all device IMEI info exported from on-prem. Save it on C:\migration folder.


3. A csv file called LoteYYYYMMDD.csv where you have all users in O365.


4. The magic script:

[string]$Script:sourcefilename = “migration.csv”,
[System.Management.Automation.CredentialAttribute()]$cred = $null

Write-Host “This script must be run from a Powershell AD AZURE”
Write-Host “We load the list of users migrated from file $($Script:sourcefilename)”
$migrados = Import-Csv $Script:sourcefilename
if([String]::IsNullOrEmpty($cred)){$cred = Get-credential}

Write-Host “We load the list of devices.”
$Users = Import-Csv “C:\MIGRATION\Device_Info.csv” | Sort-Object PrimarySMTPAddress
$UserID = $null

Foreach ($user in $Users)
#Let’s see if the device line in the file contains a migrated user
$containsMailMigrado = $migrados | %{$_ -match $user.PrimarySMTPAddress}
If($containsMailMigrado -contains $true)
Write-Host ” Finded MailMigrado – $($user.PrimarySMTPAddress)”
$UserID = $user.PrimarySMTPAddress
$DeviceID = $user.DeviceID
Write-Host ” Adding device DeviceID = $($DeviceID)”
Set-CASMailbox -Identity $UserID -activesyncalloweddeviceid @{Add=$DeviceID}

Save that script as ScriptDevicesO365.PS1

Having all requisites showed above you can execute the line .\ScriptDevicesO365.PS1 LoteYYYMMDD.csv $UserCredential that will permit all your corporate devices be used with the assigned user on Office 365 – Exchange Online.