The following text is from the MS docs site but screen shot from my lab (no need to recreate good document): https://docs.microsoft.com/en-us/sccm/core/get-started/capabilities-in-technical-preview-1802#report-on-windows-autopilot-device-information
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.
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.
Some examples and additional recommendations are available here https://docs.microsoft.com/en-us/sccm/core/get-started/capabilities-in-technical-preview-1802
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.
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.
One of the new features of the CM 1802 TP is the ability to create deployment templates for Task Sequences and then use that to apply to existing task sequences to create new deployments.
To create a template, during the deployment of a TS, in the Summary screen, there is a new button in the upper righthand corner “Save As Template…”.
Once you select that, you have a new popup box to select what you want included in the template and name the template.
In this case, I chose all of it and named it Win 10 Deployment.
Now to apply the template in a new deployment, in the first dialog, you have the Select Deployment Template button (above the Comments area).
Once clicked, you can select the template of your choice.
Video showcasing the updated feature which allows the user interaction to happen while the installation is taking place as the SYSTEM
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.