The ConfigMgr team has been hard at work on adding features. The Product Lifecycle dashboard (under Assets and Compliance\Overview\Asset Intelligence), can visually show you your installed products and support time frame.
Hopefully you don’t need this to tell you that you have less than 2 years to get off Windows 7.
Windows AutoPilot is a solution for onboarding and configuring new Windows 10 devices in a modern way. For more information, see an overview of Windows AutoPilot. One method of registering existing devices with Windows AutoPilot is to upload device information to the Microsoft Store for Business and Education. This information includes the device serial number, Windows product identifier, and a hardware identifier. Use Configuration Manager to collect and report this device information.
This device information only applies to clients on Windows 10, version 1703, and later
In the Configuration Manager console, Monitoring workspace, expand the Reporting node, expand Reports, and select the Hardware – General node.
Run the new report, Windows AutoPilot Device Information and view the results.
In the report viewer click the Export icon, and select CSV (comma delimited) option.
In 1802 TP, when you create a upgrade Task Sequence, now there will be additional groups created that is based on recommendations what Microsoft and others have seen done in the field. These groups are just recommendations and the actual tasks/scripts to do the checks, installs, etc. will need to be done by you. Several example scripts are out on the next that can help you get started.
New feature of Configuration Manager in 1802 Technical Preview.
In the Client settings, under Software Center, choose Customize. Now there is an option to Hide installed applications in Software Center. This is better sometimes than showing an application just to state it’s installed and clutter the list.
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.
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.
A new feature in technical preview 1607 is the connector to OMS to allow syncing of data such as collections from ConfigMgr to OMS.
ASSUMPTION: You have knowledge of Azure and OMS configuration outside of SCCM.
In update 1607, you will see a new item called OMS Connector
Click OMS Connector and click on Create connection to Operations Management Suite from the toolbar
You will see the first dialog of the Connection to the Operations Management Suite Wizard. Click Next
Enter the Tenant, Client ID, and Client secret key in the next dialog. All this information can be gathered from the Azure Portal. You may need to create a new Application (Under the Directory -> Applications) for the Client ID and key (second screen shot below).
Once entered, you will need to click Verify to continue.
Once the it’s properly verified, you will see the options to add your subscription, resource group, and Workspace name. Click Add to add the ConfigMgr collection(s) that OMS will collect the data from.
Final confirmation box will show your selections.
After few minutes, logon to the OMS portal (mms.microsoft.com). Do a Log Search for * Type=ComputerGroup.
Now you will see all the computers in the selected Collection (in the above settings) display in OMS. You will see the GroupSource equal to SCCM for those machines. My OMS was configured only for this so other servers are not there yet in my lab.