-| Deployment Status | Description
- |
| Feature Update | A concatenation of servicing branch (CB, CBB, LTSB) and OS Version (e.g., 1607)
- |
| Installed | The number of devices that have reported to be on the given servicing train and feature update.
- |
| In progress | The number of devices that have reported to be at some stage in the installation process for the given feature update.
-
Example: Device X running CB 1507 could be installing CB 1607. In this example, X would count as both **Installed** for **CB 1507** and **In Progress** for **CB 1607**.
- |
| Scheduled next 7 days | The total number of devices that are set to have a deferral period expire within 7 days, and after that deferral period expires are targeted to install the given update.
-
Example: Device Y running CB 1507 could be scheduled to install CB 1607 in 5 days. In this example, X would count as both **Installed** for **CB 1507** and **Scheduled next 7 days** for **CB 1607**
- |
| Update Failed | The total number of devices that were **In progress** with the installation for the given feature update, but encountered a failure.
-
Example: Device X running CB 1507 could be installing CB 1607. X then encounters an error during installation. In this example, X would count as both **Installed** for **CB 1507** and **Update failed** for **CB 1607**, but not as **In progress** for **CB 1607**.
- |
| Status Unknown | For devices not using Windows Update to get updates, some information on deployment progress cannot be known. It is possible to know the current installed Feature Update for a device, but not which devices are **In Progress**, **Scheduled next 7 days**, or devices with **Update Failed**.
-
Devices that Update Compliance knows belongs to your organization, but it does not know update failures or installation progress, will be counted here.
- |
-
-
-## Quality Update Perspective
-
-The Quality Update Deployment Status perspective is a breakdown of the most essential data the user should know about the status of their devices with respect to being Up-to-date. The perspective shows a summary of the organization’s devices for one specific OS version, or build.
-
-### Quality Update Build Summary
-
-The build summary blade attempts to summarize the most important data points to the user for the given build. It is divided into two sections. The first section is a summary of devices for that build – the total number of devices, and the amount that need attention. Each row within the table below is a breakdown of why each device requires attention. The rows can be interacted with to be taken to a larger table view that shows detailed information about all the devices that meet the given criteria. See the following example:
-
-
-
-
-
-### Quality Update Deferral Configurations
-
-The next blade is the Deferral configuration blade, which shows the WUFB Deferral configurations for all devices that are using WUFB and are reporting to Update Compliance. If no information can be gathered from a device or it is not configured to use WUFB, it will show up as **Not configured (-1)**. See the following example:
-
-
-
-
-
-### Quality Update Deployment Status
-
-Under the three top-level blades is the deployment status for the newest quality update for the given build. It provides information on the revision number as well as how many days it has been since that revision has been released. See the following example:
-
-
-
-
-
-See the following table for a description of last reported states for devices deploying that quality update.
-
-
-
-| Deployment State | Description
- |
| Update Completed | When a device has finished the update process and is on the given update, it will display here as **Update completed**.
- |
| In Progress | Devices that are “in progress” installing an update will fall within this category. This category is detailed in the following blade: **Detailed Deployment Status**.
- |
| Deferred | If a device’s WUfB deferral policy dictates that it is not set to receive this update, the device will show as Update deferred.
- |
| Cancelled | A device will report that the update has been cancelled if the user, at some point, cancelled the update on the device.
- |
| Blocked | Devices that are blocked are prevented from proceeding further with the given update. This could be because another update is paused, or some other task on the device must be performed before the update process can proceed.
- |
-
-
-
-
-### Quality Update Detailed Deployment Status
-
-This blade provides more detail on the deployment process for the update in the Deployment Status blade. This blade is more of a deployment funnel for devices, enabling you to see at a more granular level how devices are progressing along in their deployment. See the following example:
-
-
-
-
-
->Devices that are not managed using Windows Update (Windows Update for Business or otherwise) will not have detailed deployment information.
-
-
-The following table provides a list of the detailed deployment states a device can report:
-
-
-
-| Detailed Deployment State | Description
- |
| Update deferred | The WUfB policy of the device dictates the update is deferred.
- |
| Pre-Download Tasks Passed | The device has finished all tasks necessary prior to downloading the update.
- |
| Download Started | The update has begun downloading on the device.
- |
| Download Succeeded | The device has successfully downloaded the update.
- |
| Pre-Install Tasks Passed | The device has downloaded the update successfully, and successfully passed all checks prior to beginning installation of the update.
- |
| Install Started | The device has begun installing the update.
- |
| Reboot Required | The device has finished installing the update, and a reboot is required before the update can be completed.
- |
| Reboot Pending | The device is pending a scheduled reboot before the update can be completed.
- |
| Reboot Initiated | The device has reported to have initiated the reboot process for completing the update.
- |
| Update completed | The device has completed installing, rebooting, and applying the update.
- |
-
-
-## Feature Update Perspective
-
-
-Like Quality Updates, the Feature Update Deployment Status perspective is a breakdown of information most essential to an administrator. This information is viewed by clicking on a given build on the Feature Update Status blade and then navigating to the **Update Deployment Status** pane as displayed previously. In Update Compliance, a perspective is assigned to a query; the query used to generate the perspective can be altered to show other information, if desired.
-
-Every piece of data shown in this view can be clicked; when clicked, it will alter the query to focus only on the data you need. If the perspective is not meaningful after the query is altered, you can use the other data views like the List and Table.
-
->After clicking on an OS version from the Feature Update Status blade, the query must fully load the results before you can select the Update Deployment Status perspective.
-
-### Feature Update Build Summary
-
-
-The Build Summary blade provides a summary for all devices on the given build. It gives a count of all devices, as well as a count of all devices that need attention. Below the counts, you can see why the devices need attention, with a count of devices that fall into each category. See the following example:
-
-
-
-### Feature Update Deferral Configuration
-
-
-This blade shows all deferral configurations for the devices on the given build. See the following example:
-
-
-
-
-
-Deferral configurations are WUfB-specific, and are shown as days. Some useful information regarding how deferral configurations are shown:
-- The devices are grouped based off what their deferral policy is set at. For feature updates, this can be up to 120 days.
-- A deferral of zero days means the device has WUfB configured, but is set to not defer the update. These devices will be under “0” for the Update Deferred field.
-- Devices that are not configured to use WUfB deferral policies have a “-1” for their deferral days. In this table, the devices will show up as “Not Configured (-1)”.
-
-### Feature Update Deployment Status
-
-As stated earlier in this section, the Feature Updates blade focuses on how Current your devices are. A device is only Current when it is on the latest feature update and quality update Microsoft offers. Thus, the Deployment Status blade displays the deployment status for devices regarding their deployment to the latest feature update. See the following example:
-
-
-
-
-
-This blade breaks down the main states a device can be in through the deployment of a feature update. The possible states are as follows:
-
-
-
-| Deployment State | Description
- |
| Update completed | When a device has completely finished the update process and is on the given update, it will show up here as **Update completed**.
- |
| Inprogress | Devices “in progress” of installing the given update will fall within this category. This category is iterated on with further granularity in the proceeding blade, “Detailed Deployment Status”.
- |
| Update deferred | If a device’s WUfB deferral policy dictates that it is not set to receive this update yet, the device will show as Update deferred.
- |
| Cancelled | A device will report that the update has been cancelled if the user, at some point, cancelled the update on the device.
- |
| Blocked | Devices that are blocked are prevented from proceeding further with the given update. This could be because another update is paused, or some other task on the device must be performed before the update process can proceed.
- |
-
-
-
-
-
-
-
-
-### Feature Update Detailed Deployment Status
-
-This blade provides more detail on the deployment process for the update in the Deployment Status blade. This blade is more of a deployment funnel for devices, enabling you to see at a more granular level how devices are progressing along in their deployment. See the following example:
-
-
-
-
-
-The following table displays all states a device can report:
-
-
-
-| Detailed Deployment State | Description
- |
| Update deferred | The WUfB policy of the device dictates the update is deferred.
- |
| Pre-Download Tasks Passed | The device has finished all tasks necessary prior to downloading the update.
- |
| Download Started | The update has begun downloading on the device.
- |
| Download Succeeded | The device has successfully downloaded the update.
- |
| Pre-Install Tasks Passed | The device has downloaded the update successfully, and successfully passed all checks prior to beginning installation of the update.
- |
| Install Started | The device has begun installing the update.
- |
| Reboot Required | The device has finished installing the update, and a reboot is required before the update can be completed.
- |
| Reboot Pending | The device is pending a scheduled reboot before the update can be completed.
- |
| Reboot Initiated | The device has reported to have initiated the reboot process for completing the update.
- |
| Update completed | The device has completed installing, rebooting, and applying the update.
- |
-
-
-
-## List of Queries
-
-Operations Management Suite leverages its powerful Log Analytics querying to perform all data calculations. For this blade, we provide examples of queries that show useful data to the user about their organization’s devices. See the following example:
-
-
-
-
-
-The following **Common queries** are available:
-
-
-
-| Query Title | Description
- |
| OS Security Update Status | This query provides an all-up view with respect to how many devices are on the latest security update for their OS version. The table will detail an aggregated count of the number of devices, out of the total (so count, or percent) are on the latest security update for their OS build.
- |
| Update Deployment Failures | This query provides a chart view, displaying an aggregation of all devices that have reported a deployment failure for either feature or quality updates. The aggregation of the data is on the given update for which a given device has reported a deployment failure.
- |
| Devices pending reboot to complete update | This query will provide a table showing all devices that are at the stage of "Reboot Pending" In the update deployment process.
This query will show devices which are in this state for both feature and quality updates; the data will be organized on precisely which update the given device(s) are pending a reboot to install.
- |
| Servicing Option Distribution for the devices | This query provides a chart view that aggregates all devices seen by the solution on for each servicing option available for Windows 10 devices (CB, CBB, LTSB)
-OS Distribution for the devices This query provides a chart view displaying the distribution of the different editions of Windows 10 that devices seen by the solution are running (e.g., Enterprise, Professional, Education, etc.)
- |
| Deferral configurations for Feature Update | This query provides a chart view which displays a breakdown of the different Feature Update deferral configurations through WUfB that the devices seen by the solution are using.
The configuration is in days. 0 days means the device has WUfB deferrals configured, but is not set to defer feature updates. -1 means the device has no feature update deferral policies configured.
- |
| Pause configurations for Feature Update | The WUfB policy
- |
| Update deferred | This query provides a chart view displaying the breakdown of devices that are either paused, or not paused for feature updates.
“Not configured” means the device is not paused. “Paused” means it is currently paused.
- |
| Deferral configurations for Quality Update | This query provides a chart view which displays a breakdown of the different Quality Update deferral configurations through WUfB that the devices seen by the solution are using.
The configuration is in days. 0 days means the device has WUfB deferrals configured, but is not set to defer quality updates. -1 means the device has no quality update deferral policies configured.
- |
| Pause configurations for Quality Update | This query provides to a chart view displaying the breakdown of devices that are either paused, or not paused for quality updates.
**Not configured** means the device is not paused. **Paused** means it is currently paused.
- |
-
## Related topics
[Get started with Update Compliance](update-compliance-get-started.md)
\ No newline at end of file
diff --git a/windows/deployment/update/update-compliance-wd-av-status.md b/windows/deployment/update/update-compliance-wd-av-status.md
new file mode 100644
index 0000000000..0f4b1fa78f
--- /dev/null
+++ b/windows/deployment/update/update-compliance-wd-av-status.md
@@ -0,0 +1,28 @@
+---
+title: Update Compliance - Windows Defender AV Status report
+description: an overview of the Windows Defender AV Status report
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: deploy
+author: DaniHalfin
+ms.author: daniha
+ms.date: 10/17/2017
+---
+
+# Windows Defender AV Status
+
+
+
+The Windows Defender AV Status section deals with data concerning signature and threat status for devices that use Windows Defender Antivirus. The section tile in the [Overview Blade](update-compliance-using.md#overview-blade) provides the percentage of devices with insufficient protection – this percentage only considers devices using Windows Defender Antivirus.
+
+The **Protection Status** blade gives a count for devices that have either out-of-date signatures or real-time protection turned off. Below, it gives a more detailed breakdown of the two issues. Clicking any of these statuses will navigate you to a Log Search view containing the query.
+
+The **Threat Status** blade provides a visualization of, for devices that have encountered threats, how many were and were not remediated successfully. It also provides a detailed count. Clicking either of these will navigate to the respective query in Log Search for further investigation.
+
+Here are some important terms to consider when utilizing the Windows Defender AV Status section of Update Compliance:
+* **Signature out of date** devices are devices with signature older than 14 days.
+* **No real-time protection** devices are devices who are using Windows Defender AV but have turned off Real-time protection.
+* **Recently disappeared** devices are devices that were previously seen by Windows Defender AV and are no longer seen in the past 7 days.
+* **Remediation failed** devices are devices where Windows Defender AV failed to remediate the threat. This can be due to reason like disk full, network error, operation aborted, etc. Manual intervention may be needed from IT team.
+* **Not assessed** devices are devices where either a third-party AV solution is used or it has been more than 7 days since the device recently disappeared.
diff --git a/windows/deployment/update/waas-windows-insider-for-business-aad.md b/windows/deployment/update/waas-windows-insider-for-business-aad.md
index 9f3bfed774..93eb3de9b6 100644
--- a/windows/deployment/update/waas-windows-insider-for-business-aad.md
+++ b/windows/deployment/update/waas-windows-insider-for-business-aad.md
@@ -16,7 +16,7 @@ ms.author: daniha
- Windows 10
-> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
+> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
We recently added features and benefits to better support the IT Professionals and business users in our Insider community. This includes the option to download Windows 10 Insider Preview builds using your corporate credentials in Azure Active Directory (AAD). By enrolling devices in AAD, you increase the visibility of feedback submitted by users in your organization – especially on features that support your specific business needs.
@@ -30,15 +30,25 @@ We recently added features and benefits to better support the IT Professionals a
In order to get the most benefit out of the Windows Insider Program for Business, organizations should not use a test tenant of AAD. There will be no modifications to the AAD tenant to support the Windows Insider Program as it will only be used as an authentication method.
+## Register your organization's Azure AD domain to the Windows Insider Program for Business
+Rather than have each user in your organization register for Windows 10 Insider Preview builds, you can now simply register your domain – and cover all users with just one registration.
+
+1. On the [Windows Insider](https://insider.windows.com) website, go to **For Business > Getting Started** to [register you organizational Azure AD account](https://insider.windows.com/en-us/insidersigninaad/).
+2. **Register your domain**. Rather than have each user register individually for Insider Preview builds, administrators can simply [register their domain](https://insider.windows.com/en-us/for-business-organization-admin/) and control settings centrally.
+
+>[!IMPORTANT]
+>The signed-in user needs to be a **Global Administrator** of the Azure AD domain in order to be able to register the domain.
+
## Check if a device is connected to your company’s Azure Active Directory subscription
Simply go to **Settings > Accounts > Access work or school**. If a corporate account is on Azure Active Directory and it is connected to the device, you will see the account listed as highlighted in the image below.
## Enroll a device with an Azure Active Directory account
-1. Visit [insider.windows.com](https://insider.windows.com). Sign-in with your corporate account in AAD and follow the on-screen registration directions.
-2. On your Windows 10 device, go to **Settings > Updates & Security > Windows Insider Program**.
-3. Enter the AAD account that you used to register and follow the on-screen directions.
+1. Navigate to the [**Getting Started**](https://insider.windows.com/en-us/getting-started/) page on [Windows Insider](https://insider.windows.com).
+2. Go to the **Register your organization account** and follow the instructions.
+3. On your Windows 10 device, go to **Settings > Updates & Security > Windows Insider Program**.
+4. Enter the AAD account that you used to register and follow the on-screen directions.
>[!NOTE]
>Make sure that you have administrator rights to the machine and that it has latest Windows updates.
@@ -61,7 +71,7 @@ With the current version of the Feedback Hub app, we need the user's consent to
-Once agreed, everything will work fine and that user won't be prompted for permission again.
+Once agreed, everything will work fine, and that user won't be prompted for permission again.
### Something went wrong
@@ -73,7 +83,7 @@ In case the administrators blocked this option, when the user signs in with the
This blocks the user from signing in, which means they won't be able to use the Feedback Hub app with their AAD credentials.
-**To fix this issue**, an adminsitrator of the AAD directory will need to enable user consent for apps to access their data.
+**To fix this issue**, an administrator of the AAD directory will need to enable user consent for apps to access their data.
To do this through the **classic Azure portal**:
1. Go to https://manage.windowsazure.com/ .
diff --git a/windows/deployment/update/waas-windows-insider-for-business-faq.md b/windows/deployment/update/waas-windows-insider-for-business-faq.md
index 7115a9f6d5..4709203a9c 100644
--- a/windows/deployment/update/waas-windows-insider-for-business-faq.md
+++ b/windows/deployment/update/waas-windows-insider-for-business-faq.md
@@ -16,13 +16,13 @@ ms.author: daniha
- Windows 10
-> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
+> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
### Are the Windows Insider Program and Windows Insider Program for Business separate programs?
No, in fact just the opposite. The Windows Insider Program was created in 2014 to help Microsoft engage with Windows Fans worldwide. Windows Insiders are the first to be able to try new Windows features that we introduce through Windows 10 Insider Preview Builds. At the same time, they can provide feedback through the Feedback Hub App which helps create even better versions of Windows for all users. The Windows Insider Program for Business enables you to incorporate Insider Preview builds into your deployment plans using your corporate credentials, deepen connections with the IT Pro community, collect feedback within your organization, and increase the visibility of your organization’s feedback – especially on features that support productivity and business needs. Together we can resolve blocking or critical issues to better support your organization’s needs sooner. Incorporating the Windows Insider Program for Business into your deployment plans enables you to prepare your organization for the next update of Windows 10, to deploy new services and tools more quickly, to help secure your applications, and to increase productivity and confidence in the stability of your environment. Windows Insider Program for Business participants collaborate with the Windows team to build and document features, infuse innovation, and plan for what’s around the bend. We’ve architected some great features together, received amazing feedback, and we’re not done.
### What Languages are available?
-Insider Preview builds are available in the following languages: English (United States), English (United Kingdom), Chinese (Simplified), Chinese (Traditional), Portuguese (Brazilian), Japanese,Russian, German, French, French (Canada), Korean, Italian, Spanish, Spanish (Latin America), Swedish, Finnish, Turkish, Arabic, Dutch, Czech, Polish, Thai, Catalan, Hindi, and Vietnamese.
+Insider Preview builds are available in the following languages: English (United States), English (United Kingdom), Chinese (Simplified), Chinese (Traditional), Portuguese (Brazilian), Japanese, Russian, German, French, French (Canada), Korean, Italian, Spanish, Spanish (Latin America), Swedish, Finnish, Turkish, Arabic, Dutch, Czech, Polish, Thai, Catalan, Hindi, and Vietnamese.
If your Windows build is not in one of the available base languages, you will not receive Insider Preview builds.
@@ -31,7 +31,7 @@ Hindi, Catalan, and Vietnamese can only be installed as a language pack over [su
>[!NOTE]
> To learn how to install a language pack, see [How to add an input language to your PC Additional](https://support.microsoft.com/instantanswers/60f32ff8-8697-4452-af7d-647439c38433/how-to-add-and-switch-input-languages-on-your-pc).
-### How do I register for the Windows Insider Program for Business?
+### How do I register for the Windows Insider Program for Business?
To register for the Windows Insider Program for Business, follow the steps below using your corporate account in Azure Active Directory (AAD). This account is the same account that you use for Office 365 and other Microsoft services.
1. Visit https://insider.windows.com and click **Get Started**.
@@ -41,12 +41,23 @@ To register for the Windows Insider Program for Business, follow the steps below
>[!NOTE]
>Make sure that you have administrator rights to your machine and that it has latest Windows updates.
+### Are there any management capabilities that allow an IT admin to manage settings for a corporate environment?
+Yes. Starting with Windows 10, version 1709, the Windows Insider Program for Business now enables administrators to apply the following group policies to help them manage their organization’s preview builds:
+
+**Manage preview builds:** Administrators can enable or prevent builds from installing on a device. You also have an option to disable preview builds once the release is public.
+**Branch Readiness Level:** Administrators can set the Windows readiness level, including Fast, Slow, Release Preview Rings of Windows Insider Preview) and allows administrators to defer or pause delivery of updates.
+
+See more information on the [Getting started with Windows Insider Program for Business](waas-windows-insider-for-business.md#getting-started-with-windows-insider-program-for-business) section.
+
### How can I find out if my corporate account is on Azure Active Directory?
On your PC, go to **Settings > Accounts > Access work or school**. If your organization has set up your corporate account in Azure Active Directory and it is connected to your PC, you will see the account listed.
### I have more than one Azure Active Directory account. Which should I use?
Register for Windows Insider Program for Business with the same active account that you use to access your corporate email in Office 365 and other Microsoft services. To ensure you get the most benefit out of the Windows Insider Program for Business and that your company is fully represented, do not set up a separate tenant for testing activities. There will be no modifications to the AAD tenant to support Windows Insider Program for Business, and it will only be used as an authentication method.
+### Can I register multiple users from my organization at the same time for the Windows Insider Program for Business?
+Yes. The Windows Insider Program for Business now allows organizations to register their domain and control settings centrally rather than require each user to register individually for Insider Preview builds. In order to register, follow instructions on the [Getting started with Windows Insider Program for Business](waas-windows-insider-for-business.md#getting-started-with-windows-insider-program-for-business) section.
+
### My account is listed in Active Directory but not Azure Active Directory. Can I still register using my Active Directory credentials?
No. At this point, we are only supporting Azure Active Directory as a corporate authentication method. If you’d like to suggest or upvote another authentication method, please visit this [forum](https://answers.microsoft.com/en-us/insider/forum/insider_wintp).
diff --git a/windows/deployment/update/waas-windows-insider-for-business.md b/windows/deployment/update/waas-windows-insider-for-business.md
index 333ee70f35..d1cc8d07ea 100644
--- a/windows/deployment/update/waas-windows-insider-for-business.md
+++ b/windows/deployment/update/waas-windows-insider-for-business.md
@@ -16,35 +16,54 @@ ms.author: daniha
- Windows 10
-> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
+> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
-For many IT pros, gaining visibility into feature updates early—before they’re available to the CB servicing branch—can be both intriguing and valuable for future end user communications as well as provide additional prestaging for CB machines. With Windows 10, feature flighting enables Windows Insiders to consume and deploy preproduction code to their test machines, gaining early visibility into the next build. Testing the early builds of Windows 10 helps both Microsoft and its customers because they have the opportunity to discover possible issues before the update is ever publicly available and can report it to Microsoft. Also, as flighted builds get closer to their release to CB, organizations can test their deployment on test devices for compatibility validation.
+For many IT pros, gaining visibility into feature updates early, before they’re available to the Semi-Annual Channel, can be both intriguing and valuable for future end user communications as well as provide additional prestaging for Semi-Annual Channel devices. With Windows 10, feature flighting enables Windows Insiders to consume and deploy preproduction code to their test devices, gaining early visibility into the next build. Testing the early builds of Windows 10 helps both Microsoft and its customers because they have the opportunity to discover possible issues before the update is ever publicly available and can report it to Microsoft. Also, as flighted builds get closer to their release to the Semi-Annual Channel, organizations can test their deployment on test devices for compatibility validation.
The Windows Insider Program for Business gives you the opportunity to:
* Get early access to Windows Insider Preview Builds.
* Provide feedback to Microsoft in real-time via the Feedback Hub app.
* Sign-in with corporate credentials (Azure Active Directory) and increase the visibility of your organization's feedback with Microsoft – especially on features that support your productivity and business needs.
+* Register your Azure AD domain into the program, to cover all users within your organization with just one registration.
+* Starting with Windows 10, version 1709, enable, disable, defer and pause the installation of preview builds through policies.
+* Track feedback provided through the Feedback Hub app, across your organization.
Microsoft recommends that all organizations have at least a few PCs enrolled in the Windows Insider Program, to include the Windows Insider Program in their deployment plans and to provide feedback on any issues they encounter to Microsoft via our Feedback Hub app.
-The Windows Insider Program isn’t intended to replace CB deployments in an organization. Rather, it provides IT pros and other interested parties with pre-release Windows builds that they can test and ultimately provide feedback on to Microsoft.
+The Windows Insider Program isn’t intended to replace Semi-Annual Channel deployments in an organization. Rather, it provides IT pros and other interested parties with pre-release Windows builds that they can test and ultimately provide feedback on to Microsoft.
+
+>[!IMPORTANT]
+>The **Allow Telemetry** setting has to be set to 2 or higher, to receive Insider preview builds.
+>
+>The setting is available in **Group Policy**, through **Computer Configuration/Administrative Templates/Windows Components/Data Collection and Preview Builds - Allow Telemetry** or in **MDM**, through **System/AllowTelemetry**.
## Getting started with Windows Insider Program for Business
To get started with the Windows Insider Program for Business, you will need to follow a few simple steps:
-1. Navigate to [insider.windows.com](https://insider.windows.com) and go to **Get Started**.
-2. Sign-in with you desired account. It can be either a Microsoft Account or your organizational Azure Active Directory Account.
+1. On the [Windows Insider](https://insider.windows.com) website, go to **For Business > Getting Started** to [register you organizational Azure AD account](https://insider.windows.com/en-us/insidersigninaad/).
+2. **Register your domain**. Rather than have each user register individually for Insider Preview builds, administrators can simply [register their domain](https://insider.windows.com/en-us/for-business-organization-admin/) and control settings centrally.**Note:** The signed-in user needs to be a **Global Administrator** of the Azure AD domain in order to be able to register the domain.
+3. Make sure the **Allow Telemetry** setting is set to **2** or higher.
+4. Starting with Windows 10, version 1709, set policies to manage preview builds and their delivery:
-
+The **Manage preview builds** setting, gives administrators control over enabling or disabling preview build installation on a device. You can also decide to stop preview builds once the release is public.
+* Group Policy: **Computer Configuration/Administrative Templates/Windows Components/Windows Update/Windows Update for Business** - *Manage preview builds*
+* MDM: **Update/ManagePreviewBuilds**
+The **Branch Readiness Level** settings, allows you to choose between preview flight rings, and allows you to defer or pause the delivery of updates.
+* Group Policy: **Computer Configuration/Administrative Templates/Windows Components/Windows Update/ Windows Update for Business** - *Select when Preview Builds and Feature Updates are received*
+* MDM: **Update/BranchReadinessLevel**
+
+
+
+If you want to control Windows 10 devices prior to version 1709, follow these simple steps:
+
+1. Navigate to the [**Getting Started**](https://insider.windows.com/en-us/getting-started/) page on [Windows Insider](https://insider.windows.com).
+2. Go to the **Register your organization account** and follow the instructions.
3. Enroll your device by going to **Start > Settings > Update & security > Windows Insider Program** and selecting **Get Started**. Sign-in using the account you used to register for the Windows Insider Program.
4. After reading the privacy statement and clicking **Next**, **Confirm** and schedule a restart.
-
-## Install your first preview build from the Windows Insider Program
-
-After enrolling your devices, you are ready to install your first preview build. To do so, go to **Start** > **Settings** > **Update & security** > **Windows Insider Program** to select your Insider level. The device receives the most recent Windows Insider build for the Insider level you select.
+5. You are ready to install your first preview build. To do so, go to **Start** > **Settings** > **Update & security** > **Windows Insider Program** to select your Insider level. The device receives the most recent Windows Insider build for the Insider level you select.
>[!TIP]
>Flighting rings are used to evaluate the quality of our software as it is released to progressively larger audiences. We will flight a Feature Update, application, etc. to the first ring if it passes all required automated testing in the lab. The flight will continue to be evaluated against a set of criteria to ensure it is ready to progress to the next ring.
@@ -53,12 +72,12 @@ The options for Insider level are:
### Release Preview
-Best for Insiders who enjoy getting early access to updates for the Current Branch, Microsoft applications, and drivers, with minimal risk to their devices, and still want to provide feedback to make Windows devices great.
+Best for Insiders who enjoy getting early access to updates for the Semi-Annual Channel, Microsoft applications, and drivers, with minimal risk to their devices, and still want to provide feedback to make Windows devices great.
-Insiders on this level receive builds of Windows just before Microsoft releases them for CB. Although these builds aren’t final, they are the most complete and stable builds available to Windows Insider Program participants. This level provides the best testing platform for organizations that conduct early application compatibility testing on Windows Insider PCs.
+Insiders on this level receive builds of Windows just before Microsoft releases them to the Semi-Annual Channel. Although these builds aren’t final, they are the most complete and stable builds available to Windows Insider Program participants. This level provides the best testing platform for organizations that conduct early application compatibility testing on Windows Insider PCs.
-* The Release Preview Ring will only be visible when your Windows build version is the same as the Current Branch.
-* The easiest way to go between the Development Branch to the Current Branch is to use the [Media Creation Tool](http://go.microsoft.com/fwlink/?LinkId=691209) (for PC) or [Windows Device Recovery Tool](http://go.microsoft.com/fwlink/p/?LinkId=522381) (for Mobile) to reinstall Windows.
+* The Release Preview Ring will only be visible when your Windows build version is the same as the Semi-Annual Channel.
+* The easiest way to go from a Preview build to the Semi-Annual Channel is to use the [Media Creation Tool](http://go.microsoft.com/fwlink/?LinkId=691209) (for PC) or [Windows Device Recovery Tool](http://go.microsoft.com/fwlink/p/?LinkId=522381) (for Mobile) to reinstall Windows.
### Slow
@@ -70,12 +89,12 @@ The Slow Windows Insider level is for users who enjoy seeing new builds of Windo
### Fast
-Best for Insiders who enjoy being the first to get access to builds and feature upgrades, with some risk to their devices in order to identify issues, and provide suggestions and ideas to make Windows software and devices great.
+Best for Insiders who enjoy being the first to get access to builds and feature updates, with some risk to their devices in order to identify issues, and provide suggestions and ideas to make Windows software and devices great.
* Windows Insiders with devices in the Fast Ring should be prepared for more issues that may block key activities that are important to you or may require significant workarounds.
* Because we are also validating a build on a smaller set of devices before going to Fast, there is also a chance that some features may work on some devices but may fail in other device configurations.
* Windows Insiders should be ready to reinstall Windows using the [Media Creation Tool](http://go.microsoft.com/fwlink/?LinkId=691209) or [Windows Device Recovery Tool](http://go.microsoft.com/fwlink/p/?LinkId=522381) when you are significantly blocked.
-* Please remember to report any issue to us through the Windows Insider Feedback Hub or the Windows Insider community Forum.
+* Please remember to report any issue to us through the Windows Insider Feedback Hub or the Windows Insider community forum.
>[!NOTE]
>Once your machine is updated to Windows 10 and you select your desired flight ring, the process known as "Compatibility check" will need to run in the background. There is no manual way to force this process to run. This process allows for the discovery of your OS type (32-bit, 64-bit), build edition (Home, Pro, Enterprise), country and language settings, and other required information. Once this process is complete, your machine will be auto-targeted for the next available flight for your selected ring. For the first build on any given machine, this may take up to 24 hours to complete.
@@ -90,11 +109,16 @@ During your time in the Windows Insider Program, you may want to change between
* [Windows Insider Slow](#slow)
* [Release Preview](#release-preview)
+Starting with Windows 10, version 1709, use the **Branch Readiness Level** to switch between flight rings.
+* Group Policy: **Computer Configuration/Administrative Templates/Windows Components/Windows Update/ Windows Update for Business** - *Select when Preview Builds and Feature Updates are received*
+* MDM: **Update/BranchReadinessLevel**
+
## How to switch between your MSA and your Corporate AAD account
The Windows Insider Program for Business now gives users the option to register and enroll devices using a corporate account in [Azure Active Directory](https://azure.microsoft.com/services/active-directory/) (AAD) as well as their Microsoft Account (MSA).
To switch between accounts, go to **Settings > Updates & Security > Windows Insider Program**, and under **Windows Insider account** select **Change**.
+
>[!NOTE]
@@ -108,6 +132,9 @@ When providing feedback, please consider the following:
2. Check for existing feedback on the topic you are preparing to log. Another user may have already shared the same feedback. If they have, please “upvote” the existing feedback to help prevent duplicate submissions. Adding additional comments to existing feedback can help others by providing clarity to existing information or additional scenarios to review.
3. Provide as much information to us as possible: include reproduction steps, screenshots, any detail you think would help us experience the issue as you have, so that we can work on a fix and get it into a new build as soon as possible.
+>[!TIP]
+>You can then track feedback provided by all users in your organization through the Feedback Hub. Simply filter by **My Organization**.
+
### How to use your corporate AAD account for additional Feedback Hub benefits
Get even more out of the Feedback Hub by signing in to the Feedback Hub using the same corporate account in AAD that you're using to flight builds. One of the benefits of submitting feedback using your AAD account is the addition of a page to the Feedback Hub for your organization. Simply click the **My Company** page in the feedback hub to see and upvote all feedback submitted by other Insiders in your organization.
@@ -115,9 +142,9 @@ Get even more out of the Feedback Hub by signing in to the Feedback Hub using th
>If you signed into the Feedback Hub previously with your MSA, your feedback and badges will not be transferred to your AAD sing-in. However, you can switch back to your MSA account in the Feedback Hub to access feedback you’ve submitted and badges you’ve earned.
>[!IMPORTANT]
->With the current version of the Feedback Hub app, we need the user's consent to access their AAD account profile data (We read their name, organizational tenant ID and user ID). When they sign in for the first time with the AAD account, they will se a popup asking for their permissions. Once agreed, everything will work fine and that user won't be asked for permissions again.
+>With the current version of the Feedback Hub app, we need the user's consent to access their AAD account profile data (We read their name, organizational tenant ID and user ID). When they sign in for the first time with the AAD account, they will see a popup asking for their permissions. Once agreed, everything will work fine, and that user won't be asked for permissions again.
>
-> If something goes wrong, it is possible that users aren't enabled to give persmissions to access their data. This can be resolved through the AAD portal. For more information about this, please see [User consent requirement](waas-windows-insider-for-business-aad.md#user-consent-requirement).
+> If something goes wrong, it is possible that users aren't enabled to give permissions to access their data. This can be resolved through the AAD portal. For more information about this, please see [User consent requirement](waas-windows-insider-for-business-aad.md#user-consent-requirement).
## Not receiving Windows 10 Insider Preview build updates?
@@ -142,10 +169,10 @@ Open **Settings > Update & Security > Windows Insider Program** and select your
If so, please double-check your flight settings under **Settings > Update & Security > Windows Insider Program**.
### Did you do a clean install?
-After a clean-install and initial setup of a Microsoft or coporate account (even one that has been used previously for flighting) the appropriate targeting needs to take place for your PC. This background process is known as Compatibility Checker and will run during idle time on your PC. This process may take up to 24 hours. Please leave your PC turned on to ensure this occurs in timely manner.
+After a clean-install and initial setup of a Microsoft or corporate account (even one that has been used previously for flighting) the appropriate targeting needs to take place for your PC. This background process is known as Compatibility Checker and will run during idle time on your PC. This process may take up to 24 hours. Please leave your PC turned on to ensure this occurs in timely manner.
### Are there known issues for your current build?
-On rare occasion, there may be an issue with a build that could lead to issues with updates being received. Please check the most recent Blog Post or reach out to the Windows Insider team on Twitter for verification (*@WindowsInsider*). You can also check the **Feedback Hub** for announcments and known issues.
+On rare occasion, there may be an issue with a build that could lead to issues with updates being received. Please check the most recent Blog Post or reach out to the Windows Insider team on Twitter for verification (*@WindowsInsider*). You can also check the **Feedback Hub** for announcements and known issues.
## Exiting flighting
@@ -154,6 +181,7 @@ After you’ve tried the latest Insider Preview builds, you may want to opt out.
## Additional help resources
* [**Windows Blog**](https://blogs.windows.com/blog/tag/windows-insider-program/) - With each new build release we publish a Windows Blog post that outlines key feature changes as well as known issues that Insiders may encounter while using the build.
+* [**Microsoft Technical Community for Windows Insiders**](https://techcommunity.microsoft.com/t5/Windows-Insider-Program/bd-p/WindowsInsiderProgram) - Engage with Windows Insiders around the world in a community dedicated to the Windows Insider Program.
* [**Windows Insider Preview community forum**](https://answers.microsoft.com/en-us/insider/forum/insider_wintp) - Answers is Microsoft’s forum platform and there is an entire area dedicated to the Windows Insider Program. Insiders can filter between PC, Office, Edge, and many others.
## Learn More
@@ -165,7 +193,7 @@ After you’ve tried the latest Insider Preview builds, you may want to opt out.
- [Overview of Windows as a service](waas-overview.md)
- [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md)
- [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md)
-- [Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md)
+- [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md)
- [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md)
- [Manage updates using Windows Update for Business](waas-manage-updates-wufb.md)
- [Manage Windows 10 updates using Windows Server Update Services (WSUS)](waas-manage-updates-wsus.md)
diff --git a/windows/whats-new/get-started-with-1709.md b/windows/whats-new/get-started-with-1709.md
new file mode 100644
index 0000000000..d9a5849869
--- /dev/null
+++ b/windows/whats-new/get-started-with-1709.md
@@ -0,0 +1,45 @@
+---
+title: Get started with Windows 10, version 1709
+description: All the information to get you started with Windows 10, version 1709.
+keywords: ["get started", "windows 10", "fall creators update", "1709"]
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+author: DaniHalfin
+ms.author: daniha
+ms.date: 10/17/2017
+ms.localizationpriority: high
+---
+
+# Get started with Windows 10, version 1709
+
+**Applies to**
+
+- Windows 10
+
+> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
+
+Welcome to Windows 10, version 1709, also known as the Fall Creators Update. Use the following information to learn about new features, review system requirements, and plan your deployment of the latest version of Windows 10.
+
+## Specification and systems requirements
+
+Before you install any version of Windows 10, make sure you visit the [Windows 10 Specifications & Systems Requirements](https://www.microsoft.com/windows/windows-10-specifications) page. This page contains the minimum systems requirements and important notes to install Windows 10, as well as feature deprecation information and additional requirements to use certain features.
+
+## What's new in Windows 10, version 1709 IT pro content
+
+Take a look at the [What's new in Windows 10, version 1709 IT pro content](whats-new-windows-10-version-1709), for the latest updates in content. Use this topic to easily navigate the documentation for the new features in Windows 10, version 1709.
+
+## Windows 10 release information and update history
+
+To view availability dates and servicing options for each version and update of Windows, including version 1709, visit the [Windows 10 release information](https://technet.microsoft.com/windows/mt679505.aspx) page. For further details on each update, go to the [Windows 10 update history](https://support.microsoft.com/help/4018124/windows-10-update-history) page.
+
+## Windows 10 Roadmap
+
+If you'd like to gain some insight into preview, or in-development features, visit the [Windows 10 Roadmap](https://www.microsoft.com/en-us/WindowsForBusiness/windows-roadmap) page. You'll be able to filter by feature state and product category, to make this information easier to navigate.
+
+## Top support solutions for Windows 10
+
+Having problems with your latest deployment of Windows 10, version 1709? Check out the [Top support solutions for Windows 10](/windows/client-management/windows-10-support-solutions) topic, where we've collected the top Microsoft Support solutions for the most common issues experienced when using Windows 10 in an enterprise or IT pro environment.
+
+
+> Want even more information? Visit the [Windows 10 lifecycle page](https://www.microsoft.com/itpro/windows-10) on the [Windows IT Pro Center](https://itpro.windows.com).
\ No newline at end of file