mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
resolving merge conflict?
This commit is contained in:
jaimeo
@ -235,10 +235,6 @@
|
||||
### [Manage device restarts after updates](update/waas-restart.md)
|
||||
### [Manage additional Windows Update settings](update/waas-wu-settings.md)
|
||||
### [Determine the source of Windows updates](update/windows-update-sources.md)
|
||||
### [Windows Insider Program for Business](update/waas-windows-insider-for-business.md)
|
||||
#### [Introduction to the Windows Insider Program for Business](update/WIP4Biz-intro.md)
|
||||
#### [Windows Insider Program for Business Frequently Asked Questions](update/waas-windows-insider-for-business-faq.md)
|
||||
#### [Olympia Corp enrollment](update/olympia/olympia-enrollment-guidelines.md)
|
||||
### [Change history for Update Windows 10](update/change-history-for-update-windows-10.md)
|
||||
|
||||
## [Windows Analytics](update/windows-analytics-overview.md)
|
||||
|
||||
@ -29,7 +29,7 @@ Windows Update for Business enables information technology administrators to kee
|
||||
|
||||
Specifically, Windows Update for Business allows for:
|
||||
|
||||
- The creation of deployment rings, where administrators can specify which devices go first in an update wave, and which ones will come later (to ensure any quality bars are met).
|
||||
- The creation of deployment rings, where administrators can specify which devices go first in an update wave, and which ones will come later (to allow for reliability and performance testing on a subset of systems before rolling out updates across the organization).
|
||||
- Selectively including or excluding drivers as part of Microsoft-provided updates
|
||||
- Integration with existing management tools such as Windows Server Update Services (WSUS), System Center Configuration Manager, and Microsoft Intune.
|
||||
- Peer-to-peer delivery for Microsoft updates, which optimizes bandwidth efficiency and reduces the need for an on-site server caching solution.
|
||||
|
||||
@ -70,7 +70,7 @@ To align with this new update delivery model, Windows 10 has three servicing cha
|
||||
### Naming changes
|
||||
|
||||
As part of the alignment with Windows 10 and Office 365 ProPlus, we are adopting common terminology to make it as easy as possible to understand the servicing process. Going forward, these are the new terms we will be using:
|
||||
* Semi-Annual Channel - We will be referreing to Current Branch (CB) as "Semi-Annual Channel (Targeted)", while Current Branch for Business (CBB) will simply be referred to as "Semi-Annual Channel".
|
||||
* Semi-Annual Channel - We will be referring to Current Branch (CB) as "Semi-Annual Channel (Targeted)", while Current Branch for Business (CBB) will simply be referred to as "Semi-Annual Channel".
|
||||
* Long-Term Servicing Channel - The Long-Term Servicing Branch (LTSB) will be referred to as Long-Term Servicing Channel (LTSC).
|
||||
|
||||
>[!IMPORTANT]
|
||||
|
||||
@ -1,123 +0,0 @@
|
||||
---
|
||||
title: Windows Insider Program for Business using Azure Active Directory
|
||||
description: Benefits and configuration of corporate accounts in the Windows Insider Program
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: DaniHalfin
|
||||
ms.localizationpriority: medium
|
||||
ms.author: daniha
|
||||
ms.date: 10/16/2017
|
||||
---
|
||||
|
||||
# Windows Insider Program for Business using Azure Active Directory
|
||||
|
||||
|
||||
**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)
|
||||
|
||||
We recently added features and benefits to better support the IT Professionals and business users in our Windows 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.
|
||||
|
||||
>[!NOTE]
|
||||
>At this point, the Windows Insider Program for Business only supports Azure Active Directory (and not Active Directory on premises) as a corporate authentication method.
|
||||
|
||||
>[!TIP]
|
||||
>New to Azure Active Directory? Go here for [an introduction to AAD](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect), including guidance for [adding users](https://docs.microsoft.com/azure/active-directory/active-directory-users-create-azure-portal), [device registration](https://docs.microsoft.com/azure/active-directory/active-directory-device-registration-overview) and [integrating your on-premises directories with Azure AD](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect).
|
||||
>
|
||||
>If your company is currently not using AAD – but has a paid subscription to Office 365, Microsoft Dynamics CRM Online, Enterprise Mobility Suite, or other Microsoft services – you have a free subscription to Microsoft Azure Active Directory. This subscription can be used to create users for enrollment in the Windows Insider Program for Business.
|
||||
|
||||
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 your organizational Azure AD account](https://insider.windows.com/en-us/insidersigninaad/).
|
||||
2. **Register your domain**. Rather than have each user register individually for Windows 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. Navigate to the [**Getting Started**](https://insider.windows.com/en-us/getting-started/) page on [Windows Insider](https://insider.windows.com).
|
||||
2. Go to **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.
|
||||
|
||||
## Switch device enrollment from your Microsoft account to your AAD account
|
||||
1. Visit [insider.windows.com](https://insider.windows.com) to register your AAD account. If you are signed in with your Microsoft account, sign out, then sign back in with your corporate AAD account.
|
||||
2. Click **Get started**, read and accept the privacy statement and program terms and click **Submit**.
|
||||
3. On your Windows 10 PC, go to **Settings > Updates & Security > Windows Insider Program**.
|
||||
4. Under Windows Insider account, click your Microsoft account, then **Change** to open a Sign In box.
|
||||
5. Select your corporate account and click Continue to change your account.
|
||||
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>Your device must be connected to your corporate account in AAD for the account to appear in the account list.
|
||||
|
||||
## User consent requirement
|
||||
|
||||
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 permission, like this:
|
||||
|
||||
|
||||
|
||||
Once agreed, everything will work fine, and that user won't be prompted for permission again.
|
||||
|
||||
### Something went wrong
|
||||
|
||||
The option for users to give consent for apps to access their profile data is controlled through Azure Active Directory. This means the AAD administrators have the ability to allow or block users from giving consent.
|
||||
|
||||
In case the administrators blocked this option, when the user signs in with the AAD account, they will see the following error message:
|
||||
|
||||
|
||||
|
||||
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 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/ .
|
||||
2. Switch to the **Active Directory** dashboard.
|
||||
|
||||
3. Select the appropriate directory and go to the **Configure** tab.
|
||||
4. Under the **integrated applications** section, enable **Users may give applications permissions to access their data**.
|
||||
|
||||
|
||||
To do this through the **new Azure portal**:
|
||||
1. Go to https://portal.azure.com/ .
|
||||
2. Switch to the **Active Directory** dashboard.
|
||||
|
||||
3. Switch to the appropriate directory.
|
||||
|
||||
4. Under the **Manage** section, select **User settings**.
|
||||
|
||||
5. In the **Enterprise applications** section, enable **Users can allow apps to access their data**.
|
||||
|
||||
|
||||
|
||||
## Frequently Asked Questions
|
||||
|
||||
### Will my test machines be affected by automatic registration?
|
||||
All devices enrolled in the Windows Insider Program (physical or virtual) will receive Windows 10 Insider Preview builds (regardless of registration with MSA or AAD).
|
||||
|
||||
### Once I register with my corporate account in AAD, do I need to keep my Microsoft account for the Windows Insider Program?
|
||||
No, once you set up your device using AAD credentials – all feedback and flighting on that machine will be under your AAD account. You may need MSA for other machines that aren’t being used on your corporate network or to get Microsoft Store App updates.
|
||||
|
||||
### How do I stop receiving updates?
|
||||
You can simply “unlink” your account by going to **Settings > Updates & Security > Windows Insider Program**, select Windows Insider Account and click **Unlink**.
|
||||
|
||||
|
||||
## Related Topics
|
||||
- [Windows Insider Program for Business](waas-windows-insider-for-business.md)
|
||||
- [Windows Insider Program for Business Frequently Asked Questions](waas-windows-insider-for-business-faq.md)
|
||||
@ -1,106 +0,0 @@
|
||||
---
|
||||
title: Windows Insider Program for Business Frequently Asked Questions
|
||||
description: Frequently Asked Questions and answers about the Windows Insider Program
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: DaniHalfin
|
||||
ms.localizationpriority: medium
|
||||
ms.author: daniha
|
||||
ms.date: 10/24/2017
|
||||
---
|
||||
|
||||
# Windows Insider Program for Business Frequently Asked Questions
|
||||
|
||||
|
||||
**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)
|
||||
|
||||
### 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.
|
||||
|
||||
If your Windows build is not in one of the available base languages, you will not receive Insider Preview builds.
|
||||
|
||||
Hindi, Catalan, and Vietnamese can only be installed as a language pack over [supported base languages](https://support.microsoft.com/help/14236/language-packs).
|
||||
|
||||
>[!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?
|
||||
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**.
|
||||
2. Sign-in with your corporate account in AAD (username/password) and follow the on-screen registration directions.
|
||||
3. Enroll your Windows 10 PC to get the latest Windows 10 Insider Preview builds. Go to **Settings > Updates & Security > Windows Insider Program**. Click **Get Started**, enter your corporate credentials that you used to register, then follow the on-screen directions.
|
||||
|
||||
>[!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](/windows-insider/at-work-pro/wip-4-biz-get-started) section.
|
||||
|
||||
### <a id="connected-to-aad"> </a>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 as highlighted in the image below.
|
||||
|
||||
|
||||
|
||||
### 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](/windows-insider/at-work-pro/wip-4-biz-get-started) 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).
|
||||
|
||||
### I just want to participate as a Windows Insider. Do I still need to register with my corporate account in Azure Active Directory?
|
||||
No. You can join using your Microsoft account (MSA) by following the steps below. However, please note that if you want to access the benefits of the Windows Insider Program for Business, you will need to sign-up using your corporate account in Azure Active Directory.
|
||||
|
||||
1. Visit https://insider.windows.com and click Get Started.
|
||||
2. Register with your Microsoft account and follow the on-screen registration directions.
|
||||
3. Enroll your Windows 10 PC to get the latest Windows 10 Insider Preview builds by going to **Settings > Updates & Security > Windows Insider Program** and entering your Microsoft account that you used to register. Now follow the on-screen directions.
|
||||
|
||||
>[!NOTE]
|
||||
>Make sure that you have administrator rights to your machine and that it has latest Windows updates.
|
||||
|
||||
### I am already a Windows Insider. I want to switch my account from my Microsoft account to my corporate account in Azure Active Directory. How do I do this?
|
||||
In just a few steps, you can switch your existing program registration from your Microsoft account to your corporate account in Azure Active Directory.
|
||||
|
||||
1. Visit https://insider.windows.com. If you are signed in with your Microsoft account, sign out then sign back in to register with your corporate account in AAD.
|
||||
2. On your Windows 10 PC, go to **Settings > Updates & Security > Windows Insider Program**.
|
||||
3. In your account Under Windows Insider account, click **Change** to open a pop-up box.
|
||||
4. Select your corporate account and click Continue to change your account.
|
||||
|
||||
>[!NOTE]
|
||||
>Your corporate account must be connected to the device for it to appear in the account list.
|
||||
|
||||
### How do I sign into the Feedback Hub with my corporate credentials?
|
||||
Sign in to the Feedback Hub using the same AAD account you are using to flight builds.
|
||||
|
||||
### Am I going to lose all the feedback I submitted and badges I earned with my MSA?
|
||||
No. However, your feedback will not be transferred from your MSA to your AAD account. You can switch back to your MSA account in the Feedback Hub to access feedback you’ve submitted and badges you’ve earned.
|
||||
|
||||
### How is licensing handled for Windows 10 Insider builds?
|
||||
All PCs need to have a valid Windows 10 license. This requirement applies whether the device is joined to the Windows Insider Program using a Microsoft account or an Azure Active Directory account.
|
||||
|
||||
### Can I use the Software in a live operating environment?
|
||||
The software is a pre-release version, and we do not recommend that organizations run Windows Insider Preview builds outside of their test environments. This software may not work the way a final version of the software will. We may change it for the final, commercial version. We also may not release a commercial version.
|
||||
|
||||
### Can a single MSA or AAD account be used to register more than one PC in the program?
|
||||
Yes. If each PC has a valid Windows 10 or Windows 10 Mobile license you can use your MSA on as many devices as you’d like. However, the main concern would be that within the feedback it all looks like it comes from a single user. If multiple devices are experiencing problems with a build, you’d want the ability to submit the same feedback from multiple people (or upvote the same piece of feedback).
|
||||
|
||||
|
||||
## Related Topics
|
||||
- [Windows Insider Program for Business](waas-windows-insider-for-business.md)
|
||||
- [Windows Insider Program for Business using Azure Active Directory](waas-windows-insider-for-business-aad.md)
|
||||
@ -99,6 +99,7 @@ If you know that devices are experiencing stop error crashes that do not seem to
|
||||
[](images/event_1001.png)
|
||||
|
||||
You can use the following Windows PowerShell snippet to summarize recent occurences of Event 1001. Most events should have a value for BucketID (a few intermittent blank values are OK, however).
|
||||
<<<<<<< HEAD
|
||||
|
||||
```powershell
|
||||
|
||||
@ -148,6 +149,53 @@ If apps that you know are crashing do not appear in App Reliability, follow thes
|
||||
|
||||
3. Verify that *per-user* Windows Error Reporting (WER) is not disabled or redirected by confirming the registry settings in **HKCU\SOFTWARE\Microsoft\Windows\Windows Error Reporting** (or **HKCU\Software\Policies\Microsoft\Windows\DataCollection**, which will take precedence if set):
|
||||
|
||||
=======
|
||||
|
||||
```powershell
|
||||
$limitToMostRecentNEvents = 20
|
||||
Get-WinEvent -FilterHashTable @{ProviderName="Windows Error Reporting"; ID=1001} |
|
||||
?{ $_.Properties[2].Value -match "crash|blue" } |
|
||||
% { [pscustomobject]@{
|
||||
TimeCreated=$_.TimeCreated
|
||||
WEREvent=$_.Properties[2].Value
|
||||
BucketId=$_.Properties[0].Value
|
||||
ContextHint = $(
|
||||
if($_.Properties[2].Value -eq "bluescreen"){"kernel"}
|
||||
else{ $_.Properties[5].Value }
|
||||
)
|
||||
}} | Select-Object -First $limitToMostRecentNEvents
|
||||
```
|
||||
The output should look something like this:
|
||||
[](images/device-reliability-event1001-PSoutput.png)
|
||||
|
||||
6. Check that some other installed device, app, or crash monitoring solution is not intercepting crash events.
|
||||
7. Wait 48 hours for activity to appear in the reports.
|
||||
8. If you need additional troubleshooting, contact Microsoft Support.
|
||||
|
||||
#### Endpoint connectivity
|
||||
|
||||
Devices must be able to reach the endpoints specified in [Enrolling devices in Windows Analytics](windows-analytics-get-started.md).
|
||||
|
||||
If you are using proxy server authentication, it's worth taking extra care to check the configuration. Prior to Windows 10, version 1703, WER only uploads error reports in the machine context, so whitelisting endpoints to allow non-authenticated access was typically used. In Windows 10, version 1703 and later versions, WER will attempt to use the context of the user that is logged on for proxy authentication such that only the user account requires proxy access.
|
||||
|
||||
|
||||
For more information, see [Enrolling devices in Windows Analytics](windows-analytics-get-started.md#configuring-endpoint-access-with-proxy-server-authentication).
|
||||
|
||||
### Apps not appearing in Device Health App Reliability
|
||||
|
||||
[](images/app-reliability.png)
|
||||
|
||||
If apps that you know are crashing do not appear in App Reliability, follow these steps to investigate the issue:
|
||||
|
||||
1. Double-check the steps in the [Devices not appearing in Device Health Device Reliability](#devices-not-appearing-in-device-health-device-reliability) and [Device crashes not appearing in Device Health Device Reliability](#device-crashes-not-appearing-in-device-health-device-reliability) sections of this topic.
|
||||
2. Confirm that an in-scope application has crashed on an enrolled device. Keep the following points in mind:
|
||||
- Not all user-mode crashes are included in App Reliability, which tracks only apps that have a GUI, have been used interactively by a user, and are not part of the operating system.
|
||||
- Enrolling more devices helps to ensure that there are enough naturally occurring app crashes.
|
||||
- You can also use test apps which are designed to crash on demand.
|
||||
|
||||
3. Verify that *per-user* Windows Error Reporting (WER) is not disabled or redirected by confirming the registry settings in **HKCU\SOFTWARE\Microsoft\Windows\Windows Error Reporting** (or **HKCU\Software\Policies\Microsoft\Windows\DataCollection**, which will take precedence if set):
|
||||
|
||||
>>>>>>> 3e50323e04da8c8c155ca39ad5e95f7e4447b349
|
||||
- Verify that the value "Disabled" (REG_DWORD), if set, is 0.
|
||||
- Verify that the value "DontSendAdditionalData" (REG_DWORD), if set, is 0.
|
||||
- Verify that the value "CorporateWERServer" (REG_SZ) is not configured.
|
||||
|
||||
@ -6,7 +6,7 @@ ms.localizationpriority: medium
|
||||
ms.prod: w10
|
||||
author: jaimeo
|
||||
ms.author: jaimeo
|
||||
ms.date: 08/30/2017
|
||||
ms.date: 07/31/2018
|
||||
---
|
||||
|
||||
# Use Upgrade Readiness to manage Windows upgrades
|
||||
@ -22,7 +22,7 @@ When you are ready to begin the upgrade process, a workflow is provided to guide
|
||||
|
||||
Each step in the workflow is enumerated using blue tiles. Helpful data is provided on white tiles to help you get started, to monitor your progress, and to complete each step.
|
||||
|
||||
>**Important**: You can use the [Target version](#target-version) setting to evaluate computers that are runnign a specified version of Windows before starting the Upgrade Readiness workflow. By default, the Target version is configured to the released version of Windows 10 for the Current Branch for Business (CBB).
|
||||
>**Important**: You can use the [Target version](#target-version) setting to evaluate computers that are running a specified version of Windows before starting the Upgrade Readiness workflow. By default, the Target version is configured to the released version of Windows 10 for the Current Branch for Business (CBB).
|
||||
|
||||
The following information and workflow is provided:
|
||||
|
||||
@ -41,11 +41,11 @@ The target version setting is used to evaluate the number of computers that are
|
||||
|
||||
|
||||
|
||||
As mentioned previously, the default target version in Upgrade Readiness is set to the released version of the Current Branch for Business (CBB). CBB can be determined by reviewing [Windows 10 release information](https://technet.microsoft.com/windows/release-info.aspx). The target version setting is used to evaluate the number of computers that are already running this version of Windows, or a later version.
|
||||
The default target version in Upgrade Readiness is set to the released version of the Current Branch for Business (CBB). CBB can be determined by reviewing [Windows 10 release information](https://technet.microsoft.com/windows/release-info.aspx). The target version setting is used to evaluate the number of computers that are already running this version of Windows, or a later version.
|
||||
|
||||
The number displayed under **Computers upgraded** in the Upgrade Overview blade is the total number of computers that are already running the same or a later version of Windows compared to the target version. It also is used in the evaluation of apps and drivers: Known issues and guidance for the apps and drivers in Upgrade Readiness is based on the target operating system version.
|
||||
|
||||
You now have the ability to change the Windows 10 version you wish to target. The available options currently are: Windows 10 version 1507, Windows 10 version 1511, Windows 10 version 1607, and Windows 10 version 1703.
|
||||
You now have the ability to change the Windows 10 version you wish to target. The available options currently are: Windows 10 version 1507, Windows 10 version 1511, Windows 10 version 1607, Windows 10 version 1703, Windows 10 version 1709 and Windows 10 version 1803.
|
||||
|
||||
To change the target version setting, click on **Solutions Settings**, which appears at the top when you open you Upgrade Readiness solution:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user