To force a syncronization of all identities with powershell use the below command:
- Open PowerShell with elevated rights.
- Execute Import-module ADSync.
- Execute Start-ADSyncSyncCycle –PolicyType Delta
- Check thru MIIS console it’s syncing.
These days I am migrating from GMail to Exchange Online and I have found that if the user fills his main mailbox and you enable archiving this does not go into action at same moment, yo noeed to wait for 30-60 minutes.
For this you have to force it from powershell with the following command:
Start-ManagedFolderAssistant –Identity <mailbox>
To force to ConfigMgr to download Current Branch 1606 version use the below powershell script. With that script you don’t need to wait for ConfigMgr.
The link explains how to use it. It’s simple!
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:
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:
These days I’m going to upgrade a SCCM 2012 R2 to SCCM 1511 CB.
Checking the environment I see problems with the Management Point.
Verifying the mpcontrol.log I saw errors like these:
Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER
Http test request failed, status code is 500, ‘Internal Server Error’. SMS_MP_CONTROL_MANAGER 584 (0x0248) STATMSG: ID=5436 SEV=E LEV=M SOURCE=”SMS Server” COMP=”SMS_MP_CONTROL_MANAGER
To fix it I give user rights over C:\Program Files\SMS_CCM\SMS_MP folder and enabled directory browsing on SMS_MP web directory.
To verify I went to http://localhost/sms_mp/.sms_aut?mplist and http://localhost/sms_mp/.sms_aut?MPCert. It showed info correctly.