In the updated 1802 TP, we now have an option to create Edge policies.
In Assets and Compliance, under Compliance Settings, there is an option for Microsoft Edge Browser Profiles
Highlight that and choose from the Menu (or right click) to Create Microsoft Edge profile
In the Create Microsoft Edge Browser Policy wizard, name your profile/policy just as an example below. You can create multiple profiles to target different collections like any other deployment.
In the next screen, choose the configuration needed based on your corporate policies.
Once done, select next and choose the OS which will always be Windows 10 but you can target between x32 and x64.
Once all done, from the menu bar or right click to deploy the policy to a collection.
We always see computers left unattended and unlocked at the workplace and even worse, public places like coffee shops. In Windows Creators update, Microsoft has introduced Dynamic Lock. When you pair your phone (Bluetooth) with Windows 10, now the option to lock the computer automatically when you walk away will be available.
If you have the Insiders Preview today, you can test this by enabling Dynamic Lock by going to Settings > Accounts > Sign-in options and toggle Dynamic lock to “on”. Make sure you phone is paired to your computer first.
For the Enterprise, Dynamic Lock can also be enforced via Group Policy.
To be able to review Windows 10 endpoints (Anniversary Update or higher) into Windows Defender ATP, you will need to onboard first. There are several ways to do so including scripts, Group Policy, Intune, Configuration Manager 2012 through current branch 1602. With the release of Configuration Manager branch update 1606, it now includes integrated Windows Defender ATP to be able to monitor and deploy the policies.
- To get started, login to the Windows Defender ATP site to download the policies https://securitycenter.windows.com/download
Choose the drop down Select your deployment tool, and select the System Center Configuration Manager (current branch) version 1606
- This will download a ZIP file with the onboarding package. Unzip it to where you can access it with ConfigMgr.
- Under Assets and Compliance, expand Endpoint Protection where you will see Windows Defender ATP Policies. Select Windows Defender ATP Policies , and click Create Windows Defender ATP Policy from the toolbar or right click.
- Follow the wizard to import the onboarding file you downloaded from the site. (NOTE: SCREENSHOT SHOWS OFFBOARDING, BUT SHOULD BE ONBOARDING)
- Once done, you will see the policies in the console. Right client or from the toolbar, click Deploy.
- You can do this for off-boarding as well. From the same site, you can select to download the off-boarding package and then follow the steps above to import into ConfigMgr.
Microsoft in the latest Insider Previews has introduced (or reintroduced) Quick Assist. Quick Assist is a remote desktop tool to assist other users with Windows 10 or apps. This can be very useful for business to help remote users or folks in IT trying to help friends and family.
From the Start Menu, go to Windows Accessories and you will see the desktop app called Quick Assist. Currently I have build 10.0.14393 which has this application.
- Click Quick Assist and click Give Assistant.
- You will be asked to sign into your Microsoft Account (MSA, Live, Hotmail, Outlook.com, etc.) that you have registered.
Once you sign in, you will get the Share security code dialog with a code. (* I have crossed out the code here. Even though it will not work after the expiration, I wanted to play it safe).
- You can copy to clipboard, send email or provide instructions.
- Now tell the user how to use the code so they can let you in to remote in.
- Open the Start menu and select All apps > Windows Accessories > Quick Assist.
- Select Get assistance and follow the instructions.
- If User Account Control appears, select Yes to continue.
After the steps are completed, please wait a few minutes for your devices to connect
You will see it connecting and the remote user will need to click
Allow to give access.
Here are few new items in the 1602 branch of Configuration Manager
- A new option in the Software Center that allows the user to poll the user and machine policies (without going through the Control Paten applet). In Software Center (after the new client push), a Sync Policy button has been added to the Options > Computer Maintenance page.
- Windows 10 Device Health Attestation. This can be enabled in Administration > Overview > Client Settings under Computer Agent
To view the device health attestation view, in the Configuration Manager console go to the Monitoring workspace of, click Security node, and then click Health Attestation.
- Configuration Manager sites that run version 1602 or later support the in-place upgrade of the site servers operating system from Windows Server 2008 R2 to Windows Server 2012 R2. Before you upgrade to Windows Server 2012 R2, you must uninstall WSUS 3.2 from the server.
- New filter options are available for Windows 10 servicing plans that allow you to filter for Language, Required, and Title. Only upgrades that meet the specified criteria will be added to the associated deployment. Prior this change, all upgrades were being downloaded regardless of language or SKU.
Update to registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WcmSvc\wifinetworkmanager\config
Or via Login Script or during the task sequences in Configuration Manager or MDT (post image install)
reg add HKLM\SOFTWARE\Microsoft\WcmSvc\wifinetworkmanager\config /t REG_DWORD /v AutoConnectAllowedOEM /d 0
Modify Unattend.xml to add Microsoft-Windows-WiFiNetworkManager
Set WiFiSenseAllowed to 0
For Windows 10 build 1511 or later
Configure the Group Policy Object Allow Windows to automatically connect to suggested open hotspots, to networks shared by contacts, and to hotspots offering paid services under
Computer Configuration\Administrative Templates\Network\WLAN Service\WLAN Settings\.
Microsoft has just released an update to MDT 2013 today as Update 2. Update 1 provided Windows 10 support (Windows 10 supported ADK is needed still). Update 2 as stated in the blog does not add major new features but adds some improvements to existing features and functionality.
jparekh at netrixllc dot com