mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
Merge branch 'main' of https://github.com/MicrosoftDocs/windows-docs-pr into dep-apst1-9183716
This commit is contained in:
Meghan Stewart
commit
f1b1e039c6
41
.github/workflows/AutoLabelAssign.yml
vendored
Normal file
41
.github/workflows/AutoLabelAssign.yml
vendored
Normal file
@ -0,0 +1,41 @@
|
||||
name: Assign and label PR
|
||||
|
||||
permissions:
|
||||
pull-requests: write
|
||||
contents: read
|
||||
actions: read
|
||||
|
||||
on:
|
||||
workflow_run:
|
||||
workflows: [Background tasks]
|
||||
types:
|
||||
- completed
|
||||
|
||||
jobs:
|
||||
download-payload:
|
||||
name: Download and extract payload artifact
|
||||
uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-ExtractPayload.yml@workflows-prod
|
||||
with:
|
||||
WorkflowId: ${{ github.event.workflow_run.id }}
|
||||
OrgRepo: ${{ github.repository }}
|
||||
secrets:
|
||||
AccessToken: ${{ secrets.GITHUB_TOKEN }}
|
||||
|
||||
label-assign:
|
||||
name: Run assign and label
|
||||
needs: [download-payload]
|
||||
uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoLabelAssign.yml@workflows-prod
|
||||
with:
|
||||
PayloadJson: ${{ needs.download-payload.outputs.WorkflowPayload }}
|
||||
AutoAssignUsers: 1
|
||||
AutoLabel: 1
|
||||
ExcludedUserList: '["user1", "user2"]'
|
||||
ExcludedBranchList: '["branch1", "branch2"]'
|
||||
secrets:
|
||||
AccessToken: ${{ secrets.GITHUB_TOKEN }}
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
40
.github/workflows/AutoLabelMsftContributor.yml
vendored
Normal file
40
.github/workflows/AutoLabelMsftContributor.yml
vendored
Normal file
@ -0,0 +1,40 @@
|
||||
name: Auto label Microsoft contributors
|
||||
|
||||
permissions:
|
||||
pull-requests: write
|
||||
contents: read
|
||||
actions: read
|
||||
|
||||
on:
|
||||
workflow_run:
|
||||
workflows: [Background tasks]
|
||||
types:
|
||||
- completed
|
||||
|
||||
jobs:
|
||||
download-payload:
|
||||
if: github.repository_visibility == 'public'
|
||||
name: Download and extract payload artifact
|
||||
uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-ExtractPayload.yml@workflows-prod
|
||||
with:
|
||||
WorkflowId: ${{ github.event.workflow_run.id }}
|
||||
OrgRepo: ${{ github.repository }}
|
||||
secrets:
|
||||
AccessToken: ${{ secrets.GITHUB_TOKEN }}
|
||||
|
||||
label-msft:
|
||||
name: Label Microsoft contributors
|
||||
if: github.repository_visibility == 'public'
|
||||
needs: [download-payload]
|
||||
uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoLabelMsftContributor.yml@workflows-prod
|
||||
with:
|
||||
PayloadJson: ${{ needs.download-payload.outputs.WorkflowPayload }}
|
||||
secrets:
|
||||
AccessToken: ${{ secrets.GITHUB_TOKEN }}
|
||||
TeamReadAccessToken: ${{ secrets.ORG_READTEAMS_TOKEN }}
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
26
.github/workflows/BackgroundTasks.yml
vendored
Normal file
26
.github/workflows/BackgroundTasks.yml
vendored
Normal file
@ -0,0 +1,26 @@
|
||||
name: Background tasks
|
||||
|
||||
permissions:
|
||||
pull-requests: write
|
||||
contents: read
|
||||
|
||||
on:
|
||||
pull_request_target:
|
||||
|
||||
jobs:
|
||||
upload:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- name: Save payload data
|
||||
env:
|
||||
PayloadJson: ${{ toJSON(github) }}
|
||||
AccessToken: ${{ github.token }}
|
||||
run: |
|
||||
mkdir -p ./pr
|
||||
echo $PayloadJson > ./pr/PayloadJson.json
|
||||
sed -i -e "s/$AccessToken/XYZ/g" ./pr/PayloadJson.json
|
||||
- uses: actions/upload-artifact@v4
|
||||
with:
|
||||
name: PayloadJson
|
||||
path: pr/
|
||||
22
.github/workflows/LiveMergeCheck.yml
vendored
Normal file
22
.github/workflows/LiveMergeCheck.yml
vendored
Normal file
@ -0,0 +1,22 @@
|
||||
name: PR can merge into branch
|
||||
|
||||
permissions:
|
||||
pull-requests: write
|
||||
statuses: write
|
||||
contents: read
|
||||
|
||||
on:
|
||||
pull_request_target:
|
||||
types: [opened, reopened, synchronize, edited]
|
||||
|
||||
jobs:
|
||||
|
||||
live-merge:
|
||||
uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-LiveMergeCheck.yml@workflows-prod
|
||||
with:
|
||||
PayloadJson: ${{ toJSON(github) }}
|
||||
secrets:
|
||||
AccessToken: ${{ secrets.GITHUB_TOKEN }}
|
||||
|
||||
|
||||
|
||||
22
.github/workflows/PrFileCount.yml
vendored
Normal file
22
.github/workflows/PrFileCount.yml
vendored
Normal file
@ -0,0 +1,22 @@
|
||||
name: PR file count less than limit
|
||||
|
||||
permissions:
|
||||
pull-requests: write
|
||||
statuses: write
|
||||
contents: read
|
||||
|
||||
on:
|
||||
pull_request_target:
|
||||
types: [opened, reopened, synchronize, labeled, unlabeled, edited]
|
||||
|
||||
jobs:
|
||||
|
||||
file-count:
|
||||
uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-PrFileCount.yml@workflows-prod
|
||||
with:
|
||||
PayloadJson: ${{ toJSON(github) }}
|
||||
secrets:
|
||||
AccessToken: ${{ secrets.GITHUB_TOKEN }}
|
||||
|
||||
|
||||
|
||||
20
.github/workflows/ProtectedFiles.yml
vendored
Normal file
20
.github/workflows/ProtectedFiles.yml
vendored
Normal file
@ -0,0 +1,20 @@
|
||||
name: PR has no protected files
|
||||
|
||||
permissions:
|
||||
pull-requests: write
|
||||
statuses: write
|
||||
contents: read
|
||||
|
||||
on: [pull_request_target]
|
||||
|
||||
jobs:
|
||||
|
||||
protected-files:
|
||||
uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-ProtectedFiles.yml@workflows-prod
|
||||
with:
|
||||
PayloadJson: ${{ toJSON(github) }}
|
||||
secrets:
|
||||
AccessToken: ${{ secrets.GITHUB_TOKEN }}
|
||||
|
||||
|
||||
|
||||
@ -1272,7 +1272,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configure/basic-level-windows-diagnostic-events-and-fields-1703.md",
|
||||
"redirect_url": "/windows/configuration/basic-level-windows-diagnostic-events-and-fields",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/basic-level-windows-diagnostic-events-and-fields-1703",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -1302,7 +1302,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configure/configure-windows-telemetry-in-your-organization.md",
|
||||
"redirect_url": "/windows/configuration/configure-windows-diagnostic-data-in-your-organization",
|
||||
"redirect_url": "/windows/privacy/configure-windows-diagnostic-data-in-your-organization",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -1527,7 +1527,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configure/windows-diagnostic-data-1703.md",
|
||||
"redirect_url": "/windows/configuration/windows-diagnostic-data",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/basic-level-windows-diagnostic-events-and-fields-1703",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -1582,7 +1582,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/add-manage-products-vamt.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/add-manage-products-vamt",
|
||||
"redirect_url": "/windows/deployment/volume-activation/add-remove-computers-vamt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -1732,7 +1732,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/install-configure-vamt.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/install-configure-vamt",
|
||||
"redirect_url": "/windows/deployment/volume-activation/vamt-requirements",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -1777,17 +1777,17 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/manage-activations-vamt.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/manage-activations-vamt",
|
||||
"redirect_url": "/windows/deployment/volume-activation/online-activation-vamt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/manage-product-keys-vamt.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/manage-product-keys-vamt",
|
||||
"redirect_url": "/windows/deployment/volume-activation/add-remove-product-key-vamt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/manage-vamt-data.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/manage-vamt-data",
|
||||
"redirect_url": "/windows/deployment/volume-activation/import-export-vamt-data",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -2422,7 +2422,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deploy/vamt-step-by-step.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/vamt-step-by-step",
|
||||
"redirect_url": "/windows/deployment/volume-activation/scenario-online-activation-vamt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -10372,7 +10372,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/manage/configure-windows-telemetry-in-your-organization.md",
|
||||
"redirect_url": "/windows/configuration/configure-windows-diagnostic-data-in-your-organization",
|
||||
"redirect_url": "/windows/privacy/configure-windows-diagnostic-data-in-your-organization",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
|
||||
@ -2,17 +2,17 @@
|
||||
"redirections": [
|
||||
{
|
||||
"source_path": "windows/configuration/basic-level-windows-diagnostic-events-and-fields-1703.md",
|
||||
"redirect_url": "/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1703",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/basic-level-windows-diagnostic-events-and-fields-1703",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/basic-level-windows-diagnostic-events-and-fields-1709.md",
|
||||
"redirect_url": "/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1709",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/basic-level-windows-diagnostic-events-and-fields-1709",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/basic-level-windows-diagnostic-events-and-fields.md",
|
||||
"redirect_url": "/windows/privacy/basic-level-windows-diagnostic-events-and-fields",
|
||||
"redirect_url": "/windows/privacy/index",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -27,7 +27,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/configure-windows-telemetry-in-your-organization.md",
|
||||
"redirect_url": "/windows/configuration/configure-windows-diagnostic-data-in-your-organization",
|
||||
"redirect_url": "/windows/privacy/configure-windows-diagnostic-data-in-your-organization",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -37,7 +37,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/enhanced-diagnostic-data-windows-analytics-events-and-fields.md",
|
||||
"redirect_url": "/windows/privacy/enhanced-diagnostic-data-windows-analytics-events-and-fields",
|
||||
"redirect_url": "https://techcommunity.microsoft.com/t5/windows-it-pro-blog/preview-app-and-driver-compatibility-insights-in-endpoint/ba-p/3482136",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -47,7 +47,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/gdpr-win10-whitepaper.md",
|
||||
"redirect_url": "/windows/privacy/gdpr-win10-whitepaper",
|
||||
"redirect_url": "/windows/privacy/windows-privacy-compliance-guide",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -72,7 +72,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/manage-windows-endpoints-version-1709.md",
|
||||
"redirect_url": "/windows/privacy/manage-windows-endpoints",
|
||||
"redirect_url": "/windows/privacy/index",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -262,17 +262,17 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/windows-diagnostic-data-1703.md",
|
||||
"redirect_url": "/windows/privacy/windows-diagnostic-data-1703",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/basic-level-windows-diagnostic-events-and-fields-1703",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/windows-diagnostic-data-1709.md",
|
||||
"redirect_url": "/windows/configuration/windows-diagnostic-data",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/basic-level-windows-diagnostic-events-and-fields-1709",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/windows-diagnostic-data.md",
|
||||
"redirect_url": "/windows/privacy/windows-diagnostic-data",
|
||||
"redirect_url": "/windows/privacy/index",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
|
||||
@ -1185,10 +1185,185 @@
|
||||
"redirect_url": "/windows/compatibility/",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/do/waas-delivery-optimization-setup.md",
|
||||
"redirect_url": "/windows/deployment/do/delivery-optimization-configure",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/update/plan-determine-app-readiness.md",
|
||||
"redirect_url": "/windows/compatibility/windows-11/testing-guidelines",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/volume-activation/add-manage-products-vamt.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/add-remove-computers-vamt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/volume-activation/install-configure-vamt.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/vamt-requirements",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/volume-activation/manage-activations-vamt.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/online-activation-vamt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/volume-activation/manage-product-keys-vamt.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/add-remove-product-key-vamt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/volume-activation/manage-vamt-data.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/import-export-vamt-data",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/volume-activation/vamt-step-by-step.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/scenario-online-activation-vamt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-update-management.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/overview/windows-autopatch-overview",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-and-feature-update-reports-overview.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-windows-quality-and-feature-update-reports-overview",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-summary-dashboard.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-windows-quality-update-summary-dashboard",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-status-report.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-windows-quality-update-status-report",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-trending-report.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-windows-quality-update-trending-report",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-reliability-report.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-reliability-report",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-summary-dashboard.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-windows-feature-update-summary-dashboard",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-status-report.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-windows-feature-update-status-report",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-trending-report.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-windows-feature-update-trending-report",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-device-alerts.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-device-alerts",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-policy-health-and-remediation.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-policy-health-and-remediation",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-resolve-policy-conflicts.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-resolve-policy-conflicts",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-maintain-environment",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-customize-windows-update-settings.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-customize-windows-update-settings",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-edge.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-edge",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-exclude-device.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-exclude-device",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-manage-driver-and-firmware-updates.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-driver-and-firmware-updates",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-manage-windows-feature-update-releases.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-windows-feature-update-releases",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-microsoft-365-apps-enterprise.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-microsoft-365-apps-enterprise",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-support-request",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-teams.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-teams",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-unenroll-tenant.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-unenroll-tenant",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-feature-update-overview",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-communications.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-quality-update-communications",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-end-user-exp.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-quality-update-end-user-update-exp",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-quality-update-overview",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-signals.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-quality-update-signals",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/references/windows-autopatch-microsoft-365-policies.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-microsoft-365-policies",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@ -2,22 +2,22 @@
|
||||
"redirections": [
|
||||
{
|
||||
"source_path": "windows/privacy/basic-level-windows-diagnostic-events-and-fields.md",
|
||||
"redirect_url": "/windows/privacy/required-windows-diagnostic-data-events-and-fields-2004",
|
||||
"redirect_url": "/windows/privacy/index",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/deploy-data-processor-service-windows.md",
|
||||
"redirect_url": "/windows/privacy/windows-10-and-privacy-compliance",
|
||||
"redirect_url": "/windows/privacy/windows-privacy-compliance-guide",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/gdpr-it-guidance.md",
|
||||
"redirect_url": "/windows/privacy/windows-10-and-privacy-compliance",
|
||||
"redirect_url": "/windows/privacy/windows-privacy-compliance-guide",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/gdpr-win10-whitepaper.md",
|
||||
"redirect_url": "/windows/privacy/windows-10-and-privacy-compliance",
|
||||
"redirect_url": "/windows/privacy/windows-privacy-compliance-guide",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -27,33 +27,138 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/manage-windows-1709-endpoints.md",
|
||||
"redirect_url": "/windows/privacy/manage-windows-21h2-endpoints",
|
||||
"redirect_url": "/windows/privacy/index",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/manage-windows-1803-endpoints.md",
|
||||
"redirect_url": "/windows/privacy/manage-windows-21h2-endpoints",
|
||||
"redirect_url": "/windows/privacy/index",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/manage-windows-endpoints.md",
|
||||
"redirect_url": "/windows/privacy/manage-windows-2004-endpoints",
|
||||
"redirect_url": "/windows/privacy/index",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/windows-endpoints-1709-non-enterprise-editions.md",
|
||||
"redirect_url": "/windows/privacy/windows-endpoints-21h1-non-enterprise-editions",
|
||||
"redirect_url": "/windows/privacy/index",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/windows-endpoints-1803-non-enterprise-editions.md",
|
||||
"redirect_url": "/windows/privacy/windows-endpoints-21h1-non-enterprise-editions",
|
||||
"redirect_url": "/windows/privacy/index",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/windows-personal-data-services-configuration.md",
|
||||
"redirect_url": "/windows/privacy/windows-10-and-privacy-compliance",
|
||||
"redirect_url": "/windows/privacy/windows-privacy-compliance-guide",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/enhanced-diagnostic-data-windows-analytics-events-and-fields.md",
|
||||
"redirect_url": "https://techcommunity.microsoft.com/t5/windows-it-pro-blog/preview-app-and-driver-compatibility-insights-in-endpoint/ba-p/3482136",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/basic-level-windows-diagnostic-events-and-fields-1703.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/basic-level-windows-diagnostic-events-and-fields-1703",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/basic-level-windows-diagnostic-events-and-fields-1709.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/basic-level-windows-diagnostic-events-and-fields-1709",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/basic-level-windows-diagnostic-events-and-fields-1803.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/basic-level-windows-diagnostic-events-and-fields-1803",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/basic-level-windows-diagnostic-events-and-fields-1903.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/basic-level-windows-diagnostic-events-and-fields-1903",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/manage-windows-1903-endpoints.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/manage-windows-1903-endpoints",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/manage-windows-1909-endpoints.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/manage-windows-1909-endpoints",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/manage-windows-2004-endpoints.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/manage-windows-2004-endpoints",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/manage-windows-20H2-endpoints.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/manage-windows-20H2-endpoints",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/manage-windows-21H1-endpoints.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/manage-windows-21H1-endpoints",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/windows-endpoints-1809-non-enterprise-editions.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/windows-endpoints-1809-non-enterprise-editions",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/windows-endpoints-1903-non-enterprise-editions.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/windows-endpoints-1903-non-enterprise-editions",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/windows-endpoints-1909-non-enterprise-editions.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/windows-endpoints-1909-non-enterprise-editions",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/windows-endpoints-2004-non-enterprise-editions.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/windows-endpoints-2004-non-enterprise-editions",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/windows-endpoints-20H2-non-enterprise-editions.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/windows-endpoints-20H2-non-enterprise-editions",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/windows-endpoints-21H1-non-enterprise-editions.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/windows-endpoints-21H1-non-enterprise-editions",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/windows-diagnostic-data-1703.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/basic-level-windows-diagnostic-events-and-fields-1703",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/changes-to-windows-diagnostic-data-collection.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/changes-to-windows-diagnostic-data-collection",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/windows-10-and-privacy-compliance.md",
|
||||
"redirect_url": "/windows/privacy/windows-privacy-compliance-guide",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/windows-diagnostic-data.md",
|
||||
"redirect_url": "/windows/privacy/optional-diagnostic-data",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/Microsoft-DiagnosticDataViewer.md",
|
||||
"redirect_url": "/windows/privacy/diagnostic-data-viewer-powershell",
|
||||
"redirect_document_id": true
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@ -52,7 +52,12 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security//threat-protection/microsoft-defender-application-guard/md-app-guard-browser-extension.md",
|
||||
"redirect_url": "/windows/security/application-security/application-isolation/microsoft-defender-application-guard/md-app-guard-browser-extension",
|
||||
"redirect_url": "/windows/security/application-security/application-isolation/microsoft-defender-application-guard/md-app-guard-overview",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/application-security/application-isolation/microsoft-defender-application-guard/md-app-guard-browser-extension.md",
|
||||
"redirect_url": "/windows/security/application-security/application-isolation/microsoft-defender-application-guard/md-app-guard-overview",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -4077,7 +4082,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md",
|
||||
"redirect_url": "/windows/security/operating-system-security/virus-and-threat-protection/microsoft-defender-smartscreen",
|
||||
"redirect_url": "https://feedback.smartscreen.microsoft.com/smartscreenfaq.aspx",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -6722,7 +6727,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-overview.md",
|
||||
"redirect_url": "/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview",
|
||||
"redirect_url": "https://feedback.smartscreen.microsoft.com/smartscreenfaq.aspx",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
|
||||
@ -8,7 +8,7 @@ metadata:
|
||||
title: Microsoft 365 Education Documentation
|
||||
description: Learn about product documentation and resources available for school IT administrators, teachers, students, and education app developers.
|
||||
ms.topic: hub-page
|
||||
ms.date: 11/06/2023
|
||||
ms.date: 07/22/2024
|
||||
|
||||
productDirectory:
|
||||
title: For IT admins
|
||||
|
||||
@ -12,16 +12,16 @@ metadata:
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
manager: aaroncz
|
||||
ms.date: 10/30/2023
|
||||
ms.date: 07/22/2024
|
||||
|
||||
highlightedContent:
|
||||
items:
|
||||
- title: Get started with Windows 11 SE
|
||||
itemType: get-started
|
||||
url: windows-11-se-overview.md
|
||||
- title: Windows 11, version 22H2
|
||||
- title: Windows 11, version 23H2
|
||||
itemType: whats-new
|
||||
url: /windows/whats-new/whats-new-windows-11-version-22H2
|
||||
url: /windows/whats-new/whats-new-windows-11-version-23h2
|
||||
- title: Explore all Windows trainings and learning paths for IT pros
|
||||
itemType: learn
|
||||
url: https://learn.microsoft.com/en-us/training/browse/?products=windows&roles=administrator
|
||||
|
||||
@ -51,7 +51,6 @@
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
},
|
||||
"titleSuffix": "Windows Application Management",
|
||||
"contributors_to_exclude": [
|
||||
"dstrome2",
|
||||
"rjagiewich",
|
||||
|
||||
@ -56,7 +56,6 @@
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
},
|
||||
"titleSuffix": "Windows Client Management",
|
||||
"contributors_to_exclude": [
|
||||
"dstrome2",
|
||||
"rjagiewich",
|
||||
|
||||
@ -1222,8 +1222,11 @@ If you enter an invalid value, you'll remain on your current version until you c
|
||||
<!-- TargetReleaseVersion-Editable-Begin -->
|
||||
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
|
||||
Supported value type is a string containing Windows version number. For example, `1809`, `1903`, etc.
|
||||
<!-- TargetReleaseVersion-Editable-End -->
|
||||
|
||||
> [!NOTE]
|
||||
> You need to set up the ProductVersion CSP along with the TargetReleaseVersion CSP for it to work.
|
||||
|
||||
<!-- TargetReleaseVersion-Editable-End -->
|
||||
<!-- TargetReleaseVersion-DFProperties-Begin -->
|
||||
**Description framework properties**:
|
||||
|
||||
|
||||
@ -18,9 +18,9 @@ The table below shows the applicability of Windows:
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
The UniversalPrint configuration service provider (CSP) is used to add Universal Print-compatible printers to Windows client endpoints. Universal Print is a cloud-based printing solution that runs entirely in Microsoft Azure. It doesn't require any on-premises infrastructure. For more specific information, go to [What is Universal Print](/universal-print/fundamentals/universal-print-whatis).
|
||||
The UniversalPrint configuration service provider (CSP) is used to add Universal Print-compatible printers to Windows client endpoints. Universal Print is a cloud-based printing solution that runs entirely in Microsoft Azure. It doesn't require any on-premises infrastructure. For more specific information, see [Discover Universal Print](/universal-print/discover-universal-print).
|
||||
|
||||
This CSP was added in Windows 11 and in Windows 10 21H2 July 2022 update [KB5015807](https://support.microsoft.com/topic/july-12-2022-kb5015807-os-builds-19042-1826-19043-1826-and-19044-1826-8c8ea8fe-ec83-467d-86fb-a2f48a85eb41).
|
||||
This CSP was added in Windows 11 and in Windows 10, version 21H2 July 2022 update [KB5015807](https://support.microsoft.com/topic/july-12-2022-kb5015807-os-builds-19042-1826-19043-1826-and-19044-1826-8c8ea8fe-ec83-467d-86fb-a2f48a85eb41).
|
||||
|
||||
The following example shows the UniversalPrint configuration service provider in tree format.
|
||||
|
||||
@ -52,7 +52,7 @@ The data type is node (XML node). Supported operation is Get.
|
||||
|
||||
<a href="" id="guidprintersharedid)"></a>**`<GUID>` (PrinterSharedID)**
|
||||
|
||||
The Share ID is used to identify the Universal Print printer you want to install on the targeted user account. You can get the printer's Share ID in the printer's properties in the [Universal Print portal](/universal-print/portal/navigate-up).
|
||||
The Share ID is used to identify the Universal Print printer you want to install on the targeted user account. You can get the printer's Share ID in the printer's properties in the [Universal Print portal](/universal-print/reference/portal/navigate-azure-portal).
|
||||
|
||||
The data type is node (XML node). Supported operations are Get, Add, and Delete.
|
||||
|
||||
@ -61,7 +61,7 @@ The data type is node (XML node). Supported operations are Get, Add, and Delete.
|
||||
|
||||
<a href="" id="clouddeviceid"></a>**CloudDeviceID**
|
||||
|
||||
The Printer ID is used to identify the Universal Print printer you want to install on the targeted user account. You can get the printer's Printer ID in the printer's properties in the [Universal Print portal](/universal-print/portal/navigate-up).
|
||||
The Printer ID is used to identify the Universal Print printer you want to install on the targeted user account. You can get the printer's Printer ID in the printer's properties in the [Universal Print portal](/universal-print/reference/portal/navigate-azure-portal).
|
||||
|
||||
The data type is string/text (GUID). Supported operations are Get, Add, Delete, and Replace.
|
||||
|
||||
@ -70,7 +70,7 @@ The data type is string/text (GUID). Supported operations are Get, Add, Delete,
|
||||
|
||||
<a href="" id="printersharedname"></a>**PrinterSharedName**
|
||||
|
||||
The Share Name is used to identify the Universal Print printer you want to install on the targeted user account. You can get the printer's Share Name in the printer's properties in the [Universal Print portal](/universal-print/portal/navigate-up).
|
||||
The Share Name is used to identify the Universal Print printer you want to install on the targeted user account. You can get the printer's Share Name in the printer's properties in the [Universal Print portal](/universal-print/reference/portal/navigate-azure-portal).
|
||||
|
||||
The data type is string/text. Supported operations are Get, Add, Delete, and Replace.
|
||||
|
||||
|
||||
@ -17,6 +17,13 @@ The table below shows the applicability of Windows:
|
||||
|Enterprise|Yes|Yes|
|
||||
|Education|Yes|Yes|
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Windows 11 Home devices that have been upgraded to one of the below mentioned applicable editions might require you to run the following command before onboarding:
|
||||
>
|
||||
> `DISM /online /Add-Capability /CapabilityName:Microsoft.Windows.Sense.Client~~~~`
|
||||
>
|
||||
> For more information about edition upgrades and features, see [Customize Windows features](/windows-hardware/manufacture/desktop/windows-features?view=windows-11&preserve-view=true).
|
||||
|
||||
The Windows Defender Advanced Threat Protection (WDATP) configuration service provider (CSP) allows IT Admins to onboard, determine configuration and health status, and offboard endpoints for WDATP.
|
||||
|
||||
The following example shows the WDATP configuration service provider in tree format as used by the Open Mobile Alliance (OMA) Device Management (DM).
|
||||
|
||||
@ -1,94 +1,43 @@
|
||||
---
|
||||
title: Windows accessibility information for IT Pros
|
||||
description: Lists the various accessibility features available in Windows client with links to detailed guidance on how to set them.
|
||||
ms.date: 01/25/2024
|
||||
ms.topic: conceptual
|
||||
title: Windows accessibility for IT pros
|
||||
description: Basic guidance for IT administrators on accessibility features available in Windows client.
|
||||
ms.date: 07/25/2024
|
||||
ms.topic: concept-article
|
||||
ms.collection: tier1
|
||||
---
|
||||
|
||||
<!-- MAXADO-8138357 -->
|
||||
<!-- MAXADO-8138352 -->
|
||||
|
||||
# Accessibility information for IT professionals
|
||||
|
||||
Microsoft is dedicated to making its products and services accessible and usable for everyone. Windows includes accessibility features that benefit all users. These features make it easier to customize the computer and give users with different abilities options to improve their experience with Windows.
|
||||
|
||||
This article helps you as the IT administrator learn about built-in accessibility features. It also includes recommendations for how to support people in your organization who use these features.
|
||||
For more information about the accessibility resources available in Windows, see [Discover Windows accessibility features](https://support.microsoft.com/windows/discover-windows-accessibility-features-8b1068e6-d3b8-4ba8-b027-133dd8911df9#WindowsVersion=Windows_11).
|
||||
|
||||
Windows 11, version 22H2, includes improvements for people with disabilities: system-wide live captions, Focus sessions, voice access, and more natural voices for Narrator. For more information, see [New accessibility features coming to Windows 11](https://blogs.windows.com/windowsexperience/2022/05/10/new-accessibility-features-coming-to-windows-11/) and [How inclusion drives innovation in Windows 11](https://blogs.windows.com/windowsexperience/?p=177554).
|
||||
<!-- 6294246 -->
|
||||
Windows 11, version 22H2, includes improvements for people with disabilities. For example, system-wide live captions, Focus sessions, voice access, and more natural voices for Narrator. For more information, see the following Windows Experience blog posts:
|
||||
|
||||
- [New accessibility features coming to Windows 11](https://blogs.windows.com/windowsexperience/2022/05/10/new-accessibility-features-coming-to-windows-11/)
|
||||
|
||||
- [How inclusion drives innovation in Windows 11](https://blogs.windows.com/windowsexperience/2022/09/20/how-inclusion-drives-innovation-in-windows-11/)
|
||||
|
||||
## General recommendations
|
||||
|
||||
- **Be aware of Ease of Access settings**. Understand how people in your organization might use these settings. Help people in your organization learn how they can customize Windows.
|
||||
|
||||
- **Don't block settings**. Avoid using group policy or MDM settings that override Ease of Access settings.
|
||||
|
||||
- **Encourage choice**. Allow people in your organization to customize their computers based on their needs. That customization might be installing an add-on for their browser, or a non-Microsoft assistive technology.
|
||||
|
||||
## Vision
|
||||
- Use the [Azure AI Translator](/azure/ai-services/translator/) service to add machine translation to your solutions.
|
||||
|
||||
- [Use Narrator to use devices without a screen](https://support.microsoft.com/windows/complete-guide-to-narrator-e4397a0d-ef4f-b386-d8ae-c172f109bdb1). Narrator describes Windows and apps and enables you to control devices by using a keyboard, controller, or with a range of gestures on touch-supported devices. Now the user is able to download and install 10 more natural languages.
|
||||
- [Create accessible apps](/windows/apps/develop/accessibility). You can develop accessible apps just like Mail, Groove, and Store that work well with Narrator and other leading screen readers.
|
||||
- Use keyboard shortcuts. Get the most out of Windows with shortcuts for apps and desktops.
|
||||
- [Keyboard shortcuts in Windows](https://support.microsoft.com/windows/keyboard-shortcuts-in-windows-dcc61a57-8ff0-cffe-9796-cb9706c75eec)
|
||||
- [Narrator keyboard commands and touch gestures](https://support.microsoft.com/windows/appendix-b-narrator-keyboard-commands-and-touch-gestures-8bdab3f4-b3e9-4554-7f28-8b15bd37410a)
|
||||
- [Windows keyboard shortcuts for accessibility](https://support.microsoft.com/windows/windows-keyboard-shortcuts-for-accessibility-021bcb62-45c8-e4ef-1e4f-41b8c1fc87fd)
|
||||
- Get closer with [Magnifier](https://support.microsoft.com/windows/use-magnifier-to-make-things-on-the-screen-easier-to-see-414948ba-8b1c-d3bd-8615-0e5e32204198). Magnifier enlarges all or part of your screen and offers various configuration settings.
|
||||
- [Make Windows easier to see](https://support.microsoft.com/windows/make-windows-easier-to-see-c97c2b0d-cadb-93f0-5fd1-59ccfe19345d).
|
||||
- Changing the size or color of pointers or adding trails or touch feedback make it easier to follow the mouse.
|
||||
- Adjust the size of text, icons, and other screen items to make them easier to see.
|
||||
- Many high-contrast themes are available to suit your needs.
|
||||
- [Have Cortana assist](https://support.microsoft.com/topic/what-is-cortana-953e648d-5668-e017-1341-7f26f7d0f825). Cortana can handle various tasks for you, including setting reminders, opening apps, finding facts, and sending emails and texts.
|
||||
- [Dictate text and commands](https://support.microsoft.com/windows/use-voice-recognition-in-windows-83ff75bd-63eb-0b6c-18d4-6fae94050571). Windows includes speech recognition that lets you tell it what to do.
|
||||
- [Simplify for focus](https://support.microsoft.com/windows/make-it-easier-to-focus-on-tasks-0d259fd9-e9d0-702c-c027-007f0e78eaf2). Reducing animations and turning off background images and transparency can minimize distractions.
|
||||
- [Keep notifications around longer](https://support.microsoft.com/windows/make-windows-easier-to-hear-9c18cfdc-63be-2d47-0f4f-5b00facfd2e1). If notifications aren't staying visible long enough for you to notice them, you can increase the time a notification will be displayed up to five minutes.
|
||||
- [Read in braille](https://support.microsoft.com/windows/chapter-8-using-narrator-with-braille-3e5f065b-1c9d-6eb2-ec6d-1d07c9e94b20). Narrator supports braille displays from more than 35 manufacturers using more than 40 languages and multiple braille variants.
|
||||
- Starting in Windows 11, version 22H2 with [KB5022913](https://support.microsoft.com/kb/5022913), the compatibility of braille displays has been expanded. Braille displays work seamlessly and reliably across multiple screen readers, improving the end user experience.
|
||||
- [Create accessible apps](/windows/apps/develop/accessibility) that work well with Narrator and other leading screen readers.
|
||||
|
||||
## Hearing
|
||||
|
||||
- [Use live captions to better understand audio](https://support.microsoft.com/windows/use-live-captions-to-better-understand-audio-b52da59c-14b8-4031-aeeb-f6a47e6055df). Use Windows 11, version 22H2 or later to better understand any spoken audio with real time captions.
|
||||
- Starting with Windows 11, version 22H2 with [KB5026446](https://support.microsoft.com/kb/5026446), live captions now supports additional languages.
|
||||
- [View live transcription in a Teams meeting](https://support.microsoft.com/office/view-live-transcription-in-a-teams-meeting-dc1a8f23-2e20-4684-885e-2152e06a4a8b). During any Teams meeting, view a live transcription so you don't miss what's being said.
|
||||
- [Use Teams for sign language](https://www.microsoft.com/microsoft-teams/group-chat-software). Teams is available on various platforms and devices, so you don't have to worry about whether your co-workers, friends, and family can communicate with you.
|
||||
|
||||
- [Make Windows easier to hear](https://support.microsoft.com/windows/make-windows-easier-to-hear-9c18cfdc-63be-2d47-0f4f-5b00facfd2e1).
|
||||
- Replace audible alerts with visual alerts.
|
||||
- If notifications aren't staying visible long enough for you to notice them, you can increase the time a notification will be displayed up to five minutes.
|
||||
- Send all sounds to both left and right channels, which is helpful for those people with partial hearing loss or deafness in one ear.
|
||||
- [Read spoken words with captioning](https://support.microsoft.com/windows/change-caption-settings-135c465b-8cfd-3bac-9baf-4af74bc0069a). You can customize things like color, size, and background transparency to suit your needs and tastes.
|
||||
- Use the [Azure Cognitive Services Translator](/azure/cognitive-services/translator/) service to add machine translation to your solutions.
|
||||
|
||||
## Physical
|
||||
|
||||
- [Have Cortana assist you](https://support.microsoft.com/topic/what-is-cortana-953e648d-5668-e017-1341-7f26f7d0f825). Cortana can handle various tasks for you, including setting reminders, opening apps, finding facts, and sending emails and texts.
|
||||
- [Dictate text and commands](https://support.microsoft.com/windows/use-voice-recognition-in-windows-83ff75bd-63eb-0b6c-18d4-6fae94050571). Windows includes voice recognition that lets you tell it what to do.
|
||||
- [Use the On-Screen Keyboard (OSK)](https://support.microsoft.com/windows/use-the-on-screen-keyboard-osk-to-type-ecbb5e08-5b4e-d8c8-f794-81dbf896267a). Instead of relying on a physical keyboard, use the OSK to enter data and select keys with a mouse or other pointing device. It also offers word prediction and completion.
|
||||
- [Make your mouse, keyboard, and other input devices easier to use](https://support.microsoft.com/windows/make-your-mouse-keyboard-and-other-input-devices-easier-to-use-10733da7-fa82-88be-0672-f123d4b3dcfe).
|
||||
|
||||
- If you have limited control of your hands, you can personalize your keyboard to do helpful things like ignore repeated keys.
|
||||
- If a mouse is difficult to use, you can control the pointer by using your numeric keypad.
|
||||
|
||||
## Cognition
|
||||
|
||||
- [Simplify for focus](https://support.microsoft.com/windows/make-it-easier-to-focus-on-tasks-0d259fd9-e9d0-702c-c027-007f0e78eaf2). Reducing animations and turning off background images and transparency can minimize distractions.
|
||||
- [Download and use fonts that are easier to read](https://www.microsoft.com/download/details.aspx?id=50721). **Fluent Sitka Small** and **Fluent Calibri** are fonts that address "visual crowding" by adding character and enhance word and line spacing.
|
||||
- [Microsoft Edge reading view](https://support.microsoft.com/windows/take-your-reading-with-you-b6699255-4436-708e-7b93-4d2e19a15af8). Clears distracting content from web pages so you can stay focused on what you really want to read.
|
||||
|
||||
## Assistive technology devices built into Windows
|
||||
|
||||
- [Hear text read aloud with Narrator](https://support.microsoft.com/windows/hear-text-read-aloud-with-narrator-040f16c1-4632-b64e-110a-da4a0ac56917). Narrator reads text on your PC screen aloud and describes events, such as notifications or calendar appointments, so you can use your PC without a display.
|
||||
- Scripting functionality has been added to Narrator. There is store delivery of Narrator extension scripts which currently include an Outlook script and an Excel script.
|
||||
- [Use voice recognition](https://support.microsoft.com/windows/use-voice-recognition-in-windows-83ff75bd-63eb-0b6c-18d4-6fae94050571).
|
||||
|
||||
<!-- MAXADO-8138354 -->
|
||||
- With spellings experience in voice access, you can dictate a complex or non-standard word letter-by-letter and add it to Windows dictionary. The next time you try to dictate the same word, voice access improves its recognition.
|
||||
|
||||
- [Save time with keyboard shortcuts](https://support.microsoft.com/windows/keyboard-shortcuts-in-windows-dcc61a57-8ff0-cffe-9796-cb9706c75eec).
|
||||
- [Use voice access to control your PC and author text with your voice](https://support.microsoft.com/topic/use-voice-access-to-control-your-pc-author-text-with-your-voice-4dcd23ee-f1b9-4fd1-bacc-862ab611f55d).
|
||||
|
||||
## Other resources
|
||||
|
||||
[Windows accessibility](https://www.microsoft.com/Accessibility/windows)
|
||||
[Designing accessible software](/windows/apps/design/accessibility/designing-inclusive-software)
|
||||
[Inclusive design](https://www.microsoft.com/design/inclusive)
|
||||
[Accessibility guide for Microsoft 365 Apps](/deployoffice/accessibility-guide)
|
||||
- [Windows accessibility](https://www.microsoft.com/windows/accessibility-features)
|
||||
|
||||
- [Designing accessible software](/windows/apps/design/accessibility/designing-inclusive-software)
|
||||
|
||||
- [Inclusive design](https://inclusive.microsoft.design/)
|
||||
|
||||
- [Accessibility guide for Microsoft 365 Apps](/microsoft-365-apps/deploy/accessibility-guide)
|
||||
|
||||
@ -106,7 +106,7 @@ Each profile defines a `Shell` element, which contains details about the applica
|
||||
|-|-|-|
|
||||
|`Shell`| Application that is used as a Windows shell. |- For Universal Windows Platform (UWP) apps, you must provide the App User Model ID (AUMID). Learn how to [Find the Application User Model ID of an installed app](../../store/find-aumid.md).<br>- For desktop apps, specify the full path of the executable, which can contain system environment variables in the form of `%variableName%`. You can also specify any parameters that the app might require. |
|
||||
|`V2:AppType`| Defines the type of application. |Allowed values are `Desktop` and `UWP`.|
|
||||
|`V2:AllAppsFullScreen` | Boolean value that defines if all applications are executed in full screen. |- When set to `True`, Shell Launcher runs every app in full screen, or maximized for desktop apps.<br>- When set to `False` or not set, only the custom shell app runs in full screen; other apps launched by the user run in windowed mode.|
|
||||
|`V2:AllAppsFullScreen` | Boolean value that defines if all applications are executed in full screen. |- When set to `true`, Shell Launcher runs every app in full screen, or maximized for desktop apps.<br>- When set to `false` or not set, only the custom shell app runs in full screen; other apps launched by the user run in windowed mode.|
|
||||
|
||||
Example:
|
||||
|
||||
|
||||
@ -52,7 +52,6 @@
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
},
|
||||
"titleSuffix": "Configure Windows",
|
||||
"contributors_to_exclude": [
|
||||
"dstrome2",
|
||||
"rjagiewich",
|
||||
|
||||
@ -0,0 +1,20 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 07/11/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
### Hide entry points for Fast User Switching
|
||||
|
||||
With this policy setting you can prevent multiple users to sign in at the same time, using the Fast User Switching feature.
|
||||
|
||||
- If enabled, only one user can sign in at a time. The Fast User Switching entry points are hidden from the sign-in screen, the Start menu, and the Task Manager. If multiple users want to sign in, the current user must sign out first
|
||||
- If disabled or not configured, multiple users can sign in at the same time. The Fast User Switching entry points are available from the sign-in screen, the Start menu, and the Task Manager. The current user doesn't have to sign out to allow another user to sign in
|
||||
|
||||
| | Path |
|
||||
|--|--|
|
||||
| **CSP** | `./Device/Vendor/MSFT/Policy/Config/WindowsLogon/`[HideFastUserSwitching](/windows/client-management/mdm/policy-csp-windowslogon#hidefastuserswitching) |
|
||||
| **GPO** | **Computer Configuration** > **Administrative Templates** > **System** > **Logon** > **Hide entry points for Fast User Switching** |
|
||||
|
||||
To learn more, see [Fast User Switching](/windows/win32/shell/fast-user-switching).
|
||||
@ -9,5 +9,5 @@ ms.topic: include
|
||||
|
||||
| | Path |
|
||||
|--|--|
|
||||
| **CSP** | `./Device/Vendor/MSFT/Policy/Config/Start/`[HideSignOut](/windows/client-management/mdm/policy-csp-start#hidelock) |
|
||||
| **CSP** | `./Device/Vendor/MSFT/Policy/Config/Start/`[HideLock](/windows/client-management/mdm/policy-csp-start#hidelock) |
|
||||
| **GPO** | Not available. |
|
||||
|
||||
@ -5,7 +5,12 @@ ms.date: 04/10/2024
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
### Hide Switch account
|
||||
### Hide Switch user
|
||||
|
||||
With this policy setting you can hide the **Switch user** option from the user tile in the start menu:
|
||||
|
||||
- If enabled, the **Switch user** option is hidden
|
||||
- If disabled or not configured, the **Switch user** option is available
|
||||
|
||||
| | Path |
|
||||
|--|--|
|
||||
@ -2,7 +2,7 @@
|
||||
title: Start policy settings
|
||||
description: Learn about the policy settings to configure the Windows Start menu.
|
||||
ms.topic: reference
|
||||
ms.date: 04/10/2024
|
||||
ms.date: 07/10/2024
|
||||
appliesto:
|
||||
zone_pivot_groups: windows-versions-11-10
|
||||
---
|
||||
@ -132,19 +132,37 @@ Select one of the tabs to see the list of available settings:
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/user.svg"::: **Account options**](#tab/user)
|
||||
|
||||
::: zone pivot="windows-11"
|
||||
|Policy name| CSP | GPO |
|
||||
|-|-|-|
|
||||
|[Hide **Change account settings**](#hide-change-account-settings)|✅|❌|
|
||||
|[Hide **Sign out**](#hide-sign-out)|✅|✅|
|
||||
|[Hide **Switch user**](#hide-switch-user)|✅|❌|
|
||||
|[Hide entry points for Fast User Switching](#hide-entry-points-for-fast-user-switching)|✅|✅|
|
||||
|[Hide user tile](#hide-user-tile)|✅|❌|
|
||||
::: zone-end
|
||||
|
||||
::: zone pivot="windows-10"
|
||||
|Policy name| CSP | GPO |
|
||||
|-|-|-|
|
||||
|[Hide **Change account settings**](#hide-change-account-settings)|✅|❌|
|
||||
|[Hide **Lock**](#hide-lock)|✅|❌|
|
||||
|[Hide **Sign out**](#hide-sign-out)|✅|✅|
|
||||
|[Hide **Switch account**](#hide-switch-account)|✅|❌|
|
||||
|[Hide **Switch user**](#hide-switch-user)|✅|❌|
|
||||
|[Hide entry points for Fast User Switching](#hide-entry-points-for-fast-user-switching)|✅|✅|
|
||||
|[Hide user tile](#hide-user-tile)|✅|❌|
|
||||
::: zone-end
|
||||
|
||||
[!INCLUDE [hide-change-account-settings](includes/hide-change-account-settings.md)]
|
||||
|
||||
::: zone pivot="windows-10"
|
||||
[!INCLUDE [hide-lock](includes/hide-lock.md)]
|
||||
::: zone-end
|
||||
|
||||
[!INCLUDE [hide-signout](includes/hide-signout.md)]
|
||||
[!INCLUDE [hide-switch-user](includes/hide-switch-account.md)]
|
||||
[!INCLUDE [hide-switch-user](includes/hide-user-tile.md)]
|
||||
[!INCLUDE [hide-switch-user](includes/hide-switch-user.md)]
|
||||
[!INCLUDE [hide-lock](includes/hide-entry-points-for-fast-user-switching.md)]
|
||||
[!INCLUDE [hide-user-tile](includes/hide-user-tile.md)]
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/folder.svg"::: **Pinned folders**](#tab/folders)
|
||||
|
||||
@ -174,6 +192,21 @@ Select one of the tabs to see the list of available settings:
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/power.svg"::: **Power options**](#tab/power)
|
||||
|
||||
|
||||
::: zone pivot="windows-11"
|
||||
|Policy name| CSP | GPO |
|
||||
|-|-|-|
|
||||
|[Hide **Hibernate** ](#hide-hibernate)|✅|❌|
|
||||
|[Hide **Lock**](#hide-lock)|✅|❌|
|
||||
|[Hide **Power** button](#hide-power-button)|✅|❌|
|
||||
|[Hide **Restart**](#hide-restart)|✅|❌|
|
||||
|[Hide **Shut down**](#hide-shut-down)|✅|❌|
|
||||
|[Hide **Sleep**](#hide-sleep)|✅|❌|
|
||||
|[Remove and prevent access to the shut down restart sleep and hibernate commands](#remove-and-prevent-access-to-the-shut-down-restart-sleep-and-hibernate-commands)|❌|✅|
|
||||
::: zone-end
|
||||
|
||||
::: zone pivot="windows-10"
|
||||
|
||||
|Policy name| CSP | GPO |
|
||||
|-|-|-|
|
||||
|[Hide **Hibernate** ](#hide-hibernate)|✅|❌|
|
||||
@ -183,7 +216,12 @@ Select one of the tabs to see the list of available settings:
|
||||
|[Hide **Sleep**](#hide-sleep)|✅|❌|
|
||||
|[Remove and prevent access to the shut down restart sleep and hibernate commands](#remove-and-prevent-access-to-the-shut-down-restart-sleep-and-hibernate-commands)|❌|✅|
|
||||
|
||||
::: zone-end
|
||||
|
||||
[!INCLUDE [hide-hibernate](includes/hide-hibernate.md)]
|
||||
::: zone pivot="windows-11"
|
||||
[!INCLUDE [hide-lock](includes/hide-lock.md)]
|
||||
::: zone-end
|
||||
[!INCLUDE [hide-power-button](includes/hide-power-button.md)]
|
||||
[!INCLUDE [hide-restart](includes/hide-restart.md)]
|
||||
[!INCLUDE [hide-shut-down](includes/hide-shut-down.md)]
|
||||
|
||||
@ -455,7 +455,7 @@ ConfigureTelemetryOptInSettingsUx | This policy setting determines whether peopl
|
||||
| DisableDeviceDelete | Specify whether the delete diagnostic data is enabled in the Diagnostic & Feedback Settings page. | ✅ | | | |
|
||||
| DisableDataDiagnosticViewer | Configure whether users can enable and launch the Diagnostic Data Viewer from the Diagnostic & Feedback Settings page. | ✅ | | | |
|
||||
| [DisableOneDriveFileSync](/windows/client-management/mdm/policy-configuration-service-provider#system-disableonedrivefilesync) | Prevent apps and features from working with files on OneDrive. | ✅ | | | |
|
||||
| [LimitEnhancedDiagnosticDataWindowsAnalytics](/windows/client-management/mdm/policy-csp-system#system-limitenhanceddiagnosticdatawindowsanalytics) | This policy setting, in combination with the System/AllowTelemetry policy setting, enables organizations to send Microsoft a specific set of diagnostic data for IT insights via Windows Analytics services. To enable this behavior you must enable this policy setting, and set Allow Telemetry to level 2 (Enhanced). When you configure these policy settings, a basic level of diagnostic data plus other events that are required for Windows Analytics are sent to Microsoft. These events are documented in [Windows 10, version 1703 basic level Windows diagnostic events and fields](/windows/privacy/enhanced-diagnostic-data-windows-analytics-events-and-fields). Enabling enhanced diagnostic data in the System/AllowTelemetry policy in combination with not configuring this policy will also send the required events for Windows Analytics, plus other enhanced level diagnostic data. This setting has no effect on computers configured to send full, basic or security level diagnostic data to Microsoft. If you disable or don't configure this policy setting, then the level of diagnostic data sent to Microsoft is determined by the System/AllowTelemetry policy. | ✅ | | | |
|
||||
| [LimitEnhancedDiagnosticDataWindowsAnalytics](/windows/client-management/mdm/policy-csp-system#limitenhanceddiagnosticdatawindowsanalytics) | This policy setting, in combination with the System/AllowTelemetry policy setting, enables organizations to send Microsoft a specific set of diagnostic data for IT insights via Windows Analytics services. To enable this behavior you must enable this policy setting, and set Allow Telemetry to level 2 (Enhanced). When you configure these policy settings, a basic level of diagnostic data plus other events that are required for Windows Analytics are sent to Microsoft. Enabling enhanced diagnostic data in the System/AllowTelemetry policy in combination with not configuring this policy will also send the required events for Windows Analytics, plus other enhanced level diagnostic data. This setting has no effect on computers configured to send full, basic or security level diagnostic data to Microsoft. If you disable or don't configure this policy setting, then the level of diagnostic data sent to Microsoft is determined by the System/AllowTelemetry policy. | ✅ | | | |
|
||||
|
||||
## TextInput
|
||||
|
||||
|
||||
@ -74,7 +74,7 @@
|
||||
- name: Update Baseline
|
||||
href: update/update-baseline.md
|
||||
- name: Set up Delivery Optimization for Windows client updates
|
||||
href: do/waas-delivery-optimization-setup.md?context=/windows/deployment/context/context
|
||||
href: do/delivery-optimization-configure.md?context=/windows/deployment/context/context
|
||||
- name: Configure BranchCache for Windows client updates
|
||||
href: update/waas-branchcache.md
|
||||
- name: Prepare for deployment with Configuration Manager
|
||||
@ -186,83 +186,70 @@
|
||||
href: volume-activation/monitor-activation-client.md
|
||||
- name: Use the Volume Activation Management Tool
|
||||
href: volume-activation/use-the-volume-activation-management-tool-client.md
|
||||
href: volume-activation/appendix-information-sent-to-microsoft-during-activation-client.md
|
||||
- name: Information sent to Microsoft during activation
|
||||
href: volume-activation/appendix-information-sent-to-microsoft-during-activation-client.md
|
||||
- name: Volume Activation Management Tool (VAMT)
|
||||
items:
|
||||
- name: VAMT technical reference
|
||||
href: volume-activation/volume-activation-management-tool.md
|
||||
- name: Introduction to VAMT
|
||||
href: volume-activation/introduction-vamt.md
|
||||
- name: Active Directory-Based Activation Overview
|
||||
- name: Active Directory-Based activation overview
|
||||
href: volume-activation/active-directory-based-activation-overview.md
|
||||
- name: Install and Configure VAMT
|
||||
- name: Install and configure VAMT
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/install-configure-vamt.md
|
||||
- name: VAMT Requirements
|
||||
- name: VAMT requirements
|
||||
href: volume-activation/vamt-requirements.md
|
||||
- name: Install VAMT
|
||||
href: volume-activation/install-vamt.md
|
||||
- name: Configure Client Computers
|
||||
- name: Configure client computers
|
||||
href: volume-activation/configure-client-computers-vamt.md
|
||||
- name: Add and Manage Products
|
||||
- name: Add and manage products
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/add-manage-products-vamt.md
|
||||
- name: Add and Remove Computers
|
||||
- name: Add and remove computers
|
||||
href: volume-activation/add-remove-computers-vamt.md
|
||||
- name: Update Product Status
|
||||
- name: Update product status
|
||||
href: volume-activation/update-product-status-vamt.md
|
||||
- name: Remove Products
|
||||
- name: Remove products
|
||||
href: volume-activation/remove-products-vamt.md
|
||||
- name: Manage Product Keys
|
||||
- name: Manage product keys
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/manage-product-keys-vamt.md
|
||||
- name: Add and Remove a Product Key
|
||||
- name: Add and remove a product key
|
||||
href: volume-activation/add-remove-product-key-vamt.md
|
||||
- name: Install a Product Key
|
||||
- name: Install a product key
|
||||
href: volume-activation/install-product-key-vamt.md
|
||||
- name: Install a KMS Client Key
|
||||
- name: Install a KMS client key
|
||||
href: volume-activation/install-kms-client-key-vamt.md
|
||||
- name: Manage Activations
|
||||
- name: Manage activations
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/manage-activations-vamt.md
|
||||
- name: Run Online Activation
|
||||
- name: Run online activation
|
||||
href: volume-activation/online-activation-vamt.md
|
||||
- name: Run Proxy Activation
|
||||
- name: Run proxy activation
|
||||
href: volume-activation/proxy-activation-vamt.md
|
||||
- name: Run KMS Activation
|
||||
- name: Run KMS activation
|
||||
href: volume-activation/kms-activation-vamt.md
|
||||
- name: Run Local Reactivation
|
||||
- name: Run local reactivation
|
||||
href: volume-activation/local-reactivation-vamt.md
|
||||
- name: Activate an Active Directory Forest Online
|
||||
- name: Activate an Active Directory forest online
|
||||
href: volume-activation/activate-forest-vamt.md
|
||||
- name: Activate by Proxy an Active Directory Forest
|
||||
- name: Activate by proxy an Active Directory forest
|
||||
href: volume-activation/activate-forest-by-proxy-vamt.md
|
||||
- name: Manage VAMT Data
|
||||
- name: Manage VAMT data
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/manage-vamt-data.md
|
||||
- name: Import and Export VAMT Data
|
||||
- name: Import and export VAMT data
|
||||
href: volume-activation/import-export-vamt-data.md
|
||||
- name: Use VAMT in Windows PowerShell
|
||||
href: volume-activation/use-vamt-in-windows-powershell.md
|
||||
- name: VAMT Step-by-Step Scenarios
|
||||
items:
|
||||
- name: Overview
|
||||
href: volume-activation/vamt-step-by-step.md
|
||||
- name: "Scenario 1: Online Activation"
|
||||
href: volume-activation/scenario-online-activation-vamt.md
|
||||
- name: "Scenario 2: Proxy Activation"
|
||||
href: volume-activation/scenario-proxy-activation-vamt.md
|
||||
- name: "Scenario 3: KMS Client Activation"
|
||||
href: volume-activation/scenario-kms-activation-vamt.md
|
||||
- name: VAMT Known Issues
|
||||
href: volume-activation/vamt-known-issues.md
|
||||
- name: Information sent to Microsoft during activation
|
||||
href: volume-activation/appendix-information-sent-to-microsoft-during-activation-client.md
|
||||
- name: VAMT step-by-step scenarios
|
||||
items:
|
||||
- name: "Scenario 1: online activation"
|
||||
href: volume-activation/scenario-online-activation-vamt.md
|
||||
- name: "Scenario 2: proxy activation"
|
||||
href: volume-activation/scenario-proxy-activation-vamt.md
|
||||
- name: "Scenario 3: KMS client activation"
|
||||
href: volume-activation/scenario-kms-activation-vamt.md
|
||||
- name: VAMT known issues
|
||||
href: volume-activation/vamt-known-issues.md
|
||||
- name: Monitor
|
||||
items:
|
||||
- name: Windows Update for Business reports
|
||||
|
||||
@ -1,16 +1,14 @@
|
||||
---
|
||||
title: Deploy Windows Enterprise licenses
|
||||
description: Steps to deploy Windows Enterprise licenses for Windows Enterprise E3 or E5 subscription activation, or for Windows Enterprise E3 in CSP.
|
||||
author: frankroj
|
||||
ms.author: frankroj
|
||||
manager: aaroncz
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: how-to
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier2
|
||||
ms.date: 03/04/2024
|
||||
zone_pivot_groups: windows-versions-11-10
|
||||
appliesto:
|
||||
|
||||
@ -11,10 +11,12 @@
|
||||
href: waas-delivery-optimization-faq.yml
|
||||
- name: Configure Delivery Optimization for Windows
|
||||
items:
|
||||
- name: Set up Delivery Optimization for Windows
|
||||
href: waas-delivery-optimization-setup.md
|
||||
- name: Delivery Optimization configuration considerations
|
||||
href: delivery-optimization-configure.md
|
||||
- name: Monitor Delivery Optimization for Windows
|
||||
href: waas-delivery-optimization-monitor.md
|
||||
- name: Troubleshoot Delivery Optimization
|
||||
href: delivery-optimization-troubleshoot.md
|
||||
- name: Configure Delivery Optimization settings using Microsoft Intune
|
||||
href: /mem/intune/configuration/delivery-optimization-windows
|
||||
- name: Resources for Delivery Optimization
|
||||
@ -27,8 +29,6 @@
|
||||
href: delivery-optimization-proxy.md
|
||||
- name: Testing Delivery Optimization
|
||||
href: delivery-optimization-test.md
|
||||
- name: Delivery Optimization Troubleshooter
|
||||
href: https://aka.ms/do-fix
|
||||
- name: Microsoft Connected Cache
|
||||
items:
|
||||
- name: What is Microsoft Connected Cache?
|
||||
|
||||
243
windows/deployment/do/delivery-optimization-configure.md
Normal file
243
windows/deployment/do/delivery-optimization-configure.md
Normal file
@ -0,0 +1,243 @@
|
||||
---
|
||||
title: Configure Delivery Optimization for Windows
|
||||
description: In this article, learn about the different configuration considerations to optimize Delivery Optimization (DO) in your environment.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
author: cmknox
|
||||
ms.author: carmenf
|
||||
ms.reviewer: mstewart
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- tier3
|
||||
- essentials-get-started
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization target=_blank>Delivery Optimization</a>
|
||||
ms.date: 07/23/2024
|
||||
---
|
||||
|
||||
# Configure Delivery Optimization (DO) for Windows
|
||||
|
||||
This article describes the different configuration considerations to optimize Delivery Optimization (DO) in your environment.
|
||||
|
||||
## Delivery Optimization set up considerations
|
||||
|
||||
Use this checklist to guide you through different aspects when modifying Delivery Optimization configurations for your environment.
|
||||
|
||||
1. Prerequisites to allow Delivery Optimization communication
|
||||
1. Evaluate Delivery Optimization policies based on the following items:
|
||||
|
||||
* Network topology
|
||||
* Organization size
|
||||
* System resources
|
||||
* Improve P2P efficiencies
|
||||
|
||||
1. Using Connected Cache (MCC)
|
||||
1. Choose where to set Delivery Optimization policies
|
||||
|
||||
## 1. Prerequisites to allow Delivery Optimization communication
|
||||
|
||||
:::image type="content" source="images/do-setup-allow-communication.png" alt-text="Screenshot of the considerations to allow Delivery Optimization communication." lightbox="images/do-setup-allow-communication.png":::
|
||||
|
||||
Delivery Optimization (DO) is used to download Microsoft content from different sources (HTTP source, peers, and/or dedicated cache solution). It requires communication between the DO client and services to find the best and most reliable sources of content. For this technology to work, the DO client running on the Windows device must be able to reach the DO cloud service.
|
||||
|
||||
Find out more about the requirements for Firewall, Proxy, and Port settings to enable Delivery Optimization communication.
|
||||
|
||||
### Firewall
|
||||
|
||||
There are service endpoints that you need to permit through your Firewall to communicate with the Delivery Optimization service. Check the [full list](waas-delivery-optimization-faq.yml#what-hostnames-should-i-allow-through-my-firewall-to-support-delivery-optimization) of endpoints to permit.
|
||||
|
||||
### Proxy
|
||||
|
||||
To allow peer-to-peer (P2P) to work properly, you need to allow direct calls to the Delivery Optimization service from your devices. When using a proxy, you want to bypass calls from the Delivery Optimization service (*.prod.do.dsp.mp.microsoft.com).
|
||||
|
||||
#### Local proxy
|
||||
|
||||
For downloads from HTTP sources, Delivery Optimization can use the automatic proxy discovery capability of WinHttp to handle communication with the proxy server. It's important to know that Delivery Optimization uses byte range requests, so you'll want to make sure your proxy allows this capability. [Learn more](delivery-optimization-proxy.md) about using Delivery Optimization with a proxy server.
|
||||
|
||||
#### Cloud proxy
|
||||
|
||||
If you're using a cloud proxy, the calls to the DO service are funneled through your cloud proxy and the public IP address of the devices is altered, preventing P2P from working properly. To avoid any issues, you should configure it to allow Delivery Optimization traffic to [bypass the proxy](waas-delivery-optimization-faq.yml#what-is-the-recommended-configuration-for-delivery-optimization-used-with-cloud-proxies). Otherwise, you may experience reduced performance and increased bandwidth consumption.
|
||||
|
||||
### Ports
|
||||
|
||||
Delivery Optimization requires the use of certain ports to deliver content. Make sure all the [required ports](waas-delivery-optimization-faq.yml#which-ports-does-delivery-optimization-use) are open to make Delivery Optimization work seamlessly.
|
||||
|
||||
| Port | Protocol | Function |
|
||||
|---------|-------------------|----------|
|
||||
| 7680 | TCP/IP | Listen for P2P using TCP/IP |
|
||||
| 3544 | TCP/IP | Use Teredo to discover and connect to peers across NATs |
|
||||
| 443 | HTTPS / TLS 1.2 | Use to communicate Delivery Optimization client and service |
|
||||
|
||||
## 2. Evaluate Delivery Optimization policies
|
||||
|
||||
There are a range of [Delivery Optimization settings](waas-delivery-optimization-reference.md) available to meet the needs of your environment. To fully leverage Delivery Optimization, you should focus on key areas to determine the most suitable settings for your unique environment.
|
||||
|
||||
### 2a. Network topology
|
||||
|
||||
:::image type="content" source="images/do-setup-network-topology.png" alt-text="Screenshot of Delivery Optimization network topology considerations." lightbox="images/do-setup-network-topology.png":::
|
||||
|
||||
Peer groups can be defined in Delivery Optimization using a combination of settings such as [DODownloadMode](waas-delivery-optimization-reference.md#download-mode), [DOGroupID](waas-delivery-optimization-reference.md#group-id), [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids), and [DORestrictPeerSelection](waas-delivery-optimization-reference.md#select-a-method-to-restrict-peer-selection). *The combination of settings used depends on your desired peer group(s) and your network topology.*
|
||||
|
||||
#### Peering setup options
|
||||
|
||||
Delivery Optimization can use P2P to help improve bandwidth efficiencies. The section outlines the different options available to define peer groups for your environment.
|
||||
|
||||
##### Local area network (LAN)
|
||||
|
||||
To define a peer group limited to your LAN, choose [DODownloadMode](waas-delivery-optimization-reference.md#download-mode) (1), LAN-mode. This download mode setting includes any devices that share the same public IP address when they connect to the Internet (behind the same NAT) in a single peer group.
|
||||
|
||||
> [!NOTE]
|
||||
> Consider using Group download mode and/or limiting peer selection to the subnet if your network topology is a Hub and Spoke.
|
||||
|
||||
##### Wide area network (WAN)
|
||||
|
||||
To achieve peer groups across NATs within the same site, over the WAN, or to have more control in your local environment, use download mode '2', Group-mode. Group download mode allows you to define a unique GUID Group ID or use existing logical groupings (for example, AD Site) in your enterprise with the [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids) setting to identify a peer group.
|
||||
|
||||
##### GroupIDSource default behavior
|
||||
|
||||
There are several options for identifying your Group ID using the [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids). The default behavior, when the [DOGroupID](waas-delivery-optimization-reference.md#group-id) or [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids) policies aren't set, is to determine the Group ID using AD Site (1), Authenticated domain SID (2), or Microsoft Entra tenant ID (5). [Learn more](waas-delivery-optimization-reference.md#select-the-source-of-group-ids) about all DOGroupIDSource available options.
|
||||
|
||||
> [!NOTE]
|
||||
> If your peer group spans across NATs, the Teredo service will be used on port 3544.
|
||||
>
|
||||
> For Configuration Manager users, we recommend leveraging existing [boundary groups](/mem/configmgr/core/plan-design/hierarchy/fundamental-concepts-for-content-management#delivery-optimization) to define the peer groups.
|
||||
|
||||
##### Restrict peer selection
|
||||
|
||||
If your environment requires a more granular approach, you can use the restrict peer discovery setting alongside the download mode to achieve more control. For example, if you have several different subnets behind the same NAT but want to limit your peer groups to a single subnet, choose [DODownloadMode](waas-delivery-optimization-reference.md#download-mode) (1) and [DORestrictPeerSelection](waas-delivery-optimization-reference.md#select-a-method-to-restrict-peer-selection) (Subnet). This setting can be used with any of the peer-related download modes (1, 2, or 3).
|
||||
|
||||
#### Nonpeering options
|
||||
|
||||
There are two valid download modes that don't use P2P functionality to deliver content; download modes (0) and (99). Download mode (0) uses additional metadata provided by the Delivery Optimization services for a peerless, reliable, and efficient download experience. Download mode (99) will provide a reliable download experience over HTTP from the download's original source or Microsoft, with no other checks.
|
||||
|
||||
#### Peering with VPN
|
||||
|
||||
By default, if Delivery Optimization detects a VPN, peering isn't used. To change this behavior, use the [DOAllowVPNPeerCaching](waas-delivery-optimization-reference.md#enable-peer-caching-while-the-device-connects-via-vpn) policy. The Delivery Optimization client looks in the network adapter's 'Description' and 'FriendlyName' strings to determine VPN usage. To allow greater flexibility for VPN identification, use the [DOVpnKeywords](waas-delivery-optimization-reference.md#vpn-keywords) to add descriptors for a particular VPN you use in your organization.
|
||||
|
||||
> [!NOTE]
|
||||
> The default keyword list is "VPN", "Secure", and "Virtual Private Network". For example, "MYVPN" matches the "VPN" keyword and would be detected as a VPN connection.
|
||||
|
||||
### 2b. Organization size
|
||||
|
||||
:::image type="content" source="images/do-setup-org-size.png" alt-text="Screenshot of optimizing P2P usage for your organization." lightbox="images/do-setup-org-size.png":::
|
||||
|
||||
Delivery Optimization is designed to perform best in a large-scale environment with many devices. Depending on the size of the environment, you should evaluate the value of the [DOMinFileSizeToCache](waas-delivery-optimization-reference.md#minimum-peer-caching-content-file-size) to optimize peering.
|
||||
|
||||
#### Minimum file size to cache
|
||||
|
||||
Content peering has a limited number of slots available at any given time. By default, only content files that are 50 MB or larger can be used for peering. In an environment with more than 30 devices, change the [DOMinFileSizeToCache](waas-delivery-optimization-reference.md#minimum-peer-caching-content-file-size) to a lower value (10 MB), to have more content available for peering, which can be distributed among many devices. For an even larger number of devices (>100), you can raise this setting to (1 MB).
|
||||
|
||||
#### Mobile devices
|
||||
|
||||
By default, P2P capabilities aren't enabled for devices using a battery. If there are many mobile devices in your environment, consider enabling the [DOMinBatteryPercentageAllowedToUpload](waas-delivery-optimization-reference.md#allow-uploads-while-the-device-is-on-battery-while-under-set-battery-level) policy to 60%, to use peering while on battery.
|
||||
|
||||
### 2c. System resources
|
||||
|
||||
:::image type="content" source="images/do-setup-system-resources.png" alt-text="Screenshot of Delivery Optimization system resources considerations." lightbox="images/do-setup-system-resources.png":::
|
||||
|
||||
There are some Delivery Optimization configurations that can make an impact when various system resources are available.
|
||||
|
||||
#### Disk size
|
||||
|
||||
Alter the minimum disk size (default is 32 GB) a device must have to use peering with the [DOMinDiskSizeAllowedToPeer](waas-delivery-optimization-reference.md#minimum-disk-size-allowed-to-use-peer-caching) setting.
|
||||
|
||||
#### Optimize cache size
|
||||
|
||||
You can also manage the amount of space the Delivery Optimization cache uses with the following settings: [DOMaxCacheSize](waas-delivery-optimization-reference.md#max-cache-size) (default is 20%) and [DOAbsoluteMaxCacheSize](waas-delivery-optimization-reference.md#absolute-max-cache-size) (default isn't configured).
|
||||
|
||||
#### RAM size
|
||||
|
||||
Control the minimum amount of RAM (inclusive) allowed to use peer caching (default is 4 GB), with [DOMinRAMAllowedToPeer](waas-delivery-optimization-reference.md#minimum-ram-inclusive-allowed-to-use-peer-caching).
|
||||
|
||||
#### Large number of devices with idle system resources
|
||||
|
||||
In an environment with devices that are plugged in and have ample free disk space try increasing the content expiration interval of [DOMaxCacheAge](waas-delivery-optimization-reference.md#max-cache-age) to seven or more (up to 30 days). You can take advantage of these devices, using them as excellent upload sources to upload more content over a longer period.
|
||||
|
||||
### 2d. Improve P2P efficiency
|
||||
|
||||
:::image type="content" source="images/do-setup-improve-efficiency.png" alt-text="Screenshot of Delivery Optimization improve efficiency considerations." lightbox="images/do-setup-improve-efficiency.png":::
|
||||
|
||||
Looking to improve P2P efficiency? Some of the most powerful settings you can change that could have a significant impact within your environment include:
|
||||
|
||||
- Help optimize peer connection over HTTP connections using the [DOMinBackgroundQoS](waas-delivery-optimization-reference.md#minimum-background-qos) policy. A good value for the [DOMinBackgroundQoS](waas-delivery-optimization-reference.md#minimum-background-qos) policy is something lower than the average download speed seen in your network. For example, if your average speed is 1000 KB/s, set this policy to 500 KB/s.
|
||||
- Improve chances of downloading from peers and/or cache server by delaying the time DO attempts to make connections before falling back to the HTTP source. The set of delay-related policies include:
|
||||
- [DODelayBackgroundDownloadFromHttp](waas-delivery-optimization-reference.md#delay-background-download-from-http-in-secs)
|
||||
- [DODelayForegroundDownloadFromHttp](waas-delivery-optimization-reference.md#delay-foreground-download-from-http-in-secs)
|
||||
|
||||
To improve efficiencies from peers or a dedicated cache server, a good starting point is 60 seconds for background settings and 30 seconds for foreground settings.
|
||||
|
||||
> [!NOTE]
|
||||
> Not all content types are eligible for P2P. Refer to the [complete list](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) to learn more.
|
||||
|
||||
#### Bandwidth throttling options
|
||||
|
||||
Regardless of P2P, consider setting the following policies to avoid network disruption.
|
||||
|
||||
- Manage network usage as a percentage or absolute value. These policies include:
|
||||
- [DOPercentageMaxBackgroundBandwidth](waas-delivery-optimization-reference.md#maximum-background-download-bandwidth)
|
||||
- [DOPercentageMaxForegroundBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth)
|
||||
- [DOMaxBackgroundDownloadBandwidth](waas-delivery-optimization-reference.md#maximum-background-download-bandwidth-in-kbs)
|
||||
- [DOMaxForegroundDownloadBandwidth](waas-delivery-optimization-reference.md#maximum-foreground-download-bandwidth-in-kbs)
|
||||
- Reduce disruptions by throttling differently at different times of day, using the following business hours policies:
|
||||
- [DOSetHoursToLimitBackgroundDownloadBandwidth](waas-delivery-optimization-reference.md#set-business-hours-to-limit-background-download-bandwidth)
|
||||
- [DOSetHoursToLimitForegroundDownloadBandwidth](waas-delivery-optimization-reference.md#set-business-hours-to-limit-foreground-download-bandwidth).
|
||||
|
||||
> [!NOTE]
|
||||
> The absolute policies are recommended in low bandwidth environments.
|
||||
|
||||
## 3. Using Connected Cache (MCC)
|
||||
|
||||
:::image type="content" source="images/do-setup-connected-cache.png" alt-text="Screenshot of Delivery Optimization options when using Connected Cache." lightbox="images/do-setup-connected-cache.png":::
|
||||
|
||||
- [DOCacheHost](waas-delivery-optimization-reference.md#cache-server-hostname) is the list of cache host server names, separated with commas. *Delivery Optimization client connects to the listed Microsoft Connected Cache servers in the order as they're listed.*
|
||||
- [DOCacheHostSource](waas-delivery-optimization-reference.md#cache-server-hostname-source) can be used to dynamically discover cache host servers on the network, using DHCP.
|
||||
- [DelayCacheServerFallbackBackground](waas-delivery-optimization-reference.md#delay-background-download-cache-server-fallback-in-secs) and [DelayCacheServerFallbackForeground](waas-delivery-optimization-reference.md#delay-foreground-download-cache-server-fallback-in-secs) are the delay policies to help improve chances of pulling content from the network cache host servers. (See recommended values in [Improve P2P efficiency](#2d-improve-p2p-efficiency) section above).
|
||||
- [DODisallowCacheServerDownloadsOnVPN](waas-delivery-optimization-reference.md#disallow-cache-server-downloads-on-vpn) allows control of the cache host server to supply content, when device is on a VPN connection.
|
||||
|
||||
## 4. Choose where to set Delivery Optimization policies
|
||||
|
||||
:::image type="content" source="images/do-setup-presence.png" alt-text="Screenshot of different product areas where you find Delivery Optimization." lightbox="images/do-setup-presence.png":::
|
||||
|
||||
### Group Policies
|
||||
|
||||
Use Group Policy to manage Delivery Optimization settings here,
|
||||
|
||||
`Computer Configuration\Administrative Templates\Windows Components\Delivery Optimization`
|
||||
|
||||
### MDM Policies
|
||||
|
||||
Use MDM to manage Delivery Optimization settings here,
|
||||
|
||||
`.Vendor/MSFT/Policy/Config/DeliveryOptimization/`
|
||||
|
||||
Delivery Optimization is integrated with both Microsoft Endpoint Manager and Configuration Manager.
|
||||
|
||||
- [Microsoft Endpoint Manager (MEM)](/mem/intune/configuration/delivery-optimization-windows)
|
||||
- [Microsoft Endpoint Configuration Manager (MECM)](/mem/configmgr/sum/deploy-use/optimize-windows-10-update-delivery)
|
||||
|
||||
## Summary of basic configuration recommendations
|
||||
|
||||
| Use case | Policy | Recommended value |
|
||||
| ----- | ----- | ----------------- |
|
||||
| Use P2P | DownloadMode | 1 or 2 |
|
||||
| Don't use P2P | DownloadMode | 0 |
|
||||
| Number of devices in the organization | MinFileSizeToCache | 1 MB for peer group > 100 devices |
|
||||
| Idle system resources | MaxCacheAge | 7 days (604800 seconds) |
|
||||
| Improve P2P efficiency | MinBackgroundQoS and DelayBackgroundDownloadFromHttp / DelayForegroundDownloadFromHttp | 500 KB/s and 60/30 seconds |
|
||||
| Using Connected Cache? | DelayCacheServerFallbackBackground / DelayCacheServerFallbackForeground | 60/30 seconds |
|
||||
|
||||
## Monitor Delivery Optimization
|
||||
|
||||
Whether you opt for the default Delivery Optimization configurations or tailor them to suit your environment, you'll want to track the outcomes to see how they improve your efficiency. [Learn more](waas-delivery-optimization-monitor.md) about the monitoring options for Delivery Optimization.
|
||||
|
||||
## Troubleshoot Delivery Optimization
|
||||
|
||||
There could be many different reasons why Delivery Optimization isn't working in your environment. [Learn more](delivery-optimization-troubleshoot.md) about the DO Troubleshooter and common problems and solutions to help improve the experience of using Delivery Optimization.
|
||||
|
||||
## Test Delivery Optimization
|
||||
|
||||
[Learn more](delivery-optimization-test.md) about guidance on basic testing scenarios to see how Delivery Optimization works.
|
||||
@ -31,7 +31,7 @@ Use the table below to reference any particular content types or services endpoi
|
||||
| *.delivery.mp.microsoft.com | HTTP / 80 | Edge Browser | [Complete list](/deployedge/microsoft-edge-security-endpoints) of endpoints for Edge Browser. | Both |
|
||||
| *.officecdn.microsoft.com.edgesuite.net, *.officecdn.microsoft.com, *.cdn.office.net | HTTP / 80 | Office CDN updates | [Complete list](/office365/enterprise/office-365-endpoints) of endpoints for Office CDN updates. | Both |
|
||||
| *.manage.microsoft.com, *.swda01.manage.microsoft.com, *.swda02.manage.microsoft.com, *.swdb01.manage.microsoft.com, *.swdb02.manage.microsoft.com, *.swdc01.manage.microsoft.com, *.swdc02.manage.microsoft.com, *.swdd01.manage.microsoft.com, *.swdd02.manage.microsoft.com, *.swda01-mscdn.manage.microsoft.com, *.swda02-mscdn.manage.microsoft.com, *.swdb01-mscdn.manage.microsoft.com, *.swdb02-mscdn.manage.microsoft.com, *.swdc01-mscdn.manage.microsoft.com, *.swdc02-mscdn.manage.microsoft.com, *.swdd01-mscdn.manage.microsoft.com, *.swdd02-mscdn.manage.microsoft.com | HTTP / 80 </br> HTTPs / 443 | Intune Win32 Apps | [Complete list](/mem/intune/fundamentals/intune-endpoints) of endpoints for Intune Win32 Apps updates. | Both |
|
||||
| *.statics.teams.cdn.office.net | HTTP / 80 </br> HTTPs / 443 | Teams | | Both |
|
||||
| *.statics.teams.cdn.office.net | HTTP / 80 </br> HTTPs / 443 | Teams | Future support is planned for peering and Connected Cache | TBD |
|
||||
| *.assets1.xboxlive.com, *.assets2.xboxlive.com, *.dlassets.xboxlive.com, *.dlassets2.xboxlive.com, *.d1.xboxlive.com, *.d2.xboxlive.com, *.assets.xbox.com, *.xbl-dlassets-origin.xboxlive.com, *.assets-origin.xboxlive.com, *.xvcb1.xboxlive.com, *.xvcb2.xboxlive.com, *.xvcf1.xboxlive.com, *.xvcf2.xboxlive.com | HTTP / 80 | Xbox | | Both |
|
||||
| *.tlu.dl.adu.microsoft.com, *.nlu.dl.adu.microsoft.com, *.dcsfe.prod.adu.microsoft.com | HTTP / 80 | Device Update | [Complete list](/azure/iot-hub-device-update/) of endpoints for Device Update updates. | Both |
|
||||
| *.do.dsp.mp.microsoft.com | HTTP / 80 </br> HTTPs / 443 | Microsoft Connected Cache -> Delivery Optimization Services communication | [Complete list](../do/waas-delivery-optimization-faq.yml) of endpoints for Delivery Optimization only. | Connected Cache Managed in Azure |
|
||||
|
||||
@ -14,7 +14,7 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization target=_blank>Delivery Optimization</a>
|
||||
ms.date: 11/08/2022
|
||||
ms.date: 07/23/2024
|
||||
---
|
||||
|
||||
# Testing Delivery Optimization
|
||||
@ -31,7 +31,7 @@ One of the most powerful advantages of using Delivery Optimization is the abilit
|
||||
|
||||
## Monitoring the Results
|
||||
|
||||
Since Delivery Optimization is on by default, you're able to monitor the value either through the Windows Settings for 'Delivery Optimization' using Delivery Optimization PowerShell [cmdlets.](waas-delivery-optimization-setup.md), and/or via the [Windows Update for Business Report](../update/wufb-reports-workbook.md) experience in Azure.
|
||||
Since Delivery Optimization is on by default, you're able to monitor the value either through the Windows Settings for 'Delivery Optimization' using Delivery Optimization PowerShell [cmdlets.](waas-delivery-optimization-reference.md), and/or via the [Windows Update for Business Report](../update/wufb-reports-workbook.md) experience in Azure.
|
||||
|
||||
In the case where Delivery Optimization isn't working in your environment, it's important to investigate to get to the root of the problem. We recommend a test environment be created to easily evaluate typical devices to ensure Delivery Optimization is working properly. For starters, 'Scenario 1: Basic Setup' should be created to test the use of Delivery Optimization between two machines. This scenario is designed to eliminate any noise in the environment to ensure there's nothing preventing Delivery Optimization from working on the devices. Once you have a baseline, you can expand the test environment for more sophisticated tests.
|
||||
|
||||
@ -221,4 +221,4 @@ Using Delivery Optimization can help make a significant impact in customer envir
|
||||
|
||||
The testing scenarios found in this document help to show a controlled test environment, helping to prevent updates from interrupting the peering results. The other, a more real-world case, demonstrates how content available across peers will be used as the source of the content.
|
||||
|
||||
If there are issues found while testing, the Delivery Optimization PowerShell [cmdlets](waas-delivery-optimization-setup.md) can be a helpful tool to help explain what is happening in the environment.
|
||||
If there are issues found while testing, the Delivery Optimization PowerShell [cmdlets](waas-delivery-optimization-reference.md) can be a helpful tool to help explain what is happening in the environment.
|
||||
|
||||
85
windows/deployment/do/delivery-optimization-troubleshoot.md
Normal file
85
windows/deployment/do/delivery-optimization-troubleshoot.md
Normal file
@ -0,0 +1,85 @@
|
||||
---
|
||||
title: Troubleshoot Delivery Optimization
|
||||
description: In this article, learn how to troubleshoot Delivery Optimization.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
author: cmknox
|
||||
ms.author: carmenf
|
||||
ms.reviewer: mstewart
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- tier3
|
||||
- essentials-get-started
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization target=_blank>Delivery Optimization</a>
|
||||
ms.date: 07/23/2024
|
||||
---
|
||||
|
||||
# Troubleshoot Delivery Optimization
|
||||
|
||||
This article discusses how to troubleshoot Delivery Optimization.
|
||||
|
||||
## DO Troubleshooter
|
||||
|
||||
[Check out](https://aka.ms/do-fix) for the new Delivery Optimization Troubleshooter. This tool provides a device health check to verify the device is set up properly to use Delivery Optimization. To scope the output more specifically, use one of the available switches:
|
||||
|
||||
- -HealthCheck: Provides an overall check of the device setup to ensure Delivery Optimization communication is possible on the device.
|
||||
- -P2P: Provides output specific to P2P settings, efficiency, and errors.
|
||||
- -MCC: Provides output specific to MCC settings and verifies the client can access the cache server.
|
||||
|
||||
## Common problems and solutions
|
||||
|
||||
This section summarizes common problems and some solutions to try.
|
||||
|
||||
### If you don't see any bytes from peers
|
||||
|
||||
If you don't see any bytes coming from peers, the cause might be one of the following issues:
|
||||
|
||||
- Clients aren't able to reach the Delivery Optimization cloud services.
|
||||
- The cloud service doesn't see other peers on the network.
|
||||
- Clients aren't able to connect to peers that are offered back from the cloud service.
|
||||
- None of the computers on the network are getting updates from peers.
|
||||
|
||||
### Clients aren't able to reach the Delivery Optimization cloud services
|
||||
|
||||
Try these steps:
|
||||
|
||||
1. Start a download of an app that is larger than 50 MB from the Store (for example "Candy Crush Saga").
|
||||
1. Run `Get-DeliveryOptimizationStatus` from an elevated PowerShell window and observe the [DODownloadMode](waas-delivery-optimization-reference.md#download-mode) setting. For peering to work, download mode should be 1, 2, or 3.
|
||||
1. If the download mode is 99, it could indicate your device is unable to reach the Delivery Optimization cloud services. Ensure that the Delivery Optimization host names are allowed access: most importantly **\*.prod.do.dsp.mp.microsoft.com**.
|
||||
|
||||
#### The cloud service doesn't see other peers on the network
|
||||
|
||||
Try these steps:
|
||||
|
||||
1. Download the same app on two different devices on the same network, waiting 10 - 15 minutes between downloads.
|
||||
1. Run `Get-DeliveryOptimizationStatus` from an elevated PowerShell window and ensure that **[DODownloadMode](waas-delivery-optimization-reference.md#download-mode)** is 1 or 2 on both devices.
|
||||
1. Run `Get-DeliveryOptimizationPerfSnap` from an elevated PowerShell window on the second device. The **NumberOfPeers** field should be nonzero.
|
||||
1. If the number of peers is zero and **[DODownloadMode](waas-delivery-optimization-reference.md#download-mode)** is 1, ensure that both devices are using the same public IP address to reach the internet (you can easily do this by opening a browser window and do a search for "what is my IP"). In the case where devices aren't reporting the same public IP address, configure **[DODownloadMode](waas-delivery-optimization-reference.md#download-mode)** to 2 (Group) and use a custom **[DOGroupID (Guid)](waas-delivery-optimization-reference.md#group-id)**.
|
||||
|
||||
> [!NOTE]
|
||||
> Starting in Windows 10, version 2004, `Get-DeliveryOptimizationStatus` has a new option `-PeerInfo` which returns a real-time list of potential peers per file, including which peers are successfully connected and the total bytes sent or received from each peer.
|
||||
|
||||
### Clients aren't able to connect to peers offered by the cloud service
|
||||
|
||||
Try a Telnet test between two devices on the network to ensure they can connect using port 7680. Follow these steps:
|
||||
|
||||
1. Install Telnet by running `dism /online /Enable-Feature /FeatureName:TelnetClient` from an elevated command prompt.
|
||||
1. Run the test. For example, if you're on device with IP 192.168.8.12 and you're trying to test the connection to 192.168.9.17 run `telnet 192.168.9.17 7680` (the syntax is *telnet [destination IP] [port]*. When you see a connection error or a blinking cursor like this /_. The blinking cursor means success.
|
||||
|
||||
> [!NOTE]
|
||||
> You can also use [Test-NetConnection](/powershell/module/nettcpip/test-netconnection) instead of Telnet to run the test.
|
||||
> **Test-NetConnection -ComputerName 192.168.9.17 -Port 7680**
|
||||
|
||||
### None of the computers on the network are getting updates from peers
|
||||
|
||||
Check Delivery Optimization settings that could limit participation in peer caching. Check whether the following settings in assigned group policies, local group policies, or MDM policies are too restrictive:
|
||||
|
||||
- Minimum RAM (inclusive) allowed to use peer caching
|
||||
- Minimum disk size allowed to use peer caching
|
||||
- Enable peer caching while the device connects using VPN.
|
||||
- Allow uploads when the device is on battery while under the set battery level
|
||||
BIN
windows/deployment/do/images/do-setup-allow-communication.png
Normal file
BIN
windows/deployment/do/images/do-setup-allow-communication.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 61 KiB |
BIN
windows/deployment/do/images/do-setup-connected-cache.png
Normal file
BIN
windows/deployment/do/images/do-setup-connected-cache.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
BIN
windows/deployment/do/images/do-setup-improve-efficiency.png
Normal file
BIN
windows/deployment/do/images/do-setup-improve-efficiency.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
BIN
windows/deployment/do/images/do-setup-network-topology.png
Normal file
BIN
windows/deployment/do/images/do-setup-network-topology.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 69 KiB |
BIN
windows/deployment/do/images/do-setup-org-size.png
Normal file
BIN
windows/deployment/do/images/do-setup-org-size.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 32 KiB |
BIN
windows/deployment/do/images/do-setup-presence.png
Normal file
BIN
windows/deployment/do/images/do-setup-presence.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
BIN
windows/deployment/do/images/do-setup-system-resources.png
Normal file
BIN
windows/deployment/do/images/do-setup-system-resources.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 31 KiB |
@ -41,12 +41,12 @@ landingContent:
|
||||
linkLists:
|
||||
- linkListType: how-to-guide
|
||||
links:
|
||||
- text: Delivery Optimization recommended settings
|
||||
url: waas-delivery-optimization-setup.md#recommended-delivery-optimization-settings
|
||||
- text: Delivery Optimization configuration considerations
|
||||
url: delivery-optimization-configure.md
|
||||
- text: Monitor Delivery Optimization for Windows
|
||||
url: waas-delivery-optimization-monitor.md
|
||||
- text: Troubleshoot Delivery Optimization
|
||||
url: waas-delivery-optimization-setup.md#troubleshooting
|
||||
url: delivery-optimization-troubleshoot.md
|
||||
- text: Delivery Optimization Frequently Asked Questions
|
||||
url: ../do/waas-delivery-optimization-faq.yml
|
||||
- text: Submit feedback
|
||||
|
||||
@ -21,7 +21,7 @@ ms.date: 05/23/2024
|
||||
|
||||
> **Looking for Group Policy objects?** See [Delivery Optimization reference](waas-delivery-optimization-reference.md) or the main spreadsheet available at the Download Center [for Windows 11](https://www.microsoft.com/en-us/download/details.aspx?id=104594) or [for Windows 10](https://www.microsoft.com/en-us/download/details.aspx?id=104678).
|
||||
|
||||
There are many configuration options you can set in Delivery Optimization to customize the content delivery experience specific to your environment needs. This article summarizes those configurations for your reference. If you just need an overview of Delivery Optimization, see [What is Delivery Optimization](waas-delivery-optimization.md). If you need information about setting up Delivery Optimization, including tips for the best settings in different scenarios, see [Set up Delivery Optimization for Windows](waas-delivery-optimization-setup.md).
|
||||
There are many configuration options you can set in Delivery Optimization to customize the content delivery experience specific to your environment needs. This article summarizes those configurations for your reference. If you just need an overview of Delivery Optimization, see [What is Delivery Optimization](waas-delivery-optimization.md). If you need information about setting up Delivery Optimization, including tips for the best settings in different scenarios, see [Set up Delivery Optimization for Windows](delivery-optimization-configure.md).
|
||||
|
||||
## Delivery Optimization options
|
||||
|
||||
@ -127,7 +127,7 @@ Download mode dictates which download sources clients are allowed to use when do
|
||||
|
||||
| Download mode option | Functionality when configured |
|
||||
| --- | --- |
|
||||
| HTTP Only (0) | This setting disables peer-to-peer caching but still allows Delivery Optimization to download content over HTTP from the download's original source or a Microsoft Connected Cache server. This mode uses additional metadata provided by the Delivery Optimization cloud services for a peerless reliable and efficient download experience. |
|
||||
| HTTP Only (0) | This setting disables peer-to-peer caching but still allows Delivery Optimization to download content over HTTP from the download's original source or a Microsoft Connected Cache server. This mode uses additional metadata provided by the Delivery Optimization cloud services for a peerless, reliable and efficient download experience. |
|
||||
| LAN (**1 - Default**) | This default operating mode for Delivery Optimization enables peer sharing on the same network. The Delivery Optimization cloud service finds other clients that connect to the Internet using the same public IP as the target client. These clients then try to connect to other peers on the same network by using their private subnet IP.|
|
||||
| Group (2) | When group mode is set, the group is automatically selected based on the device's Active Directory Domain Services (AD DS) site (Windows 10, version 1607) or the domain the device is authenticated to (Windows 10, version 1511). In group mode, peering occurs across internal subnets, between devices that belong to the same group, including devices in remote offices. You can use GroupID option to create your own custom group independently of domains and AD DS sites. Starting with Windows 10, version 1803, you can use the GroupIDSource parameter to take advantage of other method to create groups dynamically. Group download mode is the recommended option for most organizations looking to achieve the best bandwidth optimization with Delivery Optimization. |
|
||||
| Internet (3) | Enable Internet peer sources for Delivery Optimization. |
|
||||
|
||||
@ -1,164 +0,0 @@
|
||||
---
|
||||
title: Set up Delivery Optimization
|
||||
description: In this article, learn how to set up Delivery Optimization for use by Windows clients in your organization.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
author: cmknox
|
||||
ms.author: carmenf
|
||||
ms.reviewer: mstewart
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- tier3
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization target=_blank>Delivery Optimization</a>
|
||||
ms.date: 05/23/2024
|
||||
---
|
||||
|
||||
# Set up Delivery Optimization for Windows
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
## Set up Delivery Optimization
|
||||
|
||||
You can use Group Policy or an MDM solution like Intune to configure Delivery Optimization.
|
||||
|
||||
You find the Delivery Optimization settings in Group Policy under **Computer Configuration\Administrative Templates\Windows Components\Delivery Optimization**.
|
||||
|
||||
Starting with Microsoft Intune version 1902, you can set many Delivery Optimization policies as a profile, which you can then apply to groups of devices. For more information, see [Delivery Optimization settings in Microsoft Intune](/mem/intune/configuration/delivery-optimization-windows).
|
||||
|
||||
**Starting with Windows 10, version 1903**, you can use the Microsoft Entra tenant ID as a means to define groups. To set the value for [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids) to its new maximum value of 5.
|
||||
|
||||
## Allow service endpoints
|
||||
|
||||
When using a firewall, it's important that the Delivery Optimization Service endpoints are allowed and associated ports are open. For more information, see [Delivery Optimization FAQ](waas-delivery-optimization-faq.yml#what-hostnames-should-i-allow-through-my-firewall-to-support-delivery-optimization).
|
||||
|
||||
## Allow content endpoints
|
||||
|
||||
When using a firewall, it's important that the content endpoints are allowed and associated ports are open. For more information, see [Endpoints for Delivery Optimization and Microsoft Connected Cache content](delivery-optimization-endpoints.md).
|
||||
|
||||
## Recommended Delivery Optimization settings
|
||||
|
||||
Delivery Optimization offers a great many settings to fine-tune its behavior see [Delivery Optimization reference](waas-delivery-optimization-reference.md) for a comprehensive list, but for the most efficient performance, there are just a few key parameters that have the greatest impact if particular situations exist in your deployment. If you just need an overview of Delivery Optimization, see [Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md).
|
||||
|
||||
- Does your topology include multiple breakouts to the internet that is, a "hybrid WAN" or are there only a few connections to the internet, so that all requests appear to come from a single external IP address a "hub and spoke" topology?
|
||||
- If you use boundary groups in your topology, how many devices are present in a given group?
|
||||
- What percentage of your devices are mobile?
|
||||
- Do your devices have a lot of free space on their drives?
|
||||
- Do you have a lab scenario with many devices on AC power?
|
||||
|
||||
> [!NOTE]
|
||||
> These scenarios (and the recommended settings for each) are not mutually exclusive. It's possible that your deployment might involve more than one of these scenarios, in which case you can employ the related settings in any combination as needed. In all cases, however, "download mode" is the most important one to set.
|
||||
>
|
||||
> [!NOTE]
|
||||
> Microsoft Intune includes a profile to make it easier to set Delivery Optimization policies. For details, see [Delivery Optimization settings for Intune](/mem/intune/configuration/delivery-optimization-settings).
|
||||
|
||||
Quick-reference table:
|
||||
|
||||
| Use case | Policy | Recommended value | Reason |
|
||||
| --- | --- | --- | --- |
|
||||
| Hub & spoke topology | Download mode | 1 or 2 | Automatic grouping of peers to match your topology |
|
||||
| Sites with > 30 devices | Minimum file size to cache | 10 MB (or 1 MB) | Use peers-to-peer capability in more downloads |
|
||||
| Large number of mobile devices | Allow uploads on battery power | 60% | Increase # of devices that can upload while limiting battery drain |
|
||||
| Labs with AC-powered devices | Content expiration | 7 (up to 30) days | Leverage devices that can upload more for a longer period |
|
||||
|
||||
### Hybrid WAN scenario
|
||||
|
||||
For this scenario, grouping devices by domain allows devices to be included in peer downloads and uploads across VLANs. **Set Download Mode to 2 - Group**. The default group, when the GroupID or GroupIDSource policies aren't set, is the AD Site (1), Authenticated domain SID (2) or Microsoft Entra tenant ID (5), in that order. If your domain-based group is too wide, or your Active Directory sites aren't aligned with your site network topology, then you should consider other options for dynamically creating groups, for example by using the [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids) policy.
|
||||
|
||||
In Group Policy go to **Computer Configuration\Administrative Templates\Windows Components\Delivery Optimization** and set **Download mode** to **2**.
|
||||
|
||||
Using with MDM, go to **./Device/Vendor/MSFT/Policy/Config/DeliveryOptimization/** and set [DODownloadMode](/windows/client-management/mdm/policy-csp-deliveryoptimization#dodownloadmode) to 1 or 2.
|
||||
|
||||
### Hub and spoke topology with boundary groups
|
||||
|
||||
The default download mode setting is **1**; this means all devices breaking out to the internet using the same public IP is considered as a single peer group. To prevent peer-to-peer activity across your WAN, you should set the download mode to **2**. If you have already defined Active Directory sites per hub or branch office, then you don't need to do anything else since the Active Directory sites are used by default as the source for creation of Group IDs. If you're not using Active Directory sites, you should set a different source for Groups by using the [DOGroupIDSource](waas-delivery-optimization-reference.md#select-the-source-of-group-ids) options or the [DORestrictPeerSelectionBy](waas-delivery-optimization-reference.md#select-a-method-to-restrict-peer-selection) policy to restrict the activity to the subnet.
|
||||
|
||||
With Group Policy go to **Computer Configuration\Administrative Templates\Windows Components\Delivery Optimization** and set **Download mode** to **2**.
|
||||
|
||||
Using MDM, go to **./Device/Vendor/MSFT/Policy/Config/DeliveryOptimization/** and set [DODownloadMode](/windows/client-management/mdm/policy-csp-deliveryoptimization#dodownloadmode) to **2**.
|
||||
|
||||
> [!NOTE]
|
||||
> For more information about using Delivery Optimization with Configuration Manager boundary groups, see [Delivery Optimization for Configuration Manager](/mem/configmgr/core/plan-design/hierarchy/fundamental-concepts-for-content-management#delivery-optimization).
|
||||
|
||||
### Large number of mobile devices
|
||||
|
||||
If you have a mobile workforce with a great many mobile devices, set Delivery Optimization to allow uploads on battery power, while limiting the use to prevent battery drain. A setting for **DOMinBatteryPercentageAllowedToUpload** of 60% is a good starting point, though you might want to adjust it later.
|
||||
|
||||
With Group Policy, go to **Computer Configuration\Administrative Templates\Windows Components\Delivery Optimization** and set **Allow uploads while the device is on battery while under set Battery level** to 60.
|
||||
|
||||
Using MDM, go to **./Device/Vendor/MSFT/Policy/Config/DeliveryOptimization/** and set [DOMinBatteryPercentageAllowedToUpload](/windows/client-management/mdm/policy-csp-deliveryoptimization#dominbatterypercentageallowedtoupload) to 60.
|
||||
|
||||
### Plentiful free space and large numbers of devices
|
||||
|
||||
Many devices now come with large internal drives. You can set Delivery Optimization to take better advantage of this space (especially if you have large numbers of devices) by changing the minimum file size to cache. If you have more than 30 devices in your local network or group, change it from the default 50 MB to 10 MB. If you have more than 100 devices (and are running Windows 10, version 1803 or later), set this value to 1 MB.
|
||||
|
||||
With Group Policy, go to **Computer Configuration\Administrative Templates\Windows Components\Delivery Optimization** and set **Minimum Peer Caching Content File Size** to 10 (if you have more than 30 devices) or 1 (if you have more than 100 devices).
|
||||
|
||||
Using MDM, go to **./Device/Vendor/MSFT/Policy/Config/DeliveryOptimization/** and set [DOMinFileSizeToCache](/windows/client-management/mdm/policy-csp-deliveryoptimization#dominfilesizetocache) to 100 (if you have more than 30 devices) or 1 (if you have more than 100 devices).
|
||||
|
||||
### Lab scenario
|
||||
|
||||
In a lab situation, you typically have a large number of devices that are plugged in and have a lot of free disk space. By increasing the content expiration interval, you can take advantage of these devices, using them as excellent upload sources in order to upload more content over a longer period.
|
||||
|
||||
With Group Policy, go to **Computer Configuration\Administrative Templates\Windows Components\Delivery Optimization** and set **Max Cache Age** to **604800** (7 days) or more (up to 30 days).
|
||||
|
||||
Using MDM, go to **./Device/Vendor/MSFT/Policy/Config/DeliveryOptimization/** and set [DOMaxCacheAge](/windows/client-management/mdm/policy-csp-deliveryoptimization#domaxcacheage) to 7 or more (up to 30 days).
|
||||
|
||||
[Learn more](delivery-optimization-test.md) about Delivery Optimization testing scenarios.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
This section summarizes common problems and some solutions to try.
|
||||
|
||||
### If you don't see any bytes from peers
|
||||
|
||||
If you don't see any bytes coming from peers the cause might be one of the following issues:
|
||||
|
||||
- Clients aren't able to reach the Delivery Optimization cloud services.
|
||||
- The cloud service doesn't see other peers on the network.
|
||||
- Clients aren't able to connect to peers that are offered back from the cloud service.
|
||||
- None of the computers on the network are getting updates from peers.
|
||||
|
||||
### Clients aren't able to reach the Delivery Optimization cloud services
|
||||
|
||||
Try these steps:
|
||||
|
||||
1. Start a download of an app that is larger than 50 MB from the Store (for example "Candy Crush Saga").
|
||||
2. Run `Get-DeliveryOptimizationStatus` from an elevated PowerShell window and observe the [DODownloadMode](waas-delivery-optimization-reference.md#download-mode) setting. For peering to work, download mode should be 1, 2, or 3.
|
||||
3. If the download mode is 99, it could indicate your device is unable to reach the Delivery Optimization cloud services. Ensure that the Delivery Optimization host names are allowed access: most importantly **\*.prod.do.dsp.mp.microsoft.com**.
|
||||
|
||||
### The cloud service doesn't see other peers on the network
|
||||
|
||||
Try these steps:
|
||||
|
||||
1. Download the same app on two different devices on the same network, waiting 10 - 15 minutes between downloads.
|
||||
2. Run `Get-DeliveryOptimizationStatus` from an elevated PowerShell window and ensure that **[DODownloadMode](waas-delivery-optimization-reference.md#download-mode)** is 1 or 2 on both devices.
|
||||
3. Run `Get-DeliveryOptimizationPerfSnap` from an elevated PowerShell window on the second device. The **NumberOfPeers** field should be nonzero.
|
||||
4. If the number of peers is zero and **[DODownloadMode](waas-delivery-optimization-reference.md#download-mode)** is 1, ensure that both devices are using the same public IP address to reach the internet (you can easily do this by opening a browser window and do a search for "what is my IP"). In the case where devices aren't reporting the same public IP address, configure **[DODownloadMode](waas-delivery-optimization-reference.md#download-mode)** to 2 (Group) and use a custom **[DOGroupID (Guid)](waas-delivery-optimization-reference.md#group-id)**.
|
||||
|
||||
> [!NOTE]
|
||||
> Starting in Windows 10, version 2004, `Get-DeliveryOptimizationStatus` has a new option `-PeerInfo` which returns a real-time list of potential peers per file, including which peers are successfully connected and the total bytes sent or received from each peer.
|
||||
|
||||
### Clients aren't able to connect to peers offered by the cloud service
|
||||
|
||||
Try a Telnet test between two devices on the network to ensure they can connect using port 7680. Follow these steps:
|
||||
|
||||
1. Install Telnet by running `dism /online /Enable-Feature /FeatureName:TelnetClient` from an elevated command prompt.
|
||||
2. Run the test. For example, if you are on device with IP 192.168.8.12 and you're trying to test the connection to 192.168.9.17 run `telnet 192.168.9.17 7680` (the syntax is *telnet [destination IP] [port]*. You'll either see a connection error or a blinking cursor like this /_. The blinking cursor means success.
|
||||
|
||||
> [!NOTE]
|
||||
> You can also use [Test-NetConnection](/powershell/module/nettcpip/test-netconnection) instead of Telnet to run the test.
|
||||
> **Test-NetConnection -ComputerName 192.168.9.17 -Port 7680**
|
||||
|
||||
### None of the computers on the network are getting updates from peers
|
||||
|
||||
Check Delivery Optimization settings that could limit participation in peer caching. Check whether the following settings in assigned group policies, local group policies, or MDM policies are too restrictive:
|
||||
|
||||
- Minimum RAM (inclusive) allowed to use peer caching
|
||||
- Minimum disk size allowed to use peer caching
|
||||
- Enable peer caching while the device connects using VPN.
|
||||
- Allow uploads when the device is on battery while under the set battery level
|
||||
@ -28,7 +28,7 @@ To use either the peer-to-peer functionality or the Microsoft Connected Cache fe
|
||||
|
||||
You can use Delivery Optimization with Windows Update, Windows Server Update Services (WSUS), Microsoft Intune/Windows Update for Business, or Microsoft Configuration Manager (when installation of Express Updates is enabled).
|
||||
|
||||
For information about setting up Delivery Optimization, including tips for the best settings in different scenarios, see [Set up Delivery Optimization](waas-delivery-optimization-setup.md). For a comprehensive list of all Delivery Optimization settings, see [Delivery Optimization reference](waas-delivery-optimization-reference.md).
|
||||
For information about setting up Delivery Optimization, including tips for the best settings in different scenarios, see [Set up Delivery Optimization](delivery-optimization-configure.md). For a comprehensive list of all Delivery Optimization settings, see [Delivery Optimization reference](waas-delivery-optimization-reference.md).
|
||||
|
||||
> [!NOTE]
|
||||
> WSUS can also use [BranchCache](../update/waas-branchcache.md) for content sharing and caching. If Delivery Optimization is enabled on devices that use BranchCache, Delivery Optimization will be used instead.
|
||||
@ -98,7 +98,7 @@ To gain a deeper understanding of the Delivery Optimization client-service commu
|
||||
|
||||
## Set up Delivery Optimization for Windows
|
||||
|
||||
[Learn more](waas-delivery-optimization-setup.md) about the Delivery Optimization settings to ensure proper setup in your environment.
|
||||
[Learn more](delivery-optimization-configure.md) about the Delivery Optimization settings to ensure proper setup in your environment.
|
||||
|
||||
## Delivery Optimization reference
|
||||
|
||||
|
||||
@ -49,7 +49,6 @@
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
},
|
||||
"titleSuffix": "Windows Deployment",
|
||||
"contributors_to_exclude": [
|
||||
"dstrome2",
|
||||
"rjagiewich",
|
||||
|
||||
@ -27,7 +27,7 @@ landingContent:
|
||||
- linkListType: concept
|
||||
links:
|
||||
- text: Plan for Windows 11
|
||||
url: /windows/whats-new/windows-11-plan?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
url: /windows/whats-new/windows-11-plan?context=/windows/deployment/context/context
|
||||
- text: Create a deployment plan
|
||||
url: update/create-deployment-plan.md
|
||||
- text: Define readiness criteria
|
||||
@ -44,7 +44,7 @@ landingContent:
|
||||
- linkListType: get-started
|
||||
links:
|
||||
- text: Prepare for Windows 11
|
||||
url: /windows/whats-new/windows-11-prepare?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
url: /windows/whats-new/windows-11-prepare?context=/windows/deployment/context/context
|
||||
- text: Prepare to deploy Windows updates
|
||||
url: update/prepare-deploy-windows.md
|
||||
- text: Prepare updates using Windows Update for Business
|
||||
@ -52,7 +52,7 @@ landingContent:
|
||||
- text: Evaluate and update infrastructure
|
||||
url: update/update-policies.md
|
||||
- text: Set up Delivery Optimization for Windows client updates
|
||||
url: do/waas-delivery-optimization-setup.md?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
url: do/delivery-optimization-configure.md?context=/windows/deployment/context/context
|
||||
- text: Prepare for imaging with Configuration Manager
|
||||
url: deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md
|
||||
|
||||
|
||||
@ -5,9 +5,9 @@ ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: overview
|
||||
ms.date: 06/25/2024
|
||||
author: mikolding
|
||||
ms.author: v-mikolding
|
||||
ms.reviewer: mstewart,thtrombl,v-fvalentyna,arcarley
|
||||
author: v-fvalentyna
|
||||
ms.author: v-fvalentyna
|
||||
ms.reviewer: mstewart,thtrombl,arcarley
|
||||
manager: aaroncz
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
|
||||
@ -50,4 +50,4 @@ Extensive advanced testing isn't required. Instead, only business-critical apps
|
||||
|
||||
This process repeats with each new feature update. These are small deployment projects, compared to the large projects that were necessary with the old three-to-five-year Windows release cycles.
|
||||
|
||||
Other technologies such as [BranchCache](waas-branchcache.md) and [Delivery Optimization](../do/waas-delivery-optimization-setup.md), both peer-to-peer distribution tools, can help with the distribution of the feature update installation files.
|
||||
Other technologies such as [BranchCache](waas-branchcache.md) and [Delivery Optimization](../do/delivery-optimization-configure.md), both peer-to-peer distribution tools, can help with the distribution of the feature update installation files.
|
||||
|
||||
@ -59,7 +59,7 @@ Windows Update for Business reports uses the following Delivery Optimization ter
|
||||
|
||||
## Calculations for Delivery Optimization
|
||||
|
||||
Each calculated values used in the Delivery Optimization report are listed below.
|
||||
The calculated values used in the Delivery Optimization report are listed below.
|
||||
|
||||
**Efficiency (%) Calculations**:
|
||||
|
||||
@ -188,7 +188,7 @@ A row in UCDOAggregatedStatus represents data summarized at the tenant level (Az
|
||||
If there's a Connected Cache server at the ISP level, BytesFromCache filters out any bytes coming the ISP's Connected Cache.
|
||||
|
||||
- **How do the results from the Delivery Optimization PowerShell cmdlets compare to the results in the report?**
|
||||
[Delivery Optimization PowerShell cmdlets](waas-delivery-optimization-setup.md#monitor-delivery-optimization) can be a powerful tool used to monitor Delivery Optimization data on the device. These cmdlets use the cache on the device. The data calculated in the report is taken from the Delivery Optimization telemetry events.
|
||||
[Delivery Optimization PowerShell cmdlets](waas-delivery-optimization-reference.md) can be a powerful tool used to monitor Delivery Optimization data on the device. These cmdlets use the cache on the device. The data calculated in the report is taken from the Delivery Optimization telemetry events.
|
||||
|
||||
- **The report represents the last 28 days of data, why do some queries include >= seven days?**
|
||||
The data in the report does represent the last 28 days of data. The query for last seven days is just to get the data for the latest snapshot from past seven days. It's possible that data is delayed for sometime and not available for current day, so we look for past 7 day snapshot in log analytics and show the latest snapshot.
|
||||
|
||||
@ -20,7 +20,7 @@ summary: |
|
||||
- [Is Windows Update for Business reports free?](#is-windows-update-for-business-reports-free)
|
||||
- [What Windows versions are supported?](#what-windows-versions-are-supported)
|
||||
|
||||
**Set up questions**:
|
||||
**Setup questions**:
|
||||
|
||||
- [How do you set up Windows Update for Business reports?](#how-do-you-set-up-windows-update-for-business-reports)
|
||||
- [Why is "Waiting for Windows Update for Business reports data" displayed on the page](#why-is--waiting-for-windows-update-for-business-reports-data--displayed-on-the-page)
|
||||
@ -183,7 +183,7 @@ sections:
|
||||
If there's a Connected Cache server at the ISP level, BytesFromCache filters out any bytes coming the ISP's Connected Cache.
|
||||
- question: How do the results from the Delivery Optimization PowerShell cmdlets compare to the results in the report?
|
||||
answer: |
|
||||
[Delivery Optimization PowerShell cmdlets](waas-delivery-optimization-setup.md#monitor-delivery-optimization) can be a powerful tool used to monitor Delivery Optimization data on the device. These cmdlets use the cache on the device. The data calculated in the report is taken from the Delivery Optimization events.
|
||||
[Delivery Optimization PowerShell cmdlets](waas-delivery-optimization-reference.md) can be a powerful tool used to monitor Delivery Optimization data on the device. These cmdlets use the cache on the device. The data calculated in the report is taken from the Delivery Optimization events.
|
||||
- question: The report represents the last 28 days of data, why do some queries include >= seven days?
|
||||
answer: |
|
||||
The data in the report does represent the last 28 days of data. The query for last seven days is just to get the data for the latest snapshot from past seven days. It's possible that data is delayed for sometime and not available for current day, so we look for past seven day snapshot in log analytics and show the latest snapshot.
|
||||
|
||||
@ -2,9 +2,9 @@
|
||||
title: Configure VDA for Windows subscription activation
|
||||
description: Learn how to configure virtual machines (VMs) to enable Windows 10 Subscription Activation in a Windows Virtual Desktop Access (VDA) scenario.
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
author: frankroj
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
ms.localizationpriority: medium
|
||||
|
||||
@ -1,17 +1,17 @@
|
||||
---
|
||||
title: Activate by Proxy an Active Directory Forest (Windows 10)
|
||||
title: Activate by proxy an Active Directory forest
|
||||
description: Learn how to use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate by proxy an Active Directory (AD) forest.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Activate by Proxy an Active Directory Forest
|
||||
# Activate by proxy an Active Directory forest
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate by proxy an Active Directory (AD) forest for an isolated workgroup that doesn't have Internet access. ADBA enables certain volume products to inherit activation from the domain.
|
||||
|
||||
@ -64,4 +64,4 @@ VAMT displays the **Activating Active Directory** dialog box until it completes
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Add and Remove Computers](add-remove-computers-vamt.md)
|
||||
[Add and remove computers](add-remove-computers-vamt.md)
|
||||
|
||||
@ -1,17 +1,17 @@
|
||||
---
|
||||
title: Activate an Active Directory Forest Online (Windows 10)
|
||||
title: Activate an Active Directory forest online
|
||||
description: Use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate an Active Directory (AD) forest online.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Activate an Active Directory Forest Online
|
||||
# Activate an Active Directory forest online
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) Active Directory-Based Activation (ADBA) function to activate an Active Directory (AD) forest over the Internet. ADBA enables certain products to inherit activation from the domain.
|
||||
|
||||
@ -51,5 +51,6 @@ The activated object and the date that it was created appear in the **Active Dir
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Scenario 1: Online Activation](scenario-online-activation-vamt.md)
|
||||
- [Add and Remove Computers](add-remove-computers-vamt.md)
|
||||
- [Scenario 1: online activation](scenario-online-activation-vamt.md)
|
||||
|
||||
- [Add and remove computers](add-remove-computers-vamt.md)
|
||||
|
||||
@ -1,18 +1,15 @@
|
||||
---
|
||||
title: Activate using Active Directory-based activation
|
||||
description: Learn how active directory-based activation is implemented as a role service that relies on Active Directory Domain Services (ADDS) to store activation objects.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
author: frankroj
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: how-to
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier2
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
|
||||
@ -28,8 +25,8 @@ appliesto:
|
||||
>
|
||||
> Looking for information on retail activation?
|
||||
>
|
||||
> - [Activate Windows](https://support.microsoft.com/help/12440/).
|
||||
> - [Product activation for Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644).
|
||||
> - [Activate Windows](https://support.microsoft.com/windows/activate-windows-c39005d4-95ee-b91e-b399-2820fda32227).
|
||||
> - [Product activation for Windows](https://support.microsoft.com/windows/product-activation-for-windows-online-support-telephone-numbers-35f6a805-1259-88b4-f5e9-b52cccef91a0).
|
||||
|
||||
Active Directory-based activation is implemented as a role service that relies on Active Directory Domain Services (ADDS) to store activation objects. Active Directory-based activation requires updating the forest schema with `adprep.exe` on a supported server OS. After the schema is updated, older domain controllers can still activate clients.
|
||||
|
||||
|
||||
@ -1,18 +1,15 @@
|
||||
---
|
||||
title: Activate using Key Management Service
|
||||
description: Learn how to use Key Management Service (KMS) to activate Windows.
|
||||
ms.reviewer: nganguly
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
author: frankroj
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: how-to
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier2
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
|
||||
@ -27,8 +24,8 @@ appliesto:
|
||||
>
|
||||
> For information on retail activation, see the following articles:
|
||||
>
|
||||
> - [Activate Windows](https://support.microsoft.com/help/12440/)
|
||||
> - [Product activation for Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644)
|
||||
> - [Activate Windows](https://support.microsoft.com/windows/activate-windows-c39005d4-95ee-b91e-b399-2820fda32227)
|
||||
> - [Product activation for Windows](https://support.microsoft.com/windows/product-activation-for-windows-online-support-telephone-numbers-35f6a805-1259-88b4-f5e9-b52cccef91a0)
|
||||
|
||||
Volume activation can be performed via Key Management Service (KMS). KMS can be hosted either on a client version of Windows or on Windows Server.
|
||||
|
||||
|
||||
@ -1,14 +1,14 @@
|
||||
---
|
||||
title: Activate clients running Windows
|
||||
description: Activate clients running Windows after configuring Key Management Service (KMS) or Active Directory-based activation.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
@ -24,8 +24,8 @@ appliesto:
|
||||
>
|
||||
> Looking for information on retail activation?
|
||||
>
|
||||
> - [Activate Windows](https://support.microsoft.com/help/12440/).
|
||||
> - [Product activation for Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644).
|
||||
> - [Activate Windows](https://support.microsoft.com/windows/activate-windows-c39005d4-95ee-b91e-b399-2820fda32227).
|
||||
> - [Product activation for Windows](https://support.microsoft.com/windows/product-activation-for-windows-online-support-telephone-numbers-35f6a805-1259-88b4-f5e9-b52cccef91a0).
|
||||
|
||||
After Key Management Service (KMS) or Active Directory-based activation is configured in a network, activating a client running Windows is easy. If the computer is configured with a Generic Volume License Key (GVLK), IT or the user don't need to take any action. It just works.
|
||||
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Active Directory-Based Activation Overview (Windows 10)
|
||||
title: Active Directory-based activation overview
|
||||
description: Enable your enterprise to activate its computers through a connection to their domain using Active Directory-Based Activation (ADBA).
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
|
||||
@ -1,24 +0,0 @@
|
||||
---
|
||||
title: Add and Manage Products
|
||||
description: Add client computers into the Volume Activation Management Tool (VAMT). After the computers are added, the products that are installed in the network can be managed.
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Add and manage products
|
||||
|
||||
This section describes how to add client computers into the Volume Activation Management Tool (VAMT). After the computers are added, the products that are installed in the network can be managed.
|
||||
|
||||
## In this Section
|
||||
|
||||
|Article |Description |
|
||||
|-------|------------|
|
||||
|[Add and Remove Computers](add-remove-computers-vamt.md) |Describes how to add client computers to VAMT. |
|
||||
|[Update Product Status](update-product-status-vamt.md) |Describes how to update the status of product license. |
|
||||
|[Remove Products](remove-products-vamt.md) |Describes how to remove a product from the product list. |
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Add and Remove Computers (Windows 10)
|
||||
description: The Discover products function on the Volume Activation Management Tool (VAMT) allows you to search the Active Directory domain or a general LDAP query.
|
||||
title: Add and remove computers
|
||||
description: The discover products function on the Volume Activation Management Tool (VAMT) allows you to search the Active Directory domain or a general LDAP query.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
@ -71,4 +71,6 @@ You can delete a computer by clicking on it in the product list view, and then c
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Add and Manage Products](add-manage-products-vamt.md)
|
||||
[Update product status](update-product-status-vamt.md)
|
||||
|
||||
[Remove products](remove-products-vamt.md)
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Add and Remove a Product Key (Windows 10)
|
||||
title: Add and remove a product key
|
||||
description: Add a product key to the Volume Activation Management Tool (VAMT) database. Also, learn how to remove the key from the database.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
@ -38,4 +38,6 @@ Before you can use a Multiple Activation Key (MAK), retail, or KMS Host key (CSV
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Manage Product Keys](manage-product-keys-vamt.md)
|
||||
[Install a product key](install-product-key-vamt.md)
|
||||
|
||||
[Install a KMS client key](install-kms-client-key-vamt.md)
|
||||
|
||||
@ -1,15 +1,15 @@
|
||||
---
|
||||
title: Appendix Information sent to Microsoft during activation
|
||||
title: Appendix information sent to Microsoft during activation
|
||||
description: Learn about the information sent to Microsoft during activation.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: reference
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
|
||||
@ -24,8 +24,8 @@ appliesto:
|
||||
>
|
||||
> Looking for information on retail activation?
|
||||
>
|
||||
> - [Activate Windows](https://support.microsoft.com/help/12440/).
|
||||
> - [Product activation for Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644).
|
||||
> - [Activate Windows](https://support.microsoft.com/windows/activate-windows-c39005d4-95ee-b91e-b399-2820fda32227).
|
||||
> - [Product activation for Windows](https://support.microsoft.com/windows/product-activation-for-windows-online-support-telephone-numbers-35f6a805-1259-88b4-f5e9-b52cccef91a0).
|
||||
|
||||
When a computer running a currently supported version of Windows is activated, the following information is sent to Microsoft:
|
||||
|
||||
@ -78,8 +78,4 @@ Standard computer information is also sent, but the computer's IP address is onl
|
||||
|
||||
Microsoft uses the information to confirm a properly licensed copy of the software. Microsoft doesn't use the information to contact individual consumers.
|
||||
|
||||
For more information, see [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/p/?LinkId=619879).
|
||||
|
||||
## Related content
|
||||
|
||||
- [Volume Activation for Windows](volume-activation-windows.md).
|
||||
For more information, see [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement).
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Configure Client Computers (Windows 10)
|
||||
title: Configure client computers
|
||||
description: Learn how to configure client computers to enable the Volume Activation Management Tool (VAMT) to function correctly.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
author: frankroj
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
@ -109,4 +109,6 @@ The above configurations will open an additional port through the Windows Firewa
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Install and Configure VAMT](install-configure-vamt.md)
|
||||
[VAMT requirements](vamt-requirements.md)
|
||||
|
||||
[Install VAMT](install-vamt.md)
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Import and export VAMT data
|
||||
description: Learn how to use the VAMT to import product-activation data from a file into SQL Server.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
@ -1,29 +0,0 @@
|
||||
---
|
||||
title: Install and Configure VAMT
|
||||
description: Learn how to install and configure the Volume Activation Management Tool (VAMT), and learn where to find information about the process.
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Install and configure VAMT
|
||||
|
||||
This section describes how to install and configure the Volume Activation Management Tool (VAMT).
|
||||
|
||||
## In this section
|
||||
|
||||
|Article |Description |
|
||||
|-------|------------|
|
||||
|[VAMT Requirements](vamt-requirements.md) |Provides system requirements for installing VAMT on a host computer. |
|
||||
|[Install VAMT](install-vamt.md) |Describes how to get and install VAMT. |
|
||||
|[Configure Client Computers](configure-client-computers-vamt.md) |Describes how to configure client computers in the network to work with VAMT. |
|
||||
|
||||
## Related content
|
||||
|
||||
- [Introduction to VAMT](introduction-vamt.md).
|
||||
@ -1,25 +1,25 @@
|
||||
---
|
||||
title: Install a KMS Client Key (Windows 10)
|
||||
title: Install a KMS client key
|
||||
description: Learn to use the Volume Activation Management Tool (VAMT) to install Generic Volume License Key (GVLK), or KMS client, product keys.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Install a KMS Client Key
|
||||
# Install a KMS client key
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) to install Generic Volume License Key (GVLK), or KMS client, product keys. For example, if you're converting a MAK-activated product to KMS activation.
|
||||
|
||||
> [!NOTE]
|
||||
> By default, volume license editions of Windows Vista, Windows® 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server® 2012, and Microsoft® Office 2010 use KMS for activation. GVLKs are already installed in volume license editions of these products.
|
||||
|
||||
## To install a KMS Client key
|
||||
## To install a KMS client key
|
||||
|
||||
1. Open VAMT.
|
||||
|
||||
@ -47,4 +47,8 @@ You can use the Volume Activation Management Tool (VAMT) to install Generic Volu
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Perform KMS Activation](kms-activation-vamt.md)
|
||||
[Run KMS activation](kms-activation-vamt.md)
|
||||
|
||||
[Add and remove a product key](add-remove-product-key-vamt.md)
|
||||
|
||||
[Install a product key](install-product-key-vamt.md)
|
||||
|
||||
@ -1,22 +1,22 @@
|
||||
---
|
||||
title: Install a Product Key (Windows 10)
|
||||
title: Install a product key
|
||||
description: Learn to use the Volume Activation Management Tool (VAMT) to install retail, Multiple Activation Key (MAK), and KMS Host key (CSVLK).
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Install a Product Key
|
||||
# Install a product key
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) to install retail, Multiple Activation Key (MAK), and KMS Host key (CSVLK).
|
||||
|
||||
## To install a Product key
|
||||
## To install a product key
|
||||
|
||||
1. Open VAMT.
|
||||
|
||||
@ -47,4 +47,6 @@ You can use the Volume Activation Management Tool (VAMT) to install retail, Mult
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Manage Product Keys](manage-product-keys-vamt.md)
|
||||
[Add and remove a product key](add-remove-product-key-vamt.md)
|
||||
|
||||
[Install a KMS client key](install-kms-client-key-vamt.md)
|
||||
|
||||
@ -1,14 +1,14 @@
|
||||
---
|
||||
title: Install VAMT
|
||||
description: Learn how to install Volume Activation Management Tool (VAMT) as part of the Windows Assessment and Deployment Kit (ADK) for Windows.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Introduction to VAMT (Windows 10)
|
||||
title: Introduction to VAMT
|
||||
description: VAMT enables administrators to automate and centrally manage the Windows, Microsoft Office, and select other Microsoft products volume and retail activation process.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: overview
|
||||
---
|
||||
@ -64,4 +64,4 @@ VAMT provides a single, graphical user interface for managing activations, and f
|
||||
|
||||
## Next steps
|
||||
|
||||
[VAMT step-by-step scenarios](vamt-step-by-step.md)
|
||||
[VAMT requirements](vamt-requirements.md)
|
||||
|
||||
@ -1,19 +1,19 @@
|
||||
---
|
||||
title: Perform KMS Activation (Windows 10)
|
||||
description: The Volume Activation Management Tool (VAMT) can be used to perform volume activation using the Key Management Service (KMS).
|
||||
title: Run KMS activation
|
||||
description: The Volume Activation Management Tool (VAMT) can be used to run volume activation using the Key Management Service (KMS).
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Perform KMS activation
|
||||
# Run KMS activation
|
||||
|
||||
The Volume Activation Management Tool (VAMT) can be used to perform volume activation using the Key Management Service (KMS). You can use VAMT to activate Generic Volume Licensing Keys, or KMS client keys, on products accessible to VAMT. GVLKs are the default product keys used by the volume-license editions of Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server® 2012, and Microsoft Office 2010. GVLKs are already installed in volume-license editions of these products.
|
||||
The Volume Activation Management Tool (VAMT) can be used to run volume activation using the Key Management Service (KMS). You can use VAMT to activate Generic Volume Licensing Keys, or KMS client keys, on products accessible to VAMT. GVLKs are the default product keys used by the volume-license editions of Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server® 2012, and Microsoft Office 2010. GVLKs are already installed in volume-license editions of these products.
|
||||
|
||||
## Requirements
|
||||
|
||||
@ -47,7 +47,7 @@ Before configuring KMS activation, ensure that your network and VAMT installatio
|
||||
|
||||
5. Select **Apply**, and then select **OK** to close the **Volume Activation Management Tool Preferences** dialog box.
|
||||
|
||||
6. Select the products to be activated by selecting individual products in the product list view in the center pane. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box.In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
6. Select the products to be activated by selecting individual products in the product list view in the center pane. You can use the **Filter** function to narrow your search for computers by clicking **Filter** in the right-side pane to open the **Filter Products** dialog box. In the **Filter Products** dialog box, you can filter the list by computer name, product name, product key type, license status, or by any combination of these options.
|
||||
|
||||
- To filter the list by computer name, enter a name in the **Computer Name** box.
|
||||
|
||||
@ -61,3 +61,11 @@ Before configuring KMS activation, ensure that your network and VAMT installatio
|
||||
|
||||
10. If you're supplying alternate credentials, at the prompt, type the appropriate user name and password and select **OK**.
|
||||
VAMT displays the **Volume Activation** dialog box until it completes the requested action. When the process is finished, the updated activation status of each product appears in the product list view in the center pane.
|
||||
|
||||
## Related articles
|
||||
|
||||
[Run online activation](online-activation-vamt.md)
|
||||
|
||||
[Run proxy activation](proxy-activation-vamt.md)
|
||||
|
||||
[Run local reactivation](local-reactivation-vamt.md)
|
||||
|
||||
@ -1,17 +1,17 @@
|
||||
---
|
||||
title: Perform Local Reactivation (Windows 10)
|
||||
title: Run local reactivation
|
||||
description: An initially activated a computer using scenarios like MAK, retail, or CSLVK (KMS host), can be reactivated with Volume Activation Management Tool (VAMT).
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Perform local reactivation
|
||||
# Run local reactivation
|
||||
|
||||
If you reinstall Windows® or Microsoft® Office 2010 on a computer that was initially activated using proxy activation (MAK, retail, or CSLVK (KMS host)), and have not made significant changes to the hardware, use this local reactivation procedure to reactivate the program on that computer.
|
||||
Local reactivation relies upon data that was created during the initial proxy activation and stored in the Volume Activation Management Tool (VAMT) database. The database contains the installation ID (IID) and confirmation ID (Pending CID). Local reactivation uses this data to reapply the CID and reactivate those products. Reapplying the same CID conserves the remaining activations on the key.
|
||||
@ -19,7 +19,7 @@ Local reactivation relies upon data that was created during the initial proxy ac
|
||||
> [!NOTE]
|
||||
> During the initial proxy activation, the CID is bound to a digital "fingerprint", which is calculated from values assigned to several different hardware components in the computer. If the computer has had significant hardware changes, this fingerprint will no longer match the CID. In this case, you must obtain a new CID for the computer from Microsoft.
|
||||
|
||||
## To perform a local reactivation
|
||||
## To run a local reactivation
|
||||
|
||||
1. Open VAMT. Make sure that you're connected to the desired database.
|
||||
|
||||
@ -51,4 +51,8 @@ Local reactivation relies upon data that was created during the initial proxy ac
|
||||
|
||||
## Related article
|
||||
|
||||
- [Manage Activations](manage-activations-vamt.md)
|
||||
[Run online activation](online-activation-vamt.md)
|
||||
|
||||
[Run proxy activation](proxy-activation-vamt.md)
|
||||
|
||||
[Run KMS activation](kms-activation-vamt.md)
|
||||
|
||||
@ -1,27 +0,0 @@
|
||||
---
|
||||
title: Manage Activations
|
||||
description: Learn how to manage activations and how to activate a client computer by using various activation methods.
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Manage Activations
|
||||
|
||||
This section describes how to activate a client computer, by using various activation methods.
|
||||
|
||||
## In this Section
|
||||
|
||||
|Article |Description |
|
||||
|-------|------------|
|
||||
|[Perform Online Activation](online-activation-vamt.md) |Describes how to activate a client computer over the Internet. |
|
||||
|[Perform Proxy Activation](proxy-activation-vamt.md) |Describes how to perform volume activation for client products that don't have Internet access. |
|
||||
|[Perform KMS Activation](kms-activation-vamt.md) |Describes how to perform volume activation using the Key Management Service (KMS). |
|
||||
|[Perform Local Reactivation](local-reactivation-vamt.md) |Describes how to reactivate an operating system or Office program that was reinstalled. |
|
||||
|[Activate an Active Directory Forest Online](activate-forest-vamt.md) |Describes how to use Active Directory-Based Activation to activate an Active Directory forest, online. |
|
||||
|[Activate by Proxy an Active Directory Forest](activate-forest-by-proxy-vamt.md) |Describes how to use Active Directory-Based Activation to proxy activate an Active Directory forest that isn't connected to the Internet. |
|
||||
@ -1,24 +0,0 @@
|
||||
---
|
||||
title: Manage Product Keys
|
||||
description: In this article, learn how to add and remove a product key from the Volume Activation Management Tool (VAMT).
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Manage Product Keys
|
||||
|
||||
This section describes how to add and remove a product key from the Volume Activation Management Tool (VAMT). After a product key is added to VAMT, that product key can be installed on a product, or products selected in the VAMT database.
|
||||
|
||||
## In this Section
|
||||
|
||||
|Article |Description |
|
||||
|-------|------------|
|
||||
|[Add and Remove a Product Key](add-remove-product-key-vamt.md) |Describes how to add a product key to the VAMT database. |
|
||||
|[Install a Product Key](install-product-key-vamt.md) |Describes how to install a product key for specific product. |
|
||||
|[Install a KMS Client Key](install-kms-client-key-vamt.md) |Describes how to install a GVLK (KMS client) key. |
|
||||
@ -1,23 +0,0 @@
|
||||
---
|
||||
title: Manage VAMT Data
|
||||
description: Learn how to save, import, export, and merge a Computer Information List (CILX) file using the Volume Activation Management Tool (VAMT).
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Manage VAMT Data
|
||||
|
||||
This section describes how to save, import, export, and merge a Computer Information List (CILX) file using the Volume Activation Management Tool (VAMT).
|
||||
|
||||
## In this Section
|
||||
|
||||
|Article |Description |
|
||||
|-------|------------|
|
||||
|[Import and Export VAMT Data](import-export-vamt-data.md) |Describes how to import and export VAMT data. |
|
||||
|[Use VAMT in Windows PowerShell](use-vamt-in-windows-powershell.md) |Describes how to access Windows PowerShell and how to import the VAMT PowerShell module. |
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Monitor activation
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
description: Understand the most common methods to monitor the success of the activation process for a computer running Windows.
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
ms.date: 03/29/2024
|
||||
appliesto:
|
||||
@ -24,8 +24,8 @@ appliesto:
|
||||
>
|
||||
> Looking for information on retail activation?
|
||||
>
|
||||
> - [Activate Windows](https://support.microsoft.com/help/12440/).
|
||||
> - [Product activation for Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644).
|
||||
> - [Activate Windows](https://support.microsoft.com/windows/activate-windows-c39005d4-95ee-b91e-b399-2820fda32227).
|
||||
> - [Product activation for Windows](https://support.microsoft.com/windows/product-activation-for-windows-online-support-telephone-numbers-35f6a805-1259-88b4-f5e9-b52cccef91a0).
|
||||
|
||||
The success of the activation process for a computer running Windows can be monitored in several ways. The most popular methods include:
|
||||
|
||||
@ -39,10 +39,10 @@ The success of the activation process for a computer running Windows can be moni
|
||||
|
||||
- Microsoft System Center Operations Manager and the KMS Management Pack can provide insight and information to users of System Center Operations Manager.
|
||||
|
||||
- See [Troubleshooting activation error codes](/windows-server/get-started/activation-error-codes) for information about troubleshooting procedures for Multiple Activation Key (MAK) or the Key Management Service (KMS).
|
||||
- See [Troubleshooting activation error codes](/troubleshoot/windows-server/licensing-and-activation/troubleshoot-activation-error-codes) for information about troubleshooting procedures for Multiple Activation Key (MAK) or the Key Management Service (KMS).
|
||||
|
||||
- The Volume Activation Management Tool (VAMT) provides a single site from which to manage and monitor volume activations. This feature is explained in the next section.
|
||||
- The Volume Activation Management Tool (VAMT) provides a single site from which to manage and monitor volume activations. For more information, see [Introduction to VAMT](introduction-vamt.md).
|
||||
|
||||
## Related content
|
||||
|
||||
- [Volume Activation for Windows](volume-activation-windows.md).
|
||||
[Volume activation for Windows](volume-activation-windows.md).
|
||||
|
||||
@ -1,35 +1,35 @@
|
||||
---
|
||||
title: Perform Online Activation (Windows 10)
|
||||
title: Run online activation
|
||||
description: Learn how to use the Volume Activation Management Tool (VAMT) to enable client products to be activated online.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Perform online activation
|
||||
# Run online activation
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) to enable client products to be activated over the Internet. You can install the client products with any kind of product key that is eligible for online activation—Multiple Activation Key (MAK), retail, and Windows Key Management Services (KMS) host key.
|
||||
You can use the Volume Activation Management Tool (VAMT) to enable client products to be activated over the internet. You can install the client products with any kind of product key that is eligible for online activation—Multiple Activation Key (MAK), retail, and Windows Key Management Services (KMS) host key.
|
||||
|
||||
## Requirements
|
||||
|
||||
Before performing online activation, ensure that the network and the VAMT installation meet the following requirements:
|
||||
Before running online activation, ensure that the network and the VAMT installation meet the following requirements:
|
||||
|
||||
- VAMT is installed on a central computer that has network access to all client computers.
|
||||
|
||||
- Both the VAMT host and client computers have Internet access.
|
||||
- Both the VAMT host and client computers have internet access.
|
||||
|
||||
- The products that you want to activate are added to VAMT.
|
||||
|
||||
- VAMT has administrative permissions on all computers that you intend to activate, and that Windows Management Instrumentation (WMI) can be accessed through the Windows firewall. For more information, see [Configure Client Computers](configure-client-computers-vamt.md).
|
||||
- VAMT has administrative permissions on all computers that you intend to activate, and that Windows Management Instrumentation (WMI) can be accessed through the Windows firewall. For more information, see [Configure client computers](configure-client-computers-vamt.md).
|
||||
|
||||
The product keys that are installed on the client products must have a sufficient number of remaining activations. If you're activating a MAK key, you can retrieve the remaining number of activations for that key by selecting the MAK in the product key list in the center pane and then clicking **Refresh product key data online** in the right-side pane. This action retrieves the number of remaining activations for the MAK from Microsoft. This step requires Internet access and that the remaining activation count can only be retrieved for MAKs.
|
||||
The product keys that are installed on the client products must have a sufficient number of remaining activations. If you're activating a MAK key, you can retrieve the remaining number of activations for that key by selecting the MAK in the product key list in the center pane and then clicking **Refresh product key data online** in the right-side pane. This action retrieves the number of remaining activations for the MAK from Microsoft. This step requires internet access and that the remaining activation count can only be retrieved for MAKs.
|
||||
|
||||
## To perform an online activation
|
||||
## To run an online activation
|
||||
|
||||
1. Open VAMT.
|
||||
|
||||
@ -54,11 +54,15 @@ The product keys that are installed on the client products must have a sufficien
|
||||
The same status is shown under the **Status of Last Action** column in the products list view in the center pane.
|
||||
|
||||
> [!NOTE]
|
||||
> Online activation does not enable you to save the Confirmation IDs (CIDs). As a result, you cannot perform local reactivation.
|
||||
> Online activation doesn't enable you to save the Confirmation IDs (CIDs). As a result, you can't run local reactivation.
|
||||
|
||||
> [!NOTE]
|
||||
> You can use online activation to select products that have different key types and activate the products at the same time.
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Manage activations](manage-activations-vamt.md)
|
||||
[Run proxy activation](proxy-activation-vamt.md)
|
||||
|
||||
[Run KMS activation](kms-activation-vamt.md)
|
||||
|
||||
[Run local reactivation](local-reactivation-vamt.md)
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Plan for volume activation
|
||||
description: Product activation is the process of validating software with the manufacturer after it's installed on a specific computer.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
ms.date: 03/29/2024
|
||||
appliesto:
|
||||
@ -24,8 +24,8 @@ appliesto:
|
||||
>
|
||||
> Looking for information on retail activation?
|
||||
>
|
||||
> - [Activate Windows](https://support.microsoft.com/help/12440/).
|
||||
> - [Product activation for Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644).
|
||||
> - [Activate Windows](https://support.microsoft.com/windows/activate-windows-c39005d4-95ee-b91e-b399-2820fda32227).
|
||||
> - [Product activation for Windows](https://support.microsoft.com/windows/product-activation-for-windows-online-support-telephone-numbers-35f6a805-1259-88b4-f5e9-b52cccef91a0).
|
||||
|
||||
*Product activation* is the process of validating software with the manufacturer after it's installed on a specific computer. Activation confirms that the product is genuine and not a fraudulent copy. Activation also confirms that the product key or serial number is valid and isn't compromised or revoked. Activation also establishes a link or relationship between the product key and the particular installation.
|
||||
|
||||
@ -76,7 +76,7 @@ With a retail product, the Volume Activation Management Tool (VAMT), which is di
|
||||
- Telephone activation.
|
||||
- VAMT proxy activation.
|
||||
|
||||
Telephone activation is primarily used in situations where a computer is isolated from all networks. VAMT proxy activation with retail keys is sometimes used when an IT department wants to centralize retail activations. VAMT can also be used when a computer with a retail version of the operating system is isolated from the Internet but connected to the LAN. For volume-licensed products, however, the best method or combination of methods must be determined to use in the environment. For currently supported versions of Windows Pro and Enterprise, one of the following three models can be chosen:
|
||||
Telephone activation is primarily used in situations where a computer is isolated from all networks. VAMT proxy activation with retail keys is sometimes used when an IT department wants to centralize retail activations. VAMT can also be used when a computer with a retail version of the operating system is isolated from the internet but connected to the LAN. For volume-licensed products, however, the best method or combination of methods must be determined to use in the environment. For currently supported versions of Windows Pro and Enterprise, one of the following three models can be chosen:
|
||||
|
||||
- Multiple Activation Keys (MAK).
|
||||
- KMS.
|
||||
@ -97,7 +97,7 @@ To use a MAK, the computers to be activated must have a MAK installed. The MAK i
|
||||
|
||||
In the simplest terms, a MAK acts like a retail key, except that a MAK is valid for activating multiple computers. Each MAK can be used a specific number of times. The VAMT can help with tracking the number of performed activations with each key and how many activations remain.
|
||||
|
||||
Organizations can download MAK and KMS keys from the [Volume Licensing Service Center](https://go.microsoft.com/fwlink/p/?LinkId=618213) website. Each MAK has a preset number of activations, which are based on a percentage of the count of licenses the organization purchases. However, the number of activations that are available can be increased with the MAK by calling Microsoft.
|
||||
Organizations can download MAK and KMS keys from the [Volume Licensing Service Center](https://admin.microsoft.com/adminportal/home#/subscriptions/vlnew) website. Each MAK has a preset number of activations, which are based on a percentage of the count of licenses the organization purchases. However, the number of activations that are available can be increased with the MAK by calling Microsoft.
|
||||
|
||||
### Key Management Service
|
||||
|
||||
@ -121,7 +121,7 @@ A modern business network has many nuances and interconnections. This section ex
|
||||
|
||||
### Core network
|
||||
|
||||
The organization's core network is that part of the network that enjoys stable, high-speed, reliable connectivity to infrastructure servers. In many cases, the core network is also connected to the Internet. However, Internet connectivity isn't a requirement to use the KMS or Active Directory-based activation after the KMS server or ADDS is configured and active. The organization's core network likely consists of many network segments. In many organizations, the core network makes up most of the business network.
|
||||
The organization's core network is that part of the network that enjoys stable, high-speed, reliable connectivity to infrastructure servers. In many cases, the core network is also connected to the internet. However, internet connectivity isn't a requirement to use the KMS or Active Directory-based activation after the KMS server or ADDS is configured and active. The organization's core network likely consists of many network segments. In many organizations, the core network makes up most of the business network.
|
||||
|
||||
In the core network, a centralized KMS solution is recommended. Active Directory-based activation can also be used, but in many organizations, KMS might still be required to computers that aren't joined to the domain. Some administrators prefer to run both solutions to have the most flexibility, while others prefer to choose only a KMS-based solution for simplicity. Active Directory-based activation as the only solution is workable if all of the clients in the organization are running currently supported versions of Windows.
|
||||
|
||||
@ -163,7 +163,7 @@ If the network is fully isolated, MAK-independent activation would be the recomm
|
||||
|
||||
#### Branch offices and distant networks
|
||||
|
||||
From mining operations to ships at sea, organizations often have a few computers that aren't easily connected to the core network or the Internet. Some organizations have network segments at branch offices that are large and well-connected internally, but have a slow or unreliable WAN link to the rest of the organization. There are several options in these situations:
|
||||
From mining operations to ships at sea, organizations often have a few computers that aren't easily connected to the core network or the internet. Some organizations have network segments at branch offices that are large and well-connected internally, but have a slow or unreliable WAN link to the rest of the organization. There are several options in these situations:
|
||||
|
||||
- **Active Directory-based activation**. In any site where the client computers are running currently supported versions of Windows, Active Directory-based activation is supported, and it can be activated by joining the domain.
|
||||
|
||||
@ -183,7 +183,7 @@ Active Directory-based activation can be used on computers when they meet the fo
|
||||
- The computer is running a currently supported version of Windows or Windows Server.
|
||||
- The computer connects to the domain at least once every 180 days, either directly or through a VPN.
|
||||
|
||||
Otherwise for computers that rarely or never connect to the network, MAK independent activation should be used either via the telephone or the Internet.
|
||||
Otherwise for computers that rarely or never connect to the network, MAK independent activation should be used either via the telephone or the internet.
|
||||
|
||||
### Test and development labs
|
||||
|
||||
@ -215,13 +215,13 @@ By evaluating network connectivity and the numbers of computers at each site, th
|
||||
|
||||
When it's know which keys are needed, the keys must be obtained. Generally speaking, volume licensing keys are collected in two ways:
|
||||
|
||||
- Go to the **Product Keys** section of the [Volume Licensing Service Center](https://go.microsoft.com/fwlink/p/?LinkID=618213) for the following agreements: Open, Open Value, Select, Enterprise, and Services Provider License.
|
||||
- Go to the **Product Keys** section of the [Volume Licensing Service Center](https://admin.microsoft.com/adminportal/home#/subscriptions/vlnew) for the following agreements: Open, Open Value, Select, Enterprise, and Services Provider License.
|
||||
|
||||
- Contact the [Microsoft activation center](https://go.microsoft.com/fwlink/p/?LinkId=618264).
|
||||
- Contact the [Microsoft activation center](https://www.microsoft.com/licensing/existing-customer/activation-centers).
|
||||
|
||||
### KMS host keys
|
||||
|
||||
A KMS host needs a key that activates, or authenticates, the KMS host with Microsoft. This key is referred to as the *KMS host key*, but it's formally known as a *Microsoft Customer Specific Volume License Key* (CSVLK). Some documentation and Internet references use the term KMS key, but CSVLK is the proper name for current documentation and management tools.
|
||||
A KMS host needs a key that activates, or authenticates, the KMS host with Microsoft. This key is referred to as the *KMS host key*, but it's formally known as a *Microsoft Customer Specific Volume License Key* (CSVLK). Some documentation and internet references use the term KMS key, but CSVLK is the proper name for current documentation and management tools.
|
||||
|
||||
A KMS host running a currently supported version of Windows Server can activate both Windows Server and Windows client operating systems. A KMS host key is also needed to create the activation objects in ADDS, as described later in this guide. A KMS host key is needed for any KMS that is set up. Additionally, it needs to be determined if Active Directory-based activation will be used.
|
||||
|
||||
@ -274,4 +274,4 @@ The flow of KMS activation is shown in Figure 3, and it follows this sequence:
|
||||
|
||||
## Related content
|
||||
|
||||
- [Volume Activation for Windows](volume-activation-windows.md).
|
||||
- [Volume activation for Windows](volume-activation-windows.md).
|
||||
|
||||
@ -1,30 +1,30 @@
|
||||
---
|
||||
title: Perform Proxy Activation (Windows 10)
|
||||
description: Perform proxy activation by using the Volume Activation Management Tool (VAMT) to activate client computers that don't have Internet access.
|
||||
title: Run proxy activation
|
||||
description: Run proxy activation by using the Volume Activation Management Tool (VAMT) to activate client computers that don't have internet access.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Perform Proxy Activation
|
||||
# Run proxy activation
|
||||
|
||||
You can use the Volume Activation Management Tool (VAMT) to perform activation for client computers that don't have Internet access. The client products can be installed with any type of product key that is eligible for proxy activation: Multiple activation Key (MAK), KMS Host key (CSVLK), or retail key.
|
||||
You can use the Volume Activation Management Tool (VAMT) to run activation for client computers that don't have internet access. The client products can be installed with any type of product key that is eligible for proxy activation: Multiple activation Key (MAK), KMS Host key (CSVLK), or retail key.
|
||||
|
||||
In a typical proxy-activation scenario, the VAMT host computer distributes a MAK to one or more client computers and collects the installation ID (IID) from each computer. The VAMT host computer sends the IIDs to Microsoft on behalf of the client computers and obtains the corresponding Confirmation IDs (CIDs). The VAMT host computer then installs the CIDs on the client computer to complete the activation. Using this activation method, only the VAMT host computer needs Internet access.
|
||||
In a typical proxy-activation scenario, the VAMT host computer distributes a MAK to one or more client computers and collects the installation ID (IID) from each computer. The VAMT host computer sends the IIDs to Microsoft on behalf of the client computers and obtains the corresponding Confirmation IDs (CIDs). The VAMT host computer then installs the CIDs on the client computer to complete the activation. Using this activation method, only the VAMT host computer needs internet access.
|
||||
|
||||
> [!NOTE]
|
||||
> For workgroups that are completely isolated from any larger network, you can still perform MAK, KMS Host key (CSVLK), or retail proxy activation. This requires installing a second instance of VAMT on a computer within the isolated group and using removable media to transfer activation data between that computer and another VAMT host computer that has Internet access. For more information about this scenario, see [Scenario 2: Proxy Activation](scenario-proxy-activation-vamt.md). Similarly, you can proxy activate a KMS Host key (CSVLK) located in an isolated network. You can also proxy activate a KMS Host key (CSVLK) in the core network if you do not want the KMS host computer to connect to Microsoft over the Internet.
|
||||
> For workgroups that are completely isolated from any larger network, you can still run MAK, KMS Host key (CSVLK), or retail proxy activation. This requires installing a second instance of VAMT on a computer within the isolated group and using removable media to transfer activation data between that computer and another VAMT host computer that has internet access. For more information about this scenario, see [Scenario 2: Proxy Activation](scenario-proxy-activation-vamt.md). Similarly, you can proxy activate a KMS Host key (CSVLK) located in an isolated network. You can also proxy activate a KMS Host key (CSVLK) in the core network if you do not want the KMS host computer to connect to Microsoft over the internet.
|
||||
|
||||
## Requirements
|
||||
|
||||
Before performing proxy activation, ensure that your network and the VAMT installation meet the following requirements:
|
||||
Before running proxy activation, ensure that your network and the VAMT installation meet the following requirements:
|
||||
|
||||
- There's an instance of VAMT that is installed on a computer that has Internet access. If you're performing proxy activation for an isolated workgroup, you also need to have VAMT installed on one of the computers in the workgroup.
|
||||
- There's an instance of VAMT that is installed on a computer that has internet access. If you're running proxy activation for an isolated workgroup, you also need to have VAMT installed on one of the computers in the workgroup.
|
||||
|
||||
- The products to be activated have been added to VAMT and are installed with a retail product key, a KMS Host key (CSVLK) or a MAK. If the products haven't been installed with a proper product key, refer to the steps in the [Add and Remove a Product Key](add-remove-product-key-vamt.md) section for instructions on how to install a product key.
|
||||
|
||||
@ -32,9 +32,9 @@ Before performing proxy activation, ensure that your network and the VAMT instal
|
||||
|
||||
- For workgroup computers, a registry key must be created to enable remote administrative actions under User Account Control (UAC). For more information, see [Configure client computers](configure-client-computers-vamt.md).
|
||||
|
||||
The product keys that are installed on the client products must have a sufficient number of remaining activations. If you're activating a MAK key, you can retrieve the remaining number of activations for that key by selecting the MAK in the product key list in the center pane and then clicking **Refresh product key data online** in the right-side pane. This action retrieves the number of remaining activations for the MAK from Microsoft. This step requires Internet access and that the remaining activation count can only be retrieved for MAKs.
|
||||
The product keys that are installed on the client products must have a sufficient number of remaining activations. If you're activating a MAK key, you can retrieve the remaining number of activations for that key by selecting the MAK in the product key list in the center pane and then clicking **Refresh product key data online** in the right-side pane. This action retrieves the number of remaining activations for the MAK from Microsoft. This step requires internet access and that the remaining activation count can only be retrieved for MAKs.
|
||||
|
||||
## To Perform Proxy Activation
|
||||
## To run proxy activation
|
||||
|
||||
1. Open VAMT.
|
||||
|
||||
@ -66,3 +66,11 @@ Before performing proxy activation, ensure that your network and the VAMT instal
|
||||
|
||||
> [!NOTE]
|
||||
You can use proxy activation to select products that have different key types and activate the products at the same time.
|
||||
|
||||
## Related articles
|
||||
|
||||
[Run online activation](online-activation-vamt.md)
|
||||
|
||||
[Run KMS activation](kms-activation-vamt.md)
|
||||
|
||||
[Run local reactivation](local-reactivation-vamt.md)
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Remove Products (Windows 10)
|
||||
title: Remove products
|
||||
description: Learn how you must delete products from the product list view so you can remove products from the Volume Activation Management Tool (VAMT).
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
@ -37,4 +37,6 @@ To remove one or more products from the Volume Activation Management Tool (VAMT)
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Add and Manage Products](add-manage-products-vamt.md)
|
||||
[Add and remove computers](add-remove-computers-vamt.md)
|
||||
|
||||
[Update product status](update-product-status-vamt.md)
|
||||
|
||||
@ -1,19 +1,19 @@
|
||||
---
|
||||
title: Scenario 3 KMS Client Activation (Windows 10)
|
||||
title: Scenario 3 - KMS client activation
|
||||
description: Learn how to use the Volume Activation Management Tool (VAMT) to activate Key Management Service (KMS) client keys or Generic Volume License Keys (GVLKs).
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Scenario 3: KMS client activation
|
||||
|
||||
In this scenario, you use the Volume Activation Management Tool (VAMT) to activate Key Management Service (KMS) client keys or Generic Volume License Keys (GVLKs). This type of activation can be performed on either Core Network or Isolated Lab computers. By default, volume license editions of Windows Vista, Windows® 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server® 2012, and Microsoft® Office 2010 use KMS for activation. GVLKs are already installed in volume license editions of these products. You don't have to enter a key to activate a product as a GVLK, unless you're converting a MAK-activated product to a KMS activation. For more information, see [Install a KMS Client Key](install-kms-client-key-vamt.md).
|
||||
In this scenario, you use the Volume Activation Management Tool (VAMT) to activate Key Management Service (KMS) client keys or Generic Volume License Keys (GVLKs). This type of activation can be performed on either Core Network or Isolated Lab computers. By default, volume license editions of Windows Vista, Windows® 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server® 2012, and Microsoft® Office 2010 use KMS for activation. GVLKs are already installed in volume license editions of these products. You don't have to enter a key to activate a product as a GVLK, unless you're converting a MAK-activated product to a KMS activation. For more information, see [Install a KMS client key](install-kms-client-key-vamt.md).
|
||||
|
||||
The procedure that is described below assumes the following configuration:
|
||||
|
||||
@ -56,4 +56,8 @@ The same status is shown under the **Status of Last Action** column in the produ
|
||||
|
||||
## Related articles
|
||||
|
||||
- [VAMT step-by-step scenarios](vamt-step-by-step.md)
|
||||
[Run KMS activation](kms-activation-vamt.md)
|
||||
|
||||
[Activate using Key Management Service](activate-using-key-management-service-vamt.md)
|
||||
|
||||
[Install a KMS client key](install-kms-client-key-vamt.md)
|
||||
|
||||
@ -1,17 +1,17 @@
|
||||
---
|
||||
title: Scenario 1 Online Activation (Windows 10)
|
||||
title: Scenario 1 - online activation
|
||||
description: Achieve network access by deploying the Volume Activation Management Tool (VAMT) in a Core Network environment.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Scenario 1: Online Activation
|
||||
# Scenario 1: online activation
|
||||
|
||||
In this scenario, the Volume Activation Management Tool (VAMT) is deployed in the Core Network environment. VAMT is installed on a central computer that has network access to all of the client computers. Both the VAMT host and the client computers have Internet access. The following illustration shows a diagram of an online activation scenario for Multiple Activation Keys (MAKs). You can use this scenario for online activation of the following key types:
|
||||
|
||||
@ -36,10 +36,10 @@ The Secure Zone represents higher-security Core Network computers that have addi
|
||||
|
||||
## Step 2: Configure the Windows Management Instrumentation firewall exception on target computers
|
||||
|
||||
- Ensure that the Windows Management Instrumentation (WMI) firewall exception has been enabled for all target computers. For more information, see [Configure Client Computers](configure-client-computers-vamt.md).
|
||||
- Ensure that the Windows Management Instrumentation (WMI) firewall exception has been enabled for all target computers. For more information, see [Configure client computers](configure-client-computers-vamt.md).
|
||||
|
||||
> [!NOTE]
|
||||
> To retrieve product license status, VAMT must have administrative permissions on the remote computers and WMI must be available through the Windows Firewall. In addition, for workgroup computers, a registry key must be created to enable remote administrative actions under User Account Control (UAC). For more information, see [Configure Client Computers](configure-client-computers-vamt.md).
|
||||
> To retrieve product license status, VAMT must have administrative permissions on the remote computers and WMI must be available through the Windows Firewall. In addition, for workgroup computers, a registry key must be created to enable remote administrative actions under User Account Control (UAC). For more information, see [Configure client computers](configure-client-computers-vamt.md).
|
||||
|
||||
## Step 3: Connect to a VAMT database
|
||||
|
||||
@ -47,7 +47,7 @@ The Secure Zone represents higher-security Core Network computers that have addi
|
||||
|
||||
2. Select **Connect**.
|
||||
|
||||
3. If you're already connected to a database, VAMT displays an inventory of the products and product keys in the center pane, and a license overview of the computers in the database. If you need to connect to a different database, select **Successfully connected to Server** to open **the Database Connection Settings** dialog box. For more information about how to create VAMT databases and adding VAMT data, see [Manage VAMT Data](manage-vamt-data.md)
|
||||
3. If you're already connected to a database, VAMT displays an inventory of the products and product keys in the center pane, and a license overview of the computers in the database. If you need to connect to a different database, select **Successfully connected to Server** to open **the Database Connection Settings** dialog box. For more information about how to create VAMT databases and adding VAMT data, see [Import and export VAMT data](import-export-vamt-data.md).
|
||||
|
||||
## Step 4: Discover products
|
||||
|
||||
@ -57,11 +57,11 @@ The Secure Zone represents higher-security Core Network computers that have addi
|
||||
|
||||
3. In the **Discover Products** dialog box, select **Search for computers in the Active Directory** to display the search options, and then select the search options that you want to use. You can search for computers in an Active Directory domain, by individual computer name or IP address, in a workgroup, or by a general Lightweight Directory Access Protocol (LDAP) query:
|
||||
|
||||
- To search for computers in an Active Directory domain, select **Search for computers in the Active Directory**. Then under **Domain Filter Criteria**, in the list of domain names select the name of the domain that you want to search. You can narrow the search further by typing a name in the **Filter by computer name** field to search for specific computers in the domain. This filter supports the asterisk (\*) wildcard. For example, typing "a\*" will display only those computer names that start with the letter "a".
|
||||
- To search for computers in an Active Directory domain, select **Search for computers in the Active Directory**. Then under **Domain Filter Criteria**, in the list of domain names select the name of the domain that you want to search. You can narrow the search further by typing a name in the **Filter by computer name** field to search for specific computers in the domain. This filter supports the asterisk (`*`) wildcard. For example, typing `a*` will display only those computer names that start with the letter "a".
|
||||
|
||||
- To search by individual computer name or IP address, select **Manually enter name or IP address**. Then enter the full name or IP address in the **One or more computer names or IP addresses separated by commas** text box. Separate multiple entries with a comma. VAMT supports both IPv4 and IPV6 addressing.
|
||||
|
||||
- To search for computers in a workgroup, select **Search for computers in the workgroup**. Then under **Workgroup Filter Criteria**, in the list of workgroup names, select the name of the workgroup that you want to search. You can narrow the search further by typing a name in the **Filter by computer name** field to search for a specific computer in the workgroup. This filter supports the asterisk (\*) wildcard. For example, typing "a\*" will display only computer names that start with the letter "a".
|
||||
- To search for computers in a workgroup, select **Search for computers in the workgroup**. Then under **Workgroup Filter Criteria**, in the list of workgroup names, select the name of the workgroup that you want to search. You can narrow the search further by typing a name in the **Filter by computer name** field to search for a specific computer in the workgroup. This filter supports the asterisk (`*`) wildcard. For example, typing `a*` will display only computer names that start with the letter "a".
|
||||
|
||||
- To search for computers by using a general LDAP query, select **Search with LDAP query** and enter your query in the text box that appears. VAMT will validate the LDAP query syntax, but will otherwise run the query without additional checks.
|
||||
|
||||
@ -156,4 +156,4 @@ To collect the status from select computers in the database, you can select comp
|
||||
|
||||
## Related articles
|
||||
|
||||
- [VAMT Step-by-Step Scenarios](vamt-step-by-step.md)
|
||||
[Run online activation](online-activation-vamt.md)
|
||||
|
||||
@ -1,34 +1,34 @@
|
||||
---
|
||||
title: Scenario 2 Proxy Activation (Windows 10)
|
||||
title: Scenario 2 - proxy activation
|
||||
description: Use the Volume Activation Management Tool (VAMT) to activate products that are installed on workgroup computers in an isolated lab environment.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Scenario 2: Proxy Activation
|
||||
# Scenario 2: proxy activation
|
||||
|
||||
In this scenario, the Volume Activation Management Tool (VAMT) is used to activate products that are installed on workgroup computers in an isolated lab environment. For workgroups that are isolated from the larger network, you can perform proxy activation of Multiple Activation Keys (MAKs), KMS Host keys (CSVLKs), Generic Volume License Keys (GVLKs) (or KMS client keys), or retail keys. Proxy activation is performed by installing a second instance of VAMT on a computer in the isolated workgroup. You can then use removable media to transfer VAMT Computer Information Lists (CILXs) between the instance of VAMT in the isolated workgroup and another VAMT host that has Internet access. The following diagram shows a Multiple Activation Key (MAK) proxy activation scenario:
|
||||
In this scenario, the Volume Activation Management Tool (VAMT) is used to activate products that are installed on workgroup computers in an isolated lab environment. For workgroups that are isolated from the larger network, you can perform proxy activation of Multiple Activation Keys (MAKs), KMS Host keys (CSVLKs), Generic Volume License Keys (GVLKs) (or KMS client keys), or retail keys. Proxy activation is performed by installing a second instance of VAMT on a computer in the isolated workgroup. You can then use removable media to transfer VAMT Computer Information Lists (CILXs) between the instance of VAMT in the isolated workgroup and another VAMT host that has internet access. The following diagram shows a Multiple Activation Key (MAK) proxy activation scenario:
|
||||
|
||||
|
||||
|
||||
## Step 1: Install VAMT on a Workgroup Computer in the Isolated Lab
|
||||
## Step 1: Install VAMT on a workgroup computer in the isolated lab
|
||||
|
||||
1. Install VAMT on a host computer in the isolated lab workgroup. This computer can be running Windows 7, Windows 8, Windows 10, Windows Server 2008 R2, or Windows Server® 2012.
|
||||
|
||||
2. Select the VAMT icon in the **Start** menu to open VAMT.
|
||||
|
||||
## Step 2: Configure the Windows Management Instrumentation Firewall Exception on target computers
|
||||
## Step 2: Configure the Windows Management Instrumentation firewall exception on target computers
|
||||
|
||||
- Ensure that the Windows Management Instrumentation (WMI) firewall exception has been enabled for all target computers. For more information, see [Configure Client Computers](configure-client-computers-vamt.md).
|
||||
- Ensure that the Windows Management Instrumentation (WMI) firewall exception has been enabled for all target computers. For more information, see [Configure client computers](configure-client-computers-vamt.md).
|
||||
|
||||
> [!NOTE]
|
||||
> To retrieve the license status on the selected computers, VAMT must have administrative permissions on the remote computers and WMI must be accessible through the Windows Firewall. In addition, for workgroup computers, a registry key must be created to enable remote administrative actions under User Account Control (UAC). For more information, see [Configure Client Computers](configure-client-computers-vamt.md).
|
||||
> To retrieve the license status on the selected computers, VAMT must have administrative permissions on the remote computers and WMI must be accessible through the Windows Firewall. In addition, for workgroup computers, a registry key must be created to enable remote administrative actions under User Account Control (UAC). For more information, see [Configure client computers](configure-client-computers-vamt.md).
|
||||
|
||||
## Step 3: Connect to a VAMT database
|
||||
|
||||
@ -36,7 +36,7 @@ In this scenario, the Volume Activation Management Tool (VAMT) is used to activa
|
||||
|
||||
2. Select **Connect**.
|
||||
|
||||
3. If you're already connected to a database, in the center pane VAMT displays an inventory of the products and product keys, and a license overview of the computers in the database. If you need to connect to a different database, select **Successfully connected to the Server** to open the **Database Connection Settings** dialog box. For more information about how to create VAMT databases and adding VAMT data, see [Manage VAMT Data.](manage-vamt-data.md)
|
||||
3. If you're already connected to a database, in the center pane VAMT displays an inventory of the products and product keys, and a license overview of the computers in the database. If you need to connect to a different database, select **Successfully connected to the Server** to open the **Database Connection Settings** dialog box. For more information about how to create VAMT databases and adding VAMT data, see [Import and export Volume Activation Management Tool data](import-export-vamt-data.md).
|
||||
|
||||
## Step 4: Discover products
|
||||
|
||||
@ -46,7 +46,7 @@ In this scenario, the Volume Activation Management Tool (VAMT) is used to activa
|
||||
|
||||
3. In the **Discover Products** dialog box, select **Search for computers in the Active Directory** to display the search options, and then select the search options that you want to use. You can search for computers in an Active Directory domain, by individual computer name or IP address, in a workgroup, or by a general LDAP query:
|
||||
|
||||
- To search for computers in an Active Directory domain, select **Search for computers in the Active Directory**. Then under **Domain Filter Criteria**, in the list of domain names, select the name of the domain that you want to search. You can narrow the search further by typing a name in the **Filter by computer name** field to search for specific computers in the domain. This filter supports the asterisk (\*) wildcard. For example, typing "a\*" will display only computer names that start with the letter "a".
|
||||
- To search for computers in an Active Directory domain, select **Search for computers in the Active Directory**. Then under **Domain Filter Criteria**, in the list of domain names, select the name of the domain that you want to search. You can narrow the search further by typing a name in the **Filter by computer name** field to search for specific computers in the domain. This filter supports the asterisk (`*`) wildcard. For example, typing `a*` will display only computer names that start with the letter "a".
|
||||
|
||||
- To search by individual computer name or IP address, select **Manually enter name or IP address**. Then enter the full name or IP address in the **One or more computer names or IP addresses separated by commas** text box. Separate multiple entries with a comma. Both IPv4 and IPv6addressing are supported.
|
||||
|
||||
@ -94,7 +94,7 @@ To collect the status from select computers in the database, you can select comp
|
||||
> [!NOTE]
|
||||
> If a computer has more than one supported product installed, VAMT adds an entry for each product. The entry appears under the appropriate product heading.
|
||||
|
||||
## Step 7: Add Product Keys
|
||||
## Step 7: Add product keys
|
||||
|
||||
1. Select the **Product Keys** node in the left-side pane, and then select **Add Product Keys** in the right-side pane to open the **Add Product Keys** dialog box.
|
||||
|
||||
@ -106,7 +106,7 @@ To collect the status from select computers in the database, you can select comp
|
||||
|
||||
The keys that you have added appear in the **Product Keys** list view in the center pane.
|
||||
|
||||
## Step 8: Install the Product Keys on the Isolated Lab Computers
|
||||
## Step 8: Install the product keys on the isolated lab computers
|
||||
|
||||
1. In the left-side pane, in the **Products** node select the product that you want to install keys onto.
|
||||
|
||||
@ -130,7 +130,7 @@ To collect the status from select computers in the database, you can select comp
|
||||
|
||||
## Step 9: Export VAMT data to a `.cilx` file
|
||||
|
||||
In this step, you export VAMT from the workgroup's host computer and save it in a `.cilx` file. Then you copy the `.cilx` file to removable media so that you can take it to a VAMT host computer that is connected to the Internet. In MAK proxy activation, it's critical to retain this file, because VAMT uses it to apply the Confirmation IDs (CIDs) to the proper products.
|
||||
In this step, you export VAMT from the workgroup's host computer and save it in a `.cilx` file. Then you copy the `.cilx` file to removable media so that you can take it to a VAMT host computer that is connected to the internet. In MAK proxy activation, it's critical to retain this file, because VAMT uses it to apply the Confirmation IDs (CIDs) to the proper products.
|
||||
|
||||
1. Select the individual products that successfully received a product key in Step 8. If needed, sort and filter the list to find the products.
|
||||
|
||||
@ -157,7 +157,7 @@ In this step, you export VAMT from the workgroup's host computer and save it in
|
||||
|
||||
## Step 10: Acquire confirmation IDs from Microsoft on the internet connected host computer
|
||||
|
||||
1. Insert the removable media into the VAMT host that has Internet access.
|
||||
1. Insert the removable media into the VAMT host that has internet access.
|
||||
|
||||
2. Open VAMT. Make sure you are on the root node, and that the **Volume Activation Management Tool** view is displayed in the center pane.
|
||||
|
||||
@ -167,9 +167,9 @@ In this step, you export VAMT from the workgroup's host computer and save it in
|
||||
|
||||
5. When the CID collection process is complete, VAMT displays a **Volume Activation Management Tool** message that shows the number of confirmation IDs that were successfully acquired, and the name of the file where the IDs were saved. Select **OK** to close the message.
|
||||
|
||||
## Step 11: Import the `.cilx` file onto the VAMT host within the Isolated lab workgroup
|
||||
## Step 11: Import the `.cilx` file onto the VAMT host within the isolated lab workgroup
|
||||
|
||||
1. Remove the storage device that contains the `.cilx` file from the Internet-connected VAMT host computer and insert it into the VAMT host computer in the isolated lab.
|
||||
1. Remove the storage device that contains the `.cilx` file from the internet-connected VAMT host computer and insert it into the VAMT host computer in the isolated lab.
|
||||
|
||||
2. Open VAMT and verify that you're connected to the database that contains the computer with the product keys that you're activating.
|
||||
|
||||
@ -181,7 +181,7 @@ In this step, you export VAMT from the workgroup's host computer and save it in
|
||||
|
||||
6. VAMT displays a progress message while the data is being imported. Select **OK** when a message appears and confirms that the data has been successfully imported.
|
||||
|
||||
## Step 12: Apply the CIDs and Activate the Isolated Lab Computers
|
||||
## Step 12: Apply the CIDs and activate the isolated lab computers
|
||||
|
||||
1. Select the products to which you want to apply CIDs. If needed, sort and filter the list to find the products.
|
||||
|
||||
@ -190,7 +190,7 @@ In this step, you export VAMT from the workgroup's host computer and save it in
|
||||
VAMT displays the **Applying Confirmation Id** dialog box while it installs the CIDs on the selected products. When VAMT finishes installing the CIDs, the status appears in the **Action Status** column of the dialog box. Select **Close** to close the dialog box. You can also select the **Automatically close when done** check box when the dialog box appears.
|
||||
The same status appears under the **Status of Last Action** column in the product list view in the center pane.
|
||||
|
||||
## Step 13: (Optional) Reactivating Reimaged Computers in the Isolated Lab
|
||||
## Step 13: (Optional) Reactivating reimaged computers in the isolated lab
|
||||
|
||||
If you have captured new images of the computers in the isolated lab, but the underlying hardware of those computers hasn't changed, VAMT can reactivate those computers using the CIDs that are stored in the database.
|
||||
|
||||
@ -213,4 +213,4 @@ If you have captured new images of the computers in the isolated lab, but the un
|
||||
|
||||
## Related articles
|
||||
|
||||
- [VAMT Step-by-Step Scenarios](vamt-step-by-step.md)
|
||||
[Run proxy activation](proxy-activation-vamt.md)
|
||||
|
||||
@ -1,20 +1,20 @@
|
||||
---
|
||||
title: Update Product Status
|
||||
title: Update product status
|
||||
description: Learn how to use the Update license status function to add the products that are installed on the computers.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Update product status
|
||||
|
||||
After computers are added to the Volume Activation Management Tool (VAMT) database, the **Update license status** function needs to be used to add the products that are installed on the computers. The **Update license status** can also be used at any time to retrieve the most current license status for any products in the VAMT database.
|
||||
To retrieve license status, VAMT must have administrative permissions on all selected computers and Windows Management Instrumentation (WMI) must be accessible through the Windows Firewall. In addition, for workgroup computers, a registry key must be created to enable remote administrative actions under User Account Control (UAC). For more information, see [Configure Client Computers](configure-client-computers-vamt.md).
|
||||
To retrieve license status, VAMT must have administrative permissions on all selected computers and Windows Management Instrumentation (WMI) must be accessible through the Windows Firewall. In addition, for workgroup computers, a registry key must be created to enable remote administrative actions under User Account Control (UAC). For more information, see [Configure client computers](configure-client-computers-vamt.md).
|
||||
|
||||
> [!NOTE]
|
||||
> The license-status query requires a valid computer name for each system queried. If the VAMT database contains computers that were added without Personally Identifiable Information, computer names will not be available for those computers, and the status for these computers will not be updated.
|
||||
@ -37,4 +37,6 @@ To retrieve license status, VAMT must have administrative permissions on all sel
|
||||
|
||||
## Related content
|
||||
|
||||
- [Add and Manage Products](add-manage-products-vamt.md).
|
||||
[Add and remove computers](add-remove-computers-vamt.md)
|
||||
|
||||
[Remove products](remove-products-vamt.md)
|
||||
|
||||
@ -1,14 +1,14 @@
|
||||
---
|
||||
title: Use the Volume Activation Management Tool
|
||||
description: The Volume Activation Management Tool (VAMT) provides several useful features, including the ability to track and monitor several types of product keys.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
@ -24,8 +24,8 @@ appliesto:
|
||||
>
|
||||
> Looking for information on retail activation?
|
||||
>
|
||||
> - [Activate Windows](https://support.microsoft.com/help/12440/).
|
||||
> - [Product activation for Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644).
|
||||
> - [Activate Windows](https://support.microsoft.com/windows/activate-windows-c39005d4-95ee-b91e-b399-2820fda32227).
|
||||
> - [Product activation for Windows](https://support.microsoft.com/windows/product-activation-for-windows-online-support-telephone-numbers-35f6a805-1259-88b4-f5e9-b52cccef91a0).
|
||||
|
||||
The Volume Activation Management Tool (VAMT) provides several useful features, including the ability to perform VAMT proxy activation and to track and monitor several types of product keys.
|
||||
|
||||
@ -35,7 +35,7 @@ For currently supported versions of Windows Server, VAMT can be installed direct
|
||||
|
||||
For currently supported versions of Windows client, VAMT can be installed as part of the Windows Assessment and Deployment Kit (Windows ADK). The Windows ADK is a free download. For more information, including links to download the Windows ADK, see [Download and install the Windows ADK](/windows-hardware/get-started/adk-install).
|
||||
|
||||
## Activating with the Volume Activation Management Tool
|
||||
## Activate with VAMT
|
||||
|
||||
VAMT can be used to complete the activation process in products by using MAK and retail keys. Computers can be activated either individually or in groups. The VAMT enables two activation scenarios:
|
||||
|
||||
@ -45,7 +45,7 @@ VAMT can be used to complete the activation process in products by using MAK and
|
||||
|
||||
When this method is used, only the VAMT host computer requires Internet access. Proxy activation by using the VAMT is beneficial for isolated network segments and for cases where the organization has a mix of retail, MAK, and KMS-based activations.
|
||||
|
||||
## Tracking products and computers with the Volume Activation Management Tool
|
||||
## Track products and computers
|
||||
|
||||
The VAMT provides an overview of the activation and licensing status of computers across an organization's network, as shown in Figure 18. Several prebuilt reports are also available to help proactively manage licensing.
|
||||
|
||||
@ -53,7 +53,7 @@ The VAMT provides an overview of the activation and licensing status of computer
|
||||
|
||||
**Figure 18**. The VAMT showing the licensing status of multiple computers
|
||||
|
||||
## Tracking key usage with the Volume Activation Management Tool
|
||||
## Track key usage
|
||||
|
||||
The VAMT makes it easier to track the various keys that are issued to an organization. Each key can be entered into VAMT, and then the VAMT can use those keys for online or proxy activation of clients. The tool can also describe what type of key it's and to which product group it belongs. The VAMT is the most convenient way to quickly determine how many activations remain on a MAK. Figure 19 shows an example of key types and usage.
|
||||
|
||||
@ -61,7 +61,7 @@ The VAMT makes it easier to track the various keys that are issued to an organiz
|
||||
|
||||
**Figure 19**. The VAMT showing key types and usage
|
||||
|
||||
## Other Volume Activation Management Tool features
|
||||
## Other features
|
||||
|
||||
The VAMT stores information in a Microsoft SQL Server database for performance and flexibility, and it provides a single graphical user interface for managing activations and performing other activation-related tasks, such as:
|
||||
|
||||
@ -74,7 +74,6 @@ The VAMT stores information in a Microsoft SQL Server database for performance a
|
||||
For more information, see:
|
||||
|
||||
- [Volume Activation Management Tool (VAMT) Overview](./volume-activation-management-tool.md).
|
||||
- [VAMT Step-by-Step Scenarios](./vamt-step-by-step.md).
|
||||
|
||||
## Related content
|
||||
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Use VAMT in Windows PowerShell (Windows 10)
|
||||
title: Use VAMT in Windows PowerShell
|
||||
description: Learn how to use Volume Activation Management Tool (VAMT) PowerShell cmdlets to perform the same functions as the Vamt.exe command-line tool.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
@ -19,11 +19,11 @@ The Volume Activation Management Tool (VAMT) PowerShell cmdlets can be used to p
|
||||
|
||||
### Install PowerShell 3.0
|
||||
|
||||
VAMT PowerShell cmdlets require Windows PowerShell, which is included in Windows 10, Windows 8 and Windows Server® 2012. You can download PowerShell for Windows 7 or other operating systems from the [Microsoft Download Center](/powershell/scripting/install/installing-powershell).
|
||||
VAMT PowerShell cmdlets require Windows PowerShell, which is included in Windows 10 and later. To download the latest version of PowerShell, see [Installing PowerShell on Windows](/powershell/scripting/install/installing-powershell).
|
||||
|
||||
### Install the Windows Assessment and Deployment Kit**
|
||||
### Install the Windows Assessment and Deployment Kit
|
||||
|
||||
In addition to PowerShell, you must import the VAMT PowerShell module. The module is included in the VAMT 3.0 folder after you install the Windows Assessment and Deployment Kit (Windows ADK).
|
||||
In addition to PowerShell, you must import the VAMT PowerShell module. The module is included in the VAMT 3.0 folder after you install the [Windows Assessment and Deployment Kit (Windows ADK)](/windows-hardware/get-started/adk-install).
|
||||
|
||||
### Prepare the VAMT PowerShell environment
|
||||
|
||||
@ -34,12 +34,8 @@ To open PowerShell with administrative credentials, select **Start** and enter `
|
||||
|
||||
The x86 versions of Windows PowerShell are available in the following directories:
|
||||
|
||||
- PowerShell:
|
||||
|
||||
`C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe`
|
||||
- PowerShell ISE:
|
||||
|
||||
`C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell_ise.exe`
|
||||
- PowerShell: `C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe`
|
||||
- PowerShell ISE: `C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell_ise.exe`
|
||||
|
||||
For all supported operating systems, you can use the VAMT PowerShell module included with the Windows ADK. By default, the module is installed with the Windows ADK in the VAMT folder. Change directories to the directory where VAMT is located. For example, if the Windows ADK is installed in the default location of `C:\Program Files(x86)\Windows Kits\10`, enter:
|
||||
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: VAMT known issues (Windows 10)
|
||||
title: VAMT known issues
|
||||
description: Find out the current known issues with the Volume Activation Management Tool (VAMT), versions 3.0. and 3.1.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 11/07/2022
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: VAMT Requirements
|
||||
description: In this article, learn about the product key and system requirements for Volume Activation Management Tool (VAMT).
|
||||
title: VAMT requirements
|
||||
description: Learn about the product key and system requirements for Volume Activation Management Tool (VAMT).
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
@ -21,7 +21,7 @@ The Volume Activation Management Tool (VAMT) can be used to perform activations
|
||||
|
||||
|Product key type |Where to obtain |
|
||||
|-----------------|----------------|
|
||||
|<ul><li>Multiple Activation Key (MAK)</li><li>Key Management Service (KMS) host key (CSVLK)</li><li>KMS client setup keys (GVLK)</li></ul> |Volume licensing keys can only be obtained with a signed contract from Microsoft. For more info, see the [Microsoft Volume Licensing portal](https://go.microsoft.com/fwlink/p/?LinkId=227282). |
|
||||
|<ul><li>Multiple Activation Key (MAK)</li><li>Key Management Service (KMS) host key (CSVLK)</li><li>KMS client setup keys (GVLK)</li></ul> |Volume licensing keys can only be obtained with a signed contract from Microsoft. For more information, see the [Microsoft Volume Licensing portal](https://admin.microsoft.com/adminportal/home#/subscriptions/vlnew). |
|
||||
|Retail product keys |Obtained at time of product purchase. |
|
||||
|
||||
## System requirements
|
||||
@ -41,4 +41,6 @@ The following table lists the system requirements for the VAMT host computer.
|
||||
|
||||
## Related content
|
||||
|
||||
- [Install and configure VAMT](install-configure-vamt.md).
|
||||
[Install VAMT](install-vamt.md)
|
||||
|
||||
[Configure client computers](configure-client-computers-vamt.md)
|
||||
|
||||
@ -1,28 +0,0 @@
|
||||
---
|
||||
title: VAMT Step-by-Step Scenarios
|
||||
description: Learn step-by-step instructions on implementing the Volume Activation Management Tool (VAMT) in typical environments.
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.subservice: itpro-fundamentals
|
||||
---
|
||||
|
||||
# VAMT step-by-step scenarios
|
||||
|
||||
This section provides instructions on how to implement the Volume Activation Management Tool (VAMT) in typical environments. VAMT supports many common scenarios. To get started, some of the most common scenarios are described here.
|
||||
|
||||
## In this section
|
||||
|
||||
|Article |Description |
|
||||
|-------|------------|
|
||||
|[Scenario 1: Online Activation](scenario-online-activation-vamt.md) |Describes how to distribute Multiple Activation Keys (MAKs) to products installed on one or more connected computers within a network. Additionally, it also describes how to instruct these products to contact Microsoft over the Internet for activation. |
|
||||
|[Scenario 2: Proxy Activation](scenario-proxy-activation-vamt.md) |Describes how to use two VAMT host computers—the first one with Internet access and a second computer within an isolated workgroup—as proxies to perform MAK volume activation for workgroup computers that don't have Internet access. |
|
||||
|[Scenario 3: Key Management Service (KMS) Client Activation](scenario-kms-activation-vamt.md) |Describes how to use VAMT to configure client products for Key Management Service (KMS) activation. By default, volume license editions of currently supported versions of Windows and Microsoft Office use KMS for activation. |
|
||||
|
||||
## Related content
|
||||
|
||||
- [Introduction to VAMT](introduction-vamt.md).
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: VAMT technical reference
|
||||
description: The Volume Activation Management Tool (VAMT) enables network administrators to automate and centrally manage volume activation and retail activation.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
author: frankroj
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: overview
|
||||
---
|
||||
@ -21,16 +21,6 @@ The Volume Activation Management Tool (VAMT) allows automation and central manag
|
||||
|
||||
VAMT is only available in an EN-US (x86) package.
|
||||
|
||||
## In this section
|
||||
## Next steps
|
||||
|
||||
|Article |Description |
|
||||
|------|------------|
|
||||
|[Introduction to VAMT](introduction-vamt.md) |Provides a description of VAMT and common usages. |
|
||||
|[Active Directory-based activation overview](active-directory-based-activation-overview.md) |Describes Active Directory-based activation scenarios. |
|
||||
|[Install and configure VAMT](install-configure-vamt.md) |Describes how to install VAMT and use it to configure client computers in the network. |
|
||||
|[Add and manage products](add-manage-products-vamt.md) |Describes how to add client computers into VAMT. |
|
||||
|[Manage product keys](manage-product-keys-vamt.md) |Describes how to add and remove a product key from VAMT. |
|
||||
|[Manage activations](manage-activations-vamt.md) |Describes how to activate a client computer by using various activation methods. |
|
||||
|[Manage VAMT data](manage-vamt-data.md) |Describes how to save, import, export, and merge a Computer Information List (CILX) file using VAMT. |
|
||||
|[VAMT step-by-step scenarios](vamt-step-by-step.md) |Provides step-by-step instructions for using VAMT in typical environments. |
|
||||
|[VAMT known issues](vamt-known-issues.md) |Lists known issues in VAMT. |
|
||||
[Introduction to VAMT](introduction-vamt.md)
|
||||
|
||||
@ -1,14 +1,14 @@
|
||||
---
|
||||
title: Volume Activation for Windows
|
||||
title: Volume activation for Windows
|
||||
description: Learn how to use volume activation to deploy & activate Windows.
|
||||
ms.author: kaushika
|
||||
author: kaushika-msft
|
||||
manager: cshepard
|
||||
ms.reviewer: nganguly
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
author: frankroj
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 03/29/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: overview
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
@ -18,7 +18,7 @@ appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/windows-server-release-info" target="_blank">Windows Server 2016</a>
|
||||
---
|
||||
|
||||
# Volume Activation for Windows
|
||||
# Volume activation for Windows
|
||||
|
||||
> [!TIP]
|
||||
>
|
||||
@ -28,8 +28,8 @@ appliesto:
|
||||
>
|
||||
> Looking for information on retail activation?
|
||||
>
|
||||
> - [Activate Windows](https://support.microsoft.com/help/12440/).
|
||||
> - [Product activation for Windows](https://go.microsoft.com/fwlink/p/?LinkId=618644).
|
||||
> - [Activate Windows](https://support.microsoft.com/windows/activate-windows-c39005d4-95ee-b91e-b399-2820fda32227).
|
||||
> - [Product activation for Windows](https://support.microsoft.com/windows/product-activation-for-windows-online-support-telephone-numbers-35f6a805-1259-88b4-f5e9-b52cccef91a0).
|
||||
|
||||
This guide is designed to help organizations that are planning to use volume activation to deploy and activate Windows.
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ author: frankroj
|
||||
ms.author: frankroj
|
||||
manager: aaroncz
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/25/2024
|
||||
ms.date: 07/19/2024
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
@ -21,48 +21,56 @@ appliesto:
|
||||
|
||||
The operating system deployment functionality of [Windows Deployment Services](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831764(v=ws.11)) (WDS) is being partially deprecated. Starting with Windows 11, workflows that rely on **boot.wim** from installation media or on running Windows Setup in WDS mode is no longer supported.
|
||||
|
||||
When you PXE-boot from a WDS server that uses the **boot.wim** file from installation media as its boot image, Windows Setup automatically launches in WDS mode. This workflow is deprecated for Windows 11 and newer boot images. The following deprecation message is displayed:
|
||||
When PXE booting from a WDS server that uses the **boot.wim** file from installation media as its boot image, Windows Setup automatically launches in WDS mode. This workflow is deprecated for Windows 11 and newer boot images. The following deprecation message is displayed:
|
||||
|
||||
> Windows Setup
|
||||
>
|
||||
> Windows Deployment Services client functionality is being partly deprecated. Please visit https://aka.ms/WDSSupport for more details on what is deprecated and what will continue to be supported.
|
||||
> Windows Deployment Services client functionality is being partly deprecated. Please visit https://aka.ms/WDSSupport for more details on what is deprecated and what is still supported.
|
||||
|
||||
## Deployment scenarios affected
|
||||
|
||||
The following table provides support details for specific deployment scenarios. Boot.wim is the `boot.wim` file obtained from the Windows source files for each specified version of Windows.
|
||||
|
||||
|Windows Version being deployed |Boot.wim from Windows 10|Boot.wim from Windows Server 2016|Boot.wim from Windows Server 2019|Boot.wim from Windows Server 2022|Boot.wim from Windows 11|
|
||||
|--- |--- |--- |--- |--- |--- |
|
||||
|**Windows 11**|Not supported, blocked.|Not supported, blocked.|Not supported, blocked.|Not supported, blocked.|Not supported, blocked.|
|
||||
|**Windows 10**|Supported, using a boot image from matching or newer version.|Supported, using a boot image from Windows 10, version 1607 or later.|Supported, using a boot image from Windows 10, version 1809 or later.|Not supported.|Not supported.|
|
||||
|**Windows Server 2022**|Deprecated, with a warning message.|Deprecated, with a warning message.|Deprecated, with a warning message.|Deprecated, with a warning message.|Not supported.|
|
||||
|**Windows Server 2019**|Supported, using a boot image from Windows 10, version 1809 or later.|Supported.|Supported.|Not supported.|Not supported.|
|
||||
|**Windows Server 2016**|Supported, using a boot image from Windows 10, version 1607 or later.|Supported.|Not supported.|Not supported.|Not supported.|
|
||||
|
||||
## Reason for the change
|
||||
|
||||
Alternatives to WDS, such as [Microsoft Configuration Manager](/mem/configmgr/) and [Microsoft Deployment Toolkit](/mem/configmgr/mdt/) (MDT) provide a better, more flexible, and feature-rich experience for deploying Windows images.
|
||||
| Windows Version being deployed | Boot.wim from Windows 10 | Boot.wim from Windows Server 2016 | Boot.wim from Windows Server 2019 | Boot.wim from Windows Server 2022 | Boot.wim from Windows 11 |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| **Windows 11** | Not supported, blocked. | Not supported, blocked. | Not supported, blocked. |Not supported, blocked. | Not supported, blocked. |
|
||||
| **Windows 10** | Supported, using a boot image from matching or newer version. | Supported, using a boot image from a [currently supported version of Windows 10](/windows/release-health/supported-versions-windows-client#windows-10-supported-versions). | Supported, using a boot image from a [currently supported version of Windows 10](/windows/release-health/supported-versions-windows-client#windows-10-supported-versions).| Not supported. | Not supported. |
|
||||
| **Windows Server 2025** | Not supported. | Not supported. | Not supported. | Not supported. | Not supported. |
|
||||
| **Windows Server 2022** | Deprecated, with a warning message. | Deprecated, with a warning message. | Deprecated, with a warning message. | Deprecated, with a warning message. | Not supported. |
|
||||
| **Windows Server 2019** | Supported, using a boot image from a [currently supported version of Windows 10](/windows/release-health/supported-versions-windows-client#windows-10-supported-versions). | Supported. | Supported. | Not supported. | Not supported. |
|
||||
| **Windows Server 2016** | Supported, using a boot image from a [currently supported version of Windows 10](/windows/release-health/supported-versions-windows-client#windows-10-supported-versions). |Supported. | Not supported. | Not supported. | Not supported. |
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> [Microsoft Deployment Toolkit](/mem/configmgr/mdt/) (MDT) only supports deployment of Windows 10. It doesn't support deployment of Windows 11. For more information, see [Supported platforms](/mem/configmgr/mdt/release-notes#supported-platforms).
|
||||
> The following error message might be displayed when attempting to use **boot.wim** on WDS running on Windows Server 2025:
|
||||
>
|
||||
> `A media driver your computer needs is missing. This could be a DVD, USB or Hard disk driver. If you have a CD, DVD, or USB flash drive with the driver on it, please insert it now.`
|
||||
>
|
||||
> An error message is expected since using **boot.wim** on WDS running on Windows Server 2025 isn't supported.
|
||||
|
||||
## Reason for the change
|
||||
|
||||
Alternatives to WDS, such as [Microsoft Configuration Manager](/mem/configmgr/osd/understand/introduction-to-operating-system-deployment), provide a better, more flexible, and feature-rich experience for deploying Windows images.
|
||||
|
||||
## Not affected
|
||||
|
||||
This change doesn’t affect WDS PXE boot. You can still use WDS to PXE boot devices with custom boot images, but you can't use **boot.wim** as the boot image and run Windows Setup in WDS mode.
|
||||
This change doesn't affect WDS PXE boot. WDS can still be used to PXE boot devices with custom boot images, but **boot.wim** can't be used as the boot image and run Windows Setup in WDS mode.
|
||||
|
||||
You can still run Windows Setup from a network share. This change doesn't change Workflows that use a custom boot.wim, such as MDT or Configuration Manager.
|
||||
Windows Setup can still run from a network share. This change doesn't change Workflows that use a custom boot.wim, such as Microsoft Deployment Toolkit (MDT) or Microsoft Configuration Manager.
|
||||
|
||||
## Summary
|
||||
|
||||
- Windows 11 workflows that rely on **boot.wim** from installation media are blocked. You can't perform an end to end deployment of Windows 11 using only WDS.
|
||||
- Windows 11 workflows that rely on **boot.wim** from installation media are blocked. An end to end deployment of Windows 11 using only WDS can't be performed.
|
||||
|
||||
- This change doesn't affect Windows 10, Windows Server 2019, and previous operating system versions.
|
||||
|
||||
- Windows Server 2022 workflows that rely on **boot.wim** from installation media show a non-blocking deprecation notice. The notice can be dismissed, and currently the workflow isn't blocked.
|
||||
|
||||
- Windows Server workflows after Windows Server 2022 that rely on **boot.wim** from installation media are blocked.
|
||||
|
||||
If you currently use WDS with **boot.wim** from installation media for end-to-end operating system deployment, and your OS version isn't supported, deprecated, or blocked, it's recommended that you use deployment tools such as MDT, Configuration Manager, or a non-Microsoft solution with a custom boot.wim image.
|
||||
If WDS is being used with **boot.wim** from installation media for end-to-end operating system deployment, and the OS version isn't supported, deprecated, or blocked, Microsoft recommends using deployment tools such as Microsoft Configuration Manager, or a non-Microsoft solution that uses a custom boot.wim image.
|
||||
|
||||
## Also see
|
||||
## Related content
|
||||
|
||||
- [Features removed or no longer developed starting with Windows Server 2022](/windows-server/get-started/removed-deprecated-features-windows-server-2022#features-were-no-longer-developing)
|
||||
- [Create a custom Windows PE boot image with Configuration Manager](deploy-windows-cm/create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
- [Features removed or no longer developed starting with Windows Server 2022](/windows-server/get-started/removed-deprecated-features-windows-server-2022#features-were-no-longer-developing).
|
||||
- [Customize boot images with Configuration Manager](/mem/configmgr/osd/get-started/customize-boot-images).
|
||||
|
||||
@ -47,79 +47,79 @@
|
||||
href: deploy/windows-autopatch-groups-manage-autopatch-groups.md
|
||||
- name: Post-device registration readiness checks
|
||||
href: deploy/windows-autopatch-post-reg-readiness-checks.md
|
||||
- name: Operate
|
||||
- name: Manage
|
||||
href:
|
||||
items:
|
||||
- name: Software update management
|
||||
href: operate/windows-autopatch-groups-update-management.md
|
||||
- name: Customize Windows Update settings
|
||||
href: manage/windows-autopatch-customize-windows-update-settings.md
|
||||
- name: Windows feature updates
|
||||
href: manage/windows-autopatch-windows-feature-update-overview.md
|
||||
items:
|
||||
- name: Windows updates
|
||||
href:
|
||||
items:
|
||||
- name: Customize Windows Update settings
|
||||
href: operate/windows-autopatch-groups-windows-update.md
|
||||
- name: Windows quality updates
|
||||
href: operate/windows-autopatch-groups-windows-quality-update-overview.md
|
||||
items:
|
||||
- name: Windows quality update end user experience
|
||||
href: operate/windows-autopatch-groups-windows-quality-update-end-user-exp.md
|
||||
- name: Windows quality update signals
|
||||
href: operate/windows-autopatch-groups-windows-quality-update-signals.md
|
||||
- name: Windows quality update communications
|
||||
href: operate/windows-autopatch-groups-windows-quality-update-communications.md
|
||||
- name: Windows feature updates
|
||||
href: operate/windows-autopatch-groups-windows-feature-update-overview.md
|
||||
items:
|
||||
- name: Manage Windows feature updates
|
||||
href: operate/windows-autopatch-groups-manage-windows-feature-update-release.md
|
||||
- name: Microsoft 365 Apps for enterprise
|
||||
href: operate/windows-autopatch-microsoft-365-apps-enterprise.md
|
||||
- name: Microsoft Edge
|
||||
href: operate/windows-autopatch-edge.md
|
||||
- name: Microsoft Teams
|
||||
href: operate/windows-autopatch-teams.md
|
||||
- name: Windows quality and feature update reports overview
|
||||
href: operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md
|
||||
- name: Manage Windows feature updates
|
||||
href: manage/windows-autopatch-manage-windows-feature-update-releases.md
|
||||
- name: Windows quality updates
|
||||
href: manage/windows-autopatch-windows-quality-update-overview.md
|
||||
items:
|
||||
- name: Windows quality update end user experience
|
||||
href: manage/windows-autopatch-windows-quality-update-end-user-exp.md
|
||||
- name: Windows quality update signals
|
||||
href: manage/windows-autopatch-windows-quality-update-signals.md
|
||||
- name: Windows quality update communications
|
||||
href: manage/windows-autopatch-windows-quality-update-communications.md
|
||||
- name: Manage driver and firmware updates
|
||||
href: manage/windows-autopatch-manage-driver-and-firmware-updates.md
|
||||
- name: Microsoft 365 Apps for enterprise
|
||||
href: manage/windows-autopatch-microsoft-365-apps-enterprise.md
|
||||
items:
|
||||
- name: Microsoft 365 Apps for enterprise update policies
|
||||
href: manage/windows-autopatch-microsoft-365-policies.md
|
||||
- name: Microsoft Edge
|
||||
href: manage/windows-autopatch-edge.md
|
||||
- name: Microsoft Teams
|
||||
href: manage/windows-autopatch-teams.md
|
||||
- name: Submit a support request
|
||||
href: manage/windows-autopatch-support-request.md
|
||||
- name: Exclude a device
|
||||
href: manage/windows-autopatch-exclude-device.md
|
||||
- name: Unenroll your tenant
|
||||
href: manage/windows-autopatch-unenroll-tenant.md
|
||||
- name: Monitor
|
||||
href:
|
||||
items:
|
||||
- name: Windows feature and quality update reports overview
|
||||
href: monitor/windows-autopatch-windows-quality-and-feature-update-reports-overview.md
|
||||
items:
|
||||
- name: Windows quality update reports
|
||||
href:
|
||||
items:
|
||||
- name: Summary dashboard
|
||||
href: operate/windows-autopatch-groups-windows-quality-update-summary-dashboard.md
|
||||
- name: Quality update status report
|
||||
href: operate/windows-autopatch-groups-windows-quality-update-status-report.md
|
||||
- name: Quality update trending report
|
||||
href: operate/windows-autopatch-groups-windows-quality-update-trending-report.md
|
||||
- name: Reliability report
|
||||
href: operate/windows-autopatch-reliability-report.md
|
||||
- name: Windows feature update reports
|
||||
href:
|
||||
items:
|
||||
- name: Summary dashboard
|
||||
href: operate/windows-autopatch-groups-windows-feature-update-summary-dashboard.md
|
||||
href: monitor/windows-autopatch-windows-feature-update-summary-dashboard.md
|
||||
- name: Feature update status report
|
||||
href: operate/windows-autopatch-groups-windows-feature-update-status-report.md
|
||||
href: monitor/windows-autopatch-windows-feature-update-status-report.md
|
||||
- name: Feature update trending report
|
||||
href: operate/windows-autopatch-groups-windows-feature-update-trending-report.md
|
||||
- name: Windows quality and feature update device alerts
|
||||
href: operate/windows-autopatch-device-alerts.md
|
||||
href: monitor/windows-autopatch-windows-feature-update-trending-report.md
|
||||
- name: Windows quality update reports
|
||||
href:
|
||||
items:
|
||||
- name: Summary dashboard
|
||||
href: monitor/windows-autopatch-windows-quality-update-summary-dashboard.md
|
||||
- name: Quality update status report
|
||||
href: monitor/windows-autopatch-windows-quality-update-status-report.md
|
||||
- name: Quality update trending report
|
||||
href: monitor/windows-autopatch-windows-quality-update-trending-report.md
|
||||
- name: Reliability report
|
||||
href: monitor/windows-autopatch-reliability-report.md
|
||||
- name: Windows feature and quality update device alerts
|
||||
href: monitor/windows-autopatch-device-alerts.md
|
||||
- name: Policy health
|
||||
href:
|
||||
items:
|
||||
- name: Policy health and remediation
|
||||
href: operate/windows-autopatch-policy-health-and-remediation.md
|
||||
href: monitor/windows-autopatch-policy-health-and-remediation.md
|
||||
- name: Resolve policy conflicts
|
||||
href: operate/windows-autopatch-resolve-policy-conflicts.md
|
||||
href: monitor/windows-autopatch-resolve-policy-conflicts.md
|
||||
- name: Maintain the Windows Autopatch environment
|
||||
href: operate/windows-autopatch-maintain-environment.md
|
||||
- name: Manage driver and firmware updates
|
||||
href: operate/windows-autopatch-manage-driver-and-firmware-updates.md
|
||||
- name: Submit a support request
|
||||
href: operate/windows-autopatch-support-request.md
|
||||
- name: Exclude a device
|
||||
href: operate/windows-autopatch-exclude-device.md
|
||||
- name: Unenroll your tenant
|
||||
href: operate/windows-autopatch-unenroll-tenant.md
|
||||
href: monitor/windows-autopatch-maintain-environment.md
|
||||
- name: References
|
||||
href:
|
||||
items:
|
||||
@ -128,8 +128,6 @@
|
||||
items:
|
||||
- name: Windows update policies
|
||||
href: references/windows-autopatch-windows-update-unsupported-policies.md
|
||||
- name: Microsoft 365 Apps for enterprise update policies
|
||||
href: references/windows-autopatch-microsoft-365-policies.md
|
||||
- name: Conflicting configurations
|
||||
href: references/windows-autopatch-conflicting-configurations.md
|
||||
- name: Changes made at tenant enrollment
|
||||
|
||||
@ -128,9 +128,7 @@ For organizations seeking greater control, you can allow or block Microsoft 365
|
||||
|
||||
[Servicing profiles](/deployoffice/admincenter/servicing-profile) is a feature in the [Microsoft 365 Apps admin center](https://config.office.com/) that provides controlled update management of monthly Office updates, including controls for user and device targeting, scheduling, rollback, and reporting.
|
||||
|
||||
A [service profile](/deployoffice/admincenter/servicing-profile#compatibility-with-other-management-tools) takes precedence over other policies, such as a Microsoft Intune policy or the Office Deployment Tool. The servicing profile affects all devices that meet the [device eligibility requirements](#device-eligibility) regardless of existing management tools in your environment. So, if you're targeting a managed device with a servicing profile it's ineligible for Microsoft 365 App update management.
|
||||
|
||||
However, the device may still be eligible for other managed updates. For more information about a device's eligibility for a given [software update workload](windows-autopatch-update-management.md#software-update-workloads), see the Device eligibility section of each respective software update workload.
|
||||
A [service profile](/deployoffice/admincenter/servicing-profile#compatibility-with-other-management-tools) takes precedence over other policies, such as a Microsoft Intune policy or the Office Deployment Tool. The servicing profile affects all devices that meet the [device eligibility requirements](#device-eligibility) regardless of existing management tools in your environment. So, if you're targeting a managed device with a servicing profile it's ineligible for Microsoft 365 App update management.However, the device may still be eligible for other managed updates.
|
||||
|
||||
## Incidents and outages
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user