| Exit code | Meaning + |
|---|---|
| 0 | Success + |
| 1 | Unexpected error occurred while executing the script + |
| 2 | Error when logging to console. $logMode = 0. + |
| 3 | Error when logging to console and file. $logMode = 1. + |
| 4 | Error when logging to file. $logMode = 2. + |
| 5 | Error when logging to console and file. $logMode = unknown. + |
| 6 | The commercialID parameter is set to unknown. Modify the script. + |
| 7 | Function -CheckCommercialId: Unexpected failure. + |
| 8 | Failure to create registry key path: HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection. + |
| 9 | Error when writing CommercialId to registry. + |
| 10 | Error when writing CommercialDataOptIn to registry. + |
| 11 | Function -SetupCommercialId: Unexpected failure. + |
| 12 | Can’t connect to Microsoft – Vortex. Check your network/proxy settings. + |
| 13 | Can’t connect to Microsoft – setting. Check your network/proxy settings. + |
| 14 | Can’t connect to Microsoft – compatexchange. Check your network/proxy settings. + |
| 15 | Error connecting to Microsoft. Check your network/proxy settings. + |
| 16 | Machine requires reboot. + |
| 17 | Function -CheckRebootRequired: Unexpected failure. + |
| 18 | Outdated compatibility update KB package. Update via Windows Update/WSUS. + |
| 19 | This machine doesn’t have the proper KBs installed. Make sure you have recent compatibility update KB downloaded. + |
| 20 | Error writing RequestAllAppraiserVersions registry key. + |
| 21 | Function – SetRequestAllAppraiserVersions: Unexpected failure. + |
| 22 | Error when running inventory scan. + |
| 23 | Error finding system variable %WINDIR%. + |
| Product version | -Windows 10 support | -
|---|---|
[System Center Configuration Manager (current branch) ](https://technet.microsoft.com/en-us/library/mt346023.aspx) |
-Client deployment, upgrade, and management with new and existing features |
-
Configuration Manager and Configuration Manager SP1 |
-Deployment, upgrade, and management with existing features |
-
Configuration Manager 2007 |
-Management with existing features |
-
+
+As indicated in the diagram, Microsoft continues to provide support for deep manageability and security through technologies like Group Policy, Active Directory, and System Center Configuration Manager. It also delivers a “mobile-first, cloud-first” approach of simplified, modern management using cloud-based device management solutions such as Microsoft Enterprise Mobility + Security (EMS). Future Windows innovations, delivered through Windows as a Service, are complemented by cloud services like Microsoft Intune, Azure Active Directory, Azure Rights Management Service, Office 365, and the Windows Store for Business.
+
+## Deployment and Provisioning
+
+With Windows 10, you can continue to use traditional OS deployment, but you can also “manage out of the box.” To transform new devices into fully-configured, fully-managed devices, you can:
+
+
+
+- Avoid reimaging by using dynamic provisioning, enabled by a cloud-based device management services like Microsoft Intune.
+
+- Create self-contained provisioning packages built with the [Windows Imaging and Configuration Designer (ICD)](https://msdn.microsoft.com/library/windows/hardware/dn916113(v=vs.85).aspx).
+
+- Use traditional imaging techniques such as deploying custom images using [System Center Configuration Manager](https://docs.microsoft.com/sccm/core/understand/introduction).
+
+You have multiple options for [upgrading to Windows 10](https://technet.microsoft.com/itpro/windows/deploy/windows-10-deployment-scenarios). For existing devices running Windows 7 or Windows 8.1, you can use the robust in-place upgrade process for a fast, reliable move to Windows 10 while automatically preserving all the existing apps, data, and settings. This can mean significantly lower deployment costs, as well as improved productivity as end users can be immediately productive – everything is right where they left it. Of course, you can also use a traditional wipe-and-load approach if you prefer, using the same tools that you use today with Windows 7.
+
+## Identity and Authentication
+
+You can use Windows 10 and services like [Azure Active Directory](https://azure.microsoft.com/documentation/articles/active-directory-whatis/) in new ways for cloud-based identity, authentication, and management. You can offer your users the ability to **“bring your own device” (BYOD)** or to **“choose your own device” (CYOD)** from a selection you make available. At the same time, you might be managing PCs and tablets that must be domain-joined because of specific applications or resources that are used on them.
+
+You can envision user and device management as falling into these two categories:
+
+- **Corporate (CYOD) or personal (BYOD) devices used by mobile users for SaaS apps such as Office 365.** With Windows 10, your employees can self-provision their devices:
+
+ - For corporate devices, they can set up corporate access with [Azure AD Join](https://azure.microsoft.com/documentation/articles/active-directory-azureadjoin-overview/). When you offer them Azure AD Join with automatic Intune MDM enrollment, they can bring devices into a corporate-managed state in [*one step*](https://blogs.technet.microsoft.com/ad/2015/08/14/windows-10-azure-ad-and-microsoft-intune-automatic-mdm-enrollment-powered-by-the-cloud/), all from the cloud.