diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 02f5b9f131..81bb0aadf1 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -1,5 +1,525 @@ { "redirections": [ + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Add-or-Remove-Computers.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Add-or-Remove-Computers", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Add-printers.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Add-printers", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Allow-one-account-to-have-multiple-sessions.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Allow-one-account-to-have-multiple-sessions", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Application-Considerations.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Application-Considerations", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Block-or-Unblock-a-Station.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Block-or-Unblock-a-Station", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Block-or-Unblock-USB-Storage.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Block-or-Unblock-USB-Storage", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Common-MultiPoint-services-Usage-Scenarios.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Common-MultiPoint-services-Usage-Scenarios", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Configure-Disk-Protection-in-MultiPoint-services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Configure-Disk-Protection-in-MultiPoint-services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Configure-group-policies-for-a-domain-deployment.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Configure-group-policies-for-a-domain-deployment", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Configure-stations-for-automatic-logon.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Configure-stations-for-automatic-logon", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Create-a-MultiPoint-Dashboard-User-Account.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Create-a-MultiPoint-Dashboard-User-Account", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Create-a-Standard-User-Account.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Create-a-Standard-User-Account", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Create-an-Administrative-User-Account.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Create-an-Administrative-User-Account", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Create-local-user-accounts.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Create-local-user-accounts", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Create-Windows-10-Enterprise-virtual-desktops-for-stations.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Create-Windows-10-Enterprise-virtual-desktops-for-stations", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Deploy-a-new-MultiPoint-Services-system.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Deploy-a-new-MultiPoint-Services-system", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/deploy-multipoint-services-task-list.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/deploy-multipoint-services-task-list", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Deploying-MultiPoint-Services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Deploying-MultiPoint-Services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Edit-Server-Settings.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Edit-Server-Settings", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Enable-file-sharing-in-multipoint-services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Enable-file-sharing-in-multipoint-services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Enable-or-Disable-Disk-Protection.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Enable-or-Disable-Disk-Protection", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/End-a-User-Session.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/End-a-User-Session", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Getting-Started-with-MultiPoint-Services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Getting-Started-with-MultiPoint-Services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Glossary.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Glossary", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/hardware-and-performance-recommendations.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/hardware-and-performance-recommendations", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Install-MultiPoint-services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Install-MultiPoint-services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/install-server-backup-on-multipoint.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/install-server-backup-on-multipoint", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/install-software-on-multipoint.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/install-software-on-multipoint", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Install-updates.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Install-updates", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Introducing-MultiPoint-services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Introducing-MultiPoint-services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/join-multipoint-services-to-a-domain.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/join-multipoint-services-to-a-domain", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Keep-Files-Private.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Keep-Files-Private", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Launch-or-Close-Applications-on-a-Station.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Launch-or-Close-Applications-on-a-Station", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/limit-user-access-to-multipoint.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/limit-user-access-to-multipoint", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Limit-Web-Access.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Limit-Web-Access", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Log-off-or-Disconnect-User-Sessions.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Log-off-or-Disconnect-User-Sessions", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Log-Off-User-Sessions.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Log-Off-User-Sessions", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Manage-Client-Access-Licenses.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Manage-Client-Access-Licenses", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Manage-MultiPoint-Systems-Using-MultiPoint-Dashboard.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Manage-MultiPoint-Systems-Using-MultiPoint-Dashboard", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Manage-Station-Hardware.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Manage-Station-Hardware", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Manage-System-Tasks-Using-MultiPoint-Manager.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Manage-System-Tasks-Using-MultiPoint-Manager", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Manage-User-Accounts.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Manage-User-Accounts", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Manage-User-Desktops-Using-MultiPoint-Dashboard.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Manage-User-Desktops-Using-MultiPoint-Dashboard", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Manage-User-Files.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Manage-User-Files", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Manage-User-Stations.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Manage-User-Stations", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Manage-Virtual-Desktops.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Manage-Virtual-Desktops", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Managing-MultiPoint-Services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Managing-MultiPoint-Services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Managing-Your-MultiPoint-Services-System.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Managing-Your-MultiPoint-Services-System", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/multipoint-attach-additional-stations.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/multipoint-attach-additional-stations", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/multipoint-hardware-device-drivers.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/multipoint-hardware-device-drivers", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/multipoint-services-migrate.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/multipoint-services-migrate", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/multipoint-services-migration-preparation.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/multipoint-services-migration-preparation", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/multipoint-services-migration-steps.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/multipoint-services-migration-steps", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/multipoint-services-migration-worksheet.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/multipoint-services-migration-worksheet", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/multipoint-services-post-migration-steps.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/multipoint-services-post-migration-steps", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/MultiPoint-services-Site-Planning.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/MultiPoint-services-Site-Planning", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/MultiPoint-services-Stations.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/MultiPoint-services-Stations", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/MultiPoint-services-Virtualization-Support.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/MultiPoint-services-Virtualization-Support", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/MultiPoint-Services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/MultiPoint-Services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/multipoint-software-license-compliance.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/multipoint-software-license-compliance", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/multipoint-users-scenario.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/multipoint-users-scenario", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Network-Considerations-and-User-Accounts.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Network-Considerations-and-User-Accounts", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Optional-configuration-tasks-for-a-MultiPoint-services-deployment.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Optional-configuration-tasks-for-a-MultiPoint-services-deployment", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Plan-user-accounts-for-your-MultiPoint-services-environment.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Plan-user-accounts-for-your-MultiPoint-services-environment", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Planning-a-MultiPoint-Services-Deployment.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Planning-a-MultiPoint-Services-Deployment", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Predeployment-Checklist.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Predeployment-Checklist", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Prepare-your-MultiPoint-services-system-for-users.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Prepare-your-MultiPoint-services-system-for-users", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Privacy-and-Security-Considerations.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Privacy-and-Security-Considerations", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Project-a-Station-to-Other-Stations.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Project-a-Station-to-Other-Stations", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Protecting-the-System-Volume-with-Disk-Protection.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Protecting-the-System-Volume-with-Disk-Protection", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Remap-All-Stations.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Remap-All-Stations", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Remap-Selected-MultiPoint-Systems.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Remap-Selected-MultiPoint-Systems", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Restart-or-Shut-Down-MultiPoint-Systems.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Restart-or-Shut-Down-MultiPoint-Systems", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Restart-or-Shut-Down.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Restart-or-Shut-Down", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Save-and-Share-Files-on-a-USB-Flash-Drive.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Save-and-Share-Files-on-a-USB-Flash-Drive", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Save-Connection-Settings-to-File.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Save-Connection-Settings-to-File", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/select-hardware-mps.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/select-hardware-mps", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/set-the-date-time.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/set-the-date-time", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Set-up-a-direct-video-connected-station-in-MultiPoint-services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Set-up-a-direct-video-connected-station-in-MultiPoint-services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Set-up-a-split-screen-station-in-multipoint-services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Set-up-a-split-screen-station-in-multipoint-services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Set-up-a-Station-for-Automatic-Logon.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Set-up-a-Station-for-Automatic-Logon", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Set-Up-a-Station.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Set-Up-a-Station", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Set-up-a-USB-zero-client-connected-station-in-MultiPoint-services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Set-up-a-USB-zero-client-connected-station-in-MultiPoint-services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Set-up-an-RDP-over-LAN-connected-station-in-multipoint-services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Set-up-an-RDP-over-LAN-connected-station-in-multipoint-services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Set-up-the-physical-computer-and-primary-station.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Set-up-the-physical-computer-and-primary-station", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Share-Files.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Share-Files", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Show-All-Stations.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Show-All-Stations", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Split-a-User-Station.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Split-a-User-Station", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Storing-Files-with-MultiPoint-services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Storing-Files-with-MultiPoint-services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Suspend-and-Leave-User-Session-Active.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Suspend-and-Leave-User-Session-Active", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Switch-Between-Modes.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Switch-Between-Modes", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/System-administration-in-multipoint-services.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/System-administration-in-multipoint-services", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Take-Control-of-a-User-Session.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Take-Control-of-a-User-Session", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Troubleshooting.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Troubleshooting", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Update-and-install-device-drivers-if-needed.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Update-and-install-device-drivers-if-needed", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Update-or-Delete-a-User-Account.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Update-or-Delete-a-User-Account", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Use-IM.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Use-IM", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/User-Account-Considerations.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/User-Account-Considerations", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Variables-Affecting-MultiPoint-services-System-Performance.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Variables-Affecting-MultiPoint-services-System-Performance", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/View-Hardware-Status.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/View-Hardware-Status", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/View-Options-for-Session-Thumbnails-in-MultiPoint-Dashboard.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/View-Options-for-Session-Thumbnails-in-MultiPoint-Dashboard", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/View-User-Connection-Status.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/View-User-Connection-Status", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Work-with-USB-Devices.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Work-with-USB-Devices", + "redirect_document_id": false + }, + { + "source_path": "WindowsServerDocs/remote/multipoint-services/Work-with-Video-Devices.md", + "redirect_url": "/previous-versions/windows-server/it-pro/windows-server-2019/remote/multipoint-services/Work-with-Video-Devices", + "redirect_document_id": false + }, { "source_path": "WindowsServerDocs/windows-server.md", "redirect_url": "/windows-server/index", diff --git a/WindowsServerDocs/administration/windows-commands/active.md b/WindowsServerDocs/administration/windows-commands/active.md index 868549a594..40f1d14603 100644 --- a/WindowsServerDocs/administration/windows-commands/active.md +++ b/WindowsServerDocs/administration/windows-commands/active.md @@ -3,8 +3,8 @@ title: active no-loc: [active] description: Reference article for the active command, which on basic disks, marks the partition with focus as active. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/add-alias.md b/WindowsServerDocs/administration/windows-commands/add-alias.md index 4e5a8a3a76..3a4be91216 100644 --- a/WindowsServerDocs/administration/windows-commands/add-alias.md +++ b/WindowsServerDocs/administration/windows-commands/add-alias.md @@ -3,8 +3,8 @@ title: add alias no-loc: [add alias] description: Reference article for the add alias command, which adds aliases to the alias environment. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/add-volume.md b/WindowsServerDocs/administration/windows-commands/add-volume.md index 8ce2660f97..8752708077 100644 --- a/WindowsServerDocs/administration/windows-commands/add-volume.md +++ b/WindowsServerDocs/administration/windows-commands/add-volume.md @@ -3,8 +3,8 @@ title: add volume no-loc: [add volume] description: Reference article for the add volume command, which adds volumes to the shadow copy Set, which is the set of volumes to be shadow copied. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/add.md b/WindowsServerDocs/administration/windows-commands/add.md index e372dd75d1..8fa773ee06 100644 --- a/WindowsServerDocs/administration/windows-commands/add.md +++ b/WindowsServerDocs/administration/windows-commands/add.md @@ -3,8 +3,8 @@ title: add (diskshadow) no-loc: [add (diskshadow)] description: Reference article for the add command, which adds volumes to the set of volumes that are to be shadow copied, or adds aliases to the alias environment. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/13/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/add_2.md b/WindowsServerDocs/administration/windows-commands/add_2.md index 298a5e1c97..23c4cb7d96 100644 --- a/WindowsServerDocs/administration/windows-commands/add_2.md +++ b/WindowsServerDocs/administration/windows-commands/add_2.md @@ -3,8 +3,8 @@ title: add no-loc: [add] description: Reference article for the add command, which adds a disk or volume in an existing RAID configuration. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/12/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/adprep.md b/WindowsServerDocs/administration/windows-commands/adprep.md index f2bf7a2f7b..2456bbc5b6 100644 --- a/WindowsServerDocs/administration/windows-commands/adprep.md +++ b/WindowsServerDocs/administration/windows-commands/adprep.md @@ -3,8 +3,8 @@ title: Adprep no-loc: [Adprep] description: Learn about adprep command line tool to prepare a forest and domain for a domain controller for Windows Server. ms.topic: reference -author: meaghanlewis -ms.author: mosagie +author: dknappettmsft +ms.author: daknappe ms.date: 04/22/2024 --- @@ -23,9 +23,9 @@ For more information about running `Adprep.exe` and how to resolve errors that c For examples of how this command can be used, see [Examples](#examples). -For more information about running `adprep /forestprep`, see [Prepare a Windows 2000 or Windows Server 2003 Forest Schema for a Domain Controller that Runs Windows Server 2008 or Windows Server 2008 R2](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc753437(v=ws.10)). +For more information about running `adprep /forestprep`, see [Prepare a Windows 2000 or Windows Server 2003 Forest Schema for a Domain Controller that Runs Windows Server 2008 or Windows Server 2008 R2](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc753437(v=ws.10)). -For more information about running `adprep /domainprep /gpprep`, see [Prepare a Windows 2000 or Windows Server 2003 Domain for a Domain Controller That Runs Windows Server 2008 or Windows Server 2008 R2](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754670(v=ws.10)). +For more information about running `adprep /domainprep /gpprep`, see [Prepare a Windows 2000 or Windows Server 2003 Domain for a Domain Controller That Runs Windows Server 2008 or Windows Server 2008 R2](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754670(v=ws.10)). For more information about running `adprep /rodcprep`, see [Prepare a Forest for a Read-Only Domain Controller](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc771055(v=ws.10)). @@ -40,7 +40,7 @@ adprep {/forestprep | /domainprep | /domainprep /gpprep | /rodcprep | /wssg | /s |---|---| | /forestprep |

Prepares a forest for the introduction of a domain controller that runs Windows Server. You run this command only once in the forest. You must run this command on the domain controller that holds the schema operations master role (also known as flexible single master operations or FSMO) for the forest. You must be a member of all the following groups to run this command:

| | /domainprep |

Prepares a domain for the introduction of a domain controller that runs Windows Server. You run this command after the **forestprep** command finishes and after the changes replicate to all the domain controllers in the forest.

Run this command in each domain where you plan to add a domain controller that runs Windows Server. You must run this command on the domain controller that holds the infrastructure operations master role for the domain. You must be a member of the Domain Admins group to run this command.

| -|

/domainprep

/gpprep |

Performs similar updates to **domainprep**. However, this command also provides updates that are necessary to enable the Resultant Set of Policy (RSOP) Planning Mode functionality.

In Active Directory environments that run Microsoft Windows, this command performs updates during off-peak hours. Replicating updates to file system permissions and Active Directory permissions on existing Group Policy objects (GPOs) during off-peak hours minimizes replication traffic.

Run this command after the **forestprep** command finishes and after the changes replicate to all domain controllers in the forest. You must run this command on the infrastructure master for the domain. For more information about running this command in Windows Active Directory environments, see [Prepare Your Infrastructure for Upgrade](/previous-versions/windows/it-pro/windows-server-2003/cc783495(v=ws.10)). | +|

/domainprep

/gpprep |

Performs similar updates to **domainprep**. However, this command also provides updates that are necessary to enable the Resultant Set of Policy (RSOP) Planning Mode functionality.

In Active Directory environments that run Microsoft Windows, this command performs updates during off-peak hours. Replicating updates to file system permissions and Active Directory permissions on existing Group Policy objects (GPOs) during off-peak hours minimizes replication traffic.

Run this command after the **forestprep** command finishes and after the changes replicate to all domain controllers in the forest. You must run this command on the infrastructure master for the domain. For more information about running this command in Windows Active Directory environments, see [Prepare Your Infrastructure for Upgrade](/previous-versions/windows/it-pro/windows-server-2003/cc783495(v=ws.10)). | | /rodcprep | This parameter updates permissions on the application directory partitions to enable replication of the partitions to read-only domain controllers (RODCs). This operation runs remotely; it contacts the infrastructure master in each domain to update the permissions. You need to run this command only once in the forest. However, you can rerun this command anytime if it fails to complete successfully because an infrastructure master isn't available. You can run this command on any computer in the forest. You must be a member of the Enterprise Admins group to run this command. | | /wssg | Returns an expanded set of exit codes, instead of just 0 (Success) and 1 (Failure). | | /silent | Specifies that no standard output is returned from an operation. This parameter can be used only if /wssg is also used. | @@ -50,7 +50,7 @@ adprep {/forestprep | /domainprep | /domainprep /gpprep | /rodcprep | /wssg | /s ## Remarks -- To prepare an existing Windows or Windows Server Active Directory environment for a Windows Server domain controller, run the version of adprep included in the Windows Server installation media. +- To prepare an existing Windows or Windows Server Active Directory environment for a Windows Server domain controller, run the version of adprep included in the Windows Server installation media. - You can also perform verification steps before and after you run the **adprep** command to help ensure that the operations complete successfully. For more information, see [Steps for Extending the Schema](/previous-versions/windows/it-pro/windows-server-2003/cc773360(v=ws.10)). diff --git a/WindowsServerDocs/administration/windows-commands/append.md b/WindowsServerDocs/administration/windows-commands/append.md index 04d6a4da4f..d74a254fb9 100644 --- a/WindowsServerDocs/administration/windows-commands/append.md +++ b/WindowsServerDocs/administration/windows-commands/append.md @@ -3,8 +3,8 @@ title: append no-loc: [append] description: Reference article for the append command, which allows programs to open data files in specified directories, as if they were in the current directory. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/arp.md b/WindowsServerDocs/administration/windows-commands/arp.md index 3699b6d20d..4749876e2f 100644 --- a/WindowsServerDocs/administration/windows-commands/arp.md +++ b/WindowsServerDocs/administration/windows-commands/arp.md @@ -2,8 +2,8 @@ title: arp description: Reference article for the arp command, which displays and modifies entries in the Address Resolution Protocol (arp) cache used to store IP addresses and their resolved physical addresses in Windows. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 08/15/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/assign.md b/WindowsServerDocs/administration/windows-commands/assign.md index d68e98e2d3..5bb83024ff 100644 --- a/WindowsServerDocs/administration/windows-commands/assign.md +++ b/WindowsServerDocs/administration/windows-commands/assign.md @@ -3,8 +3,8 @@ title: assign no-loc: [assign] description: Reference article for the assign command, which assigns a drive letter or mount point to the volume with focus. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/assoc.md b/WindowsServerDocs/administration/windows-commands/assoc.md index 11182ef3e7..b6983bb48d 100644 --- a/WindowsServerDocs/administration/windows-commands/assoc.md +++ b/WindowsServerDocs/administration/windows-commands/assoc.md @@ -3,8 +3,8 @@ title: assoc no-loc: [assoc] description: Reference article for the assoc command, which displays or modifies file name extension associations. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/at.md b/WindowsServerDocs/administration/windows-commands/at.md index 84a103a36e..86d79a58fb 100644 --- a/WindowsServerDocs/administration/windows-commands/at.md +++ b/WindowsServerDocs/administration/windows-commands/at.md @@ -3,8 +3,8 @@ title: at no-loc: [at] description: Reference article for the at command, which schedules commands and programs to run on a computer at a specified time and date. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/atmadm.md b/WindowsServerDocs/administration/windows-commands/atmadm.md index 4c41997d9b..893ac4b4e4 100644 --- a/WindowsServerDocs/administration/windows-commands/atmadm.md +++ b/WindowsServerDocs/administration/windows-commands/atmadm.md @@ -2,8 +2,8 @@ title: atmadm description: Reference article for the atmadm command, which monitors connections and addresses that are registered by the atM call Manager on an asynchronous transfer mode (atM) network. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # atmadm diff --git a/WindowsServerDocs/administration/windows-commands/attach-vdisk.md b/WindowsServerDocs/administration/windows-commands/attach-vdisk.md index af8a04027b..40baf5fbc8 100644 --- a/WindowsServerDocs/administration/windows-commands/attach-vdisk.md +++ b/WindowsServerDocs/administration/windows-commands/attach-vdisk.md @@ -2,8 +2,8 @@ title: attach vdisk description: Reference article for the attach vdisk command, which attaches (sometimes called mounts or surfaces) a virtual hard disk (VHD) so that it appears on the host computer as a local hard disk drive. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # attach vdisk diff --git a/WindowsServerDocs/administration/windows-commands/attrib.md b/WindowsServerDocs/administration/windows-commands/attrib.md index ab7b4a862d..36e2c84679 100644 --- a/WindowsServerDocs/administration/windows-commands/attrib.md +++ b/WindowsServerDocs/administration/windows-commands/attrib.md @@ -2,8 +2,8 @@ title: attrib description: Reference article for the attrib command that displays, sets, or removes attributes assigned to files or directories. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 09/22/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/attributes-disk.md b/WindowsServerDocs/administration/windows-commands/attributes-disk.md index 34ebccc501..e25308f581 100644 --- a/WindowsServerDocs/administration/windows-commands/attributes-disk.md +++ b/WindowsServerDocs/administration/windows-commands/attributes-disk.md @@ -2,8 +2,8 @@ title: attributes disk description: Reference article for the attributes disk command, which displays, sets, or clears the attributes of a disk. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/attributes-volume.md b/WindowsServerDocs/administration/windows-commands/attributes-volume.md index 55551f4463..8d7583fe01 100644 --- a/WindowsServerDocs/administration/windows-commands/attributes-volume.md +++ b/WindowsServerDocs/administration/windows-commands/attributes-volume.md @@ -2,8 +2,8 @@ title: attributes volume description: Reference article for the attributes volume command, which displays, sets, or clears the attributes of a volume. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # attributes volume diff --git a/WindowsServerDocs/administration/windows-commands/attributes.md b/WindowsServerDocs/administration/windows-commands/attributes.md index 9aa4e8d184..449182c103 100644 --- a/WindowsServerDocs/administration/windows-commands/attributes.md +++ b/WindowsServerDocs/administration/windows-commands/attributes.md @@ -2,8 +2,8 @@ title: attributes description: Reference article for the attributes command, which displays, sets, or clears the attributes of a disk or volume. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/auditpol-backup.md b/WindowsServerDocs/administration/windows-commands/auditpol-backup.md index d05cd93e3a..4b38dcb40a 100644 --- a/WindowsServerDocs/administration/windows-commands/auditpol-backup.md +++ b/WindowsServerDocs/administration/windows-commands/auditpol-backup.md @@ -2,8 +2,8 @@ title: auditpol backup description: Reference article for the auditpol backup command that backs up system audit policy settings, per-user audit policy settings for all users, and all auditing options to a comma-separated value (CSV) text file. ms.topic: reference -author: meaghanlewis -ms.author: mosagie +author: robinharwood +ms.author: roharwoo ms.date: 04/01/2023 --- # auditpol backup diff --git a/WindowsServerDocs/administration/windows-commands/auditpol-clear.md b/WindowsServerDocs/administration/windows-commands/auditpol-clear.md index 67d8ae5cbe..2bb103072c 100644 --- a/WindowsServerDocs/administration/windows-commands/auditpol-clear.md +++ b/WindowsServerDocs/administration/windows-commands/auditpol-clear.md @@ -2,8 +2,8 @@ title: auditpol clear description: Reference article for the auditpol clear command, which deletes the per-user audit policy for all users, resets (disables) the system audit policy for all subcategories, and sets all the auditing options to disabled. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # auditpol clear diff --git a/WindowsServerDocs/administration/windows-commands/auditpol-get.md b/WindowsServerDocs/administration/windows-commands/auditpol-get.md index 9d727aea90..bcaa8ca998 100644 --- a/WindowsServerDocs/administration/windows-commands/auditpol-get.md +++ b/WindowsServerDocs/administration/windows-commands/auditpol-get.md @@ -2,8 +2,8 @@ title: auditpol get description: Reference article for the auditpol get command, which retrieves the system policy, per-user policy, auditing options, and audit security descriptor object. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # auditpol get diff --git a/WindowsServerDocs/administration/windows-commands/auditpol-list.md b/WindowsServerDocs/administration/windows-commands/auditpol-list.md index 5474af887f..5e6d227ea1 100644 --- a/WindowsServerDocs/administration/windows-commands/auditpol-list.md +++ b/WindowsServerDocs/administration/windows-commands/auditpol-list.md @@ -2,8 +2,8 @@ title: auditpol list description: Reference article for the auditpol list command, which lists audit policy categories and subcategories, or lists users for whom a per-user audit policy is defined. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # auditpol list diff --git a/WindowsServerDocs/administration/windows-commands/auditpol-remove.md b/WindowsServerDocs/administration/windows-commands/auditpol-remove.md index 8d6c8bf2ba..6fb7e67d4f 100644 --- a/WindowsServerDocs/administration/windows-commands/auditpol-remove.md +++ b/WindowsServerDocs/administration/windows-commands/auditpol-remove.md @@ -2,8 +2,8 @@ title: auditpol remove description: Reference article for the auditpol remove command; auditpol removes the per-user audit policy for a specified account or all accounts. ms.topic: reference -author: meaghanlewis -ms.author: mosagie +author: dknappettmsft +ms.author: daknappe ms.date: 04/01/2023 --- # auditpol remove diff --git a/WindowsServerDocs/administration/windows-commands/auditpol-resourcesacl.md b/WindowsServerDocs/administration/windows-commands/auditpol-resourcesacl.md index 4cb43088e0..0e74efb2e7 100644 --- a/WindowsServerDocs/administration/windows-commands/auditpol-resourcesacl.md +++ b/WindowsServerDocs/administration/windows-commands/auditpol-resourcesacl.md @@ -2,8 +2,8 @@ title: auditpol resourceSACL description: Reference article for the auditpol resourceSACL command, which configures global resource system access control lists (SAcls). ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/auditpol-restore.md b/WindowsServerDocs/administration/windows-commands/auditpol-restore.md index fa68268533..c05fd34c5d 100644 --- a/WindowsServerDocs/administration/windows-commands/auditpol-restore.md +++ b/WindowsServerDocs/administration/windows-commands/auditpol-restore.md @@ -2,8 +2,8 @@ title: auditpol restore description: Reference article for the auditpol restore command, which restores system audit policy settings, per-user audit policy settings for all users, and all auditing options from a file that is syntactically consistent with the comma-separated value (CSV) file format used by the /backup option. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # auditpol restore diff --git a/WindowsServerDocs/administration/windows-commands/auditpol-set.md b/WindowsServerDocs/administration/windows-commands/auditpol-set.md index a323b57ae1..b3f7bebcf1 100644 --- a/WindowsServerDocs/administration/windows-commands/auditpol-set.md +++ b/WindowsServerDocs/administration/windows-commands/auditpol-set.md @@ -2,8 +2,8 @@ title: auditpol set description: Reference article for the auditpol set command, which sets the per-user audit policy, system audit policy, or auditing options. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # auditpol set diff --git a/WindowsServerDocs/administration/windows-commands/auditpol.md b/WindowsServerDocs/administration/windows-commands/auditpol.md index 25ddd2af22..64ed8a980b 100644 --- a/WindowsServerDocs/administration/windows-commands/auditpol.md +++ b/WindowsServerDocs/administration/windows-commands/auditpol.md @@ -2,8 +2,8 @@ title: auditpol description: Reference article for the auditpol command, which displays information about and performs functions to manipulate audit policies. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/autochk.md b/WindowsServerDocs/administration/windows-commands/autochk.md index 38beef0894..83342795da 100644 --- a/WindowsServerDocs/administration/windows-commands/autochk.md +++ b/WindowsServerDocs/administration/windows-commands/autochk.md @@ -2,8 +2,8 @@ title: autochk description: Reference article for the autochk command, which runs when the computer is started and prior to Windows Server starting to verify the logical integrity of a file system. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/autoconv.md b/WindowsServerDocs/administration/windows-commands/autoconv.md index 072d9e1b56..34cc98e70b 100644 --- a/WindowsServerDocs/administration/windows-commands/autoconv.md +++ b/WindowsServerDocs/administration/windows-commands/autoconv.md @@ -2,8 +2,8 @@ title: autoconv description: Reference article for the autoconv command, which converts file allocation table (Fat) and Fat32 volumes to the NTFS file system. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/autofmt.md b/WindowsServerDocs/administration/windows-commands/autofmt.md index af136ac457..9acc1ac6dd 100644 --- a/WindowsServerDocs/administration/windows-commands/autofmt.md +++ b/WindowsServerDocs/administration/windows-commands/autofmt.md @@ -2,8 +2,8 @@ title: autofmt description: Reference article for the autofmt command, which formats a drive or partition when called from the Windows Recovery Console. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/automount.md b/WindowsServerDocs/administration/windows-commands/automount.md index 5a9da7ce92..c83dea134d 100644 --- a/WindowsServerDocs/administration/windows-commands/automount.md +++ b/WindowsServerDocs/administration/windows-commands/automount.md @@ -2,8 +2,8 @@ title: automount description: Reference article for the automount command, which enables or disables the automount feature. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bcdboot.md b/WindowsServerDocs/administration/windows-commands/bcdboot.md index 532d5a49c4..1d72ab2a6c 100644 --- a/WindowsServerDocs/administration/windows-commands/bcdboot.md +++ b/WindowsServerDocs/administration/windows-commands/bcdboot.md @@ -2,8 +2,8 @@ title: bcdboot description: Reference article for the bcdboot command, which quickly set up a system partition, or repair the boot environment located on the system partition. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bcdedit.md b/WindowsServerDocs/administration/windows-commands/bcdedit.md index 158e0b350b..356bc722fd 100644 --- a/WindowsServerDocs/administration/windows-commands/bcdedit.md +++ b/WindowsServerDocs/administration/windows-commands/bcdedit.md @@ -2,8 +2,8 @@ title: bcdedit description: Reference article for the bcdedit command, which creates new stores, modify existing stores, and add boot menu parameters. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 05/27/2021 --- diff --git a/WindowsServerDocs/administration/windows-commands/bdehdcfg-driveinfo.md b/WindowsServerDocs/administration/windows-commands/bdehdcfg-driveinfo.md index d949cd09b4..a90c22b394 100644 --- a/WindowsServerDocs/administration/windows-commands/bdehdcfg-driveinfo.md +++ b/WindowsServerDocs/administration/windows-commands/bdehdcfg-driveinfo.md @@ -2,8 +2,8 @@ title: bdehdcfg driveinfo description: Reference article for the bdehdcfg driveinfo command, which displays the drive letter, the total size, the maximum free space, and the partition characteristics. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bdehdcfg: driveinfo diff --git a/WindowsServerDocs/administration/windows-commands/bdehdcfg-newdriveletter.md b/WindowsServerDocs/administration/windows-commands/bdehdcfg-newdriveletter.md index 461d2950f3..58cc4650fb 100644 --- a/WindowsServerDocs/administration/windows-commands/bdehdcfg-newdriveletter.md +++ b/WindowsServerDocs/administration/windows-commands/bdehdcfg-newdriveletter.md @@ -2,8 +2,8 @@ title: bdehdcfg newdriveletter description: Reference article for the bdehdcfg newdriveletter command, which assigns a new drive letter to the portion of a drive used as the system drive. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bdehdcfg-quiet.md b/WindowsServerDocs/administration/windows-commands/bdehdcfg-quiet.md index e11aa44ae1..2d822c6ab0 100644 --- a/WindowsServerDocs/administration/windows-commands/bdehdcfg-quiet.md +++ b/WindowsServerDocs/administration/windows-commands/bdehdcfg-quiet.md @@ -2,8 +2,8 @@ title: bdehdcfg quiet description: Reference article for the bdehdcfg quiet command, which tells bdehdcfg to not display all actions and errors. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bdehdcfg-restart.md b/WindowsServerDocs/administration/windows-commands/bdehdcfg-restart.md index 83faaae15e..b221dc1db3 100644 --- a/WindowsServerDocs/administration/windows-commands/bdehdcfg-restart.md +++ b/WindowsServerDocs/administration/windows-commands/bdehdcfg-restart.md @@ -2,8 +2,8 @@ title: bdehdcfg restart description: Reference article for the bdehdcfg restart command, which tells bdehdcfg that the computer should be restarted after the drive preparation has concluded. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bdehdcfg-size.md b/WindowsServerDocs/administration/windows-commands/bdehdcfg-size.md index bec9b9735c..54f15cd2b4 100644 --- a/WindowsServerDocs/administration/windows-commands/bdehdcfg-size.md +++ b/WindowsServerDocs/administration/windows-commands/bdehdcfg-size.md @@ -2,8 +2,8 @@ title: bdehdcfg size description: Reference article for the bdehdcfg size command, which specifies the size of the system partition when a new system drive is being created. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bdehdcfg-target.md b/WindowsServerDocs/administration/windows-commands/bdehdcfg-target.md index 8d0f79a805..8d657d905c 100644 --- a/WindowsServerDocs/administration/windows-commands/bdehdcfg-target.md +++ b/WindowsServerDocs/administration/windows-commands/bdehdcfg-target.md @@ -2,8 +2,8 @@ title: bdehdcfg target description: Reference article for the bdehdcfg target command, which prepares a partition for use as a system drive by BitLocker and Windows recovery. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bdehdcfg.md b/WindowsServerDocs/administration/windows-commands/bdehdcfg.md index 9e69682115..739535667d 100644 --- a/WindowsServerDocs/administration/windows-commands/bdehdcfg.md +++ b/WindowsServerDocs/administration/windows-commands/bdehdcfg.md @@ -2,8 +2,8 @@ title: bdehdcfg description: Reference article for the bdehdcfg command, which prepares a hard drive with the partitions necessary for BitLocker Drive Encryption. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/begin-backup.md b/WindowsServerDocs/administration/windows-commands/begin-backup.md index e58833b51f..e3c9f3fdfb 100644 --- a/WindowsServerDocs/administration/windows-commands/begin-backup.md +++ b/WindowsServerDocs/administration/windows-commands/begin-backup.md @@ -2,8 +2,8 @@ title: begin backup description: Reference article for the begin backup command, which starts a full backup session. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/begin-restore.md b/WindowsServerDocs/administration/windows-commands/begin-restore.md index 2abf2e99da..7a44b94687 100644 --- a/WindowsServerDocs/administration/windows-commands/begin-restore.md +++ b/WindowsServerDocs/administration/windows-commands/begin-restore.md @@ -2,8 +2,8 @@ title: begin restore description: Reference article for the begin restore command, which starts a restore session and issues a PreRestore event to involved writers. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-addfile.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-addfile.md index 47b3acf049..bf37588f30 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-addfile.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-addfile.md @@ -2,8 +2,8 @@ title: bitsadmin addfile description: Reference article for the bitsadmin addfile command, which adds a file to the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-addfileset.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-addfileset.md index 2269ad9006..f822e5d9e5 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-addfileset.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-addfileset.md @@ -2,8 +2,8 @@ title: bitsadmin addfileset description: Reference article for the bitsadmin addfileset command, which adds one or more files to the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-addfilewithranges.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-addfilewithranges.md index c18576ab04..bb3a8c2447 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-addfilewithranges.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-addfilewithranges.md @@ -2,8 +2,8 @@ title: bitsadmin addfilewithranges description: Reference article for the bitsadmin addfilewithranges command, which adds a file to the specified job. BITS downloads the specified ranges from the remote file. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-delete.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-delete.md index d201eedd35..8095a6cd14 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-delete.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-delete.md @@ -2,8 +2,8 @@ title: bitsadmin cache and delete description: Reference article for the bitsadmin cache and delete command, which deletes a specific cache entry. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-deleteurl.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-deleteurl.md index a2688b66eb..1c201b065b 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-deleteurl.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-deleteurl.md @@ -2,8 +2,8 @@ title: bitsadmin cache and deleteURL description: Reference article for the bitsadmin cache and deleteURL command, which deletes all cache entries for the given URL. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-getexpirationtime.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-getexpirationtime.md index 04d05c904c..f5f4986f2a 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-getexpirationtime.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-getexpirationtime.md @@ -2,8 +2,8 @@ title: bitsadmin cache and getexpirationtime description: Reference article for the bitsadmin cache and getexpirationtime command, which retrieves the cache expiration time. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-getlimit.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-getlimit.md index 910e885ddf..0d103d5fd6 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-getlimit.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-getlimit.md @@ -2,8 +2,8 @@ title: bitsadmin cache and getlimit description: Reference article for the bitsadmin cache and getlimit command that retrieves the cache limit. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 01/03/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-help.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-help.md index d345a6038e..c5bbc9d09e 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-help.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-help.md @@ -2,8 +2,8 @@ title: bitsadmin cache and help description: Reference article for the bitsadmin cache and help command, which displays the command-line usage for the **cache** switches. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-info.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-info.md index 318f8dfc07..8aba4b17c4 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-info.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-info.md @@ -2,8 +2,8 @@ title: bitsadmin cache and info description: Reference article for the bitsadmin cache and info command, which dumps a specific cache entry. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-list.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-list.md index b78f5947aa..a055081cd8 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-list.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-list.md @@ -2,8 +2,8 @@ title: bitsadmin cache and list description: Reference article for the bitsadmin cache and list command, which lists all cache entries. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-setexpirationtime.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-setexpirationtime.md index 25aa4ab0f7..2de4b09d19 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-setexpirationtime.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-setexpirationtime.md @@ -2,8 +2,8 @@ title: bitsadmin cache and setexpirationtime description: Reference article for the bitsadmin cache and setexpirationtime command, which sets the cache expiration time. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-setlimit.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-setlimit.md index 9104692520..ee3ff858e5 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-setlimit.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-and-setlimit.md @@ -2,8 +2,8 @@ title: bitsadmin cache and setlimit description: Reference article for the bitsadmin cache and setlimit command, which sets the cache size limit. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-clear.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-clear.md index 527b0bfac5..f676cf47b5 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-clear.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache-clear.md @@ -2,8 +2,8 @@ title: bitsadmin cache and clear description: Reference article for the bitsadmin cache and clear command that purges the local cache. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 01/06/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache.md index c12863548c..e70fea2e81 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-cache.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-cache.md @@ -2,8 +2,8 @@ title: bitsadmin cache description: Reference article for the bitsadmin cache command, which contains a list of the bitsadmin cache switches. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bitsadmin cache diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-cancel.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-cancel.md index 41242d148a..e37e3f77ad 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-cancel.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-cancel.md @@ -2,8 +2,8 @@ title: bitsadmin cancel description: Reference article for the bitsadmin cancel command, which removes the job from the transfer queue and deletes all temporary files associated with the job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-complete.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-complete.md index b3bd762a73..a58ad35e1c 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-complete.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-complete.md @@ -2,8 +2,8 @@ title: bitsadmin complete description: Reference article for the bitsadmin complete command, which completes the job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-create.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-create.md index bb81093540..ee677f5ea5 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-create.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-create.md @@ -2,8 +2,8 @@ title: bitsadmin create description: Reference article for the bitsadmin create command, which creates a transfer job with the given display name. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- @@ -14,7 +14,7 @@ ms.date: 10/16/2017 Creates a transfer job with the given display name. > [!NOTE] -> The **/Upload** and **/Upload-Reply** parameter types aren't supported by BITS 1.2 and earlier. +> The **/Upload** and **/Upload-Reply** parameter types aren't supported by BITS 1.2 and earlier. ## Syntax diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-examples.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-examples.md index 93682267b5..5a5de9eff0 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-examples.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-examples.md @@ -2,8 +2,8 @@ title: bitsadmin examples description: Examples showing how to use the bitsadmin tool to perform the most common tasks. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 05/31/2018 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getaclflags.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getaclflags.md index 8f270288b1..cde44f6db1 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getaclflags.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getaclflags.md @@ -2,8 +2,8 @@ title: bitsadmin getaclflags description: Reference article for the bitsadmin getaclflags command, which retrieves the access control list (ACL) propagations flags. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getbytestotal.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getbytestotal.md index 4fb8703d46..5cd0b4929c 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getbytestotal.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getbytestotal.md @@ -2,8 +2,8 @@ title: bitsadmin getbytestotal description: Reference article for the bitsadmin getbytestotal command, which Retrieves the size of the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getbytestransferred.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getbytestransferred.md index 001fc18850..c16150fbb0 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getbytestransferred.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getbytestransferred.md @@ -2,8 +2,8 @@ title: bitsadmin getbytestransferred description: Reference article for the bitsadmin getbytestransferred command, which retrieves the number of bytes transferred for the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getclientcertificate.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getclientcertificate.md index a772f8c2fe..0b57179ce6 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getclientcertificate.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getclientcertificate.md @@ -2,8 +2,8 @@ title: bitsadmin getclientcertificate description: Reference article for the bitsadmin getclientcertificate command, which retrieves the client certificate from the job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getcompletiontime.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getcompletiontime.md index 8d1e076257..1bbe14ac9c 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getcompletiontime.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getcompletiontime.md @@ -2,8 +2,8 @@ title: bitsadmin getcompletiontime description: Reference article for the bitsadmin getcompletiontime command, which retrieves the time that the job finished transferring data. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getcreationtime.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getcreationtime.md index 742d14bc23..2970ad93b8 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getcreationtime.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getcreationtime.md @@ -2,8 +2,8 @@ title: bitsadmin getcreationtime description: Reference article for the bitsadmin getcreationtime command, which retrieves the creation time for the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getcustomheaders.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getcustomheaders.md index 59b45a0d34..12e9027e07 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getcustomheaders.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getcustomheaders.md @@ -2,8 +2,8 @@ title: bitsadmin getcustomheaders description: Reference article for the bitsadmin getcustomheaders command, which retrieves the custom HTTP headers from the job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getdescription.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getdescription.md index 76d1a9d509..77306f4465 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getdescription.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getdescription.md @@ -2,8 +2,8 @@ title: bitsadmin getdescription description: Reference article for the bitsadmin getdescription command, which retrieves the description of the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getdisplayname.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getdisplayname.md index c8821aba00..c316acd0e4 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getdisplayname.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getdisplayname.md @@ -2,8 +2,8 @@ title: bitsadmin getdisplayname description: Reference article for the bitsadmin getdisplayname command, which retrieves the display name of the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-geterror.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-geterror.md index 284eff8fd0..995753cf5a 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-geterror.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-geterror.md @@ -2,8 +2,8 @@ title: bitsadmin geterror description: Reference article for the bitsadmin geterror command, which retrieves detailed error information for the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-geterrorcount.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-geterrorcount.md index e20b2ea379..1482b2d0ab 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-geterrorcount.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-geterrorcount.md @@ -2,8 +2,8 @@ title: bitsadmin geterrorcount description: Reference article for the bitsadmin geterrorcount command, which retrieves a count of the number of times the specified job generated a transient error. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getfilestotal.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getfilestotal.md index 425e7080b9..e019385429 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getfilestotal.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getfilestotal.md @@ -2,8 +2,8 @@ title: bitsadmin getfilestotal description: Reference article for the bitsadmin getfilestotal command, which retrieves the number of files in the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getfilestransferred.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getfilestransferred.md index b436e8e3e1..87974a837e 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getfilestransferred.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getfilestransferred.md @@ -2,8 +2,8 @@ title: bitsadmin getfilestransferred description: Reference article for the bitsadmin getfilestransferred command, which retrieves the number of files transferred for the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-gethelpertokenflags.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-gethelpertokenflags.md index 9bdd913b91..5eb5427ac1 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-gethelpertokenflags.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-gethelpertokenflags.md @@ -1,15 +1,15 @@ --- title: bitsadmin gethelpertokenflags -description: Reference article for the bitsadmin gethelpertokenflags command, which returns the usage flags for a helper token that is associated with a BITS transfer job. +description: Reference article for the bitsadmin gethelpertokenflags command, which returns the usage flags for a helper token that is associated with a BITS transfer job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 03/01/2019 --- # bitsadmin gethelpertokenflags -Returns the usage flags for a [helper token](/windows/win32/bits/helper-tokens-for-bits-transfer-jobs) that is associated with a BITS transfer job. +Returns the usage flags for a [helper token](/windows/win32/bits/helper-tokens-for-bits-transfer-jobs) that is associated with a BITS transfer job. > [!NOTE] > This command isn't supported by BITS 3.0 and earlier. @@ -32,11 +32,11 @@ Possible return values, including: - **0x0001.** The helper token is used to open the local file of an upload job, to create or rename the temporary file of a download job, or to create or rename the reply file of an upload-reply job. -- **0x0002.** The helper token is used to open the remote file of a Server Message Block (SMB) upload or download job, or in response to an HTTP server or proxy challenge for implicit NTLM or Kerberos credentials. You must call `/SetCredentialsJob TargetScheme NULL NULL` to allow the credentials to be sent over HTTP. +- **0x0002.** The helper token is used to open the remote file of a Server Message Block (SMB) upload or download job, or in response to an HTTP server or proxy challenge for implicit NTLM or Kerberos credentials. You must call `/SetCredentialsJob TargetScheme NULL NULL` to allow the credentials to be sent over HTTP. ## Examples -To retrieve the usage flags for a helper token associated with a BITS transfer job named *myDownloadJob*: +To retrieve the usage flags for a helper token associated with a BITS transfer job named *myDownloadJob*: ``` bitsadmin /gethelpertokenflags myDownloadJob diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-gethelpertokensid.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-gethelpertokensid.md index 329663cd84..cd1ba2d9de 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-gethelpertokensid.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-gethelpertokensid.md @@ -1,15 +1,15 @@ --- title: bitsadmin gethelpertokensid -description: Reference article for the bitsadmin gethelpertokensid command, which returns the SID of a BITS transfer job's helper token, if one is set. +description: Reference article for the bitsadmin gethelpertokensid command, which returns the SID of a BITS transfer job's helper token, if one is set. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 03/01/2019 --- # bitsadmin gethelpertokensid -Returns the SID of a BITS transfer job's [helper token](/windows/win32/bits/helper-tokens-for-bits-transfer-jobs), if one is set. +Returns the SID of a BITS transfer job's [helper token](/windows/win32/bits/helper-tokens-for-bits-transfer-jobs), if one is set. > [!NOTE] > This command isn't supported by BITS 3.0 and earlier. diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-gethttpmethod.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-gethttpmethod.md index 7fe550761b..3af4290606 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-gethttpmethod.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-gethttpmethod.md @@ -2,8 +2,8 @@ title: bitsadmin gethttpmethod description: Reference article for the bitsadmin gethttpmethod command, which gets the HTTP verb to use with the job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 03/01/2019 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getmaxdownloadtime.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getmaxdownloadtime.md index d220533861..e46e913220 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getmaxdownloadtime.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getmaxdownloadtime.md @@ -2,8 +2,8 @@ title: bitsadmin getmaxdownloadtime description: Reference article for the bitsadmin getmaxdownloadtime command, which retrieves the download timeout in seconds. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # bitsadmin getmaxdownloadtime diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getminretrydelay.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getminretrydelay.md index 6da0361f80..33c06abf3f 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getminretrydelay.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getminretrydelay.md @@ -2,8 +2,8 @@ title: bitsadmin getminretrydelay description: Reference article for the bitsadmin getminretrydelay command, which retrieves the length of time, in seconds, that the service waits after encountering a transient error before trying to transfer the file. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getmodificationtime.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getmodificationtime.md index 21aae8ebf9..965f4fd3e7 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getmodificationtime.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getmodificationtime.md @@ -2,8 +2,8 @@ title: bitsadmin getmodificationtime description: Reference article for the bitsadmin getmodificationtime command, which retrieves the last time the job was modified or data was successfully transferred. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getnoprogresstimeout.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getnoprogresstimeout.md index 3ed4a4d4c6..61471651b6 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getnoprogresstimeout.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getnoprogresstimeout.md @@ -2,8 +2,8 @@ title: bitsadmin getnoprogresstimeout description: Reference article for the bitsadmin getnoprogresstimeout command, which retrieves the length of time, in seconds, that the service will try to transfer the file after a transient error occurs. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getnotifycmdline.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getnotifycmdline.md index 7387888362..95480ac006 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getnotifycmdline.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getnotifycmdline.md @@ -2,8 +2,8 @@ title: bitsadmin getnotifycmdline description: Reference article for the bitsadmin getnotifycmdline command, which retrieves the command-line command that is run when the job finishes transferring data. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getnotifyflags.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getnotifyflags.md index 785a413a27..1e8101d5e0 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getnotifyflags.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getnotifyflags.md @@ -2,8 +2,8 @@ title: bitsadmin getnotifyflags description: Reference article for the bitsadmin getnotifyflags command, which retrieves the notification flags for the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getnotifyinterface.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getnotifyinterface.md index 3c8b66d50b..d74523b5ec 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getnotifyinterface.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getnotifyinterface.md @@ -2,8 +2,8 @@ title: bitsadmin getnotifyinterface description: Reference article for the bitsadmin getnotifyinterface command, which determines if another program has registered a COM callback interface for the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getowner.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getowner.md index 9052319d1b..605d42775a 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getowner.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getowner.md @@ -2,8 +2,8 @@ title: bitsadmin getowner description: Reference article for the bitsadmin getowner command, which retrieves the owner of the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getpeercachingflags.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getpeercachingflags.md index c63e2a6361..da06d3523b 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getpeercachingflags.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getpeercachingflags.md @@ -2,8 +2,8 @@ title: bitsadmin getpeercachingflags description: Reference article for the bitsadmin getpeercachingflags command, which retrieves flags that determine if the files of the job can be cached and served to peers, and if BITS can download content for the job from peers. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bitsadmin getpeercachingflags diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getpriority.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getpriority.md index 58534c7cf8..a594bb17cb 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getpriority.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getpriority.md @@ -2,8 +2,8 @@ title: bitsadmin getpriority description: Reference article for the bitsadmin getpriority command, which retrieves the priority of the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 03/01/2019 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getproxybypasslist.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getproxybypasslist.md index cd5328a068..5748620ddc 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getproxybypasslist.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getproxybypasslist.md @@ -2,8 +2,8 @@ title: bitsadmin getproxybypasslist description: Reference article for the bitsadmin getproxybypasslist command that retrieves the proxy bypass list for the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 01/06/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getproxylist.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getproxylist.md index 76d51f9fe0..3fffdf9510 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getproxylist.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getproxylist.md @@ -2,8 +2,8 @@ title: bitsadmin getproxylist - Retrieves the proxy list for the specified job. description: Reference article for the bitsadmin getproxylist command, which retrieves the proxy list for the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getproxyusage.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getproxyusage.md index 7124e2240b..c8f66351aa 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getproxyusage.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getproxyusage.md @@ -2,8 +2,8 @@ title: bitsadmin getproxyusage description: Reference article for the bitsadmin getproxyusage command, which retrieves the proxy usage setting for the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getreplydata.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getreplydata.md index 1002118bd9..bb838c2d2d 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getreplydata.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getreplydata.md @@ -2,8 +2,8 @@ title: bitsadmin getreplydata description: Reference article for the bitsadmin getreplydata command, which retrieves the server's upload-reply data in hexadecimal format for the job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getreplyfilename.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getreplyfilename.md index b9e1db1aa0..60fb601651 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getreplyfilename.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getreplyfilename.md @@ -2,8 +2,8 @@ title: bitsadmin getreplyfilename description: Reference article for the bitsadmin getreplyfilename command, which gets the path of the file that contains the server upload-reply for the job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getreplyprogress.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getreplyprogress.md index 44cb3badd8..6b2daf8599 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getreplyprogress.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getreplyprogress.md @@ -2,8 +2,8 @@ title: bitsadmin getreplyprogress description: Reference article for the bitsadmin getreplyprogress command, which retrieves the size and progress of the server upload-reply. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getsecurityflags.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getsecurityflags.md index 4c042984cf..51e3054d78 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getsecurityflags.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getsecurityflags.md @@ -2,8 +2,8 @@ title: bitsadmin getsecurityflags description: Reference article for the bitsadmin getsecurityflags command, which reports the HTTP security flags for URL redirection and checks performed on the server certificate during the transfer. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bitsadmin getsecurityflags diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getstate.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getstate.md index 86784b65f7..193a8ef006 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getstate.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getstate.md @@ -2,8 +2,8 @@ title: bitsadmin getstate description: Reference article for the bitsadmin getstate command, which retrieves the state of the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 04/01/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-gettemporaryname.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-gettemporaryname.md index 17bb39e013..2034ceef66 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-gettemporaryname.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-gettemporaryname.md @@ -2,8 +2,8 @@ title: bitsadmin gettemporaryname description: Reference article for the bitsadmin gettemporaryname command, which reports the temporary filename of the given file within the job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-gettype.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-gettype.md index 922d86cefc..58a2da435a 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-gettype.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-gettype.md @@ -2,8 +2,8 @@ title: bitsadmin gettype description: Reference article for the bitsadmin gettype command, which retrieves the job type of the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-getvalidationstate.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-getvalidationstate.md index 6640ea07bd..f8fc3a150c 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-getvalidationstate.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-getvalidationstate.md @@ -2,8 +2,8 @@ title: bitsadmin getvalidationstate description: Reference article for the bitsadmin getvalidationstate command, which reports the content validation state of the given file within the job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-help.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-help.md index 93761540d4..a9f4a540e9 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-help.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-help.md @@ -2,8 +2,8 @@ title: bitsadmin help description: Reference article for the bitsadmin help command, which displays the command-line usage. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 01/06/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-info.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-info.md index 043bd651a9..84e9661d2d 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-info.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-info.md @@ -2,8 +2,8 @@ title: bitsadmin info description: Reference article for the bitsadmin info command, which displays summary information about the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-list.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-list.md index f9c7f77e24..9f1656471a 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-list.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-list.md @@ -2,8 +2,8 @@ title: bitsadmin list description: Reference article for the bitsadmin list command, which lists the transfer jobs owned by the current user. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-listfiles.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-listfiles.md index 3aee75451d..04197d220f 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-listfiles.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-listfiles.md @@ -2,8 +2,8 @@ title: bitsadmin listfiles description: Reference article for the bitsadmin listfiles command, which lists the files in the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-makecustomheaderswriteonly.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-makecustomheaderswriteonly.md index 45db166400..3db3eee676 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-makecustomheaderswriteonly.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-makecustomheaderswriteonly.md @@ -2,8 +2,8 @@ title: bitsadmin makecustomheaderswriteonly description: Reference article for the bitsadmin makecustomheaderswriteonly command, which make a job's Custom HTTP Headers write-only. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 03/01/2019 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-monitor.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-monitor.md index 057aa143ba..73563a4570 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-monitor.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-monitor.md @@ -2,8 +2,8 @@ title: bitsadmin monitor description: Reference article for the bitsadmin monitor command, which monitors jobs in the transfer queue that are owned by the current user. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-nowrap.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-nowrap.md index 8cf28d194d..18c97998f4 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-nowrap.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-nowrap.md @@ -2,8 +2,8 @@ title: bitsadmin nowrap description: Reference article for the bitsadmin nowrap command, which truncates any line of output text extending beyond the rightmost edge of the command window. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching-and-getconfigurationflags.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching-and-getconfigurationflags.md index 8744fa2f52..51ad63fd10 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching-and-getconfigurationflags.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching-and-getconfigurationflags.md @@ -2,8 +2,8 @@ title: bitsadmin peercaching and getconfigurationflags description: Reference article for the bitsadmin peercaching and getconfigurationflags command, which gets the configuration flags that determine if the computer serves content to peers and if it can download content from peers. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching-and-help.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching-and-help.md index 7f3ed27179..1bdd4a82c1 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching-and-help.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching-and-help.md @@ -2,8 +2,8 @@ title: bitsadmin peercaching and help description: Reference article for bitsadmin peercaching and help command that displays the command-line usage for the /peercaching switches. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 04/01/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching-and-setconfigurationflags.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching-and-setconfigurationflags.md index 9ab082e3ed..13b680d9f0 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching-and-setconfigurationflags.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching-and-setconfigurationflags.md @@ -2,8 +2,8 @@ title: bitsadmin peercaching and setconfigurationflags description: Reference article for the bitsadmin peercaching and setconfigurationflags command, which sets the configuration flags that determine if the computer can serve content to peers and if it can download content from peers. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching.md index 51b34faad6..95e785651d 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-peercaching.md @@ -2,8 +2,8 @@ title: bitsadmin peercaching description: Reference article for the bitsadmin peercaching command, which lists the /peercaching switches. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # bitsadmin peercaching diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-clear.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-clear.md index d6513d0274..3d3127df6c 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-clear.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-clear.md @@ -2,8 +2,8 @@ title: bitsadmin peers and clear description: Reference article for the bitsadmin peers and clear command that clears the peer list. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 04/01/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-discover.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-discover.md index 963ccf73e9..c43d3b1499 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-discover.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-discover.md @@ -2,8 +2,8 @@ title: bitsadmin peers and discover description: Reference article for the bitsadmin peers and discover command that rediscovers peers. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 01/03/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-help.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-help.md index b9cfa984c7..0d6777e332 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-help.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-help.md @@ -2,8 +2,8 @@ title: bitsadmin peers and help description: Reference article for the bitsadmin peers and help command, which displays the command-line usage for the /peers switches. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-list.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-list.md index dff0150a0e..fb7cdb3176 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-list.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-peers-and-list.md @@ -2,8 +2,8 @@ title: bitsadmin peers and list description: Reference article for the bitsadmin peers and list command that lists all peers. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 04/01/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-peers.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-peers.md index 15ddcee3c0..dd622cdffb 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-peers.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-peers.md @@ -2,8 +2,8 @@ title: bitsadmin peers description: Reference article for the bitsadmin peers command, which lists the /peers switches. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bitsadmin peers diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-rawreturn.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-rawreturn.md index 53e88f1116..8c248d2f1b 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-rawreturn.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-rawreturn.md @@ -2,8 +2,8 @@ title: bitsadmin rawreturn description: Reference article for the bitsadmin rawreturn command that returns data suitable for parsing. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 04/01/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-removeclientcertificate.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-removeclientcertificate.md index 98ed2a7762..086aa94989 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-removeclientcertificate.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-removeclientcertificate.md @@ -2,8 +2,8 @@ title: bitsadmin removeclientcertificate description: Reference article for the bitsadmin removeclientcertificate command, which removes the client certificate from the job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-removecredentials.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-removecredentials.md index c5bf4a1e17..884d0c2b0e 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-removecredentials.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-removecredentials.md @@ -2,8 +2,8 @@ title: bitsadmin removecredentials description: Reference article for the bitsadmin removecredentials command, which removes credentials from a job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-replaceremoteprefix.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-replaceremoteprefix.md index cc381c3952..d085cae279 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-replaceremoteprefix.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-replaceremoteprefix.md @@ -2,8 +2,8 @@ title: bitsadmin replaceremoteprefix description: Reference article for the bitsadmin replaceremoteprefix command, which changes the remote URL for all files in the job from *oldprefix* to *newprefix*, as necessary. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-reset.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-reset.md index e0f17286a6..f863e19c5f 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-reset.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-reset.md @@ -2,8 +2,8 @@ title: bitsadmin reset description: Reference article for the bitsadmin reset command, which cancels all jobs in the transfer queue owned by the current user. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-resume.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-resume.md index a1964b3611..95c3accd66 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-resume.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-resume.md @@ -2,8 +2,8 @@ title: bitsadmin resume description: Reference article for the bitsadmin resume command, which activates a new or suspended job in the transfer queue. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setaclflag.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setaclflag.md index 1a6dc709a0..b9c865f47a 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setaclflag.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setaclflag.md @@ -2,14 +2,14 @@ title: bitsadmin setaclflag description: Reference article for the bitsadmin setaclflag command, which sets the access control list (ACL) propagations flags. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bitsadmin setaclflag -Sets the access control list (ACL) propagations flags for the job. The flags indicate that you want to maintain the owner and ACL information with the file being downloaded. For example, to maintain the owner and group with the file, set the **flags** parameter to `og`. +Sets the access control list (ACL) propagations flags for the job. The flags indicate that you want to maintain the owner and ACL information with the file being downloaded. For example, to maintain the owner and group with the file, set the **flags** parameter to `og`. ## Syntax diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setclientcertificatebyid.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setclientcertificatebyid.md index 9b31b46eb7..aee19443aa 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setclientcertificatebyid.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setclientcertificatebyid.md @@ -2,8 +2,8 @@ title: bitsadmin setclientcertificatebyid description: Reference article for the bitsadmin setclientcertificatebyid command, which specifies the identifier of the client certificate to use for client authentication in an HTTPS (SSL) request ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setclientcertificatebyname.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setclientcertificatebyname.md index 7c4154b4df..0710d3c070 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setclientcertificatebyname.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setclientcertificatebyname.md @@ -2,8 +2,8 @@ title: bitsadmin setclientcertificatebyname description: Reference article for the bitsadmin setclientcertificatebyname command, which specifies the subject name of the client certificate to use for client authentication in an HTTPS (SSL) request. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setcredentials.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setcredentials.md index c97b706feb..40ce074d12 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setcredentials.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setcredentials.md @@ -2,8 +2,8 @@ title: bitsadmin setcredentials description: Reference article for the bitsadmin setcredentials command, which adds credentials to a job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setcustomheaders.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setcustomheaders.md index a061de26b0..9ffb9765db 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setcustomheaders.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setcustomheaders.md @@ -2,8 +2,8 @@ title: bitsadmin setcustomheaders description: Reference article for the bitsadmin setcustomheaders command, which adds a custom HTTP header to a GET request. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setdescription.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setdescription.md index 89cade4b90..9e84a6dc34 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setdescription.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setdescription.md @@ -2,8 +2,8 @@ title: bitsadmin setdescription description: Reference article for the bitsadmin setdescription command, which sets the description of the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setdisplayname.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setdisplayname.md index 55b0ea5665..da20a557a3 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setdisplayname.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setdisplayname.md @@ -2,8 +2,8 @@ title: bitsadmin setdisplayname description: Reference article for the bitsadmin setdisplayname command, which sets the display name of the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-sethelpertoken.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-sethelpertoken.md index 9df6e36a8b..24566d3918 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-sethelpertoken.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-sethelpertoken.md @@ -1,15 +1,15 @@ ---- +--- title: bitsadmin sethelpertoken -description: Reference article for the bitsadmin sethelpertoken command, which sets the current command prompt's primary token (or an arbitrary local user account's token, if specified) as a BITS transfer job's helper token. +description: Reference article for the bitsadmin sethelpertoken command, which sets the current command prompt's primary token (or an arbitrary local user account's token, if specified) as a BITS transfer job's helper token. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 03/01/2019 --- # bitsadmin sethelpertoken -Sets the current command prompt's primary token (or an arbitrary local user account's token, if specified) as a BITS transfer job's [helper token](/windows/win32/bits/helper-tokens-for-bits-transfer-jobs). +Sets the current command prompt's primary token (or an arbitrary local user account's token, if specified) as a BITS transfer job's [helper token](/windows/win32/bits/helper-tokens-for-bits-transfer-jobs). > [!NOTE] > This command isn't supported by BITS 3.0 and earlier. diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-sethelpertokenflags.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-sethelpertokenflags.md index eaa2ba6f8e..64cd6e2361 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-sethelpertokenflags.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-sethelpertokenflags.md @@ -1,15 +1,15 @@ --- title: bitsadmin sethelpertokenflags -description: Reference article for the bitsadmin sethelpertokenflags command, which sets the usage flags for a helper token that is associated with a BITS transfer job. +description: Reference article for the bitsadmin sethelpertokenflags command, which sets the usage flags for a helper token that is associated with a BITS transfer job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 03/01/2019 --- # bitsadmin sethelpertokenflags -Sets the usage flags for a [helper token](/windows/win32/bits/helper-tokens-for-bits-transfer-jobs) that is associated with a BITS transfer job. +Sets the usage flags for a [helper token](/windows/win32/bits/helper-tokens-for-bits-transfer-jobs) that is associated with a BITS transfer job. > [!NOTE] > This command isn't supported by BITS 3.0 and earlier. @@ -25,7 +25,7 @@ bitsadmin /sethelpertokenflags | Parameter | Description | | --------- | ----------- | | job | The job's display name or GUID. | -| flags | Possible helper token values, including:

You must call `/setcredentialsjob targetscheme null null` to send the credentials over HTTP. | +| flags | Possible helper token values, including:You must call `/setcredentialsjob targetscheme null null` to send the credentials over HTTP. | ## Related links diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-sethttpmethod.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-sethttpmethod.md index 070611db03..7208bc8d22 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-sethttpmethod.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-sethttpmethod.md @@ -2,8 +2,8 @@ title: bitsadmin sethttpmethod description: Reference article for the bitsadmin sethttpmethod command, which sets the HTTP verb to use. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 03/01/2019 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setmaxdownloadtime.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setmaxdownloadtime.md index c226aafcf6..355e798549 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setmaxdownloadtime.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setmaxdownloadtime.md @@ -2,8 +2,8 @@ title: bitsadmin setmaxdownloadtime description: Reference article for the bitsadmin setmaxdownloadtime command, which sets the download timeout in seconds. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setminretrydelay.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setminretrydelay.md index 774c4f1ead..f6349256ea 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setminretrydelay.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setminretrydelay.md @@ -2,8 +2,8 @@ title: bitsadmin setminretrydelay description: Reference article for the bitsadmin setminretrydelay command, which sets the minimum length of time, in seconds, that BITS waits after encountering a transient error before trying to transfer the file. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setnoprogresstimeout.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setnoprogresstimeout.md index 39c41288b2..4e4c197e28 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setnoprogresstimeout.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setnoprogresstimeout.md @@ -2,8 +2,8 @@ title: bitsadmin setnoprogresstimeout description: Reference article for the bitsadmin setnoprogresstimeout command, which sets the length of time, in seconds, that the service tries to transfer the file after a transient error occurs. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setnotifycmdline.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setnotifycmdline.md index a68f329c6b..a78463b184 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setnotifycmdline.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setnotifycmdline.md @@ -2,8 +2,8 @@ title: bitsadmin setnotifycmdline description: Reference article for the bitsadmin setnotifycmdline command, which sets the command-line command that will run when the job finishes transferring data, or when a job enters a state. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setnotifyflags.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setnotifyflags.md index 2dd5de0cc1..ae87ec4c57 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setnotifyflags.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setnotifyflags.md @@ -2,8 +2,8 @@ title: bitsadmin setnotifyflags description: Reference article for the bitsadmin setnotifyflags command, which sets the event notification flags for the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setpeercachingflags.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setpeercachingflags.md index 52221eded6..bbe43eea1b 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setpeercachingflags.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setpeercachingflags.md @@ -2,8 +2,8 @@ title: bitsadmin setpeercachingflags description: Reference article for the bitsadmin setpeercachingflags command, which sets flags that determine if the files of the job can be cached and served to peers and if the job can download content from peers. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setpriority.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setpriority.md index 7bc83515ed..4f96a86179 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setpriority.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setpriority.md @@ -2,8 +2,8 @@ title: bitsadmin setpriority description: Reference article for the bitsadmin setpriority command, which sets the priority of the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setproxysettings.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setproxysettings.md index cca4b15628..df9bdc9ab0 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setproxysettings.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setproxysettings.md @@ -2,8 +2,8 @@ title: bitsadmin setproxysettings description: Reference article for the bitsadmin setproxysettings command, which sets the proxy settings for the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- @@ -35,14 +35,14 @@ bitsadmin /setproxysettings myDownloadJob PRECONFIG ``` ``` -bitsadmin /setproxysettings myDownloadJob NO_PROXY +bitsadmin /setproxysettings myDownloadJob NO_PROXY ``` ``` -bitsadmin /setproxysettings myDownloadJob OVERRIDE proxy1:80 +bitsadmin /setproxysettings myDownloadJob OVERRIDE proxy1:80 ``` ``` -bitsadmin /setproxysettings myDownloadJob OVERRIDE proxy1,proxy2,proxy3 NULL +bitsadmin /setproxysettings myDownloadJob OVERRIDE proxy1,proxy2,proxy3 NULL ``` ## Related links diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setreplyfilename.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setreplyfilename.md index d7558f74fa..dd5739a337 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setreplyfilename.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setreplyfilename.md @@ -2,8 +2,8 @@ title: bitsadmin setreplyfilename description: Reference article for the bitsadmin setreplyfilename command, which specifies the path of the file that contains the server upload-reply. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setsecurityflags.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setsecurityflags.md index 8bddfae24c..3d9ff6d6e6 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setsecurityflags.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setsecurityflags.md @@ -2,8 +2,8 @@ title: bitsadmin setsecurityflags description: Reference article for the bitsadmin setsecurityflags command, which sets security flags for HTTP to determine if BITS should check the certificate revocation list, ignore certain certificate errors, and define the policy to use when a server redirects the HTTP request. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-setvalidationstate.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-setvalidationstate.md index 674e2e6d92..a13c5a0aa9 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-setvalidationstate.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-setvalidationstate.md @@ -2,8 +2,8 @@ title: bitsadmin setvalidationstate description: Reference article for the bitsadmin setvalidationstate command, which sets the content validation state of the given file within the job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-suspend.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-suspend.md index 557b09385e..c85a667ffc 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-suspend.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-suspend.md @@ -2,8 +2,8 @@ title: bitsadmin suspend description: Reference article for the bitsadmin suspend command, which suspends the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bitsadmin suspend diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-takeownership.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-takeownership.md index 419a272047..b3aa260802 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-takeownership.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-takeownership.md @@ -2,8 +2,8 @@ title: bitsadmin takeownership description: Reference article for the bitsadmin takeownership command, which lets a user with administrative privileges take ownership of the specified job. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-transfer.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-transfer.md index 7f68a55cee..27fb370208 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-transfer.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-transfer.md @@ -2,8 +2,8 @@ title: bitsadmin transfer description: Reference article for the bitsadmin transfer command, which transfers one or more files. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-enableanalyticchannel.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-enableanalyticchannel.md index 12a7b4df40..d323d2e7fc 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-enableanalyticchannel.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-enableanalyticchannel.md @@ -2,8 +2,8 @@ title: bitsadmin util and enableanalyticchannel description: Reference article for the bitsadmin util and enableanalyticchannel command, which enables or disables the BITS client analytic channel. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-getieproxy.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-getieproxy.md index bb2c3bb7c6..7eea50d791 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-getieproxy.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-getieproxy.md @@ -2,8 +2,8 @@ title: bitsadmin util and getieproxy description: Reference article for the bitsadmin util and getieproxy command, which retrieves the proxy usage for the given service account. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # bitsadmin util and getieproxy diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-help.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-help.md index d604d49015..d695f4ed40 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-help.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-help.md @@ -2,8 +2,8 @@ title: bitsadmin util and help description: Reference article for the bitsadmin util and help command that displays the command-line usage for the /util switches. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 04/01/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-repairservice.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-repairservice.md index 0490763315..6120269a43 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-repairservice.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-repairservice.md @@ -2,8 +2,8 @@ title: bitsadmin util and repairservice description: Reference article for the bitsadmin util and repairservice command, which fixes known issues in various versions of BITS service. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-setieproxy.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-setieproxy.md index 5cade23b4f..b25e207b9e 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-setieproxy.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-setieproxy.md @@ -2,8 +2,8 @@ title: bitsadmin util and setieproxy description: Reference article for the bitsadmin util and setieproxy command, which sets the proxy settings to use when transferring files using a service account. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- @@ -41,11 +41,11 @@ bitsadmin /util /setieproxy localsystem AUTODETECT ``` ``` -bitsadmin /util /setieproxy localsystem MANUAL_PROXY proxy1,proxy2,proxy3 NULL +bitsadmin /util /setieproxy localsystem MANUAL_PROXY proxy1,proxy2,proxy3 NULL ``` ``` -bitsadmin /util /setieproxy localsystem MANUAL_PROXY proxy1:80 +bitsadmin /util /setieproxy localsystem MANUAL_PROXY proxy1:80 ``` ## Related links diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-version.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-version.md index a8119538be..1c13158d5f 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-version.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-util-and-version.md @@ -2,8 +2,8 @@ title: bitsadmin util and version description: Reference article for the bitsadmin util and version command, which displays the version of BITS service. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-util.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-util.md index 45a8002af5..e213dd8e2a 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-util.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-util.md @@ -2,8 +2,8 @@ title: bitsadmin util description: Reference article for the bitsadmin util command, which lists the Util switches. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bitsadmin util @@ -28,7 +28,7 @@ bitsadmin /util /version | Parameter | Description | | --------- | ----------- | -| [bitsadmin util and help](bitsadmin-util-and-help.md) | Displays the command-line usage for the /Util switches. You can also specify /?. | +| [bitsadmin util and help](bitsadmin-util-and-help.md) | Displays the command-line usage for the /Util switches. You can also specify /?. | | [bitsadmin util and getieproxy](bitsadmin-util-and-getieproxy.md) | Retrieves the proxy usage for the given service account. | | [bitsadmin util and repairservice](bitsadmin-util-and-repairservice.md) | Repairs known issues with BITS service. | | [bitsadmin util and setieproxy](bitsadmin-util-and-setieproxy.md) | Specifies proxy settings to use when transferring files using a service account. | diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin-wrap.md b/WindowsServerDocs/administration/windows-commands/bitsadmin-wrap.md index 5e6609da91..3ac68da326 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin-wrap.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin-wrap.md @@ -2,8 +2,8 @@ title: bitsadmin wrap description: Reference article for the bitsadmin wrap command, which wraps any line of output text extending beyond the rightmost edge of the command window to the next line. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bitsadmin wrap diff --git a/WindowsServerDocs/administration/windows-commands/bitsadmin.md b/WindowsServerDocs/administration/windows-commands/bitsadmin.md index ed40007665..c642ce9d85 100644 --- a/WindowsServerDocs/administration/windows-commands/bitsadmin.md +++ b/WindowsServerDocs/administration/windows-commands/bitsadmin.md @@ -2,8 +2,8 @@ title: bitsadmin description: Reference article for the bitsadmin command, which is a command-line tool used to create, download, or upload jobs and monitor their progress. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bitsadmin diff --git a/WindowsServerDocs/administration/windows-commands/bootcfg-addsw.md b/WindowsServerDocs/administration/windows-commands/bootcfg-addsw.md index 525700492d..d83941f87f 100644 --- a/WindowsServerDocs/administration/windows-commands/bootcfg-addsw.md +++ b/WindowsServerDocs/administration/windows-commands/bootcfg-addsw.md @@ -2,8 +2,8 @@ title: bootcfg addsw description: Reference article for the bootcfg addsw command, which adds operating system load options for a specified operating system entry. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bootcfg addsw diff --git a/WindowsServerDocs/administration/windows-commands/bootcfg-copy.md b/WindowsServerDocs/administration/windows-commands/bootcfg-copy.md index 2df32f2cd4..6c9db9e440 100644 --- a/WindowsServerDocs/administration/windows-commands/bootcfg-copy.md +++ b/WindowsServerDocs/administration/windows-commands/bootcfg-copy.md @@ -2,8 +2,8 @@ title: bootcfg copy description: Reference article for the bootcfg copy command, which makes a copy of an existing boot entry, to which you can add command-line options. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bootcfg copy diff --git a/WindowsServerDocs/administration/windows-commands/bootcfg-dbg1394.md b/WindowsServerDocs/administration/windows-commands/bootcfg-dbg1394.md index b53357a5cd..fed4c4f1f6 100644 --- a/WindowsServerDocs/administration/windows-commands/bootcfg-dbg1394.md +++ b/WindowsServerDocs/administration/windows-commands/bootcfg-dbg1394.md @@ -2,8 +2,8 @@ title: bootcfg dbg1394 description: Reference article for the bootcfg dbg1394 command, which configures 1394 port debugging for a specified operating system entry ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # bootcfg dbg1394 diff --git a/WindowsServerDocs/administration/windows-commands/bootcfg-debug.md b/WindowsServerDocs/administration/windows-commands/bootcfg-debug.md index cd3b1d5664..bcbdd0748a 100644 --- a/WindowsServerDocs/administration/windows-commands/bootcfg-debug.md +++ b/WindowsServerDocs/administration/windows-commands/bootcfg-debug.md @@ -2,8 +2,8 @@ title: bootcfg debug description: Reference article for the bootcfg debug command, which adds or changes the debug settings for a specified operating system entry. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # bootcfg debug diff --git a/WindowsServerDocs/administration/windows-commands/bootcfg-default.md b/WindowsServerDocs/administration/windows-commands/bootcfg-default.md index ad74540932..08f8afaf00 100644 --- a/WindowsServerDocs/administration/windows-commands/bootcfg-default.md +++ b/WindowsServerDocs/administration/windows-commands/bootcfg-default.md @@ -2,8 +2,8 @@ title: bootcfg default description: Reference article for the bootcfg default command, which specifies the operating system entry to designate as the default. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bootcfg default diff --git a/WindowsServerDocs/administration/windows-commands/bootcfg-delete.md b/WindowsServerDocs/administration/windows-commands/bootcfg-delete.md index 1b38c719d4..52770c6884 100644 --- a/WindowsServerDocs/administration/windows-commands/bootcfg-delete.md +++ b/WindowsServerDocs/administration/windows-commands/bootcfg-delete.md @@ -2,8 +2,8 @@ title: bootcfg delete description: Reference article for the bootcfg delete command, which deletes an operating system entry in the operating systems section of the Boot.ini file. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bootcfg delete diff --git a/WindowsServerDocs/administration/windows-commands/bootcfg-ems.md b/WindowsServerDocs/administration/windows-commands/bootcfg-ems.md index afd5acc580..52b9460aa2 100644 --- a/WindowsServerDocs/administration/windows-commands/bootcfg-ems.md +++ b/WindowsServerDocs/administration/windows-commands/bootcfg-ems.md @@ -2,8 +2,8 @@ title: bootcfg ems description: Reference article for the bootcfg ems command, which enables the user to add or change the settings for redirection of the Emergency Management Services console to a remote computer. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # bootcfg ems diff --git a/WindowsServerDocs/administration/windows-commands/bootcfg-query.md b/WindowsServerDocs/administration/windows-commands/bootcfg-query.md index 72103431c3..b2a7b0816b 100644 --- a/WindowsServerDocs/administration/windows-commands/bootcfg-query.md +++ b/WindowsServerDocs/administration/windows-commands/bootcfg-query.md @@ -2,8 +2,8 @@ title: bootcfg query description: Reference article for the bootcfg query command, which queries and displays the boot loader and operating system section entries from Boot.ini. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bootcfg query diff --git a/WindowsServerDocs/administration/windows-commands/bootcfg-raw.md b/WindowsServerDocs/administration/windows-commands/bootcfg-raw.md index 10cc36a652..d1e45f7709 100644 --- a/WindowsServerDocs/administration/windows-commands/bootcfg-raw.md +++ b/WindowsServerDocs/administration/windows-commands/bootcfg-raw.md @@ -2,8 +2,8 @@ title: bootcfg raw description: Reference article for the bootcfg raw command, which adds operating system load options, specified as a string, to an operating system entry in the operating system section of the Boot.ini file. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # bootcfg raw diff --git a/WindowsServerDocs/administration/windows-commands/bootcfg-rmsw.md b/WindowsServerDocs/administration/windows-commands/bootcfg-rmsw.md index a0ae9d6ca3..bdc1475bc6 100644 --- a/WindowsServerDocs/administration/windows-commands/bootcfg-rmsw.md +++ b/WindowsServerDocs/administration/windows-commands/bootcfg-rmsw.md @@ -2,8 +2,8 @@ title: bootcfg rmsw description: Reference article for the bootcfg rmsw command, which removes operating system load options for a specified operating system entry. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # bootcfg rmsw diff --git a/WindowsServerDocs/administration/windows-commands/bootcfg-timeout.md b/WindowsServerDocs/administration/windows-commands/bootcfg-timeout.md index e597668c91..5011a1fe59 100644 --- a/WindowsServerDocs/administration/windows-commands/bootcfg-timeout.md +++ b/WindowsServerDocs/administration/windows-commands/bootcfg-timeout.md @@ -2,8 +2,8 @@ title: bootcfg timeout description: Reference article for the bootcfg timeout command, which changes the operating system time-out value. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # bootcfg timeout diff --git a/WindowsServerDocs/administration/windows-commands/bootcfg.md b/WindowsServerDocs/administration/windows-commands/bootcfg.md index 2be3c8af20..9002fab155 100644 --- a/WindowsServerDocs/administration/windows-commands/bootcfg.md +++ b/WindowsServerDocs/administration/windows-commands/bootcfg.md @@ -2,8 +2,8 @@ title: bootcfg description: Reference article for the bootcfg command, which configures, queries, or changes Boot.ini file settings. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/break.md b/WindowsServerDocs/administration/windows-commands/break.md index dcdb3f62c2..c359e56485 100644 --- a/WindowsServerDocs/administration/windows-commands/break.md +++ b/WindowsServerDocs/administration/windows-commands/break.md @@ -2,8 +2,8 @@ title: break description: Reference article for the break command, which breaks the mirrored volume with focus into two simple volumes. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 no-loc: [break] --- diff --git a/WindowsServerDocs/administration/windows-commands/break_2.md b/WindowsServerDocs/administration/windows-commands/break_2.md index 1fbaf3c357..286ca780c7 100644 --- a/WindowsServerDocs/administration/windows-commands/break_2.md +++ b/WindowsServerDocs/administration/windows-commands/break_2.md @@ -2,8 +2,8 @@ title: break (diskshadow) description: Reference article for the break command, which disassociates a shadow copy volume from VSS and makes it accessible as a regular volume. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/12/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/cacls.md b/WindowsServerDocs/administration/windows-commands/cacls.md index 8fef1c3d2f..ced90eeff3 100644 --- a/WindowsServerDocs/administration/windows-commands/cacls.md +++ b/WindowsServerDocs/administration/windows-commands/cacls.md @@ -2,8 +2,8 @@ title: cacls description: Reference article for the cacls command. This command has been deprecated and isn't guaranteed to be supported in future releases of Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/call.md b/WindowsServerDocs/administration/windows-commands/call.md index 9dfd6d05cf..0766d2511c 100644 --- a/WindowsServerDocs/administration/windows-commands/call.md +++ b/WindowsServerDocs/administration/windows-commands/call.md @@ -2,8 +2,8 @@ title: call description: Reference article for the call command, which calls one batch program from another without stopping the parent batch program. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/28/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/cd.md b/WindowsServerDocs/administration/windows-commands/cd.md index fca03a85d6..27830c4a99 100644 --- a/WindowsServerDocs/administration/windows-commands/cd.md +++ b/WindowsServerDocs/administration/windows-commands/cd.md @@ -2,8 +2,8 @@ title: cd description: Reference article for the cd command, which displays the name of or changes the current directory. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/certreq_1.md b/WindowsServerDocs/administration/windows-commands/certreq_1.md index 9c527a7a84..5a44ee7f54 100644 --- a/WindowsServerDocs/administration/windows-commands/certreq_1.md +++ b/WindowsServerDocs/administration/windows-commands/certreq_1.md @@ -2,8 +2,8 @@ title: certreq description: Reference article for the certreq command, which requests certificates from a certification authority (CA), retrieves a response to a previous request from a CA, creates a new request from an .inf file, accepts and installs a response to a request, constructs a cross-certification or qualified subordination request from an existing CA certificate or request, and signs a cross-certification or qualified subordination request. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 09/02/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/certutil.md b/WindowsServerDocs/administration/windows-commands/certutil.md index 8c65cefc54..2a8e87647d 100644 --- a/WindowsServerDocs/administration/windows-commands/certutil.md +++ b/WindowsServerDocs/administration/windows-commands/certutil.md @@ -2,8 +2,8 @@ title: certutil description: Learn about certutil, a command-line program that displays CA configuration information, configures Certificate Services, and backs up and restores CA components in Windows. ms.topic: reference -author: xelu86 -ms.author: alalve +author: robinharwood +ms.author: roharwoo ms.date: 05/01/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/change-logon.md b/WindowsServerDocs/administration/windows-commands/change-logon.md index 3afd7119fc..d8a08bb88d 100644 --- a/WindowsServerDocs/administration/windows-commands/change-logon.md +++ b/WindowsServerDocs/administration/windows-commands/change-logon.md @@ -2,8 +2,8 @@ title: change logon description: Reference article for the change logon command, which enables or disables logons from client sessions, or displays current logon status. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/change-port.md b/WindowsServerDocs/administration/windows-commands/change-port.md index a32c7a6034..faeb1a1c48 100644 --- a/WindowsServerDocs/administration/windows-commands/change-port.md +++ b/WindowsServerDocs/administration/windows-commands/change-port.md @@ -2,8 +2,8 @@ title: change port description: Reference article for the change port command, which lists or changes the COM port mappings to be compatible with MS-DOS applications. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/change-user.md b/WindowsServerDocs/administration/windows-commands/change-user.md index 34a5c93f2d..d7621688a4 100644 --- a/WindowsServerDocs/administration/windows-commands/change-user.md +++ b/WindowsServerDocs/administration/windows-commands/change-user.md @@ -2,8 +2,8 @@ title: change user description: Reference article for the change user command, which changes the install mode for the Remote Desktop Session Host server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # change user diff --git a/WindowsServerDocs/administration/windows-commands/change.md b/WindowsServerDocs/administration/windows-commands/change.md index 0ef3c7bd3d..7acf063435 100644 --- a/WindowsServerDocs/administration/windows-commands/change.md +++ b/WindowsServerDocs/administration/windows-commands/change.md @@ -2,8 +2,8 @@ title: change description: Reference article for the change command, which changes Remote Desktop Session Host server settings for logons, COM port mappings, and install mode. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/chcp.md b/WindowsServerDocs/administration/windows-commands/chcp.md index 0b5d368d71..e494c8ae69 100644 --- a/WindowsServerDocs/administration/windows-commands/chcp.md +++ b/WindowsServerDocs/administration/windows-commands/chcp.md @@ -2,8 +2,8 @@ title: chcp description: Reference article for the chcp command, which changes the active console code page. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/chdir.md b/WindowsServerDocs/administration/windows-commands/chdir.md index 5420056971..661f4cf4be 100644 --- a/WindowsServerDocs/administration/windows-commands/chdir.md +++ b/WindowsServerDocs/administration/windows-commands/chdir.md @@ -2,8 +2,8 @@ title: chdir description: Reference article for the chdir command, which performs the same actions as the cd command. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # chdir diff --git a/WindowsServerDocs/administration/windows-commands/chglogon.md b/WindowsServerDocs/administration/windows-commands/chglogon.md index d47015c9c3..36c835cafc 100644 --- a/WindowsServerDocs/administration/windows-commands/chglogon.md +++ b/WindowsServerDocs/administration/windows-commands/chglogon.md @@ -3,8 +3,8 @@ title: chglogon description: Reference article for the chglogon command, which enables or disables logons from client sessions on an Remote Desktop Session Host server, or displays current logon status. ms.topic: reference ms.date: 10/16/2017 -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood --- # chglogon diff --git a/WindowsServerDocs/administration/windows-commands/chgport.md b/WindowsServerDocs/administration/windows-commands/chgport.md index 13e454e6a0..27941985eb 100644 --- a/WindowsServerDocs/administration/windows-commands/chgport.md +++ b/WindowsServerDocs/administration/windows-commands/chgport.md @@ -2,8 +2,8 @@ title: chgport description: Reference article for the chgport command, which lists or changes the COM port mappings to be compatible with MS-DOS applications. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # chgport diff --git a/WindowsServerDocs/administration/windows-commands/chgusr.md b/WindowsServerDocs/administration/windows-commands/chgusr.md index c3b9137e06..4a7db618d9 100644 --- a/WindowsServerDocs/administration/windows-commands/chgusr.md +++ b/WindowsServerDocs/administration/windows-commands/chgusr.md @@ -2,8 +2,8 @@ title: chgusr description: Reference article for the chgusr command, which changes the install mode for the Remote Desktop Session Host server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # chgusr diff --git a/WindowsServerDocs/administration/windows-commands/chkdsk.md b/WindowsServerDocs/administration/windows-commands/chkdsk.md index 08b06f6b1d..cf566370d9 100644 --- a/WindowsServerDocs/administration/windows-commands/chkdsk.md +++ b/WindowsServerDocs/administration/windows-commands/chkdsk.md @@ -2,8 +2,8 @@ title: chkdsk description: Reference article for the chkdsk command, which checks the file system and file system metadata of a volume for logical and physical errors. ms.topic: reference -author: xelu86 -ms.author: alalve +author: dknappettmsft +ms.author: daknappe ms.date: 05/23/2025 --- @@ -103,7 +103,7 @@ chkdsk [[[]]] [/f] [/v] [/r] [/x] [/i] [/c] [/l[:] - The physical head must move to each data location being checked, which is **slower** due to mechanical movement. - Checking for *bad sectors* (with `/r`) takes longer as every sector's physical integrity is checked and bad ones are replaced if possible. - - High-hour runtimes aren’t uncommon for large drives. + - High-hour runtimes aren't uncommon for large drives. Normally, on large capacity HDDs, `/r` or `/b` would take a considerable amount of time as it reads every sector. Even without errors and with a mostly empty drive, the physical read speed bottlenecks the process. @@ -122,7 +122,7 @@ Viewing the `chkdsk` logs might point to a potential issue during scans. To lear - **When chkdsk runs:** - - **No seek time:** Reading any sector is equally fast; there’s no mechanical latency. + - **No seek time:** Reading any sector is equally fast; there's no mechanical latency. - Checking for *bad sectors* (with `/r`) is faster but still requires reading **every single sector**. However, NAND flash can read much **faster** than an HDD can. - Marking *clusters bad* is logical, not physical remapping. @@ -132,7 +132,7 @@ There might be cases where on large capacity SSDs where `chkdsk` might complete - The `chkdsk` operation didn't actually scan every sector on the drive. - The SSD didn't have much data to process (more free space). -- The SSD scanned is an NVMe that isn’t heavily fragmented. +- The SSD scanned is an NVMe that isn't heavily fragmented. - The SSD might internally optimize "full scans" efficiently, thus further improving scan speed. Viewing the `chkdsk` logs might point to a potential issue during scans. To learn more, see [Viewing chkdsk logs](#viewing-chkdsk-logs). diff --git a/WindowsServerDocs/administration/windows-commands/chkntfs.md b/WindowsServerDocs/administration/windows-commands/chkntfs.md index 5b7dab8ee7..e2245eb48e 100644 --- a/WindowsServerDocs/administration/windows-commands/chkntfs.md +++ b/WindowsServerDocs/administration/windows-commands/chkntfs.md @@ -2,8 +2,8 @@ title: chkntfs description: Reference article for the chkntfs command, which displays or modifies automatic disk checking when the computer is started. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/choice.md b/WindowsServerDocs/administration/windows-commands/choice.md index 253e32547b..7d5ce0dfa4 100644 --- a/WindowsServerDocs/administration/windows-commands/choice.md +++ b/WindowsServerDocs/administration/windows-commands/choice.md @@ -2,8 +2,8 @@ title: choice description: Reference article for the choice command, which prompts the user to select one item from a list of single-character choices in a batch program, and then returns the index of the selected choice. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/cipher.md b/WindowsServerDocs/administration/windows-commands/cipher.md index 59744cef3c..3ea4246e3b 100644 --- a/WindowsServerDocs/administration/windows-commands/cipher.md +++ b/WindowsServerDocs/administration/windows-commands/cipher.md @@ -2,8 +2,8 @@ title: cipher description: Reference article for the cipher command, which displays or alters the encryption of directories and files on NTFS volumes. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 no-loc: [cipher] --- diff --git a/WindowsServerDocs/administration/windows-commands/clean.md b/WindowsServerDocs/administration/windows-commands/clean.md index 83723b2a53..95ff5a427a 100644 --- a/WindowsServerDocs/administration/windows-commands/clean.md +++ b/WindowsServerDocs/administration/windows-commands/clean.md @@ -2,8 +2,8 @@ title: clean description: Reference article for the Diskpart clean command, which removes all partitions or volume formatting from the disk with focus. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/cleanmgr.md b/WindowsServerDocs/administration/windows-commands/cleanmgr.md index aa8bd48b94..bd0412db61 100644 --- a/WindowsServerDocs/administration/windows-commands/cleanmgr.md +++ b/WindowsServerDocs/administration/windows-commands/cleanmgr.md @@ -2,8 +2,8 @@ title: cleanmgr description: Configure the Disk Cleanup tool (Cleanmgr.exe) to automatically clean up certain files. ms.reviewer: cosmosdarwin -author: xelu86 -ms.author: alalve +author: robinharwood +ms.author: roharwoo ms.date: 01/18/2024 ms.topic: reference --- diff --git a/WindowsServerDocs/administration/windows-commands/clip.md b/WindowsServerDocs/administration/windows-commands/clip.md index 10c3b0fc2c..e34c5fccfa 100644 --- a/WindowsServerDocs/administration/windows-commands/clip.md +++ b/WindowsServerDocs/administration/windows-commands/clip.md @@ -2,8 +2,8 @@ title: clip description: Reference article for the clip command, which redirects the command output from the command line to the Windows clipboard. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft no-loc: [clip] ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/cls.md b/WindowsServerDocs/administration/windows-commands/cls.md index 679ce5c8aa..d6cd72e89d 100644 --- a/WindowsServerDocs/administration/windows-commands/cls.md +++ b/WindowsServerDocs/administration/windows-commands/cls.md @@ -2,8 +2,8 @@ title: cls description: Reference article for the cls command, which clears the Command Prompt window. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/cmd.md b/WindowsServerDocs/administration/windows-commands/cmd.md index b97b878a31..b9cada4217 100644 --- a/WindowsServerDocs/administration/windows-commands/cmd.md +++ b/WindowsServerDocs/administration/windows-commands/cmd.md @@ -2,8 +2,8 @@ title: cmd description: Reference article for the cmd command, which starts a new instance of the command interpreter. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 05/23/2025 --- @@ -133,7 +133,7 @@ The following table lists valid hexadecimal digits that you can use as the value - **HKEY_CURRENT_USER\Software\Microsoft\Command Processor\EnableExtensions\REG_DWORD** - Set the **REG_DWORD** value to either **0×1** (enabled) or **0×0** (disabled) in the registry by using Regedit.exe. User-specified settings take precedence over computer settings, and command-line options take precedence over registry settings. + Set the **REG_DWORD** value to either **0x1** (enabled) or **0x0** (disabled) in the registry by using Regedit.exe. User-specified settings take precedence over computer settings, and command-line options take precedence over registry settings. > [!CAUTION] > Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data on the computer. @@ -173,7 +173,7 @@ The following table lists valid hexadecimal digits that you can use as the value - **HKEY_CURRENT_USER\Software\Microsoft\Command Processor\PathCompletionChar\REG_DWORD** - To set the **REG_DWORD** value, run Regedit.exe and use the hexadecimal value of a control character for a particular function (for example, **0×9** is TAB and **0×08** is BACKSPACE). Use the [**0×20**] value for white space, because it isn't a valid control character. User-specified settings take precedence over computer settings, and command-line options take precedence over registry settings. + To set the **REG_DWORD** value, run Regedit.exe and use the hexadecimal value of a control character for a particular function (for example, **0x9** is TAB and **0x08** is BACKSPACE). Use the [**0x20**] value for white space, because it isn't a valid control character. User-specified settings take precedence over computer settings, and command-line options take precedence over registry settings. > [!CAUTION] > Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data on the computer. diff --git a/WindowsServerDocs/administration/windows-commands/cmdkey.md b/WindowsServerDocs/administration/windows-commands/cmdkey.md index b188a5d975..9959c0fe04 100644 --- a/WindowsServerDocs/administration/windows-commands/cmdkey.md +++ b/WindowsServerDocs/administration/windows-commands/cmdkey.md @@ -2,8 +2,8 @@ title: cmdkey description: Reference article for the cmdkey command, which creates, lists, and deletes stored user names and passwords or credentials. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # cmdkey diff --git a/WindowsServerDocs/administration/windows-commands/cmstp.md b/WindowsServerDocs/administration/windows-commands/cmstp.md index e226130fe1..800429e137 100644 --- a/WindowsServerDocs/administration/windows-commands/cmstp.md +++ b/WindowsServerDocs/administration/windows-commands/cmstp.md @@ -2,8 +2,8 @@ title: cmstp description: Reference article for cmstp, which installs or removes a Connection Manager service profile. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/color.md b/WindowsServerDocs/administration/windows-commands/color.md index c3956f1004..29bb4c3d69 100644 --- a/WindowsServerDocs/administration/windows-commands/color.md +++ b/WindowsServerDocs/administration/windows-commands/color.md @@ -2,8 +2,8 @@ title: color description: Reference article for the color command, which changes the foreground and background colors in the Command Prompt window for the current session. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 09/19/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/command-line-syntax-key.md b/WindowsServerDocs/administration/windows-commands/command-line-syntax-key.md index d3dad7638f..201ea7fa00 100644 --- a/WindowsServerDocs/administration/windows-commands/command-line-syntax-key.md +++ b/WindowsServerDocs/administration/windows-commands/command-line-syntax-key.md @@ -2,8 +2,8 @@ title: Command-line syntax key description: Reference article for the command-line syntax key, which describes the notation used to indicate command-line syntax. ms.topic: reference -author: xelu86 -ms.author: alalve +author: robinharwood +ms.author: roharwoo ms.date: 09/08/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/commands-by-server-role.md b/WindowsServerDocs/administration/windows-commands/commands-by-server-role.md index dae7f707fb..21d68e4b87 100644 --- a/WindowsServerDocs/administration/windows-commands/commands-by-server-role.md +++ b/WindowsServerDocs/administration/windows-commands/commands-by-server-role.md @@ -2,8 +2,8 @@ title: Commands by Server role description: Reference article for Commands by Server role, which describes the primary function of the server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # Commands by Server role diff --git a/WindowsServerDocs/administration/windows-commands/comp.md b/WindowsServerDocs/administration/windows-commands/comp.md index dbc9aa19f4..fd26462934 100644 --- a/WindowsServerDocs/administration/windows-commands/comp.md +++ b/WindowsServerDocs/administration/windows-commands/comp.md @@ -2,8 +2,8 @@ title: comp description: Reference article for the comp command, which compares the contents of two files or sets of files byte-by-byte. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/compact-vdisk.md b/WindowsServerDocs/administration/windows-commands/compact-vdisk.md index d51d394758..d4b7355964 100644 --- a/WindowsServerDocs/administration/windows-commands/compact-vdisk.md +++ b/WindowsServerDocs/administration/windows-commands/compact-vdisk.md @@ -2,8 +2,8 @@ title: compact vdisk description: Reference article for the compact vdisk command, which reduces the physical size of a dynamically expanding virtual hard disk (VHD) file. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # compact vdisk diff --git a/WindowsServerDocs/administration/windows-commands/compact.md b/WindowsServerDocs/administration/windows-commands/compact.md index b436792d05..0ee4de5e98 100644 --- a/WindowsServerDocs/administration/windows-commands/compact.md +++ b/WindowsServerDocs/administration/windows-commands/compact.md @@ -2,8 +2,8 @@ title: compact description: Reference article for the compact command, which displays or alters the compression of files or directories on NTFS partitions. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/convert-basic.md b/WindowsServerDocs/administration/windows-commands/convert-basic.md index 7994c6a73e..c8be7ee0eb 100644 --- a/WindowsServerDocs/administration/windows-commands/convert-basic.md +++ b/WindowsServerDocs/administration/windows-commands/convert-basic.md @@ -2,8 +2,8 @@ title: convert basic description: Reference article for the convert basic command, which converts an empty dynamic disk to a basic disk. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/convert-dynamic.md b/WindowsServerDocs/administration/windows-commands/convert-dynamic.md index db36ee2a06..59a5c067c8 100644 --- a/WindowsServerDocs/administration/windows-commands/convert-dynamic.md +++ b/WindowsServerDocs/administration/windows-commands/convert-dynamic.md @@ -2,8 +2,8 @@ title: convert dynamic description: Reference article for the convert dynamic command, which converts a basic disk into a dynamic disk. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/convert-gpt.md b/WindowsServerDocs/administration/windows-commands/convert-gpt.md index 37faca621a..c148f66c98 100644 --- a/WindowsServerDocs/administration/windows-commands/convert-gpt.md +++ b/WindowsServerDocs/administration/windows-commands/convert-gpt.md @@ -2,8 +2,8 @@ title: convert gpt description: Reference article for the convert gpt command, which converts an empty basic disk with the master boot record (MBR) partition style into a basic disk with the GUID partition table (GPT) partition style. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/convert-mbr.md b/WindowsServerDocs/administration/windows-commands/convert-mbr.md index 1cd7619c18..312225e3fd 100644 --- a/WindowsServerDocs/administration/windows-commands/convert-mbr.md +++ b/WindowsServerDocs/administration/windows-commands/convert-mbr.md @@ -2,8 +2,8 @@ title: convert mbr description: Reference article for the convert mbr command, which converts an empty basic disk with the GUID Partition Table (GPT) partition style into a basic disk with the master boot record (MBR) partition style. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/convert.md b/WindowsServerDocs/administration/windows-commands/convert.md index 5f9ef5d986..7c99529e9f 100644 --- a/WindowsServerDocs/administration/windows-commands/convert.md +++ b/WindowsServerDocs/administration/windows-commands/convert.md @@ -2,8 +2,8 @@ title: convert description: Reference article for the convert command, which converts a disk from one disk type to another. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/copy.md b/WindowsServerDocs/administration/windows-commands/copy.md index 10d9e85443..aeaccd5a58 100644 --- a/WindowsServerDocs/administration/windows-commands/copy.md +++ b/WindowsServerDocs/administration/windows-commands/copy.md @@ -2,8 +2,8 @@ title: copy description: Reference article for the copy command, which copies one or more files from one location to another. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/create-partition-efi.md b/WindowsServerDocs/administration/windows-commands/create-partition-efi.md index f8be6fc32d..8ef370f4cb 100644 --- a/WindowsServerDocs/administration/windows-commands/create-partition-efi.md +++ b/WindowsServerDocs/administration/windows-commands/create-partition-efi.md @@ -2,8 +2,8 @@ title: create partition efi description: Reference article for the create partition efi command, which creates an Extensible Firmware Interface (EFI) system partition on a GUID Partition Table (gpt) disk on Itanium-based computers. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/create-partition-extended.md b/WindowsServerDocs/administration/windows-commands/create-partition-extended.md index 7b52a75160..d2e819a84d 100644 --- a/WindowsServerDocs/administration/windows-commands/create-partition-extended.md +++ b/WindowsServerDocs/administration/windows-commands/create-partition-extended.md @@ -2,8 +2,8 @@ title: create partition extended description: Reference article for the create partition extended command, which creates an extended partition on the disk with focus. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/create-partition-logical.md b/WindowsServerDocs/administration/windows-commands/create-partition-logical.md index 075b8e7162..c98c861f7d 100644 --- a/WindowsServerDocs/administration/windows-commands/create-partition-logical.md +++ b/WindowsServerDocs/administration/windows-commands/create-partition-logical.md @@ -2,8 +2,8 @@ title: create partition logical description: Reference article for the create partition logical command, which creates a logical partition in an existing extended partition. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/create-partition-msr.md b/WindowsServerDocs/administration/windows-commands/create-partition-msr.md index f841c7a240..394380fee5 100644 --- a/WindowsServerDocs/administration/windows-commands/create-partition-msr.md +++ b/WindowsServerDocs/administration/windows-commands/create-partition-msr.md @@ -2,8 +2,8 @@ title: create partition msr description: Reference article for create partition msr, which creates a Microsoft Reserved (MSR) partition on a GUID partition table (gpt) disk. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/create-partition-primary.md b/WindowsServerDocs/administration/windows-commands/create-partition-primary.md index 11ae27ecab..4bb8a0718b 100644 --- a/WindowsServerDocs/administration/windows-commands/create-partition-primary.md +++ b/WindowsServerDocs/administration/windows-commands/create-partition-primary.md @@ -2,8 +2,8 @@ title: create partition primary description: Reference article for the create partition primary command, which creates a primary partition on the basic disk with focus. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # create partition primary diff --git a/WindowsServerDocs/administration/windows-commands/create-volume-mirror.md b/WindowsServerDocs/administration/windows-commands/create-volume-mirror.md index c8b2ed4ab6..6581be733e 100644 --- a/WindowsServerDocs/administration/windows-commands/create-volume-mirror.md +++ b/WindowsServerDocs/administration/windows-commands/create-volume-mirror.md @@ -2,8 +2,8 @@ title: create volume mirror description: Reference article for the create volume mirror command, which creates a volume mirror by using the two specified dynamic disks. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # create volume mirror diff --git a/WindowsServerDocs/administration/windows-commands/create-volume-raid.md b/WindowsServerDocs/administration/windows-commands/create-volume-raid.md index 0b7d11781d..83a3c72b25 100644 --- a/WindowsServerDocs/administration/windows-commands/create-volume-raid.md +++ b/WindowsServerDocs/administration/windows-commands/create-volume-raid.md @@ -2,8 +2,8 @@ title: create volume raid description: Reference article for the create volume raid command, which creates a RAID-5 volume using three or more specified dynamic disks. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # create volume raid diff --git a/WindowsServerDocs/administration/windows-commands/create-volume-simple.md b/WindowsServerDocs/administration/windows-commands/create-volume-simple.md index 4a32f6727c..bb3ae959ae 100644 --- a/WindowsServerDocs/administration/windows-commands/create-volume-simple.md +++ b/WindowsServerDocs/administration/windows-commands/create-volume-simple.md @@ -2,8 +2,8 @@ title: create volume simple description: Reference article for the create volume simple command, which creates a simple volume on the specified dynamic disk. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # create volume simple diff --git a/WindowsServerDocs/administration/windows-commands/create-volume-stripe.md b/WindowsServerDocs/administration/windows-commands/create-volume-stripe.md index 8f284d4dea..c89fbf4fa7 100644 --- a/WindowsServerDocs/administration/windows-commands/create-volume-stripe.md +++ b/WindowsServerDocs/administration/windows-commands/create-volume-stripe.md @@ -2,8 +2,8 @@ title: create volume stripe description: Reference article for the create volume stripe command, which creates a striped volume using two or more specified dynamic disks. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # create volume stripe diff --git a/WindowsServerDocs/administration/windows-commands/create.md b/WindowsServerDocs/administration/windows-commands/create.md index b03bdf879e..39258223a4 100644 --- a/WindowsServerDocs/administration/windows-commands/create.md +++ b/WindowsServerDocs/administration/windows-commands/create.md @@ -2,8 +2,8 @@ title: create description: Reference article for the create command, which creates a partition or shadow partition on a disk, a volume on one or more disks, or a virtual hard disk (VHD). ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/create_2.md b/WindowsServerDocs/administration/windows-commands/create_2.md index 810acbafd6..48c63c2de5 100644 --- a/WindowsServerDocs/administration/windows-commands/create_2.md +++ b/WindowsServerDocs/administration/windows-commands/create_2.md @@ -2,8 +2,8 @@ title: create (diskshadow) description: Reference article for the create command, which creates a shadow copy (snapshot) of a volume or alias. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/12/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/cscript.md b/WindowsServerDocs/administration/windows-commands/cscript.md index 8a7efb24ed..af7ebe74a4 100644 --- a/WindowsServerDocs/administration/windows-commands/cscript.md +++ b/WindowsServerDocs/administration/windows-commands/cscript.md @@ -2,8 +2,8 @@ title: cscript description: Reference article for the cscript command, which starts a script so that it runs in a command-line environment. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # cscript diff --git a/WindowsServerDocs/administration/windows-commands/date.md b/WindowsServerDocs/administration/windows-commands/date.md index 6a593d1e6d..bd3250f2ac 100644 --- a/WindowsServerDocs/administration/windows-commands/date.md +++ b/WindowsServerDocs/administration/windows-commands/date.md @@ -2,8 +2,8 @@ title: date description: Reference article for the date command, which displays or sets the system date. If used without parameters, ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/26/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/dcdiag.md b/WindowsServerDocs/administration/windows-commands/dcdiag.md index 5b9364faef..656cd100b9 100644 --- a/WindowsServerDocs/administration/windows-commands/dcdiag.md +++ b/WindowsServerDocs/administration/windows-commands/dcdiag.md @@ -3,8 +3,8 @@ title: dcdiag description: DCDiag is used to diagnose Active Directory domain controller health and as a troubleshooting tool by performing several network connectivity tests. ms.topic: reference ms.date: 11/14/2023 -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.custom: template-how-to, team=cloud_advocates #Required; leave this attribute/value as-is. ms.contributor: nedpyle --- @@ -59,28 +59,28 @@ The following table displays known tests that run by default unless specified ot |--|--| |Advertising| Checks whether each domain controller advertises itself in the roles that it should be capable of performing. This test validates that the public [DsGetDcName](/windows/win32/api/dsgetdc/nf-dsgetdc-dsgetdcnamea) function used by computers to locate domain controllers will correctly locate any DCs.

This test fails if the Netlogon Service has stopped or failed to start. If the [Key Distribution Key](/windows/win32/secauthn/key-distribution-center) (KDC) service is stopped, the Advertising test fails since the flag returned from DsGetDcName won't include KDC. If port 88 over TCP and UDP is blocked on a firewall, the Advertising test will pass despite the KDC not being able to answer Kerberos tickets requests.| |CheckSDRefDom| Checks that all application directory partitions have appropriate security descriptor reference domains.

This test uses LDAP and validates [cross reference objects](/windows/win32/adschema/c-crossref) located in **cn=partitions,cn=configuration,dc=\** contain the correct domain names in their [msDS-SDReferenceDomain](/openspecs/windows_protocols/ms-ada2/fab57b2b-5f1e-4ebd-893b-a4b6b6be78e0) attributes.| -|CheckSecurityError| Test is **not** run by default. Performs various security checks for errors related to the security components of the DC, such as issues with the security policy or the security database using LDAP, RPC, RPC over SMB, and ICMP. It checks:
  • That at least one KDC is online for each domain and is reachable.
  • That DCs computer object has replicated to other DCs.
  • If packet fragmentation of Kerberos over UDP might be an issue based on current MTU size by sending non-fragmenting ICMP packets.
  • That there aren't any replication or Knowledge Consistency Checker ([KCC](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731537(v=ws.10))) connection issues for connected partners by querying the function [DsReplicaGetInfo](/windows/win32/api/ntdsapi/nf-ntdsapi-dsreplicagetinfow) to get any security-related errors.
  • If the DCs computer account exists in Active Directory (AD) as part of the default “Domain Controllers” OU along with the correct UserAccountControl flags for DCs, the correct ServerReference attributes are set, and has the minimum required Service Principal Names (SPN) configured.

When the **/ReplSource** parameter is added, the partner also checks:
  • The time skew calculated between the servers to verify it's less than 300 seconds (5 minutes) for Kerberos. It **doesn't** check the Kerberos policy to see if the allowed skew has been modified.
  • Permissions on all the naming contexts (such as Schema, Configuration, etc.) on the source DC that validates replication and connectivity functions between DCs.
  • Connectivity to validate that the user running DCDiag can connect to and read the SYSVOL and NETLOGON shares without any security errors.
  • The **Access this computer from the network** privilege on the DC is checked to verify it's held by the _Administrators_, _Authenticated Users_, and _Everyone_ groups.
  • The DC's computer object is checked to ensure it's the latest version on the DCs. This is done to prove [replication convergence](/previous-versions/windows/it-pro/windows-server-2003/cc772726(v=ws.10)) along with checking versions, USNs, originating servers, and timestamps.
| +|CheckSecurityError| Test is **not** run by default. Performs various security checks for errors related to the security components of the DC, such as issues with the security policy or the security database using LDAP, RPC, RPC over SMB, and ICMP. It checks:
  • That at least one KDC is online for each domain and is reachable.
  • That DCs computer object has replicated to other DCs.
  • If packet fragmentation of Kerberos over UDP might be an issue based on current MTU size by sending non-fragmenting ICMP packets.
  • That there aren't any replication or Knowledge Consistency Checker ([KCC](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731537(v=ws.10))) connection issues for connected partners by querying the function [DsReplicaGetInfo](/windows/win32/api/ntdsapi/nf-ntdsapi-dsreplicagetinfow) to get any security-related errors.
  • If the DCs computer account exists in Active Directory (AD) as part of the default _Domain Controllers_ OU along with the correct UserAccountControl flags for DCs, the correct ServerReference attributes are set, and has the minimum required Service Principal Names (SPN) configured.

When the **/ReplSource** parameter is added, the partner also checks:
  • The time skew calculated between the servers to verify it's less than 300 seconds (5 minutes) for Kerberos. It **doesn't** check the Kerberos policy to see if the allowed skew has been modified.
  • Permissions on all the naming contexts (such as Schema, Configuration, etc.) on the source DC that validates replication and connectivity functions between DCs.
  • Connectivity to validate that the user running DCDiag can connect to and read the SYSVOL and NETLOGON shares without any security errors.
  • The **Access this computer from the network** privilege on the DC is checked to verify it's held by the _Administrators_, _Authenticated Users_, and _Everyone_ groups.
  • The DC's computer object is checked to ensure it's the latest version on the DCs. This is done to prove [replication convergence](/previous-versions/windows/it-pro/windows-server-2003/cc772726(v=ws.10)) along with checking versions, USNs, originating servers, and timestamps.
| |Connectivity| Verifies that the DSA and DNS are registered and reachable using LDAP and RPC. | |CrossRefValidation| Retrieves a list of [naming contexts](/openspecs/windows_protocols/ms-adts/f0f1e85a-3ac2-466a-87bf-2a8a1d18e4b8) located in _cn=partitions,cn=configuration,dc=\_ with their cross references and then validates them similar to the **CheckSDRefDom** test using LDAP. This test looks at the nCName, dnsRoot, nETBIOSName, and systemFlags attributes to:
  • Ensure DNs names aren't invalid or null.
  • Confirm DNs haven't been altered by CNF or 0ADEL.
  • Ensure systemFlags are correct for that object.
  • Call out empty (orphaned) replica sets.
| -|CutoffServers| Tests AD replication to ensure there aren't DCs without working connection objects between partners. Any servers that can't replicate inbound or outbound from any DCs are considered “cut off” using the [DsReplicaSyncAll](/windows/win32/api/ntdsapi/nf-ntdsapi-dsreplicasyncalla) function, which triggers replication on the DCs. Use the `/e` parameter with caution if there are poorly implemented WAN links that are kept clean using schedules.

If a server can't be contacted or is unavailable to LDAP on the network, then it provides no error or test results, even if the `/v` parameter is specified. This test uses RPC. | -|DcPromo| Tests against the server specified in the client DNS settings if the infrastructure meets the necessary requirements to promote your device to a DC. This test uses DNS on the network and checks:
  • If at least one network adapter has a primary DNS server set.
  • If there's a disjointed namespace based on the DNS suffix.
  • That proposed authoritative DNS zone can be contacted.
  • If dynamic DNS updates are possible for the server’s A record. It checks both the setting on the authoritative DNS zone and client registry configuration for DnsUpdateOnAllAdapters and DisableDynamicUpdate.
  • If an LDAP DClocator record, like **_ldap._tcp.dc._msdcs.\**, is returned when querying for existing forests.

The following arguments are required:
  • `/DnsDomain`:
    • Using this parameter requires one of the following arguments: `/ChildDomain`, `/NewForest`, `/NewTree`, or `/ReplicaDC`
  • If `/NewTree` is specified, the following argument is required:
    • `/ForestRoot`:
    • | -|DFSREvent| This test validates the Distributed File System Replication (DFSR) service’s health by checking the DFSR event log warning and error entries from the past 24 hours. This test uses RPC and EventLog Remoting Protocol. | +|CutoffServers| Tests AD replication to ensure there aren't DCs without working connection objects between partners. Any servers that can't replicate inbound or outbound from any DCs are considered cut off using the [DsReplicaSyncAll](/windows/win32/api/ntdsapi/nf-ntdsapi-dsreplicasyncalla) function, which triggers replication on the DCs. Use the `/e` parameter with caution if there are poorly implemented WAN links that are kept clean using schedules.

    If a server can't be contacted or is unavailable to LDAP on the network, then it provides no error or test results, even if the `/v` parameter is specified. This test uses RPC. | +|DcPromo| Tests against the server specified in the client DNS settings if the infrastructure meets the necessary requirements to promote your device to a DC. This test uses DNS on the network and checks:
    • If at least one network adapter has a primary DNS server set.
    • If there's a disjointed namespace based on the DNS suffix.
    • That proposed authoritative DNS zone can be contacted.
    • If dynamic DNS updates are possible for the server's A record. It checks both the setting on the authoritative DNS zone and client registry configuration for DnsUpdateOnAllAdapters and DisableDynamicUpdate.
    • If an LDAP DClocator record, like **_ldap._tcp.dc._msdcs.\**, is returned when querying for existing forests.

    The following arguments are required:
    • `/DnsDomain`:
      • Using this parameter requires one of the following arguments: `/ChildDomain`, `/NewForest`, `/NewTree`, or `/ReplicaDC`
    • If `/NewTree` is specified, the following argument is required:
      • `/ForestRoot`:
      • | +|DFSREvent| This test validates the Distributed File System Replication (DFSR) service™s health by checking the DFSR event log warning and error entries from the past 24 hours. This test uses RPC and EventLog Remoting Protocol. | |DNS| Tests enterprise-wide DNS health checks using DNS, RPC, and WMI protocols. Not ran by default and must be explicitly requested. See [DNS syntax](dcdiag.md#dns-syntax). | |FrsEvent| Checks to see if there are errors in the File Replication Service (FRS) event log from the past 24 hours as failing replication of the SysVol share can cause policy problems. This test uses RPC and EventLog Remoting Protocol. | |Intersite| Checks for failures that would prevent or temporarily hold up intersite replication and predicts how long it would take for the KCC to recover. This test uses DRS functions to check for conditions that would prevent intersite AD replication within a specific site or all sites by:
      • Locating and connecting to the Intersite Topology Generators (ISTG).
      • Locating and connecting to the bridgehead servers.
      • Reporting back any replication failures after triggering a replication.
      • Validating all DCs within sites with inbound connections to this site are available.
      • Checking the KCC values for **IntersiteFailuresAllowed** and **MaxFailureTimeForIntersiteLink** overrides within the registry key: **KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters**.

      The `/a` or `/e` parameter must be used as not providing a site would allow the test to run but skips actual testing. This test uses RPC over the network to test the replication aspects and asks registry connections to check for NTDS override entries. LDAP is also used to locate connection info. | |KccEvent| This test queries the KCC on the DC for errors and warnings generated in the Directory Services event log during the last 15 minutes. The 15-minute threshold is irrespective of the [Repl topology update period (secs)](/previous-versions/windows/it-pro/windows-server-2003/cc739941(v=ws.10)#repltopology-update-delay-secs) registry value on the DC.

      If firewall rules are causing this test to fail, see [KB2512643](/troubleshoot/windows-server/identity/dcdiag-commands-running-errors#resolution) that covers enabling those rules to allow the test to succeed. This test uses RPC along with the EventLog Remoting Protocol. | |KnowsOfRoleHolders| This test returns the DCs knowledge of the five Flexible Single Master Operation (FSMO) roles but doesn't check all DCs knowledge for consistency. Using the `/e` parameter provides data for comparison. This test uses RPC to return [DSListRoles](/windows/win32/api/ntdsapi/nf-ntdsapi-dslistrolesa) within the [Directory Replication Service](/openspecs/windows_protocols/ms-drsr/06205d97-30da-4fdc-a276-3fd831b272e0) (DRS) functions. | -|MachineAccount| Checks whether the machine account has properly registered and that the services are advertised using LDAP and RPC over SMB, including checking:
      • The DC's computer account exists in AD.
      • It’s within the Domain Controllers OU.
      • It has the correct [UserAccountControl](/troubleshoot/windows-server/identity/useraccountcontrol-manipulate-account-properties) flags for DCs.
      • The correct [ServerReference](/openspecs/windows_protocols/ms-ada3/f08d0b62-0b0a-4268-9d8e-da4c62f647f1) attributes are set.
      • The minimum [Service Principal Names](/windows/win32/ad/service-principal-names) (SPN) are set. This test is identical to **CheckSecurityError** as they use the same internal test.

      This test also has two repair options:
      • `/RecreateMachineAccount` - Recreates a missing DC computer object. This is **not** a recommended fix as it doesn't recreate any child objects of a DC, such as FRS and DFSR subscriptions. The best practice is to use a valid SystemState backup to authoritatively restore the DC's deleted object and child objects. If you use this option, the DC needs to be gracefully demoted and promoted to repair all the missing relationships.
      • `/FixMachineAccount` - Adds the UserAccountControl flags **TRUSTED_FOR_DELEGATION** and **SERVER_TRUST_ACCOUNT** to a DCs computer object. Using this repair option is preferred over trying to set these flags yourself through **ADSIEDIT** or other LDAP editors. | +|MachineAccount| Checks whether the machine account has properly registered and that the services are advertised using LDAP and RPC over SMB, including checking:
        • The DC's computer account exists in AD.
        • It's within the Domain Controllers OU.
        • It has the correct [UserAccountControl](/troubleshoot/windows-server/identity/useraccountcontrol-manipulate-account-properties) flags for DCs.
        • The correct [ServerReference](/openspecs/windows_protocols/ms-ada3/f08d0b62-0b0a-4268-9d8e-da4c62f647f1) attributes are set.
        • The minimum [Service Principal Names](/windows/win32/ad/service-principal-names) (SPN) are set. This test is identical to **CheckSecurityError** as they use the same internal test.

        • This test also has two repair options:
        • `/RecreateMachineAccount` - Recreates a missing DC computer object. This is **not** a recommended fix as it doesn't recreate any child objects of a DC, such as FRS and DFSR subscriptions. The best practice is to use a valid SystemState backup to authoritatively restore the DC's deleted object and child objects. If you use this option, the DC needs to be gracefully demoted and promoted to repair all the missing relationships.
        • `/FixMachineAccount` - Adds the UserAccountControl flags **TRUSTED_FOR_DELEGATION** and **SERVER_TRUST_ACCOUNT** to a DCs computer object. Using this repair option is preferred over trying to set these flags yourself through **ADSIEDIT** or other LDAP editors. | |NCSecDesc| Checks permissions on all the naming contexts (such as Schema, Configuration, etc.) on the source DC to validate that replication and connectivity works between DCs. It makes sure that _Enterprise Domain Controllers_ and _Administrators_ groups have the correct minimum permissions, which is the same test performed within **CheckSecurityError**. This test uses LDAP.
        | |NetLogons| Validates that the user running DCDiag can connect to and read the SYSVOL and NETLOGON shares without any security errors. It also verifies that the _Administrators_, _Authenticated Users_, and _Everyone_ group have the **access this computer from the network** privilege on the DC.| -|ObjectsReplicated| Checks that the Machine Account and Directory System Agent (DSA) objects have replicated. Two objects are validated by default and that they exist in each DC and are up to date on all other DCs:
        • **CN=NTDS Settings**
        • **CN=\**

        You can use the `/objectdn:dn` parameter with the `/n:nc` parameter to specify an additional object to check. This test is done using RPC with DRS functions. | -|OutboundSecureChannels| This test doesn't run by default. It checks that secure channels exist from all of the domain controllers in the domain to the domains specified by the `/testdomain` parameter. The `/nositerestriction` parameter prevents DCDiag from limiting the test to the domain controllers in the site.| -|RegisterInDNS| Tests whether the directory server can register the directory Server Locator DNS records. These records must be present in DNS in order for other computers to locate this directory server for the **** domain. This also reports if any modifications to the existing DNS infrastructure are required. The parameter `/DnsDomain`: must be used. This test checks:
        • The authoritative DNS zone can be contacted.
        • If at least one network adapter has a primary DNS server set.
        • If you would have a [disjoint namespace](/previous-versions/windows/it-pro/windows-server-2003/cc731125(v=ws.10)) based on the DNS suffix.
        • The proposed authoritative DNS zone can be contacted.
        • If dynamic DNS updates are possible for the server’s A record. It checks settings on the authoritative DNS zone and the client registry configuration of **DnsUpdateOnAllAdapters** and **DisableDynamicUpdate**.
        • If an LDAP DClocator record, like **_ldap._tcp.dc._msdcs.\**, is returned when querying for existing forests.
        | +|ObjectsReplicated| Checks that the Machine Account and Directory System Agent (DSA) objects have replicated. Two objects are validated by default and that they exist in each DC and are up to date on all other DCs:
        • **CN=NTDS Settings**
        • **CN=\**

        You can use the `/objectdn:dn` parameter with the `/n:nc` parameter to specify an additional object to check. This test is done using RPC with DRS functions. | +|OutboundSecureChannels| This test doesn't run by default. It checks that secure channels exist from all of the domain controllers in the domain to the domains specified by the `/testdomain` parameter. The `/nositerestriction` parameter prevents DCDiag from limiting the test to the domain controllers in the site.| +|RegisterInDNS| Tests whether the directory server can register the directory Server Locator DNS records. These records must be present in DNS in order for other computers to locate this directory server for the **** domain. This also reports if any modifications to the existing DNS infrastructure are required. The parameter `/DnsDomain`: must be used. This test checks:
        • The authoritative DNS zone can be contacted.
        • If at least one network adapter has a primary DNS server set.
        • If you would have a [disjoint namespace](/previous-versions/windows/it-pro/windows-server-2003/cc731125(v=ws.10)) based on the DNS suffix.
        • The proposed authoritative DNS zone can be contacted.
        • If dynamic DNS updates are possible for the server's A record. It checks settings on the authoritative DNS zone and the client registry configuration of **DnsUpdateOnAllAdapters** and **DisableDynamicUpdate**.
        • If an LDAP DClocator record, like **_ldap._tcp.dc._msdcs.\**, is returned when querying for existing forests.
        | |Replications| This test checks all [AD replication](/previous-versions/windows/it-pro/windows-server-2003/cc772726(v=ws.10)) connection objects for all naming contexts on specified DC(s) if:
        • The last replication attempted was successful or returns an error.
        • That replication is disabled.
        • Replication latency is more than 12 hours.
        | |RidManager| Checks whether the relative identifier ([RID](/previous-versions/windows/it-pro/windows-server-2003/cc773108(v=ws.10))) master is accessible and if:
        • It contains the proper information.
        • Can be located and contacted through a [DsBind](/windows/win32/api/ntdsapi/nf-ntdsapi-dsbinda).
        • Has valid RID pool values.

        The role holder must be online and accessible for DCs to be able to create security principals (users, computers, and groups) as well as for further DCs to be promoted within a domain. This test uses LDAP and RPC. | |Services| This test validates that various AD-dependent services are running, accessible, and set to specific start types. These services start automatically and run in a shared process unless specified otherwise:
        • DFSR (runs in own process)
        • DNSCACHE
        • EVENTSYSTEM
        • IISADMIN (If using SMTP-based AD replication)
        • ISMSERV
        • KDC
        • NETLOGON
        • NTDS
        • NTFRS (runs in own process)
        • RPCSS
        • SAMSS
        • SERVER
        • SMTPSVC (If using SMTP-based AD replication)
        • W32TIME (starts automatically or manually)
        • WORKSTATION

        These service names are listed in the registry path **HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services**. This test uses RPC and the [Service Control Manager](/openspecs/windows_protocols/ms-scmr/705b624a-13de-43cc-b8a2-99573da3635f) remote protocol. | -|SysVolCheck| This test reads the DCs Netlogon [SysVolReady](/previous-versions/cc939543(v=technet.10)) registry key to validate that SYSVOL is ready. The value name has to exist with a value of 1 to pass this test and works with either FRS or DFSR replicated SYSVOLs. It doesn’t check if the SYSVOL and NELOGON shares are accessible as this is performed by **CheckSecurityError**. This test uses RPC over SMB. | -|SystemLog| Validates the System Event Log’s health by reading and writing entries from the past 60 minutes for any errors and warnings. This test uses RPC and the [Service Control Manager](/openspecs/windows_protocols/ms-scmr/705b624a-13de-43cc-b8a2-99573da3635f) remote protocol. | +|SysVolCheck| This test reads the DCs Netlogon [SysVolReady](/previous-versions/cc939543(v=technet.10)) registry key to validate that SYSVOL is ready. The value name has to exist with a value of 1 to pass this test and works with either FRS or DFSR replicated SYSVOLs. It doesn't check if the SYSVOL and NELOGON shares are accessible as this is performed by **CheckSecurityError**. This test uses RPC over SMB. | +|SystemLog| Validates the System Event Log's health by reading and writing entries from the past 60 minutes for any errors and warnings. This test uses RPC and the [Service Control Manager](/openspecs/windows_protocols/ms-scmr/705b624a-13de-43cc-b8a2-99573da3635f) remote protocol. | |Topology| Checks that the generated AD replication topology is fully connected for all DSAs. This test isn't performed by default and must be ran explicitly. It checks:
        • If automatic intra-site topology generation is disabled.
        • If automatic inter-site topology generation is disabled.
        • For disconnected topologies (missing connection objects), both upstream and downstream from each reference DC.

        This test uses RPC, LDAP, and [DsReplicaSyncAll](/windows/win32/api/ntdsapi/nf-ntdsapi-dsreplicasyncalla) with the flag **DS_REPSYNCALL_DO_NOT_SYNC**, meaning that it analyzes and validates replication topology without actually replicating changes. This test doesn't validate the availability of replication partners. Having a partner offline won't cause failures in this test. It also doesn't test if the schedule is closed, preventing replication. To see those active replication results, use tests **Replications** or **CutoffServers**. | |VerifyEnterpriseReferences| Checks that specified system references are intact for the FRS and replication infrastructure across all objects in the enterprise on each domain controller. This includes the following DC site attributes and objects:
        • **frsComputerReference**: cn=domain system volume (sysvol share),cn=ntfrs subscriptions,cn=\,ou=domain controllers,DC=\
        • **frsComputerReferenceBL**: cn=\,cn=domain system volume (sysvol share),cn=file replication service,cn=system,dc=\
        • **hasMasterNCs**: cn=ntds settings,cn=\,cn=\,cn=sites,cn=configuration,dc=\
        • **msDFSR-ComputerReference**: cn=\,cn=topology,cn=domain system volume,cn=dfsr-blobalsettings,cn=system,dc=\
        • **msDFSR-ComputerReferenceBL**: cn=\,ou=domain controllers,dc=\
        • **nCName**: cn=\,cn=partitions,cn=configuration,dc=\
        • **ServerReference**: cn=\,cn=\,cn=sites,cn=configuration,dc=\
        • **ServerReferenceBL**: cn=\,ou=domain controllers,dc=\

        The two **DFSR** tests are only performed if domain functional level is Windows Server 2008 or higher. This means there will be an expected failure if **DFSR** hasn't been migrated to SYSVOL. This test uses LDAP and only the specified DCs are contacted. | |VerifyReferences| Checks that certain system references are intact for the FRS and replication infrastructure. This test verifies computer reference attributes for a single DC, including the following DC site attributes and objects:
        • **frsComputerReference**: cn=domain system volume (sysvol share),cn=ntfrs subscriptions,cn=\,ou=domain controllers,DC=\
        • **frsComputerReferenceBL**: cn=\,cn=domain system volume (sysvol share),cn=file replication service,cn=system,dc=\
        • **msDFSR-ComputerReference**: cn=\,cn=topology,cn=domain system volume,cn=dfsr-blobalsettings,cn=system,dc=\
        • **msDFSR-ComputerReferenceBL**: cn=\,ou=domain controllers,dc=\
        • **ServerReference**: cn=\,cn=\,cn=sites,cn=configuration,dc=\
        • **ServerReferenceBL**: cn=\,ou=domain controllers,dc=\

        This test uses LDAP and is similar to the **VerifyEnterpriseRefrences** test except that it doesn't check partition cross references or all other DC objects. | diff --git a/WindowsServerDocs/administration/windows-commands/dcgpofix.md b/WindowsServerDocs/administration/windows-commands/dcgpofix.md index 907598e51c..a6dfdcc2af 100644 --- a/WindowsServerDocs/administration/windows-commands/dcgpofix.md +++ b/WindowsServerDocs/administration/windows-commands/dcgpofix.md @@ -2,8 +2,8 @@ title: dcgpofix description: Reference article for the dcgpofix command, which recreates the default Group Policy Objects (GPOs) for a domain. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 04/16/2024 --- diff --git a/WindowsServerDocs/administration/windows-commands/dcpromo.md b/WindowsServerDocs/administration/windows-commands/dcpromo.md index 826d78fdde..7f64ee144d 100644 --- a/WindowsServerDocs/administration/windows-commands/dcpromo.md +++ b/WindowsServerDocs/administration/windows-commands/dcpromo.md @@ -2,8 +2,8 @@ title: dcpromo in Windows Server description: Learn about using the dcpromo command to install, promote, demote, and remove Active Directory Domain Services (AD DS) from a Windows Server. ms.topic: reference -author: xelu86 -ms.author: alalve +author: robinharwood +ms.author: roharwoo ms.date: 04/22/2024 --- @@ -11,7 +11,7 @@ ms.date: 04/22/2024 Applies To: Windows Server (All supported versions) -The dcpromo command installs, promotes, demotes, and removes Active Directory Domain Services (AD DS) from a Windows Server. +The dcpromo command installs, promotes, demotes, and removes Active Directory Domain Services (AD DS) from a Windows Server. For examples of how to use **dcpromo**, see [Examples](). @@ -37,13 +37,13 @@ For examples of how to use **dcpromo**, see [Examples](). The following table shows the parameters available when running `dcpromo.exe` from a command prompt for the unattended installation of a domain controller that runs Windows Server. -For more information about creating a new forest, see [Installing a New Windows Server 2008 Forest](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc772464(v=ws.10)). +For more information about creating a new forest, see [Installing a New Windows Server 2008 Forest](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc772464(v=ws.10)). -For more information about creating a new domain, see [Installing a New Windows Server 2008 Child Domain](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731394(v=ws.10)). +For more information about creating a new domain, see [Installing a New Windows Server 2008 Child Domain](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731394(v=ws.10)). -For more information about creating a new domain tree, see [Installing a New Windows Server 2008 Domain Tree](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc733006(v=ws.10)). +For more information about creating a new domain tree, see [Installing a New Windows Server 2008 Domain Tree](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc733006(v=ws.10)). -For more information about creating another domain controller for a domain, see [Installing an Additional Windows Server 2008 Domain Controller](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc733027(v=ws.10)). +For more information about creating another domain controller for a domain, see [Installing an Additional Windows Server 2008 Domain Controller](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc733027(v=ws.10)). | Parameter and value pair | Description and default | |---|---| @@ -82,7 +82,7 @@ For more information about creating another domain controller for a domain, see | SkipAutoConfigDns | Skips automatic configuration of DNS client settings, forwarders, and root hints. This parameter is in effect only if the DNS Server service is already installed. | | Syskey:{\ \| system key} |

        Specifies the system key for the media from which you replicate the data.

        The default is **none**.

        | | SysVolPath:"path_to_database_file" |

        Specifies the fully qualified, non-UNC path to a directory on a fixed disk of the local computer, for example, **C:\Windows\SYSVOL**.

        The default is **%SYSTEMROOT%\SYSVOL**. | -| TransferIMRoleIfNecessary:{Yes \| \} |

        Specifies whether to transfer the infrastructure master operations master role (also known as flexible single master operations or FSMO) to the domain controller that you're creating. Perform the transfer in case it's currently hosted on a global catalog server—and you don't plan to make the domain controller that you're creating a global catalog server. Use **Yes** to transfer the infrastructure master role to the domain controller that you're creating in case the transfer is needed; in this case, make sure to use `/ConfirmGC:No`. Use **No** if you want the infrastructure master role to remain where it currently is.

        The default is **No**.

        | +| TransferIMRoleIfNecessary:{Yes \| \} |

        Specifies whether to transfer the infrastructure master operations master role (also known as flexible single master operations or FSMO) to the domain controller that you're creating. Perform the transfer in case it's currently hosted on a global catalog server and you don't plan to make the domain controller that you're creating a global catalog server. Use **Yes** to transfer the infrastructure master role to the domain controller that you're creating in case the transfer is needed; in this case, make sure to use `/ConfirmGC:No`. Use **No** if you want the infrastructure master role to remain where it currently is.

        The default is **No**.

        | | UserDomain:"domain_name" |

        Specifies the domain name for the user name (account credentials) for installing a domain controller.

        Use this parameter with the **UserName** parameter.

        | | UserName:"user_name" | Specifies the user name (account credentials) for the operation. If no value is specified, the credentials of the current user are used for the operation. | @@ -136,15 +136,15 @@ For more information about attaching a server to an RODC account, see [Performin ## dcpromo Demotion operation parameters -You can use parameters in the following list when you remove AD DS from a domain controller that runs Windows Server. +You can use parameters in the following list when you remove AD DS from a domain controller that runs Windows Server. -For more information about removing a domain controller from a domain, see [Removing a Windows Server 2008 Domain Controller from a Domain](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc771844(v=ws.10)). +For more information about removing a domain controller from a domain, see [Removing a Windows Server 2008 Domain Controller from a Domain](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc771844(v=ws.10)). -For more information about removing the last domain controller in a domain, see [Removing the Last Windows Server 2008 Domain Controller in a Domain](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc771839(v=ws.10)). +For more information about removing the last domain controller in a domain, see [Removing the Last Windows Server 2008 Domain Controller in a Domain](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc771839(v=ws.10)). -For more information about removing the last domain controller in a forest, see [Removing the Last Windows Server 2008 Domain Controller in a Forest](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc771835(v=ws.10)). +For more information about removing the last domain controller in a forest, see [Removing the Last Windows Server 2008 Domain Controller in a Forest](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc771835(v=ws.10)). -For more information about forcing the removal of a domain controller, see [Forcing the Removal of a Windows Server 2008 Domain Controller](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731871(v=ws.10)). +For more information about forcing the removal of a domain controller, see [Forcing the Removal of a Windows Server 2008 Domain Controller](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731871(v=ws.10)). | Parameter and value pair | Description and default | |---|---| @@ -172,7 +172,7 @@ The following example supplies an answer file named **NewForestInstallation**: dcpromo /answer:NewForestInstallation ``` -The following example creates the first domain controller in a new child domain where you expect to install at least some Windows Server 2025 domain controllers: +The following example creates the first domain controller in a new child domain where you expect to install at least some Windows Server 2025 domain controllers: ```cli dcpromo /unattend /InstallDns:yes /ParentDomainDNSName:contoso.com /replicaOrNewDomain:domain /newDomain:child /newDomainDnsName:east.contoso.com /childName:east /DomainNetbiosName:east /databasePath:"e:\ntds" /logPath:"e:\ntdslogs" /sysvolpath:"g:\sysvol" /safeModeAdminPassword:FH#3573.cK /forestLevel:10 /domainLevel:10 /rebootOnCompletion:yes diff --git a/WindowsServerDocs/administration/windows-commands/defrag.md b/WindowsServerDocs/administration/windows-commands/defrag.md index 5dd0e06d1a..57471d31f3 100644 --- a/WindowsServerDocs/administration/windows-commands/defrag.md +++ b/WindowsServerDocs/administration/windows-commands/defrag.md @@ -2,8 +2,8 @@ title: defrag description: Reference article for the defrag command, which locates and consolidates fragmented files on local volumes to improve system performance. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 09/28/2023 --- # defrag diff --git a/WindowsServerDocs/administration/windows-commands/del.md b/WindowsServerDocs/administration/windows-commands/del.md index 8f0bf9f305..42ce521048 100644 --- a/WindowsServerDocs/administration/windows-commands/del.md +++ b/WindowsServerDocs/administration/windows-commands/del.md @@ -2,8 +2,8 @@ title: del description: Reference article for the del command, which deletes one or more files. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 6/22/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/delete-disk.md b/WindowsServerDocs/administration/windows-commands/delete-disk.md index d3e1775435..8c3e94e6c4 100644 --- a/WindowsServerDocs/administration/windows-commands/delete-disk.md +++ b/WindowsServerDocs/administration/windows-commands/delete-disk.md @@ -2,8 +2,8 @@ title: delete disk description: Reference article for the delete disk command, which deletes a missing dynamic disk from the list of disks. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/delete-partition.md b/WindowsServerDocs/administration/windows-commands/delete-partition.md index d5a0c967c8..fd09f80876 100644 --- a/WindowsServerDocs/administration/windows-commands/delete-partition.md +++ b/WindowsServerDocs/administration/windows-commands/delete-partition.md @@ -2,8 +2,8 @@ title: delete partition description: Reference article for the delete partition command, which deletes the partition with focus. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/delete-shadows.md b/WindowsServerDocs/administration/windows-commands/delete-shadows.md index a6e41841e3..c79857440a 100644 --- a/WindowsServerDocs/administration/windows-commands/delete-shadows.md +++ b/WindowsServerDocs/administration/windows-commands/delete-shadows.md @@ -2,8 +2,8 @@ title: delete shadows description: Reference article for the delete shadows command, which deletes shadow copies. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/delete-volume.md b/WindowsServerDocs/administration/windows-commands/delete-volume.md index cb9545cc4e..ed97f6e32e 100644 --- a/WindowsServerDocs/administration/windows-commands/delete-volume.md +++ b/WindowsServerDocs/administration/windows-commands/delete-volume.md @@ -2,8 +2,8 @@ title: delete volume description: Reference article for the delete volume command, which deletes the selected volume. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/delete.md b/WindowsServerDocs/administration/windows-commands/delete.md index 46c65a2d4f..11e908fc69 100644 --- a/WindowsServerDocs/administration/windows-commands/delete.md +++ b/WindowsServerDocs/administration/windows-commands/delete.md @@ -2,8 +2,8 @@ title: delete description: Reference article for the delete command, which deletes a partition or a volume. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/12/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/detach-vdisk.md b/WindowsServerDocs/administration/windows-commands/detach-vdisk.md index 0798aa1885..51b93d0259 100644 --- a/WindowsServerDocs/administration/windows-commands/detach-vdisk.md +++ b/WindowsServerDocs/administration/windows-commands/detach-vdisk.md @@ -2,8 +2,8 @@ title: detach vdisk description: Reference article for the detach vdisk command, which stops the selected virtual hard disk (VHD) from appearing as a local hard disk drive on the host computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/detail-disk.md b/WindowsServerDocs/administration/windows-commands/detail-disk.md index b9ed6d4d2c..dc2b812ff0 100644 --- a/WindowsServerDocs/administration/windows-commands/detail-disk.md +++ b/WindowsServerDocs/administration/windows-commands/detail-disk.md @@ -2,8 +2,8 @@ title: detail disk description: Reference article for the detail disk command, which displays the properties of the selected disk and the volumes on that disk. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/detail-partition.md b/WindowsServerDocs/administration/windows-commands/detail-partition.md index 07f4e89f87..cb8c2eb329 100644 --- a/WindowsServerDocs/administration/windows-commands/detail-partition.md +++ b/WindowsServerDocs/administration/windows-commands/detail-partition.md @@ -2,8 +2,8 @@ title: detail partition description: Reference article for the detail partition command, which displays the properties of the selected partition. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/detail-vdisk.md b/WindowsServerDocs/administration/windows-commands/detail-vdisk.md index bb5ebc75d0..440b9cc9fa 100644 --- a/WindowsServerDocs/administration/windows-commands/detail-vdisk.md +++ b/WindowsServerDocs/administration/windows-commands/detail-vdisk.md @@ -2,8 +2,8 @@ title: detail vdisk description: Reference article for the detail vdisk command, which displays the properties of the selected virtual hard disk (VHD). ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/detail-volume.md b/WindowsServerDocs/administration/windows-commands/detail-volume.md index 95683051f4..2537f20055 100644 --- a/WindowsServerDocs/administration/windows-commands/detail-volume.md +++ b/WindowsServerDocs/administration/windows-commands/detail-volume.md @@ -2,8 +2,8 @@ title: detail volume description: Reference article for detail volume, which displays the disks on which the current volume resides. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/detail.md b/WindowsServerDocs/administration/windows-commands/detail.md index 60e7efb782..d01fdec687 100644 --- a/WindowsServerDocs/administration/windows-commands/detail.md +++ b/WindowsServerDocs/administration/windows-commands/detail.md @@ -2,8 +2,8 @@ title: detail description: Reference article for the detail command, which displays information about the selected disk, partition, volume, or virtual hard disk (VHD). ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/dfsdiag-testdcs.md b/WindowsServerDocs/administration/windows-commands/dfsdiag-testdcs.md index 5ee34a2218..1ef6f39af0 100644 --- a/WindowsServerDocs/administration/windows-commands/dfsdiag-testdcs.md +++ b/WindowsServerDocs/administration/windows-commands/dfsdiag-testdcs.md @@ -2,8 +2,8 @@ title: dfsdiag testdcs description: Reference article for the dfsdiag testdcs command, which checks the configuration of domain controllers in the specified domain. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/dfsdiag-testdfsconfig.md b/WindowsServerDocs/administration/windows-commands/dfsdiag-testdfsconfig.md index 30600623c8..6e3fddb33a 100644 --- a/WindowsServerDocs/administration/windows-commands/dfsdiag-testdfsconfig.md +++ b/WindowsServerDocs/administration/windows-commands/dfsdiag-testdfsconfig.md @@ -2,8 +2,8 @@ title: dfsdiag testdfsconfig description: Reference article for the dfsdiag testdfsconfig, which checks the configuration of a Distributed File System (DFS) namespace. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 06/30/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/dfsdiag-testdfsintegrity.md b/WindowsServerDocs/administration/windows-commands/dfsdiag-testdfsintegrity.md index 3340bdf72a..2a3905aa29 100644 --- a/WindowsServerDocs/administration/windows-commands/dfsdiag-testdfsintegrity.md +++ b/WindowsServerDocs/administration/windows-commands/dfsdiag-testdfsintegrity.md @@ -2,8 +2,8 @@ title: dfsdiag testdfsintegrity description: Reference article for the dfsdiag testdfsintegrity command, which checks the integrity of the Distributed File System (DFS) namespace. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/dfsdiag-testreferral.md b/WindowsServerDocs/administration/windows-commands/dfsdiag-testreferral.md index 06af13ee60..341cb66315 100644 --- a/WindowsServerDocs/administration/windows-commands/dfsdiag-testreferral.md +++ b/WindowsServerDocs/administration/windows-commands/dfsdiag-testreferral.md @@ -2,8 +2,8 @@ title: dfsdiag testreferral description: Reference article for the dfsdiag testreferral command, which checks Distributed File System (DFS) referrals. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/dfsdiag-testsites.md b/WindowsServerDocs/administration/windows-commands/dfsdiag-testsites.md index 67345691df..05afb4f5e5 100644 --- a/WindowsServerDocs/administration/windows-commands/dfsdiag-testsites.md +++ b/WindowsServerDocs/administration/windows-commands/dfsdiag-testsites.md @@ -2,8 +2,8 @@ title: dfsdiag testsites description: Reference article for dfsdiag testsites, which checks the configuration of active directory Domain Services (AD DS) sites by verifying that servers that act as namespace servers or folder (link) targets have the same site associations on all domain controllers. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/dfsdiag.md b/WindowsServerDocs/administration/windows-commands/dfsdiag.md index 4bb64a8bd9..fdd001c481 100644 --- a/WindowsServerDocs/administration/windows-commands/dfsdiag.md +++ b/WindowsServerDocs/administration/windows-commands/dfsdiag.md @@ -2,8 +2,8 @@ title: dfsdiag description: Reference article for the dfsdiag command, which provides diagnostic information for DFS Namespaces. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/dfsrmig.md b/WindowsServerDocs/administration/windows-commands/dfsrmig.md index 8616505f4d..6b4abe4e3b 100644 --- a/WindowsServerDocs/administration/windows-commands/dfsrmig.md +++ b/WindowsServerDocs/administration/windows-commands/dfsrmig.md @@ -2,8 +2,8 @@ title: dfsrmig description: Reference article for the dfsrmig command, which migrates SYSvol replication from FRS to DFS Replication, provides information about the progress of the migration, and modifies AD DS objects to support the migration. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 1/03/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/dfsutil.md b/WindowsServerDocs/administration/windows-commands/dfsutil.md index 90af607b0d..e72d6742a0 100644 --- a/WindowsServerDocs/administration/windows-commands/dfsutil.md +++ b/WindowsServerDocs/administration/windows-commands/dfsutil.md @@ -2,8 +2,8 @@ title: dfsutil description: Reference article for the dfsutil command, which manages DFS Namespaces, servers and clients. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/diantz.md b/WindowsServerDocs/administration/windows-commands/diantz.md index 3497eb5a95..4d13a302a6 100644 --- a/WindowsServerDocs/administration/windows-commands/diantz.md +++ b/WindowsServerDocs/administration/windows-commands/diantz.md @@ -2,8 +2,8 @@ title: diantz description: Reference article for the diantz command, which packages existing files into a cabinet (.cab) file. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- # diantz diff --git a/WindowsServerDocs/administration/windows-commands/dir.md b/WindowsServerDocs/administration/windows-commands/dir.md index 2bd54fdbc9..539079b4d4 100644 --- a/WindowsServerDocs/administration/windows-commands/dir.md +++ b/WindowsServerDocs/administration/windows-commands/dir.md @@ -2,8 +2,8 @@ title: dir description: Reference article for the dir command, which displays a list of a directory's files and subdirectories. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/diskcomp.md b/WindowsServerDocs/administration/windows-commands/diskcomp.md index 1d198f185d..1a46ce0d9e 100644 --- a/WindowsServerDocs/administration/windows-commands/diskcomp.md +++ b/WindowsServerDocs/administration/windows-commands/diskcomp.md @@ -2,8 +2,8 @@ title: diskcomp description: Reference article for the diskcomp command, which compares the contents of two floppy disks. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/diskcopy.md b/WindowsServerDocs/administration/windows-commands/diskcopy.md index b1b59378f5..a442c06f13 100644 --- a/WindowsServerDocs/administration/windows-commands/diskcopy.md +++ b/WindowsServerDocs/administration/windows-commands/diskcopy.md @@ -2,8 +2,8 @@ title: diskcopy description: Reference article for the diskcopy command, which copies the contents of the floppy disk in the source drive to a formatted or unformatted floppy disk in the destination drive. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 05/07/2018 --- diff --git a/WindowsServerDocs/administration/windows-commands/diskpart-scripts-and-examples.md b/WindowsServerDocs/administration/windows-commands/diskpart-scripts-and-examples.md index c7259c145d..5ee803850d 100644 --- a/WindowsServerDocs/administration/windows-commands/diskpart-scripts-and-examples.md +++ b/WindowsServerDocs/administration/windows-commands/diskpart-scripts-and-examples.md @@ -2,8 +2,8 @@ title: diskpart scripts and examples description: Reference article for diskpart scripts and examples about how to automate disk-related tasks, such as creating volumes or converting disks to dynamic disks. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/diskpart.md b/WindowsServerDocs/administration/windows-commands/diskpart.md index bce88bdbfb..0fb039a913 100644 --- a/WindowsServerDocs/administration/windows-commands/diskpart.md +++ b/WindowsServerDocs/administration/windows-commands/diskpart.md @@ -2,8 +2,8 @@ title: diskpart description: Reference article for the diskpart command interpreter, which helps you manage your computer's drives. ms.topic: reference -author: xelu86 -ms.author: alalve +author: dknappettmsft +ms.author: daknappe ms.date: 09/21/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/diskperf.md b/WindowsServerDocs/administration/windows-commands/diskperf.md index ac74cff390..e7f399cb5b 100644 --- a/WindowsServerDocs/administration/windows-commands/diskperf.md +++ b/WindowsServerDocs/administration/windows-commands/diskperf.md @@ -2,8 +2,8 @@ title: diskperf description: Reference article for the diskperf command, which can be used to remotely enable or disable physical or logical disk performance counters on computers running Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/diskraid.md b/WindowsServerDocs/administration/windows-commands/diskraid.md index 51a330f1de..04b506fea8 100644 --- a/WindowsServerDocs/administration/windows-commands/diskraid.md +++ b/WindowsServerDocs/administration/windows-commands/diskraid.md @@ -2,8 +2,8 @@ title: Diskraid description: Reference article for the Diskraid command-line tool, which enables you to configure and manage redundant array of independent (or inexpensive) disks (RAID) storage subsystems. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- @@ -735,7 +735,7 @@ Press ENTER and output similar to the following is displayed: ``` Microsoft Diskraid version 5.2.xxxx -Copyright (©) 2003 Microsoft Corporation +Copyright (©) 2003 Microsoft Corporation On computer: COMPUTER_NAME ``` diff --git a/WindowsServerDocs/administration/windows-commands/diskshadow.md b/WindowsServerDocs/administration/windows-commands/diskshadow.md index a2a1d9aa4d..e98926b3ca 100644 --- a/WindowsServerDocs/administration/windows-commands/diskshadow.md +++ b/WindowsServerDocs/administration/windows-commands/diskshadow.md @@ -2,8 +2,8 @@ title: Diskshadow description: Reference article for the Diskshadow command, which is a tool that exposes the functionality offered by the volume shadow copy service (VSS). ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- # Diskshadow diff --git a/WindowsServerDocs/administration/windows-commands/dispdiag.md b/WindowsServerDocs/administration/windows-commands/dispdiag.md index 3d9120b010..d7831f5e33 100644 --- a/WindowsServerDocs/administration/windows-commands/dispdiag.md +++ b/WindowsServerDocs/administration/windows-commands/dispdiag.md @@ -2,8 +2,8 @@ title: dispdiag description: Reference article for the dispdiag command, which logs display information to a file. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/dnscmd.md b/WindowsServerDocs/administration/windows-commands/dnscmd.md index 2d2795f70e..fb890d2069 100644 --- a/WindowsServerDocs/administration/windows-commands/dnscmd.md +++ b/WindowsServerDocs/administration/windows-commands/dnscmd.md @@ -2,8 +2,8 @@ title: Dnscmd description: Reference article for the dnscmd command, which is a command-line interface for managing DNS servers. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 03/21/2024 --- @@ -99,7 +99,7 @@ dnscmd [] /config #### Parameters > [!NOTE] -> This article contains references to the term slave, a term that Microsoft no longer uses. When the term is removed from the software, we’ll remove it from this article. +> This article contains references to the term slave, a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article. | Parameters | Description | | ---------- | ----------- | diff --git a/WindowsServerDocs/administration/windows-commands/doskey.md b/WindowsServerDocs/administration/windows-commands/doskey.md index b275b18827..f8347782b2 100644 --- a/WindowsServerDocs/administration/windows-commands/doskey.md +++ b/WindowsServerDocs/administration/windows-commands/doskey.md @@ -2,8 +2,8 @@ title: doskey description: Reference article for the doskey command and Doskey.exe, which recalls previously entered command-line commands, edits command lines, and creates macros. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- @@ -63,7 +63,7 @@ doskey [/reinstall] [/listsize=] [/macros:[all | ] [/history] [/i | END | Moves the insertion point to the end of the line. | | ESC | Clears the command from the display. | | F1 | Copies one character from a column in the template to the same column in the Command Prompt window. (The template is a memory buffer that holds the last command you typed.) | - | F2 | Searches forward in the template for the next key that you type after you press F2. Doskey.exe inserts the text from the template—up to, but not including, the character you specify. | + | F2 | Searches forward in the template for the next key that you type after you press F2. Doskey.exe inserts the text from the template up to, but not including, the character you specify. | | F3 | Copies the remainder of the template to the command line. Doskey.exe begins copying characters from the position in the template that corresponds to the position indicated by the insertion point on the command line. | | F4 | Deletes all characters from the current insertion point position up to, but not including, the next occurrence of the character that you type after you press F4. | | F5 | Copies the template into the current command line. | diff --git a/WindowsServerDocs/administration/windows-commands/driverquery.md b/WindowsServerDocs/administration/windows-commands/driverquery.md index 3d158b9d0b..fef3e101af 100644 --- a/WindowsServerDocs/administration/windows-commands/driverquery.md +++ b/WindowsServerDocs/administration/windows-commands/driverquery.md @@ -2,8 +2,8 @@ title: driverquery description: Reference article for the driverquery command, which enables an administrator to display a list of installed device drivers and their properties. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/dtrace.md b/WindowsServerDocs/administration/windows-commands/dtrace.md index 963dc4a70f..18c559a7a2 100644 --- a/WindowsServerDocs/administration/windows-commands/dtrace.md +++ b/WindowsServerDocs/administration/windows-commands/dtrace.md @@ -2,8 +2,8 @@ title: DTrace description: DTrace is a dynamic tracing framework that allows users to monitor and debug system performance for Windows and other operating systems. ms.topic: reference -author: xelu86 -ms.author: alalve +author: robinharwood +ms.author: roharwoo ms.date: 04/18/2024 --- diff --git a/WindowsServerDocs/administration/windows-commands/echo.md b/WindowsServerDocs/administration/windows-commands/echo.md index 7aa25b605b..f4d8b16b01 100644 --- a/WindowsServerDocs/administration/windows-commands/echo.md +++ b/WindowsServerDocs/administration/windows-commands/echo.md @@ -2,8 +2,8 @@ title: echo description: Reference article for the echo command, which displays messages or turns on or off the command echoing feature. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/02/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/edit.md b/WindowsServerDocs/administration/windows-commands/edit.md index 831012399f..45ce220793 100644 --- a/WindowsServerDocs/administration/windows-commands/edit.md +++ b/WindowsServerDocs/administration/windows-commands/edit.md @@ -2,8 +2,8 @@ title: edit description: Reference article for the edit command, which starts the MS-DOS Editor, so you can create and change ASCII text files. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood no-loc: [edit] ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/end-backup.md b/WindowsServerDocs/administration/windows-commands/end-backup.md index 6db7c7a0d2..f103b88ebc 100644 --- a/WindowsServerDocs/administration/windows-commands/end-backup.md +++ b/WindowsServerDocs/administration/windows-commands/end-backup.md @@ -2,8 +2,8 @@ title: end backup description: Reference article for the end backup command, which ends a full backup session and issues a **BackupComplete** event with the appropriate writer state, if needed. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/end-restore.md b/WindowsServerDocs/administration/windows-commands/end-restore.md index e59174f76d..e2f0776b97 100644 --- a/WindowsServerDocs/administration/windows-commands/end-restore.md +++ b/WindowsServerDocs/administration/windows-commands/end-restore.md @@ -2,8 +2,8 @@ title: end restore description: Reference article for the end restore command, which ends a restore session and issues a **PostRestore** event to involved writers. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/endlocal.md b/WindowsServerDocs/administration/windows-commands/endlocal.md index 7650a830de..ed66fd0886 100644 --- a/WindowsServerDocs/administration/windows-commands/endlocal.md +++ b/WindowsServerDocs/administration/windows-commands/endlocal.md @@ -2,8 +2,8 @@ title: endlocal description: Reference article for the endlocal command, which ends localization of environment changes in a batch file, and restores environment variables to their values before the corresponding setlocal command was run. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/erase.md b/WindowsServerDocs/administration/windows-commands/erase.md index f11efb538b..d311a71191 100644 --- a/WindowsServerDocs/administration/windows-commands/erase.md +++ b/WindowsServerDocs/administration/windows-commands/erase.md @@ -2,8 +2,8 @@ title: erase description: Reference article for the erase command, which deletes one or more files. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/eventcreate.md b/WindowsServerDocs/administration/windows-commands/eventcreate.md index f32a0b3a40..b1aa3721be 100644 --- a/WindowsServerDocs/administration/windows-commands/eventcreate.md +++ b/WindowsServerDocs/administration/windows-commands/eventcreate.md @@ -2,8 +2,8 @@ title: eventcreate description: Reference article for the eventcreate command, which enables an administrator to create a custom event in a specified event log. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/evntcmd.md b/WindowsServerDocs/administration/windows-commands/evntcmd.md index 02d5681e74..1c36581bc4 100644 --- a/WindowsServerDocs/administration/windows-commands/evntcmd.md +++ b/WindowsServerDocs/administration/windows-commands/evntcmd.md @@ -2,8 +2,8 @@ title: evntcmd description: Reference article for the evntcmd command, which configures the translation of events to traps, trap destinations, or both based on information in a configuration file. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/exec.md b/WindowsServerDocs/administration/windows-commands/exec.md index 3f7326a1e7..f8b3a0cdf2 100644 --- a/WindowsServerDocs/administration/windows-commands/exec.md +++ b/WindowsServerDocs/administration/windows-commands/exec.md @@ -2,8 +2,8 @@ title: exec description: Reference article for the exec command, which runs a script file on the local computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/exit-diskshadow.md b/WindowsServerDocs/administration/windows-commands/exit-diskshadow.md index 51b7c29f2d..7621a2d924 100644 --- a/WindowsServerDocs/administration/windows-commands/exit-diskshadow.md +++ b/WindowsServerDocs/administration/windows-commands/exit-diskshadow.md @@ -2,8 +2,8 @@ title: exit (diskshadow) description: Reference article for exit, which exits the DiskShadow command interpreter. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/12/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/exit.md b/WindowsServerDocs/administration/windows-commands/exit.md index d028b6b82b..e55703257a 100644 --- a/WindowsServerDocs/administration/windows-commands/exit.md +++ b/WindowsServerDocs/administration/windows-commands/exit.md @@ -2,8 +2,8 @@ title: exit description: Reference article for exit, which exits the diskpart command interpreter. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/12/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/expand-vdisk.md b/WindowsServerDocs/administration/windows-commands/expand-vdisk.md index f2ccaad242..e442039646 100644 --- a/WindowsServerDocs/administration/windows-commands/expand-vdisk.md +++ b/WindowsServerDocs/administration/windows-commands/expand-vdisk.md @@ -2,8 +2,8 @@ title: expand vdisk description: Reference article for the expand vdisk command, which expands a virtual hard disk (VHD) to a specified size. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/expand.md b/WindowsServerDocs/administration/windows-commands/expand.md index 4a277074b7..97cba8ac78 100644 --- a/WindowsServerDocs/administration/windows-commands/expand.md +++ b/WindowsServerDocs/administration/windows-commands/expand.md @@ -2,8 +2,8 @@ title: expand description: Reference article for the expand command, which expands one or more compressed files. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 11/01/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/expose.md b/WindowsServerDocs/administration/windows-commands/expose.md index ccdccb6be1..01f3b2d428 100644 --- a/WindowsServerDocs/administration/windows-commands/expose.md +++ b/WindowsServerDocs/administration/windows-commands/expose.md @@ -2,8 +2,8 @@ title: expose description: Reference article for the expose command, which exposes a persistent shadow copy as a drive letter, share, or mount point. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/extend.md b/WindowsServerDocs/administration/windows-commands/extend.md index 045e37bd4c..00131143c7 100644 --- a/WindowsServerDocs/administration/windows-commands/extend.md +++ b/WindowsServerDocs/administration/windows-commands/extend.md @@ -2,8 +2,8 @@ title: extend description: Reference article for the extend command, which extends the volume or partition with focus and its file system into free (unallocated) space on a disk. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/extract.md b/WindowsServerDocs/administration/windows-commands/extract.md index 15c81ee411..cb23592567 100644 --- a/WindowsServerDocs/administration/windows-commands/extract.md +++ b/WindowsServerDocs/administration/windows-commands/extract.md @@ -2,8 +2,8 @@ title: extract description: Reference article for the extract command, which extracts files from a source location. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 12/29/2020 --- diff --git a/WindowsServerDocs/administration/windows-commands/fc.md b/WindowsServerDocs/administration/windows-commands/fc.md index 774d9f45c0..e0d93b370f 100644 --- a/WindowsServerDocs/administration/windows-commands/fc.md +++ b/WindowsServerDocs/administration/windows-commands/fc.md @@ -2,8 +2,8 @@ title: fc description: Reference article for the fc command, which compares two files or sets of files and displays the differences between them. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/filesystems.md b/WindowsServerDocs/administration/windows-commands/filesystems.md index ee93a6400f..65de885ac8 100644 --- a/WindowsServerDocs/administration/windows-commands/filesystems.md +++ b/WindowsServerDocs/administration/windows-commands/filesystems.md @@ -2,8 +2,8 @@ title: filesystems description: Reference article for the filesystems command, which displays information about the current file system of the volume with focus and lists the file systems that are supported for formatting the volume. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/find.md b/WindowsServerDocs/administration/windows-commands/find.md index 90a6914ef6..019495a753 100644 --- a/WindowsServerDocs/administration/windows-commands/find.md +++ b/WindowsServerDocs/administration/windows-commands/find.md @@ -2,8 +2,8 @@ title: find description: Reference article for the find command, which searches for a string of text in files, displaying the specified text string in the file. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/findstr.md b/WindowsServerDocs/administration/windows-commands/findstr.md index 712b12dd95..33733e9b0f 100644 --- a/WindowsServerDocs/administration/windows-commands/findstr.md +++ b/WindowsServerDocs/administration/windows-commands/findstr.md @@ -2,8 +2,8 @@ title: findstr description: Reference article for the findstr command, which searches for patterns of text in files. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/finger.md b/WindowsServerDocs/administration/windows-commands/finger.md index dd46e344ee..02d04deefd 100644 --- a/WindowsServerDocs/administration/windows-commands/finger.md +++ b/WindowsServerDocs/administration/windows-commands/finger.md @@ -2,8 +2,8 @@ title: finger description: Reference article for the finger command, which displays information about users on a specified remote computer running the finger service or daemon. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/flattemp.md b/WindowsServerDocs/administration/windows-commands/flattemp.md index 27ebad0178..81ce3036f4 100644 --- a/WindowsServerDocs/administration/windows-commands/flattemp.md +++ b/WindowsServerDocs/administration/windows-commands/flattemp.md @@ -2,8 +2,8 @@ title: flattemp description: Reference article for the flattemp command, which enables or disables flat temporary folders. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fondue.md b/WindowsServerDocs/administration/windows-commands/fondue.md index 6357d6251c..4bc8294f6a 100644 --- a/WindowsServerDocs/administration/windows-commands/fondue.md +++ b/WindowsServerDocs/administration/windows-commands/fondue.md @@ -2,8 +2,8 @@ title: fondue description: Reference article for the fondue command, which enables Windows optional features by downloading required files from Windows Update or another source specified by Group Policy. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/for.md b/WindowsServerDocs/administration/windows-commands/for.md index f71a4dfd29..9357d52266 100644 --- a/WindowsServerDocs/administration/windows-commands/for.md +++ b/WindowsServerDocs/administration/windows-commands/for.md @@ -2,8 +2,8 @@ title: for description: Reference article for the for command, which runs a specified command for each file, within a set of files. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/04/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/forfiles.md b/WindowsServerDocs/administration/windows-commands/forfiles.md index df23f27004..0d419e801a 100644 --- a/WindowsServerDocs/administration/windows-commands/forfiles.md +++ b/WindowsServerDocs/administration/windows-commands/forfiles.md @@ -2,8 +2,8 @@ title: forfiles description: Reference article for forfiles command, which selects and runs a command on a file or set of files. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 05/20/2020 --- diff --git a/WindowsServerDocs/administration/windows-commands/format.md b/WindowsServerDocs/administration/windows-commands/format.md index d1e8264a69..eff5313a4e 100644 --- a/WindowsServerDocs/administration/windows-commands/format.md +++ b/WindowsServerDocs/administration/windows-commands/format.md @@ -1,9 +1,9 @@ --- title: format description: Reference article for the format command that formats a drive to accept Windows files. -ms.author: alalve +ms.author: roharwoo ms.topic: reference -author: xelu86 +author: robinharwood ms.date: 09/28/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/freedisk.md b/WindowsServerDocs/administration/windows-commands/freedisk.md index 0d402ded58..af6ef705c0 100644 --- a/WindowsServerDocs/administration/windows-commands/freedisk.md +++ b/WindowsServerDocs/administration/windows-commands/freedisk.md @@ -2,8 +2,8 @@ title: freedisk description: Reference article for the freedisk command, which checks to see if the specified amount of disk space is available before continuing with an installation process. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-8dot3name.md b/WindowsServerDocs/administration/windows-commands/fsutil-8dot3name.md index f929ffd8fc..22ae160116 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-8dot3name.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-8dot3name.md @@ -1,8 +1,8 @@ --- title: fsutil 8dot3name description: Reference article for the fsutil 8dot3name command, which queries or changes the settings for short name (8dot3 name) behavior. -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.topic: reference ms.date: 11/22/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-behavior.md b/WindowsServerDocs/administration/windows-commands/fsutil-behavior.md index 51bebfa802..9ee2c3b213 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-behavior.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-behavior.md @@ -1,8 +1,8 @@ --- title: fsutil behavior description: Reference article for the fsutil behavior command, which queries or sets NTFS volume behavior. -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-clfs.md b/WindowsServerDocs/administration/windows-commands/fsutil-clfs.md index bf7e359989..daa49f59eb 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-clfs.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-clfs.md @@ -1,8 +1,8 @@ --- title: fsutil clfs description: Reference article for the fsutil clfs command. -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.topic: reference ms.date: 03/04/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-dirty.md b/WindowsServerDocs/administration/windows-commands/fsutil-dirty.md index 207191f7c1..3476126649 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-dirty.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-dirty.md @@ -1,8 +1,8 @@ --- title: fsutil dirty description: Reference article for the fsutil dirty command, which queries or sets a volume's dirty bit. -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-file.md b/WindowsServerDocs/administration/windows-commands/fsutil-file.md index 34d2b7c5e3..2494f0b0a1 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-file.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-file.md @@ -1,8 +1,8 @@ --- title: fsutil file description: Reference article for the fsutil file command, which finds a file by user name, queries allocated ranges for a file, sets a file's short name, sets a file's valid data length, sets zero data for a file, or creates a new file. -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-fsinfo.md b/WindowsServerDocs/administration/windows-commands/fsutil-fsinfo.md index df89104383..9029e26592 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-fsinfo.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-fsinfo.md @@ -1,8 +1,8 @@ --- title: Fsutil fsinfo description: Reference article for the fsutil fsinfo command, which lists all drives, queries the drive type, queries volume information, queries NTFS-specific volume information, or queries file system statistics. -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-hardlink.md b/WindowsServerDocs/administration/windows-commands/fsutil-hardlink.md index c9ee034148..a4ad9dbf34 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-hardlink.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-hardlink.md @@ -1,8 +1,8 @@ --- title: fsutil hardlink description: Reference article for the fsutil hardlink command, which creates a hard link between an existing file and a new file. -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-objectid.md b/WindowsServerDocs/administration/windows-commands/fsutil-objectid.md index f2856b062a..2d1aa72c44 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-objectid.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-objectid.md @@ -1,8 +1,8 @@ --- title: fsutil objectid description: Reference article for the fsutil objectid command, which manages object identifiers to track other objects such as files, directories, and links. -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-quota.md b/WindowsServerDocs/administration/windows-commands/fsutil-quota.md index d242f8e8ad..50655504a2 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-quota.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-quota.md @@ -1,8 +1,8 @@ --- title: fsutil quota description: Reference article for the fsutil quota command, which manages disk quotas on NTFS volumes to provide more precise control of network-based storage. -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-repair.md b/WindowsServerDocs/administration/windows-commands/fsutil-repair.md index 6721f83b0a..e195ec20d6 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-repair.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-repair.md @@ -1,8 +1,8 @@ --- title: fsutil repair description: Reference article for the fsutil repair command, which administers and monitors NTFS self-healing repair operations. -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-reparsepoint.md b/WindowsServerDocs/administration/windows-commands/fsutil-reparsepoint.md index 89307d3b73..f9a871dde5 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-reparsepoint.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-reparsepoint.md @@ -1,8 +1,8 @@ --- title: fsutil reparsepoint description: Reference article for the fsutil reparsepoint command, which queries or deletes reparse points. -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-resource.md b/WindowsServerDocs/administration/windows-commands/fsutil-resource.md index ba7281a620..4394ad6edf 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-resource.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-resource.md @@ -1,8 +1,8 @@ --- title: fsutil resource description: Reference article for the fsutil resource command, which manages a Transactional Resource Manager and its behavior. -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-sparse.md b/WindowsServerDocs/administration/windows-commands/fsutil-sparse.md index b43796ad73..be886814ca 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-sparse.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-sparse.md @@ -1,8 +1,8 @@ --- title: fsutil sparse description: Reference article for the fsutil sparse command, which manages sparse files. -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-tiering.md b/WindowsServerDocs/administration/windows-commands/fsutil-tiering.md index b21b57f11a..1cd380ec16 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-tiering.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-tiering.md @@ -1,8 +1,8 @@ --- title: fsutil tiering description: Reference article for the fsutil tiering command, which enables management of storage tier functions, such as setting and disabling flags and listing of tiers. -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-transaction.md b/WindowsServerDocs/administration/windows-commands/fsutil-transaction.md index ae49459fc5..9894fad516 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-transaction.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-transaction.md @@ -1,8 +1,8 @@ --- title: fsutil transaction description: Reference article for the fsutil transaction command, which manages NTFS transactions. -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-usn.md b/WindowsServerDocs/administration/windows-commands/fsutil-usn.md index f91c8851ba..54ae7eecb1 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-usn.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-usn.md @@ -1,8 +1,8 @@ --- title: fsutil usn description: Reference article for the fsutil usn command, which manages the update sequence number (USN) change journal. -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-volume.md b/WindowsServerDocs/administration/windows-commands/fsutil-volume.md index 6ba3f4eb2d..904c613d6c 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-volume.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-volume.md @@ -1,8 +1,8 @@ --- title: fsutil volume description: Reference article for the fsutil volume command, which dismounts a volume, or queries the hard disk drive to determine how much free space is currently available on the hard disk drive or which file is using a particular cluster. -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.topic: reference ms.date: 10/16/2017 --- @@ -21,7 +21,7 @@ fsutil volume [diskfree] fsutil volume [dismount] fsutil volume [filelayout] fsutil volume [list] -fsutil volume [querycluster] [] … … +fsutil volume [querycluster] [] … ``` ### Parameters diff --git a/WindowsServerDocs/administration/windows-commands/fsutil-wim.md b/WindowsServerDocs/administration/windows-commands/fsutil-wim.md index 3fc2f05c3c..b304bfb77b 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil-wim.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil-wim.md @@ -1,8 +1,8 @@ --- title: fsutil wim description: Reference article for the fsutil wim command, which provides functions to discover and manage Windows Image (WIM)-backed files. -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.topic: reference ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fsutil.md b/WindowsServerDocs/administration/windows-commands/fsutil.md index 5bfbb7d1de..c24900c7d3 100644 --- a/WindowsServerDocs/administration/windows-commands/fsutil.md +++ b/WindowsServerDocs/administration/windows-commands/fsutil.md @@ -1,8 +1,8 @@ --- title: fsutil description: Reference article for the fsutil command, which performs tasks that are related to file allocation table (FAT) and NTFS file systems. -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.topic: reference ms.date: 03/04/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-append.md b/WindowsServerDocs/administration/windows-commands/ftp-append.md index 7831b7d2cc..5fd6266069 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-append.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-append.md @@ -2,8 +2,8 @@ title: ftp append description: Reference article for the ftp append command, which appends a local file to a file on the remote computer using the current file type setting. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-ascii.md b/WindowsServerDocs/administration/windows-commands/ftp-ascii.md index 3fcddd8518..6d88251265 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-ascii.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-ascii.md @@ -2,8 +2,8 @@ title: ftp ascii description: Reference article for the ftp ascii command, which sets the file transfer type to ASCII. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-bell_1.md b/WindowsServerDocs/administration/windows-commands/ftp-bell_1.md index e2749d55c2..822850b633 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-bell_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-bell_1.md @@ -2,8 +2,8 @@ title: ftp bell description: Reference article for the ftp bell command, which toggles an audible sound to occur after each file transfer command is completed. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-binary.md b/WindowsServerDocs/administration/windows-commands/ftp-binary.md index 944c971b8b..b76a270cf8 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-binary.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-binary.md @@ -2,8 +2,8 @@ title: ftp binary description: Reference article for the ftp binary command, which sets the file transfer type to binary. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-bye.md b/WindowsServerDocs/administration/windows-commands/ftp-bye.md index f29f584730..957565cc65 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-bye.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-bye.md @@ -2,8 +2,8 @@ title: ftp bye description: Reference article for the ftp bye command, which ends the ftp session on the remote computer, and then exits. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-cd.md b/WindowsServerDocs/administration/windows-commands/ftp-cd.md index 11782b0caf..33757543d0 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-cd.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-cd.md @@ -2,8 +2,8 @@ title: ftp cd description: Reference article for the ftp cd command, which changes the working directory on the remote computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-close_1.md b/WindowsServerDocs/administration/windows-commands/ftp-close_1.md index 38a95bba8b..aae6ca9a4d 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-close_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-close_1.md @@ -2,8 +2,8 @@ title: ftp close description: Reference article for the ftp close command, which ends the ftp session with the remote server and remains at the ftp prompt. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-debug.md b/WindowsServerDocs/administration/windows-commands/ftp-debug.md index a3e5df7ad7..335093f0c8 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-debug.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-debug.md @@ -2,8 +2,8 @@ title: ftp debug description: Reference article for the ftp debug command, which toggles Debugging mode. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-delete.md b/WindowsServerDocs/administration/windows-commands/ftp-delete.md index eafec6c69f..eea14eb6ba 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-delete.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-delete.md @@ -2,8 +2,8 @@ title: ftp delete description: Reference article for the ftp delete command, which deletes files on remote computers. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-dir.md b/WindowsServerDocs/administration/windows-commands/ftp-dir.md index 264ef5053c..ac34c10d89 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-dir.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-dir.md @@ -2,8 +2,8 @@ title: ftp dir description: Reference article for the ftp dir command, which displays a list of directory files and subdirectories on a remote computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-disconnect_1.md b/WindowsServerDocs/administration/windows-commands/ftp-disconnect_1.md index 0ee65e31af..2eb801989d 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-disconnect_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-disconnect_1.md @@ -2,8 +2,8 @@ title: ftp disconnect description: Reference article for the ftp disconnect command, which disconnects from the remote computer and retains the ftp prompt. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-get.md b/WindowsServerDocs/administration/windows-commands/ftp-get.md index c43cd6d8ad..ad92ba3c71 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-get.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-get.md @@ -2,8 +2,8 @@ title: ftp get description: Reference article for the ftp get command, which copies a remote file to the local computer using the current file transfer type. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-glob_1.md b/WindowsServerDocs/administration/windows-commands/ftp-glob_1.md index 54686b00c6..401ca70285 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-glob_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-glob_1.md @@ -2,8 +2,8 @@ title: ftp glob description: Reference article for the ftp glob command, which toggles allowing wildcard expansion for local file names. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-hash_1.md b/WindowsServerDocs/administration/windows-commands/ftp-hash_1.md index 9b0b7faa9a..9440da0c47 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-hash_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-hash_1.md @@ -2,8 +2,8 @@ title: ftp hash description: Reference article for the ftp hash command, which toggles number sign (#) printing for each transferred data block. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-lcd.md b/WindowsServerDocs/administration/windows-commands/ftp-lcd.md index 6d6da22708..b874586ac4 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-lcd.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-lcd.md @@ -2,8 +2,8 @@ title: ftp lcd description: Reference article for the ftp lcd command, which changes the working directory on the local computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-literal_1.md b/WindowsServerDocs/administration/windows-commands/ftp-literal_1.md index 7e03f6a246..7a8db4c3c5 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-literal_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-literal_1.md @@ -2,8 +2,8 @@ title: ftp literal description: Reference article for the ftp literal command, which sends verbatim arguments to the remote ftp server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-ls_1.md b/WindowsServerDocs/administration/windows-commands/ftp-ls_1.md index b9d1e4c785..190ecb4f2e 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-ls_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-ls_1.md @@ -2,8 +2,8 @@ title: ftp ls description: Reference article for the ftp ls command, which displays an abbreviated list of files and subdirectories from the remote computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-mget.md b/WindowsServerDocs/administration/windows-commands/ftp-mget.md index 2f918ec956..65f5d21e45 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-mget.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-mget.md @@ -2,8 +2,8 @@ title: ftp mget description: Reference article for the ftp mget command, which copies remote files to the local computer using the current file transfer type. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-mkdir.md b/WindowsServerDocs/administration/windows-commands/ftp-mkdir.md index 8b0a84b2eb..4ac75a80da 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-mkdir.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-mkdir.md @@ -2,8 +2,8 @@ title: ftp mkdir description: Reference article for the ftp mkdir command, which creates a directory on the remote computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-mls_1.md b/WindowsServerDocs/administration/windows-commands/ftp-mls_1.md index 640a755c28..d8c0616630 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-mls_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-mls_1.md @@ -2,8 +2,8 @@ title: ftp mls description: Reference article for the ftp mls command, which displays an abbreviated list of files and subdirectories in a remote directory. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-mput_1.md b/WindowsServerDocs/administration/windows-commands/ftp-mput_1.md index 55fad9cde8..2b23e36b47 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-mput_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-mput_1.md @@ -2,8 +2,8 @@ title: ftp mput description: Reference article for the ftp mput command, which copies local files to the remote computer using the current file transfer type. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-open_1.md b/WindowsServerDocs/administration/windows-commands/ftp-open_1.md index d7ceea2830..c3e22f7a47 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-open_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-open_1.md @@ -2,8 +2,8 @@ title: ftp open description: Reference article for the ftp open command, which connects to the specified ftp server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-prompt_1.md b/WindowsServerDocs/administration/windows-commands/ftp-prompt_1.md index 5e9d985f4f..886d5f3fba 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-prompt_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-prompt_1.md @@ -2,8 +2,8 @@ title: ftp prompt description: Reference article for the ftp prompt command, which toggles Prompt mode on and off. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-put.md b/WindowsServerDocs/administration/windows-commands/ftp-put.md index 29c48ba023..4e0c25ff1f 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-put.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-put.md @@ -2,8 +2,8 @@ title: ftp put description: Reference article for the ftp put command, which copies a local file to the remote computer using the current file transfer type. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 03/30/2020 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-pwd_1.md b/WindowsServerDocs/administration/windows-commands/ftp-pwd_1.md index 2f324f4c08..88888f4615 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-pwd_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-pwd_1.md @@ -2,8 +2,8 @@ title: ftp pwd description: Reference article for the ftp pwd command, which displays the current remote computer directory. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-quit.md b/WindowsServerDocs/administration/windows-commands/ftp-quit.md index b4f5732369..ab9ff1618d 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-quit.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-quit.md @@ -2,8 +2,8 @@ title: ftp quit description: Reference article for the ftp quit command, which ends the ftp session with the remote computer, and then exits. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-quote.md b/WindowsServerDocs/administration/windows-commands/ftp-quote.md index 2c6a605872..c3a2248a2e 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-quote.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-quote.md @@ -2,8 +2,8 @@ title: ftp quote description: Reference article for the ftp quote command, which sends verbatim arguments to the remote ftp server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-recv.md b/WindowsServerDocs/administration/windows-commands/ftp-recv.md index 26b6926d5e..cbd34419d6 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-recv.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-recv.md @@ -2,8 +2,8 @@ title: ftp recv description: Reference article for the ftp recv command, which copies a remote file to the local computer using the current file transfer type. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-remotehelp_1.md b/WindowsServerDocs/administration/windows-commands/ftp-remotehelp_1.md index 810b6b95ee..19b9bec047 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-remotehelp_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-remotehelp_1.md @@ -2,8 +2,8 @@ title: ftp remotehelp description: Reference article for the ftp remotehelp command, which displays help for remote commands. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-rename.md b/WindowsServerDocs/administration/windows-commands/ftp-rename.md index dafde964eb..d1105c2892 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-rename.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-rename.md @@ -2,8 +2,8 @@ title: ftp rename description: Reference article for the ftp rename command, which renames remote files. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-rmdir.md b/WindowsServerDocs/administration/windows-commands/ftp-rmdir.md index e43fe95ea3..f5990290df 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-rmdir.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-rmdir.md @@ -2,8 +2,8 @@ title: ftp rmdir description: Reference article for the ftp rmdir command, which deletes a root directory. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-send_1.md b/WindowsServerDocs/administration/windows-commands/ftp-send_1.md index 220199a983..ac7afc0190 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-send_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-send_1.md @@ -2,8 +2,8 @@ title: ftp send description: Reference article for the ftp send command, which copies a local file to the remote computer using the current file transfer type. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-status.md b/WindowsServerDocs/administration/windows-commands/ftp-status.md index 64fafdbeaf..a8ea9b022e 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-status.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-status.md @@ -2,8 +2,8 @@ title: ftp status description: Reference article for the ftp status command, which displays the current status of your ftp connections. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-trace_1.md b/WindowsServerDocs/administration/windows-commands/ftp-trace_1.md index 83a49cf82b..878baba1c0 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-trace_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-trace_1.md @@ -2,8 +2,8 @@ title: ftp trace description: Reference article for the ftp trace command, which toggles packet tracing. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-type.md b/WindowsServerDocs/administration/windows-commands/ftp-type.md index 4bc9d01453..fc174a1f72 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-type.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-type.md @@ -2,8 +2,8 @@ title: ftp type description: Reference article for the ftp type command, which sets or displays the file transfer type. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-user.md b/WindowsServerDocs/administration/windows-commands/ftp-user.md index 9f6ea1f459..705207c506 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-user.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-user.md @@ -2,8 +2,8 @@ title: ftp user description: Reference article for the ftp user command, which specifies a user to the remote computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp-verbose_1.md b/WindowsServerDocs/administration/windows-commands/ftp-verbose_1.md index 817820661e..cd03a34e5a 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp-verbose_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp-verbose_1.md @@ -2,8 +2,8 @@ title: ftp verbose description: Reference article for the ftp verbose command, which toggles verbose mode. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp.md b/WindowsServerDocs/administration/windows-commands/ftp.md index 1773df903e..daf989695d 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp.md +++ b/WindowsServerDocs/administration/windows-commands/ftp.md @@ -2,8 +2,8 @@ title: ftp description: Reference article for the ftp command, which transfers files to and from a computer running a File Transfer Protocol (ftp) server service. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/17/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp.mdelete_1.md b/WindowsServerDocs/administration/windows-commands/ftp.mdelete_1.md index 76ce6f7565..db8cd10d56 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp.mdelete_1.md +++ b/WindowsServerDocs/administration/windows-commands/ftp.mdelete_1.md @@ -2,8 +2,8 @@ title: ftp mdelete description: Reference article for the ftp mdelete command, which deletes files on the remote computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftp.mdir.md b/WindowsServerDocs/administration/windows-commands/ftp.mdir.md index efbf1b82c4..a96bb5a518 100644 --- a/WindowsServerDocs/administration/windows-commands/ftp.mdir.md +++ b/WindowsServerDocs/administration/windows-commands/ftp.mdir.md @@ -2,8 +2,8 @@ title: ftp mdir description: Reference article for the ftp mdir command, which displays a directory list of files and subdirectories in a remote directory. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ftype.md b/WindowsServerDocs/administration/windows-commands/ftype.md index 51c12f88d9..e81f1e3881 100644 --- a/WindowsServerDocs/administration/windows-commands/ftype.md +++ b/WindowsServerDocs/administration/windows-commands/ftype.md @@ -2,8 +2,8 @@ title: ftype description: Reference article for the ftype command, which displays or modifies file type used in file name extension associations. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/fveupdate.md b/WindowsServerDocs/administration/windows-commands/fveupdate.md index 4042f5558d..7d82a00ad4 100644 --- a/WindowsServerDocs/administration/windows-commands/fveupdate.md +++ b/WindowsServerDocs/administration/windows-commands/fveupdate.md @@ -2,8 +2,8 @@ title: fveupdate description: Reference article for the fveupdate tool, which is an internal tool used by the setup program when a computer is upgraded. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/getmac.md b/WindowsServerDocs/administration/windows-commands/getmac.md index d897ee53ba..a8f798d0db 100644 --- a/WindowsServerDocs/administration/windows-commands/getmac.md +++ b/WindowsServerDocs/administration/windows-commands/getmac.md @@ -2,8 +2,8 @@ title: getmac description: Reference article for the getmac command, which returns the media access control (MAC) address and the list of network protocols associated with each, locally or across a network. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/gettype.md b/WindowsServerDocs/administration/windows-commands/gettype.md index 269926f26b..e0004c04c7 100644 --- a/WindowsServerDocs/administration/windows-commands/gettype.md +++ b/WindowsServerDocs/administration/windows-commands/gettype.md @@ -2,8 +2,8 @@ title: gettype description: Reference article for the gettype command. This command is deprecated and may not be supported in future releases of Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 04/01/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/goto.md b/WindowsServerDocs/administration/windows-commands/goto.md index 6e9f351bf9..0255e7fb6d 100644 --- a/WindowsServerDocs/administration/windows-commands/goto.md +++ b/WindowsServerDocs/administration/windows-commands/goto.md @@ -2,8 +2,8 @@ title: goto description: Reference article for the goto command, which directs cmd.exe to a labeled line in a batch program. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/gpfixup.md b/WindowsServerDocs/administration/windows-commands/gpfixup.md index 38cae992df..b5cbce7a0e 100644 --- a/WindowsServerDocs/administration/windows-commands/gpfixup.md +++ b/WindowsServerDocs/administration/windows-commands/gpfixup.md @@ -2,8 +2,8 @@ title: gpfixup description: Reference article for the gpfixup command, which fixes domain name dependencies in Group Policy Objects and Group Policy links after a domain rename operation. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/gpresult.md b/WindowsServerDocs/administration/windows-commands/gpresult.md index ba2446649a..07bf6f2625 100644 --- a/WindowsServerDocs/administration/windows-commands/gpresult.md +++ b/WindowsServerDocs/administration/windows-commands/gpresult.md @@ -2,8 +2,8 @@ title: gpresult description: Reference article for the gpresult command, which displays the Resultant Set of Policy (RSoP) information for a remote user and computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 09/28/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/gpt.md b/WindowsServerDocs/administration/windows-commands/gpt.md index 35295d12b7..cfedef4565 100644 --- a/WindowsServerDocs/administration/windows-commands/gpt.md +++ b/WindowsServerDocs/administration/windows-commands/gpt.md @@ -2,8 +2,8 @@ title: gpt description: Reference article for the gpt command, which assigns the gpt attribute(s) to the partition with focus. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/gpupdate.md b/WindowsServerDocs/administration/windows-commands/gpupdate.md index 2b3906e8f4..4da1f16bfe 100644 --- a/WindowsServerDocs/administration/windows-commands/gpupdate.md +++ b/WindowsServerDocs/administration/windows-commands/gpupdate.md @@ -2,8 +2,8 @@ title: gpupdate description: Reference article for the gpupdate command, which updates Group Policy settings. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/graftabl.md b/WindowsServerDocs/administration/windows-commands/graftabl.md index 2f47a32f93..9092761467 100644 --- a/WindowsServerDocs/administration/windows-commands/graftabl.md +++ b/WindowsServerDocs/administration/windows-commands/graftabl.md @@ -2,8 +2,8 @@ title: graftabl description: Reference article for the graftabl command, which enables Windows operating systems to display an extended character set in graphics mode. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/help.md b/WindowsServerDocs/administration/windows-commands/help.md index 21311f2f4c..48ec6934fc 100644 --- a/WindowsServerDocs/administration/windows-commands/help.md +++ b/WindowsServerDocs/administration/windows-commands/help.md @@ -2,8 +2,8 @@ title: help description: Reference article for the help command, which displays a list of the available commands or detailed help information on a specified command. ms.topic: reference -author: meaghanlewis -ms.author: mosagie +author: robinharwood +ms.author: roharwoo ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/helpctr.md b/WindowsServerDocs/administration/windows-commands/helpctr.md index 53d7175561..dc63517f6b 100644 --- a/WindowsServerDocs/administration/windows-commands/helpctr.md +++ b/WindowsServerDocs/administration/windows-commands/helpctr.md @@ -2,8 +2,8 @@ title: helpctr description: Reference article for the helpctr command. This command has been deprecated and isn't guaranteed to be supported in future releases of Windows. ms.topic: reference -author: meaghanlewis -ms.author: mosagie +author: robinharwood +ms.author: roharwoo ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/hostname.md b/WindowsServerDocs/administration/windows-commands/hostname.md index b64be34980..5c808de503 100644 --- a/WindowsServerDocs/administration/windows-commands/hostname.md +++ b/WindowsServerDocs/administration/windows-commands/hostname.md @@ -2,8 +2,8 @@ title: hostname description: Reference article for the hostname command, which displays the host name portion of the full computer name of the computer. ms.topic: reference -author: meaghanlewis -ms.author: mosagie +author: robinharwood +ms.author: roharwoo ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/icacls.md b/WindowsServerDocs/administration/windows-commands/icacls.md index b340348208..616ff455a8 100644 --- a/WindowsServerDocs/administration/windows-commands/icacls.md +++ b/WindowsServerDocs/administration/windows-commands/icacls.md @@ -2,8 +2,8 @@ title: icacls description: Reference article for the icacls command, which displays or modifies discretionary access control lists (DACL) on specified files, and applies stored DACLs to files in specified directories. ms.topic: reference -author: meaghanlewis -ms.author: mosagie +author: dknappettmsft +ms.author: daknappe ms.date: 06/06/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/if.md b/WindowsServerDocs/administration/windows-commands/if.md index a5fe1802b4..56be83201a 100644 --- a/WindowsServerDocs/administration/windows-commands/if.md +++ b/WindowsServerDocs/administration/windows-commands/if.md @@ -2,8 +2,8 @@ title: if description: Reference article for the if command, which performs conditional processing in batch programs. ms.topic: reference -author: meaghanlewis -ms.author: mosagie +author: robinharwood +ms.author: roharwoo ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/import.md b/WindowsServerDocs/administration/windows-commands/import.md index a07ecb4f2c..b6ca6f5857 100644 --- a/WindowsServerDocs/administration/windows-commands/import.md +++ b/WindowsServerDocs/administration/windows-commands/import.md @@ -2,8 +2,8 @@ title: import diskshadow description: Reference article for the import command, which imports a transportable shadow copy from a loaded metadata file into the system. ms.topic: reference -author: meaghanlewis -ms.author: mosagie +author: robinharwood +ms.author: roharwoo ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/import_1.md b/WindowsServerDocs/administration/windows-commands/import_1.md index dbce71f409..10ade00906 100644 --- a/WindowsServerDocs/administration/windows-commands/import_1.md +++ b/WindowsServerDocs/administration/windows-commands/import_1.md @@ -2,8 +2,8 @@ title: import diskpart description: Reference article for the import command, which imports a foreign disk group into the disk group of the local computer. ms.topic: reference -author: meaghanlewis -ms.author: mosagie +author: robinharwood +ms.author: roharwoo ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/inactive.md b/WindowsServerDocs/administration/windows-commands/inactive.md index 00337f34f0..e3b655897f 100644 --- a/WindowsServerDocs/administration/windows-commands/inactive.md +++ b/WindowsServerDocs/administration/windows-commands/inactive.md @@ -2,8 +2,8 @@ title: inactive description: Reference article for the inactive command, which marks the system partition or boot partition with focus as inactive on basic master boot record (MBR) disks. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ipconfig.md b/WindowsServerDocs/administration/windows-commands/ipconfig.md index 18dd7f12f1..55f301da2a 100644 --- a/WindowsServerDocs/administration/windows-commands/ipconfig.md +++ b/WindowsServerDocs/administration/windows-commands/ipconfig.md @@ -2,8 +2,8 @@ title: ipconfig description: Reference article for the ipconfig command, which displays all current TCP/IP network configuration values and refreshes Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) settings. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ipxroute.md b/WindowsServerDocs/administration/windows-commands/ipxroute.md index 032950f795..4d03c02ef3 100644 --- a/WindowsServerDocs/administration/windows-commands/ipxroute.md +++ b/WindowsServerDocs/administration/windows-commands/ipxroute.md @@ -2,8 +2,8 @@ title: ipxroute description: Reference article for the ipxroute command, which displays and modifies information about the routing tables used by the IPX protocol. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/irftp.md b/WindowsServerDocs/administration/windows-commands/irftp.md index 390a838fa9..d17c43bdf9 100644 --- a/WindowsServerDocs/administration/windows-commands/irftp.md +++ b/WindowsServerDocs/administration/windows-commands/irftp.md @@ -2,8 +2,8 @@ title: irftp description: Reference article for the irftp command, which sends files over an infrared link. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/jetpack.md b/WindowsServerDocs/administration/windows-commands/jetpack.md index af6763788e..9655b7867d 100644 --- a/WindowsServerDocs/administration/windows-commands/jetpack.md +++ b/WindowsServerDocs/administration/windows-commands/jetpack.md @@ -2,8 +2,8 @@ title: jetpack description: Reference article for the jetpack command, which compacts a Windows Internet Name Service (WINS) or Dynamic Host Configuration Protocol (DHCP) database. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/klist.md b/WindowsServerDocs/administration/windows-commands/klist.md index 1659af540f..cf311caa27 100644 --- a/WindowsServerDocs/administration/windows-commands/klist.md +++ b/WindowsServerDocs/administration/windows-commands/klist.md @@ -2,8 +2,8 @@ title: klist description: Reference article for the klist command, which displays a list of currently cached Kerberos tickets. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-addenctypeattr.md b/WindowsServerDocs/administration/windows-commands/ksetup-addenctypeattr.md index c6f76cf9fd..ad40d0744c 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-addenctypeattr.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-addenctypeattr.md @@ -2,8 +2,8 @@ title: ksetup addenctypeattr description: Reference article for the ksetup addenctypeattr command, which adds the encryption type attribute to the list of possible types for the domain. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-addhosttorealmmap.md b/WindowsServerDocs/administration/windows-commands/ksetup-addhosttorealmmap.md index 7ac1ab45ea..a817ae228c 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-addhosttorealmmap.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-addhosttorealmmap.md @@ -2,8 +2,8 @@ title: ksetup addhosttorealmmap description: Reference article for the ksetup addhosttorealmmap command, which adds a service principal name (SPN) mapping between the stated host and the realm. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-addkdc.md b/WindowsServerDocs/administration/windows-commands/ksetup-addkdc.md index e764d30a2b..0bb07c9f7a 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-addkdc.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-addkdc.md @@ -2,8 +2,8 @@ title: ksetup addkdc description: Reference article for the ksetup addkdc command, which ads a Key Distribution Center (KDC) address for the given Kerberos realm. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-addkpasswd.md b/WindowsServerDocs/administration/windows-commands/ksetup-addkpasswd.md index b8ecd0d357..072ef02e43 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-addkpasswd.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-addkpasswd.md @@ -2,8 +2,8 @@ title: ksetup addkpasswd description: Reference article for the ksetup addkpasswd command, which adds a Kerberos password (kpasswd) server address for a realm. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-addrealmflags.md b/WindowsServerDocs/administration/windows-commands/ksetup-addrealmflags.md index 55ad8f9305..2c13d9a7f4 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-addrealmflags.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-addrealmflags.md @@ -2,8 +2,8 @@ title: ksetup addrealmflags description: Reference article for the ksetup addrealmflags command that adds other realm flags to a specified realm. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 04/01/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-changepassword.md b/WindowsServerDocs/administration/windows-commands/ksetup-changepassword.md index a1ec6c62af..6f02ff2087 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-changepassword.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-changepassword.md @@ -2,8 +2,8 @@ title: ksetup changepassword description: Reference article for the ksetup changepassword command, which uses the Key Distribution Center (KDC) password (kpasswd) value to change the password of the logged-on user. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-delenctypeattr.md b/WindowsServerDocs/administration/windows-commands/ksetup-delenctypeattr.md index 73db609b2f..355681420f 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-delenctypeattr.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-delenctypeattr.md @@ -2,8 +2,8 @@ title: ksetup delenctypeattr description: Reference article for the ksetup delenctypeattr, which removes the encryption type attribute for the domain. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-delhosttorealmmap.md b/WindowsServerDocs/administration/windows-commands/ksetup-delhosttorealmmap.md index a825d1b0ae..211909280e 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-delhosttorealmmap.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-delhosttorealmmap.md @@ -2,8 +2,8 @@ title: ksetup delhosttorealmmap description: Reference article for the ksetup delhosttorealmmap command, which removes a service principal name (SPN) mapping between the stated host and the realm. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-delkdc.md b/WindowsServerDocs/administration/windows-commands/ksetup-delkdc.md index d7cf70c8b0..48ae717c01 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-delkdc.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-delkdc.md @@ -2,8 +2,8 @@ title: ksetup delkdc description: Reference article for the ksetup delkdc command, which deletes instances of Key Distribution Center (KDC) names for the Kerberos realm. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-delkpasswd.md b/WindowsServerDocs/administration/windows-commands/ksetup-delkpasswd.md index e6bc4adb92..0050b530a0 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-delkpasswd.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-delkpasswd.md @@ -2,8 +2,8 @@ title: ksetup delkpasswd description: Reference article for the ksetup delkpasswd command, which removes a Kerberos password server (kpasswd) for a realm. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-delrealmflags.md b/WindowsServerDocs/administration/windows-commands/ksetup-delrealmflags.md index db2d06dedb..26577b91ff 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-delrealmflags.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-delrealmflags.md @@ -2,8 +2,8 @@ title: ksetup delrealmflags description: Reference article for the ksetup delrealmflags command, which removes realm flags from the specified realm. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-domain.md b/WindowsServerDocs/administration/windows-commands/ksetup-domain.md index d3a043e43e..59a0551c13 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-domain.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-domain.md @@ -2,8 +2,8 @@ title: ksetup domain description: Reference article for the ksetup domain command, which sets the domain name for all Kerberos operations. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-dumpstate.md b/WindowsServerDocs/administration/windows-commands/ksetup-dumpstate.md index 01a3763398..f13a015903 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-dumpstate.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-dumpstate.md @@ -2,8 +2,8 @@ title: ksetup dumpstate description: Reference article for the ksetup dumpstate command, which displays the current state of realm settings for all realms that are defined on the computer. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-getenctypeattr.md b/WindowsServerDocs/administration/windows-commands/ksetup-getenctypeattr.md index 29d1a7cabe..80f1b20206 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-getenctypeattr.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-getenctypeattr.md @@ -2,8 +2,8 @@ title: ksetup getenctypeattr description: Reference article for the ksetup getenctypeattr command, which retrieves the encryption type attribute for the domain. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-listrealmflags.md b/WindowsServerDocs/administration/windows-commands/ksetup-listrealmflags.md index d8b7424f53..2cf36e84f0 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-listrealmflags.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-listrealmflags.md @@ -2,8 +2,8 @@ title: ksetup listrealmflags description: Reference article for the ksetup listrealmflags command, which lists the available realm flags that can be reported by ksetup. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-mapuser.md b/WindowsServerDocs/administration/windows-commands/ksetup-mapuser.md index 1365c7d4da..be854b27ff 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-mapuser.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-mapuser.md @@ -2,8 +2,8 @@ title: ksetup mapuser description: Reference article for the ksetup mapuser command, which maps the name of a Kerberos principal to an account. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-removerealm.md b/WindowsServerDocs/administration/windows-commands/ksetup-removerealm.md index 830a6567a2..ba8b13901c 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-removerealm.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-removerealm.md @@ -2,8 +2,8 @@ title: ksetup removerealm description: Reference article for the ksetup removerealm command, which deletes all information for the specified realm from the registry. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-server.md b/WindowsServerDocs/administration/windows-commands/ksetup-server.md index 993b70bf69..19bcd28a11 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-server.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-server.md @@ -2,8 +2,8 @@ title: ksetup server description: Reference article for the ksetup server command, which allows you to specify a name for a computer running the Windows operating system, so changes made by the ksetup command update the target computer. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-setcomputerpassword.md b/WindowsServerDocs/administration/windows-commands/ksetup-setcomputerpassword.md index 707be2fde1..ffe2d1a97e 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-setcomputerpassword.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-setcomputerpassword.md @@ -2,8 +2,8 @@ title: ksetup setcomputerpassword description: Reference article for the ksetup setcomputerpassword command, which sets the password for the local computer. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-setenctypeattr.md b/WindowsServerDocs/administration/windows-commands/ksetup-setenctypeattr.md index 0abf209804..d4274e7bd5 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-setenctypeattr.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-setenctypeattr.md @@ -2,8 +2,8 @@ title: ksetup setenctypeattr description: Reference article for the ksetup setenctypeattr command, which sets the encryption type attribute for the domain. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-setrealm.md b/WindowsServerDocs/administration/windows-commands/ksetup-setrealm.md index a99f0ea770..52bbcbfc3e 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-setrealm.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-setrealm.md @@ -2,8 +2,8 @@ title: ksetup setrealm description: Reference article for the ksetup setrealm command, which sets the name of a Kerberos realm. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup-setrealmflags.md b/WindowsServerDocs/administration/windows-commands/ksetup-setrealmflags.md index 1061c5d8f3..6e81e3e94e 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup-setrealmflags.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup-setrealmflags.md @@ -2,8 +2,8 @@ title: ksetup setrealmflags description: Reference article for the ksetup setrealmflags command, which sets realm flags for the specified realm. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ksetup.md b/WindowsServerDocs/administration/windows-commands/ksetup.md index a5e1210afd..a74ccaa515 100644 --- a/WindowsServerDocs/administration/windows-commands/ksetup.md +++ b/WindowsServerDocs/administration/windows-commands/ksetup.md @@ -2,8 +2,8 @@ title: ksetup description: Reference article for the ksetup command, which performs tasks related to setting up and maintaining Kerberos protocol and the Key Distribution Center (KDC) to support Kerberos realms. ms.topic: reference -ms.author: mosagie -author: meaghanlewis +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ktmutil.md b/WindowsServerDocs/administration/windows-commands/ktmutil.md index ad91ddd021..0c118b42ab 100644 --- a/WindowsServerDocs/administration/windows-commands/ktmutil.md +++ b/WindowsServerDocs/administration/windows-commands/ktmutil.md @@ -2,8 +2,8 @@ title: ktmutil description: Reference article for the ktmutil command, which starts the Kernel Transaction Manager utility. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/ktpass.md b/WindowsServerDocs/administration/windows-commands/ktpass.md index d220515f12..c3c91bcac6 100644 --- a/WindowsServerDocs/administration/windows-commands/ktpass.md +++ b/WindowsServerDocs/administration/windows-commands/ktpass.md @@ -2,8 +2,8 @@ title: ktpass description: Reference article for the ktpass command, which configures the server principal name for the host or service in AD DS and generates a .keytab file that contains the shared secret key of the service. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/label.md b/WindowsServerDocs/administration/windows-commands/label.md index 06e1f2f131..12b8f9500a 100644 --- a/WindowsServerDocs/administration/windows-commands/label.md +++ b/WindowsServerDocs/administration/windows-commands/label.md @@ -2,8 +2,8 @@ title: label description: Reference article for the label command, which creates, changes, or deletes the volume label (that is, the name) of a disk. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/list-providers.md b/WindowsServerDocs/administration/windows-commands/list-providers.md index 88f59fb5ff..04fb18cdd1 100644 --- a/WindowsServerDocs/administration/windows-commands/list-providers.md +++ b/WindowsServerDocs/administration/windows-commands/list-providers.md @@ -2,8 +2,8 @@ title: list providers description: Reference article for the list providers command, which lists shadow copy providers that are currently registered on the system. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/list-shadows.md b/WindowsServerDocs/administration/windows-commands/list-shadows.md index b55a568f32..006bf529d4 100644 --- a/WindowsServerDocs/administration/windows-commands/list-shadows.md +++ b/WindowsServerDocs/administration/windows-commands/list-shadows.md @@ -2,8 +2,8 @@ title: list shadows description: Reference article for the list shadows command, which lists persistent and existing non-persistent shadow copies that are on the system. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/list-volume.md b/WindowsServerDocs/administration/windows-commands/list-volume.md index fad26780c6..c369fec2ce 100644 --- a/WindowsServerDocs/administration/windows-commands/list-volume.md +++ b/WindowsServerDocs/administration/windows-commands/list-volume.md @@ -2,8 +2,8 @@ title: list volume description: Reference article for the list volume command, which displays a list of basic and dynamic volumes on all disks. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/list-writers.md b/WindowsServerDocs/administration/windows-commands/list-writers.md index 925b9e49c3..e85411c910 100644 --- a/WindowsServerDocs/administration/windows-commands/list-writers.md +++ b/WindowsServerDocs/administration/windows-commands/list-writers.md @@ -2,8 +2,8 @@ title: list writers description: Reference article for the list writers command, which lists writers that are on the system. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/list.md b/WindowsServerDocs/administration/windows-commands/list.md index 97c232612a..d317756b24 100644 --- a/WindowsServerDocs/administration/windows-commands/list.md +++ b/WindowsServerDocs/administration/windows-commands/list.md @@ -2,8 +2,8 @@ title: list description: Reference article for the list command, which displays a list of disks, of partitions in a disk, of volumes in a disk, or of virtual hard disks (VHDs). ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/list_2.md b/WindowsServerDocs/administration/windows-commands/list_2.md index 0ed21391e6..11f7131d03 100644 --- a/WindowsServerDocs/administration/windows-commands/list_2.md +++ b/WindowsServerDocs/administration/windows-commands/list_2.md @@ -2,8 +2,8 @@ title: list (diskshadow) description: Reference article for the list command, which displays information about the shadow copy (snapshot) set of an existing drive or volume. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/12/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/load-metadata.md b/WindowsServerDocs/administration/windows-commands/load-metadata.md index a8e2d44bc3..fb1310197f 100644 --- a/WindowsServerDocs/administration/windows-commands/load-metadata.md +++ b/WindowsServerDocs/administration/windows-commands/load-metadata.md @@ -2,8 +2,8 @@ title: load metadata description: Reference article for the load metadata command, which loads a metadata .cab file prior to importing a transportable shadow copy or loads the writer metadata in the case of a restore. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/lodctr.md b/WindowsServerDocs/administration/windows-commands/lodctr.md index 2b81282abf..557c39b0b9 100644 --- a/WindowsServerDocs/administration/windows-commands/lodctr.md +++ b/WindowsServerDocs/administration/windows-commands/lodctr.md @@ -2,8 +2,8 @@ title: lodctr description: Reference article for the lodctr command, which allows you to register or save performance counter name and registry settings in a file and designate trusted services. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/22/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-create-alert.md b/WindowsServerDocs/administration/windows-commands/logman-create-alert.md index 9a8e53cba7..6346037aee 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-create-alert.md +++ b/WindowsServerDocs/administration/windows-commands/logman-create-alert.md @@ -2,8 +2,8 @@ title: logman create alert description: Reference article for the logman create alert command, which creates an alert data collector. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-create-api.md b/WindowsServerDocs/administration/windows-commands/logman-create-api.md index 9fe9e33bc1..f9565b5016 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-create-api.md +++ b/WindowsServerDocs/administration/windows-commands/logman-create-api.md @@ -2,8 +2,8 @@ title: logman create api description: Reference article for the logman create api command, which creates an API-tracing data collector. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-create-cfg.md b/WindowsServerDocs/administration/windows-commands/logman-create-cfg.md index f5006232c9..3e2cfdc161 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-create-cfg.md +++ b/WindowsServerDocs/administration/windows-commands/logman-create-cfg.md @@ -2,8 +2,8 @@ title: logman create cfg description: Reference article for the logman create cfg command, which creates a configuration data collector. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-create-counter.md b/WindowsServerDocs/administration/windows-commands/logman-create-counter.md index dbdc7f2e2f..b2a46d8c75 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-create-counter.md +++ b/WindowsServerDocs/administration/windows-commands/logman-create-counter.md @@ -2,8 +2,8 @@ title: logman create counter description: Reference article for the logman create counter command, which creates a counter data collector. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-create-trace.md b/WindowsServerDocs/administration/windows-commands/logman-create-trace.md index 897b36a4be..4371a24e31 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-create-trace.md +++ b/WindowsServerDocs/administration/windows-commands/logman-create-trace.md @@ -2,8 +2,8 @@ title: logman create trace description: Reference article for the logman create trace command, which creates an event trace data collector. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-create.md b/WindowsServerDocs/administration/windows-commands/logman-create.md index 1652691d9a..e5683e3be7 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-create.md +++ b/WindowsServerDocs/administration/windows-commands/logman-create.md @@ -2,8 +2,8 @@ title: logman create description: Reference article for the logman create command, which creates a counter, trace, configuration data collector, or API. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-delete.md b/WindowsServerDocs/administration/windows-commands/logman-delete.md index 90033caf68..d7b2c52c84 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-delete.md +++ b/WindowsServerDocs/administration/windows-commands/logman-delete.md @@ -2,8 +2,8 @@ title: logman delete description: Reference article for the logman delete command, which deletes an existing data collector. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-import-export.md b/WindowsServerDocs/administration/windows-commands/logman-import-export.md index 6ff0af5d1d..cd34f52cfb 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-import-export.md +++ b/WindowsServerDocs/administration/windows-commands/logman-import-export.md @@ -2,8 +2,8 @@ title: logman import and logman export description: Reference article for logman import and logman export, which imports a Data Collector Set from an XML file, or exports a Data Collector Set to an XML file. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-query.md b/WindowsServerDocs/administration/windows-commands/logman-query.md index ab19a6f7e4..a93fdace38 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-query.md +++ b/WindowsServerDocs/administration/windows-commands/logman-query.md @@ -2,8 +2,8 @@ title: logman query description: Reference article for the logman query command, which queries data collector or data collector set properties. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-start-stop.md b/WindowsServerDocs/administration/windows-commands/logman-start-stop.md index 5627ee3485..713ce345d5 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-start-stop.md +++ b/WindowsServerDocs/administration/windows-commands/logman-start-stop.md @@ -2,8 +2,8 @@ title: logman start and logman stop description: Reference article for the logman start and logman stop commands, which starts a data collector and sets the begin time to manual, or stops a Data Collector Set and sets the end time to manual. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-update-alert.md b/WindowsServerDocs/administration/windows-commands/logman-update-alert.md index 37385a5e00..e48efba980 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-update-alert.md +++ b/WindowsServerDocs/administration/windows-commands/logman-update-alert.md @@ -2,8 +2,8 @@ title: logman update alert description: Reference article for the logman update alert command, which updates the properties of an existing alert data collector. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-update-api.md b/WindowsServerDocs/administration/windows-commands/logman-update-api.md index 1c5cbd66bd..d9e7fff97d 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-update-api.md +++ b/WindowsServerDocs/administration/windows-commands/logman-update-api.md @@ -2,8 +2,8 @@ title: logman update api description: Reference article for the logman update api command, which updates the properties of an existing API tracking data collector. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-update-cfg.md b/WindowsServerDocs/administration/windows-commands/logman-update-cfg.md index 8161554ab2..9ee4638952 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-update-cfg.md +++ b/WindowsServerDocs/administration/windows-commands/logman-update-cfg.md @@ -2,8 +2,8 @@ title: logman update cfg description: Reference article for the logman update cfg command, which updates the properties of an existing configuration data collector. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-update-counter.md b/WindowsServerDocs/administration/windows-commands/logman-update-counter.md index 2ba76fe483..0de96c38c1 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-update-counter.md +++ b/WindowsServerDocs/administration/windows-commands/logman-update-counter.md @@ -2,8 +2,8 @@ title: logman update counter description: Reference article for the logman update counter command, which updates an existing counter data collector's properties. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-update-trace.md b/WindowsServerDocs/administration/windows-commands/logman-update-trace.md index 8caed7010b..82ddf46f10 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-update-trace.md +++ b/WindowsServerDocs/administration/windows-commands/logman-update-trace.md @@ -2,8 +2,8 @@ title: logman update trace description: Reference article for the logman update trace command, which updates the properties of an existing event trace data collector. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman-update.md b/WindowsServerDocs/administration/windows-commands/logman-update.md index 7d91f22db4..06f00a79cf 100644 --- a/WindowsServerDocs/administration/windows-commands/logman-update.md +++ b/WindowsServerDocs/administration/windows-commands/logman-update.md @@ -2,8 +2,8 @@ title: logman update description: Reference article for the logman update command, which updates an existing data collector. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logman.md b/WindowsServerDocs/administration/windows-commands/logman.md index fa4b76f726..6f74ff9af9 100644 --- a/WindowsServerDocs/administration/windows-commands/logman.md +++ b/WindowsServerDocs/administration/windows-commands/logman.md @@ -2,8 +2,8 @@ title: logman description: Reference article for the logman command, which creates and manages Event Trace Session and Performance logs and supports many functions of Performance Monitor from the command line. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/logoff.md b/WindowsServerDocs/administration/windows-commands/logoff.md index 0afac3ce04..da1e7940ed 100644 --- a/WindowsServerDocs/administration/windows-commands/logoff.md +++ b/WindowsServerDocs/administration/windows-commands/logoff.md @@ -2,8 +2,8 @@ title: logoff description: Reference article for the logoff command, which logs off a user from a session on a Remote Desktop Session Host server and deletes the session. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/lpq.md b/WindowsServerDocs/administration/windows-commands/lpq.md index bc25f9c196..361a64d3bd 100644 --- a/WindowsServerDocs/administration/windows-commands/lpq.md +++ b/WindowsServerDocs/administration/windows-commands/lpq.md @@ -2,8 +2,8 @@ title: lpq description: Reference article for the lpq command, which displays the status of a print queue on a computer running Line printer Daemon (LPD). ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/lpr.md b/WindowsServerDocs/administration/windows-commands/lpr.md index 779f238c38..73e04b461f 100644 --- a/WindowsServerDocs/administration/windows-commands/lpr.md +++ b/WindowsServerDocs/administration/windows-commands/lpr.md @@ -2,8 +2,8 @@ title: lpr description: Reference article for the lpr command, which sends a file to a computer or printer sharing device running the Line printer Daemon (LPD) service in preparation for printing. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/manage-bde-lock.md b/WindowsServerDocs/administration/windows-commands/manage-bde-lock.md index f48e49a7c1..c16a0e8d12 100644 --- a/WindowsServerDocs/administration/windows-commands/manage-bde-lock.md +++ b/WindowsServerDocs/administration/windows-commands/manage-bde-lock.md @@ -2,8 +2,8 @@ title: manage-bde lock description: Reference article for the manage-bde lock command, which locks a BitLocker-protected drive to prevent access to it unless the unlock key is provided. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 01/17/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/manage-bde-tpm.md b/WindowsServerDocs/administration/windows-commands/manage-bde-tpm.md index 34b5eb37db..ed0d7a3946 100644 --- a/WindowsServerDocs/administration/windows-commands/manage-bde-tpm.md +++ b/WindowsServerDocs/administration/windows-commands/manage-bde-tpm.md @@ -2,8 +2,8 @@ title: manage-bde tpm description: Reference article for the manage-bde tpm command, which configures the computer's Trusted Platform Module (TPM). ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 08/29/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/manage-bde-unlock.md b/WindowsServerDocs/administration/windows-commands/manage-bde-unlock.md index 0a541a872b..dbcc177bab 100644 --- a/WindowsServerDocs/administration/windows-commands/manage-bde-unlock.md +++ b/WindowsServerDocs/administration/windows-commands/manage-bde-unlock.md @@ -2,8 +2,8 @@ title: manage-bde unlock description: Reference article for the manage-bde unlock command, which unlocks a BitLocker-protected drive by using a recovery password or a recovery key. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 01/17/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/mount.md b/WindowsServerDocs/administration/windows-commands/mount.md index 7d774c17d9..f3036a324e 100644 --- a/WindowsServerDocs/administration/windows-commands/mount.md +++ b/WindowsServerDocs/administration/windows-commands/mount.md @@ -2,8 +2,8 @@ title: mount description: Reference article for the mount command, which mounts Network File System (NFS) network shares. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 09/27/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/msg.md b/WindowsServerDocs/administration/windows-commands/msg.md index 947443f654..084b920537 100644 --- a/WindowsServerDocs/administration/windows-commands/msg.md +++ b/WindowsServerDocs/administration/windows-commands/msg.md @@ -2,8 +2,8 @@ title: msg description: Reference article for the msg command, which sends a message to a user on a Remote Desktop Session Host server ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/19/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/mstsc.md b/WindowsServerDocs/administration/windows-commands/mstsc.md index f76b452c67..9541cb5abc 100644 --- a/WindowsServerDocs/administration/windows-commands/mstsc.md +++ b/WindowsServerDocs/administration/windows-commands/mstsc.md @@ -2,8 +2,8 @@ title: mstsc description: Reference article for the mstsc command, which creates connections to Remote Desktop Session Host servers or other remote computers and edits an existing Remote Desktop Connection (.rdp) configuration file ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/19/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/net-user.md b/WindowsServerDocs/administration/windows-commands/net-user.md index 35d9f8a244..3e7e0ddb31 100644 --- a/WindowsServerDocs/administration/windows-commands/net-user.md +++ b/WindowsServerDocs/administration/windows-commands/net-user.md @@ -2,8 +2,8 @@ title: net user description: Reference article for the net user command, which adds, deletes, modifies, and displays user account information. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 08/06/2025 --- @@ -66,25 +66,25 @@ To display information about the user account **TommyH**, run the following comm net user tommyh ``` -To add a user account for **Jay Samson** (user name: **jays**), with sign in rights from 8 AM to 5 PM, Monday through Friday, with the mandatory password **Cyk4^g3B**, and use the user's full name, run the following command: +To add a user account for **Jay Samson** (user name: **jays**), with sign in rights from 8 AM to 5 PM, Monday through Friday, with the mandatory password **Cyk4^g3B**, and use the user's full name, run the following command: ```cmd net user jays Cyk4^g3B /add /passwordreq:yes /times:monday-friday,8am-5pm /fullname:"Jay Jamison" ``` -To set the sign-in time from 8 AM to 5 PM for the username **MikeD** using 24-hour notation, run the following command: +To set the sign-in time from 8 AM to 5 PM for the username **MikeD** using 24-hour notation, run the following command: ```cmd net user miked /time:M-F,08:00-17:00 ``` -To set the sign-in time from 8 AM to 5 PM for **MikeD** using 12-hour notation, run the following command: +To set the sign-in time from 8 AM to 5 PM for **MikeD** using 12-hour notation, run the following command: ```cmd net user miked /time:M-F,8AM-5PM ``` -To specify sign-in hours of 4 AM to 12 PM on Monday, 12 PM to 8 PM on Tuesday, and 8 AM to 5 PM Wednesday through Friday for username **AnibalS**, run the following command: +To specify sign-in hours of 4 AM to 12 PM on Monday, 12 PM to 8 PM on Tuesday, and 8 AM to 5 PM Wednesday through Friday for username **AnibalS**, run the following command: ```cmd net user anibals /time:M,4AM-12PM;T,12PM-8PM;W-F,8AM-5PM diff --git a/WindowsServerDocs/administration/windows-commands/netdom-add.md b/WindowsServerDocs/administration/windows-commands/netdom-add.md index 9b636b550e..0d08614c7e 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom-add.md +++ b/WindowsServerDocs/administration/windows-commands/netdom-add.md @@ -2,14 +2,14 @@ title: Netdom add description: Netdom add is a command-line utility that adds a workstation or server account to a domain in Windows Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 06/09/2025 --- # netdom add -The `netdom add` command adds a workstation or server account to a domain. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). To use `netdom add`, you must run the command from an elevated command prompt. +The `netdom add` command adds a workstation or server account to a domain. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). To use `netdom add`, you must run the command from an elevated command prompt. ## Syntax @@ -27,8 +27,8 @@ netdom add machine [/Domain:domain] [/UserD:user] [/PasswordD:[password | *]] |`/userd:`|Specifies the user account that makes the connection with the domain that you specify using the `/domain` parameter. If you don't specify this parameter, `netdom add` uses the current user account.| |`/passwordd:` \| `*`|Specifies the password of the user account that you specify using the `/userd` parameter. If you specify the value of this parameter as a wildcard character (`*`), this parameter prompts you for the password.| |`/server:`|Specifies the name of a domain controller that performs the *add* operation. This parameter can't be used with the `/ou` parameter.| -|`/ou:`|Specifies the organizational unit (OU) under which to create the account. You must use the full [RFC 1779](https://www.rfc-editor.org/rfc/rfc1779) distinguished name of the OU. If you don't specify this parameter, `netdom add` creates the account under the default OU for computer objects for that domain.| -|`/dc`|Specifies that a domain controller's machine account is to be created. This makes it possible for the computer accounts for new AD DS domain controllers. This parameter can't be used with the **/ou** parameter.| +|`/ou:`|Specifies the organizational unit (OU) under which to create the account. You must use the full [RFC 1779](https://www.rfc-editor.org/rfc/rfc1779) distinguished name of the OU. If you don't specify this parameter, `netdom add` creates the account under the default OU for computer objects for that domain.| +|`/dc`|Specifies that a domain controller's machine account is to be created. This makes it possible for the computer accounts for new AD DS domain controllers. This parameter can't be used with the **/ou** parameter.| | `/securepasswordprompt` | Opens a secure credentials popup for entering credentials. This is useful when specifying smartcard credentials. This option is effective only when the password is entered as `*`. | |`help` \| `/?`|Displays help at the command prompt.| diff --git a/WindowsServerDocs/administration/windows-commands/netdom-computername.md b/WindowsServerDocs/administration/windows-commands/netdom-computername.md index c472c2f265..d4d8c8eac6 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom-computername.md +++ b/WindowsServerDocs/administration/windows-commands/netdom-computername.md @@ -2,14 +2,14 @@ title: Netdom computername description: Netdom computername is a command-line utility that manages the primary and alternate names for a computer in Windows Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 06/09/2025 --- # netdom computername -The `netdom computername` command manages the primary and alternate names for a computer. This command can safely rename Active Directory (AD) domain controllers (DC) and member servers. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). To use `netdom computername`, you must run the command from an elevated command prompt. +The `netdom computername` command manages the primary and alternate names for a computer. This command can safely rename Active Directory (AD) domain controllers (DC) and member servers. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). To use `netdom computername`, you must run the command from an elevated command prompt. ## Syntax diff --git a/WindowsServerDocs/administration/windows-commands/netdom-join.md b/WindowsServerDocs/administration/windows-commands/netdom-join.md index e1e86bb3af..bdc6b01486 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom-join.md +++ b/WindowsServerDocs/administration/windows-commands/netdom-join.md @@ -2,14 +2,14 @@ title: Netdom join description: Netdom is a command-line utility that joins a workstation or member server to a domain in Windows Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 06/09/2025 --- # netdom join -The `netdom join` command joins a workstation or member server to a domain. The act of joining a computer to a domain creates an account for the computer on the domain, if it doesn't already exist. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the Active Directory Domain Services Tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). +The `netdom join` command joins a workstation or member server to a domain. The act of joining a computer to a domain creates an account for the computer on the domain, if it doesn't already exist. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the Active Directory Domain Services Tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). To use `netdom join`, you must run the command from an elevated command prompt. @@ -31,7 +31,7 @@ netdom join machine /Domain:domain [/OU:ou path] [/UserD:user] |-----------|-------------| | `` | Specifies the name of the computer that you want to join to the domain. | | `/domain:` | Specifies the domain that you want to join the computer to. Using the Fully Qualified Domain Name (FQDN) format is recommended for clarity. If not specified, `netdom join` defaults to the domain to which the current computer belongs to. | -| `/ou:` | Specifies the organizational unit (OU) under which you want to create the account. You must specify the full [RFC 1779](https://www.rfc-editor.org/rfc/rfc1779) distinguished name of the OU. If not specified, `netdom join` creates the account under the default OU for computer objects for that domain. | +| `/ou:` | Specifies the organizational unit (OU) under which you want to create the account. You must specify the full [RFC 1779](https://www.rfc-editor.org/rfc/rfc1779) distinguished name of the OU. If not specified, `netdom join` creates the account under the default OU for computer objects for that domain. | | `/userd:\` | Specifies the user account that makes the connection with the domain specified with the `/domain` parameter. If not specified, `netdom join` uses the current user account. | | `/usero:` | Specifies the user account that makes the connection with the computer you want to join to the domain. If not specified, `netdom join` uses the current user account. | | `/passwordd:` \| `*` | Specifies the password of the user account specified with the `/userd` parameter. If you specify `*`, you're prompted for the password. | diff --git a/WindowsServerDocs/administration/windows-commands/netdom-move.md b/WindowsServerDocs/administration/windows-commands/netdom-move.md index 1b74f88cf8..bf71db84ba 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom-move.md +++ b/WindowsServerDocs/administration/windows-commands/netdom-move.md @@ -2,14 +2,14 @@ title: Netdom move description: Netdom move is a command-line utility moves a workstation or member server to a new domain in Windows Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 06/09/2025 --- # netdom move -The `netdom move` command moves a workstation or member server to a new domain. The act of moving a computer to a new domain creates an account for the computer on the domain, if it doesn't already exist. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). To use `netdom move`, you must run the command from an elevated command prompt. +The `netdom move` command moves a workstation or member server to a new domain. The act of moving a computer to a new domain creates an account for the computer on the domain, if it doesn't already exist. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). To use `netdom move`, you must run the command from an elevated command prompt. ## Syntax @@ -31,7 +31,7 @@ netdom move machine /Domain:domain [/OU:ou path] |-----------|-------------| | `` | Specifies the name of the computer that you want to move. | | `/domain:` | Specifies the domain to which you want to move the account. If you don't specify the parameter, then `netdom move` uses the domain to which the current computer belongs. | -| `/ou:` | Specifies the organizational unit (OU) under which to create the account. This must be the full [RFC 1779](https://www.rfc-editor.org/rfc/rfc1779) distinguished name of the OU. If you don't specify this parameter, `netdom move` creates the account under the default OU for computer objects for that domain. | +| `/ou:` | Specifies the organizational unit (OU) under which to create the account. This must be the full [RFC 1779](https://www.rfc-editor.org/rfc/rfc1779) distinguished name of the OU. If you don't specify this parameter, `netdom move` creates the account under the default OU for computer objects for that domain. | | `/userd:` | Specifies the user account that makes the connection with the domain that you specify using the `/domain` parameter. If you don't specify this parameter, `netdom move` uses the current user account. | | `/passwordd:` \| `*` | Specifies the password of the user account that you specify using the `/userd` parameter. If you specify the value of this parameter as a wildcard character (`*`), this parameter prompts you for the password. | | `/usero:` | Specifies the user account to make the connection with the computer that you want to move. If you don't specify this parameter, `netdom move` uses the current user account. | @@ -50,7 +50,7 @@ To move **mywksta** from its current domain into the **MyDomain** domain, run th netdom move mywksta /domain:mydomain /userd:mydomain\admin /passwordd:* ``` -If the destination is an AD DS domain, this command updates the Security ID history for the workstation, retaining the security permissions that the computer account had previously. +If the destination is an AD DS domain, this command updates the Security ID history for the workstation, retaining the security permissions that the computer account had previously. To move **Srv01** to the domain **NewDomain** and specify the OU, run the following command: diff --git a/WindowsServerDocs/administration/windows-commands/netdom-movent4bdc.md b/WindowsServerDocs/administration/windows-commands/netdom-movent4bdc.md index 9525cbc17d..f3fd108888 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom-movent4bdc.md +++ b/WindowsServerDocs/administration/windows-commands/netdom-movent4bdc.md @@ -1,15 +1,15 @@ --- title: Netdom movent4bdc -description: Netdom movent4bdc is a command-line utility that renames a Windows NT 4.0 backup domain controller in Windows Server. +description: Netdom movent4bdc is a command-line utility that renames a Windows NT 4.0 backup domain controller in Windows Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 06/09/2025 --- # netdom movent4bdc -The `netdom movent4bdc` command renames a Windows NT 4.0 backup domain controller (DC). It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). To use `netdom movent4bdc`, you must run the command from an elevated command prompt. +The `netdom movent4bdc` command renames a Windows NT 4.0 backup domain controller (DC). It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). To use `netdom movent4bdc`, you must run the command from an elevated command prompt. This command is specific to legacy Windows Server operating systems. diff --git a/WindowsServerDocs/administration/windows-commands/netdom-query.md b/WindowsServerDocs/administration/windows-commands/netdom-query.md index 8811d273e1..abf2c094a1 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom-query.md +++ b/WindowsServerDocs/administration/windows-commands/netdom-query.md @@ -2,14 +2,14 @@ title: Netdom query description: Netdom query is a command-line utility that retrieves information from a domain about its membership and trust relationships in Windows Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 06/09/2025 --- # netdom query -The `netdom query` command retrieves information from a domain about its membership and trust relationships. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). +The `netdom query` command retrieves information from a domain about its membership and trust relationships. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). To use `netdom query`, you must run the command from an elevated command prompt. diff --git a/WindowsServerDocs/administration/windows-commands/netdom-remove.md b/WindowsServerDocs/administration/windows-commands/netdom-remove.md index b915f8520e..42b037ede6 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom-remove.md +++ b/WindowsServerDocs/administration/windows-commands/netdom-remove.md @@ -2,14 +2,14 @@ title: Netdom remove description: Netdom remove is a command-line utility that removes a workstation or server from a domain in Windows Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 06/09/2025 --- # netdom remove -The `netdom remove` command removes a workstation or server from a domain. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). +The `netdom remove` command removes a workstation or server from a domain. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). To use `netdom remove`, you must run the command from an elevated command prompt. diff --git a/WindowsServerDocs/administration/windows-commands/netdom-renamecomputer.md b/WindowsServerDocs/administration/windows-commands/netdom-renamecomputer.md index 7b6cb0cec4..c4d18197ac 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom-renamecomputer.md +++ b/WindowsServerDocs/administration/windows-commands/netdom-renamecomputer.md @@ -2,14 +2,14 @@ title: netdom renamecomputer description: Netdom renamecomputer is a command-line utility that renames a domain workstation or member server in Windows Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 06/09/2025 --- # netdom renamecomputer -The `netdom renamecomputer` command renames a domain workstation or member server and its corresponding domain account. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). +The `netdom renamecomputer` command renames a domain workstation or member server and its corresponding domain account. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). To use `netdom renamecomputer`, you must run the command from an elevated command prompt. diff --git a/WindowsServerDocs/administration/windows-commands/netdom-reset.md b/WindowsServerDocs/administration/windows-commands/netdom-reset.md index 089f4b68b6..b43242fcb2 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom-reset.md +++ b/WindowsServerDocs/administration/windows-commands/netdom-reset.md @@ -2,14 +2,14 @@ title: Netdom reset description: Netdom reset is a command-line utility that resets the secure connection between a workstation and a domain controller in Windows Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 06/09/2025 --- # netdom reset -The `netdom reset` command resets the secure connection between a workstation and a domain controller (DC). It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). +The `netdom reset` command resets the secure connection between a workstation and a domain controller (DC). It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). To use `netdom reset`, you must run the command from an elevated command prompt. diff --git a/WindowsServerDocs/administration/windows-commands/netdom-resetpwd.md b/WindowsServerDocs/administration/windows-commands/netdom-resetpwd.md index 387e204638..6a48eddde2 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom-resetpwd.md +++ b/WindowsServerDocs/administration/windows-commands/netdom-resetpwd.md @@ -2,14 +2,14 @@ title: Netdom resetpwd description: Netdom resetpwd is a command-line utility that resets the computer account password for a domain controller in Windows Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 06/09/2025 --- # netdom resetpwd -The `netdom resetpwd` command resets the secure channel password of the machine account for a domain controller (DC). This command must be run on the DC whose machine account password you wish to reset. It doesn't support resetting passwords for remote machines or member servers. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). +The `netdom resetpwd` command resets the secure channel password of the machine account for a domain controller (DC). This command must be run on the DC whose machine account password you wish to reset. It doesn't support resetting passwords for remote machines or member servers. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). diff --git a/WindowsServerDocs/administration/windows-commands/netdom-trust.md b/WindowsServerDocs/administration/windows-commands/netdom-trust.md index 9b5fa49db4..10a6001bc2 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom-trust.md +++ b/WindowsServerDocs/administration/windows-commands/netdom-trust.md @@ -2,14 +2,14 @@ title: Netdom trust description: Netdom trust is a command-line utility that manages, establishes, verifies, or resets trust relationships between domains in Windows Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 06/09/2025 --- # netdom trust -The `netdom trust` command allows administrators to manage, establish, verify, or reset trust relationships between domains. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). +The `netdom trust` command allows administrators to manage, establish, verify, or reset trust relationships between domains. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). To use `netdom trust`, you must run the command from an elevated command prompt. diff --git a/WindowsServerDocs/administration/windows-commands/netdom-verify.md b/WindowsServerDocs/administration/windows-commands/netdom-verify.md index 70f52fc751..b96bab7c2a 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom-verify.md +++ b/WindowsServerDocs/administration/windows-commands/netdom-verify.md @@ -2,14 +2,14 @@ title: Netdom verify description: Netdom verify is a command-line utility that verifies the secure channel between a specified computer and a domain controller in Windows Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 06/09/2025 --- # netdom verify -The `netdom verify` command checks the secure channel between a specified computer and a domain controller to ensure trust and connectivity are intact. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). +The `netdom verify` command checks the secure channel between a specified computer and a domain controller to ensure trust and connectivity are intact. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). For more information, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). To use `netdom verify`, you must run the command from an elevated command prompt. diff --git a/WindowsServerDocs/administration/windows-commands/netdom.md b/WindowsServerDocs/administration/windows-commands/netdom.md index 05059f5beb..79dbb39a04 100644 --- a/WindowsServerDocs/administration/windows-commands/netdom.md +++ b/WindowsServerDocs/administration/windows-commands/netdom.md @@ -2,14 +2,14 @@ title: Netdom description: Netdom is a command-line utility for administering Active Directory (AD) domains, managing computer accounts, and configuring or verifying trust relationships between domains. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 06/09/2025 --- # netdom -`Netdom` is a command-line tool that enables administrators to manage Active Directory (AD) domains and trust relationships from the command line. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). To learn more, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). +`Netdom` is a command-line tool that enables administrators to manage Active Directory (AD) domains and trust relationships from the command line. It's available if you have the Active Directory Domain Services (AD DS) server role installed. It's also available if you install the AD DS tools that are part of the Remote Server Administration Tools (RSAT). To learn more, see [How to Administer Microsoft Windows Client and Server Computers Locally and Remotely](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee649281(v=ws.10)). You must run the `netdom` command from an elevated command prompt. The `netdom` allows you to performing the following actions: @@ -57,7 +57,7 @@ netdom [ ADD | COMPUTERNAME | HELP | JOIN | MOVE | MOVENT4BDC | QUERY | REMOVE | | [netdom computername](netdom-computername.md) | Manages the primary and alternate names for a computer. This command can safely rename Active Directory domain controllers and member servers. | | [netdom join](netdom-join.md) | Joins a workstation or member server to a domain. The act of joining a computer to a domain creates an account for the computer on the domain, if it doesn't already exist. | | [netdom move](netdom-move.md) | Moves a workstation or member server to a new domain. The act of moving a computer to a new domain creates an account for the computer on the domain, if it doesn't already exist. | -| [netdom movent4bdc](netdom-movent4bdc.md) | Renames a Windows NT 4.0 backup domain controller to reflect a domain name change. This can help Windows NT 4.0 domain renaming efforts. | +| [netdom movent4bdc](netdom-movent4bdc.md) | Renames a Windows NT 4.0 backup domain controller to reflect a domain name change. This can help Windows NT 4.0 domain renaming efforts. | | [netdom query](netdom-query.md) | Queries the domain for information such as membership and trust. | | [netdom remove](netdom-remove.md) | Removes a workstation or server from the domain. | | [netdom renamecomputer](netdom-renamecomputer.md) | Renames a domain computer and its corresponding domain account. Use this command to rename domain workstations and member servers only. To rename domain controllers, use the `netdom computername` command. | diff --git a/WindowsServerDocs/administration/windows-commands/netsh-add.md b/WindowsServerDocs/administration/windows-commands/netsh-add.md index 00c285b2a2..11aed8af9f 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-add.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-add.md @@ -2,8 +2,8 @@ title: netsh add description: Reference article for the netsh add command that adds a helper dll. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 07/24/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-advfirewall.md b/WindowsServerDocs/administration/windows-commands/netsh-advfirewall.md index 286cb944d1..dfea429881 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-advfirewall.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-advfirewall.md @@ -2,8 +2,8 @@ title: netsh advfirewall description: Reference article for the netsh command, which is a command-line scripting utility that allows you to display or modify the network configuration of a currently running computer locally or remotely. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 07/24/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-branchcache.md b/WindowsServerDocs/administration/windows-commands/netsh-branchcache.md index 962359c5d6..e96e63cb37 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-branchcache.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-branchcache.md @@ -2,8 +2,8 @@ title: netsh branchcache description: Reference article for the netsh branchcache command in Windows, which manages data access speeds in branch offices locally. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 07/24/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-bridge.md b/WindowsServerDocs/administration/windows-commands/netsh-bridge.md index 257703ee48..fffb9c5c9c 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-bridge.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-bridge.md @@ -2,8 +2,8 @@ title: netsh bridge description: The netsh bridge command manages network adapter bridge settings to combine two or more network segments as one network in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/10/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-delete.md b/WindowsServerDocs/administration/windows-commands/netsh-delete.md index 724630011c..771b3e6243 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-delete.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-delete.md @@ -2,8 +2,8 @@ title: netsh delete description: Reference article for the netsh delete command that removes a helper dll. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 07/24/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-dhcpclient.md b/WindowsServerDocs/administration/windows-commands/netsh-dhcpclient.md index 6a06403351..c42a2d9ad7 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-dhcpclient.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-dhcpclient.md @@ -2,8 +2,8 @@ title: netsh dhcpclient description: Reference article for the netsh dhcpclient command, which configures and manages the DHCP client settings. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 07/28/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-dnsclient.md b/WindowsServerDocs/administration/windows-commands/netsh-dnsclient.md index 9864dbf701..4875cc64e9 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-dnsclient.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-dnsclient.md @@ -2,8 +2,8 @@ title: netsh dnsclient description: The netsh dnsclient command configures and manages DNS client settings in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 07/28/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-dump.md b/WindowsServerDocs/administration/windows-commands/netsh-dump.md index 6d9de27368..fca1f379fe 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-dump.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-dump.md @@ -2,8 +2,8 @@ title: netsh dump description: Reference article for the netsh dump command that allows exporting network configuration settings to a text file. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 07/25/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-exec.md b/WindowsServerDocs/administration/windows-commands/netsh-exec.md index 515c0986ff..9c93b74624 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-exec.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-exec.md @@ -2,8 +2,8 @@ title: netsh exec description: Reference article for the netsh exec command that runs a script file containing a series of netsh commands to automate network configuration tasks. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 07/25/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-http.md b/WindowsServerDocs/administration/windows-commands/netsh-http.md index 73253a3fb1..e117014ccf 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-http.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-http.md @@ -2,8 +2,8 @@ title: netsh http description: The netsh http command configures and manages HTTP traffic for applications and system components for the HTTP Service in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 08/19/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-ipsec.md b/WindowsServerDocs/administration/windows-commands/netsh-ipsec.md index 590b0e6739..49ecf54487 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-ipsec.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-ipsec.md @@ -2,8 +2,8 @@ title: netsh ipsec description: The netsh ipsec command is a suite of commands that configures and manages Internet Protocol Security (IPsec) policies and settings in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 08/04/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-lan.md b/WindowsServerDocs/administration/windows-commands/netsh-lan.md index 383edf8754..a43b608578 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-lan.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-lan.md @@ -2,8 +2,8 @@ title: netsh lan description: Reference article for the netsh lan command that manages and configures LAN settings on your Windows-based computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 07/25/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-mbn.md b/WindowsServerDocs/administration/windows-commands/netsh-mbn.md index 190240a2f8..44d2294fc8 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-mbn.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-mbn.md @@ -2,8 +2,8 @@ title: netsh mbn description: The netsh mbn command manages Mobile Broadband (MBN) interfaces, cellular modems, and SIM-based network connections in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/09/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-namespace.md b/WindowsServerDocs/administration/windows-commands/netsh-namespace.md index 7d09025e50..4cd9137104 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-namespace.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-namespace.md @@ -2,8 +2,8 @@ title: netsh namespace description: The netsh namespace command retrieves namespace policies in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 07/29/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-netio.md b/WindowsServerDocs/administration/windows-commands/netsh-netio.md index 794f630114..62c59750d6 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-netio.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-netio.md @@ -2,8 +2,8 @@ title: netsh netio description: The netsh netio command manages network binding filters in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 08/12/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-nlm.md b/WindowsServerDocs/administration/windows-commands/netsh-nlm.md index b5dbf563e1..7c66d0c53b 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-nlm.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-nlm.md @@ -2,8 +2,8 @@ title: netsh nlm description: The netsh nlm command manages the Network Location Manager (NLM) settings to override network connection quality classification in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/09/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-ras.md b/WindowsServerDocs/administration/windows-commands/netsh-ras.md index e308a5cbfe..676eb4fc94 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-ras.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-ras.md @@ -2,8 +2,8 @@ title: netsh ras description: The netsh ras command manages Remote Access Service (RAS) settings to configure, monitor, and troubleshoot remote access features in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/03/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-rpc.md b/WindowsServerDocs/administration/windows-commands/netsh-rpc.md index da4ef91793..085ed800b0 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-rpc.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-rpc.md @@ -2,8 +2,8 @@ title: netsh rpc description: The netsh rpc command configures and manages Remote Procedure Call (RPC) service settings in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 08/20/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-set.md b/WindowsServerDocs/administration/windows-commands/netsh-set.md index b3639400a3..4948b74577 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-set.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-set.md @@ -2,8 +2,8 @@ title: netsh set description: The netsh set command targets local or remote devices to perform network configuration tasks in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 07/29/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-show.md b/WindowsServerDocs/administration/windows-commands/netsh-show.md index d7ae3925cd..0067a12795 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-show.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-show.md @@ -2,8 +2,8 @@ title: netsh show description: The netsh show command displays the alias and DLL helper modules available within the netsh in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 07/29/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-trace.md b/WindowsServerDocs/administration/windows-commands/netsh-trace.md index ec8e3d7de1..275a7424ab 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-trace.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-trace.md @@ -2,8 +2,8 @@ title: netsh trace description: The netsh trace command captures network traffic and trace events for network diagnostics and troubleshooting in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/06/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-wcn.md b/WindowsServerDocs/administration/windows-commands/netsh-wcn.md index c8655cf2e2..a33450f8ec 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-wcn.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-wcn.md @@ -2,8 +2,8 @@ title: netsh wcn description: The netsh wcn command configures, manages, and troubleshoots Wireless Configuration Network (WCN) settings on Windows devices. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 07/29/2025 --- @@ -58,7 +58,7 @@ netsh wcn query SSID=your-network-ssid interface=your-interface-name The `enroll` parameter starts WPS enrollment with the device identified by the enrollee UUID. The specified network profile is applied using the chosen interface, or the default if none is given. -The device password is usually a 4-digit or 8-digit PIN. Refer to your device’s documentation for its UUID and PIN. If no transport type is set, or "auto" is used, the system selects the best available option. +The device password is usually a 4-digit or 8-digit PIN. Refer to your device's documentation for its UUID and PIN. If no transport type is set, or "auto" is used, the system selects the best available option. ## See also diff --git a/WindowsServerDocs/administration/windows-commands/netsh-wfp.md b/WindowsServerDocs/administration/windows-commands/netsh-wfp.md index 1be24cb7f7..9d811a72e5 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-wfp.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-wfp.md @@ -2,8 +2,8 @@ title: netsh wfp description: The netsh wfp command manages the Windows Filtering Platform (WFP) to capture, display, and analyze network traffic in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 08/11/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-winhttp.md b/WindowsServerDocs/administration/windows-commands/netsh-winhttp.md index fe76349ed7..eb5e53e036 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-winhttp.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-winhttp.md @@ -2,8 +2,8 @@ title: netsh winhttp description: The netsh winhttp command configures and manages WinHTTP settings for network communications for applications that use WinHTTP in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 08/19/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-winsock.md b/WindowsServerDocs/administration/windows-commands/netsh-winsock.md index 9611490e7d..1749e3a65d 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-winsock.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-winsock.md @@ -2,8 +2,8 @@ title: netsh winsock description: The netsh winsock command manages the Windows Sockets (Winsock) API network communication in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 08/12/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/netsh-wlan.md b/WindowsServerDocs/administration/windows-commands/netsh-wlan.md index 7c756876e4..a964f477a6 100644 --- a/WindowsServerDocs/administration/windows-commands/netsh-wlan.md +++ b/WindowsServerDocs/administration/windows-commands/netsh-wlan.md @@ -2,8 +2,8 @@ title: netsh wlan description: The netsh wlan command manages, configures, and helps troubleshoot wireless networking settings in Windows. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/08/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/ntbackup.md b/WindowsServerDocs/administration/windows-commands/ntbackup.md index 55a7ace418..69ea5c1759 100644 --- a/WindowsServerDocs/administration/windows-commands/ntbackup.md +++ b/WindowsServerDocs/administration/windows-commands/ntbackup.md @@ -2,8 +2,8 @@ title: ntbackup description: Reference article for the ntbackup command (replaced with the wbadmin command). ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 04/01/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/refsutil-compression.md b/WindowsServerDocs/administration/windows-commands/refsutil-compression.md index 9c8a4c6d55..e30f5e3cf4 100644 --- a/WindowsServerDocs/administration/windows-commands/refsutil-compression.md +++ b/WindowsServerDocs/administration/windows-commands/refsutil-compression.md @@ -1,8 +1,8 @@ --- title: refsutil compression description: Reference article for the refsutil compression tool, which queries or modifies compression settings on a Resilient File System (ReFS) volume in Windows. -author: xelu86 -ms.author: alalve +author: dknappettmsft +ms.author: daknappe ms.date: 04/02/2025 ms.topic: reference --- diff --git a/WindowsServerDocs/administration/windows-commands/refsutil-dedup.md b/WindowsServerDocs/administration/windows-commands/refsutil-dedup.md index 2844013ce1..98b2ddf647 100644 --- a/WindowsServerDocs/administration/windows-commands/refsutil-dedup.md +++ b/WindowsServerDocs/administration/windows-commands/refsutil-dedup.md @@ -1,8 +1,8 @@ --- title: refsutil dedup description: Reference article for the refsutil dedup tool, which deduplicates a Resilient File System (ReFS) volume in Windows. -author: xelu86 -ms.author: alalve +author: dknappettmsft +ms.author: daknappe ms.date: 04/02/2025 ms.topic: reference --- diff --git a/WindowsServerDocs/administration/windows-commands/refsutil-fixboot.md b/WindowsServerDocs/administration/windows-commands/refsutil-fixboot.md index 324da64dff..9668b26e74 100644 --- a/WindowsServerDocs/administration/windows-commands/refsutil-fixboot.md +++ b/WindowsServerDocs/administration/windows-commands/refsutil-fixboot.md @@ -1,8 +1,8 @@ --- title: refsutil fixboot description: Reference article for the refsutil fixboot tool, which repairs or updates the boot sector of a ReFS (Resilient File System) volume in Windows. -author: xelu86 -ms.author: alalve +author: dknappettmsft +ms.author: daknappe ms.date: 04/02/2025 ms.topic: reference --- diff --git a/WindowsServerDocs/administration/windows-commands/refsutil-iometrics.md b/WindowsServerDocs/administration/windows-commands/refsutil-iometrics.md index f113c74691..28f07435fa 100644 --- a/WindowsServerDocs/administration/windows-commands/refsutil-iometrics.md +++ b/WindowsServerDocs/administration/windows-commands/refsutil-iometrics.md @@ -1,8 +1,8 @@ --- title: refsutil iometrics description: Reference article for the refsutil iometrics tool, which tracks IO data to monitor performance and usage patterns on a Resilient File System (ReFS) volume in Windows. -author: xelu86 -ms.author: alalve +author: robinharwood +ms.author: roharwoo ms.date: 04/02/2025 ms.topic: reference --- diff --git a/WindowsServerDocs/administration/windows-commands/refsutil-leak.md b/WindowsServerDocs/administration/windows-commands/refsutil-leak.md index 9ba15895bd..832d54bf2f 100644 --- a/WindowsServerDocs/administration/windows-commands/refsutil-leak.md +++ b/WindowsServerDocs/administration/windows-commands/refsutil-leak.md @@ -1,8 +1,8 @@ --- title: refsutil leak description: Reference article for the refsutil leak tool, which detects and diagnoses storage leaks, revealing their location and size to optimize storage usage on a specified Resilient File System (ReFS) volume in Windows. -author: xelu86 -ms.author: alalve +author: dknappettmsft +ms.author: daknappe ms.date: 04/03/2025 ms.topic: reference --- diff --git a/WindowsServerDocs/administration/windows-commands/refsutil-salvage.md b/WindowsServerDocs/administration/windows-commands/refsutil-salvage.md index 4c46492689..40e6cee85b 100644 --- a/WindowsServerDocs/administration/windows-commands/refsutil-salvage.md +++ b/WindowsServerDocs/administration/windows-commands/refsutil-salvage.md @@ -1,8 +1,8 @@ --- title: refsutil salvage description: Reference article for the refsutil salvage tool, which attempts to diagnose and recover a damaged Resilient File System (ReFS) volume by copying data to another volume in Windows. -author: xelu86 -ms.author: alalve +author: robinharwood +ms.author: roharwoo ms.date: 04/02/2025 ms.topic: reference --- diff --git a/WindowsServerDocs/administration/windows-commands/refsutil-streamsnapshot.md b/WindowsServerDocs/administration/windows-commands/refsutil-streamsnapshot.md index 2ffc6acb07..025039186f 100644 --- a/WindowsServerDocs/administration/windows-commands/refsutil-streamsnapshot.md +++ b/WindowsServerDocs/administration/windows-commands/refsutil-streamsnapshot.md @@ -1,8 +1,8 @@ --- title: refsutil streamsnapshot description: Reference article for the refsutil streamsnapshot tool, which manages Resilient File System (ReFS) data stream snapshots where you can create, delete, list, or compare snapshots in Windows. -author: xelu86 -ms.author: alalve +author: robinharwood +ms.author: roharwoo ms.date: 04/02/2025 ms.topic: reference --- diff --git a/WindowsServerDocs/administration/windows-commands/refsutil-triage.md b/WindowsServerDocs/administration/windows-commands/refsutil-triage.md index ebfa5bc88a..764bb29024 100644 --- a/WindowsServerDocs/administration/windows-commands/refsutil-triage.md +++ b/WindowsServerDocs/administration/windows-commands/refsutil-triage.md @@ -1,8 +1,8 @@ --- title: refsutil triage description: Reference article for the refsutil triage tool, which ensures data integrity and consistency by scrubbing the directory contents or global tables on a ReFS (Resilient File System) volume in Windows. -author: xelu86 -ms.author: alalve +author: dknappettmsft +ms.author: daknappe ms.date: 04/02/2025 ms.topic: reference --- diff --git a/WindowsServerDocs/administration/windows-commands/refsutil.md b/WindowsServerDocs/administration/windows-commands/refsutil.md index 62d4fa4dc6..c0fed085b3 100644 --- a/WindowsServerDocs/administration/windows-commands/refsutil.md +++ b/WindowsServerDocs/administration/windows-commands/refsutil.md @@ -1,8 +1,8 @@ --- title: refsutil description: Reference article for the refsutil tool, which manages and repairs Resilient File System (ReFS) volumes in Windows ensuring their integrity, performance, and optimization. -author: xelu86 -ms.author: alalve +author: robinharwood +ms.author: roharwoo ms.date: 04/02/2025 ms.topic: reference --- diff --git a/WindowsServerDocs/administration/windows-commands/reg-add.md b/WindowsServerDocs/administration/windows-commands/reg-add.md index 2656245f50..13b6d36d3d 100644 --- a/WindowsServerDocs/administration/windows-commands/reg-add.md +++ b/WindowsServerDocs/administration/windows-commands/reg-add.md @@ -2,8 +2,8 @@ title: reg add description: Reference article for the reg add command, which adds a new subkey or entry to the registry. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 01/04/2024 --- diff --git a/WindowsServerDocs/administration/windows-commands/reg-delete.md b/WindowsServerDocs/administration/windows-commands/reg-delete.md index 5d60334620..953540c9aa 100644 --- a/WindowsServerDocs/administration/windows-commands/reg-delete.md +++ b/WindowsServerDocs/administration/windows-commands/reg-delete.md @@ -2,8 +2,8 @@ title: reg delete description: Reference article for the reg delete command, which deletes a key, subkey, or entries from the registry. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/20/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/reg-import.md b/WindowsServerDocs/administration/windows-commands/reg-import.md index 144ce5972a..f0fc122731 100644 --- a/WindowsServerDocs/administration/windows-commands/reg-import.md +++ b/WindowsServerDocs/administration/windows-commands/reg-import.md @@ -2,8 +2,8 @@ title: reg import description: Reference article for the reg import command, which copies the contents of a file that contains exported registry subkeys, entries, and values into the registry of the local computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/20/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/reg-query.md b/WindowsServerDocs/administration/windows-commands/reg-query.md index be5f5e3e1d..b5dc811310 100644 --- a/WindowsServerDocs/administration/windows-commands/reg-query.md +++ b/WindowsServerDocs/administration/windows-commands/reg-query.md @@ -2,8 +2,8 @@ title: reg query description: Reference article for the reg query command, which returns a list of the next tier of subkeys and entries that are located under a specified subkey in the registry. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 11/02/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/robocopy.md b/WindowsServerDocs/administration/windows-commands/robocopy.md index 788c8bac2f..bf7aa8aba4 100644 --- a/WindowsServerDocs/administration/windows-commands/robocopy.md +++ b/WindowsServerDocs/administration/windows-commands/robocopy.md @@ -2,8 +2,8 @@ title: Robocopy description: Reference article for the robocopy command, which copies file data from one location to another. ms.topic: reference -author: xelu86 -ms.author: alalve +author: dknappettmsft +ms.author: daknappe ms.date: 03/17/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/sc-create.md b/WindowsServerDocs/administration/windows-commands/sc-create.md index ff7f841115..df25258084 100644 --- a/WindowsServerDocs/administration/windows-commands/sc-create.md +++ b/WindowsServerDocs/administration/windows-commands/sc-create.md @@ -2,8 +2,8 @@ title: sc.exe create description: Reference article for the sc.exe create command, which creates a subkey and entries for a service in the registry and in the Service Control Manager database. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 09/29/2023 ms.custom: sfi-ropc-nochange --- diff --git a/WindowsServerDocs/administration/windows-commands/schtasks-create.md b/WindowsServerDocs/administration/windows-commands/schtasks-create.md index ae9b847222..de5b2cec35 100644 --- a/WindowsServerDocs/administration/windows-commands/schtasks-create.md +++ b/WindowsServerDocs/administration/windows-commands/schtasks-create.md @@ -2,8 +2,8 @@ title: schtasks create description: Reference article for the schtasks create command to automate tasks. ms.topic: reference -author: xelu86 -ms.author: alalve +author: robinharwood +ms.author: roharwoo ms.date: 10/10/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/schtasks-query.md b/WindowsServerDocs/administration/windows-commands/schtasks-query.md index d3c7722b4e..8f84cfaefd 100644 --- a/WindowsServerDocs/administration/windows-commands/schtasks-query.md +++ b/WindowsServerDocs/administration/windows-commands/schtasks-query.md @@ -2,8 +2,8 @@ title: schtasks query description: Reference article for the schtasks query command, which lists all the tasks scheduled to run on the computer. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 02/13/2024 --- diff --git a/WindowsServerDocs/administration/windows-commands/schtasks.md b/WindowsServerDocs/administration/windows-commands/schtasks.md index 9478033b22..355ab1192d 100644 --- a/WindowsServerDocs/administration/windows-commands/schtasks.md +++ b/WindowsServerDocs/administration/windows-commands/schtasks.md @@ -2,8 +2,8 @@ title: schtasks commands description: Reference article for the schtasks commands, which schedules commands and programs to run periodically or at a specific time, adds and removes tasks from the schedule, starts and stops tasks on demand, and displays and changes scheduled tasks. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 02/01/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/set_1.md b/WindowsServerDocs/administration/windows-commands/set_1.md index bfa27a8196..64ab01b1bb 100644 --- a/WindowsServerDocs/administration/windows-commands/set_1.md +++ b/WindowsServerDocs/administration/windows-commands/set_1.md @@ -2,8 +2,8 @@ title: set description: Reference article for set, which displays, sets, or removes cmd.exe environment variables. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 09/06/2023 --- @@ -68,7 +68,7 @@ set /a = - If you run **set /a** from the command line outside of a command script, it displays the final value of the expression. -- Numeric values are decimal numbers unless prefixed by 0× for hexadecimal numbers or 0 for octal numbers. Therefore, 0×12 is the same as 18, which is the same as 022. +- Numeric values are decimal numbers unless prefixed by 0x for hexadecimal numbers or 0 for octal numbers. Therefore, 0x12 is the same as 18, which is the same as 022. - Delayed environment variable expansion support is disabled by default, but you can enable or disable it by using **cmd /v**. diff --git a/WindowsServerDocs/administration/windows-commands/setspn.md b/WindowsServerDocs/administration/windows-commands/setspn.md index f38bc521f8..d13410a88a 100644 --- a/WindowsServerDocs/administration/windows-commands/setspn.md +++ b/WindowsServerDocs/administration/windows-commands/setspn.md @@ -1,15 +1,15 @@ --- title: Setspn -description: The setspn command reads, modifies, and deletes the Service Principal Names (SPN) directory property for an Active Directory service account. +description: The setspn command reads, modifies, and deletes the Service Principal Names (SPN) directory property for an Active Directory service account. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 03/24/2025 --- # setspn -The `setspn` command line utility reads, modifies, and deletes the Service Principal Names (SPN) directory property for an Active Directory (AD) service account. You use SPNs to locate a target principal name for running a service. You can use `setspn` to view the current SPNs, reset the account's default SPNs, and add or delete supplemental SPNs. `Setspn` is available if you have the Active Directory Domain Services (AD DS) server role installed. `Setspn` must be ran through an elevated command prompt. +The `setspn` command line utility reads, modifies, and deletes the Service Principal Names (SPN) directory property for an Active Directory (AD) service account. You use SPNs to locate a target principal name for running a service. You can use `setspn` to view the current SPNs, reset the account's default SPNs, and add or delete supplemental SPNs. `Setspn` is available if you have the Active Directory Domain Services (AD DS) server role installed. `Setspn` must be ran through an elevated command prompt. ## Syntax @@ -53,7 +53,7 @@ Query Mode modifiers can be used with the `-S` switch in order to specify where - SPNs must be constructed using the base name of the account specified as the _accountname_ parameter. If this condition isn't met, the directory service returns a constraint violation error. -You might not have the rights to access or modify this property on some account objects. You can determine what your access rights are by viewing the security attributes of the account object using the Microsoft Management Console (MMC) in Active Directory Users and Computers. You can also delegate the permission by assigning the Validated write to service principal name permission to the desired user or group. +You might not have the rights to access or modify this property on some account objects. You can determine what your access rights are by viewing the security attributes of the account object using the Microsoft Management Console (MMC) in Active Directory Users and Computers. You can also delegate the permission by assigning the Validated write to service principal name permission to the desired user or group. The built-in SPNs that are recognized for computer accounts are: diff --git a/WindowsServerDocs/administration/windows-commands/sfc.md b/WindowsServerDocs/administration/windows-commands/sfc.md index fe349b38d1..c3c435caec 100644 --- a/WindowsServerDocs/administration/windows-commands/sfc.md +++ b/WindowsServerDocs/administration/windows-commands/sfc.md @@ -2,8 +2,8 @@ title: sfc description: Reference article for the sfc command, which scans and verifies the integrity of all protected system files and replaces incorrect versions with correct versions. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/19/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/shutdown.md b/WindowsServerDocs/administration/windows-commands/shutdown.md index 780c0fe53a..2fba57aab9 100644 --- a/WindowsServerDocs/administration/windows-commands/shutdown.md +++ b/WindowsServerDocs/administration/windows-commands/shutdown.md @@ -2,8 +2,8 @@ title: shutdown description: Reference article for the shutdown command, which enables you to shut down or restart local or remote computers, one at a time. ms.topic: reference -author: xelu86 -ms.author: alalve +author: robinharwood +ms.author: roharwoo ms.date: 05/01/2025 --- @@ -28,7 +28,7 @@ shutdown [/i | /l | /s | /sg | /r | /g | /a | /p | /h | /e | /o] [/hybrid] [/sof | /r | Restarts the computer after shutdown. | | /g | Fully shuts down and restarts the computer. On restart, if **Automatic Restart Sign-On** is enabled, the device automatically signs in and locks based on the last interactive user. After sign in, it restarts any registered applications. | | /a | Aborts a system shutdown. Can only be used during the time-out period. Combine with **/fw** to clear any pending boots to firmware. | -| /p | Turns off the local computer only (not a remote computer)—with no time-out period or warning. You can use **/p** only with **/d** or **/f**. If your computer doesn't support power-off functionality, it shuts down when you use **/p**, but the power to the computer remains on. | +| /p | Turns off the local computer only (not a remote computer) with no time-out period or warning. You can use **/p** only with **/d** or **/f**. If your computer doesn't support power-off functionality, it shuts down when you use **/p**, but the power to the computer remains on. | | /h | Puts the local computer into hibernation, if hibernation is enabled. The **/f** switch can be used with the **/h** switch. | | /hybrid | Shuts down the device and prepares it for fast startup. This option must be used with the **/s** option. | | /soft | Allows running processes and applications to gracefully close instead of forcibly terminating. | diff --git a/WindowsServerDocs/administration/windows-commands/start.md b/WindowsServerDocs/administration/windows-commands/start.md index 361d3d43f7..bec748518a 100644 --- a/WindowsServerDocs/administration/windows-commands/start.md +++ b/WindowsServerDocs/administration/windows-commands/start.md @@ -2,8 +2,8 @@ title: start description: Reference article for the start command, which starts a separate Command Prompt window to run a specified program or command. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/02/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/typeperf.md b/WindowsServerDocs/administration/windows-commands/typeperf.md index 2c7963f649..34dfd037bb 100644 --- a/WindowsServerDocs/administration/windows-commands/typeperf.md +++ b/WindowsServerDocs/administration/windows-commands/typeperf.md @@ -2,8 +2,8 @@ title: typeperf description: Reference article for the typeperf command, which writes performance data to the command window or to a log file. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 06/15/2023 --- diff --git a/WindowsServerDocs/administration/windows-commands/ver.md b/WindowsServerDocs/administration/windows-commands/ver.md index 1f7d573b4a..df28ebe39e 100644 --- a/WindowsServerDocs/administration/windows-commands/ver.md +++ b/WindowsServerDocs/administration/windows-commands/ver.md @@ -2,8 +2,8 @@ title: ver description: Reference article for the ver command, which displays the operating system version number. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/20/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/verifier.md b/WindowsServerDocs/administration/windows-commands/verifier.md index 94698e4eda..ee8d370958 100644 --- a/WindowsServerDocs/administration/windows-commands/verifier.md +++ b/WindowsServerDocs/administration/windows-commands/verifier.md @@ -2,8 +2,8 @@ title: verifier description: Reference article for the verifier command, which runs the Driver Verifier manager utility. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/20/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/verify.md b/WindowsServerDocs/administration/windows-commands/verify.md index ae67011144..c41378cd35 100644 --- a/WindowsServerDocs/administration/windows-commands/verify.md +++ b/WindowsServerDocs/administration/windows-commands/verify.md @@ -2,8 +2,8 @@ title: verify description: Reference article for the verify command, which tells the Command Prompt tool whether to verify your files are written correctly to a disk. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 11/01/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-add-alldriverpackages.md b/WindowsServerDocs/administration/windows-commands/wdsutil-add-alldriverpackages.md index 471f1f77b5..05156ba62c 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-add-alldriverpackages.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-add-alldriverpackages.md @@ -2,8 +2,8 @@ title: wdsutil add-alldriverpackages description: Reference article for the wdsutil add-alldriverpackages command, which adds all driver packages that are stored in a folder to a server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-add-device.md b/WindowsServerDocs/administration/windows-commands/wdsutil-add-device.md index 7e336c8183..7ea0d85423 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-add-device.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-add-device.md @@ -2,8 +2,8 @@ title: wdsutil add-device description: Reference article for the wdsutil add-device command, which pre-stages a computer in Active Directory Domain Services. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergroup.md b/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergroup.md index 965650f71f..c3252a9293 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergroup.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergroup.md @@ -2,8 +2,8 @@ title: wdsutil add-drivergroup description: Reference article for the wdsutil add-drivergroup command, which adds a driver group to the server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergroupfilter.md b/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergroupfilter.md index 1222e970d8..be5d952e07 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergroupfilter.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergroupfilter.md @@ -2,8 +2,8 @@ title: add-DriverGroupFilter description: Reference article for the add-DriverGroupFilter command, which adds a filter to a driver group on a server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergrouppackage.md b/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergrouppackage.md index 6973f6aad7..365c862563 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergrouppackage.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergrouppackage.md @@ -2,8 +2,8 @@ title: wdsutil add-drivergrouppackage description: Reference article for the wdsutil add-drivergrouppackage command, which adds a driver package to a driver group. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergrouppackages.md b/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergrouppackages.md index 5c1624a372..0305f37c00 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergrouppackages.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-add-drivergrouppackages.md @@ -2,8 +2,8 @@ title: wdsutil add-drivergrouppackages description: Reference article for the wdsutil add-drivergrouppackages command, which add driver group packages. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-add-driverpackage.md b/WindowsServerDocs/administration/windows-commands/wdsutil-add-driverpackage.md index 81b54ebaa1..f04aab6f21 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-add-driverpackage.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-add-driverpackage.md @@ -2,8 +2,8 @@ title: add-DriverPackage description: Reference article for the add-DriverPackage command, which adds a driver package to the server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-add-image.md b/WindowsServerDocs/administration/windows-commands/wdsutil-add-image.md index 04f3970ea0..877b78fe72 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-add-image.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-add-image.md @@ -2,8 +2,8 @@ title: wdsutil add-image description: Reference article for the wdsutil add-image command, which adds images to a Windows Deployment Services server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 06/30/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-add-imagedriverpackage.md b/WindowsServerDocs/administration/windows-commands/wdsutil-add-imagedriverpackage.md index 143a0f7a0c..d14d23e5b7 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-add-imagedriverpackage.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-add-imagedriverpackage.md @@ -2,8 +2,8 @@ title: wdsutil add-imagedriverpackage description: Reference article for the wdsutil add-imagedriverpackage command, which adds a driver package that is in the driver store to an existing boot image on the server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-add-imagedriverpackages.md b/WindowsServerDocs/administration/windows-commands/wdsutil-add-imagedriverpackages.md index 353f9ed53c..6e898ee8c2 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-add-imagedriverpackages.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-add-imagedriverpackages.md @@ -2,8 +2,8 @@ title: wdsutil add-imagedriverpackages description: Reference article for the wdsutil add-imagedriverpackages command, which adds driver packages from the driver store to a boot image. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-add-imagegroup.md b/WindowsServerDocs/administration/windows-commands/wdsutil-add-imagegroup.md index 14bb2a91ea..5283c11b22 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-add-imagegroup.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-add-imagegroup.md @@ -2,8 +2,8 @@ title: wdsutil add-imagegroup description: Reference article for the wdsutil add-imagegroup command, which adds an image group to a Windows Deployment Services server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-add.md b/WindowsServerDocs/administration/windows-commands/wdsutil-add.md index 053c404c19..d51d00448c 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-add.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-add.md @@ -2,8 +2,8 @@ title: wdsutil add description: Reference article for the wdsutil add commands. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-approve-autoadddevices.md b/WindowsServerDocs/administration/windows-commands/wdsutil-approve-autoadddevices.md index c084d43875..960c414e85 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-approve-autoadddevices.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-approve-autoadddevices.md @@ -2,8 +2,8 @@ title: wdsutil approve-autoadddevices description: Reference article for the wdsutil approve-autoadddevices command, which approves computers that are pending administrative approval. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-convert-riprepimage.md b/WindowsServerDocs/administration/windows-commands/wdsutil-convert-riprepimage.md index d17d61b039..a9c3beb623 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-convert-riprepimage.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-convert-riprepimage.md @@ -2,8 +2,8 @@ title: convert-riprepimage description: Reference article for the convert-riprepimage command, which converts an existing Remote Installation Preparation (RIPrep) image to Windows Image (.wim) format. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-copy-drivergroup.md b/WindowsServerDocs/administration/windows-commands/wdsutil-copy-drivergroup.md index 99d8f35ff8..4175ed9b96 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-copy-drivergroup.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-copy-drivergroup.md @@ -2,8 +2,8 @@ title: copy-drivergroup description: Reference article for the copy-drivergroup command, which duplicates an existing driver group on the server including the filters, driver packages, and enabled/disabled status. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-copy-image.md b/WindowsServerDocs/administration/windows-commands/wdsutil-copy-image.md index e96ac9398c..96ec3e5643 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-copy-image.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-copy-image.md @@ -2,8 +2,8 @@ title: wdsutil copy-image description: Reference article for the wdsutil copy-image command, which copies images that are within the same image group. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-copy.md b/WindowsServerDocs/administration/windows-commands/wdsutil-copy.md index cdfb5ea743..b4318db01b 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-copy.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-copy.md @@ -2,8 +2,8 @@ title: wdsutil copy description: Reference article for the wdsutil copy commands, which copies an image or a driver group. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-delete-autoadddevices.md b/WindowsServerDocs/administration/windows-commands/wdsutil-delete-autoadddevices.md index 48dcad7168..f26c04cea3 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-delete-autoadddevices.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-delete-autoadddevices.md @@ -2,8 +2,8 @@ title: wdsutil delete-autoadddevices description: Reference article for the wdsutil delete-autoadddevices command, which deletes computers that are pending, rejected, or approved from the Auto-add database. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-disable-server.md b/WindowsServerDocs/administration/windows-commands/wdsutil-disable-server.md index ec486a60d4..fe3f1da526 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-disable-server.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-disable-server.md @@ -2,8 +2,8 @@ title: wdsutil disable-server description: Reference article for the wdsutil disable-server command, which disables all services for a Windows Deployment Services server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-disable-transportserver.md b/WindowsServerDocs/administration/windows-commands/wdsutil-disable-transportserver.md index 4b027a8b07..de8903cf43 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-disable-transportserver.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-disable-transportserver.md @@ -2,8 +2,8 @@ title: wdsutil disable-transportserver description: Reference article for the wdsutil disable-transportserver command, which disables all services for a Transport Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-disable.md b/WindowsServerDocs/administration/windows-commands/wdsutil-disable.md index 649133baa5..815a80c555 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-disable.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-disable.md @@ -2,8 +2,8 @@ title: wdsutil disable description: Reference article for the wdsutil disable commands, which disables all services for Windows Deployment Services. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-disconnect-client.md b/WindowsServerDocs/administration/windows-commands/wdsutil-disconnect-client.md index 36a1ecfb88..28d4caf779 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-disconnect-client.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-disconnect-client.md @@ -2,8 +2,8 @@ title: wdsutil disconnect-client description: Reference article for the wdsutil disconnect-client command, which disconnects a client from a multicast transmission or namespace. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-enable-server.md b/WindowsServerDocs/administration/windows-commands/wdsutil-enable-server.md index 70f783604d..cecdf706e2 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-enable-server.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-enable-server.md @@ -2,8 +2,8 @@ title: wdsutil enable-server description: Reference article for the wdsutil enable-server command, which enables all services for Windows Deployment Services. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-enable-transportserver.md b/WindowsServerDocs/administration/windows-commands/wdsutil-enable-transportserver.md index 758f2635a5..011d63e446 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-enable-transportserver.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-enable-transportserver.md @@ -2,8 +2,8 @@ title: wdsutil enable-transportserver description: Reference article for the wdsutil enable-transportserver command, which enables all services for the Transport Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-enable.md b/WindowsServerDocs/administration/windows-commands/wdsutil-enable.md index 0ca9b5e3e5..1e1987f3fe 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-enable.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-enable.md @@ -2,8 +2,8 @@ title: wdsutil enable description: Reference article for the wdsutil enable commands, which enables all services for Windows Deployment Services. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-export-image.md b/WindowsServerDocs/administration/windows-commands/wdsutil-export-image.md index 4073ce5e33..5687039994 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-export-image.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-export-image.md @@ -2,8 +2,8 @@ title: wdsutil export-image description: Reference article for the wdsutil export-image command, which exports an existing image from the image store to another Windows Image (.wim) file. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-alldevices.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-alldevices.md index 3794c3fb51..ae4e3c7126 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-alldevices.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-alldevices.md @@ -2,8 +2,8 @@ title: wdsutil get-alldevices description: Reference article for the wdsutil get-alldevices command, which displays the Windows Deployment Services properties of all pre-staged computers. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-alldrivergroups.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-alldrivergroups.md index fd56d8c30c..86e447eb28 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-alldrivergroups.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-alldrivergroups.md @@ -2,8 +2,8 @@ title: wdsutil get-alldrivergroups description: Reference article for the wdsutil get-alldrivergroups command, which displays information about all the driver groups on a server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-alldriverpackages.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-alldriverpackages.md index 141721a343..9dc792660d 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-alldriverpackages.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-alldriverpackages.md @@ -2,8 +2,8 @@ title: wdsutil get-alldriverpackages description: Reference article for the wdsutil get-alldriverpackages command, which displays information about all the driver packages on a server that match the specified search criteria. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-allimagegroups.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-allimagegroups.md index 957353d53b..8a4f277e90 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-allimagegroups.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-allimagegroups.md @@ -2,8 +2,8 @@ title: wdsutil get-allimagegroups description: Reference article for the wdsutil get-allimagegroups command, which retrieves information about all image groups on a server and all images in those image groups. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-allimages.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-allimages.md index 280b4a9912..38b3cb4468 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-allimages.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-allimages.md @@ -2,8 +2,8 @@ title: wdsutil get-allimages description: Reference article for the wdsutil get-allimages command, which retrieves information about all images on a server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-allmulticasttransmissions.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-allmulticasttransmissions.md index 6133171cde..091aeecc0a 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-allmulticasttransmissions.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-allmulticasttransmissions.md @@ -2,8 +2,8 @@ title: wdsutil get-allmulticasttransmissions description: Reference article for wdsutil get-allmulticasttransmissions, which displays information about all multicast transmissions on a server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-allnamespaces.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-allnamespaces.md index d98f9a231a..5476c450f5 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-allnamespaces.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-allnamespaces.md @@ -2,8 +2,8 @@ title: wdsutil get-allnamespaces description: Reference article for wdsutil get-allnamespaces, which displays information about all namespaces on a server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-allservers.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-allservers.md index e4154d2c18..a621018b02 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-allservers.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-allservers.md @@ -2,8 +2,8 @@ title: get-AllServers description: Reference article for get-AllServers, which retrieves information about all Windows Deployment Services servers. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-autoadddevices.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-autoadddevices.md index f59f8eb14a..9cfa172f46 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-autoadddevices.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-autoadddevices.md @@ -2,8 +2,8 @@ title: wdsutil get-autoadddevices description: Reference article for wdsutil get-autoadddevices, which displays all computers that are in the Auto-add database on a Windows Deployment Services server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-device.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-device.md index 44aeffd1e1..3352b91335 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-device.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-device.md @@ -2,8 +2,8 @@ title: wdsutil get-device description: Reference article for wdsutil get-device, which retrieves Windows Deployment Services information about a prestaged computer (that is, a physical computer that has been lined to a computer account in active directory Domain Services. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-drivergroup.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-drivergroup.md index af3e13293f..9fd48057de 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-drivergroup.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-drivergroup.md @@ -2,8 +2,8 @@ title: wdsutil get-drivergroup description: Reference article for wdsutil get-drivergroup, which displays information about the driver groups on a server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-driverpackage.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-driverpackage.md index d19ef976f3..60260be35b 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-driverpackage.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-driverpackage.md @@ -2,8 +2,8 @@ title: get-DriverPackage description: Reference article for get-DriverPackage, which displays information about a driver package on the server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-driverpackagefile.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-driverpackagefile.md index dcb9c4d081..9f0cf23c6e 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-driverpackagefile.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-driverpackagefile.md @@ -2,8 +2,8 @@ title: wdsutil get-driverpackagefile description: Reference article for wdsutil get-driverpackagefile, which displays information about a driver package, including the drivers and files it contains. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 08/19/2024 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-image.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-image.md index 87cfc66686..2b0be01aaf 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-image.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-image.md @@ -2,8 +2,8 @@ title: wdsutil get-image description: Reference article for wdsutil get-image, which retrieves information about an image. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-imagefile.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-imagefile.md index e891151882..6d2069492a 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-imagefile.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-imagefile.md @@ -2,8 +2,8 @@ title: get-ImageFile description: Reference article for get-ImageFile, which retrieves information about the images contained in a Windows Image (.wim) file. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-imagegroup.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-imagegroup.md index c8c92fd3a1..b61aebccc9 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-imagegroup.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-imagegroup.md @@ -2,8 +2,8 @@ title: wdsutil get-imagegroup description: Reference article for wdsutil get-imagegroup, which retrieves information about an image group and the images in it. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-multicasttransmission.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-multicasttransmission.md index 575a12daee..11c25b0186 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-multicasttransmission.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-multicasttransmission.md @@ -2,8 +2,8 @@ title: wdsutil get-multicasttransmission description: Reference article for wdsutil get-multicasttransmission, which displays information about the multicast transmission for a specified image. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-namespace.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-namespace.md index 7e5e2efbd6..a1e1371cb2 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-namespace.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-namespace.md @@ -2,8 +2,8 @@ title: wdsutil get-namespace description: Reference article for wdsutil get-namespace, which displays information about a custom namespace. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-server.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-server.md index 845c5d81ee..b943310b1d 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-server.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-server.md @@ -2,8 +2,8 @@ title: wdsutil get-server description: Reference article for wdsutil get-server, which retrieves information from the specified Windows Deployment Services server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get-transportserver.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get-transportserver.md index ee92ef9394..7d3b3972d4 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get-transportserver.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get-transportserver.md @@ -2,8 +2,8 @@ title: wdsutil get-transportserver description: Reference article for wdsutil get-transportserver, which displays information about a specified Transport Server. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 10/16/2017 --- diff --git a/WindowsServerDocs/administration/windows-commands/wdsutil-get.md b/WindowsServerDocs/administration/windows-commands/wdsutil-get.md index 9acdee77fd..97a09cdfb0 100644 --- a/WindowsServerDocs/administration/windows-commands/wdsutil-get.md +++ b/WindowsServerDocs/administration/windows-commands/wdsutil-get.md @@ -2,8 +2,8 @@ title: wdsutil get description: Reference article for wdsutil get command, which retrieves properties or attributes about the specified object. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: roharwoo +author: robinharwood ms.date: 08/19/2024 --- diff --git a/WindowsServerDocs/administration/windows-commands/wevtutil.md b/WindowsServerDocs/administration/windows-commands/wevtutil.md index a909202716..5c82d76cdd 100644 --- a/WindowsServerDocs/administration/windows-commands/wevtutil.md +++ b/WindowsServerDocs/administration/windows-commands/wevtutil.md @@ -2,8 +2,8 @@ title: wevtutil description: Reference article for wevtutil, which lets you retrieve information about event logs and publishers. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 10/26/2022 --- diff --git a/WindowsServerDocs/administration/windows-commands/whoami.md b/WindowsServerDocs/administration/windows-commands/whoami.md index 7caf107d33..8a6238ae87 100644 --- a/WindowsServerDocs/administration/windows-commands/whoami.md +++ b/WindowsServerDocs/administration/windows-commands/whoami.md @@ -2,8 +2,8 @@ title: whoami description: Reference article for whoami, which displays user, group and privileges information for the user who is currently logged on to the local system. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 05/23/2025 --- diff --git a/WindowsServerDocs/administration/windows-commands/wmic.md b/WindowsServerDocs/administration/windows-commands/wmic.md index 097e95e7b4..66a146365a 100644 --- a/WindowsServerDocs/administration/windows-commands/wmic.md +++ b/WindowsServerDocs/administration/windows-commands/wmic.md @@ -2,8 +2,8 @@ title: wmic description: Reference article for wmic, which displays WMI information inside an interactive command shell. ms.topic: reference -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 05/19/2025 --- @@ -12,7 +12,7 @@ ms.date: 05/19/2025 Displays WMI information inside an interactive command shell. > [!IMPORTANT] -> The WMI command-line (WMIC) utility is deprecated as of Windows 10, version 21H1, and as of the 21H1 semi-annual channel release of Windows Server. This utility is superseded by Windows PowerShell for WMI (see [Chapter 7—Working with WMI](/powershell/scripting/learn/ps101/07-working-with-wmi)). This deprecation applies only to the WMI command-line (WMIC) utility; Windows Management Instrumentation (WMI) itself is not affected. Also see [Windows 10 features we're no longer developing](/windows/deployment/planning/windows-10-deprecated-features). +> The WMI command-line (WMIC) utility is deprecated as of Windows 10, version 21H1, and as of the 21H1 semi-annual channel release of Windows Server. This utility is superseded by Windows PowerShell for WMI (see [Chapter 7 - Working with WMI](/powershell/scripting/learn/ps101/07-working-with-wmi)). This deprecation applies only to the WMI command-line (WMIC) utility; Windows Management Instrumentation (WMI) itself is not affected. Also see [Windows 10 features we're no longer developing](/windows/deployment/planning/windows-10-deprecated-features). ## Syntax diff --git a/WindowsServerDocs/breadcrumbs/toc.yml b/WindowsServerDocs/breadcrumbs/toc.yml index 474ef98553..a905e3f583 100644 --- a/WindowsServerDocs/breadcrumbs/toc.yml +++ b/WindowsServerDocs/breadcrumbs/toc.yml @@ -65,12 +65,12 @@ items: ### For linking to HCI topics and keeping the context in Windows Server TOC - name: Windows Server tocHref: /azure/azure-local/ - topicHref: /windows-server/index + topicHref: /windows-server/virtualization/hyper-v/ ### For linking to system center topics and keeping the context in Windows Server TOC -- name: Windows Server # Destination doc set name - tocHref: /system-center/ # Destination doc set route - topicHref: /windows-server/ # Original doc set route +- name: Windows Server + tocHref: /system-center/ + topicHref: /windows-server/ ### For linking to Azure topic and keeping the context in Windows Server TOC - name: Windows Server @@ -84,4 +84,4 @@ items: items: - name: Security tocHref: /windows/security/ - topicHref: /windows-server/security/security-and-assurance \ No newline at end of file + topicHref: /windows-server/security/security-and-assurance diff --git a/WindowsServerDocs/context/windows-server-virtualization.yml b/WindowsServerDocs/context/windows-server-virtualization.yml index a5c9677907..0c1ae7ade6 100644 --- a/WindowsServerDocs/context/windows-server-virtualization.yml +++ b/WindowsServerDocs/context/windows-server-virtualization.yml @@ -1,4 +1,4 @@ ### YamlMime: ContextObject uhfHeaderId: MSDocsHeader-WindowsServer breadcrumb_path: /windows-server/breadcrumbs/toc.json -toc_rel: /windows-server/virtualization/ \ No newline at end of file +toc_rel: /windows-server/virtualization/hyper-v/ diff --git a/WindowsServerDocs/docfx.json b/WindowsServerDocs/docfx.json index 0ef8f00730..af0cf9a8bc 100644 --- a/WindowsServerDocs/docfx.json +++ b/WindowsServerDocs/docfx.json @@ -199,6 +199,11 @@ "✅ Windows Server 2019", "✅ Windows Server 2016" ], + "failover-clustering/configure-live-migration-smb-bandwidth.md": [ + "✅ Windows Server 2025", + "✅ Windows Server 2022", + "✅ Azure Local 2311.2 and later" + ], "get-started/**/*.md": [ "✅ Windows Server 2025", "✅ Windows Server 2022", diff --git a/WindowsServerDocs/failover-clustering/cluster-aware-updating-faq.yml b/WindowsServerDocs/failover-clustering/cluster-aware-updating-faq.yml index 6c45c3bdc1..a075cdf576 100644 --- a/WindowsServerDocs/failover-clustering/cluster-aware-updating-faq.yml +++ b/WindowsServerDocs/failover-clustering/cluster-aware-updating-faq.yml @@ -1,6 +1,5 @@ ### YamlMime:FAQ metadata: - ms.assetid: 6416d125-bcaf-433d-971a-2f0283bca2c2 title: Cluster-Aware Updating - Frequently Asked Questions ms.topic: faq author: dknappettmsft diff --git a/WindowsServerDocs/failover-clustering/configure-live-migration-smb-bandwidth.md b/WindowsServerDocs/failover-clustering/configure-live-migration-smb-bandwidth.md new file mode 100644 index 0000000000..5def93f4a3 --- /dev/null +++ b/WindowsServerDocs/failover-clustering/configure-live-migration-smb-bandwidth.md @@ -0,0 +1,265 @@ +--- +title: Control Live Migration SMB Bandwidth Control Cluster-wide in Windows Server and Azure Local +description: Learn how to configure cluster-wide SMB bandwidth limits for Live Migration in Windows Server and Azure Local to optimize network performance and reliability. +#customer intent: As a Hyper-V administrator, I want to calculate the SMB bandwidth limit factor so that I can allocate network resources effectively. +author: robinharwood +ms.author: roharwoo +ms.topic: how-to +ms.date: 10/23/2025 +--- + +# Control Live Migration SMB Bandwidth control cluster-wide + +Cluster-wide parameters enable you to reserve network bandwidth for SMB between failover cluster +nodes. With automatic configuration of the SMB bandwidth limits for live migration, administrators +no longer need to analyze and configure these limits on individual cluster nodes. This article +shows you how to configure cluster-wide Live Migration SMB Bandwidth control in Windows Server and +Azure Local. + +When you configure Hyper-V to use SMB for Live Migration, configuring the SMB bandwidth limits +is critical to the reliability and availability of the system. If live migration over SMB consumes +too much bandwidth, storage and cluster network traffic could be delayed or dropped, affecting the +system and hosted services. + +> [!TIP] +> If you're using Azure Local, use Network ATC for all your host networking requirements, including +> SMB Bandwidth management, live migrations, and much more. To learn more about using Network ATC to +> manage SMB bandwidth limits, see +> [Manage Network ATC](../networking/network-atc/manage-network-atc.md). + +## Prerequisites + +Before you can configure SMB bandwidth control for Live Migration, you must have the following +prerequisites. + +- A failover cluster running Windows Server or Azure Local. To learn more about creating a + failover cluster, see [Create a failover cluster](create-failover-cluster.md) for Windows Server + and + [Create an Azure Local cluster](/previous-versions/azure/azure-local/deploy/create-cluster?tabs=use-network-atc-to-deploy-and-manage-networking-recommended). + +- Each cluster node must have the Hyper-V Server role installed and has Live Migration configured. + For more information, see + [Install the Hyper-V role on Windows Server](../virtualization/hyper-v/get-started/Install-the-Hyper-V-role-on-Windows-Server.md) + on how to get started. + +- Each cluster node must have the + [FS-SMBBW](/powershell/module/smbshare/set-smbbandwidthlimit) Windows + Feature installed. + + > [!IMPORTANT] + > After you install the SMB Bandwidth Limit feature on a cluster node, SMB bandwidth is limited to + > the default of 25% of the nodes total bandwidth. + +- Each cluster node must have 2022-09 Cumulative Update for Microsoft server operating system + version 21H2 or later installed. For more information, see +[KB5017381](https://support.microsoft.com/help/5017381) for Windows Server 2022 and +[KB5017382](https://support.microsoft.com/help/5017382) for Azure Stack HCI OS, version 21H2. + +- An account that is a member of the Administrators group, or equivalent. + +## Calculate bandwidth limit + +Before you can configure a bandwidth limit for SMB, you must calculate the total bandwidth to be +reserved for SMB traffic across all physical network adapters used by the cluster. The bandwidth +limit uses a percentage of the total bandwidth available to the cluster, even when Live Migration is +configured to use a specific cluster network. + +The default SMB bandwidth limit factor is 2500 (25%) of the total bandwidth available to the cluster +node. + +You should consider how much bandwidth is available to the cluster and how much bandwidth is needed +for other cluster traffic, and other traffic using the same cluster network enabled for Live +Migration. + +To calculate the bandwidth limit factor, follow the steps. + +1. Sum the connection speed of all network adapters in one of your clusters nodes to calculate the + total bandwidth for a node. + + > [!IMPORTANT] + > Cluster nodes should have the same number of network adapters across all nodes in the cluster. + > The connected network adapters should also be connected at the same speeds as the other nodes + > in the cluster. If the cluster nodes are consistent, the bandwidth limit is calculated + > differently on those nodes. + +1. Determine how much bandwidth you wish to reserve. + +1. Calculate your SMB bandwidth limit factor using the following formula. + + :::image type="content" source="media/configure-live-migration-smb-bandwidth/smb-bandwidth-limit-factor-equation.png" alt-text="Diagram that shows the equation: (SMB bandwidth limit / total bandwidth) * 10000 = SMB bandwidth limit factor." lightbox="media/configure-live-migration-smb-bandwidth/smb-bandwidth-limit-factor-equation.png"::: + +If you already know the percentage of bandwidth you wish to reserve, times this value by 100. + +The following example uses the formula to calculate the bandwidth limit for a cluster with four +nodes. Each node has four 10GB network adapters, with two cluster networks with two adapters each. +Only one cluster network has Live Migration enabled. The two network adapters used for Live +Migration are also used for other cluster traffic and Live Migration shouldn't consume more than +10GB or 50% of the cluster network. + +The bandwidth limit is calculated as a percentage of the total bandwidth available to the cluster. +The total bandwidth is 40GB and the SMB Live Migration reservation needs to be 10GB. Therefore, the +SMB bandwidth limit factor is 2500, or 25%, as shown in the following example. + +:::image type="content" source="media/configure-live-migration-smb-bandwidth/smb-bandwidth-limit-factor-equation-example.png" alt-text="Diagram that shows an example calculation reserving 10 GB of 40 GB total bandwidth, giving a limit factor of 2500 (25%)." lightbox="media/configure-live-migration-smb-bandwidth/smb-bandwidth-limit-factor-equation-example.png"::: + +## Configure Live Migration performance options + +When you use Hyper-V in a cluster, configure the cluster nodes consistently. To use the SMB +bandwidth limit, configure the cluster nodes to use SMB for Live Migration. For more information +about Live Migration performance options, see +[Virtual Machine Live Migration Overview](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831435(v=ws.11)). + +To configure the Live Migration performance options, select the relevant method and follow the +steps. + +#### [GUI](#tab/gui) + +Here's how to set the SMB performance option using the user interface. + +1. Open Hyper-V Manager. + +1. In the left navigation pane, select the cluster node. + +1. In the right pane, select **Hyper-V Settings**. + +1. In the left navigation pane, expand **Live Migrations**, then select **Advanced Features**. + +1. In the right pane, select the **SMB** performance option. + +1. Select **OK** to save the changes. + +Repeat these steps for each cluster node. + +#### [PowerShell](#tab/powershell) + +Here's how to set the SMB performance option using PowerShell. + +1. Sign in to the cluster node. + +1. Open a PowerShell prompt as an administrator. + +1. Get all cluster nodes by running the following command. + + ```powershell + $ClusterNodes = (Get-ClusterNode).name + ``` + +1. Run the following command to set the performance option to SMB. + + ```powershell + Set-VMHost -ComputerName $ClusterNodes -VirtualMachineMigrationPerformanceOption SMB + ``` + +--- + +## Configure Live Migration network selection + +_Optional:_ When configuring SMB bandwidth limits for Live Migration, you might also want to configure +which cluster networks can be used for Live Migration settings. + +The default Live Migration settings set the cluster network used for cluster communications, CSV, +and Storage Spaces Direct at the lowest preference. The default setting keeps Live +Migration network traffic away from the same network the cluster uses to communicate between +nodes. For more information about network prioritization and traffic isolation in a cluster, see the +following articles. + +- [Configuring Network Prioritization on a Failover Cluster](https://techcommunity.microsoft.com/t5/failover-clustering/configuring-network-prioritization-on-a-failover-cluster/ba-p/371683). + +- [Network recommendations for a Hyper-V cluster](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn550728(v=ws.11)#isolate-traffic-on-the-live-migration-network). + +To configure the Live Migration network selection, select the relevant method and follow the steps. + +#### [GUI](#tab/gui) + +Here's how to set the Live Migration network selection using the user interface. + +1. Open Failover Cluster Manager. + +1. In the left navigation pane, expand the cluster. + +1. Right-click **Networks**, then select **Live Migration Settings**. + +1. In the **Live Migration Settings** dialog, select the cluster networks to use for Live + Migration by checking or unchecking the required networks. + +1. Select **OK** to save the changes. + +#### [PowerShell](#tab/powershell) + +Here's how to set the Live Migration network selection using PowerShell. + +1. Sign in to the cluster node. + +1. Open a PowerShell prompt as an administrator. + +1. Get the Virtual Machine cluster resource type and store it in a variable called `$VMResourceType`. + + ```powershell + $VMResourceType = Get-ClusterResourceType -name "Virtual Machine" + ``` + +1. Get the cluster network object for the network you want to exclude from Live Migration and store + it in a variable called `$ExcludedNetwork`. + + ```powershell + $ExcludedNetwork = Get-ClusterNetwork -Name "Cluster Network 1" + ``` + +1. Set the Live Migration network selection using the following command. + + ```powershell + $VMResourceType | Set-ClusterParameter -Name MigrationExcludeNetworks -Value $ExcludedNetwork.Id + ``` + +--- + +## Configure cluster-wide SMB bandwidth limits + +Set the cluster-wide SMB bandwidth limits by using the `SetSMBBandwidthLimit` and +`SetSMBBandwidthLimitFactor` cluster parameters. When you add a new node to the cluster, it automatically uses +the cluster-wide values. + +To apply the cluster-wide SMB bandwidth limits, follow the steps using PowerShell. + +> [!IMPORTANT] +> The cluster-wide bandwidth limits apply only if the cluster nodes run on physical +> hardware. They don't take effect if the nodes run inside of virtual +> machines. + +1. Sign in to one of the cluster nodes. + +1. Open a PowerShell prompt as an administrator. + +1. To check the current values of the `SetSMBBandwidthLimit` and `SetSMBBandwidthLimitFactor` + cluster parameters, use the following command. + + ```powershell + Get-Cluster | FL SetSMBBandwidthLimit,SetSMBBandwidthLimitFactor + ``` + +1. Set the SMB bandwidth limit factor with the following command using the value you calculated in + the [Calculate bandwidth limit](#calculate-bandwidth-limit) section. For example, the following + command sets the SMB bandwidth limit factor to 3000 (30%). + + ```powershell + Get-Cluster | %($_.SMBBandwidthLimitFactor=3000) + ``` + +1. To enable or disable the cluster-wide SMB bandwidth limits, use the following + relevant command. + + ```powershell + # Disabled the SMB bandwidth limit + Get-Cluster | %($_.SMBBandwidthLimit=0) + + # Enable the SMB bandwidth limit (default setting) + Get-Cluster | %($_.SMBBandwidthLimit=1) + ``` + +## Next steps + +Now you've configured cluster-wide Live Migration SMB bandwidth control here are some resources to +learn more. + +- [Network recommendations for a Hyper-V cluster](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn550728(v=ws.11)#isolate-traffic-on-the-live-migration-network). +- [Failover Clustering Microsoft Tech Community](https://techcommunity.microsoft.com/t5/failover-clustering/bg-p/FailoverClustering). diff --git a/WindowsServerDocs/failover-clustering/media/configure-live-migration-smb-bandwidth/smb-bandwidth-limit-factor-equation-example.png b/WindowsServerDocs/failover-clustering/media/configure-live-migration-smb-bandwidth/smb-bandwidth-limit-factor-equation-example.png new file mode 100644 index 0000000000..4c7b053848 Binary files /dev/null and b/WindowsServerDocs/failover-clustering/media/configure-live-migration-smb-bandwidth/smb-bandwidth-limit-factor-equation-example.png differ diff --git a/WindowsServerDocs/failover-clustering/media/configure-live-migration-smb-bandwidth/smb-bandwidth-limit-factor-equation.png b/WindowsServerDocs/failover-clustering/media/configure-live-migration-smb-bandwidth/smb-bandwidth-limit-factor-equation.png new file mode 100644 index 0000000000..ee77a26e77 Binary files /dev/null and b/WindowsServerDocs/failover-clustering/media/configure-live-migration-smb-bandwidth/smb-bandwidth-limit-factor-equation.png differ diff --git a/WindowsServerDocs/failover-clustering/toc.yml b/WindowsServerDocs/failover-clustering/toc.yml index c0e233a2f9..38725b8f8c 100644 --- a/WindowsServerDocs/failover-clustering/toc.yml +++ b/WindowsServerDocs/failover-clustering/toc.yml @@ -58,6 +58,8 @@ href: cluster-operating-system-rolling-upgrade.md - name: Deploy a cluster set href: cluster-set.md + - name: Configure Live Migration SMB bandwidth control + href: configure-live-migration-smb-bandwidth.md - name: Concepts items: - name: Cluster and pool quorum diff --git a/WindowsServerDocs/identity/ad-ds/deploy/dcpromo.md b/WindowsServerDocs/identity/ad-ds/deploy/dcpromo.md index 94d4e999bd..70978fbf97 100644 --- a/WindowsServerDocs/identity/ad-ds/deploy/dcpromo.md +++ b/WindowsServerDocs/identity/ad-ds/deploy/dcpromo.md @@ -1,8 +1,8 @@ --- description: An overview of the syntax and structure of DCPROMO answer files. title: DCPROMO answer file syntax -ms.author: alalve -author: xelu86 +ms.author: daknappe +author: dknappettmsft ms.date: 04/25/2024 ms.topic: reference ms.custom: sfi-ropc-nochange diff --git a/WindowsServerDocs/identity/ad-ds/manage/forest-recovery-guide/ad-forest-recovery-faq.yml b/WindowsServerDocs/identity/ad-ds/manage/forest-recovery-guide/ad-forest-recovery-faq.yml index c82793daa0..1fd0303de4 100644 --- a/WindowsServerDocs/identity/ad-ds/manage/forest-recovery-guide/ad-forest-recovery-faq.yml +++ b/WindowsServerDocs/identity/ad-ds/manage/forest-recovery-guide/ad-forest-recovery-faq.yml @@ -3,8 +3,7 @@ metadata: description: "Learn more about: AD Forest Recovery - FAQ" title: AD Forest Recovery - FAQ ms.author: roharwoo - author: iainfoulds - manager: daveba + author: robinharwood ms.date: 05/12/2025 ms.topic: faq ms.custom: ac9e5a3d-8b1e-41b7-8e02-f64b7acf1359, inhenkel diff --git a/WindowsServerDocs/identity/ad-ds/manage/forest-recovery-guide/includes/ad-forest-recovery-guide-links.md b/WindowsServerDocs/identity/ad-ds/manage/forest-recovery-guide/includes/ad-forest-recovery-guide-links.md index 7b8e5e4d4e..32ccd8f037 100644 --- a/WindowsServerDocs/identity/ad-ds/manage/forest-recovery-guide/includes/ad-forest-recovery-guide-links.md +++ b/WindowsServerDocs/identity/ad-ds/manage/forest-recovery-guide/includes/ad-forest-recovery-guide-links.md @@ -1,11 +1,11 @@ --- title: include file description: include file -author: meaghanlewis +author: robinharwood ms.service: active-directory ms.topic: include ms.date: 07/11/2023 -ms.author: mosagie +ms.author: roharwoo --- - [AD Forest Recovery - Prerequisites](../ad-forest-recovery-prerequisites.md) diff --git a/WindowsServerDocs/identity/ad-fs/deployment/Set-up-Geographic-Redundancy-with-SQL-Server-Replication.md b/WindowsServerDocs/identity/ad-fs/deployment/Set-up-Geographic-Redundancy-with-SQL-Server-Replication.md index c6e3836efd..0fb9ae8e4b 100644 --- a/WindowsServerDocs/identity/ad-fs/deployment/Set-up-Geographic-Redundancy-with-SQL-Server-Replication.md +++ b/WindowsServerDocs/identity/ad-fs/deployment/Set-up-Geographic-Redundancy-with-SQL-Server-Replication.md @@ -3,7 +3,6 @@ title: Setup Geographic Redundancy with SQL Server Replication description: "Learn more about: Setup Geographic Redundancy with SQL Server Replication" ms.date: 02/13/2024 ms.topic: how-to -ms.assetId: 7b9f9a4f-888c-4358-bacd-3237661b1935 ms.custom: sfi-image-nochange --- diff --git a/WindowsServerDocs/identity/ad-fs/overview/AD-FS-FAQ.yml b/WindowsServerDocs/identity/ad-fs/overview/AD-FS-FAQ.yml index 3bda888a03..e25a7f08a4 100644 --- a/WindowsServerDocs/identity/ad-fs/overview/AD-FS-FAQ.yml +++ b/WindowsServerDocs/identity/ad-fs/overview/AD-FS-FAQ.yml @@ -1,11 +1,9 @@ ### YamlMime:FAQ metadata: - ms.assetid: acc9101b-841c-4540-8b3c-62a53869ef7a title: Active Directory Federation Services (AD FS) FAQ description: This article provides answers to frequently asked questions about Active Directory Federation Services (AD FS). author: robinharwood ms.author: billmath - manager: mtillman ms.date: 11/02/2020 ms.topic: faq ms.service: windows-server diff --git a/WindowsServerDocs/identity/laps/laps-concepts-passwords-passphrases.md b/WindowsServerDocs/identity/laps/laps-concepts-passwords-passphrases.md index 911b0cc27a..451477a849 100644 --- a/WindowsServerDocs/identity/laps/laps-concepts-passwords-passphrases.md +++ b/WindowsServerDocs/identity/laps/laps-concepts-passwords-passphrases.md @@ -25,7 +25,7 @@ Windows LAPS supports five different complexity settings that can be used to gen |2|Large letters + small letters|"ABCDEFGHIJKLMNOPQRSTUVWXYZ"

        "abcdefghijklmnopqrstuvwxyz"|"fOiMbhmcVFHzmI"| |3|Large letters + small letters + numbers|"ABCDEFGHIJKLMNOPQRSTUVWXYZ"

        "abcdefghijklmnopqrstuvwxyz"

        "0123456789"|"logqQVGs53R4vY"| |4|Large letters + small letters + numbers + specials|"ABCDEFGHIJKLMNOPQRSTUVWXYZ"

        "abcdefghijklmnopqrstuvwxyz"

        "0123456789"

        ",.-+;!#&@{}[]$/()%"|"P5QWg43.1lA}ra"| -|5|Large letters + small letters + numbers (improved readability)|"ABCDEFGHJKLMNPRSTUVWXYZ"

        "abcdefghijkmnpqrstuvwxyz"

        "23456789"

        "!#%+@:=?*"|"vnJ!!?MTb5=U7Y"| +|5|Large letters + small letters + numbers + specials (improved readability)|"ABCDEFGHJKLMNPRSTUVWXYZ"

        "abcdefghijkmnpqrstuvwxyz"

        "23456789"

        "!#%+@:=?*"|"vnJ!!?MTb5=U7Y"| When a complexity setting with multiple character sets is chosen, Windows LAPS ensures that the resultant password contains at least one character randomly chosen from each character set. @@ -39,7 +39,7 @@ Password complexity setting five is equivalent to password complexity setting fo - Adds the symbols ':', '=', '?', and '*' > [!IMPORTANT] -> The PasswordComplexity setting of '5' is only supported in Windows 11 24H2, Windows Server 2025 and later releases. It is not required to deploy any Windows Server 2025 domain controllers in order to use this new setting. +> The PasswordComplexity setting of '5' is only supported in Windows 11 24H2, Windows Server 2025, and later releases. It isn't required to deploy any Windows Server 2025 domain controllers in order to use this new setting. ## Passphrase word lists @@ -56,7 +56,7 @@ The length of passphrases is controlled using the PassphraseLength policy settin Passphrase word lists were taken from ["Deep Dive: EFF's New Wordlists for Random Passphrases"](https://www.eff.org/deeplinks/2016/07/new-wordlists-random-passphrases) by [Electronic Frontier Foundation](https://www.eff.org/), and are used under a CC-BY-3.0 Attribution license. The specific contents of all Windows LAPS passphrase word lists can be downloaded from [Windows LAPS Passphrase Word Lists](https://go.microsoft.com/fwlink/?linkid=2255471). Microsoft made slight modifications to the original word lists; all changes are detailed in the downloadable lists. > [!IMPORTANT] -> Windows LAPS passphrase support is only supported in Windows 11 24H2, Windows Server 2025 and later releases. It is not required to deploy Windows Server 2025 domain controllers in order to use this new setting. +> Windows LAPS passphrase support is only supported in Windows 11 24H2, Windows Server 2025, and later releases. It isn't required to deploy Windows Server 2025 domain controllers in order to use this new setting. ## Entropy considerations diff --git a/WindowsServerDocs/index.yml b/WindowsServerDocs/index.yml index 5e19a3b909..973044d726 100644 --- a/WindowsServerDocs/index.yml +++ b/WindowsServerDocs/index.yml @@ -8,7 +8,6 @@ metadata: description: Windows Server is the platform for building an infrastructure of connected applications, networks, and web services, from the workgroup to the data center. ms.service: windows-server ms.topic: hub-page - manager: tedhudek ms.author: roharwoo author: robinharwood ms.date: 05/28/2025 diff --git a/WindowsServerDocs/manage/windows-admin-center/use/migrate-vmware-to-hyper-v.md b/WindowsServerDocs/manage/windows-admin-center/use/migrate-vmware-to-hyper-v.md index b9b0de9e1e..7023fc4671 100644 --- a/WindowsServerDocs/manage/windows-admin-center/use/migrate-vmware-to-hyper-v.md +++ b/WindowsServerDocs/manage/windows-admin-center/use/migrate-vmware-to-hyper-v.md @@ -533,9 +533,10 @@ Static IP configuration doesn't migrate successfully for a Windows VM. .\Prepare-MigratedVM.ps1 -StaticIPMigration -Verbose ``` -## What's new +--- -## Update (September 2025) +## What's new +## [Version 1.8.0](https://dev.azure.com/WindowsAdminCenter/Windows%20Admin%20Center%20Feed/_artifacts/feed/wac-public-extensions/NuGet/msft.sme.vm-conversion/overview/1.8.0) (September 2025) ### New Features @@ -599,3 +600,24 @@ Static IP configuration doesn't migrate successfully for a Windows VM. - **Windows VMs** - VMware Tools batch uninstall is supported only for Windows VMs. - **Licensing Note** - Differences in BIOS Serial Number may affect licensing. See [FAQ](#frequently-asked-questions) for details. + +--- + +## [Version 1.8.2](https://dev.azure.com/WindowsAdminCenter/Windows%20Admin%20Center%20Feed/_artifacts/feed/wac-public-extensions/NuGet/msft.sme.vm-conversion/overview/1.8.2) (October 2025) + +### New Features + +- **vCenter Version Display:** + You can now view the vCenter version directly on the **vCenter List** page for easier identification and management. + +- **Migration Reconnection Banner:** + A new banner now appears, prompting users to stay signed in and refresh their session every 2 hours during migration to ensure continuity. + +- **Quick Access to Documentation:** + The **“Open in New Window”** icon on the landing page now links directly to the official guide — + [Migrate VMware Virtual Machines to Hyper-V in Windows Admin Center (Preview)](../use/migrate-vmware-to-hyper-v.md). + +## Other Improvements + +- Enhanced telemetry for improved diagnostics and secure handling of environment information. + diff --git a/WindowsServerDocs/networking/branchcache/BranchCache-Network-Shell-and-Windows-PowerShell-Commands.md b/WindowsServerDocs/networking/branchcache/BranchCache-Network-Shell-and-Windows-PowerShell-Commands.md index 88d3bd8e94..d4ecf96504 100644 --- a/WindowsServerDocs/networking/branchcache/BranchCache-Network-Shell-and-Windows-PowerShell-Commands.md +++ b/WindowsServerDocs/networking/branchcache/BranchCache-Network-Shell-and-Windows-PowerShell-Commands.md @@ -2,8 +2,8 @@ title: BranchCache Network Shell and Windows PowerShell Commands description: This topic provides links to Network Shell and Windows PowerShell command reference resources for BranchCache in Windows Server 2016 ms.topic: reference -author: meaghanlewis -ms.author: mosagie +author: robinharwood +ms.author: roharwoo ms.date: 12/08/2020 --- # BranchCache Network Shell and Windows PowerShell Commands diff --git a/WindowsServerDocs/networking/index.yml b/WindowsServerDocs/networking/index.yml index f0d8d77db0..87f976412e 100644 --- a/WindowsServerDocs/networking/index.yml +++ b/WindowsServerDocs/networking/index.yml @@ -8,11 +8,9 @@ metadata: description: This topic provides an overview of the Software Defined Networking and Network Platform technologies that are available in Windows Server 2016. # Required; article description that is displayed in search results. < 160 chars. ms.subservice: networking ms.topic: landing-page # Required - manager: dougkim author: AnirbanPaul #Required; your GitHub user alias, with correct capitalization. ms.author: anpaul #Required; microsoft alias of author; optional team alias. ms.date: 06/11/2020 #Required; mm/dd/yyyy format. - ms.assetid: daaf6b61-5953-4c2d-b6b8-7c885b552646 ms.localizationpriority: medium ms.service: windows-server diff --git a/WindowsServerDocs/networking/windows-time-service/windows-time-service-tech-ref.md b/WindowsServerDocs/networking/windows-time-service/windows-time-service-tech-ref.md index 1acd6d5087..4120b31d1f 100644 --- a/WindowsServerDocs/networking/windows-time-service/windows-time-service-tech-ref.md +++ b/WindowsServerDocs/networking/windows-time-service/windows-time-service-tech-ref.md @@ -1,8 +1,8 @@ --- title: Windows Time Service Technical Reference description: The W32Time service provides network clock synchronization for computers without the need for extensive configuration. The W32Time service is essential to the successful operation of Kerberos V5 authentication and, therefore, to AD DS-based authentication. -author: xelu86 -ms.author: alalve +author: dknappettmsft +ms.author: daknappe ms.date: 11/04/2021 ms.topic: reference --- diff --git a/WindowsServerDocs/remote/TOC.yml b/WindowsServerDocs/remote/TOC.yml index 6a32440f5a..9dbfb8d0e0 100644 --- a/WindowsServerDocs/remote/TOC.yml +++ b/WindowsServerDocs/remote/TOC.yml @@ -2,226 +2,29 @@ href: index.yml items: - name: MultiPoint Services - href: multipoint-services/MultiPoint-Services.md items: - name: Planning a MultiPoint Services Deployment - href: multipoint-services/Planning-a-MultiPoint-Services-Deployment.md items: - - name: Introducing MultiPoint Services - href: multipoint-services/Introducing-MultiPoint-services.md - - name: Getting started with MultiPoint Services - href: multipoint-services/getting-started-with-MultiPoint-services.md - - name: Common Usage Scenarios - href: multipoint-services/Common-MultiPoint-services-Usage-Scenarios.md - - name: MultiPoint Stations - href: multipoint-services/MultiPoint-services-Stations.md - - name: Selecting Hardware for Your MultiPoint Services System - href: multipoint-services/select-hardware-mps.md - name: Hardware Requirements and Performance Recommendations - href: multipoint-services/hardware-and-performance-recommendations.md - items: - - name: Variables Affecting MultiPoint Services System Performance - href: multipoint-services/Variables-Affecting-MultiPoint-services-System-Performance.md - - name: MultiPoint Services Site Planning - href: multipoint-services/MultiPoint-services-Site-Planning.md - - name: Network Considerations and User Accounts - href: multipoint-services/Network-Considerations-and-User-Accounts.md - - name: Storing Files with MultiPoint Services - href: multipoint-services/Storing-Files-with-MultiPoint-services.md - - name: Protecting the System volume with Disk Protection - href: multipoint-services/Protecting-the-System-volume-with-Disk-Protection.md - - name: MultiPoint Services Virtualization Support - href: multipoint-services/MultiPoint-services-Virtualization-Support.md - - name: Application Considerations - href: multipoint-services/Application-Considerations.md - - name: Predeployment Checklist - href: multipoint-services/Predeployment-Checklist.md - - name: Glossary - href: multipoint-services/Glossary.md - name: Migrate MultiPoint Services - href: multipoint-services/multipoint-services-migrate.md - items: - - name: Prepare to migrate to MultiPoint Services - href: multipoint-services/multipoint-services-migration-preparation.md - - name: Planning worksheet for your migration - href: multipoint-services/multipoint-services-migration-worksheet.md - - name: Migrate to MultiPoint Services - href: multipoint-services/multipoint-services-migration-steps.md - - name: Post-migration tasks - href: multipoint-services/multipoint-services-post-migration-steps.md - name: Deploying MultiPoint Services - href: multipoint-services/Deploying-MultiPoint-Services.md items: - name: Deploy a new MultiPoint Services System - href: multipoint-services/Deploy-a-new-MultiPoint-services-system.md items: - - name: Collect hardware and device drivers needed for the installation - href: multipoint-services/multipoint-hardware-device-drivers.md - - name: Set up the physical computer and primary station - href: multipoint-services/Set-up-the-physical-computer-and-primary-station.md - - name: Install MultiPoint Services - href: multipoint-services/Install-MultiPoint-services.md - - name: Update and install device drivers if needed - href: multipoint-services/Update-and-install-device-drivers-if-needed.md - - name: Set the date, time, and time zone - href: multipoint-services/set-the-date-time.md - - name: Join the MultiPoint Server to a domain (optional) - href: multipoint-services/join-multipoint-services-to-a-domain.md - - name: Install updates - href: multipoint-services/Install-updates.md - name: attach additional stations to your MultiPoint server - href: multipoint-services/multipoint-attach-additional-stations.md - items: - - name: Set up a direct-video-connected station - href: multipoint-services/Set-up-a-direct-video-connected-station-in-MultiPoint-services.md - - name: Set up a USB zero client-connected station - href: multipoint-services/Set-up-a-USB-zero-client-connected-station-in-MultiPoint-services.md - - name: Set up an RDP-over-LAN connected station - href: multipoint-services/Set-up-an-RDP-over-LAN-connected-station-in-MultiPoint-services.md - - name: Manage Client Access Licenses (CAL) with MultiPoint Services - href: multipoint-services/manage-client-access-licenses.md - - name: Install software on your MultiPoint Services System - href: multipoint-services/install-software-on-multipoint.md - name: Optional configuration tasks for a MultiPoint Services deployment - href: multipoint-services/Optional-configuration-tasks-for-a-MultiPoint-services-deployment.md - items: - - name: Set up a split-screen station - href: multipoint-services/Set-up-a-split-screen-station-in-multipoint-services.md - - name: Add printers - href: multipoint-services/add-printers.md - - name: Create Windows 10 Enterprise virtual desktops for stations - href: multipoint-services/Create-Windows-10-Enterprise-virtual-desktops-for-stations.md - name: Prepare your MultiPoint Services System for users - href: multipoint-services/Prepare-your-MultiPoint-services-system-for-users.md - items: - - name: Plan user accounts for your MultiPoint Services environment - href: multipoint-services/Plan-user-accounts-for-your-MultiPoint-services-environment.md - - name: 'Example scenarios: MultiPoint Services user accounts' - href: multipoint-services/multipoint-users-scenario.md - - name: Create local user accounts - href: multipoint-services/create-local-user-accounts.md - - name: Limit users' access to the MultiPoint server - href: multipoint-services/limit-user-access-to-multipoint.md - - name: Configure stations for automatic logon - href: multipoint-services/Configure-stations-for-automatic-logon.md - - name: Allow one account to have multiple sessions - href: multipoint-services/Allow-one-account-to-have-multiple-sessions.md - - name: Enable file sharing in MultiPoint Services - href: multipoint-services/Enable-file-sharing-in-multipoint-services.md - name: System administration in MultiPoint Services - href: multipoint-services/System-administration-in-multipoint-services.md - items: - - name: Configure Disk Protection in MultiPoint Services - href: multipoint-services/Configure-Disk-Protection-in-MultiPoint-services.md - - name: Install Server Backup on your MultiPoint system - href: multipoint-services/install-server-backup-on-multiPoint.md - - name: Configure group policies for a domain deployment - href: multipoint-services/Configure-group-policies-for-a-domain-deployment.md - name: Managing MultiPoint Services - href: multipoint-services/Managing-MultiPoint-Services.md items: - name: Managing Your MultiPoint Services System - href: multipoint-services/Managing-Your-MultiPoint-Services-System.md - items: - - name: Privacy and Security Considerations - href: multipoint-services/Privacy-and-Security-Considerations.md - name: Manage Station Hardware - href: multipoint-services/Manage-Station-Hardware.md - items: - - name: View Hardware Status - href: multipoint-services/View-Hardware-Status.md - - name: Work with USB Devices - href: multipoint-services/Work-with-USB-Devices.md - - name: Work with Video Devices - href: multipoint-services/Work-with-Video-Devices.md - - name: Set Up a Station - href: multipoint-services/Set-Up-a-Station.md - name: Manage System Tasks Using MultiPoint Manager - href: multipoint-services/Manage-System-Tasks-Using-MultiPoint-Manager.md - items: - - name: Edit Server Settings - href: multipoint-services/edit-Server-Settings.md - - name: Restart or Shut Down MultiPoint Systems - href: multipoint-services/Restart-or-Shut-Down-MultiPoint-Systems.md - - name: Switch Between modes - href: multipoint-services/Switch-Between-modes.md - - name: Enable or Disable Disk Protection - href: multipoint-services/Enable-or-Disable-Disk-Protection.md - - name: Manage Client Access Licenses - href: multipoint-services/Manage-Client-Access-Licenses.md - - name: Remap All Stations - href: multipoint-services/remap-All-Stations.md - - name: Save Connection Settings to File - href: multipoint-services/Save-Connection-Settings-to-File.md - - name: Add or remove computers - href: multipoint-services/add-or-remove-computers.md - name: Manage User Stations - href: multipoint-services/Manage-User-Stations.md - items: - - name: View User Connection Status - href: multipoint-services/View-User-Connection-Status.md - - name: Log off or Disconnect User Sessions - href: multipoint-services/Log-off-or-Disconnect-User-Sessions.md - - name: Suspend and Leave User Session active - href: multipoint-services/Suspend-and-Leave-User-Session-active.md - - name: End a User Session - href: multipoint-services/End-a-User-Session.md - - name: Set up a Station for Automatic Logon - href: multipoint-services/Set-up-a-Station-for-Automatic-Logon.md - - name: Split a User Station - href: multipoint-services/Split-a-User-Station.md - name: Manage User Accounts - href: multipoint-services/Manage-User-Accounts.md - items: - - name: User Account Considerations - href: multipoint-services/User-Account-Considerations.md - - name: Create an Administrative User Account - href: multipoint-services/create-an-Administrative-User-Account.md - - name: Create a Standard User Account - href: multipoint-services/create-a-Standard-User-Account.md - - name: Create a MultiPoint Dashboard User Account - href: multipoint-services/create-a-MultiPoint-Dashboard-User-Account.md - - name: Update or delete a User Account - href: multipoint-services/Update-or-delete-a-User-Account.md - - name: Manage Virtual Desktops - href: multipoint-services/Manage-Virtual-Desktops.md - name: Manage User Files - href: multipoint-services/Manage-User-Files.md - items: - - name: Keep Files Private - href: multipoint-services/Keep-Files-Private.md - - name: Share Files - href: multipoint-services/Share-Files.md - - name: Save and Share Files on a USB Flash Drive - href: multipoint-services/Save-and-Share-Files-on-a-USB-Flash-Drive.md - name: Manage User Desktops Using MultiPoint Dashboard - href: multipoint-services/Manage-User-Desktops-Using-MultiPoint-Dashboard.md - items: - - name: Block or Unblock a Station - href: multipoint-services/Block-or-Unblock-a-Station.md - - name: Limit Web Access - href: multipoint-services/Limit-Web-Access.md - - name: Block or Unblock USB Storage - href: multipoint-services/Block-or-Unblock-USB-Storage.md - - name: Project a Station to Other Stations - href: multipoint-services/Project-a-Station-to-Other-Stations.md - - name: Launch or Close Applications on a Station - href: multipoint-services/Launch-or-Close-Applications-on-a-Station.md - - name: Use IM - href: multipoint-services/Use-IM.md - - name: Take Control of a User Session - href: multipoint-services/Take-Control-of-a-User-Session.md - - name: View Options for Session Thumbnails in MultiPoint Dashboard - href: multipoint-services/View-Options-for-Session-Thumbnails-in-MultiPoint-Dashboard.md - - name: Log Off User Sessions - href: multipoint-services/Log-Off-User-Sessions.md - name: Manage MultiPoint Systems Using MultiPoint Dashboard - href: multipoint-services/Manage-MultiPoint-Systems-Using-MultiPoint-Dashboard.md - items: - - name: Restart or Shut Down - href: multipoint-services/Restart-or-Shut-Down.md - - name: Remap selected MultiPoint Systems - href: multipoint-services/remap-selected-MultiPoint-Systems.md - name: Remote Desktop Services href: remote-desktop-services/index.yml - name: Remote Access @@ -477,9 +280,9 @@ - name: Web Application Proxy href: remote-access/web-application-proxy/web-app-proxy-windows-server.md - name: Troubleshooting - items: + items: - name: DirectAccess Known Issues - href: remote-access/directaccess/directAccess-Known-Issues.md + href: remote-access/directaccess/directAccess-Known-Issues.md - name: Reference items: - name: Remote Access PowerShell Command reference diff --git a/WindowsServerDocs/remote/multipoint-services/Add-or-Remove-Computers.md b/WindowsServerDocs/remote/multipoint-services/Add-or-Remove-Computers.md deleted file mode 100644 index a941ec6723..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Add-or-Remove-Computers.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Add or Remove Computers -description: Learn how to add and remove computers from MultiPoint Services. -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 07/13/2017 ---- -# Add or Remove Computers -You can add other computers or remove computers from your MultiPoint Services system by using MultiPoint Manager. Adding other PCs to MultiPoint Manager allows the MultiPoint Dashboard to orchestrate any user's session when logged on to that PC in the same way it can for MultiPoint stations. - -## To add or remove servers in MultiPoint - -1. Open MultiPoint Manager in station mode, and then click the **Home** tab. - -2. Under *computer name* **Tasks**, click **Add or remove MultiPoint servers**. The **Add or Remove MultiPoint Servers** screen launches and begins discovering other servers on the local network subnet that can be managed with MultiPoint Manager. - -3. Do one of the following: - - - **To add a server:** In the **Available** list, click a server that you want to manage with MultiPoint Manager, and then click **Add**. If the administrator user account and password for the server are different than the account you are currently logged on with, you are prompted to provide the account information. - - - **To add a server that is not on the subnet:** In the **MultiPoint Server name** field, type the name of the server you want to add, and then click **Manually Add**. - - - **To remove a server:** In the **Managed** list, click a server that you want to remove from management, and then click **Remove**. - -## To add or remove other computers - -1. Open MultiPoint Manager in station mode, and then click the **Home** tab. - -2. Under **Home Tasks**, click **Add or remove personal computers**. The **Add or Remove Personal Computers** screen launches and begins discovering other computers on the local network subnet that can be managed with MultiPoint Services. - -3. Do one of the following: - - - **To add a computer:** In the **Available** list, click a computer that you want to manage with MultiPoint Services, and then click **Add**. When adding a computer, you are prompted to provide the account information. - - - **To add a computer that is not on the subnet:** In the **Personal Computer name** field, type the name of the computer you want to add, and then click **Manually Add**. - - - **To remove a computer:** In the **Managed** list, click a computer that you want to remove from management, and then click **Remove**. - -## See Also -[Manage System Tasks Using MultiPoint Manager](Manage-System-Tasks-Using-MultiPoint-Manager.md) -[Edit Server Settings](Edit-Server-Settings.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Add-printers.md b/WindowsServerDocs/remote/multipoint-services/Add-printers.md deleted file mode 100644 index 424766075b..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Add-printers.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Add printers -description: Add a printer for your MultiPoint Services users. -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Add printers -Use the procedures in this topic to make a local printer available to all users on a MultiPoint Services system. - -> [!NOTE] -> If you are using domain accounts with MultiPoint Services, users can use any network printer from their stations. - -1. Connect the printer to the Multipoint server. - -2. Configure the printer as a shared printer: - - 1. Log on to the MultiPoint Server computer as an administrator. - - 2. From the **Start** screen, open **Control Panel**. - - 3. In Control Panel, click **Hardware**, and then click **Devices and Printers**. - - 4. Under **Printers and Faxes**, right-click the printer, and then click **Printer Properties**. - - 5. Click the **Sharing** tab. - - 6. Click **Share this printer**, specify a share name for the printer, and then click **OK**. - -Users logged on to any station that is connected to the Multipoint Services computer will be able to see and use the printer. diff --git a/WindowsServerDocs/remote/multipoint-services/Allow-one-account-to-have-multiple-sessions.md b/WindowsServerDocs/remote/multipoint-services/Allow-one-account-to-have-multiple-sessions.md deleted file mode 100644 index 6eee1af144..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Allow-one-account-to-have-multiple-sessions.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Allow one account to have multiple sessions -description: Let a user access multiple systems at the same time. -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Allow one account to have multiple sessions -To enable a group of users use a shared account on multiple stations at the same time, configure the MultiPoint server to allow one account to be logged on to multiple stations simultaneously. By default, if a user logs on to a second station with a shared user account, the user account is logged off the first station. - -1. From the **Start** screen, open **MultiPoint Manager**. - -2. Click the **Home** tab. - -3. In the **Computer** column, click the name of the MultiPoint Server computer, and then, in the right pane, click **Edit server settings**. - -4. Select the **Allow one account to have multiple sessions** check box, and then click **OK**. - diff --git a/WindowsServerDocs/remote/multipoint-services/Application-Considerations.md b/WindowsServerDocs/remote/multipoint-services/Application-Considerations.md deleted file mode 100644 index 1e73814f4b..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Application-Considerations.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Application Considerations -description: Compatiblity information for apps on MultiPoint Services -ms.topic: best-practice -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Application Considerations - -## Application compatibility - -Any application that you want to run on a MultiPoint Services system must fulfill the following requirements: - -- It should install and run on Windows Server 2016 -- It needs to be session aware so each user can run an instance of the app in a MultiPoint system. - -If the application does specify this requirement we recommend to try installing the application and use it in a remote desktop session. - -## Addressing application compatibility problems -MultiPoint Services offers the option to associate stations with full instances of Windows 10 Enterprise editions running virtually on the same host computer. For critical applications that will not run multiple instances for multiple users, or will not install on a 64-bit operating system, this can be a solution. Deploying desktops this way requires using the Virtual Desktops tab in MultiPoint Manager to: - -- Enable virtual desktops -- Create a desktop template -- Customize the template with the problem application -- Associate stations with the customized template - -Each station starts from the same template, so any changes are erased each time the computer starts. - ->[!NOTE] ->It is important to verify the licensing requirements for the applications you want to run on a MultiPoint. Although you are installing one copy applications might require per-user licensing. - diff --git a/WindowsServerDocs/remote/multipoint-services/Block-or-Unblock-USB-Storage.md b/WindowsServerDocs/remote/multipoint-services/Block-or-Unblock-USB-Storage.md deleted file mode 100644 index e19e082d50..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Block-or-Unblock-USB-Storage.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Block or Unblock USB Storage -description: Learn how to prevent users from using USB storage on MultiPoint stations -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Block or Unblock USB Storage -You can prevent users for using USB storage on their user stations. - -## To block USB storage for selected stations -1. In the MultiPoint Dashboard, click the station you want to block. -2. Click **Block** > **Block Selected desktop(s)**. - -## To block USB Storage for all stations -Open MultiPoint Dashboard, and then from the drop-down menu, select **Block Storage on all stations**. - -## To unblock USB Storage for selected stations -Open MultiPoint Dashboard, choose the thumbnail image of the station you want to unblock, and then click **Unblock**. diff --git a/WindowsServerDocs/remote/multipoint-services/Block-or-Unblock-a-Station.md b/WindowsServerDocs/remote/multipoint-services/Block-or-Unblock-a-Station.md deleted file mode 100644 index 93d7e69971..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Block-or-Unblock-a-Station.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Block or Unblock a Station -description: Learn how to stop a user or group from accessing a MultiPoint Services system. -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Block or Unblock a Station -You can block a user or users from the MultiPoint Services system if you need to get their attention. While users are blocked, their sessions remains active in the MultiPoint Services system's computer memory until the stations are unblocked. You can customize a message to be displayed for a blocked user. - -## To block a station - -1. In the MultiPoint Dashboard, select the thumbnail image of the station you want to block. - -2. On the Blocking tab, click **Block**, and then click **Block Selected Desktop(s)** or **Block All Desktops**. - -## To unblock a station - -1. In the MultiPoint Dashboard, select the thumbnail image of the station you want to unblock. - -2. On the Blocking tab, click **Unblock**, and then click **Unblock Selected Desktop(s)**. - -## Create a message to display for blocked users -Before you block a user, you may want to create a message to display on the user's monitor when they are blocked. For example, "Please turn your attention to the speaker." **Station blocked** is the default text if you do not create your own message. - -1. Click the **Block** drop-down menu, and then click **Set Message**. The **Set Message for Blocked Users** page opens. - -2. Type the message you want to display on the blocked station(s), and then click **OK**. diff --git a/WindowsServerDocs/remote/multipoint-services/Common-MultiPoint-services-Usage-Scenarios.md b/WindowsServerDocs/remote/multipoint-services/Common-MultiPoint-services-Usage-Scenarios.md deleted file mode 100644 index b151630747..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Common-MultiPoint-services-Usage-Scenarios.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Common MultiPoint Services Usage Scenarios -description: Learn about common uses for MultiPoint Services -ms.topic: example-scenario -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Common Usage Scenarios -MultiPoint Services delivers individual user desktops with the most important elements of the Windows 10 desktop experience. It also offers a simple management tool, the MultiPoint Manager, that system administrators can use for discovery and control of multiple MultiPoint servers and clients. Additionally, MultiPoint Services includes the MultiPoint Dashboard for real-time visibility. Examples of what you can do with MultiPoint Services include the following: - -- Give each user a personal computing experience and private folders without needing a separate computer for each person. -- Manage multiple MultiPoint systems in a computer lab, classroom, training center, or small business environment. -- Install a program once, and access it from any station. -- Monitor each user's desktop activity. -- Block screens with a customizable message to get the group's attention. -- Restrict the group to only accessing one or more websites. -- Project your screen to the other screens to demonstrate a particular task. -- Communicate privately with a standard user who is asking for help. -- Take control of a user's session to demonstrate a task. -- Do all of the above-listed items for a user who is using a traditional PC, laptop, or any other mobile device. diff --git a/WindowsServerDocs/remote/multipoint-services/Configure-Disk-Protection-in-MultiPoint-services.md b/WindowsServerDocs/remote/multipoint-services/Configure-Disk-Protection-in-MultiPoint-services.md deleted file mode 100644 index f7edc08abd..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Configure-Disk-Protection-in-MultiPoint-services.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Configure Disk Protection in MultiPoint Services -description: Learn how to set up disk protection for MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Configure Disk Protection -You can use Disk Protection in Multipoint Services to protect your system volume from unintended updates, to schedule Windows Updates to be retained while Disk Protection is active, to temporarily disable Disk Protection, and to uninstall Disk Protection. - -By enabling Disk Protection in MultiPoint Services, you can protect the system volume (the drive where Windows is installed, usually C:) from unwanted changes. When Disk Protection is enabled, changes made to the system volume are stored in a temporary location so that simply restarting the computer discards them and automatically returns the system to the previous known-good state. - -The administrator can easily install software or make configuration changes by temporarily disabling disk protection. In order to keep the system current with Windows Updates and anti-malware definitions, Disk Protection schedules a maintenance window to download and install updates. The administrator can also provide a custom script to run during the maintenance window to accommodate any maintenance needs beyond Windows Update. - -## Enable Disk Protection -Before you enable Disk Protection, make sure all applications and drivers are installed and up to date, and move your user profiles to a volume that will not be protected. If you need to make manual updates after you enable Disk Protection, you can temporarily disable Disk Protection. However, it's easiest to get the system into an ideal state before Disk Protection is turned on. - - -1. Log on to the server running MultiPoint Services as an administrator. - -2. Before you enable Disk Protection: - - - Ensure the MultiPoint Services system is in exactly the state in which you want it to remain. For example, ensure that installed software, system settings, and updates are correct. - - - Move user profiles to a volume that is not protected, or set up a shared file location off the system volume as described in [Enable file sharing in MultiPoint Services](Enable-file-sharing-in-MultiPoint-services.md). - -3. From the **Start** screen, open **MultiPoint Manager**. - -4. Click the **Home** tab, click **Enable disk protection**, and then click **OK**. - -When Disk Protection is enabled for the first time, the system is prepared by installing a driver and creating a cache file on the system volume. The cache file will temporarily store any changes made to the system volume while Disk Protection is active. Because system updates are stored in the cache file, they do not alter the protected contents of the volume outside the cache file. Each time the system starts, the cache file is reset, which discards any changes stored there since the previous system start. Thus, the system always starts in the same state as when Disk Protection was enabled. - -Windows needs to update a few system files – including the system pagefile, crash dump location, and event logs. Those files are not discarded when Disk Protection is enabled. To accomplish this, a new volume named DpReserved is created when Disk Protection is enabled for the first time, and those files are moved to that volume. The DpReserved partition is not protected, so writes to those files persist through restarts, even when Disk Protection is enabled. - -## Schedule software updates -If Windows is configured to automatically install Windows Updates, Disk Protection allows these updates at the configured time, and does not discard the updates. For example, if Windows updates are scheduled for 3:00 a.m., Disk Protection checks for updates each day at 3:00 a.m. If any updates are found, MultiPoint Services temporarily disables Disk Protection, applies the updates, and then re-enables Disk Protection. - -1. In MultiPoint Manager, display the **Home** tab, and then click **Schedule software updates**. - -2. In the Schedule Software Updates dialog box, click **Update at**, and select a time for updates - for example, **3:00 AM**. - -3. Select the **Run Windows Update** check box. - -4. If your organization runs its own update script, select the **Run the following program** check box, and specify the location of your organization's update script. - -5. Select a maximum time to allow updates to run. - -6. Under **When finished**, choose whether to have the system return to its previous power state or shut down after applying updates. - -7. Click **OK**. - -## Temporarily disable Disk Protection -If an administrator needs to install software, change system settings, or perform other maintenance tasks that involve system updates, they can temporarily disable Disk Protection. After the changes are made, re-enable Disk Protection. During system restarts, the system will retain its state when Disk Protection was enabled. - -1. In MultiPoint Manager, click the **Home** tab. - -2. On the Home tab, click **Disable disk protection**, and then click **OK**. - -> [!NOTE] -> Remember to re-enable Disk Protection after maintenance is complete. The system will not be protected again until the administrator explicitly re-enables Disk Protection. - -## Uninstall Disk Protection -Uninstalling Disk Protection removes the driver and the cache file, so you should only do this if you want to stop using Disk Protection long-term. If you simply want to perform maintenance or stop protection temporarily, use the Disable disk protection task instead. - -You can uninstall Disk Protection whether it is enabled or disabled. - -1. In MultiPoint Manager, click the **Home** tab. - -2. On the Home tab, and click **Uninstall disk protection**, and then click **OK**. - - After you click **OK**, the computer restarts. The uninstallation process requires several restarts, during which the driver and cache file are removed. The DpReserved partition remains, and the pagefile, crash dump location, and event log files remain configured to use the DpReserved partition. diff --git a/WindowsServerDocs/remote/multipoint-services/Configure-group-policies-for-a-domain-deployment.md b/WindowsServerDocs/remote/multipoint-services/Configure-group-policies-for-a-domain-deployment.md deleted file mode 100644 index 498cbb84a5..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Configure-group-policies-for-a-domain-deployment.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Configure group policies for a domain deployment -description: Learn how to set up group policies in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Configure group policies for a domain deployment -To ensure that your domain deployment of MultiPoint Services works properly, apply the following group policy settings to the WMSshell user account on a MultiPoint Services system. - -> [!IMPORTANT] -> Some group policy settings can prevent required configuration settings from being applied to MultiPoint Services. Be sure that you understand and define your group policy settings so that they work correctly on MultiPoint Services. For example, a Group Policy setting that prevents Autologon could present problems with MultiPoint Services logon behavior. - -## Update group policies for the WMSshell user account -The WMSshell user account is a system account which MultiPoint services uses to sign-in into the console, where the actual stations are created. This account is not meant to be managed by MultiPoint Manager. - -> [!NOTE] -> To find out how to update group policies, see [Local Group Policy Editor](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn265982(v=ws.11)). - -**POLICY:** User Configuration > Administrative templates > Control Panel > **Personalization** - -Assign the following values: - -|Setting|Values| -|-----------|----------| -|Enable screen saver|Disabled| -|Screen saver timeout|Disabled

        Seconds: xxx| -|Password protect the screen saver|Disabled| - -**POLICY:** Computer Configuration >Windows Settings >Security Settings >Local Policies >User Rights Assignment > **Allow log on locally** - -|Setting|Values| -|-----------|----------| -|Allow log on locally|Ensure that the list of accounts includes the WMSshell account.

        **Note:** By default, the WMSshell account is a member of the Users group. If the Users group is in the list, and WMSshell is a member of the Users group, you do not need to add the WMSshell account to the list.| - -> [!IMPORTANT] -> When you set any group policies, make sure that the policies do not interfere with automatic updates and error Windows error reporting on the MultiPoint server. These are set by the **Install updates automatically** and **Automatic Windows Error Reporting** settings that were selected during Windows MultiPoint Server installation, configured in MultiPoint Manager using **Edit server settings**, or configured in scheduled updates for Disk Protection. - -## Update the Registry -For a domain deployment of MultiPoint Services, you should update the following registry subkeys. - -> [!IMPORTANT] -> Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer. - -#### To update Registry subkeys for a domain deployment of MultiPoint Services - -1. Open Registry editor. (At a command prompt, type **regedit.exe**, and press ENTER.) - -2. In the left pane, locate and then select the following registry subkey: - - HKEY_USERS\\Software\Policies\Microsoft\Windows\Control Panel\Desktop - - where '\' is the security identifier (SID) for the WMSshell account. To identify the user, run the following PowerShell command. - - `Get-ADObject -Filter "objectSid -eq ''"` - -3. In the list on the right, update the following subkeys. - - |Subkey|Value name|Value data| - |----------|--------------|--------------| - |ScreenSaveActive|REG_SZ|0 (zero)| - |ScreenSaveTimeout|REG_SZ|120| - |ScreenSaverIsSecure|REG_SZ|0 (zero)| - - To update a Registry subkey: - - 1. With the Registry key selected in the left pane, right-click the subkey in the right pane, and then click **Modify**. - - 2. In the Edit String dialog box, type a new value in **Value data**, and then click **OK**. - -4. After you finish updating Registry subkeys, restart the computer to activate the changes. diff --git a/WindowsServerDocs/remote/multipoint-services/Configure-stations-for-automatic-logon.md b/WindowsServerDocs/remote/multipoint-services/Configure-stations-for-automatic-logon.md deleted file mode 100644 index a55b6a5bbc..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Configure-stations-for-automatic-logon.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Configure stations for automatic logon -description: Set up automatic logon for MultiPoint stations -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Configure stations for automatic logon -If you want your stations to be available to anyone – and your users do not need private folders to store their personal data or personalized desktops – you can configure the stations for automatic logon. Auto-logon automatically logs on a user account that has been specified in the auto-logon settings when the MultiPoint Services starts. - -1. From the **Start** screen, open **MultiPoint Manager**. - -2. Click the **Stations** tab, and then click the name of the station that you want to configure for auto-logon. - -3. In the right pane, click **Configure auto-logon**. - - The Configure Auto-Logon page opens. - -4. Select the **Auto-logon using the following information** check box, and then enter the user account and password to use for auto-logon. Click **OK**. - - > [!NOTE] - > The user account that you use for auto-logon must have a password. - -> [!NOTE] -> To temporarily log on to a station that is set up for automatic logon with a different user account, hover over the top right corner of the screen to display a vertical menu, click the Settings charm, click the Power icon, and then hold the SHIFT key and click **Disconnect**. Hold down the SHIFT key until a logon prompt appears. diff --git a/WindowsServerDocs/remote/multipoint-services/Create-Windows-10-Enterprise-virtual-desktops-for-stations.md b/WindowsServerDocs/remote/multipoint-services/Create-Windows-10-Enterprise-virtual-desktops-for-stations.md deleted file mode 100644 index cae8b4c827..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Create-Windows-10-Enterprise-virtual-desktops-for-stations.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -title: Create Windows 10 Enterprise virtual desktops for stations -description: Learn how to create Windows Server 2016 desktops for station -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Create Windows 10 Enterprise virtual desktops for stations -This optional configuration in MultiPoint Services is primarily intended for situations where an essential application requires its own instance of a client operating system for each user. Examples include applications that cannot be installed on Windows Server and applications that will not run multiple instances on the same host computer. - -> [!NOTE] -> These Virtual Desktops, also known as VDI, are much more resource intensive than the default MultiPoint Services desktop sessions, so we recommend that you use default MultiPoint Services sessions when possible. - -## Prerequisites -To prepare to create station virtual desktops, ensure that your MultiPoint Services system meets the following requirements: - -| Hardware | Requirements | -|--|--| -| CPU (multimedia) | 1 core or thread per virtual machine | -| Solid State Drive (SSD) | Capacity >= 20GB per station + 40GB for the MultiPoint Services host operating system

        Random Read/Write IOPS >= 3K per station | -| RAM | 2GB per station + 2GB for the Windows MultiPoint Server host operating system | -| Graphics | DX11 | -| BIOS | BIOS CPU setting configured to enable virtualization – Second Level Address Translation (SLAT) | - -- **Stations** - Set up the stations for your MultiPoint Services system. For more information, see [Attach additional stations to MultiPoint Services](./multipoint-attach-additional-stations.md). - -- **Domain** - In a domain environment, the Windows MultiPoint Server computer has been added to the domain, and a domain user has been added to the local Administrators group on the MultiPoint Services host operating system. - -## Procedures -Use the following procedures to: - -- [Create a template for virtual desktops](#create-a-template-for-virtual-desktops) - -- [Create virtual desktops from the template](#create-virtual-machine-desktops-from-the-template) - -- [Copy an existing virtual desktop template](#copy-an-existing-virtual-desktop-template) - -### Create a template for virtual desktops -Before you can create a template for your virtual desktops, you must enable the Virtual Desktop feature in MultiPoint Server. - -##### To enable the Virtual Desktop feature - -1. Log on to the MultiPoint Server host operating system with a local administrator account or, in a domain, with a domain account that is a member of the local Administrators group. - -2. From the **Start** screen, open MultiPoint Manager. - -3. Click the **Virtual Desktops** tab, click **Enable virtual desktops**, and then click **OK**, and wait for the system to restart. - -Your next step is to create a Virtual Desktop template. You are literally creating a virtual hard disk (VHD) file that you can use as a template to create station virtual desktops for MultiPoint Manager. You can either use the physical installation media for Windows or an .ISO image file to as source for the template. You can also use a .VHD of the Windows installation. Note that to use a physical installation disc, you must insert the disc before you start the wizard. - -##### To create a Virtual Desktop template - -1. Log on to the MultiPoint Server host operating system with a local Administrator account or, in domain, a domain account that is a member of the local Administrators group. - -2. From the **Start** screen, open MultiPoint Manager. - -3. Click the **Virtual Desktops** tab. - -4. Copy a Windows 10 Enterprise .iso file to the local SSD. - -5. On the Virtual Desktops tab, click **Create virtual desktop template.** - -6. In **Prefix**, enter a prefix to use to identify the template and the virtual desktops created with the template. The default prefix is the host computer name. - - The prefix is used to name the template and the virtual desktop stations. The template will be <*prefix*>-t. The virtual desktop stations will be named <*prefix*>-*n*, where *n* is the station identifier. - -7. Enter a username and password to use for the local Administrator account for the template. In a domain, enter the credentials for a domain account that will be added to the local Administrators group. This account can be used to log on to the template and all virtual desktop stations created from the template. - -8. Click **OK**, and wait for template creation to complete. - -9. The new template will be listed on the **Virtual Desktops** tab. The template will be turned off. - -Your next step is to configure the template with the software and setting that you want on the virtual desktops. You must do this before you create any virtual desktops from the template. - -##### To customize a virtual desktop template - -1. Log on to the MultiPoint server host operating system with a local administrator account or, in a domain, with a domain account in the local Administrators group. - -2. From the **Start** screen, open MultiPoint Manager. - -3. Click the **Virtual Desktops** tab. - -4. Select the template that you want to customize, click **Customize template**, and then click **OK**. - - > [!NOTE] - > Only the templates that have not been used to create virtual desktop stations are available. If you want to update a template that is already in use, you must make a copy of the template by using the **Import template** task, described later, in [Copy an existing virtual desktop template](#copy-an-existing-virtual-desktop-template). - - The template opens in a Hyper-V **VM Connect** window, and auto-logon is performed using the built-in Administrator account. - -5. At this point you can install applications and software updates, change settings, and update the administrator profile. All changes made to the template's built-in administrator profile will be copied to the default user profile in the virtual desktop stations that are created from the template. - - If you are connecting your stations over a domain, we recommend that you create a local user account and add it to the local Administrators group during customization. - - > [!NOTE] - > If the system restarts while a template is being customized, auto-logon using the built-in Administrator account might fail after the system restarts. To get around this problem, manually log on using the local Administrator account that you created, change the password of the built-in Administrator account, log off, and then log back on using the built-in Administrator account and the new password. (You will need to delete the profile that was created when you logged on using the local Administrator account.) - -6. After you finish configuring your system, double-click the **CompleteCustomization** shortcut on the administrator's desktop to run Sysprep and then shut down the template. During customization, the Sysprep tool removes all unique system information to prepare the Windows installation to be imaged. - -### Create virtual machine desktops from the template -With your virtual desktop template configured the way you want your desktops to be, you are ready to begin creating virtual desktops. A virtual desktop will be created for each station that is attached to the MultiPoint Server computer. The next time a user logs on to a station, they will see the virtual desktop instead of the session-based desktop that was displayed before. - -> [!NOTE] -> This procedure only works when MultiPoint Server is in *station mode*. If the system is in *console mode*, you can switch to station mode from MultiPoint Manager. If you are using default MultiPoint settings, you can also start station mode by restarting the computer. By default, the MultiPoint Server computer always starts in station mode - -##### To create virtual desktops for your stations - -1. Log on to the Windows MultiPoint server from a remote station (for example, from a Windows computer by using Remote Desktop Connection) using a local administrator account or, in a domain, a domain account in the local Administrators group. - - > [!NOTE] - > Alternatively, you can log on to the server using a local station. However, when you create a station virtual desktop, you will have to log off the station that you used to create the virtual desktop in order to connect the other station to the new virtual desktop. - -2. From the **Start** screen, open MultiPoint Manager. - -3. If the computer is in console mode, switch to station mode: - - 1. On the **Home** tab, click **Switch to station mode**. - - 2. When the computer restarts, log on as Administrator. - -4. Click the **Virtual Desktops** tab. - -5. Select the virtual desktop template that you want to use with the stations, click **Create virtual desktop stations**, and then click **OK**. - -When the task completes, each local station will connect to a virtual machine-based virtual desktop. - -> [!NOTE] -> If a user account is logged on to any of the local stations, you will need to log out of the session to get the station to connect to one of the newly created station virtual desktops. - -### Copy an existing virtual desktop template -Use the following procedure to create a copy of an existing virtual desktop template that you can customize and use. This can be useful in the following situations: - -- To copy a master template from a network share onto a MultiPoint Server host computer so that virtual desktop stations can be created from the master template. - -- To create a copy of a template that is currently in use so that you can make additional customizations. - -##### To import a virtual desktop template - -1. Log on to the MultiPoint server as an administrator. - -2. From the **Start** screen, open MultiPoint Manager. - -3. Click the **Virtual Desktops** tab. - -4. Click **Import virtual desktop template**, and use **Browse** to select the .vhd file (template) that you want to import. When you import a template, a copy is made of the original .vhd. By default, MultiPoint Services stores .vhd files in the C:\\Users\\Public\\Documents\\Hyper\-V\\Virtual hard disks\\ folder. - -5. Enter a prefix for the new template, and then click **OK**. - -6. If you are making further customizations to a local template, you might change the prefix name by incrementing a version number at the end of the prefix. Or, if you are importing a master template, you might want to add the version of the master template to the end of the default prefix name. - -7. When the task completes, you can customize the template or use it as it is to create stations. diff --git a/WindowsServerDocs/remote/multipoint-services/Create-a-MultiPoint-Dashboard-User-Account.md b/WindowsServerDocs/remote/multipoint-services/Create-a-MultiPoint-Dashboard-User-Account.md deleted file mode 100644 index 59e07feb54..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Create-a-MultiPoint-Dashboard-User-Account.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Create a MultiPoint Dashboard User Account -description: Create an account to use with the dashboard -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Create a MultiPoint Dashboard User Account -Create MultiPoint Dashboard user accounts for those users who will regularly access stations, but who will not manage your MultiPoint Services system. Users with MultiPoint Dashboard user accounts can run most applications and save files, but cannot run MultiPoint Manager. To see who has MultiPoint Dashboard user access, in MultiPoint Manager, click the **Users** tab. MultiPoint Dashboard user accounts are displayed in the **Account Type** column as **MultiPoint Dashboard User**. - -If your MultiPoint Services users will store private documents in Windows, each user should log on to the MultiPoint Services system using a unique user name and password. - -> [!NOTE] -> For more information about issues you, as an *administrative user*, should consider as you create and manage user accounts, see the [User Account Considerations](User-Account-Considerations.md) topic. - -#### To create a MultiPoint Dashboard user account - -1. In MultiPoint Manager, click the **Users** tab. - -2. Under **User Tasks**, click **Add user account**. The **Add User Account** wizard opens. - -3. In the **User account** field, type a logon name for the user. - -4. In the **Full name** field, type the name of the user in whatever format you prefer, such as given name, full name, or a nickname. - -5. In the **Create password** field, type a password for the user. This password should only be known to you and the user, and you should store this information in a secure location. The password can only be changed by an administrative user. - -6. In the **Confirm password** field, retype the password, and then click **Next**. - -7. On the level of access page, select **MultiPoint Dashboard user**, and then click **Next**. - -8. Click **Finish**. - -## See Also -[User Account Considerations](User-Account-Considerations.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Create-a-Standard-User-Account.md b/WindowsServerDocs/remote/multipoint-services/Create-a-Standard-User-Account.md deleted file mode 100644 index 76d6ae517c..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Create-a-Standard-User-Account.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Create a Standard User Account -description: Create a basic user account for MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 09/14/2020 ---- -# Create a Standard User Account -Create *standard user accounts* for those users who will regularly access stations, but who will not manage your MultiPoint Services system. Users with standard user accounts can run most applications and save files, but cannot run MultiPoint Manager. To see who has standard user access, in MultiPoint Manager, click the **Users** tab. Standard user accounts are displayed in the **Account Type** column as **Standard**. - -If your MultiPoint Services users will store private documents in Windows, each user should log on to the MultiPoint Services system using a unique user name and password. - -> [!NOTE] -> For more information about issues you, as an *administrative user*, should consider as you create and manage user accounts, see the [User Account Considerations](User-Account-Considerations.md) topic. - -#### To create a standard user account - -1. In MultiPoint Manager, click the **Users** tab. - -2. Under **User Tasks**, click **Add user account**. The **Add User Account** wizard opens. - -3. In the **User account** field, type a logon name for the user. Typically, the logon user name is the first and last name written together without spaces, or the first initial and last name written together without a space. - -4. In the **Full name** field, type the name of the user in whatever format you prefer, such as given name, full name, or a nickname. - -5. In the **Create password** field, type a password for the user. This password should only be known to you and the user, and you should store this information in a secure location. The password can only be changed by an administrative user. - -6. In the **Confirm password** field, retype the password, and then click **Next**. - -7. On the level of access page, select **Standard user**, and then click **Next**. - -8. Click **Finish**. diff --git a/WindowsServerDocs/remote/multipoint-services/Create-an-Administrative-User-Account.md b/WindowsServerDocs/remote/multipoint-services/Create-an-Administrative-User-Account.md deleted file mode 100644 index bc0d550ccc..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Create-an-Administrative-User-Account.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Create an Administrative User Account -description: Create an account with administrative privileges in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Create an Administrative User Account -Create *administrative user accounts* for those individuals who will manage your MultiPoint Services system. To see who has administrative access, in MultiPoint Manager, click the **Users** tab. Administrative user accounts are displayed in the **Account Type** column as **Administrator**. *Administrative users* have access to all MultiPoint Manager tasks that change desktop and system settings, such as: - -- Creating accounts - -- Adding and removing programs - -- Managing *desktops* and hardware - -- Ending other user *sessions* - -Administrative users can perform tasks that affect all other users of the MultiPoint Services system, such as install software or change security settings. For this reason, administrative users should have unique user names and passwords that are known only to them. - -For more information about issues that you, as an administrative user, should consider as you create and manage user accounts, see the [User Account Considerations](User-Account-Considerations.md) topic. - -> [!NOTE] -> You might want to create a *standard user account* for you to use when you perform tasks on the MultiPoint Services system that are not related to MultiPoint Services system management. You would then only log on to your administrative user account when you need to perform system management tasks. - -#### To create an administrative user account - -1. In MultiPoint Manager, click the **Users** tab. - -2. Under **User Tasks**, click **Add user account**. The **Add User Account** wizard opens. - -3. In the **User account** field, type a logon name for the user. Typically, the logon user name is the first and last name written together without spaces, or the first initial and last name written together without a space. - -4. In the **Full Name** field, type the name of the user in whatever format you prefer, such as given name, full name, or a nickname. - -5. In the **Password** field, type a password for the user. The password should only be known to you and the user, and you should store this information in a secure location. The password can only be changed by an administrative user. - -6. In the **Confirm password** field, retype the password, and then click **Next**. - -7. On the level of access page, select **Administrative user**, and then click **Next**. - -8. MultiPoint Services will check all of the information and display a message when the account has been set up. When you see the text, **A new user account was successfully created**, click **Finish**. diff --git a/WindowsServerDocs/remote/multipoint-services/Create-local-user-accounts.md b/WindowsServerDocs/remote/multipoint-services/Create-local-user-accounts.md deleted file mode 100644 index 1f268a9b0b..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Create-local-user-accounts.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Create local user accounts -description: Learn abou thte three kinds of user accounts in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Create local user accounts -Three levels of local user accounts can be created in using the MultiPoint Manager: Standard User accounts; MultiPoint Dashboard users, who have limited administrative rights; and full Administrative User accounts. - -Use the following procedure to create a local user account on a MultiPoint server. If your environment includes multiple MultiPoint servers, and you want the user to be able to log on to any station on any server, you need to create a local user account on each of your servers. That setup has some limitations. In a domain environment, you can also let users use their domain accounts. For an overview of your options, see [Plan user accounts for your Windows MultiPoint Services environment](Plan-user-accounts-for-your-MultiPoint-services-environment.md). - -1. Log on to the server as an administrator, and open MultiPoint Manager. - -2. Click the **Users** tab, and then click **Add user account**. - - The Add User Account Wizard opens. - -3. Enter an account name and password for the new user account, and then click **Next**. - -4. Select the type of user account that you want to create: - - - **Standard User** - Can log on to a station and perform user tasks, but has no access to MultiPoint Manager or the MultiPoint Server Dashboard, and cannot shut down the system. - - - **MultiPoint Dashboard User** - Has limited administrative rights. A Dashboard user can open the Dashboard and perform tasks such as logging users off the system or shutting down the MultiPoint Server computer, but the user does not have access to MultiPoint Manager. - - - **Administrative User** Has full administrative rights in MultiPoint Server. For example, an administrative user can run MultiPoint Manager, add and delete users, modify system settings, and update drivers. - -5. Click **Next**, and then click **Finish** to create the user account. diff --git a/WindowsServerDocs/remote/multipoint-services/Deploy-a-new-MultiPoint-Services-system.md b/WindowsServerDocs/remote/multipoint-services/Deploy-a-new-MultiPoint-Services-system.md deleted file mode 100644 index 1acd6aab02..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Deploy-a-new-MultiPoint-Services-system.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Deploy a new Windows MultiPoint Services system -description: Steps required to deploy a new MultiPoint Services environment -ms.date: 07/22/2016 -ms.topic: install-set-up-deploy -author: dknappettmsft -ms.author: daknappe ---- -# Deploy a new Windows MultiPoint Services system -The topics in this section explain how to set up your MultiPoint Services System. You will install and configure a MultiPoint server; set up your stations; install drivers, updates, and software; optionally join a domain; activate MultiPoint Server; and add client access licenses (CALs) for each station. - -> [!IMPORTANT] -> If you have not yet planned your MultiPoint Services deployment, see [Planning a Windows MultiPoint Services Deployment](Planning-a-MultiPoint-Services-Deployment.md). - -## In this section -For the initial installation, we recommend that you perform the tasks in the order in which they are presented. - -1. [Collect hardware and device drivers needed for the installation](./multipoint-hardware-device-drivers.md) - -2. [Set up the physical computer and primary station](Set-up-the-physical-computer-and-primary-station.md) - -3. [Install Windows Server 2016 and enroll MultiPoint Services](Install-MultiPoint-services.md) - -4. [Update and install device drivers if needed](Update-and-install-device-drivers-if-needed.md) - -5. [Set the date, time, and time zone](./set-the-date-time.md) - -6. [Join the MultiPoint Services system to a domain - optional](./join-multipoint-services-to-a-domain.md) - -7. [Install updates](Install-updates.md) - -8. [Attach additional stations to your MultiPoint Services computer](./multipoint-attach-additional-stations.md) - -9. [Activate Windows Server 2016 and add Remote Desktop Services CALs](./manage-client-access-licenses.md) - -10. [Install software on your MultiPoint Services system](./install-software-on-multipoint.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Deploying-MultiPoint-Services.md b/WindowsServerDocs/remote/multipoint-services/Deploying-MultiPoint-Services.md deleted file mode 100644 index ef27d15b86..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Deploying-MultiPoint-Services.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Deploying MultiPoint Services -description: Overview of the MultiPoint Services deployment process -ms.date: 07/22/2016 -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe ---- - -# Deploying MultiPoint Services - -This guide describes how to deploy a server running MultiPoint Services and set up MultiPoint stations, install and configure your system, set up user accounts, and perform some basic administration tasks, such as turning on Disk Protection and setting up backups, before you start using your system. - -> [!NOTE] -> For additional support, see the MultiPoint Services Help, which can be opened by clicking the Help icon or F1 on any MultiPoint Manager or MultiPoint Dashboard screen. - -The deployment information is organized in the following way. At a minimum, you need to complete the tasks for deploying your system and preparing your environment for users. Other tasks might or might not apply to your environment. -- [Deploy a new MultiPoint Services System](Deploy-a-new-MultiPoint-services-system.md) - - Set up your MultiPoint Services computer and stations. Install and configure MultiPoint Services; set up your stations; install drivers, updates, and software; optionally join a domain; add client licenses (CALs) for each station. - -- [Optional configuration tasks for a MultiPoint Services deployment](Optional-configuration-tasks-for-a-MultiPoint-services-deployment.md) - - Perform optional configuration tasks. Set up a split-screen station; add printers; enable access over a wireless LAN; create virtual desktops for stations with the Windows 10, Windows 8, or Windows 7 operating system; change the display language for the system or for individual users. - -- [Prepare your MultiPoint Services system for users](Prepare-your-MultiPoint-services-system-for-users.md) - - Plan and create user accounts; restrict users' access to the server; for open access, configure stations for automatic logon; allow multiple sessions for shared user accounts; implement file sharing for users. - -- [System administration in MultiPoint Services](System-administration-in-MultiPoint-services.md) - - Perform some basic server administration tasks before you start using the server. Turn on Disk Protection; install Server Backup; to save power, configure sleep settings; configure group policies and the Registry for a domain deployment. - -## Additional References - -- [MultiPoint Services](MultiPoint-Services.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Edit-Server-Settings.md b/WindowsServerDocs/remote/multipoint-services/Edit-Server-Settings.md deleted file mode 100644 index a029529693..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Edit-Server-Settings.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Edit Server Settings -description: Learn about MultiPoint Services settings -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/07/2020 ---- -# Edit Server Settings -When you installed MultiPoint Services, you configured settings for your system, including opting in to certain programs. This topic describes the settings you can set for your MultiPoint Services system, and explains how to edit the settings. - -## About MultiPoint Services settings -The following table describes the different settings that you can change for your MultiPoint Services system. - -|MultiPoint Services setting|Description| -|-----------------------------------------------------------------------------------------|---------------| -|Allow one account to have multiple sessions|Allows a single user account to be simultaneously logged on to multiple stations. This can be useful in cases such as a classroom where every student is using a shared, single account. Using this setting, any changes to the account resources, such as document folders or the desktop, are available to all users who are logged on using the same account.| -|Allow this computer to be managed remotely|Allows the computer that is running MultiPoint Services to be managed by other MultiPoint systems on your network. If this option is selected, and the managing computer is on the same subnet, this computer appears in the list of available servers to be managed. If this option is selected, and the managing computer is on a different subnet, the managing computer can still manage this computer, but you must specify the IP address of the computer.| -|Allow monitoring of this computer's desktops|Allows you to control whether desktops can be monitored on the MultiPoint Services system. If this setting is off (not selected), desktops of stations (both local and remote) that are connected to the computer that is running MultiPoint Services will not display in the Home tab of MultiPoint Manager (including on a different computer if the computer is being remotely managed).| -|Always start in console mode|Enables the RemoteFX technology, which is designed to allow faster and more efficient Remote Desktop sessions by offloading processing to the CPU and GPU. If you are connecting to MultiPoint Services using a RemoteFX-capable client, you may be able to achieve better performance using this option. The benefits depend on the capabilities of your server and network. For example, this depends in part on whether the time spent doing additional processing to compress the data stream is less than the time that is saved by transmitting less data.| -|Do not show privacy notification at first user logon|When a user logs on to a MultiPoint station for the first time, a notification displays to advise the user that their station activities may be monitored.| -|Assign a unique IP to each station|Assigns a unique IP address to each station. By default, MultiPoint Services has one IP address, which is shared with all sessions that are running on the system. This configuration, however, can cause some application compatibility problems. For example, if an application requires a unique IP address, it may not run properly on MultiPoint Services. Selecting this option, also known as IP virtualization, can resolve this problem.

        IP virtualization is also useful for monitoring active sessions on MultiPoint Services. Some monitoring tools report usage according to the IP address. To enable session monitoring, you can use IP virtualization to assign a unique IP address to each session. Note that if you select this option, each new session receives a unique IP address. Any existing sessions continue to use the shared IP address until they are logged off and logged back on.| -|Allow IM between MultiPoint Dashboard and a user session on this computer|Enables chat between MultiPoint Manager and user session on this computer. For more information see [Use IM](Use-IM.md).| -|Allow orchestration of administrator and MultiPoint Dashboard user sessions|When enabled, allows administrators to use the MultiPoint Dashboard for session orchestration. These sessions display as thumbnails.| -|Allow stations to use GPU hardware rendering|Controls whether stations can use the system's graphics processing unit (GPU).| - -## Editing the computer settings - -1. Open MultiPoint Manager in [station mode](Switch-Between-Modes.md), and then click the **Home** tab. - -2. In the **Computer** column, click the computer name, and then, under the *computer name* **Tasks**, click **Edit computer settings**. - -3. Select or clear the items you want to change, and then click **OK**. - -## See Also -[Manage System Tasks Using MultiPoint Manager](Manage-System-Tasks-Using-MultiPoint-Manager.md) - diff --git a/WindowsServerDocs/remote/multipoint-services/Enable-file-sharing-in-multipoint-services.md b/WindowsServerDocs/remote/multipoint-services/Enable-file-sharing-in-multipoint-services.md deleted file mode 100644 index a35bdfaece..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Enable-file-sharing-in-multipoint-services.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Enable file sharing -description: Learn about file sharing in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: best-practice -author: dknappettmsft -ms.author: daknappe ---- -# Enable file sharing in MultiPoint Services -You can allow users on your MultiPoint stations to share files in two ways: - -- **If you have a file server on the network,** it is recommended that you create a shared folder on the file server. - -- **If you have a small network of 2-3 MultiPoint servers, with no dedicated file server,** one of the MultiPoint servers can act as the file server for all the remaining computers running MultiPoint services. Create a shared folder on that server, and then create local user accounts for all users on that server. The shared folder can be on the original internal drive, or you can attach additional internal or external drives to the computer. - diff --git a/WindowsServerDocs/remote/multipoint-services/Enable-or-Disable-Disk-Protection.md b/WindowsServerDocs/remote/multipoint-services/Enable-or-Disable-Disk-Protection.md deleted file mode 100644 index 5eed1dbf93..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Enable-or-Disable-Disk-Protection.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Enable or Disable Disk Protection -description: Learn how to use disk protection with MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/07/2020 ---- -# Enable or Disable Disk Protection -The Disk Protection feature allows you to reset your MultiPoint Services system to a specified state each time you restart the system. Using Disk Protection, users can temporarily make changes to the MultiPoint Services system, and then those changes are discarded when the server is restarted. Examples of changes that will be discarded when the server is restarted include personalizing a user's profile, saving files, changing settings, or installing applications. - -## Enable Disk Protection - -1. In MultiPoint Manager, click the **Home** tab, and then, under *computer name***Tasks**, click **Enable Disk Protection**. - -2. Review the information, and then click **OK**. - -After the system restarts, any changes made to the system, including new applications that are installed, will be discarded on each subsequent restart. - -## Disable Disk Protection - -1. In MultiPoint Manager, click the **Home** tab, and then, under *computer name***Tasks**, click **Disable Disk Protection**. - -2. Review the information, and then click **OK**. - -After the system restarts, any changes made to the system, including applications that are installed on the server, are permanent and will not be discarded the next time the system is restarted. - diff --git a/WindowsServerDocs/remote/multipoint-services/End-a-User-Session.md b/WindowsServerDocs/remote/multipoint-services/End-a-User-Session.md deleted file mode 100644 index 3184ca3c2f..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/End-a-User-Session.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: End a User Session -description: Learn when and how to manually end a user's session in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/07/2020 ---- -# End a User Session -You should end a user's session when you have to log the user off from the MultiPoint Services system to return the desktop to its default settings. The user receives a warning that the connection is about to end. You should end a user's connection when you want to: - -- Restart the MultiPoint Services system computer - -- Shut down the MultiPoint Services system computer - -- Switch modes - -- Log off a user who forgot to log off - -To end user sessions: - -1. Open MultiPoint Manager in station mode, and then click the **Stations** tab. - -2. Do one of the following: - - - To end a single user session, in the **User** column, select the session you want to end, and then, under **Tasks**, click **Log off**. - - - To end all user sessions, under **Stations Tasks**, click **Log off all stations**. - -## See Also -[Manage User Desktops](manage-user-desktops-using-multipoint-dashboard.md) -[Log off or Disconnect User Sessions](Log-off-or-Disconnect-User-Sessions.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Getting-Started-with-MultiPoint-Services.md b/WindowsServerDocs/remote/multipoint-services/Getting-Started-with-MultiPoint-Services.md deleted file mode 100644 index 889e201144..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Getting-Started-with-MultiPoint-Services.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Getting Started with MultiPoint Services -description: Introduces MultiPoint Services and gets you started using it. -ms.topic: get-started -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Getting Started with MultiPoint Services -Your MultiPoint Services system allows many users to use multiple stations that are physically connected by using station hubs to only one computer. Each station typically consists of a station hub, mouse, keyboard, and video monitor. Each user at a MultiPoint Services station experiences a unique Windows computing session that you can manage using MultiPoint Manager. - -The components of a MultiPoint Services system include the following: - -- MultiPoint Services system software, which supports multiple monitors, keyboards, mouse devices, and other devices on the computer. - -- The MultiPoint Manager application, which lets you monitor and take actions on MultiPoint Services stations. - -- Maintenance and management tools. - -- The MultiPoint Dashboard application, which lets you complete daily tasks, such as communicating with other users. - -Information about how to manage MultiPoint Services stations with MultiPoint Manager and MultiPoint Dashboard is provided in this Help file. - -## Overview of MultiPoint Manager -MultiPoint Manager provides four tabs to use when you are managing the MultiPoint Services stations. Each tab, and the tasks that you can perform on them, is described in more detail in each Help topic. - -The tabs are as follows: - -- **Home tab:** Switch modes to perform administrative tasks, add or remove MultiPoint servers, restart or shut down the computer, enable disk protection, add client access licenses, remap stations, and get help or support. For more information, see the [Manage System Tasks Using MultiPoint Manager](Manage-System-Tasks-Using-MultiPoint-Manager.md) topic. - -- **Stations tab:** View users' *desktop* status and *end* or *suspend* user sessions. For more information, see the [Manage User Stations](Manage-User-Stations.md) topic. - -- **Users tab:** Create and manage *standard user accounts* and *administrative user accounts*. For more information, see the [Manage User Accounts](Manage-User-Accounts.md) topic. - -- **Virtual Desktops tab:** Enable virtual desktop roles. For more information, see the [Manage Virtual Desktops](Manage-Virtual-Desktops.md) topic. - -## MultiPoint Server management and maintenance -After your MultiPoint Services system is set up, you can use MultiPoint Manager to manage MultiPoint Services. - -Types of actions you can perform using MultiPoint Manager include the following: - -- **Adding user accounts:** Use MultiPoint Manager to create standard and administrative user accounts. - -- **Editing server settings:** You can configure your MultiPoint Services system to start in console mode, allow an account to have multiple sessions, assign a unique IP address to each station, and other tasks. - -- **Switching to console mode:** You can change the MultiPoint Services system to console mode in order to install new software on your MultiPoint Services system. You can specify that all users can run the software, or that only you can use the software, depending on the installation and licensing options of the software. - -- **Troubleshooting:** If you experience problems with MultiPoint Services, check the [Troubleshooting](Troubleshooting.md) section to find topics that can help you fix the problem. - -## Overview of MultiPoint Dashboard -MultiPoint Dashboard features a ribbon experience where you can choose between two tabs to access common daily tasks. - -The tabs are as follows: - -- **Home tab:** Block or unblock stations, set web limiting options, project desktops to other desktops, launch or close applications, communicate via instant messaging, assist other users through remote desktop control, adjust desktop thumbnail views, and enable or disable instant messaging and application auto-launch. For more information, see the [Manage User Desktops Using MultiPoint Dashboard](Manage-User-Desktops-Using-MultiPoint-Dashboard.md) topic. - -- **Systems tab:** Restart, shut down, or remap either all or selected systems. For more information, see the [Manage MultiPoint Systems Using MultiPoint Dashboard](Manage-MultiPoint-Systems-Using-MultiPoint-Dashboard.md) topic. - -## Daily use of your MultiPoint Server system -As you begin to use MultiPoint Services daily, there is information about how to use MultiPoint Services that you might want to share with the users on your MultiPoint Services system. This information includes the following: - -**Sharing content and keeping content private:** - -- A user can save a file or document to a private folder that can be viewed only by that user. - -- Users can also save documents to a public folder that is accessible to all users on the MultiPoint Services system. - -- It is important for MultiPoint Services users to know that administrative users have access to all files and documents on the system, even if they are stored privately in a user's personal folder. - -For more information about how to save and manage private and public content, see the [Manage User Files](Manage-User-Files.md) topic. - -**Information about a user's MultiPoint Services session:** - -- Each user has a user name and password, and a unique desktop *session* on the MultiPoint Services system. - -- A *standard user* is not an *administrative user* on the MultiPoint Services system. Standard users cannot install some types of software, but can save files and change desktop settings, except for the screen resolution. Any desktop changes the user makes are present when the user logs on again. - -- Users can disconnect from one station and log back on to their session on a different station without losing their work. For more information, see the [Suspend and Leave User Session Active](Suspend-and-Leave-User-Session-Active.md) topic. - -- A standard user's session (or all user sessions) can be disconnected or logged off by the administrative user through MultiPoint Manager. For more information, see the [Manage User Desktops](manage-user-desktops-using-multipoint-dashboard.md) topic. - -- If a user forgets a password, you can reset the password from the **Users** tab, which uses standard Windows user account management functionality. For more information, see the [Update or Delete a User Account](Update-or-Delete-a-User-Account.md) topic. - -## See Also -[Managing Your MultiPoint Server System](managing-your-multipoint-services-system.md) -[Important Information about Software License Compliance](./multipoint-software-license-compliance.md) -[Manage System Tasks Using MultiPoint Manager](Manage-System-Tasks-Using-MultiPoint-Manager.md) -[Manage User Files](Manage-User-Files.md) -[Manage User Desktops](manage-user-desktops-using-multipoint-dashboard.md) -[Suspend and Leave User Session Active](Suspend-and-Leave-User-Session-Active.md) -[View User Connection Status](View-User-Connection-Status.md) -[Manage Station Hardware](Manage-Station-Hardware.md) -[Set Up a Station](Set-Up-a-Station.md) -[Manage User Accounts](Manage-User-Accounts.md) -[Update or Delete a User Account](Update-or-Delete-a-User-Account.md) -[Manage User Desktops Using MultiPoint Dashboard](Manage-User-Desktops-Using-MultiPoint-Dashboard.md) -[Manage MultiPoint Systems Using MultiPoint Dashboard](Manage-MultiPoint-Systems-Using-MultiPoint-Dashboard.md) -[Troubleshooting](Troubleshooting.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Glossary.md b/WindowsServerDocs/remote/multipoint-services/Glossary.md deleted file mode 100644 index 574f3d5459..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Glossary.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Glossary -description: Defines words, terms, and concepts in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: glossary -author: dknappettmsft -ms.author: daknappe ---- -# Glossary -**associate a station** -To specify which monitor is used with which station and peripheral devices, such as a keyboard and mouse. For direct video connected stations, this is done by pressing a specified key on the station's keyboard when prompted to do so. For USB zero client connected stations, this typically happens automatically. - -**bus-powered hub** -A hub that draws all of its power from the computer's USB interface. Bus-powered hubs do not need separate power connections. However, many devices do not work with this type of hub because they require more power than this type of hub provides. - -**console mode** -One of the two modes MultiPoint services can start. When the system is in console mode, no stations are available for use. Instead, all of the monitors are treated as a single extended desktop for the console session of the computer system. Console mode is typically used to install, update, or configure software, which cannot be done when the computer is in station mode. See also: *station mode*. - -**direct-video-connected station** -A MultiPoint station that consists of a monitor that is directly connected to a video output on the server, and at a minimum, it includes a keyboard and mouse that are connected to the server through a USB hub. - -**domain user account** -A user account that is hosted on a domain computer. Domain user accounts can be accessed from any computer that is connected to the domain, and they are not tied to any particular computer. - -**downstream hub** -A hub that is connected to a station hub to add more available ports for station devices. A downstream hub must not have a keyboard attached to it. - -**externally powered hub** -Also known as a self-powered hub, this hub takes its power from an external power supply unit; therefore, it can provide full power (up to 500 mA) to every port. Many hubs can operate as bus-powered or externally-powered hubs. - -**HID consumer control device** -A Human Interface Device (HID) is a computer device that interacts directly with humans. It may take input from or deliver output to humans. Examples are keyboard, mouse, trackball, touchpad, pointing stick, graphics table, joystick, fingerprint scanner, gamepad, webcam, headset, and driving simulator devices. A HID consumer control device is a particular class of HID devices that includes audio volume controls and multimedia and browser control keys. - -**intermediate hub** -A hub that is between a *root hub* on the server and a station hub. Intermediate hubs are typically used to increase the number of available ports for stations hubs or to extend the distance of the stations from the computer. - -**local user account** -A user account on a specific computer. A local user account is available only on the computer where the account is defined. - -**multifunction hub** -See *USB zero client*. - -**MultiPoint Services system** -A collection of hardware and software that consists of one computer that has Windows Server 2016 installed with the MultiPoint Services role enabled and at least one MultiPoint station. For more information about system layout options, see [MultiPoint Services Site Planning](MultiPoint-services-Site-Planning.md) - -**partition** -A section of space on a physical disk that functions as if it is a separate disk. - -**primary station** -The station that is the first to start up when MultiPoint Services is started. The primary station can be used by an administrator to access startup menus and settings. When it is not being used by the administrator, it can be used as a normal station (it does not have to be reserved exclusively for administration). The primary station's monitor must always be connected directly to a video output on the computer that is running MultiPoint Services. See also: station. - -**RDP-over-LAN-connected station** -A station that is a thin client, traditional desktop, or laptop computer that connects to MultiPoint services by using Remote Desktop Protocol (RDP) through the local area network (LAN). - -**root hub** -A USB hub that is built-in to the host controller on a computer's motherboard. - -**split screen** -A station where a single monitor can be used to display two independent user desktops. Two sets of hubs, keyboards, and mice are associated with a single monitor. One set is associated with the left side of the monitor, and the other set is associated with the right side of the monitor. - -**standard station** -In contrast to the *primary station*, which can be used by an administrator to access startup menus, standard stations will not display startup menus, and they can only be used after MultiPoint Services has completed the startup process. See also: station. - -*station* -User endpoint for connecting to the computer running MultiPoint Services. Three station types are supported: direct-video-connected, USB-zero-client-connected, and RDP-over-LAN-connected stations. For more information about stations, see [MultiPoint Stations](MultiPoint-services-Stations.md). - -**station hub** -A USB hub that has been associated with a monitor to create a MultiPoint station. It connects peripheral USB devices to MultiPoint Services. See also: *USB zero client* and *USB hub*. - -**station mode** -One of the two modes MultiPoint services can start. Typically, the MultiPoint Services system is in station mode. When in station mode, the MultiPoint Services stations behave as if each station is a separate computer that is running the Windows operating system, and multiple users can use the system at the same time. See also: *console mode*. - -**USB hub** -A generic multiport USB expansion hub that complies with the universal serial bus (USB) 2.0 or later specifications. Such hubs typically have several USB ports, which allows multiple USB devices to be connected to a single USB port on the computer. USB hubs are typically separate devices that can be *externally powered* or *bus-powered*. Some other devices, such as some keyboards and video monitors, may incorporate a USB hub into their design. See also: *USB zero client*. - -**USB over Ethernet zero client** -A USB zero client that connects to the computer through a LAN connection rather than a USB port. This client appears to the server as a USB device even through the data is sent through the Ethernet connection. - -**USB zero client** -An expansion hub that connects to the computer through a USB port and enables the connection of a variety of non-USB devices to the hub. USB zero clients are produced by specific hardware manufacturers, and they require the installation of a device-specific driver. USB zero clients support connecting a video monitor (through VGA, DVI, and so on), and peripherals (through USB, sometimes PS/2, and analog audio). The USB zero client can be *externally powered* or *bus-powered*. See also, *USB hubs*. - -**USB zero client connected station** -A MultiPoint Services station that consists of (as a minimum) a monitor, keyboard, and mouse, which are connected to the server through a USB zero client. - diff --git a/WindowsServerDocs/remote/multipoint-services/Install-MultiPoint-services.md b/WindowsServerDocs/remote/multipoint-services/Install-MultiPoint-services.md deleted file mode 100644 index dcb8751119..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Install-MultiPoint-services.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Install MultiPoint Services -description: Learn how to install and configure MultiPoint Services in Windows Server 2016 -ms.topic: install-set-up-deploy -author: dknappettmsft -ms.author: daknappe -ms.date: 04/01/2023 ---- -# Install MultiPoint Services - - - -Follow these instructions to install MultiPoint Services when you're installing a new server. - -Finish installing Windows Server 2016 and then sign in as Administrator. Use Server Manager to enable MultiPoint Services. Server Manager opens automatically at start-up. On the Dashboard, select **Add roles and features** to enable MultiPoint Services and follow the instructions in the wizard. - -In the section, for the installation type select either: - -- Role-based or feature-based installation, or -- Remote Desktop Services installation - -For standard MultiPoint Services deployments, select the Remote Desktop Services installation. The Remote Desktop Services role allows you to conveniently select the MultiPoint Services role under Deployment type. For the role-based installation, select **MultiPoint Services** from the list of roles. The server will restart after successful installation. - -## Configure your primary station - -1. On the **Create a MultiPoint Server Station** page, type the specified letter from the keyboard for that monitor. The correct key entry associates the keyboard and mouse for that station. -1. Sign in as Administrator. diff --git a/WindowsServerDocs/remote/multipoint-services/Install-updates.md b/WindowsServerDocs/remote/multipoint-services/Install-updates.md deleted file mode 100644 index 04674aa8a2..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Install-updates.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Install updates -description: Learn how to install updates to MultiPoint Services -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Install updates -We recommend that you install updates if available. Installing updates requires an Internet connection. - -1. From the **Start** screen, open **Control Panel**. - -2. In Control Panel, type **updates**, and then click **Check for updates**. - -3. If the Windows Update website lists any updates that are needed on your computer, install the updates. - diff --git a/WindowsServerDocs/remote/multipoint-services/Introducing-MultiPoint-services.md b/WindowsServerDocs/remote/multipoint-services/Introducing-MultiPoint-services.md deleted file mode 100644 index 7dfdd50f29..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Introducing-MultiPoint-services.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Introducing MultiPoint Services -description: Provides an overview of MultiPoint Services, a way to let multiple users share a system -ms.date: 07/22/2016 -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe ---- -# Introducing MultiPoint Services -MultiPoint Services role in Windows Server 2016 allows multiple users, each with their own independent and familiar Windows experience, to simultaneously share one computer.There are several ways users can access their sessions. One way is by remoting into the server using the [remote desktop apps](../remote-desktop-services/clients/remote-desktop-clients.md) with any device. Another way is through physical stations attached to the MultiPoint server: - -- Directly to video ports on the computer - -- Through specialized USB zero clients (also referred to as multifunction USB hubs), as well as through similar USB-over-Ethernet devices. - -- Over the local area network (LAN) - -Each of these methods is described in more detail in [MultiPoint Services Stations](MultiPoint-services-Stations.md) later in this document. - -This document addresses the following factors to consider when you are planning to deploy MultiPoint Services: - -- What type of desktops to use with your MultiPoint Services system: Will you need sessions, virtual machines, or Windows PCs? - -- [Selecting Hardware for Your MultiPoint Services System](./select-hardware-mps.md): What hardware decisions should you make? - -- [Hardware Requirements and Performance Recommendations](./hardware-and-performance-recommendations.md): What hardware is required for MultiPoint Services? - -- [MultiPoint Services Site Planning](MultiPoint-services-Site-Planning.md): Where will the computers that are running MultiPoint Services and their stations be located, and how will they be configured? - -- [Network Considerations and User Accounts](Network-Considerations-and-User-Accounts.md): The networking environment into which the MultiPoint Services system is deployed can affect how user accounts are managed. What is your networking environment? How will user accounts be managed? - -- [Storing Files with MultiPoint Services](Storing-Files-with-MultiPoint-services.md): Where will user files be stored, and how will they be accessed? - -- [Predeployment Checklist](Predeployment-Checklist.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Keep-Files-Private.md b/WindowsServerDocs/remote/multipoint-services/Keep-Files-Private.md deleted file mode 100644 index 3ed403afa8..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Keep-Files-Private.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Keep Files Private -description: Learn how to protect certain files from users within MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Keep Files Private -This topic applies to content, such as documents, that you \(as an *administrative user*\) and *standard users* do not want to share with other users in a MultiPoint Services system. - -For more information about privacy in MultiPoint Services, see [Privacy and Security Considerations](Privacy-and-Security-Considerations.md). - -## To keep content private in Windows Explorer - -To keep your documents and other content private, you should save your work in Windows Explorer in the **Documents** library in the **My Documents** folder. The **My Documents** folder is, by default, a private folder. Note, however, that administrative users have access to private folders in Windows Explorer. - -> [!WARNING] -> While an external storage device, such as a USB flash drive, is connected to a USB port on the host or on a USB hub that is not a station hub, it is viewable by any standard or administrative user logged onto the MultiPoint Services system. If you have privacy or security concerns about the content stored on an external storage device, connect it only to a station hub on the MultiPoint Services system. For information about how to use USB storage devices, see the [Save and Share Files on a USB Flash Drive](Save-and-Share-Files-on-a-USB-Flash-Drive.md) topic. - -## See Also -[Manage User Files](Manage-User-Files.md) -[Save and Share Files on a USB Flash Drive](Save-and-Share-Files-on-a-USB-Flash-Drive.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Launch-or-Close-Applications-on-a-Station.md b/WindowsServerDocs/remote/multipoint-services/Launch-or-Close-Applications-on-a-Station.md deleted file mode 100644 index 89852bbe27..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Launch-or-Close-Applications-on-a-Station.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Launch or Close Applications on a Station -description: Learn how to work with applications in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Launch or Close Applications on a Station -As a MultiPoint Dashboard User, you can open or close an application on a user's desktop, selected desktops, or all desktops. - -## Launch an application on a user station - -1. In MultiPoint Dashboard, click the thumbnail image of the user desktop on which you want to launch the application, and then click the drop–down menu for **Launch** in the ribbon under **Applications**. - -2. Click **Launch an Application on Selected Desktops**. The **Launch Application** page opens. - -3. Click the application you want to open, or in **Enter an application, folder, document, or Internet resource to open**, type the name of the resource you want to open, and then click **OK**. - -## Launch an application on all user stations - -1. In MultiPoint Dashboard, click the drop–down menu for **Launch** (in the ribbon under **Applications**). - -2. Click **Launch an Application on All Desktops**. The **Launch Application** page opens. - -3. Click the application you want to open, or in **Enter an application, folder, document, or Internet resource to open**, type the name of the resource you want to open, and then click **OK**. - -## Close an application on a user station - -1. In MultiPoint Dashboard, click the thumbnail image of the desktop on which you want to close an application. - -2. Click **Close** in the ribbon under **Applications** to open the **Close Application** page. - -3. Select the name of the application, folder, document, or Internet resource you want to close, and then click **Close Application**. - -## See Also -[Manage User Desktops](manage-user-desktops-using-multipoint-dashboard.md) - diff --git a/WindowsServerDocs/remote/multipoint-services/Limit-Web-Access.md b/WindowsServerDocs/remote/multipoint-services/Limit-Web-Access.md deleted file mode 100644 index 6e10de7330..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Limit-Web-Access.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Limit Web Access -description: Learn how to limit user access to the Internet in MultiPoint Services -ms.date: 07/08/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Limit Web Access -In addition to monitoring user activities on individual desktops, you, as an administrative user, can limit user access to specified websites by indicating permissible websites and websites to which you want to block user access. - -## To limit web access on a station - -1. In MultiPoint Dashboard, on the **Web Limiting** tab, click **Configure**. The **Configure Web Limiting** page opens. Sites that the user can access are listed. - -2. Click the thumbnail image of the user station on which you want to limit web access. - -3. Under **Selected Item Tasks**, click **Limit web access on this station**. The **Configure Web Limiting** page opens. Sites that the user can access are listed. - -4. To add an allowed site, type the web address, and then click **Add**. - - > [!NOTE] - > For example, entering "Contoso.com" allows or blocks sites that are relative to www\.contoso.com (for example, www\.newpage.contoso.com). Entering "Contoso" will either allow or limit all Contoso-related sites (including contoso.com, contoso.uk, and so forth). - -5. To remove a web address from the list of allowed sites, click the web address you want to remove access to, and then click **Remove**. - -## To limit web access on all stations - -1. In MultiPoint Dashboard, on the **Web Limiting** tab, click the Start drop\-down menu, and then click **Limit Web Access on All Desktops**. - - The **Configure Web Limiting** page opens. Sites that the user can access are listed. Do one of the following: - -2. To add an allowed site, click **Allow only these sites**, type the allowed web address, and then click **Add**. - - To add a site you do not want users to visit, click **Disallow only these sites**, type the web address you don't want users to visit, and then click **Add**. - - > [!NOTE] - > For example, entering "Contoso.com" allows or blocks sites that are relative to www.contoso.com (for example, www\.newpage.contoso.com). Entering "Contoso" will either allow or limit all Contoso-related sites (including contoso.com, contoso.uk, and so forth). - -3. To remove a web address from the list of allowed or disallowed sites, select the web address, and then click **Remove**. - -## See Also -[Manage User Desktops](manage-user-desktops-using-multipoint-dashboard.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Log-Off-User-Sessions.md b/WindowsServerDocs/remote/multipoint-services/Log-Off-User-Sessions.md deleted file mode 100644 index 36b16359a4..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Log-Off-User-Sessions.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Log Off User Sessions -description: Learn how to log off of MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Log Off User Sessions -Standard users, MultiPoint Dashboard users, and administrative users can log on and log off of their desktop sessions as they would with any Windows session. In addition, administrative users and MultiPoint Dashboard users can end the user sessions on all of the monitored sessions on the MultiPoint Services system. - -1. In MultiPoint Dashboard, click the **Home** tab. - -2. Do one of the following: - - - To log off a single user session or selected sessions, click the thumbnail image of the session you want to end, and then click the top-left drop-down menu. Click **Log Off Users**, and then click **Log Off Selected Users**. You can also see this option by right-clicking the selected thumbnails. - - - To log off all user sessions, click the top-left drop-down menu, click **Log Off Users**, and then click **Log Off All Users**. - -## See Also -[Manage User Desktops](manage-user-desktops-using-multipoint-dashboard.md) -[Log off or Disconnect User Sessions](Log-off-or-Disconnect-User-Sessions.md) -[Suspend and Leave User Session Active](Suspend-and-Leave-User-Session-Active.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Log-off-or-Disconnect-User-Sessions.md b/WindowsServerDocs/remote/multipoint-services/Log-off-or-Disconnect-User-Sessions.md deleted file mode 100644 index 6d3bb6c918..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Log-off-or-Disconnect-User-Sessions.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Log off or Disconnect User Sessions -description: Learn how to manually log off a user -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Log off or Disconnect User Sessions -MultiPoint Services users can log on and log off of their desktop sessions as they would with any Windows session. Users can also disconnect or suspend their session so that the MultiPoint Services station is not being used, but their session remains active in the MultiPoint Services system's computer memory. - -In addition, administrative users can end a user's session if the user has stepped away from their MultiPoint Services session or has forgotten to log off of the system. - -## Logging off or disconnecting a session -The following table describes the different options that you or any user can use to log off, suspend, or end a session. - -|**Action**|**Effect**| -|-|-| -|Click **Start**, click Settings, click the user name (top-right corner), and then click **Sign out**.|The session ends and the station is available for log on by any user.| -|Click **Start**, click **Settings**, click Power, and then click **Disconnect**.|Your session is disconnected and your session is preserved in computer memory. The station becomes available for log on by the same user or a different user.| -|Click **Start**, click Settings, click the user name (top-right corner), and then click **Lock**|The station is locked and your session is preserved in computer memory.| - -## Suspending or ending a user's session -The following table describes the different options that you, as an administrative user, can use to disconnect or end a user's session. - -|**Action**|**Effect**| -|-|-| -|**Suspend:** In MultiPoint Manager, use the **Stations** tab to suspend the user's session. For more information, see the [Suspend and Leave User Session Active](Suspend-and-Leave-User-Session-Active.md) topic.|The user's session ends and is preserved in computer memory. The station becomes available for log on by the same user or a different user. The user can log on to the same station or another station and continue with their work.| -|**End:** In MultiPoint Manager, use the **Stations** tab to end the user's session. You can also end all user sessions on the **Stations** tab. For more information, see the [End a User Session](End-a-User-Session.md) topic.|The user's session ends and the station becomes available for log on by any user. The user's session no longer displays on the **Stations** tab, and it is not in computer memory.| - -## See Also -[Suspend and Leave User Session Active](Suspend-and-Leave-User-Session-Active.md) -[End a User Session](End-a-User-Session.md) -[Manage User Desktops](manage-user-desktops-using-multipoint-dashboard.md) -[Log Off User Sessions](Log-Off-User-Sessions.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Manage-Client-Access-Licenses.md b/WindowsServerDocs/remote/multipoint-services/Manage-Client-Access-Licenses.md deleted file mode 100644 index 3f9ed23429..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Manage-Client-Access-Licenses.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Manage Client Access Licenses -description: Learn how to work with CALs in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Manage Client Access Licenses -Every station that connects to a MultiPoint Services system, including the computer running MultiPoint Services that is used as a station, must have a valid per-user Remote Desktop *client access license (CAL)*. - -If you are using station virtual desktops instead of physical stations, you must install a CAL for each station virtual desktop. - -1. Purchase a client license for each station that is connected to your MultiPoint Services computer or server. For more information about purchasing CALs, visit the documentation for Remote Desktop licensing. - -2. From the **Start** screen, open **MultiPoint Manager**. - -3. Click the **Home** tab, and then click **Add client access licenses**. This will open the management tool for CAL licensing. - -## Set the licensing mode manually -If not properly configured the MultiPoint Services set-up will prompt with a notification about the grace -period being expired. Follow these steps to set the licensing mode: - -1. Launch **Local Group Policy Editor** (gpedit.msc). - -2. In the left pane, navigate to **Local Computer Policy->Computer Configuration->Administrative Templates->Windows Components->Remote Desktop Services->Remote Desktop Session Host->Licensing**. - -3. In the right pane, right click **Use the specified Remote Desktop license servers** and select **Edit**: - - In the group policy editor dialog, select **Enabled** - - Enter the local computer name in the **License servers to use** field. - - Select **OK** - -4. In the right pane, right click **Set the Remote Desktop licensing mode** and select **Edit** - - In the group policy editor dialog, select **Enabled** - - Set the **Licensing mode** to Per Device/Per User - - Select **OK** - - -## See Also -[Manage System Tasks Using MultiPoint Manager](Manage-System-Tasks-Using-MultiPoint-Manager.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Manage-MultiPoint-Systems-Using-MultiPoint-Dashboard.md b/WindowsServerDocs/remote/multipoint-services/Manage-MultiPoint-Systems-Using-MultiPoint-Dashboard.md deleted file mode 100644 index b3bf3306ce..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Manage-MultiPoint-Systems-Using-MultiPoint-Dashboard.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Manage MultiPoint Systems Using MultiPoint Dashboard -description: Provides an overview of using the MultiPoint Dashboard -ms.topic: overview -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Manage MultiPoint Systems Using MultiPoint Dashboard -In MultiPoint Dashboard, on the **Systems** tab, you can do the following: - -- Restart or shut down selected systems -You can restart or shut down selected MultiPoint Services systems. For information about restarting or shutting down selected systems, see the [Restart or Shut Down MultiPoint Systems](Restart-or-Shut-Down-MultiPoint-Systems.md) topic. -- Remap selected systems -You can remap selected MultiPoint Services systems. For more information about remapping selected systems, see the [Remap Selected MultiPoint Systems](Remap-Selected-MultiPoint-Systems.md) topic. - -## See Also -[Restart or Shut Down MultiPoint Systems](Restart-or-Shut-Down-MultiPoint-Systems.md) -[Remap Selected MultiPoint Systems](Remap-Selected-MultiPoint-Systems.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Manage-Station-Hardware.md b/WindowsServerDocs/remote/multipoint-services/Manage-Station-Hardware.md deleted file mode 100644 index 89a6ed54cd..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Manage-Station-Hardware.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Manage Station Hardware -description: Provides an overview of how to manage hardware for MultiPoint stations -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Manage Station Hardware -A MultiPoint Services system consists of a single computer and at least one station. Station hardware typically consists of a station hub, mouse, keyboard, and video monitor. Stations are typically physically wired to the computer. - -The following illustration shows an example of the layout of a MultiPoint Services system that has four stations. Each station is connected to the MultiPoint Services computer by using a USB hub and multi-monitor video cards. This illustration does not represent stations that are connected by using multifunction hubs. - -![Image of MultiPoint Services USB-based system layout](./media/WMSMultiPointServerUSBSystemLayout.gif) - -The topics in this section describe how you can view the status of the hardware connected to your MultiPoint Services system, and provide detailed information about the types of USB devices and other peripheral hardware devices that you can use to set up a MultiPoint Services station. The following is a brief description of the topics in this section that can help you select hardware and set up your MultiPoint Services station. - -## View Hardware Status -In MultiPoint Manager, you can use the **Stations** tab to view the status of the stations and hardware devices that are connected to the MultiPoint Services computer. For more information about how to view the status of your MultiPoint Services computer and the hardware devices that are connected to it, see the [View Hardware Status](View-Hardware-Status.md) topic. - -## Work with USB Devices -When USB devices and other peripheral hardware devices are connected to the MultiPoint Services system, they function differently when they are connected to the MultiPoint Services computer than when they are connected to a MultiPoint Services station. The [Work with USB Devices](Work-with-USB-Devices.md) topic describes how different hardware devices might function in these scenarios and provides detailed information about how to work with station hubs. - -## Work with Video Devices -The [Work with Video Devices](Work-with-Video-Devices.md) topic discusses how video devices, such as a monitor or projector, function when they are connected to a computer in your MultiPoint Services system or to a MultiPoint Services station. - -## Set Up a Station -The [Set Up a Station](Set-Up-a-Station.md) topic describes how to connect peripheral hardware devices to a MultiPoint Services station hub to create a MultiPoint Services station. MultiPoint Services supports two types of station hubs: - -- An externally powered or bus-powered multi-port *USB hub* that can support a mouse, keyboard, and other USB peripheral devices - -- A *multifunction hub* that can include an integrated video controller and ports for mouse, keyboard, and audio peripheral devices - -Both types of station hubs connect to the computer by way of a USB cable. Procedures in the [Set Up a Station](Set-Up-a-Station.md) topic describe how to connect hardware devices to each type of station hub. - -## See Also -[View Hardware Status](View-Hardware-Status.md) -[Work with USB Devices](Work-with-USB-Devices.md) -[Work with Video Devices](Work-with-Video-Devices.md) -[Set Up a Station](Set-Up-a-Station.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Manage-System-Tasks-Using-MultiPoint-Manager.md b/WindowsServerDocs/remote/multipoint-services/Manage-System-Tasks-Using-MultiPoint-Manager.md deleted file mode 100644 index dc898c97ef..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Manage-System-Tasks-Using-MultiPoint-Manager.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Manage System Tasks Using MultiPoint Manager -description: Overview of management tasks in MultiPoint Manager -ms.topic: overview -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Manage System Tasks Using MultiPoint Manager -In MultiPoint Manager, you can use the **Home** tab to perform MultiPoint Services tasks and check the state of the system. Tasks that you can perform on the **Home** tab include: - -- Editing the settings you selected when you installed MultiPoint Services, as described in the [Edit Server Settings](Edit-Server-Settings.md) topic. - -- Restarting or shutting down the computer, including user *sessions*, as described in the [Restart or Shut Down](Restart-or-Shut-Down.md) topic. - -- Switching modes to perform various administrative tasks, as described in the [Switch Between Modes](Switch-Between-Modes.md) topic. - -- Enabling or disabling disk protection, as described in the [Enable or Disable Disk Protection](Enable-or-Disable-Disk-Protection.md) topic. - -- Remapping all stations, as described in the [Remap All Stations](Remap-All-Stations.md) topic. - -- Adding or removing computers, as described in the [Add or Remove Computers](Add-or-Remove-Computers.md) topic. - -## See Also -[Edit Server Settings](Edit-Server-Settings.md) -[Restart or Shut Down](Restart-or-Shut-Down.md) -[Switch Between Modes](Switch-Between-Modes.md) -[Enable or Disable Disk Protection](Enable-or-Disable-Disk-Protection.md) -[Remap All Stations](Remap-All-Stations.md) -[Add or Remove Computers](Add-or-Remove-Computers.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Manage-User-Accounts.md b/WindowsServerDocs/remote/multipoint-services/Manage-User-Accounts.md deleted file mode 100644 index 8980942ff4..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Manage-User-Accounts.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Manage User Accounts -description: Navigational overview for managing MultiPoint Services user accounts -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Manage User Accounts -This section describes the different types of user accounts, how to create user accounts, and how to manage user accounts. In a MultiPoint Services system, there are two types of user accounts: *standard user accounts* and *administrative user accounts*, as described below. - -> [!TIP] -> The [User Account Considerations](User-Account-Considerations.md) topic provides guidelines that you should consider as you create and manage user accounts. diff --git a/WindowsServerDocs/remote/multipoint-services/Manage-User-Desktops-Using-MultiPoint-Dashboard.md b/WindowsServerDocs/remote/multipoint-services/Manage-User-Desktops-Using-MultiPoint-Dashboard.md deleted file mode 100644 index bf9e042804..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Manage-User-Desktops-Using-MultiPoint-Dashboard.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Manage User Desktops Using MultiPoint Dashboard -description: Provides an overview of the MultiPoint Dashboard -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Manage User Desktops Using MultiPoint Dashboard -In a MultiPoint Services system, a desktop is the software user interface presented on the monitor for each user *station*. The MultiPoint Dashboard is a tool which helps you manage those desktops. - -In MultiPoint Dashboard, on the **Home** tab, you can do the following: - -- View desktops -You can view the thumbnail images for each active desktop. For information about viewing thumbnails, see the [View Options for Session Thumbnails](View-Options-for-Session-Thumbnails-in-MultiPoint-Dashboard.md) topic. -- Block or unblock stations -You can block and unblock stations. You can also customize a message to display on blocked stations. For more information about blocking or unblocking stations, or creating a message to display on blocked stations, see the [Block or Unblock a Station](Block-or-Unblock-a-Station.md) topic. -- Limit web use -You can configure which websites users can visit. For information about setting websites, see the [Limit Web Access](Limit-Web-Access.md) topic. -- Block or unblock USB storage -You can block and unblock USB storage either per station or for all station. When storage is blocked, users cannot use any USB storage devices on their stations. See the [Block or Unblock USB Storage](Block-or-Unblock-USB-Storage.md) topic. -- Project a station to another station -You can project your station to another station or stations. You can also project a different selected station to all other stations. For information about projecting a station, see the [Project a Station to Other Stations](Project-a-Station-to-Other-Stations.md) topic. -- Launch or close applications on a station -You can launch or close applications on a station. For information about launching or closing applications, see the [Launch or Close Applications on a Station](Launch-or-Close-Applications-on-a-Station.md) topic. -- Use IM -You can chat with selected users. The chat message is only visible to the Dashboard user and the user of the selected session. See [Use IM](Use-IM.md) for more information. -- Change the size of thumbnail images -You can change the size of the thumbnails that display in MultiPoint Dashboard. For information about changing the thumbnail size, see [View Options for Session Thumbnails](View-Options-for-Session-Thumbnails-in-MultiPoint-Dashboard.md). -- Show all stations -You can view all of the stations that are connected to your system, including stations that are not active. For information about viewing all stations, see the [Show All Stations](Show-All-Stations.md) topic. -- Search and sort thumbnails -You can define the order and grouping of thumbnails in the dashboard. Use search to filter the thumbnails. -- Log off all monitored stations -You can log off all of the monitored stations on your MultiPoint Services system. For information about logging off monitored stations, see the [Log Off User Sessions](Log-Off-User-Sessions.md) topic. diff --git a/WindowsServerDocs/remote/multipoint-services/Manage-User-Files.md b/WindowsServerDocs/remote/multipoint-services/Manage-User-Files.md deleted file mode 100644 index a292ea5f70..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Manage-User-Files.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Manage User Files -description: Provides guidance for managing user files in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Manage User Files -Both standard users and administrative users at MultiPoint Services stations can save documents in Windows Explorer libraries and folders. A library is a collection of items, such as files and folders. Common libraries in Windows Explorer include **Documents**, **Music**, **Pictures**, and **Videos**. When working with libraries, there are two options for storing documents: - -- Store documents privately so that they are accessible only to the user who stored them in a library or folder. Note that administrative users can access privately stored documents of standard users. However, standard users cannot access privately stored documents of administrative users. For more information about keeping content private, see the [Keep Files Private](Keep-Files-Private.md) topic. - -- Store documents publicly so that they are accessible to all users on the MultiPoint Services system. For more information about sharing content with other users, see the [Share Files](Share-Files.md) topic. - -The **Documents** library, by default, includes two folders: **My Documents** (which is private) and **Public Documents** (which is public). Other document libraries contain similar pairs of private and public folders. All administrative and standard users of a MultiPoint Services system should understand how the Windows Explorer location at which they put documents and other files can affect the privacy or public access of those files. - -You can also share content with other users by using a USB storage device such as a USB flash drive or mass storage device (external hard disk). For more information about sharing content with storage devices, see the [Save and Share Files on a USB Flash Drive](Save-and-Share-Files-on-a-USB-Flash-Drive.md) topic. diff --git a/WindowsServerDocs/remote/multipoint-services/Manage-User-Stations.md b/WindowsServerDocs/remote/multipoint-services/Manage-User-Stations.md deleted file mode 100644 index 304f1d75ee..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Manage-User-Stations.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Manage User Stations -description: Learn how to manage user stations in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Manage User Stations -This section discusses managing the *stations* that make up the MultiPoint Services system. Managing a MultiPoint Services system includes both managing the hardware and software components of MultiPoint Manager. In a MultiPoint Services system, a desktop is the software user interface presented on the monitor for each user station. - -## Station status -You can view the following types of status for each desktop on the **Stations** tab. Status includes: - -- Users who are logged on - -- User sessions that are suspended, but are still active on the computer - -- Which stations are being used and by which user - -For more information about viewing desktop status, see the [View User Connection Status](View-User-Connection-Status.md) topic. - ->[!TIP] -> You can assign friendly names to each station, which might help you identify the stations more easily. Use **Identify station**, which dipslays the station name on the assigned screen. - -## Different ways to log standard users off of the MultiPoint Services system -As an *administrative user*, you can log off Windows at any time, which will have no effect on active users in your MultiPoint Services system. *Standard users* can *disconnect* their session or *log off* the MultiPoint Services system too. In the care where disk protection is enabled, if a user is leaving for the day, they should make sure to save their work on the computer or an external storage device so that when the MultiPoint Services system is shut down, the user can still retrieve their saved work another day. - -As an administrative user, you might need to end a standard user's *session*, rather than having the user log off. You can end a standard user's session in one of two ways: - -- End the session and log the user off. For more information about ending a user's session, see the [End a User Session](End-a-User-Session.md) topic. - -- Suspend the user to temporarily end the user's session, but keep the session active in the MultiPoint Services system's computer memory. The suspended user can then reconnect to the session from the same station or a different station and continue his or her work. For more information about suspending a user's session, see the [Suspend and Leave User Session Active](Suspend-and-Leave-User-Session-Active.md) topic. - -## Set a station to automatically log on -As an administrative user, you can set up one or more stations to automatically log on when the computer that is running MultiPoint Services starts. For more information about automatically logging on, see the [Set Up a Station for Automatic Logon](Set-up-a-Station-for-Automatic-Logon.md) topic. - -## Split a station -Any station monitor that has a resolution greater than 1024x768 can be split into two stations. For more information about splitting a station, see the [Split a User Station](Split-a-User-Station.md) topic. - -## See Also -[View User Connection Status](View-User-Connection-Status.md) -[Log off or Disconnect User Sessions](Log-off-or-Disconnect-User-Sessions.md) -[Suspend and Leave User Session Active](Suspend-and-Leave-User-Session-Active.md) -[Set Up a Station for Automatic Logon](Set-up-a-Station-for-Automatic-Logon.md) -[End a User Session](End-a-User-Session.md) -[Split a User Station](Split-a-User-Station.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Manage-Virtual-Desktops.md b/WindowsServerDocs/remote/multipoint-services/Manage-Virtual-Desktops.md deleted file mode 100644 index 180cf76b0c..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Manage-Virtual-Desktops.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Manage Virtual Desktops -description: Learn how to manage virtual desktops (VDI) in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Manage Virtual Desktops -Single computer VDI allows you to configure each *local* MultiPoint Services station to connect to a Windows 10 Enterprise guest operating system running in a Hyper-V virtual machine (VM) on the same MultiPoint Services computer as the station. These virtual desktop stations can be customized with application which cannot be installed on a Windows server version. - -## Enable the virtual desktop feature - -1. Open MultiPoint Manager, and then click the **Virtual Desktops** tab. - -2. Under **VDI Tasks**, click **Create virtual desktop**, and then browse your Windows 10 Enterprise .iso or VHD. - -The system is restarted, which could take several minutes. - -## Create a virtual desktop template - -1. Open MultiPoint Manager, and then click the **Virtual Desktops** tab. - -2. Under **VDI Tasks**, click **Create virtual desktop**, and then browse to your Windows 10 Enterprise .iso or VHD. - - If using the DVD, the program automatically finds the Windows 10 Enterprise .wim file. Otherwise, click **Browse**, and then navigate to the Windows 10 Enterprise .iso or VHD. - - Modify the prefix if desired. It will default to the host computer name. - - > [!NOTE] - > The prefix is used to name the template and the virtual desktop stations. The template is named prefix \-t. The virtual desktop stations will be named prefix \-*n*, where *n* is the station ID. - -4. Enter a name and password for the local administrator account that will be used to log on to all virtual station desktops that are created from the template, and then click **OK**. - - The template creation takes several minutes to complete. - - Next, learn how to customize the virtual desk template. - - > [!NOTE] - > If the MultiPoint server is domain-joined, the dialog populates an additional field which allows you to say whether the virtual machines that were created from the template should be joined to a domain. - -## Import a virtual desktop template -In the case where you have created a virtual desktop template on another MultiPoint server, you can import that template using the following steps. - -1. Open MultiPoint Manager, and then click the **Virtual Desktops** tab. - -2. Under the VDI tasks, click **Import Virtual desktop template**. - -3. Locate the template and define path and prefix for the imported template. - -## Customize the virtual desktop template -After you have created the virtual desktop template, you can customize it with applications, software updates and configure system settings. - -1. Open MultiPoint Manager, and then click the **Virtual Desktops** tab. -2. Choose the virtual desktop template, and then click **Customize virtual desktop template**. -The template opens in a separate window, and additional instructions are presented that highlight the most important steps for customizing the virtual template. Carefully review those instructions. - -## Create virtual desktop stations - -1. Open MultiPoint Manager in station mode, and then click the **Virtual Desktops** tab. - - > [!NOTE] - > If the MultiPoint Services system is not running in station mode, restart it before completing this procedure. - -2. Select the virtual desktop template in the left\-hand pane. It is named . - -3. Under template Tasks, click **Create virtual desktop stations**, and then click **OK**. - - The virtual desktop station creation process takes several minutes. - - > [!NOTE] - > If any of the local stations are currently connected to a session\-based virtual desktop, you must log off of those stations in order for them to connect to one of the newly created virtual desktop stations. - -### Validate the newly created customized virtual station desktops - -You can validate your customized virtual station desktops by logging on to one or more of the virtual desktop stations using either a local administrator account or a domain account, and then verify that the new VM\-based virtual desktops are working properly. - -## Disable Virtual Desktops - -When disabling virtual desktops the Hyper-V feature will be turned off. All users will be logged off and the system will be restarted. All virtual stations are assigned to MultiPoint local sessions after restart of the system. - -1. Open MultiPoint Manager in station mode, and then click the **Virtual Desktops** tab. - -2. Under the VDI Tasks click **Disable virtual desktops**. diff --git a/WindowsServerDocs/remote/multipoint-services/Managing-MultiPoint-Services.md b/WindowsServerDocs/remote/multipoint-services/Managing-MultiPoint-Services.md deleted file mode 100644 index 52df0ec3f5..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Managing-MultiPoint-Services.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Managing MultiPoint Services -description: Overview of articles about managing MultiPoint Services -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Managing MultiPoint Services -MultiPoint™ Services allows multiple users, each with their own independent Windows experience, to simultaneously share one computer. User stations, consisting of a monitor, keyboard, and mouse, are directly connected to the host computer through USB, video cables, or the network. - -Use the following information to learn about the tasks that you can perform in MultiPoint Manager and MultiPoint Dashboard, such as how to manage MultiPoint Services stations by using MultiPoint Manager, and how to use MultiPoint Dashboard daily. - - -- [Managing Your MultiPoint Services System](Managing-Your-MultiPoint-Services-System.md) -- [Manage Station Hardware](Manage-Station-Hardware.md) -- [Manage System Tasks Using MultiPoint Manager](Manage-System-Tasks-Using-MultiPoint-Manager.md) -- [Manage User Stations](Manage-User-Stations.md) -- [Manage User Accounts](Manage-User-Accounts.md) -- [Manage Virtual Desktops](Manage-Virtual-Desktops.md) -- [Manage User Files](Manage-User-Files.md) -- [Manage User Desktops Using MultiPoint Dashboard](Manage-User-Desktops-Using-MultiPoint-Dashboard.md) -- [Manage MultiPoint Systems Using MultiPoint Dashboard](Manage-MultiPoint-Systems-Using-MultiPoint-Dashboard.md) - -## Additional References - -- [MultiPoint Services](./introducing-multipoint-services.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Managing-Your-MultiPoint-Services-System.md b/WindowsServerDocs/remote/multipoint-services/Managing-Your-MultiPoint-Services-System.md deleted file mode 100644 index 9cec1e5270..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Managing-Your-MultiPoint-Services-System.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Managing Your MultiPoint Services System -description: Learn how to manage MultiPoint Services -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Managing Your MultiPoint Services System -MultiPoint Services enables multiple stations to be connected to one computer. A traditional station consists of a [*station hub*](Switch-Between-Modes.md) or zero client, monitor, keyboard, and mouse. Network-connected Remote Desktop Protocol (RDP) clients are also supported. - -The following illustration shows an example layout of a MultiPoint Services system that contains four *stations*. Such a setup enables multiple users to use the computer at the same time, and to perform independent work or a group activity. - -![Image of MultiPoint Services system layout](./media/WMSMultiPointServerSystemLayout.gif) - -MultiPoint Services includes MultiPoint Manager, which helps you, as an administrative user, to monitor and manage your MultiPoint system, and MultiPoint Dashboard, which provides day-to-day administrative functionality. The topics included in this Help guide describe many of the tasks that you can perform in MultiPoint Manager and MultiPoint Dashboard. - -## See Also -[Manage User Desktops Using MultiPoint Dashboard](Manage-User-Desktops-Using-MultiPoint-Dashboard.md) -[Privacy and Security Considerations](Privacy-and-Security-Considerations.md) diff --git a/WindowsServerDocs/remote/multipoint-services/MultiPoint-Services.md b/WindowsServerDocs/remote/multipoint-services/MultiPoint-Services.md deleted file mode 100644 index f00231a5dd..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/MultiPoint-Services.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: MultiPoint Services -description: Learn how to use MultiPoint Services, a solution that lets multiple users access the same system -ms.date: 07/22/2016 -ms.topic: overview -author: dknappettmsft -ms.author: daknappe ---- -# MultiPoint Services -MultiPoint Services is a solution that allows multiple users, each with their own independent and familiar Windows experience, to simultaneously share one computer. - -User stations, consisting of a monitor, keyboard, and mouse, are directly connected to the host computer through USB or video cables. Because MultiPoint Services is a genuine Microsoft published software product, when properly licensed, you are eligible to receive support by Microsoft or an authorized partner. This gives you the full capabilities of Windows, access to all the latest updates, and confidence that you are achieving the experience you expect. - -Because MultiPoint Services enables multiple users to share one computer, it can provide a low-cost alternative to traditional computing scenarios where each user has their own computer. MultiPoint Services also provides an easy management solution for MultiPoint Services system administration known as MultiPoint Manager and an easy management solution for day\-to\-day administration, known as MultiPoint Dashboard. diff --git a/WindowsServerDocs/remote/multipoint-services/MultiPoint-services-Site-Planning.md b/WindowsServerDocs/remote/multipoint-services/MultiPoint-services-Site-Planning.md deleted file mode 100644 index 04695b8dd8..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/MultiPoint-services-Site-Planning.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -title: MultiPoint Services Site Planning -description: Planning information for MultiPoint Services deployments in Windows Server 2016 -ms.date: 07/22/2016 -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe ---- -# MultiPoint Services Site Planning -You should consider the location where one or more computers running MultiPoint Services and its associated stations will be deployed. - -The computer that is running MultiPoint Services role should have convenient access to a power supply and to the peripheral devices that are connected directly to it, such as a printer. Additionally, the computer running MultiPoint Services must have convenient access to a network connection. A network connection is required for accessing the Internet, and where available, a LAN. - -Additional factors to consider include the following: - -- Will the MultiPoint Services system be set up in a specific room, or will it be set up on a rolling cart or table, so that it can be moved from place to place? - - > [!NOTE] - > If you plan to use a mobile setup, you can *associate* the stations with MultiPoint Services every time you reconnect them to make sure that each keyboard and mouse is associated with the appropriate monitor. - -- Will the primary station be located next to the other stations, or will it be separate? For example, if the MultiPoint Services system is set up in a classroom, will the primary station be on the teacher's desk and the standard stations positioned elsewhere in the room? When the computer running MultiPoint Services is restarted, the primary station will have access to the startup screens. If you are concerned about this level of access in a classroom setting, you may prefer to put the primary station at the teacher's desk. - -- How many stations will fit in the room? - -- Do you need a network? A single server solution that uses direct video connected or USB zero client connected stations does not need a network. - -- Are there enough network connections in the room to support the required number of computers running MultiPoint Services - -- Where are the power outlets located? - -- Will you need an additional display device, such as a projector? If you plan to use a projector, will it hang from the ceiling, or will it be positioned on a table? - -- What kind of cables will be required, and how many will be needed? - -- Consider how you might want to expand in the future. Will you be adding more stations? - -## Station layout and configuration -The physical layout of your site may affect your choice of station type. For more details about the different station types, refer to [MultiPoint Stations](MultiPoint-services-Stations.md) in this guide. Multiple station types are allowed on a single MultiPoint Services. This provides you with extra flexibility to meet your installation needs. - -### Layout for direct-video-connected stations - -- For a direct-video-connected station, the distance between the monitors and computer is limited by the video cable length. - -- Using intermediate hubs or daisy-chained station hubs is supported for ease-of-deployment, but the maximum recommended number of consecutive hubs is three. This means that the maximum distance from the computer to the station hub is 15 meters, because each USB 2.0 cable has the maximum length of five meters. - -> [!IMPORTANT] -> There should always be at least one direct video connected station per computer to act as the primary station. - -### Layout for USB zero client connected stations - -- Using intermediate hubs or daisy-chained station hubs is supported for ease-of-deployment, but the maximum recommended number of consecutive hubs is three. This means that the maximum distance from the computer to the station hub is 15 meters, because each USB 2.0 cable has the maximum length of five meters. - -- The maximum recommended number of USB zero clients connected to a single intermediate hub is three. - - > [!NOTE] - > Some computers come with a generic hub on the motherboard, which has the effect of adding an additional hub between the *root hub* of the computer and the station hubs. - -- If video will be heavily used, it is recommended that you connect no more than two USB zero clients to a USB port on the server. For example, if an intermediate hub is used, only two USB zero clients should be connected to it. Or if you are daisy chaining USB zero clients, only two USB zero clients should be chained together. The addition of each USB zero client to the USB port on the server decreases the video bandwidth available. - -- If you plan to connect more than three USB zero clients to a single USB port on the server, using USB 3.0 between the server and the intermediate hub is recommended. - -> [!NOTE] -> It is recommended that you verify the performance by using your applications and hardware to decide how many USB zero clients you can connect to a USB port on the server. - -![Downstream hubs](./media/WMS_diagram6.gif) - -**Figure 5** MultiPoint Services system with three USB zero clients connected to a single intermediate hub - -### Layout for RDP-over-LAN connected stations -There are no physical distance limitations for LAN clients. As long as they are on the LAN, they can connect to the MultiPoint Services system. - -## Using additional hubs -Additional hubs can be used to make installation easier. There are three types of hubs that are used on a MultiPoint Services system: - -- [Station hubs](#station-hubs) - -- [Intermediate hubs](#intermediate-hubs) - -- [Downstream hubs](#downstream-hubs) - -### Station hubs -A station hub is an external hub that has been associated with a MultiPoint Services station. As a minimum, the station hub will have a keyboard plugged-in to it. It may also have additional peripherals attached. A station hub can be a generic USB hub that conforms to the USB 2.0 or later specification. Station hubs should be externally powered if high-powered devices will plugin to them. - -**Root hub** A USB hub that is built-in to the host controller on a computer's motherboard is known as a *root hub*. Station hubs are generally plugged-in to the root hub on the computer running MultiPoint Services. - -> [!NOTE] -> Root hubs should not be used as station hubs. When USB ports are built-in to a computer, often it is not possible to determine which USB root hub they are internally connected to. As such, if you plugged-in a station keyboard and mouse directly to the USB ports of the computer, you may actually be plugging-in the keyboard and mouse to different USB root hubs. To guarantee that the keyboard and mouse are on the same hub, plug-in a station hub to the computer's USB port, and then plug-in the keyboard and mouse to that station hub. - -**Daisy chaining stations** It may be easier to connect station hubs to another station hub rather than directly to the computer. This allows you to connect a USB hub to a station hub that is already plugged-in to the computer, so that you have a station hub attached to another station hub. - -There should be no more than three USB zero clients or station hubs daisy chained consecutively. Care must be taken that the USB bandwidth is not exceeded when daisy chaining station hubs. - -![Daisy chaining stations](./media/WMS_diagram5.gif) - -**Figure 6** MultiPoint Services system with daisy-chained stations - -### Intermediate hubs -An intermediate hub is a hub that is between the server and a station hub. It is typically used to increase the number of ports that are available for station hubs or to extend the distance of the stations from the computer. It is recommended that no more than two intermediate hubs are used between a station hub and the server. - -Intermediate hubs must be USB 2.0 or later, and they must be externally powered. USB 3.0 is recommended between the server and the intermediate hub if you are connecting more than three USB zero clients to an intermediate hub. - -### Downstream hubs -A downstream hub is connected to a station hub to add more available ports for station devices. A downstream hub can be externally powered or bus-powered, depending on the devices that are plugged-in to the hub. - -![Multiple USB zero client connections](./media/WMS_diagram4.gif "WMS_diagram4") - -**Figure 7** MultiPoint Services system with an intermediate hub, a station hub, and a downstream hub - -## Users, stations, and computers -The number of stations you will need depends on the number of people who will have to access the computers running MultiPoint Services at the same time. Similarly, the number of computers running MultiPoint Services you will need depends on the total number of stations required. Direct-video-connected stations, USB-zero-client-connected stations, and RDP-over-LAN-connected stations are all considered stations. In addition, if the split-screen functionality is used, each half is considered a station. - -## Power considerations -The following components require access to a power strip or outlet: - -- Server -- Monitors -- Intermediate hubs \(if used\) -- Some USB zero clients -- Powered USB devices, such as some external storage devices and DVD drives - -## Sample MultiPoint Services system layouts -Depending on the available furniture, the size of the room, the number of computers that are running MultiPoint Services, and the stations in the room, there are a variety of ways that the physical stations can be arranged. The following diagrams illustrate five possible alternatives. - -> [!NOTE] -> Some of these diagrams show a projector connected to the MultiPoint Services system. This is only an example; including a projector in a MultiPoint Services system is optional. - -**Computer lab** In this setup, the stations are arranged around the walls of the room, with the students facing the walls. - -![Computer Lab Classroom Set-up](./media/WMS_ComputerLabLayout.gif) - -**Groups** In this setup, there are three computers that are running MultiPoint Services, with stations clustered around each computer. - -![Classroom configured with server pods](./media/WMS_ClassroomPods.gif) - -**Lecture room** In this setup, the stations are set up in rows. An advantage of this setup is that all of the students face the instructor. - -![Classroom configured as Lecture Room](./media/WMS_LectureRoom.gif) - -**Activity center** This setup consists of a traditional lecture-room layout for the desks, and it has a separate area with a single computer that is running MultiPoint Services with its associated stations. - -![MultiPoint Services Activity Center](./media/WMSActivityCenter.gif) - -**Small business office** In this setup, the computer that is running MultiPoint Services is placed in a central location and users throughout the office connect to it by using a local area network \(LAN\). - -![USB zero client connected station](./media/Diagram1.gif) diff --git a/WindowsServerDocs/remote/multipoint-services/MultiPoint-services-Stations.md b/WindowsServerDocs/remote/multipoint-services/MultiPoint-services-Stations.md deleted file mode 100644 index eba26fedc8..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/MultiPoint-services-Stations.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -title: MultiPoint Stations -description: Learn about stations in MultiPoint Services, including the different options for users -ms.date: 07/22/2016 -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe ---- - -# MultiPoint Stations -In a MultiPoint Services system environment, *stations* are the user endpoints for connecting to the computer running MultiPoint Services. Each station provides the user with an independent Windows 10 experience. The following station types are supported: - -- Direct-video-connected stations - -- USB-zero-client-connected stations (including USB-over-Ethernet zero clients) - -- RDP-over-LAN-connected stations (for rich client or thin client computers) - -Full PCs that have the MultiPoint Connector installed can also be monitored and controlled using the MultiPoint Dashboard. On Windows 10 the MultiPoint Connector can be enabled through the control panel for Windows features. - -Multipoint Services supports any combination of these station types, but it is recommended that one station be a direct-video-connected station, which can serve as the primary station. The reason for this recommendation is to be able to anticipate support scenarios. For example, to interact with the system's BIOS before MultiPoint Services is running. - -## Primary stations and standard stations -One direct-video-connected station is defined as the *primary station*. The remaining stations are referred to as *standard stations*. - -The primary station displays the startup screens when the computer is turned on. It provides access to system configuration and troubleshooting information that is only available during startup. The primary station must be a direct-video-connected station. After startup, you can use the primary station like any other MultiPoint station. - -## Direct-video-connected stations -The computer running MultiPoint Services can contain multiple video cards, each of which can have one or more video ports. This allows you to plug monitors for multiple stations directly into the computer. Keyboards and mice are connected through USB hubs that are associated with each monitor. These hubs are referred to as *station hubs*. Other peripheral devices, such as speakers, headphones, or USB storage devices can also be connected to a station hub, and they are available only to the user of that station. - -> [!IMPORTANT] -> There should be at least one *direct-video-connected station* per server to act as the primary station to display the startup process when the computer is turned on. - -![Image of MultiPoint Services USB-based system layout](./media/WMSMultiPointServerUSBSystemLayout.gif) - -**Figure 1** MultiPoint services system with four direct-video-connected stations - -### PS/2 stations -With MultiPoint Services, you can map the PS/2 keyboard and mouse on the motherboard to a direct video connected monitor to create a PS/2 station. High-definition analog audio on the motherboard is the audio associated with this type of station. This does not apply to computers where there are no PS/2 jacks on the motherboard. - -## USB-zero-client-connected stations -USB-zero-client-connected stations utilize a *USB zero client* as a station hub. USB zero clients are sometimes referred to as a multifunction hub with video. They are a hub that connects to the computer through a USB cable, and these hubs typically support a video monitor, a mouse and keyboard (PS/2 or USB), audio, and additional USB devices. This guide refers to these specialized hubs as USB zero clients. - -The following diagram shows a MultiPoint server system with a primary station (direct video connected station) and two additional USB zero client connected stations. - -![USB zero-client connected stations](./media/WMS11_diagram7.gif) - -**Figure 2** MultiPoint Services system with a primary station and two USB zero-client-connected stations - -### USB-over-Ethernet zero clients -USB-over-Ethernet zero clients are a variation of USB zero clients that send USB over LAN to the MultiPoint Services system. These types of USB zero clients function similarly to other USB zero clients, but are not limited by USB cable length maximums. USB-over-Ethernet zero clients are not traditional thin clients, and they appear as virtual USB devices on the MultiPoint Services system. When using these devices, refer to the device manufacturer for specific performance and site planning recommendations. Most devices have a third-party plugin for MultiPoint Manager that allows you to associate and connect devices to the MultiPoint Services system. - -## RDP-over-LAN connected stations -Thin clients and traditional desktop, laptop, or tablet computers, can connect to the computer running MultiPoint Services through the local area network (LAN) by using Remote Desktop Protocol (RDP) or a proprietary protocol and the Remote Desktop Protocol Provider. RDP connections provide an end-user experience that is very similar to any other MultiPoint station, but makes use of the local client computer's hardware. Learn more about our remote desktop applications available for Android, iOS, Mac and Windows in [Remote Desktop clients](../remote-desktop-services/clients/remote-desktop-clients.md). - -Clients and devices that are running Microsoft RemoteFX can provide a rich multimedia experience by taking advantage of the processor and video hardware capabilities of the local thin client or computer to provide high-definition video over the network. - -If you have existing LAN clients MultiPoint Services can provide a quick and cost effective way to simultaneously upgrade all of your users to a Windows 10 experience. - -From a deployment and administration perspective, the following differences exist when you use RDP-over-LAN-connected stations: - -- Not limited to physical USB connection distances - -- Potential to reuse older computer hardware as stations - -- Easier to scale to a higher number of stations. Any client on your network can potentially be used as a remote station - -- No hardware troubleshooting through the MultiPoint Manager console - -- No split-screen functionality. - - For more information, see [Split-screen Stations](#split-screen-stations) later in this topic - -- No station rename or configuring automatic logon through the MultiPoint Manager console - -![USB zero client connected station](./media/Diagram1.gif) - -**Figure 3** MultiPoint Services system with RDP-over-LAN-connected stations - -## Additional configuration options - -### Split-screen stations -MultiPoint Services offers a split screen option on computers with direct-video-connected stations or USB-zero-client-connected stations. A split screen provides the ability to create an additional station per monitor. Instead of requiring two monitors, you can use one monitor with two station hub setups to create two stations with one monitor. You can quickly increase the number of available stations without purchasing additional monitors, USB-zero clients, or video cards. - -The benefits of using a split-screen station can include: - -- Reducing cost and space by accommodating more users on a MultiPoint Services system. - -- Allowing two users to collaborate side-by-side on a project. - -- Allowing a teacher to demonstrate a procedure on one station while a student follows along on the other station. - -Any MultiPoint Services station monitor that has a 1024x768 resolution or greater can be split into two station screens. For the best split screen user experience, a wide screen with a minimum 1600x900 resolution is recommended. A mini keyboard without a number pad is also recommended to allow the two keyboards to fit in front of the monitor. - -To create split-screen stations, you set up one direct-video-connected or USB-zero-client-connected station. Then you add an additional station hub by plugging in a keyboard and mouse to a USB hub that is connected to the server. You can then convert the station into two stations by using MultiPoint Manager to split the screen and map the new hub to half of the monitor. The left half of the screen becomes one station and the right half becomes a second station. - -After a station is split, one user can log on to the left station while another user logs on to the right station. - -![Split-screen stations](./media/WMS_diagram3.gif) - -**Figure 4** MultiPoint Services system with split screen stations - -## Station type comparison - -| Description | Direct Video Connected | USB Zero Client Connected | RDP-over-LAN Connected | -|--|--|--|--| -| Video performance | Recommended for best video performance | | Use thin clients that support RemoteFX for improved video quality at lower network bandwidth | -| Physical limitations | Limited by video cable length and USB hub and cable length (Recommended 15 meter maximum length) | Limited by USB hub and cable length (Recommended 15 meter maximum length) | Limited by LAN distribution | -| Number of stations allowed | Limited by number of available PCIe slots on the motherboard times the video ports per video card | Total number may be limited by USB zero client manufacturer (For more information, see the Note that follows this table.) | Limited by available ports on network switch | -| Split-screen | Yes | Yes | No | -| MultiPoint Manager station peripheral status, auto-logon configuration, station renaming | Yes | Yes | No | -| Access to server startup menus | Yes | No | No | - -> [!NOTE] -> The total number of USB zero clients that are connected to the server may be limited by the manufacturer or the hardware capability of the computer running MultiPoint Services. diff --git a/WindowsServerDocs/remote/multipoint-services/MultiPoint-services-Virtualization-Support.md b/WindowsServerDocs/remote/multipoint-services/MultiPoint-services-Virtualization-Support.md deleted file mode 100644 index e44eeba358..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/MultiPoint-services-Virtualization-Support.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: MultiPoint Services Virtualization Support -description: Describes how to use MultiPoint Services with Hyper-V -ms.date: 07/22/2016 -ms.topic: lifecycle -author: dknappettmsft -ms.author: daknappe ---- -# MultiPoint Services Virtualization Support -MultiPoint Services supports the Hyper-V role in two ways: - -- MultiPoint Services can be deployed as a guest operating system on a server running Hyper-V. - -- MultiPoint Services can be used as a virtualization server. - -Running MultiPoint Services on a virtual machine provides the use of the Hyper-V tools to manage operating systems. These tools include checkpoint and rollback features, and they allow you to export and import virtual machines. For larger installations, you can consolidate servers by running multiple MultiPoint Services virtual computers on a single physical server. Possible scenarios include: - -- A single classroom or lab has more than 20 seats. Rather than deploying multiple physical computers running MultiPoint Services, you can deploy multiple virtual machines on a single physical computer. - - > [!NOTE] - > You can manage multiple MultiPoint servers, whether physical or virtual, through a single MultiPoint Manager console. - -- The MultiPoint server is running on a virtual machine with another server infrastructure on the same physical computer. In that case this server infrastructure centralizes the domain, security, and data for the network. The MultiPoint server provides Remote Desktop Services and centralizes the desktops. - -> [!NOTE] -> When running MultiPoint Services on a virtual machine, USB-over-Ethernet and RDP client stations are supported. Direct video and USB zero client connected stations are not supported. - -For more information about the Hyper-V role, see [Hyper-V](../../virtualization/hyper-v/hyper-v-on-windows-server.md). diff --git a/WindowsServerDocs/remote/multipoint-services/Network-Considerations-and-User-Accounts.md b/WindowsServerDocs/remote/multipoint-services/Network-Considerations-and-User-Accounts.md deleted file mode 100644 index a82e5db57f..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Network-Considerations-and-User-Accounts.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Network Considerations and User Accounts -description: Provides planning information for different network and user scenarios with MultiPoint Services -ms.date: 07/22/2016 -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe ---- -# Network Considerations and User Accounts -MultiPoint Services can be deployed in a variety of network environments, and it can support local user accounts and domain user accounts. Generally, MultiPoint Services user accounts will be managed in one of the following network environments: - -- A single computer running MultiPoint Services with local user accounts - -- Multiple computers running MultiPoint Services, each with a local user account - -- Multiple computers running MultiPoint Services and that are using domain user accounts - -By definition, *local user accounts* can only be accessed from the computer on which they were created. Local user accounts are user accounts that are created on a specific computer that is running MultiPoint Services. In contrast, *domain user accounts* are user accounts that reside on a domain controller, and they can be accessed from any computer that is connected to the domain. When you are deciding which type of network environment to use, consider the following: - -- Will resources be shared among servers? - -- Will users be switching between servers? - -- Will users access database servers that require authentication? - -- Will users access internal web servers that require authentication? - -- Is there an existing Active Directory domain infrastructure in place? - -- Who will be using the MultiPoint Manager console to manage user desktops, view thumbnails, add users, limit websites, and so on? Will this person be managing more than one server? This person must have administrative privileges on the servers. - -The following sections address user account management in these networking environments. - -## Single MultiPoint Server with local user accounts -In environments with a single computer that is running MultiPoint Services, there is no requirement to have a network. However, to take advantage of Internet resources, the networking requirements may be as basic as a router and a connection to an Internet service provider (ISP). Network connections that are associated with a network adapter on MultiPoint Services are configured, by default, to obtain an IP address and DNS server address automatically through DHCP. Internet routers are typically configured as DHCP servers, and they provide private IP addresses to computers that connect to them on the internal network. Therefore, a single computer running MultiPoint Services may be able to connect to the internal interface of the router, obtain automatic IP information, and connect to the Internet without significant effort or configuration by an administrator. - -A common way to manage users in this kind of environment is to create a local user account for each person who will access the system. Anyone who has a local user account on that computer can log on to MultiPoint Services from any station that is associated with the system. Local user accounts can be created and managed from MultiPoint Manager. - -## Multiple MultiPoint Server systems with local user accounts -Given that local user accounts are only accessible from the computer on which they were created, when you deploy multiple MultiPoint Services systems in an environment, you can manage local user accounts in one of two ways: - -- You can create user accounts for specific individuals on specific computers running MultiPoint Services. - -- You can use MultiPoint Manager to create accounts for every user on every computer running MultiPoint Services. - -For example, if you plan to assign users to a specific computer running MultiPoint Services, you might create four local user accounts on Computer A (user01, user02, user03, and user04) and four local user accounts on Computer B (user05, user06, user07, and user08). In this scenario, users 01\-04 can log on to Computer A from any station that is connected to it; however, they cannot log on to Computer B. The same is true for users 05\-08, who would be able to log on only to Computer B, but not to Computer A. Depending on the specific deployment environment, this can be acceptable or even desirable. - -However, if every user must be able to log on to any of the computers running MultiPoint Services, a local user account must be created for each user on each computer that is running MultiPoint Services. Choosing to manage users in this manner introduces certain complexities. For example, if user01 logs on to Computer A on Monday and saves a file in the Documents folder, and then the user logs on to Computer B on Tuesday, the file that was saved in the Documents folder on Computer A will not be accessible on Computer B. - -Additionally, if a user has accounts on Computer A and Computer B, there is no way to automatically synchronize the passwords for the accounts. This can result in users having difficulty logging on should the account password be changed on one computer, but not the other. You can simplify user account management in this kind of network environment by assigning each user to a single computer that is running MultiPoint Services. This way, the user can log on to any of the stations that are associated with that computer and access the appropriate files. - -## Multiple MultiPoint Services systems with domain accounts -Domain environments are common in large network environments that include multiple servers. For example, you might join one or more computers running the MultiPoint Services role to a domain, and then use Microsoft Active Directory to manage user accounts that can be accessed from any computer in the domain. This allows for individual domain user accounts to be created and accessed from any station in any MultiPoint Services system that is joined to the domain. - -When you deploy MultiPoint Services in a domain environment, there are several factors to consider: - -- If domain accounts are used, they cannot be managed from MultiPoint Manager. - -- By default, MultiPoint Services is configured to give each user permission to log on to only one station at a time. If you decide to allow users to log on to multiple stations at the same time using a single account, you can use the **Edit Server Settings** option in MultiPoint Manager. - -- The location of domain controllers may affect the speed and reliability with which users will be able to authenticate with the domain and locate resources. - -## Single user account for multiple stations -MultiPoint Services has the ability to log on to multiple stations on the same computer simultaneously using a single user account. This feature is useful in environments where users are not given unique user names, and where using a single user account can simplify the management of the MultiPoint Services system. - diff --git a/WindowsServerDocs/remote/multipoint-services/Optional-configuration-tasks-for-a-MultiPoint-services-deployment.md b/WindowsServerDocs/remote/multipoint-services/Optional-configuration-tasks-for-a-MultiPoint-services-deployment.md deleted file mode 100644 index e0f50fd959..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Optional-configuration-tasks-for-a-MultiPoint-services-deployment.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Optional configuration tasks for a MultiPoint Services deployment -description: Navigational topic for MultiPoint Services configuration information -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Optional configuration tasks for a MultiPoint Services deployment -Topics in this section explain how to perform optional configuration tasks on your MultiPoint Services system. - -[Set up a split-screen station](Set-up-a-split-screen-station-in-MultiPoint-services.md) -[Add printers](Add-printers.md) -[Create Windows 10 Enterprise virtual desktops for stations](Create-Windows-10-Enterprise-virtual-desktops-for-stations.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Plan-user-accounts-for-your-MultiPoint-services-environment.md b/WindowsServerDocs/remote/multipoint-services/Plan-user-accounts-for-your-MultiPoint-services-environment.md deleted file mode 100644 index 9268804bec..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Plan-user-accounts-for-your-MultiPoint-services-environment.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Plan user accounts for your MultiPoint Services environment -description: Planning information for user accounts in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe ---- -# Plan user accounts for your MultiPoint Services environment -The best way to implement user accounts in MultiPoint Services depends on the size and complexity of your deployment: - -- **Local user accounts** - For a small deployment with only a few computers running MultiPoind Services and few users, you might find it most convenient to use *local user accounts* that are created on MultiPoint Services. You can create an individual account for each person who will use the system, or create a generic account for each station, which anyone can use to log on. MultiPoint Services administrators create and manage local user accounts by using MultiPoint Manager. The local accounts can be administrators, have limited administrative rights, or be regular users with no access to the MultiPoint Services Desktop or MultiPoint Manager. - -- **Domain accounts** - If your environment has many computers running MultiPoint Services and many users, you probably will find it more useful to set up an Active Directory Domain Services \(AD DS\) domain and use *domain user accounts*, which enable a user to access her own user profile and settings from any station in the domain. Domain user accounts must be created on the domain controller by a domain administrator. - -> [!NOTE] -> The following sections discuss scenarios that you might implement for local user accounts in MultiPoint Services. If you are using domain user accounts, see the "One or more MultiPoint servers in a domain network environment" scenario in [Example scenarios: MultiPoint Services user accounts](./multipoint-users-scenario.md). - -## Planning local user accounts -The following sections consider the advantages, disadvantages, and requirements for several ways to implement individual or shared local user accounts in your Windows MultiPoint Services environment. - -### Use individual local user accounts -When creating local user accounts, you have the option two approaches. Assign each user to a particular server running MultiPoint Services and creating a single account for each user. Or create local user accounts for all user on every computer running Multipoint services. A key advantage of implementing individual user accounts is that each user has his or her own Windows desktop experience that includes private folders for storing data. - -From a system management perspective, assigning users to a specific MultiPoint Services computer might be more convenient. For example, if you have two MultiPoint servers with five stations each, you might create local user accounts as illustrated in the following table. - -**Table 1: Assigning local user accounts to specific computers running MultiPoint Services** - -|Computer A|Computer B| -|--------------|--------------| -|UserAccount_01|UserAccount_06| -|UserAccount_02|UserAccount_07| -|UserAccount_03|UserAccount_08| -|UserAccount_04|UserAccount_09| -|UserAccount_05|UserAccount_10| - -In this scenario, each user has a single account on a particular computer. Therefore, everyone who has a local account on Computer A can log on to her or his account from any station associated with Computer A. However, these users cannot access their accounts if they use a station associated with Computer B, and vice versa. An advantage to this approach is that, by always connecting to the same computer, users can always find and access their files. - -In contrast, it is also possible to replicate individual user accounts on all computers running MultiPoint Services, as illustrated in the following table. - -**Table 2: Replicating user accounts on all computers running MultiPoint Services** - -|Computer A|Computer B| -|--------------|--------------| -|UserAccount_01|UserAccount_01| -|UserAccount_02|UserAccount_02| -|UserAccount_03|UserAccount_03| -|UserAccount_04|UserAccount_04| -|UserAccount_05|UserAccount_05| - -An advantage of this approach is that users have a local user account on every available MultiPoint Services. However, the disadvantages might outweigh this advantage. For example, even if the user name and password for a particular person are the same on both computers, the accounts are not linked to each other. Therefore, if a user logs on to his or her account on Computer A on Monday, saves a file, and then logs on to his or her account on Computer B on Tuesday, he or she will not be able to access the file previously saved on Computer A. Additionally, replicating user accounts on multiple computers increases the administrative overhead and storage requirements. - -### Use generic local user accounts -If your MultiPoint Services system is not connected to a domain, and you do not want to create an individual account for each user, you can create generic accounts for each station. For example, if you have two computers running MultiPoint Services, and five stations are associated with each computer, you might decide to create user accounts similar to those shown in the following table. - -**Table 3: Creating generic user accounts, one account per station** - -|Computer A|Computer B| -|--------------|--------------| -|Computer_A-Station_01|Computer_B-Station_01| -|Computer_A-Station_02|Computer_B-Station_02| -|Computer_A-Station_03|Computer_B-Station_03| -|Computer_A-Station_04|Computer_B-Station_04| -|Computer_A-Station_05|Computer_B-Station_05| - -In this scenario, every station account has the same password, and both the passwords and generic user account names are available to all users. An advantage to this approach is that the overhead of managing user accounts is likely to be less than if using individual accounts, because there typically are fewer stations than users. Additionally, the overhead caused by replicating user accounts on every server is eliminated. - -Another option is to create generic accounts on each server. Every user logs on to a server as the same account. To allow this, you must enable multiple sessions per account. You can further simplify by using the same account name and password on all servers. This simplifies logon for the users, who need only know one account name and password to use any station on any server. It should be noted that in this scenario all users can see any change that any user makes. For example, if a file is saved to the desktop, all users can see the file. - -> [!IMPORTANT] -> It is important to understand that when users share a user account, either one per server or one per station, files saved on the server – even files saved in My Documents - are not private. Any user who logs on with the account has access to those files. When you use one account per station, if a user saves files to My Documents on one station, the user does not have access to those files on a different station. The same occurs when logging on to different MultiPoint Services computers. - -To enable users to access their files from any station, you can use a file server, create a file share for each user account, or let users store their personal documents on a USB flash drive or other private storage device. Individual USB flash drives enable individual users to store private documents even if they are sharing a user account on a MultiPoint Services. diff --git a/WindowsServerDocs/remote/multipoint-services/Planning-a-MultiPoint-Services-Deployment.md b/WindowsServerDocs/remote/multipoint-services/Planning-a-MultiPoint-Services-Deployment.md deleted file mode 100644 index 41bbfe52c4..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Planning-a-MultiPoint-Services-Deployment.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Planning a MultiPoint Services Deployment -description: Navigational topic for information for planning your MultiPoint Services deployment -ms.date: 07/22/2016 -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe ---- -# Planning a MultiPoint Services Deployment -MultiPoint Services enables multiple stations to be connected to one computer. Multiple users can then share one computer at the same time. Each station consists of a station hub, monitor, keyboard, and mouse. MultiPoint Services includes the MultiPoint Manager application, which helps you, as an administrative user, to monitor and manage MultiPoint stations, and the MultiPoint Dashboard application, which provides day-to-day administrative functionality. - -Use the following information to plan your deployment: - -- [Introducing MultiPoint Services](Introducing-MultiPoint-services.md) -- [Common Usage Scenarios](Common-MultiPoint-services-Usage-Scenarios.md) -- [MultiPoint Stations](MultiPoint-services-Stations.md) -- [Selecting Hardware for Your MultiPoint Services System](./select-hardware-mps.md) -- [Hardware Requirements and Performance Recommendations](./hardware-and-performance-recommendations.md) -- [MultiPoint Services Site Planning](MultiPoint-services-Site-Planning.md) -- [Network Considerations and User Accounts](Network-Considerations-and-User-Accounts.md) -- [Storing Files with MultiPoint Services](Storing-Files-with-MultiPoint-services.md) -- [Protecting the System Volume with Disk Protection](Protecting-the-System-Volume-with-Disk-Protection.md) -- [MultiPoint Services Virtualization Support](MultiPoint-services-Virtualization-Support.md) -- [Application Considerations](Application-Considerations.md) -- [Predeployment Checklist](Predeployment-Checklist.md) - -You can also visit the [MultiPoint Services](./introducing-multipoint-services.md). diff --git a/WindowsServerDocs/remote/multipoint-services/Predeployment-Checklist.md b/WindowsServerDocs/remote/multipoint-services/Predeployment-Checklist.md deleted file mode 100644 index a73e0b78aa..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Predeployment-Checklist.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Predeployment Checklist -description: Provides a checklist you can use to plan your MultiPoint Services deployment -ms.date: 07/22/2016 -ms.topic: checklist -author: dknappettmsft -ms.author: daknappe ---- -# Predeployment Checklist -Use the following checklist to help you plan your MultiPoint Services deployment. - -|Step|Issue|Help Topic| -|--------|---------|--------------| -|1.|Verify that your applications are compatible with MultiPoint Services.|[Application Considerations](Application-Considerations.md)| -|2.|Determine the number of users who are likely to access, at the same time, each computer that is running MultiPoint Services so that you can estimate the number of required computers that must run MultiPoint Services.|[Users, stations, and computers](MultiPoint-services-Site-Planning.md#users-stations-and-computers)| -|3.|Understand the software applications and the web content that will likely be accessed by users and the impact that will have on system performance.|[Hardware Requirements and Performance Recommendations](hardware-and-performance-recommendations.md)| -|4.|Determine the number and type of stations that will be connected to the system.|[MultiPoint Stations](MultiPoint-services-Stations.md)| -|5.|Determine the hardware that is needed.|[Selecting Hardware for Your MultiPoint Services System](./select-hardware-mps.md) and [Hardware Requirements and Performance Recommendations](hardware-and-performance-recommendations.md)| -|6.|Determine where your MultiPoint Services system will be located. Will it be set up in a single room, or will it be set up so that it can be moved from one location to another?|[MultiPoint Server Site Planning](MultiPoint-services-Site-Planning.md)| -|7.|Determine how the stations will be arranged.|[MultiPoint Services Site Planning](MultiPoint-services-Site-Planning.md)| -|8.|Verify a proper power and network infrastructure.|[MultiPoint Services Site Planning](MultiPoint-services-Site-Planning.md)| -|9.|Determine how user accounts will be implemented and managed.|[Network Considerations and User Accounts](Network-Considerations-and-User-Accounts.md)| -|10.|Determine how user files will be shared and stored.|[Storing Files with MultiPoint Services](Storing-Files-with-MultiPoint-services.md)| diff --git a/WindowsServerDocs/remote/multipoint-services/Prepare-your-MultiPoint-services-system-for-users.md b/WindowsServerDocs/remote/multipoint-services/Prepare-your-MultiPoint-services-system-for-users.md deleted file mode 100644 index 978fdd2874..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Prepare-your-MultiPoint-services-system-for-users.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Prepare your Windows MultiPoint Services system for users -description: Navigation topic for planning user management in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Prepare your MultiPoint Services system for users -After you install and configure MultiPoint Services, and perform any additional configuration and hardware setups, you are ready to give users access to the system. You will need to plan and create user accounts. In some environments, you also need to configure stations for auto-logon and allow multiple sessions for your shared user accounts. And you need to decide how to set up file sharing for your users. All of these topics are covered in this section. - -> [!NOTE] -> After you create your user accounts and make the other configuration updates to prepare for users, we recommend that you turn on Disk Protection so that no user can inadvertently make changes to system files and settings. For more information, see [Configure Disk Protection](Configure-Disk-Protection-in-MultiPoint-services.md). - -Use the following information to prepare your system: -[Plan user accounts for your MultiPoint services environment](Plan-user-accounts-for-your-MultiPoint-services-environment.md) -[Example scenarios for user accounts creation](./multipoint-users-scenario.md) -[Create local user accounts in MultiPoint Services](Create-local-user-accounts.md) -[Limit users' access to the server](./limit-user-access-to-multipoint.md) -[Configure stations for automatic logon](Configure-stations-for-automatic-logon.md) -[Allow one account to have multiple sessions](Allow-one-account-to-have-multiple-sessions.md) -[Enable file sharing](Enable-file-sharing-in-MultiPoint-services.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Privacy-and-Security-Considerations.md b/WindowsServerDocs/remote/multipoint-services/Privacy-and-Security-Considerations.md deleted file mode 100644 index ee9f1aca45..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Privacy-and-Security-Considerations.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Privacy and Security Considerations -description: Provides privacy and security insights about MultiPoint Services -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Privacy and Security Considerations -Because your MultiPoint Services system is, by design, a shared computing environment, you should consider the following privacy and safe computing issues. - -## Privacy in a MultiPoint Services system -The capabilities of MultiPoint Services to share or keep private user documents may be new to you, other *administrative users*, *MultiPoint Dashboard users*, or *standard users* on your MultiPoint Services system. In MultiPoint Manager, you can see screen activity on all active standard user desktops. Standard users are notified when they log on to the MultiPoint Services system, and must accept this monitoring in order to proceed. For more information about how to share content or keep it private, see [Manage User Files](Manage-User-Files.md). - -## Security in a MultiPoint Services system -As an administrative user of your MultiPoint Services system, become familiar with the security and safe computing capabilities in Windows. These include Windows automatic updating and support for firewalls, virus protection, and spyware and other malware protection. - -Shared computing resources, such as a MultiPoint Services system, may be prone to security threats due to the potentially large number of users of the system and the easy access to station hardware devices and wires. A malicious user may attempt to insert a keystroke logger or similar device at a MultiPoint Services station hub. If you see devices attached to any ports on your MultiPoint Services system that you do not recognize, consider it suspect and follow the security escalation guidelines of your organization. - -## See Also -[Manage User Files](Manage-User-Files.md) -[Managing Your MultiPoint Services System](Managing-Your-MultiPoint-Services-System.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Project-a-Station-to-Other-Stations.md b/WindowsServerDocs/remote/multipoint-services/Project-a-Station-to-Other-Stations.md deleted file mode 100644 index 90214f8067..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Project-a-Station-to-Other-Stations.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Project a Station to Other Stations -description: Learn how to share a desktop from one system to another in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Project a Station to Other Stations -As a MultiPoint Dashboard User, you can project your desktop to a single user's station or all users' (non-administrator) stations. This feature is useful when you want to demonstrate a task to a user or set of users. - -## To project your desktop to a standard user's station - -1. In MultiPoint Dashboard, click the thumbnail image of the desktop to which you want to project your station. -2. On the **Home** tab, click **Your Desktop**, and then click **Project Your Desktop to Selected Desktop(s)**. -3. To end the projection, click **Stop** (either on the **Projection** tab or in the right-hand corner below the ribbon). - -## To project your desktop to all stations - -1. In MultiPoint Dashboard, on the **Home** tab, click **Your Desktop**, and then click **Project Your Desktop to All Desktop(s)**. - -2. To end the projection, click **Stop** (either on the **Projection** tab or in the right-hand corner below the ribbon). - -## To project a different desktop to all desktops - -1. Click the thumbnail image of the desktop you want to project to all desktops. - -2. On the **Home** tab, click **Selected Desktop**, and then click **Selected Desktop**. The selected desktop is displayed on all desktops. - -3. To end the projection, click **Stop** (either on the **Projection** tab or in the right-hand corner below the ribbon). diff --git a/WindowsServerDocs/remote/multipoint-services/Protecting-the-System-Volume-with-Disk-Protection.md b/WindowsServerDocs/remote/multipoint-services/Protecting-the-System-Volume-with-Disk-Protection.md deleted file mode 100644 index f3fd914236..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Protecting-the-System-Volume-with-Disk-Protection.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Protecting the System Volume with Disk Protection -description: Provides information about disk protection for MultiPoint Services -ms.date: 07/22/2016 -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe ---- -# Protecting the System Volume with Disk Protection -MultiPoint Services provides the option to instantly erase any changes to the system volume each time the computer is started. If you enable the Disk Protection feature, any modifications to the drive, such as configuration corruption or the introduction of malware, are undone the next time the computer restarts. This is a convenient feature for administrators who want to ensure that a known "good" or "golden" software image is loaded every time. Automatic updates or software patching can be scheduled, for example, in the middle of the night. The planning consideration is whether you want to have end users be able to make changes, such as installing software, from the Internet. With this feature enabled, if you want users to be able to store files, the file share will need to be outside of the system volume. - diff --git a/WindowsServerDocs/remote/multipoint-services/Remap-All-Stations.md b/WindowsServerDocs/remote/multipoint-services/Remap-All-Stations.md deleted file mode 100644 index c60a245b88..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Remap-All-Stations.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Remap All Stations -description: Learn how to remap stations in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Remap All Stations -Remapping stations allows you to associate keyboards and mice to monitors. When you remap all stations, the original settings, such as name and auto-logon information, are erased. All local user stations are suspended while the remapping takes place. - -1. Open MultiPoint Manager in station mode, and then click the **Home** tab. -2. Under **Tasks**, click **Remap all stations**. -3. Follow the instructions on the station screens to associate the keyboards to the stations in your system. diff --git a/WindowsServerDocs/remote/multipoint-services/Remap-Selected-MultiPoint-Systems.md b/WindowsServerDocs/remote/multipoint-services/Remap-Selected-MultiPoint-Systems.md deleted file mode 100644 index e44c2ca511..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Remap-Selected-MultiPoint-Systems.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Remap Selected MultiPoint Systems -description: Learn how to remap some but not all systems in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Remap Selected MultiPoint Systems -Remapping stations in MultiPoint Dashboard allows you to associate keyboards and mice to monitors. Local user stations are suspended while a MultiPoint Services system is remapped. - -> [!CAUTION] -> Remapping is commonly used for troubleshooting purposes. Station settings, such as name and auto\-logon information, are erased during the remapping process. - -#### To remap a MultiPoint Services system - -1. In MultiPoint Services, click the **Systems** tab. - -2. Click the thumbnail image of the server you want to remap, and then, on the **Hardware** tab, click **Remap Selected System**. diff --git a/WindowsServerDocs/remote/multipoint-services/Restart-or-Shut-Down-MultiPoint-Systems.md b/WindowsServerDocs/remote/multipoint-services/Restart-or-Shut-Down-MultiPoint-Systems.md deleted file mode 100644 index 78bcfc54d3..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Restart-or-Shut-Down-MultiPoint-Systems.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Restart or Shut Down MultiPoint Systems -description: Learn how to shut down or restart one or more systems -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Restart or Shut Down MultiPoint Systems -You can restart or shut down one MultiPoint Services system or multiple MultiPoint Services systems in MultiPoint Dashboard. - -## Restart a MultiPoint Services system or multiple systems - -1. Click **Systems**. - -2. Click the thumbnail image of the server you want to restart, and then, on the **Hardware** tab, click **Restart**. - -## To shut down a MultiPoint Services system or multiple systems - -1. Click the **Systems** tab. - -2. Click the thumbnail image of the server you want to restart, and then, on the **Hardware** tab, click **Shut Down**. diff --git a/WindowsServerDocs/remote/multipoint-services/Restart-or-Shut-Down.md b/WindowsServerDocs/remote/multipoint-services/Restart-or-Shut-Down.md deleted file mode 100644 index e1b57c30b9..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Restart-or-Shut-Down.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Restart or Shut Down -description: Learn how to restart or completely shut down a system in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Restart or Shut Down -You might have to restart the host computer and all of the *stations* in your MultiPoint Services system if instructed after you install hardware, software, and software updates. If you have added new hardware devices to a station, you might also want to associate the hardware devices to that station. For more information about how to *associate stations*, see the [Switch Between Modes](Switch-Between-Modes.md) topic. - -To turn off your MultiPoint Services system's computer safely, the computer must perform a shutdown process that closes any open programs, shuts down Windows, and turns off your computer and its associated *stations*. Do not just unplug or press the **Power** button to turn off your computer. You should shut down your computer at the end of the day and when you must install new hardware enclosed in the computer case. If you add other hardware to the system, you may also need to shut down or restart the server. - -> [!NOTE] -> Before you restart or shut down the computer that is running MultiPoint Services, all user *sessions* must have ended. - -## Restart the computer - -1. End all user sessions. For more information about ending user sessions, see the [End a User Session](End-a-User-Session.md) topic. - -2. In MultiPoint Manager, click **Home**, and then click **Restart the computer**. - -## Shut down the computer - -1. End all user sessions. For more information about ending user sessions, see the [End a User Session](End-a-User-Session.md) topic. - -2. In MultiPoint Manager, click the **Home** tab, and then click **Shut down the computer**. - -## See Also -[End a User Session](End-a-User-Session.md) -[Manage System Tasks Using MultiPoint Manager](Manage-System-Tasks-Using-MultiPoint-Manager.md) -[Switch Between Modes](Switch-Between-Modes.md) -[Log off or Disconnect User Sessions](Log-off-or-Disconnect-User-Sessions.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Save-Connection-Settings-to-File.md b/WindowsServerDocs/remote/multipoint-services/Save-Connection-Settings-to-File.md deleted file mode 100644 index 84befb1fce..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Save-Connection-Settings-to-File.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Save Connection Settings to File -description: Learn how to create connection files to use to connect from one computer to another in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Save Connection Settings to File -Using Remote Desktop, you can connect to a MultiPoint Services system from another computer. If the remote computer supports Remote Desktop Protocol, the connection to the computer can be established automatically. - -There are three types of connection files you can create: - -- **MultiPoint Manager connection file**: Allows MultiPoint Manager to be run on another computer as a remote application. - -- **MultiPoint Dashboard connection file**: Allows MultiPoint Dashboard to be run on another computer as a remote application. - -- **Remote station connection file**: Allows another computer to connect to the MultiPoint Services system as a remote station. - -## To save system connection settings to a file - -1. Open MultiPoint Manager in station mode, and then click the **Home** tab. - -2. In the **Computer** column, click the name of the computer for which you want to save the connection settings to a file. - -3. Under *computer name***Tasks**, click **Save connections to file**. The **Save Connection Settings to File** page is displayed. - -4. Choose the type of connection file you want to create, and then click **OK**. - -5. Choose the folder where you want to save the file, edit the **File name** if preferred, and then click **Save**. diff --git a/WindowsServerDocs/remote/multipoint-services/Save-and-Share-Files-on-a-USB-Flash-Drive.md b/WindowsServerDocs/remote/multipoint-services/Save-and-Share-Files-on-a-USB-Flash-Drive.md deleted file mode 100644 index e08d0bb39b..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Save-and-Share-Files-on-a-USB-Flash-Drive.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Save and Share Files on a USB Flash Drive -description: Learn how to save filese to a USB flash drive in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Save and Share Files on a USB Flash Drive -In addition to being able to share content using Public folders in Windows Explorer, you can also share content using a USB storage device, such as a USB flash drive or mass storage device. When you attach a USB storage device directly to the host computer or to a USB hub that is not a station hub, that storage device will appear as a removable storage device to all users, *standard users* and *administrative users*, across the MultiPoint Services system. - -You can also use a removable storage device to save and store private documents in a private folder in Windows Explorer, such as the **My Documents** folder in the **Documents** library. - - > [!NOTE] - > The Dashboard user can block the usage of USB storage. For more information, see [Block or Unblock USB Storage](Block-or-Unblock-USB-Storage.md). - -## To share content that is stored directly on a removable storage device - -1. Connect the removable storage device to an open USB port on the host computer or a USB hub that is not a *station hub* in the MultiPoint Services system. -2. Instruct users at other *stations* to navigate to and open the removable storage device drive in Windows Explorer. Likewise, other users can share content with you from their own removable storage devices the same way. - -## To share content that is stored on a removable storage device by using Public folders - -1. Connect the removable storage device to an open USB port on the host computer or a USB hub that is not a *station hub* in the MultiPoint Services system. -2. Copy the content you want to share to a public folder in Windows Explorer, such as **Public Documents** in the **Documents** library. - -## To privately work with content that is stored on a USB storage device - -Connect the removable storage device to an open USB port on your station hub. - -## See Also -[Keep Files Private](Keep-Files-Private.md) -[Share Files](Share-Files.md) -[Manage User Files](Manage-User-Files.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Set-Up-a-Station.md b/WindowsServerDocs/remote/multipoint-services/Set-Up-a-Station.md deleted file mode 100644 index 5b9a92b210..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Set-Up-a-Station.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Set Up a Station -description: Learn how to set up a a station in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Set Up a Station -A MultiPoint Services *station* typically consists of a *station hub*, mouse, keyboard, and video monitor. This topic describes how to connect the hardware devices to the station hub to create a MultiPoint Services station. - -The station hub is a hardware device that connects peripheral devices to a computer in a MultiPoint Services system. MultiPoint Services supports two types of station hubs: - -- **USB Hub:** A generic multiport USB expansion hub that complies with the universal serial bus 2.0 or later specifications. Such hubs typically have two, four, or more USB ports that allow for multiple USB devices to be connected to a single USB port on the computer. USB hubs are commonly separate devices that may be externally powered or bus-powered. When used as a station hub with MultiPoint Services, we recommend that you use a hub with four or more ports. - - > [!IMPORTANT] - > If you plan to connect USB devices other than a keyboard and mouse to the hub, we recommend that you use an externally powered hub for best performance. - -- **Multifunction Hub:** An expansion hub that connects to the computer via a USB port, and enables the connection of a variety of non-USB devices to the hub, including a video monitor. Multifunction hubs are produced by specific hardware manufacturers and may require the installation of a device-specific driver. - -If you want to add a station to your MultiPoint Services system, first make sure that you have enough connection ports available for the station hardware that you want to use. In addition, you must secure the appropriate number of *client access licenses (CALs)* for your MultiPoint Services system. - -## Setting up station hardware -The procedures in this section describe how to connect MultiPoint Services station hardware to the different types of station hubs. - -### To set up a station with a USB hub - -1. Before you can connect a new station, *end* all user *sessions*, and then shut down the computer and other powered devices in your MultiPoint Services system. - -2. Connect the new video monitor cable to the video display port on the computer, as shown in the following illustration: - - ![Image of Video connection to USB hub-based system](./media/WMSVideoConnection.gif) - -3. Connect the new USB hub to an open USB port on the computer: - - ![Image of MultiPoint Server USB hub connection](./media/WMSUSBHubConnection.gif) - -4. Connect a keyboard and mouse to the USB hub: - - ![Image of USB hub input device connections](./media/WMSUSBDeviceConnection.gif) - -5. Connect the power cord of the video monitor to a power outlet. - -6. Turn on the computer. - -7. MultiPoint Services starts. Follow the instructions that appear on the new station's video monitor to associate the devices to the new station. - -### To set up a station with a multifunction hub - -1. Before you can connect a new station, end all user sessions, and then shut down the computer and other powered devices in your MultiPoint Services system. - -2. Connect the new video monitor cable to the DVI or VGA video display port on the multifunction hub, as shown in the following illustration: - - ![Image of multifunction hub and video connection](./media/WMSMultifunctionHubVideoConnection.gif) - -3. Connect the new multifunction hub to an open USB port on the computer: - - ![Image of a multifunction hub connection](./media/WMSMultifunctionHubConnection.gif) - -4. Connect a keyboard and mouse to the PS2 or USB connectors on the multifunction hub: - - ![Image of multifunction hub and PS2 connectors](./media/WMSMultifunctionHubPS2Connection.gif) - -5. Connect the power cord of the video monitor to a power outlet. - -6. Turn on the computer. - -7. MultiPoint Services starts. If prompted, follow the instructions that appear on the new station's video monitor to *associate* the devices to the new station. - -## See Also -[End a User Session](End-a-User-Session.md) -[Restart or Shut Down](Restart-or-Shut-Down.md) -[Manage Station Hardware](Manage-Station-Hardware.md) -[Work with USB Devices](Work-with-USB-Devices.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Set-up-a-Station-for-Automatic-Logon.md b/WindowsServerDocs/remote/multipoint-services/Set-up-a-Station-for-Automatic-Logon.md deleted file mode 100644 index 64d0a56f75..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Set-up-a-Station-for-Automatic-Logon.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Set up a Station for Automatic Logon -description: Learn how to configure automatic logon for MultiPoint Services stations -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Set up a Station for Automatic Logon -Auto-logon enables each station to be automatically logged on when the computer that is running MultiPoint Services starts, and display the desktop. An administrative user can set this feature for individual stations or for all stations. - -1. Open MultiPoint Manager in station mode, and then click the **Stations** tab. - -2. Click the name of the station you want to automatically log on. - -3. Under **Tasks**, click **Configure station**. The **Configure Stations** page opens. - -4. Select **Auto-logon using the following information**, and then enter a **User account** name. - -5. Enter the password for the user account, and then re-enter the password to confirm it. - -6. Click **OK**. The page closes. The account name is displayed in the **Auto-logon** column. - -## See Also -[Manage User Stations](Manage-User-Stations.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Set-up-a-USB-zero-client-connected-station-in-MultiPoint-services.md b/WindowsServerDocs/remote/multipoint-services/Set-up-a-USB-zero-client-connected-station-in-MultiPoint-services.md deleted file mode 100644 index 95275b6d12..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Set-up-a-USB-zero-client-connected-station-in-MultiPoint-services.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Set up a USB zero client-connected station in MultiPoint Services -description: Learn how to create a USB zero client station in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Set up a USB zero client-connected station in MultiPoint Services -When you use USB zero clients to create MultiPoint Services stations, the monitor for each station is connected to the video port on the USB zero client, as shown in the following illustration. For more information about this and other station types, see [MultiPoint Stations](MultiPoint-services-Stations.md). - -**MultiPoint Services system with one direct-video-connected station and two USB zero client-connected stations** - -![USB zerio-client connected stations](./media/WMS11_diagram7.gif) - -> [!IMPORTANT] -> Before you set up USB zero client-connected stations, be sure to install the latest drivers for your video cards and the USB zero client. Outdated drivers can prevent the MultiPoint Services configuration from completing successfully. For instructions, see [Update and install device drivers if needed](Update-and-install-device-drivers-if-needed.md). - -> [!IMPORTANT] -> If you are using a USB-over-Ethernet zero client, follow the instructions from your vendor, instead of this procedure, to use the Ethernet connection to set up the device on the network. - -### To set up a USB zero client-connected station - -1. Connect the video monitor cable to the DVI or VGA video display port on the USB zero client, as shown in the following illustration. - - ![Image of Video connection to USB hub-based system](./media/WMSVideoConnection.gif) - -2. Connect the USB zero client to an open USB port on the computer. - - ![Image of MultiPoint Services USB hub connection](./media/WMSUSBHubConnection.gif) - -3. Connect a keyboard and mouse to the USB zero client. - - ![Image of USB hub input device connections](./media/WMSUSBDeviceConnection.gif) - -4. If you are using an externally powered USB zero client, connect the power cord of the USB zero client to a power outlet. - -5. Connect the power cord of the video monitor to a power outlet. - -6. If you are prompted to associate devices with the station, follow the instructions on the monitor to complete the setup. (Generally, USB zero client-connected stations are associated with stations automatically as you add them to the server.) diff --git a/WindowsServerDocs/remote/multipoint-services/Set-up-a-direct-video-connected-station-in-MultiPoint-services.md b/WindowsServerDocs/remote/multipoint-services/Set-up-a-direct-video-connected-station-in-MultiPoint-services.md deleted file mode 100644 index 64b770ca36..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Set-up-a-direct-video-connected-station-in-MultiPoint-services.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Set up a direct-video-connected station in MultiPoint Services -description: Learn how to create a direct-video-connected station in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Set up a direct-video-connected station in MultiPoint Services -On a direct video-connected station, the monitor is connected directly to a video port on the MultiPoint Server computer. A keyboard and mouse are then connected to a USB hub, and are associated with the monitor. - -The following illustration shows a MultiPoint Server environment that has a single MultiPoint Server computer and four direct-video-connected stations. For more information, see [MultiPoint Server Stations](MultiPoint-services-Stations.md). - -**MultiPoint Services system with four direct video connections** - -![Image of MultiPoint Services USB-based system layout](./media/WMSMultiPointServerUSBSystemLayout.gif) - -> [!NOTE] -> To configure a direct-video-connected station, you must use a Latin keyboard (such as an English or Spanish language keyboard). - -## To set up a direct video-connected station - -1. Connect the monitor cable to the video display port on the computer, as shown below. - - ![Image of Video connection to USB hub-based system](./media/WMSVideoConnection.gif) - -2. Connect the power cord of the video monitor to a power outlet. - -3. Connect a USB hub to an open USB port on the computer, as shown below. - - ![Image of MultiPoint Services USB hub connection](./media/WMSUSBHubConnection.gif) - -4. Connect a keyboard and mouse to the USB station hub. - - ![Image of USB hub input device connections](./media/WMSUSBDeviceConnection.gif) - -5. Connect any additional peripherals, such as headphones, to the USB hub. - -6. If you are using an externally powered hub, connect the power cable of the hub to a power outlet. - - > [!IMPORTANT] - > We strongly recommend the use of a powered hub. Erratic system behavior can result from under-current conditions. - > - > Users should not attach mice and keyboards directly to the USB ports of the computer. Doing so is likely to cause the incorrect association of multiple keyboards and mice to the same station, or to no station at all. - -7. Follow the instructions that appear on the monitor to create the station. - -If you add more than one direct video-connected station to your MultiPoint Services environment, the primary station might change. You can easily find out which direct video connected station is your primary station. - -## To find out which direct video-connected station is the primary station - -1. Turn on all monitors that are connected directly to the computer's display adapters (video cards). - -2. Start (or restart) the MultiPoint Services computer, and see which monitor displays the startup screens. That station is the primary station. - - > [!NOTE] - > In some cases, BIOS startup information is displayed on multiple monitors simultaneously. In that case, any of the monitors can be considered the "primary station" for the purpose of accessing the BIOS. diff --git a/WindowsServerDocs/remote/multipoint-services/Set-up-a-split-screen-station-in-multipoint-services.md b/WindowsServerDocs/remote/multipoint-services/Set-up-a-split-screen-station-in-multipoint-services.md deleted file mode 100644 index 24b1b873f2..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Set-up-a-split-screen-station-in-multipoint-services.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Set up a split-screen station -description: Describes how to set up MultiPoint Services so two users can share a single system -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Set up a split-screen station -You can set up a split-screen station so two users can simultaneously use the system. - -Any monitor that has a resolution of minimum 1200 x720, when connected to a station that supports the split-screen feature, can be split into two stations. After a station is split, the desktop that the monitor had displayed moves to the left half of the screen, and a new station is displayed on the right half of the screen. To finish creating the new station, you will need to map a keyboard, mouse, and USB hub to the station. After a station is split, a user can log on to the left station while another user logs on to the right station. - -Split-screen stations have several benefits: - -- You can reduce cost and space by accommodating more users on a MultiPoint Services system. - -- Two users can collaborate together, side by side, on a project. - -- A MultiPoint Dashboard user can demonstrate a procedure on one station while a student follows along on the other station. - -The following illustration shows a MultiPoint Services system with a split screen station (on the right). - -![Split-screen stations](./media/WMS_diagram3.gif) - -## Requirements for a split screen station -To create a split-screen station, the monitor and station must meet these requirements: - -- The monitor must have a resolution of 1200 x720 or higher. - -- If you are using a USB-over-Ethernet zero client, check with your hardware vendor to find out whether split-screen stations are supported. Many USB-over-Ethernet zero client devices have limitations that prevent their configuration as split-screen stations. - -## Setting up a split-screen station -Use the following procedures to add a second hub for a split-screen station and then split the station in MultiPoint Services. The final procedure explains how to return a split-screen station to a single station. - -> [!NOTE] -> When you split a station, the active session on the station is suspended. The user must log on to the station again to resume work after the split occurs. - -**To add a second hub with keyboard and mouse:** - -1. Connect a USB hub to an open USB port on the computer, as shown in the following illustration. - - ![Image of MultiPoint server USB hub connection](./media/WMSUSBHubConnection.gif) - -2. Connect a keyboard and mouse to the USB hub. - - ![Image of USB hub input device connections](./media/WMSUSBDeviceConnection.gif) - -3. Connect any additional peripherals, such as headphones to the USB hub. - -4. If you are using an externally powered hub, connect the power cable of the hub to a power outlet. - -**To split a station:** - -1. In the MultiPoint Manager, click the **Stations** tab. - -2. Under **Station**, click the name of the station you want to split. - -3. Under **Selected Item Tasks**, click **Split station**. - - The original screen moves to the left half of the monitor, and a new station's screen is created on the right half of the same monitor. - -4. Create the new station by pressing the specified letter on the newly added keyboard as indicated when the **Create a MultiPoint Server Station** screen appears on the right half of the monitor. - -After a station is split, one user can log on to the left station while another user logs on to the right station. - -**To return a split station to a single station:** - -1. In the MultiPoint Manager, click the **Stations** tab. - -2. Under **Station**, click the name of the station you want to unsplit. - -3. Under **Selected Item Tasks**, click **Unsplit station**. diff --git a/WindowsServerDocs/remote/multipoint-services/Set-up-an-RDP-over-LAN-connected-station-in-multipoint-services.md b/WindowsServerDocs/remote/multipoint-services/Set-up-an-RDP-over-LAN-connected-station-in-multipoint-services.md deleted file mode 100644 index ef0a665a6a..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Set-up-an-RDP-over-LAN-connected-station-in-multipoint-services.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Set up an RDP-over-LAN connected station in MultiPoint Services -description: Learn how to set up an RDP-over-LAN system in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Set up an RDP-over-LAN connected station in MultiPoint Services -An RDP-over-LAN connected station is a thin client, traditional desktop, or laptop computer that connects to MultiPoint Services on a local area network (LAN) by using the Remote Desktop Protocol (RDP). For more information about this and other station types, see [MultiPoint Stations](MultiPoint-services-Stations.md). - -## To set up a MultiPoint station using a computer or thin client on a LAN - -1. Turn on the computer that is running MultiPoint Services. - -2. Ensure that the MultiPoint Server computer is connected to the LAN by a switch, router, or other networking device and has a proper IP address. (An IP address that starts with 169.254 (an APIPA address) might indicate there is an issue with the LAN connection or that the DHCP server can't be reached or is not functioning correctly.) - -3. Connect the client computer or thin client to the LAN. - -4. Turn on the client computer or thin client. - -5. On the client computer or thin client, start Remote Desktop Connection or an equivalent application, and enter the name or IP address of the computer running MultiPoint Services. - -## Set up a Windows 10 device for remote management by using Connector Services -Any PC or laptop running Windows 10 can be managed remotely as long as: -- the Connector Services have been enabled -- the machine has been added to managed computers on the MultiPoint server. - -On the PC running Windows 10 follow these steps to enable MultiPoint Connector: - -1. In the search box, type "Turn Windows features on or off" and select the proper search result. - -2. In the list of features enable **MultiPoint Connector**. This will enable MultiPoint connector services which are needed to manage the device. - -On the MultiPoint server: -1. Open MultiPoint Manager and select either **Add or remove personal computers** or **Add or remove MultiPoint Services**. - -2. Select the remote computers you want to manage and click **OK**. You will be prompted for admin credentials on the remote machines. Once this is done, you will see the remote machines on the MultiPoint Manager home tab. - -When successfully set up Dashboard Manager can monitor users working on the managed device. - -> [!IMPORTANT] -> When monitoring managed Windows 10 devices administratrive users cannot be monitored except the server settings have been changed accordingly. See [Edit Server Settings](Edit-Server-Settings.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Set-up-the-physical-computer-and-primary-station.md b/WindowsServerDocs/remote/multipoint-services/Set-up-the-physical-computer-and-primary-station.md deleted file mode 100644 index 8916d76865..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Set-up-the-physical-computer-and-primary-station.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Set up the physical computer and primary station -description: Learn how to set up your first system, the primary station, in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Set up the physical computer and primary station -Before you install MultiPoint Services, you need to set up the primary station for your MultiPoint Services system. If you will use a local area network (LAN) connect the computer to the LAN. - -A *station* is an endpoint by which MultiPoint Services is accessed. The *primary station* is the first station to start when MultiPoint Services is started. Administrators can use it to access startup menus and settings. The primary station provides access to system configuration and troubleshooting information that is only available during startup and before the MultiPoint Services system is running. After startup, you can use the primary station as you would any other station. - -The primary station must be a direct-video-connected station. The following procedure describes how to connect the needed hardware to your MultiPoint Services computer. - -For more information about stations, see [MultiPoint Stations](multipoint-services-stations.md). For help with making hardware selections, see [Selecting Hardware for Your MultiPoint Services System](./select-hardware-mps.md). For information about connecting other stations types to MultiPoint Services, see [Attach additional stations to your MultiPoint Services computer](./multipoint-attach-additional-stations.md). - -> [!NOTE] -> To create a video-connected station, you must use a Latin keyboard (such as an English- or Spanish-language keyboard). - -## To set up your primary station - -1. Ensure that the computer running MultiPoint Services is turned off and unplugged. - -2. Connect the power cord of the monitor to a power outlet, and connect the monitor cable to the video display port on the computer, as shown below. - - ![Image of Video connection to USB hub-based system](./media/WMSVideoConnection.gif) - -3. If the station will use a USB keyboard and mouse, complete the following steps: - - 1. Connect an external USB hub to an open USB port on the computer, as shown below. - - ![Image of MultiPoint Services USB hub connection](./media/WMSUSBHubConnection.gif) - - 2. Connect the USB keyboard and mouse to the USB hub. - - ![Image of USB hub input device connections](./media/WMSUSBDeviceConnection.gif) - - > [!NOTE] - > If your MultiPoint Services computer has PS/2 ports, you can, if needed, use a PS/2 keyboard and mouse plugged directly into the computer. However, this setup has significant limitations. Users cannot use audio devices, web cams, and flash drives on PS/2 stations. - - 3. If you are using an externally powered hub, connect the power cable of the hub to a power outlet. - - > [!IMPORTANT] - > We strongly recommend the use of a powered hub. Erratic system behavior can result from under-current conditions. - > - > Users should not attach mice and keyboards directly to the USB ports of the computer. Doing so is likely to cause the incorrect association of multiple keyboards and mice to the same station, or to no station at all. - - > [!NOTE] - > The host audio device on the system's motherboard is only available while MultiPoint Services is in console mode. To ensure uninterrupted audio for a station that uses an external USB hub, you must use a USB audio device plugged into the hub. - -## To connect the computer to the LAN - -- If you have a LAN, connect your computer to your network with a network cable. diff --git a/WindowsServerDocs/remote/multipoint-services/Share-Files.md b/WindowsServerDocs/remote/multipoint-services/Share-Files.md deleted file mode 100644 index b5c1aa5125..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Share-Files.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Share Files -description: Learn how to share files in MultiPoint Services by using shared folders and the network -ms.topic: how-to -author: dknappettmsft -ms.date: 08/04/2016 -ms.author: daknappe ---- -# Share Files -You can share content with other MultiPoint Services users by storing the content in a public folder in Windows Explorer. All content that is stored in public folders in Windows Explorer in a MultiPoint Services system is accessible to all users on the MultiPoint Services system. - -You can also share content by storing it on removable storage devices, as described in [Save and Share Files on a USB Flash Drive](Save-and-Share-Files-on-a-USB-Flash-Drive.md). - -For information about keeping content private, see [Keep Files Private](Keep-Files-Private.md). - -## To share content with other users by using Public folders - -Share content with other users by storing it in the **Public Documents**, **Public Music**, and other public folders in Windows Explorer libraries. - -You can also share files across multiple computers that are running MultiPoint Services on a network by creating a new folder, and then sharing it. - -## To share files across multiple computers in a MultiPoint Services network - -1. Right-click on a desktop, and then click **New**. - -2. Click **Folder**, and then type a name for the folder. - -3. Double-click the folder to open it. - -4. Click **Share with**, and then click **Specific people**. - -5. Select specific users, or click **Everyone**. - -## See Also -[Manage User Files](Manage-User-Files.md) -[Save and Share Files on a USB Flash Drive](Save-and-Share-Files-on-a-USB-Flash-Drive.md) -[Keep Files Private](Keep-Files-Private.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Show-All-Stations.md b/WindowsServerDocs/remote/multipoint-services/Show-All-Stations.md deleted file mode 100644 index e5e585d1be..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Show-All-Stations.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Show All Stations -description: Learn how to view all stations in MultiPoint Services -ms.date: 07/07/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Show All Stations -As an administrator on the MultiPoint Services system, you may want to view all of the stations that are connected to your system, including non\-active or logged off stations. For example, per your license agreement, you may need to check the number of stations that are connected the MultiPoint Services system. You can view this information using MultiPoint Manager. - -1. In normal mode, click the **Desktops** tab. - -2. Under **General Tasks**, click **Show all stations**. diff --git a/WindowsServerDocs/remote/multipoint-services/Split-a-User-Station.md b/WindowsServerDocs/remote/multipoint-services/Split-a-User-Station.md deleted file mode 100644 index 34cb358270..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Split-a-User-Station.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Split a User Station -description: Learn how to split a display in MultiPoint Services so two users can use the same station -ms.date: 07/08/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Split a User Station -Any MultiPoint Services station monitor that has a resolution greater than 1024x768 can be split into two stations using the **Split station** task on the **Stations** tab. The desktop that is present on the monitor at the time that the split occurs moves to the left half of the monitor, and a new station is created on the right half of the same monitor. The new station must be mapped to a keyboard, mouse, and USB hub to complete its creation. After a station is split, a user can log on to the left station while another user logs on to the right station. - -Benefits of using a split-screen station may include: - -- Reducing cost and space by accommodating more students on a MultiPoint Services system - -- Allowing two students to collaborate together, side-by-side on a project - -- Allowing a teacher to demonstrate a procedure on one station while a student follows along on the other station - -> [!NOTE] -> When you split a station, the active session on the station is suspended. The user must log on to the station again to resume work after the split has occurred. - -**To split a station:** - -1. In MultiPoint Manager, in station mode, click the **Stations** tab. - -2. In the **Station** column, click the name of the station you want to split. - -3. Under **Stations Tasks**, click **Split station**. - -**To return a split station to a single station:** - -1. In MultiPoint Manager, in station mode, click the **Stations** tab. - -2. In the **Station** column, click the name of the station for which you want to end a split. - -3. Under **Stations Tasks**, click **Unsplit station**. - -## See Also -[Manage User Stations](Manage-User-Stations.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Storing-Files-with-MultiPoint-services.md b/WindowsServerDocs/remote/multipoint-services/Storing-Files-with-MultiPoint-services.md deleted file mode 100644 index c625c4664f..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Storing-Files-with-MultiPoint-services.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Storing Files with MultiPoint Services -description: Learn about file storage in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe ---- -# Storing Files with MultiPoint Services -MultiPoint Services supports storing user files in the following ways: - -- **On the operating system partition of the hard disk drive.** By default, MultiPoint Services stores user files on the hard disk drive with the operating system. - -- **On a separate partition of the hard disk drive.** When the MultiPoint Services system is set up for the first time, you can *partition* the hard disk drive. That is, you can configure a section of the drive so that it functions as if it were a separate drive. This makes it easier to restore or upgrade the operating system without affecting user files. For more information, see [Create a partition or logical drive](/previous-versions/windows/it-pro/windows-server-2003/cc727978(v=ws.10)) in the Windows Server Technical Library. - -- **On an additional internal or external hard disk drive.** You can attach additional internal or external hard disk drives to MultiPoint Services for saving and backing up data. - -- **In a shared network folder.** To make user files available from any station, you can create a shared folder on the network. This requires another computer or server in addition to the computer running MultiPoint Services. This is the recommended method for storing files if there is a file server available. - - For small systems of 2-3 computers running MultiPoint Services with no file server available, one of the MultiPoint Services computers can act as the file server for all of the MultiPoint Services computers. You would then create user accounts for all users on the MultiPoint Services that is acting as the file server. diff --git a/WindowsServerDocs/remote/multipoint-services/Suspend-and-Leave-User-Session-Active.md b/WindowsServerDocs/remote/multipoint-services/Suspend-and-Leave-User-Session-Active.md deleted file mode 100644 index f4ac0b8afb..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Suspend-and-Leave-User-Session-Active.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Suspend and Leave User Session Active -description: Learn how to suspend a user from a MultiPoint session without disconnecting them -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Suspend and Leave User Session Active -You can disconnect or suspend users from the MultiPoint Services system when you do not want to end the users' sessions. A user can also disconnect the session, rather than you disconnecting the session for them. While a user session is suspended, the session remains active in the MultiPoint Services system's computer memory until the computer is shut down or restarted. At that time, all suspended sessions are ended and any unsaved work is lost. - -1. Open MultiPoint Manager in station mode, and then click the **Stations** tab. - -2. In the **Computer** column, click name of the computer whose sessions you want to suspend. - -3. Under **Stations Tasks**, click **Suspend all stations**. - -After a user session has been suspended, the user can log on to the same or another station and continue to work in the original session. - -## See Also -[Manage User Desktops](manage-user-desktops-using-multipoint-dashboard.md) -[Log off or Disconnect User Sessions](Log-off-or-Disconnect-User-Sessions.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Switch-Between-Modes.md b/WindowsServerDocs/remote/multipoint-services/Switch-Between-Modes.md deleted file mode 100644 index c758ffa66d..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Switch-Between-Modes.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Switch Between Modes -description: Learn how to switch between station and console mode in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Switch Between Modes -MultiPoint Manager includes the following modes to help you perform different types of MultiPoint Services system management: - -- *Station mode*: By default, the MultiPoint Services system starts in station mode. While in station mode, the MultiPoint Services stations behave as if each station is a separate computer that is running Windows, and multiple users can use the system at the same time. You and your users can share files and perform the work that you must do. - -- *Console mode*: When the MultiPoint Services system is in console mode, you can install and update software and drivers or perform other maintenance tasks. When the system is in console mode, no *stations* are available for use by other computer users. Such stations are not displayed in MultiPoint Manager. All monitors directly connected to the server are treated as displays of this computer system. - -> [!NOTE] -> You can enforce the system starting in Console mode by changing the default in the settings for the server. -> ## To switch from station mode to console mode - -1. Open MultiPoint Manager in station mode, and then click the **Home** tab. - -2. In the **Computer** column, click the computer for which you want to change modes. - -3. Under *computer name* **Tasks**, click **Switch to console mode**. The computer restarts and all stations become unavailable. - -## To switch from console mode to station mode - -1. Open MultiPoint Manager in console mode, and then click the **Home** tab. - -2. In the **Computer** column, click the computer for which you want to change modes. - -3. Under *computer name* **Tasks**, click **Switch to station mode**. The computer restarts and all stations become available. - -## See Also -[Manage System Tasks Using MultiPoint Manager](Manage-System-Tasks-Using-MultiPoint-Manager.md) diff --git a/WindowsServerDocs/remote/multipoint-services/System-administration-in-multipoint-services.md b/WindowsServerDocs/remote/multipoint-services/System-administration-in-multipoint-services.md deleted file mode 100644 index 0f9e7f9bf3..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/System-administration-in-multipoint-services.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: System administration in MultiPoint Services -description: Navigational topic for administration information for MultiPoint Services -ms.date: 07/22/2016 -ms.topic: overview -author: dknappettmsft -ms.author: daknappe ---- -# System administration in MultiPoint Services -Before you start using your MultiPoint Services system, it's a good idea to do some basic system administration. - -Use the following information: - -[Configure Disk Protection](Configure-Disk-Protection-in-MultiPoint-services.md) -[Install Server Backup on your MultiPoint Services computer](./install-server-backup-on-multipoint.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Take-Control-of-a-User-Session.md b/WindowsServerDocs/remote/multipoint-services/Take-Control-of-a-User-Session.md deleted file mode 100644 index 8cd2fada0a..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Take-Control-of-a-User-Session.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Take Control of a User Session -description: Learn how to access and take control of another user's station in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Take Control of a User Session -As a MultiPoint Dashboard User, you can assist another user by remotely accessing his or her desktop using the Take Control feature. - -1. In MultiPoint Dashboard, on the **Home** tab, click the thumbnail image of the desktop for the user you want to assist. - -2. On the **Assist** tab, click **Take Control**. The user's desktop opens on your desktop, and then you can navigate their desktop using your keyboard and mouse. - -3. When you are finished assisting the user, click **Stop**. - - > [!NOTE] - > You may need to minimize the user's desktop to see your MultiPoint Dashboard. - -## See Also -[Manage User Desktops Using MultiPoint Dashboard](Manage-User-Desktops-Using-MultiPoint-Dashboard.md) - diff --git a/WindowsServerDocs/remote/multipoint-services/Troubleshooting.md b/WindowsServerDocs/remote/multipoint-services/Troubleshooting.md deleted file mode 100644 index bdc0bf0041..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Troubleshooting.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Troubleshooting -description: Navigational topic for troubleshooting -ms.date: 07/22/2016 -ms.topic: troubleshooting-general -author: dknappettmsft -robots: noindex,nofollow -ms.author: daknappe ---- -# Troubleshooting -View the Troubleshooting topics to help resolve problems when you are using MultiPoint Services. diff --git a/WindowsServerDocs/remote/multipoint-services/Update-and-install-device-drivers-if-needed.md b/WindowsServerDocs/remote/multipoint-services/Update-and-install-device-drivers-if-needed.md deleted file mode 100644 index 67a4cf0e96..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Update-and-install-device-drivers-if-needed.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Update and install device drivers if needed -description: Learn how to check and update device drivers in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Update and install device drivers if needed -If you are using USB zero clients or peripherals that require drivers, you should install the drivers at this time. It's a good idea also to check **Device Manager** for any driver alerts, and install drivers for those devices. - -Generally, the most current drivers are required for following types of devices: - -- USB zero clients - -- USB-over-Ethernet zero clients - -- Disk controllers - -- Network adapters - -- Sound controllers - -- USB host controllers - -- Graphic Cards - - -## To check for driver alerts in Device Manager - -1. Open the Start screen. - -2. Type **computer management**, and then click **Computer Management** in the results. - -3. In the Computer Management console tree, click **Device Manager**. - -4. In the system devices on the right, check for driver alerts that might affect MultiPoint Server. - -## To install device drivers in MultiPoint Manager - -1. To open MultiPoint Manager, search for "MultiPoint Manager," and then click **MultiPoint Manager** in the results. - -2. In MultiPoint Manager, click the **Home** tab, and then click **Switch to console mode**. - -3. To install a device driver, double click the driver file, and follow the instructions to install the driver. - -4. Repeat the preceding step to install all required drivers. - - > [!NOTE] - > If an installation requires a computer restart, you will need to switch back to console mode before you install the next driver. MultiPoint server always starts in station mode. To switch to console mode go to the **Home** tab in the MultiPoint Manager and click **Switch to console mode**. diff --git a/WindowsServerDocs/remote/multipoint-services/Update-or-Delete-a-User-Account.md b/WindowsServerDocs/remote/multipoint-services/Update-or-Delete-a-User-Account.md deleted file mode 100644 index 32726e4cef..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Update-or-Delete-a-User-Account.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Update or Delete a User Account -description: Learn how to update or delete a user in MultiPoint Services -ms.date: 07/11/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Update or Delete a User Account -If you are logged on as an administrative user on the MultiPoint Services system, you can modify any user account, including changing the level of access for an account, changing a full name and password, or deleting an account. - -1. Open MultiPoint Manager in station mode, and then click the **Users** tab. - -2. In the **User** column, click the account that you want to modify. - -3. Under *user name* **Tasks**, click the appropriate task. - - |Selected Item Task|Description| - |----------------------|---------------| - |Change full name|Allows you to change the full name for the account.| - |Change password|Allows you to change the password for this account on to the MultiPoint Services system.| - |Change level of access|Allows you to change the account type to either administrative user or standard user.| - |Delete user account|Removes the user account from the MultiPoint Services system.| - -## See Also -[Create an Administrative User Account](Create-an-Administrative-User-Account.md) -[Create a Standard User Account](Create-a-Standard-User-Account.md) -[Manage User Accounts](Manage-User-Accounts.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Use-IM.md b/WindowsServerDocs/remote/multipoint-services/Use-IM.md deleted file mode 100644 index a06fc2bd5e..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Use-IM.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Use IM -description: Learn how to use instant messaging in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Use IM -If it has been enabled in the server settings, MultiPoint Dashboard users and station users can exchange private messages over IM. - -#### To send a chat message from the MultiPoint Dashboard to a user - -1. In MultiPoint Dashboard, click the thumbnail image or images of the user you want to send a message. - -2. Click **Send** in the ribbon - an IM chat window opens. - -> [!NOTE] -> Users can IM the dashboard user by using the IM icon in the Windows taskbar. It is automatically pinned when IM is enabled in the server settings. diff --git a/WindowsServerDocs/remote/multipoint-services/User-Account-Considerations.md b/WindowsServerDocs/remote/multipoint-services/User-Account-Considerations.md deleted file mode 100644 index 64f36f5009..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/User-Account-Considerations.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: User Account Considerations -description: PRovides user account, user name, and password considerations for MultiPoint Services -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# User Account Considerations -This topic describes issues that you, as an administrative user, should consider as you create and manage user accounts. You manage user accounts in the Users tab in MultiPoint Manager. For more information, see the [Manage User Accounts](Manage-User-Accounts.md) topic. - -## User account types -A user account is a collection of information that tells MultiPoint Services which files and folders a user can access, what changes they can make to the MultiPoint Services system, and each user's preferences, such as desktop background. Each person accesses their own user account by using a unique user name and password. MultiPoint Services supports three types of user accounts: - -- **Administrative user accounts** are for individuals who will use MultiPoint Manager to use and manage the MultiPoint Services system. For more information, see [Create an Administrative User Account](Create-an-Administrative-User-Account.md). - -- **Standard user accounts** are for individuals who will regularly access stations, but will not manage the system. Typically, you should create standard user accounts for most MultiPoint Services system users. For more information, see [Create a Standard User Account](Create-a-Standard-User-Account.md). - -- **MultiPoint Dashboard user accounts** are for individuals who use the MultiPoint Dashboard to manage standard user sessions and can log on from any station. For more information, see [Create a MultiPoint Dashboard User Account](Create-a-MultiPoint-Dashboard-User-Account.md). - -## User name and password considerations -Administrative users can perform tasks that affect all other users of the MultiPoint Services system, such as install software or change security settings. For this reason, administrative users should have unique user names and passwords that are known only to them. - -One important consideration of user accounts is that each user account is allocated a unique **Documents** library in Windows Explorer that includes the **My Documents** folder. If the standard users on your MultiPoint Services system will store private documents in their **Documents** library in Windows Explorer, they too should log on to the MultiPoint Services system using a unique user name and password known only to them. For more information about storing documents in Windows Explorer, see the [Manage User Files](Manage-User-Files.md) topic. - -> [!TIP] -> For stronger system security, all users' passwords should be strong passwords. A strong password is one that cannot be easily guessed or cracked, is at least eight characters long, does not contain all or part of the user's account name, and contains at least three of the four following categories of characters: uppercase characters, lowercase characters, numbers, and symbols found on a keyboard (such as !, @, #). - -## See Also -[Create an Administrative User Account](Create-an-Administrative-User-Account.md) -[Create a Standard User Account](Create-a-Standard-User-Account.md) -[Manage User Files](Manage-User-Files.md) -[Manage User Accounts](Manage-User-Accounts.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Variables-Affecting-MultiPoint-services-System-Performance.md b/WindowsServerDocs/remote/multipoint-services/Variables-Affecting-MultiPoint-services-System-Performance.md deleted file mode 100644 index bdde542479..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Variables-Affecting-MultiPoint-services-System-Performance.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Variables Affecting MultiPoint Services System Performance -description: Performance information for MultiPoint Services -ms.date: 07/22/2016 -ms.topic: best-practice -author: dknappettmsft -ms.author: daknappe ---- -# Variables Affecting MultiPoint Services System Performance -There are many variables that can affect the overall performance of your MultiPoint Services system. You may want to consider these when designing your system. - -## Usage - -- **Applications** The type and number of applications running at the same time, especially graphic\-heavy or memory intensive applications will affect the overall performance of your system. For more information, see [Applications and Internet Content](hardware-and-performance-recommendations.md#applications-and-internet-content). - -- **Internet use** Consider if your users will be viewing multimedia content or web pages that use full-motion videos. This type of content can overload the system if too many users are viewing concurrently. - - > [!NOTE] - > The projection feature in MultiPoint Services, which allows teachers to project their screens onto their student monitors, is not designed to project full-motion video. The projection feature is designed for demonstration purposes, such as showing a procedure. - -- **High-speed devices** If too many users are concurrently using a high-speed device, like a web camera or DVD player, this affects the overall performance of the system. - -## Configuration - -- **CPU, GPU, and RAM** See [Optimize MultiPoint Services System Performance](hardware-and-performance-recommendations.md#optimize-multipoint-services-system-performance) in this guide for CPU, GPU, and RAM recommendations. -- **Network bandwidth** For RDP-over-LAN connected stations, the network bandwidth and the capability of the client (for example, a thin client, desktop PC, or laptop) is important, particularly if video is running in the user's session. If you are using USB-over-Ethernet zero clients, network bandwidth should also be a consideration. Video data for all of the devices is sent over the same Ethernet connection, so you may want to consider setting up a separate Gigabit Ethernet network when using these devices. -- **RemoteFX** For RDP-over-LAN connected stations, you may be able to use RemoteFX to greatly improve the delivery of high-definition multimedia content. -- **Display resolution** If you have heavy full-screen video usage, you may want to consider reducing the monitor resolution to maximize performance. -- **Number of USB zero clients** The total number of USB zero clients on a single root hub on the server will directly affect video performance. For more information, see [Layout for USB Zero Client Connected Stations](MultiPoint-services-Site-Planning.md#layout-for-usb-zero-client-connected-stations). The number of USB-over-Ethernet zero client stations that are supported might be slightly less than the number of USB zero clients. -- **USB bandwidth** Consider the USB bandwidth when you are designing your system. This is especially important for USB zero clients, which send video data over the USB connection. To optimize bandwidth, minimize the number of devices that are connected to a single USB port on the server. This applies to daisy chained stations and intermediate hubs. For more information, see [Station hubs](MultiPoint-services-Site-Planning.md#station-hubs) and [Intermediate hubs](MultiPoint-services-Site-Planning.md#intermediate-hubs). - -- **USB type** Using USB 3.0 instead of USB 2.0 increases the available bandwidth between the server and the intermediate hub if you are connecting more than three USB zero clients to the hub or if you are using high-bandwidth USB devices. - -- **Stations** The total number of stations affects the performance. If you have heavy graphics, processing, or video needs, you may want to limit the overall number of stations. For more information, see [Optimize MultiPoint Services System performance](hardware-and-performance-recommendations.md#optimize-multipoint-services-system-performance). diff --git a/WindowsServerDocs/remote/multipoint-services/View-Hardware-Status.md b/WindowsServerDocs/remote/multipoint-services/View-Hardware-Status.md deleted file mode 100644 index 9c82120e85..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/View-Hardware-Status.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: View Hardware Status -description: Learn how to view hardware information in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# View Hardware Status -In MultiPoint Manager, use the **Stations** tab to view *station* information, such as: - -- Station name -- Required hardware to make each station usable (typically, hardware would include a video monitor, *station hub*, keyboard, and mouse) -- Additional peripheral hardware devices associated with a station -- Notification of required hardware that is missing or not working at a station is displayed in the relevant column -- Names of users who are currently connected to the MultiPoint Services system - -> [!TIP] -> If the stations in your MultiPoint Services system are physically arranged in a way that you intend to keep (for example, around a circular table), you may find it helpful to adhere station name or number labels, such as stickers or cards, to help identify the video monitor or hub of each station. That way, you and other users of the stations can more easily refer to and distinguish stations by their unique identifying name or number. - -> [!NOTE] -> The **Stations** tab is unavailable when the system is in console mode. - -## See Also -[Manage Station Hardware](Manage-Station-Hardware.md) -[Switch Between Modes](Switch-Between-Modes.md) diff --git a/WindowsServerDocs/remote/multipoint-services/View-Options-for-Session-Thumbnails-in-MultiPoint-Dashboard.md b/WindowsServerDocs/remote/multipoint-services/View-Options-for-Session-Thumbnails-in-MultiPoint-Dashboard.md deleted file mode 100644 index a0c7d69d30..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/View-Options-for-Session-Thumbnails-in-MultiPoint-Dashboard.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: View Options for Session Thumbnails in MultiPoint Dashboard -description: Learn how to customize your view options for MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# View Options for Session Thumbnails in MultiPoint Dashboard -An easy way to monitor user activities on individual desktops is to view thumbnail images of each active desktop on your MultiPoint Services system. By default, images of desktops are displayed in MultiPoint Dashboard on the **Home** tab. - -Using MultiPoint Dashboard, you can do the following: - -- View a user's desktop more closely by enlarging its view in the dashboard. -- Change the size of the thumbnail images that are displayed in the dashboard. Three sizes are available for view: small, medium, or large. Medium is the default setting. -- View all desktops on the MultiPoint Services system, or choose a filtered view that shows active desktops. - -## To enlarge the view of a selected desktop in MultiPoint Dashboard - -1. Click the **Home** tab, and then click the desktop you want to enlarge. - -2. On the **Home** tab, click **Enlarge Selected**. The user's desktop opens in the dashboard. - -3. When you are finished with the enlarged view, click Return to Desktops View. - -## To change the size of desktop thumbnails in MultiPoint Dashboard - -1. Click the **Home** tab, and then select the desktop thumbnail you want to enlarge. - -2. On the **Home** tab, click **Enlarge Selected**. The **Change Desktop Size** page opens. - -3. Click the size you want (**Small**, **Medium**, or **Large**), and then click **OK**. - -## To show all desktops in MultiPoint Dashboard - -1. Click the **Home** tab, and then click **Show** in the ribbon under **Desktops**.. - -2. Click **All**. All desktops are displayed in the dashboard. - -3. To change back to the filtered view, click **Show**, and then click **Filtered View**. - ->[!NOTE] -> Right-click one or more thumbnails to get to additional actions you can take on active or inactive sessions, like **Log off Selected Users**. See [Log Off User Sessions](Log-Off-User-Sessions.md) for more information. - -## See Also -[Manage User Desktops Using MultiPoint Dashboard](Manage-User-Desktops-Using-MultiPoint-Dashboard.md) diff --git a/WindowsServerDocs/remote/multipoint-services/View-User-Connection-Status.md b/WindowsServerDocs/remote/multipoint-services/View-User-Connection-Status.md deleted file mode 100644 index e906d7ab3d..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/View-User-Connection-Status.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: View User Connection Status -description: Learn how to view user status in MultiPoint Services -ms.date: 07/08/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# View User Connection Status -Use the **Stations** tab to determine the status of a standard or other administrative user's connection to a MultiPoint Services station. - -Status values include the following: - -- **Logged on**: A user session that is active on a station - -- **Suspended**: A user session that is suspended, but is still active on the computer. The user's desktop session is preserved until the user logs on again - -- **Logged off**: A user who is logged off is not displayed on the **Stations** tab - -To view station status, open MultiPoint Manager in stations mode, and then click **Stations**. - -## See Also -[Manage User Desktops](manage-user-desktops-using-multipoint-dashboard.md) -[Switch Between Modes](Switch-Between-Modes.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Work-with-USB-Devices.md b/WindowsServerDocs/remote/multipoint-services/Work-with-USB-Devices.md deleted file mode 100644 index 155a1e37f7..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Work-with-USB-Devices.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Work with USB Devices -description: Learn how USB devices work with MultiPoint Services -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- - -# Work with USB Devices - -You can connect devices to either the computer in your MultiPoint Services system or to a MultiPoint station hub. The location where a device is connected, and the type of device, affects whether a device is available to all users on the system, only to individual users, or not available to any users. The following are examples of the different connection types: - -- If you connect a device directly to the computer, such as a printer or USB mass storage device, the device can be accessed by all session users on the MultiPoint Services system. Virtual desktop station users will not be able to access the devices connected directly to the computer. - -- If you connect a device to a station hub, such as a keyboard, mouse, *audio device*, or mass storage device, the device is available only to the user logged on to that MultiPoint Services station. - -- If you connect certain types of devices to the computer, such as a keyboard or mouse, the devices are not available to any users on the system. - -The following table shows a list of devices and how they behave, depending on where they are connected to the system. Information about how to connect station hubs is described in [Working with station hubs](#working-with-station-hubs). More information about how to connect video monitors to a station is described in [Work with Video Devices](Work-with-Video-Devices.md). - -| **Device** | **Behavior when it is connected directly to the computer** | **Behavior when it is connected to a station** | **Notes** | -|--|--|--|--| -| Keyboard | We do not recommend connecting a keyboard directly to the computer. | Accessible only to the station user. | If the keyboard contains a USB port, then the USB hub inside the keyboard may be the station hub. Other USB devices attached to that port are available only to user who is using that keyboard.

        Some station hubs are equipped with a PS\/2 mouse port that is converted into a USB connection inside the hub. | -| Mouse | We do not recommend connecting a mouse directly to the computer. | Accessible only to the station user. | Some station hubs are equipped with a PS\/2 mouse port that is converted into a USB connection inside the hub. | -| USB hub | See [Working with station hubs](#working-with-station-hubs). | See [Working with station hubs](#working-with-station-hubs). | | -| Video monitor | See [MultiPoint Services Video Devices](work-with-video-devices.md). | See [MultiPoint Services Video Devices](work-with-video-devices.md). | | -| Audio output devices such as headphones | We do not recommend connecting an audio output device directly to the computer. | Accessible only to the station user. | Some station hubs are equipped with an analog audio port that is converted into a USB audio connection inside the hub. | -| Audio input devices such as microphones | We do not recommend connecting an audio input device directly to the computer. | Accessible only to the station user. | Some station hubs are equipped with an analog audio port that is converted into a USB audio connection inside the hub. | -| Printers | Accessible to all users on the system.* | Accessible only to the station user. | | -| USB mass storage device | Accessible to all users on the system.\* | Accessible only to the station user. | These devices include USB flash drives, external hard disk drives, and digital cameras. | -| Web cameras | Accessible to all users on the system.* | Accessible only to the station user. | Only one user can connect to the camera at a time. | - -*Devices that are connected to the host computer are not visible to the users who are logged on to virtual desktop stations. - -For more information about how to set up a station, see [Set Up a Station](Set-Up-a-Station.md). - -### Working with station hubs -There are four scenarios for how a USB hub can be used when it is connected to a MultiPoint Services system. Each of the following scenarios provides different access to the devices that are connected to it, depending on the type of hub and where it is connected to the system. - -- A station hub connected to the computer in your MultiPoint Services system with a keyboard attached can be used to create a MultiPoint Services station. A keyboard and mouse are connected to the station hub using the ports that are available on the hub. A video monitor is connected to a video port on the computer or to a video adapter on the station hub, if available. The keyboard, mouse, and monitor are then *associated* with a MultiPoint Services station. - -- A USB hub connected to the computer in your MultiPoint Services system with no keyboard attached can be used to connect additional devices to the computer when there are not enough ports on the computer for the required devices. All devices connected to this USB hub are available to all users of the MultiPoint Services system. This is not considered a MultiPoint Services station hub. - -- A powered USB hub connected to the computer in your MultiPoint Services system, also known as an intermediate hub, can be used to connect additional USB hubs that are used to create MultiPoint stations. - -- A USB hub connected to a station hub can be used to connect additional devices to the station hub. Keyboards must be connected directly to the station hub. - -For more information about how to set up a MultiPoint Services station, see [Set Up a Station](Set-Up-a-Station.md). - -## See Also -[Work with Video Devices](Work-with-Video-Devices.md) -[Manage Station Hardware](Manage-Station-Hardware.md) -[Set Up a Station](Set-Up-a-Station.md) diff --git a/WindowsServerDocs/remote/multipoint-services/Work-with-Video-Devices.md b/WindowsServerDocs/remote/multipoint-services/Work-with-Video-Devices.md deleted file mode 100644 index 6025b5492b..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/Work-with-Video-Devices.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Work with Video Devices -description: Learn how video monitors and projectors work with stations in MultiPoint Services -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Work with Video Devices -Learn how video devices, such as a monitor or projector, function when they are connected to a computer in your MultiPoint Services system or to a MultiPoint Services *station*. - -## Working with video monitors -Depending on your MultiPoint Services system hardware, there are two ways to connect a video monitor: - -- For *USB hub-based systems*, connect the video monitor cable to an open video port on the computer, as shown in the following illustration: - - ![Image of Video connection to USB hub-based system](./media/WMSVideoConnection.gif) - -- For *multifunction hub-based systems* with built-in video support, connect the video monitor cable to the video port on the multifunction hub: - - ![Image of multifunction hub and video connection](./media/WMSMultifunctionHubVideoConnection.gif) - -For more information, see the [Set Up a Station](Set-Up-a-Station.md) topic. - -## Working with video projectors -You can connect a video projector to your MultiPoint Services system when you want to project a large image to be viewed by others; for example, in a lab setting. For both USB hub-based and multifunction hub-based stations, you have two options for connecting a projector to a station: - -- Replace a monitor with a projector and use the projector as the display device for that station, as shown in the following illustration: - - ![Image of a projector connected to computer](./media/WMSVideoProjectorConnection.gif) - -- Obtain a video splitter device to connect both a projector and monitor to the station's video port. - - MultiPoint Services will display the same image on both display devices. When not projecting, you can turn the projector off and use just the video monitor. - -When using either option, note the following: - -- Connecting a video display may require that you *associate the station* again so that MultiPoint Services can correctly recognize the new display. Follow the instructions that appear on the station's video display device. - -- You may need to obtain adapter or converter devices to convert between DVI and VGA plugs. - -- Use of a "Y" splitter cable may decrease video quality on both video devices. - -- When using both a projector and a monitor via a "Y" splitter cable, MultiPoint Services adjusts the screen resolution of both devices to the lowest maximum resolution of either device—most typically the projector. - -- MultiPoint Services does not support extending a single station's display across multiple monitors. - -## See Also -[Manage Station Hardware](Manage-Station-Hardware.md) -[Set Up a Station](Set-Up-a-Station.md) diff --git a/WindowsServerDocs/remote/multipoint-services/deploy-multipoint-services-task-list.md b/WindowsServerDocs/remote/multipoint-services/deploy-multipoint-services-task-list.md deleted file mode 100644 index 9d02cb2523..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/deploy-multipoint-services-task-list.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Tasks for deploying MultiPoint Services -description: Lists all the tasks involved in deploying MultiPoint Services, along with links to instructions -ms.date: 07/22/2016 -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe ---- -# Task Lists: MultiPoint Services -Use the task lists in this topic to help you're the deployment of your MultiPoint Services system and keep track of completed tasks. Not all tasks apply to every environment. For example, some tasks are performed only if you deploy a MultiPoint server on an Active Directory domain. Others, such as creating split-screen stations or deploying virtual desktops for stations, are optional. For procedures that explain how to perform these tasks, see [Deploying MultiPoint Services](deploying-multipoint-services.md). - -## Task list: Deploy the server - -|Task|Description| -|--------|---------------| -|**1**|[Plan your MultiPoint Services Deployment](planning-a-multipoint-services-deployment.md)| -|**2**|[Collect hardware and device drivers needed for the installation](./multipoint-hardware-device-drivers.md)| -|**3**|[Set up the physical computer and primary station](Set-up-the-physical-computer-and-primary-station.md)| -|**4**|[Install MultiPoint Services](Install-MultiPoint-services.md)| -|**5**|[Update and install device drivers if needed](Update-and-install-device-drivers-if-needed.md)| -|**6**|[Set the date, time, and time zone](./set-the-date-time.md)| -|**7**|[Join the MultiPoint Services computer to a domain - optional](./join-multipoint-services-to-a-domain.md)| -|**8**|[Install updates](Install-updates.md)| -|**9**|[Attach additional stations to your MultiPoint Services computer](./multipoint-attach-additional-stations.md)| -|**10**|[Activate MultiPoint Services and add CALs](./manage-client-access-licenses.md)| -|**11**|[Install software on your MultiPoint Services system](./install-software-on-multipoint.md)| - -## Task list: Optional configurations - -|Task| -|--------| -|[Set up a split-screen station](Set-up-a-split-screen-station-in-MultiPoint-services.md)| -|[Add printers](Add-printers.md)| -|[Create virtual desktops for stations](Create-Windows-10-Enterprise-virtual-desktops-for-stations.md)| - -## Task list: Prepare your system for users - -|Task| -|--------| -|[Plan user accounts](Plan-user-accounts-for-your-MultiPoint-services-environment.md)| -|[Create local user accounts](Create-local-user-accounts.md)| -|[Limit users' access to the server](./limit-user-access-to-multipoint.md)| -|[Configure stations for automatic logon](Configure-stations-for-automatic-logon.md)| -|[Allow one account to have multiple sessions](Allow-one-account-to-have-multiple-sessions.md)| -|[Enable file sharing](Enable-file-sharing-in-MultiPoint-services.md)| - -## Task list: Server administration - -|Task| -|--------| -|[Configure Disk Protection](Configure-Disk-Protection-in-MultiPoint-services.md)| -|[Install Server Backup](./install-server-backup-on-multipoint.md)| diff --git a/WindowsServerDocs/remote/multipoint-services/hardware-and-performance-recommendations.md b/WindowsServerDocs/remote/multipoint-services/hardware-and-performance-recommendations.md deleted file mode 100644 index bc4e629151..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/hardware-and-performance-recommendations.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Hardware Requirements and Performance Recommendations -description: Provides hardware and performance requirements and recommendations for MultiPoint Services -ms.date: 07/22/2016 -ms.topic: best-practice -author: dknappettmsft -ms.author: daknappe ---- -# Hardware Requirements and Performance Recommendations -This topic describes the hardware that is required to run a MultiPoint Services system and support user application scenarios. The user scenario directly affects the CPU, RAM, and network bandwidth requirements. - -## Optimize MultiPoint Services system performance -The performance of your MultiPoint Services system will be directly affected by the capability of the CPU, the GPU, and the amount of RAM that is available on the computer that is running MultiPoint Services. - -### Applications and Internet content -Because MultiPoint Services is a shared resource computing solution, the type and number of applications that are running on the stations can impact the performance of your MultiPoint Services system. It is important to consider the types of programs that are used regularly when you are planning your system. For example, a graphics-intensive application requires a more powerful computer than an application such as a word processor. Overloading the computer with graphics-intensive applications will likely cause lag problems throughout the entire system. - -The type of content that is accessed by applications also affects the system's performance. If multiple stations are using web browsers to access multimedia content, such as full-motion video, fewer stations can be connected before adversely affecting the system performance. Conversely, if the multiple stations are using web browsers to access static web content, more stations can be connected without a significant effect on performance. - -### Hardware recommendations -To achieve good performance with your MultiPoint Services system under various loads, use the guidelines in the following table when you are planning and testing your system. These are the basic requirements forMultiPoint Services . The actual configuration sizing depends on your system configuration, the workload you are running, and the hardware capability. You should always validate by testing your applications and hardware. - -> [!NOTE] -> 2C = 2 cores, 4C = 4 cores, 6C = 6 cores, MT = multithreading. Processor speed should be at least 2.0 gigahertz (GHz). - -### Minimum recommended hardware for running default MultiPoint Server stations - -|Application Scenario|Up to 5 Stations|6-8 Stations|9-12 Stations|13-16 Stations|17-20 Stations|21-24 Stations| -|------------------------|----------------------|-------------------|------------------|-------------------|-------------------|-----------------| -|**Productivity**

        Office, web browsing, line-of-business applications|CPU: 2C

        RAM: 2 GB|CPU: 2C

        RAM: 4 GB|CPU: 4C

        RAM: 6 GB|CPU: 4C

        RAM: 8 GB|CPU: 4C+MT or 6C

        RAM: 10 GB| CPU: 6C+MT

        RAM: 12 GB| -|**Mixed**

        Office, web browsing, line-of-business applications, and occasional video use by some users|CPU: 2C

        RAM: 2 GB|CPU: 2C

        RAM: 4 GB|CPU: 4C

        RAM: 6 GB|CPU: 4C+MT or 6C

        RAM: 8 GB|CPU: 6C+MT

        RAM: 10 GB| CPU: 6C+MT

        RAM: 12 GB| -|**Video intensive**

        Office, web browsing, line-of-business applications, and frequent video use by all users **Note:** Video testing was performed using 360p H.264 video at native resolution.|CPU: 4C+MT

        RAM: 2 GB|CPU: 6C+MT

        RAM: 4 GB|CPU: 8C+MT

        RAM: 6 GB|CPU: 12C+MT

        RAM: 8 GB|CPU: 16C+MT

        RAM: 10 GB

        - Thin Client: RemoteFX
        - USB video not recommended| CPU: 20C+MT

        RAM: 12 GB

        - Thin Client: RemoteFX
        - USB video not recommended| - -## Minimum recommended hardware for running full Windows 10 virtual desktops -Running a full virtual operating system instance for each station is more compute resource-intensive than running the default MultiPoint desktop sessions, so the host hardware requirements per station are higher: - -1. CPU: 1 core or thread per station - -2. Solid State Drive (SSD) - - 1. Capacity >= 20GB per station + 40GB for the WMS host operating system - - 2. Random Read/Write IOPS >= 3K per station - -3. RAM >= 2GB per station + 2GB for the WMS host operating system - -BIOS CPU setting has been configured to enable virtualization – Second Level Address Translation (SLAT) - -For more information about choosing the best MultiPoint Services hardware for your needs, contact your hardware vendor. diff --git a/WindowsServerDocs/remote/multipoint-services/install-server-backup-on-multipoint.md b/WindowsServerDocs/remote/multipoint-services/install-server-backup-on-multipoint.md deleted file mode 100644 index 056f327d20..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/install-server-backup-on-multipoint.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Install Server Backup on your MultiPoint server -description: Walks you through the steps to install the backup and recovery tools -ms.date: 07/22/2016 -ms.topic: install-set-up-deploy -author: dknappettmsft -ms.author: daknappe ---- -# Install Server Backup on your MultiPoint server -It is recommended that you consider a backup and recovery plan for your MultiPoint servers. - -A good backup and recovery plan is important for any size environment. Windows Server Backup is a feature in Windows Server 2016 that provides a set of wizards and other tools for you to perform basic backup and recovery tasks for the server on which it is installed. You can use Windows Server Backup to back up a full server (all volumes), selected volumes, the system state, or specific files or folders, and to create a backup that you can use to rebuild your system. - -You can recover volumes, folders, files, certain applications, and the system state. And, for disasters like hard disk failures, you can rebuild a system either from scratch or by using alternate hardware. To do this, you must have a backup of the full server or just the volumes that contain operating system files and the Windows Recovery Environment. This restores your complete system onto your old system or onto a new hard disk. - -A key feature of Windows Server Backup is the ability to schedule backups to run automatically. - -Use the following procedures to set up the type of backup you require. - -## Install backup and recovery tools - -1. From the **Start** screen, open **Server Manager**. - -2. Click **Add Roles and Features** to start the Add Roles Wizard. Then click **Next** after you review the **Before you begin** notes. - -3. Select the **Role based or feature based installation** option, and then click **Next**. - -4. Select the local computer that you are managing, and click **Next**. - - The Add Features Wizard opens. - -5. On the **Select Features** page, expand Windows Server Backup Features, select the check boxes for **Windows Server Backup** and **Command-line Tools**, and then click **Next**. - - > [!NOTE] - > Or, if you just want to install the snap-in and the Wbadmin command-line tool, expand **Windows Server Backup Features**, and then select the **Windows Server Backup** check box only—make sure the **Command-line Tools** check box is clear. - -6. On the **Confirm Installation Selections** page, review your choices, and then click **Install**. - - If any errors occur during the installation, the **Installation Results** page will note the errors. - -7. After the installation completes successfully, you should be able to access these backup and recovery tools: - - - To open the Windows Server Backup snap-in, on the **Start** screen, type **backup**, and then click **Windows Server Backup** in the results. - - - To start the Wbadmin tool and view syntax for its commands: On the **Start** screen, type **command**. In the results, right-click **Command Prompt**, click **Run as administrator** at the bottom of the page, and then click **Yes** at the confirmation prompt. At the command prompt, type **wbadmin /?** and press ENTER. You should see command syntax and descriptions for the tool. - -## Configure backups using Windows Server Backup - -- Follow the guidance in [Backing Up Your Server](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc753528(v=ws.11)). diff --git a/WindowsServerDocs/remote/multipoint-services/install-software-on-multipoint.md b/WindowsServerDocs/remote/multipoint-services/install-software-on-multipoint.md deleted file mode 100644 index 4e233884f3..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/install-software-on-multipoint.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Install software on your MultiPoint Services system -description: Learn how to install software for users in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: install-set-up-deploy -author: dknappettmsft -ms.author: daknappe ---- -# Install software on your MultiPoint Services system -When you are logged on as an administrative user, you can install new programs either in console mode or, from a station, in station mode. However, we recommend that you install programs in console mode. - -You can install new software on the computer running MultiPoint Server so that all users can run the software, or so that only you can use the software, depending on the installation and licensing options of the software. - -1. Log on to the MultiPoint Services computer as an administrator. - -2. Open MultiPoint Manager. - -3. Click the **Home** tab, and then click **Switch to console mode**. - -4. Log on as an administrator, and install your applications. - -5. After you finish installing applications, switch the computer back to station mode. To do this, on the **Home** tab, click **Switch to station mode**. diff --git a/WindowsServerDocs/remote/multipoint-services/join-multipoint-services-to-a-domain.md b/WindowsServerDocs/remote/multipoint-services/join-multipoint-services-to-a-domain.md deleted file mode 100644 index d6ddfe5f67..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/join-multipoint-services-to-a-domain.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Join MultiPoint Services to a domain (optional) -description: Provides the steps to join MultiPoint Services to your domain -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Join the MultiPoint Services computer to a domain (optional) -If you will access your MultiPoint Services computer over an Active Directory domain, your next step is to add the computer to the domain. - -> [!IMPORTANT] -> You must verify your time zone before you join the computer to a domain. For instructions, see [Set the date, time, and time zone](./set-the-date-time.md). - -1. From the **Start** screen, open **Control Panel**. Click **System and Security**, and then click **System**. - -2. Under **Computer name, domain, and workgroup settings**, click **Change settings**. - -3. On the **Computer name** tab, click **Change**. - -4. In the **Computer Name/Domain Changes** dialog box, select **Domain**, enter the name of the domain, and click **OK**, and then follow the steps in the wizard to complete the process. - -5. After the computer restarts, log on as Administrator and wait for MultiPoint Manager to open. - -> [!IMPORTANT] -> To ensure that your MultiPoint Services domain deployment works correctly, you will need to configure a couple of group policies and update the Registry. For information, see [Configure group policies for a domain deployment](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn265982(v=ws.11)). diff --git a/WindowsServerDocs/remote/multipoint-services/limit-user-access-to-multipoint.md b/WindowsServerDocs/remote/multipoint-services/limit-user-access-to-multipoint.md deleted file mode 100644 index 2f96b908d6..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/limit-user-access-to-multipoint.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Limit user access to the server -description: Learn how to grant or deny access to MultiPoint Services for users and groups -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Limit users' access to the Multipoint server -Whether you join MultiPoint server to an Active Directory domain or you use local user accounts, all users have access to MultiPoint server by default. Before you allow users to log on to stations in your MultiPoint Services environment, you should restrict access to the server. - -Any user in the Remote Desktop Users group can log on to MultiPoint server. By default, the user group Everyone is a member of the Remote Desktop Users group, and therefore every local user and domain user can log on to the MultiPoint Server. To restrict access to MultiPoint Server, remove the Everyone user group from the Remote Desktop Users group, and then add specific users or groups to the Remote Desktop Users group. - -## Add or remove users or groups to the Remote Desktop Users group - -1. From the **Start** screen, open **Computer Management**. - -2. In the console tree, under **Local Users and Groups**, click **Groups**. - -3. Double click **Remote Desktop Users**, and follow the instructions to add or remove users. - - - To restrict general access to the server, remove the Everyone group. - - - To give your MultiPoint server users access to stations, add each local account or each domain user or group account to the Remote Desktop Users group. diff --git a/WindowsServerDocs/remote/multipoint-services/media/Diagram1.gif b/WindowsServerDocs/remote/multipoint-services/media/Diagram1.gif deleted file mode 100644 index 344fca71e2..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/Diagram1.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMS11_diagram7.gif b/WindowsServerDocs/remote/multipoint-services/media/WMS11_diagram7.gif deleted file mode 100644 index ad9e7a5c72..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMS11_diagram7.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMSActivityCenter.gif b/WindowsServerDocs/remote/multipoint-services/media/WMSActivityCenter.gif deleted file mode 100644 index 37d2a9279c..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMSActivityCenter.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMSMultiPointServerSystemLayout.gif b/WindowsServerDocs/remote/multipoint-services/media/WMSMultiPointServerSystemLayout.gif deleted file mode 100644 index ea750adb4e..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMSMultiPointServerSystemLayout.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMSMultiPointServerUSBSystemLayout.gif b/WindowsServerDocs/remote/multipoint-services/media/WMSMultiPointServerUSBSystemLayout.gif deleted file mode 100644 index d2fa41bfcc..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMSMultiPointServerUSBSystemLayout.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMSMultifunctionHubConnection.gif b/WindowsServerDocs/remote/multipoint-services/media/WMSMultifunctionHubConnection.gif deleted file mode 100644 index 0de7be05bc..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMSMultifunctionHubConnection.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMSMultifunctionHubPS2Connection.gif b/WindowsServerDocs/remote/multipoint-services/media/WMSMultifunctionHubPS2Connection.gif deleted file mode 100644 index 75459eee66..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMSMultifunctionHubPS2Connection.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMSMultifunctionHubVideoConnection.gif b/WindowsServerDocs/remote/multipoint-services/media/WMSMultifunctionHubVideoConnection.gif deleted file mode 100644 index c69690d17d..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMSMultifunctionHubVideoConnection.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMSUSBDeviceConnection.gif b/WindowsServerDocs/remote/multipoint-services/media/WMSUSBDeviceConnection.gif deleted file mode 100644 index d5f591ac09..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMSUSBDeviceConnection.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMSUSBHubConnection.gif b/WindowsServerDocs/remote/multipoint-services/media/WMSUSBHubConnection.gif deleted file mode 100644 index 8f6a81c13a..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMSUSBHubConnection.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMSVideoConnection.gif b/WindowsServerDocs/remote/multipoint-services/media/WMSVideoConnection.gif deleted file mode 100644 index 9ed6fa2d58..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMSVideoConnection.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMSVideoProjectorConnection.gif b/WindowsServerDocs/remote/multipoint-services/media/WMSVideoProjectorConnection.gif deleted file mode 100644 index 0175799eca..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMSVideoProjectorConnection.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMS_ClassroomPods.gif b/WindowsServerDocs/remote/multipoint-services/media/WMS_ClassroomPods.gif deleted file mode 100644 index c6212282ea..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMS_ClassroomPods.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMS_ComputerLabLayout.gif b/WindowsServerDocs/remote/multipoint-services/media/WMS_ComputerLabLayout.gif deleted file mode 100644 index eebb686b7c..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMS_ComputerLabLayout.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMS_LectureRoom.gif b/WindowsServerDocs/remote/multipoint-services/media/WMS_LectureRoom.gif deleted file mode 100644 index 822d127567..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMS_LectureRoom.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMS_diagram3.gif b/WindowsServerDocs/remote/multipoint-services/media/WMS_diagram3.gif deleted file mode 100644 index 79e12d91b2..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMS_diagram3.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMS_diagram4.gif b/WindowsServerDocs/remote/multipoint-services/media/WMS_diagram4.gif deleted file mode 100644 index dceae14633..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMS_diagram4.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMS_diagram5.gif b/WindowsServerDocs/remote/multipoint-services/media/WMS_diagram5.gif deleted file mode 100644 index 25d6ebaa2b..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMS_diagram5.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/media/WMS_diagram6.gif b/WindowsServerDocs/remote/multipoint-services/media/WMS_diagram6.gif deleted file mode 100644 index 4f457863f9..0000000000 Binary files a/WindowsServerDocs/remote/multipoint-services/media/WMS_diagram6.gif and /dev/null differ diff --git a/WindowsServerDocs/remote/multipoint-services/multipoint-attach-additional-stations.md b/WindowsServerDocs/remote/multipoint-services/multipoint-attach-additional-stations.md deleted file mode 100644 index 4c88b12b6e..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/multipoint-attach-additional-stations.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Attach additional stations to your MultiPoint server -description: Add more stations to your MultiPoint Services deployment -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Attach additional stations to MultiPoint Services -In your MultiPoint Services environment, your users use stations to connect to MultiPoint Services and do their work. The stations are the user endpoints for connecting to the computer running Multipoint Services. - -MultiPoint services supports three types of station: - -- Direct-video-connected stations - -- USB zero client-connected stations (and USB over Ethernet zero client connected stations) - -- RDP-over-LAN connected stations - -The classifications are based on a station's hardware and the type of connection that it uses. You can mix and match connection types for your stations. The only requirement is that the primary station (which you installed earlier) must be a direct-video-connected station. For more information about station setups, see [MultiPoint Stations](MultiPoint-services-Stations.md). - -For instructions that explain how to set up each type of station, see the following: - -- [Set up a direct-video-connected station](Set-up-a-direct-video-connected-station-in-MultiPoint-services.md) - -- [Set up a USB zero client-connected station](Set-up-a-USB-zero-client-connected-station-in-MultiPoint-services.md) - -- [Set up an RDP-over-LAN connected station](Set-up-an-RDP-over-LAN-connected-station-in-MultiPoint-services.md) - -For a detailed comparison of station types, see [Station type comparison](multipoint-services-stations.md#BKMK_StationTypeComparison). - -> [!NOTE] -> - The procedures for attaching stations do not describe how to set up intermediate hubs or downstream hubs. For information about where to install these hubs, see [MultiPoint Stations](MultiPoint-services-Stations.md). -> - In some cases, you might need to create station virtual desktops, which run in virtual machines. For example, you use applications that cannot be installed on Windows Server or applications that will not run multiple instances on the same host computer. For more information, see [Create Windows 10 Enterprise virtual desktops for stations](Create-Windows-10-Enterprise-virtual-desktops-for-stations.md). - -> [!TIP] -> It is useful to create your stations in the order of their physical locations so that they are identified sequentially in MultiPoint Server. If you later want to change the name of a station, you can do that in MultiPoint Manager. For more information, see Remap all stations in MultiPoint Server Help and Support. diff --git a/WindowsServerDocs/remote/multipoint-services/multipoint-hardware-device-drivers.md b/WindowsServerDocs/remote/multipoint-services/multipoint-hardware-device-drivers.md deleted file mode 100644 index c7e4585628..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/multipoint-hardware-device-drivers.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Collect hardware and device drivers needed for the installation -description: Information about drivers you need to install for MultiPoint Services -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- -# Collect hardware and device drivers needed for the installation -Before you start deploying your MultiPoint Services system, you will need: - -- **Hardware components for the server** - Install any additional video cards or other system components at this time. - -- **Hardware components for the stations** - For information about planning stations for your environment, see [Selecting Hardware for Your MultiPoint Services System](./select-hardware-mps.md). -- **The latest drivers for your video cards** - If your OEM or device manufacturer did not supply these, you will need to download them from the device manufacturer's website. - -- **The latest USB zero client drivers** - If you are using USB zero client stations, you must install the latest USB zero client drivers. - - > [!IMPORTANT] - > For a MultiPoint Services installation, you must install the 64-bit version of any drivers. - -> [!TIP] -> If you are installing MultiPoint Services on a computer with a different version of Windows already installed, you should find out the video card make and model in Device Manager before you start the Windows Server installation and ensure you can get drivers which are available for Windows Server 2016. Open Device Manager, open **Computer Management** from the **Start** screen. Then, in the console tree, click **Device Manager**. diff --git a/WindowsServerDocs/remote/multipoint-services/multipoint-services-migrate.md b/WindowsServerDocs/remote/multipoint-services/multipoint-services-migrate.md deleted file mode 100644 index d82e2987a1..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/multipoint-services-migrate.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Migrate to MultiPoint Services in Windows Server 2016 -description: Learn how to migrate from a previous version of MultiPoint Services -ms.date: 07/29/2016 -ms.topic: upgrade-and-migration-article -author: dknappettmsft -ms.author: daknappe ---- -# MultiPoint Services migration in Windows Server 2016 -> - -You can migrate from a previous release of Windows Server 2016 MultiPoint Services to the RTM version of MultiPoint Services. The following information provides preparation information and migration and verification steps. - -Migration documentation and tools ease the migration of server role settings and data from an existing server to a destination server that is running Windows Server 2016. By using the process described in this guide, you can simplify the migration process, reduce migration time, increase the accuracy of the migration process, and help eliminate possible conflicts that might otherwise occur during the migration process. - -## What to know before you begin -Before you begin the migration process, please note the following: - -- The migration process does not automatically gather or record settings for applications on the MultiPoint Services role. You should create a customized migration plan for any applications that you want to migrate. This is also true when using the virtual desktops feature in MultiPoint Services. -- This guide does not provide guidance for moving data saved in user or shared folders on the MultiPoint server. This applies to regular stations and virtual desktop stations. -- This guide does not contain instructions on how to migrate when the source server is running multiple roles. If your server is running multiple roles, you need to design a custom migration procedure that is specific to your server environment, based on information provided in the role migration guides. -- This guide does not contain information for migrating Remote Desktop Services CALS. For this information, see [Migrate Remote Desktop Services Client Access Licenses (RDS CALs)](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd851844(v=ws.11)). - -## Supported migration scenarios for MultiPoint Services in Windows Server 2016 -The MultiPoint Service role services is available in Windows Server 2016 Standard and Datacenter. This migration guide describes how to migrate the Multipoint Services role services from a source server running Windows Server 2016 to a destination server running the same version. - -## Scenarios that are not supported - -The following migration scenarios are not supported: - -- Migrating or upgrading from Windows MultiPoint Server 2012 and 2011. -- Migrating from a source server to a destination server that is running on operating system with a different system UI language installed. -- Migrating the MultiPoint Services role service from physical servers to virtual machines. -- Migrating any applications or application settings from the MultiPoint Server. - -## The impact of migration on MultiPoint Services -Be aware that the MultiPoint Services role will not be available during the migration. Plan your data migration to occur during off-peak hours to minimize downtime and reduce impact to users. Notify users that the resources will be unavailable during that time. - -## Migration information and steps -Use the following information to plan and carry out your MultiPoint Services migration: - -- [Gather the information you need for the migration.](multipoint-services-migration-preparation.md) -- [Migrate the MultiPoint Services role service.](multipoint-services-migration-steps.md) -- [Validate the migration and do any post-migration clean-up tasks](multipoint-services-post-migration-steps.md) diff --git a/WindowsServerDocs/remote/multipoint-services/multipoint-services-migration-preparation.md b/WindowsServerDocs/remote/multipoint-services/multipoint-services-migration-preparation.md deleted file mode 100644 index b991f016ed..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/multipoint-services-migration-preparation.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Prepare to migrate to MultiPoint Services -description: Describes information to gather before you migrate to MultiPoint Services in Windows Server 2016 -ms.date: 07/29/2016 -ms.topic: upgrade-and-migration-article -author: dknappettmsft -ms.author: daknappe ---- -# Prepare to migrate to MultiPoint Services in Windows Server 2016 - -Use the following information to gather the information you need to migrate the MultiPoint Services role service from a source server running an earlier release of Windows Server 2016 to a destination server running Windows Server 2016 RTM. - -At a minimum, you must be a member of the Administrators group on the source server and the destination server to install, remove, or set up MultiPoint Services. - ->[!NOTE] -> The steps here do not provide guidance for migrating data saved to user folder or shared folders. Ensure that users back up their data before you begin the migration. - -Use MultiPoint Manager to retrieve the information needed for migration. You will need server administrator permission to use MultiPoint Manager. - -Record the MultiPoint server, user, and environment settings in the [migration data collection worksheet](multipoint-services-migration-worksheet.md). Use the following steps to gather that information. - -## MultiPoint Server settings for the local server -1. Start MultiPoint Manager. -2. On the **Home** tab, select the local server, and then click **Edit server settings.** -3. Record the settings in the data worksheet. -4. Close the settings window. - -## Managed servers and computers - -You can find the names of the managed servers and computers on the **Home** tab in MultiPoint Manager. - -## Station settings -If auto-logon or display orientation are configured for the station, use the following steps to retrieve that information. Otherwise you can skip this step. - -To retrieve the station settings: - -1. Go to the **Stations** tab in MultiPoint Manager. -2. Find a station that has "yes" in the **Auto-logon** column. -3. Select that station, and then click **Configure station**. -4. Record the user that is used for auto-logon. - -To retrieve the display orientation settings, view the **station settings** for each station. - -## List of users -1. Click the **Users** tab in MultiPoint Manager. -2. Record the **Administrator** and **MultiPoint Dashboard User** accoutns. -3. Record the standard users. - -## VDI template location - If you previously enabled the VDI template feature, record the location of the VDI template. As long as the source and destination servers are on the same network, you can import the template by using MultiPoint Manager. - -## Next step -You're now ready to [migrate to MultiPoint Services](multipoint-services-migration-steps.md) in the RTM release of Windows Server 2016. diff --git a/WindowsServerDocs/remote/multipoint-services/multipoint-services-migration-steps.md b/WindowsServerDocs/remote/multipoint-services/multipoint-services-migration-steps.md deleted file mode 100644 index ee3e4baa28..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/multipoint-services-migration-steps.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Steps for migrating MultiPoint Services -description: Walks you through the steps to migrate to MultiPoint Services in Windows Server 2016 -ms.date: 07/29/2016 -ms.topic: upgrade-and-migration-article -author: dknappettmsft -ms.author: daknappe ---- -# Migrate to MultiPoint Services in Windows Server 2016 - -Use the following steps plus the information you gathered in the migration planning worksheet to migrate to MultiPoint Services in Windows Server 2016. - -## Transfer server settings -On the destination server, open MultiPoint Manager. Click **Edit server settings**. Apply the settings according to the migration planning worksheet. - -> [!NOTE] -> If you need to enable disk protection on the destination server, wait until after you configure MultiPoint Services. - -## Transfer station settings -Ensure that the stations are connected to the destination server and all mapped before you apply the station settings. The stations will be automatically detected. Follow the instructions on each station screen to define the server mapping of user stations and connected USB devices. Apply your preferred station settings as outlined in the migration planning worksheet. - -## Migrate the VDI template - -Before you can import the VDI template from the source server, enabled virtual desktops on the destination server by using MultiPoint Manager: - -1. Go to the **Virtual Desktops** tab in MultiPoint Manager. -2. Click **Enabled Virtual Desktops**. The server will install the Hyper-V role, and then restart. -3. Open MultiPoint Manager and navigate back to **Virtual Desktops**. -4. Click **Import virtual desktop template**. Follow the instructions to import the template from the source server. - -> [!NOTE] -> When you import a virtual desktop template, any customization applied to the template will be reset. - -## Next step -[Validate your new MultiPoint Services deployment.](multipoint-services-post-migration-steps.md) diff --git a/WindowsServerDocs/remote/multipoint-services/multipoint-services-migration-worksheet.md b/WindowsServerDocs/remote/multipoint-services/multipoint-services-migration-worksheet.md deleted file mode 100644 index f451cb5630..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/multipoint-services-migration-worksheet.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -title: Planning worksheet for MultiPoint Services migration -description: Provides planning worksheets to help you migrate to MultiPoint Services in Windows Server 2016 -ms.date: 07/29/2016 -ms.topic: upgrade-and-migration-article -author: dknappettmsft -ms.author: daknappe ---- -# Planning worksheet for MultiPoint Services migration - -Use the following lists and tables to gather the settings you need during MultiPoint Services migration. - -## Source server settings - -You can find the server settings on the **Home** tab in MultiPoint Manager. Place a check-mark next to each setting in use on the source server. - -- Allow one account to have multiple sessions. -- Allow this computer to be managed remotely. -- Allow monitoring of this computer's desktops. -- Always start in console mode. -- Do not show privacy notification at first user logon. -- Assign a unique IP to each station. -- Allow IM between the MultiPoint Dashboard and user sessions on this computer. -- Allow orchestration of administrator and MultiPoint Dashboard user sessions. -- Allow stations to use GPU hardware rendering. - -## Managed servers and computers - -Record the names of the managed servers and computers. You can find this information on the **Home** tab in MultiPoint Manager. - -| Computer | Computer name | -|----------|---------------| -| 1 | | -| 2 | | -| 3 | | -| 4 | | -| 5 | | -| 6 | | -| 7 | | -| 8 | | -| 9 | | -| 10 | | - - -## Stations - -Record the local stations and their settings. You can find this information on the **Stations** tab in MultiPoint Manager. - -| # | Station name | Auto-logon user account | Display orientation | -|----|--------------|-------------------------|---------------------| -| 1 | | | | -| 2 | | | | -| 3 | | | | -| 4 | | | | -| 5 | | | | -| 6 | | | | -| 7 | | | | -| 8 | | | | -| 9 | | | | -| 10 | | | | - -## Administrators and MultiPoint Dashboard Users - -Copy the user names for the administrators and MultiPoint Dashboard users. You can find this information on the **Users** tab in MultiPoint Manager. - -Administrators: - -- User name: -- User name: -- User name: -- User name: -- User name: -- User name: - -Dashboard users: - -- User name: -- User name: -- User name: -- User name: -- User name: - -## VDI template and virtual desktops - -Record the VDI template information and the names of virtual desktops in your MultiPoint Services deployment. You can find this information on the **Virtual Desktops** tab in MultiPoint Manager. - -**VDI template location**: - -| # | Virtual desktop name | -|---|---------------------------| -| 1 | | -| 2 | | -| 3 | | -| 4 | | -| 5 | | diff --git a/WindowsServerDocs/remote/multipoint-services/multipoint-services-post-migration-steps.md b/WindowsServerDocs/remote/multipoint-services/multipoint-services-post-migration-steps.md deleted file mode 100644 index 4e0609bd39..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/multipoint-services-post-migration-steps.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: MultiPoint Services - post-migration tasks -description: Learn how to validate and close out your migration to MultiPoint Services -ms.date: 07/29/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# MultiPoint Services - post-migration tasks - -After you migrate to MultiPoint Services in Windows Server 2016, use the following information to validate the migration and to perform clean-up steps. - -## Validate the migration by running a pilot program - -You can validate your MultiPoint Services migration by creating a pilot project in the production environment. Run the pilot project on the servers before you put the migrated role services into production to verify that your deployment works as you expect. Consider limiting the number of connections at first, slowly increasing the number of users accessing MultiPoint Services. - -> [!NOTE] -> Always use test accounts to test the migration. Use an account with administrative privileges and an account for a valid user. - -## Retire the source server -After you validate your migration, you can shut down or disconnect the source server from your network. If the server was domain-joined, remove it from the domain before you disconnect it. - diff --git a/WindowsServerDocs/remote/multipoint-services/multipoint-software-license-compliance.md b/WindowsServerDocs/remote/multipoint-services/multipoint-software-license-compliance.md deleted file mode 100644 index e9e01f97ff..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/multipoint-software-license-compliance.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Important Information about Software License Compliance -description: Provides information about licenses in MultiPoint Services. -ms.date: 07/22/2016 -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe ---- -# Important Information about Software License Compliance -You must comply with the license terms for the programs you use on the MultiPoint Services system. You must also have the proper number of licenses for the number of *stations* that you add to your MultiPoint Services system, as described in the following sections. - -## Software license compliance -If you are using other Microsoft programs or any third party programs with this Microsoft software or service, then the terms that come with such programs apply to your use of them. Microsoft may deem any failure to comply with such terms to also be a breach of your license from Microsoft. - -## Client access license (CAL) compliance -If you want to add a station to your MultiPoint Services system, you must secure the appropriate number of *client access licenses (CALs)* for all of the stations connected to the MultiPoint Services. - -## See Also -[Managing Your MultiPoint Server System](managing-your-multipoint-services-system.md) - diff --git a/WindowsServerDocs/remote/multipoint-services/multipoint-users-scenario.md b/WindowsServerDocs/remote/multipoint-services/multipoint-users-scenario.md deleted file mode 100644 index dba797687b..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/multipoint-users-scenario.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: MultiPoint Services user accounts -description: Learn about user accounts in MultiPoint Services, especially which kind to use for different scenarios -ms.topic: example-scenario -author: dknappettmsft -ms.author: daknappe -ms.date: 08/04/2016 ---- - -# Example scenarios: MultiPoint Services user accounts -What do you need to do to implement the user account scenario that you chose for your MultiPoint Services environment? The following tables describe each task to perform to configure user accounts and prepare stations for shared or individual user accounts on a stand-alone MultiPoint computer or on networked servers in a workgroup or an Active Directory domain. Choose the scenario that applies to your environment. Then follow the links in the table to complete each required configuration task. - -> [!NOTE] -> If you have not yet decided how to set up your user accounts, see [Plan user accounts for your MultiPoint Services environment](Plan-user-accounts-for-your-MultiPoint-services-environment.md) for more information about how each choice affects users. - -## Single MultiPoint Services computer in a stand-alone environment (no network) - -|Scenario|Tasks| -|-|-| -|**My users do not need to log on.** The stations can be available to anyone who walks up to them. They do not need an individual Windows desktop experience that includes private folders for storing data or personalized desktops.|1. Create a single local user account (For instructions, see [Create local user accounts](Create-local-user-accounts.md).)
        2. [Allow one account to have multiple sessions](Allow-one-account-to-have-multiple-sessions.md)
        3. [Configure stations for automatic logon](Configure-stations-for-automatic-logon.md)| -|**My users can all share the same user logon.** They do not need an individual Windows desktop experience that includes private folders for storing data or personalized desktops.|1. Create a single local user account (For instructions, see [Create local user accounts](Create-local-user-accounts.md).)
        2. [Allow one account to have multiple sessions](Allow-one-account-to-have-multiple-sessions.md)| -|**My users must have their own individual Windows desktop experience.**|Create a local user account for each user (For instructions, see [Create local user accounts](Create-local-user-accounts.md).)| - -## Multiple MultiPoint Services computers on a network, but with no domain - -|Scenario|Tasks| -|-|-| -|**My users do not need to log on.** The stations can be available to anyone who walks up to them. They do not need an individual Windows desktop experience that includes private folders for storing data or personalized desktops.|1. Create a single local user account on each server. (For instructions, see [Create local user accounts](Create-local-user-accounts.md).)
        2. [Allow one account to have multiple sessions](Allow-one-account-to-have-multiple-sessions.md) on each server
        3. [Configure stations for automatic logon](Configure-stations-for-automatic-logon.md) on each server| -|**My users can all share the same user logon.** They do not need an individual Windows desktop experience that includes private folders for storing data or personalized desktops.|1. Create a single local user account on each server. (For instructions, see [Create local user accounts](Create-local-user-accounts.md).)
        2. [Allow one account to have multiple sessions](Allow-one-account-to-have-multiple-sessions.md) on each server.| -|**My users must have their own individual Windows desktop experience.**

        - **Option A** - My users will always use local stations connected to the same MultiPoint Services computer.
        - **Option B** - My users will use local stations on more than one MultiPoint Services computer.
        - **Option C** - My users will use remote clients on the LAN.|- **Option A** - Create a single local user account on each server for the users of that server. (For instructions, see [Create local user accounts](Create-local-user-accounts.md).)
        - **Option B** - Create local user accounts for every user on every server. **Note:** This means that each user will have a profile on each server. In other words, if they save a file in My Documents while logged onto Server A's station, they will not see the file when logging onto Server B's station. (For instructions, see [Create local user accounts](Create-local-user-accounts.md).)
        - **Option C** - Assign each user to a specific MultiPoint Services computer. Create local user accounts for the assigned users on each server. (For instructions, see [Create local user accounts](Create-local-user-accounts.md).)| - -## One or more MultiPoint Services computers in a domain network environment - -|Scenario|Tasks| -|-|-| -|**My users do not need to log on.** The stations can be available to anyone who walks up to them. They do not need an individual Windows desktop experience that includes private folders for storing data or personalized desktops.|1. Create a domain account to log onto the servers.
        2. [Allow one account to have multiple sessions](Allow-one-account-to-have-multiple-sessions.md) on each server.
        3. [Configure stations for automatic logon](Configure-stations-for-automatic-logon.md) on each server.| -|**My users can all share the same user logon.** They do not need an individual Windows desktop experience that includes private folders for storing data or personalized desktops.|1. Create a domain account for a group or for each user.
        2. [Allow one account to have multiple sessions](Allow-one-account-to-have-multiple-sessions.md) on each server.| -|**My users must have their own individual Windows desktop experience.**

        - **Option A** - Any user with a domain account can use the MultiPoint Services computer.
        - **Option B** - I want to limit which domain accounts can access the server.|- **Option A** - No setup is required. By default, all domain users have access to any MultiPoint Services computer on the network.
        - **Option B** - Limit the access of domain user accounts to the MultiPoint Services computer. For instructions, see [Limit users access to the server](./limit-user-access-to-multipoint.md).| -|**I want to use local user accounts and manage them separately from my domain accounts.** For example, you want someone to manage MultiPoint Services but not the domain or you do not want to give domain accounts to all MultiPoint Services users.|Create one or more local user accounts on each server. (For instructions, see [Create local user accounts](Create-local-user-accounts.md).)

        **Note:** This means that each user account will have a profile on each server. In other words, if they save a file in My Documents while logged onto Server A's station, they will not see the file when logging onto Server B's station.| diff --git a/WindowsServerDocs/remote/multipoint-services/select-hardware-mps.md b/WindowsServerDocs/remote/multipoint-services/select-hardware-mps.md deleted file mode 100644 index a80b738338..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/select-hardware-mps.md +++ /dev/null @@ -1,198 +0,0 @@ ---- -title: Selecting Hardware for Your MultiPoint Services System -description: Hardware considerations for MultiPoint Services -ms.date: 07/22/2016 -ms.topic: concept-article -author: dknappettmsft -ms.author: daknappe ---- - -# Selecting Hardware for Your MultiPoint Services System - -When you build a MultiPoint Services system, you should select a computer that meets the Windows Server 2016 system requirements. If you are deciding which components to select, consider the following: - -- The target price range of your complete solution. - -- The types of usage scenarios that you might expect for the MultiPoint Services system, such as whether the users are running multimedia programs, using word processing or productivity programs, or browsing the Internet. - -- Whether your scenario has large processing or memory demands. - -- The number of users who could be using the system at the same time. If you plan to have many users on your system at the same time, or users who use system-intensive programs, you should plan for more computing power for your system. - -- The type of stations. How many USB ports or video ports do you need? - -- Future expansion plans. Do you plan to add stations to the MultiPoint Services system at a later date? Will you have enough video card slots, USB ports, or network taps? How many additional users will your hardware need to support? - -- Physical layout. For more information, see [MultiPoint Services Site Planning](MultiPoint-services-Site-Planning.md). - -A MultiPoint Services system typically includes the following components: - -- One computer that is running MultiPoint Services, which includes a CPU, RAM, hard disk drives, and video cards. - -- A monitor, station hub, keyboard, and mouse for each station. - -- Optional peripheral devices for the MultiPoint Services stations, including speakers, headphones, microphones, or storage devices that are available only to the user of the station. - -- Optional peripheral devices that are available to all users of the MultiPoint Services system, connected directly to the host computer, such as printers, external hard disk drives, and USB storage devices. - -Use the following information to make hardware decisions: - -- [Selecting a CPU](#selecting-a-cpu) -- [Selecting hardware components](#selecting-hardware-components) - -## Selecting a CPU - -A MultiPoint Services system is a multiple\-user environment, with all users connected to a single host computer. This increases the CPU usage because all users share the same computer. Some tasks, such as multimedia programs \(for example, media players or video\-editing software\), have larger processing demands. Therefore, make sure to select a CPU that can handle the processing requirements for the number of users and types of user scenarios that it will need to support. - -MultiPoint Services requires an x64\-based CPU, and must meet the system requirements for the computer as described in [Hardware Requirements and Performance Recommendations](./hardware-and-performance-recommendations.md). - -The following types of processors have been tested to be used on a MultiPoint Services system with high\-demand processing programs, such as multimedia programs: - -- **Dual\-core processor:** Can support up to 8 stations. -- **Quad\-core processor:** Can support up to 16 stations. -- **Quad\-core processor with multithreading:** Can support up to 20 stations. -- **Six\-core processor with multithreading:** Can support up to 24 stations. - -With this information, select a CPU that meets the processing requirements for your MultiPoint Services system. - -> [!NOTE] -> If you are running video intensive applications the recommendation is at least one core per station. - -## Selecting hardware components - -When you are building a MultiPoint Services system, consider the following hardware components that you may need: - -- Video hardware - -- MultiPoint Services station hardware - - - *USB hubs* - - - USB zero clients - - - Keyboards and mouse devices - - - Monitors - -- Peripheral devices - - - Audio devices, such as speakers and headphones - - - Microphones - - - USB mass storage devices - -When you have selected the hardware components for your MultiPoint Services system, make sure that you obtain current, 64\-bit drivers for the components. - -The following topics provide detailed information to help you select components for your MultiPoint Services system: - -[Selecting video hardware](#selecting-video-hardware) -[Selecting direct\-video\-connected or USB zero client station devices](#BKMK_Selectingdirect-video-connectedorUSBzeroclientstationdevices) -[Selecting other station peripheral devices](#selecting-other-station-peripheral-devices) -[Selecting RDP\-over\-LAN\-connected station hardware](#BKMK_SelectingRDP-over-LAN-connectedstationhardware) -[Selecting audio devices](#selecting-audio-devices) - -## Selecting video hardware - -The video hardware that you select should support the number of monitors that you will require for the number of users you intend to have working at MultiPoint Services stations. In addition, different types of video hardware can provide a higher\-performance solution for graphics\-intensive programs, such as multimedia content. - -Select the video hardware that can support the maximum number of monitors for the type of performance that your MultiPoint Services system requires. Make sure that you validate the performance of the video hardware that you choose to ensure that it meets your performance requirements. - -> [!NOTE] -> You must install a video driver that supports extending your desktop across multiple monitors. - -Video hardware options include: - -- Internal video cards that use a PCI or a PCIe bus interface - -- External video controllers connected by USB - -The following sections describe the capabilities of each of these video hardware types. You can combine internal video cards and external video controllers to create the system that you want. - -### Internal video cards -An internal video card is plugged\-in to the motherboard on the computer. The internal video card is a solution that can help the performance of graphics\-intensive multimedia programs. However, an internal video card requires an available PCI or PCIe slot to plug\-in to the motherboard. Many high\-performance video cards require a PCIe slot, but there are a limited number of PCIe slots on a motherboard. You should know what kind of video card slots are available on your computer so that you can purchase the correct type of video cards. - -The number of monitors that can connect to each video card depends on the GPU that is used on the card and the number of ports it supports, which typically ranges from 2 to 6. - -When you are selecting internal video cards, select video cards that support the number of monitors required to create the desired number of direct video connected stations. The maximum number of monitors that can be supported is equal to the number of internal video cards that are plugged\-in to the motherboard multiplied by the number of monitor ports on each of those video cards. For example, if you had two internal video cards and each card had two monitor ports, you could support up to four monitors. - -### External video controllers -USB zero clients contain an external video controller to connect a monitor to the client. The USB zero client might also include connections for headphones, speakers, a microphone, or other peripheral devices. - -Select a USB zero client if you want to enable support for additional monitors without opening the computer, or if you want to support more stations than available video outputs. For example, if you previously had four monitors plugged\-in to internal video cards, and you want to add two more monitors, you can plug\-in two external video controllers to the computer and have room for two more monitors. In this manner, you can combine a USB zero client with the video controller and not use additional PCI or PCIe slots on the motherboard. - -## Selecting direct\-video\-connected or USB zero client station devices -A MultiPoint Services station consists of a station hub or USB zero client with a keyboard and mouse plugged\-in, and a monitor that is plugged\-in to the host computer or in to a USB zero client. Other peripheral devices can be plugged\-in to the station hub or USB zero client, but they are not required to create MultiPoint station. These other peripheral devices are described in [Selecting other station peripheral devices](#selecting-other-station-peripheral-devices). - -The devices that you select to create a MultiPoint Services station should meet minimum requirements to work with MultiPoint Services. Details about the requirements for the following MultiPoint Services station devices are provided in this topic: - -- [Selecting USB hubs](#selecting-usb-hubs) -- [Selecting USB zero clients](#selecting-usb-zero-clients) -- [Selecting keyboards and mouse devices](#selecting-keyboards-and-mouse-devices) -- [Selecting monitors](#selecting-monitors) - -### Selecting USB hubs -The USB hubs that are used in a MultiPoint Services system can be a generic USB hub. Such hubs typically have four or more USB ports, and they allow multiple USB devices to be connected to a single USB port on the computer. Some other devices, such as keyboards and video monitors, may also incorporate a USB hub into their design. - -An additional consideration is the use of an *externally powered* hub, instead of a *bus\-powered* hub. With a bus\-powered hub, the amount of current that is provided by the host computer must be sufficient to provide power to all the peripheral devices that are plugged\-in to the hub, without degrading system performance. An externally powered hub allows you to connect more peripheral devices and provide sufficient power to all of them. The use of externally powered hubs can help prevent performance issues, port failures, and other intermittent issues. - -When selecting a USB hub for your MultiPoint Services system, consider its use. The hub can be used as a *station hub*, an *intermediate hub*, or a *downstream hub*. Refer to the following table for descriptions about each hub type. We recommend all USB devices to be USB 2.0 or later. - -| Description | Powered | -|--|--| -| Station Hub | Can be bus\-powered unless high\-powered devices will be plugged\-in to it or a downstream hub will be connected to it | -| Intermediate Hub | Should be externally powered | -| Downstream Hub | Can be externally powered or bus powered depending on the devices that are plugged\-in to the hub | -| Active USB Extender Cable | Active USB cables that include a USB hub are typically bus powered; therefore, they are not recommended for connecting station hubs to the computer. | - -### Selecting USB zero clients -A USB zero client is a USB hub that contains a video output. Therefore, it allows a monitor to be connected to the computer through a USB connection. For more information about using USB zero clients for video, see [Selecting video hardware](#selecting-video-hardware) in this document. A USB zero client can also enable the connection of a variety of USB and non\-USB devices to the hub. USB zero clients are produced by specific hardware manufacturers, and they require installing a device\-specific driver. - -### Selecting keyboards and mouse devices -The keyboard and mouse devices that you plug\-in to the station will typically be USB devices. Some USB zero clients provide PS\/2 ports, in which case, the keyboard and mouse should use PS\/2 to connect to the station hub. You can also use a PS\/2 keyboard and mouse if you are setting up a PS\/2 direct\-video\-connected station. - -A keyboard with an internal hub can be used as a station hub. However, all other station devices must connect to the internal hub by using ports on the keyboard. If such a keyboard is connected to the computer through another hub, that hub will be treated as an intermediate hub. - -If you are using split\-screen stations, you may want to consider using a mini keyboard that does not have a number pad so that the two keyboards can fit in front of the monitor. - -### Selecting monitors -There should be one monitor provided for each MultiPoint Services station, unless a split\-screen is planned. Monitors are plugged into the video card on the computer, the USB zero client or the LAN\-based client. Any type of monitor that is supported by the video card, USB zero client, or LAN\-based client can be used, including CRT monitors. - -Some special monitors include an internal LAN\-based client or USB zero client. Such monitors will typically include audio input\/output jacks and internal USB hubs for connecting keyboards and mice. They connect to the server through a USB or a LAN connection. - -#### Display resolution -The minimum supported resolution for a station's display area is 512 x 768 pixels. If the MultiPoint Services system starts and finds that a station's display area is less than the minimum resolution, a blank screen will be displayed on that station and the station will not be usable. - -If a display monitor is going to be shared by two stations as split\-screen stations, the minimum requirement for the display is 1024 x 768, so that the resulting individual station screen areas are at least 512 x 768. For the best split\-screen user experience, a wide screen with a minimum of resolution of 1600 x 900 is recommended. - -## Selecting other station peripheral devices -MultiPoint Services supports peripheral devices that are connected to a station hub, a USB zero client, or directly to the computer. Devices plugged into a station hub will be associated with that specific station. Other devices are available to every station when plugged directly into the computer. LAN clients can also support peripheral devices. - -> [!IMPORTANT] -> A keyboard cannot be connected to a downstream hub \(for example, a hub that is plugged into a station hub\). If you plug in a keyboard to a downstream hub, any peripherals that are plugged\-in to the downstream hub will no longer be available to that station. This behavior allows the support of daisy\-chained station hubs. - -**Available to all stations** A USB device that is plugged into the computer \(for example, not through a station hub\) is available to all stations. Depending on the device, it can be used by multiple users at one time, or only one user can access it at a time. The following table explains how USB devices can be accessed. - -> [!NOTE] -> The "Connected to Host Computer" column in the table refers to the behavior when the computer running MultiPoint Services is running in station mode with stations. If you are running in console mode, the peripherals that are plugged anywhere behave in the same way as a standard server in a console session. - -| Description | Connected to Host Computer | Connected to Station Hub or Downstream Hub | -|--|--|--| -| Keyboard | Not functional, unless it is part of a PS/2 station. | Available to individual station

        Cannot be connected to a downstream hub | -| Mouse | Not functional, unless it is part of a PS/2 station. | Available to individual station | -| Speaker/headphones | Not functional, unless it is part of a PS/2 station. | Available to individual station | -| USB storage device | Available to all stations | Available to individual station | -| HID Consumer Control | Not functional | Available to individual station | -| Other USB devices, such as cameras, document readers, and DVD drives | Available to all stations if supported by Windows Server 2012 | Available to all stations if supported by Windows Server 2008 R2 Remote Desktop Services | - -## Selecting RDP\-over\-LAN\-connected station hardware -Any LAN client that can connect to Remote Desktop Services, by using Remote Desktop Protocol, can become a MultiPoint Services station. - -If you want the LAN client to only be used as a MultiPoint station, you may want to "lock down" your LAN client. For example, configure your thin client so that it can only connect to a MultiPoint Services session, or configure your desktop computers so that access to desktop icons and Start Menu items such as a web browser is removed to prevent direct Internet access. You can make these configurations using your LAN client configuration tools or group or local policies. - -## Selecting audio devices -It is important to make sure that when you select audio devices, they can be plugged into the station hub, USB zero client or LAN client. Some USB hubs, USB zero clients, and LAN clients have an analog audio jack that can be used with traditional analog audio devices \(such as headphones or earbuds\). Station hubs that do not have analog jacks can use USB audio devices. - -If you have configured a PS\/2 direct\-video\-connected station by using PS\/2 ports on the computer's motherboard for the keyboard and mouse, you must use the analog audio on the computer's motherboard in order for the audio device to be available to this station when the MultiPoint Services system is running in station mode. - -If you do not have a PS\/2 direct\-video\-connected station, the host audio device on the system's motherboard will be available only when the MultiPoint Services system is running in console mode. diff --git a/WindowsServerDocs/remote/multipoint-services/set-the-date-time.md b/WindowsServerDocs/remote/multipoint-services/set-the-date-time.md deleted file mode 100644 index 618613964b..0000000000 --- a/WindowsServerDocs/remote/multipoint-services/set-the-date-time.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Set the date, time, and time zone -description: Learn how to set the date, time, and time zone in MultiPoint Services -ms.date: 07/22/2016 -ms.topic: how-to -author: dknappettmsft -ms.author: daknappe ---- -# Set the date, time, and time zone -After you finish installing device drivers, set the date, time, and time zone on the MultiPoint server. - -1. From the **Start** screen of the MultiPoint server, open **Control Panel**. - -2. Under **Clock, Language, and Region**, click **Set the time and date**. - -3. On the **Date and Time** tab, verify the date and time. If they are not correct, click **Change date and time**, update the date and time, and then click **OK**. - -4. Under **Time zone**, verify the time zone. If it is not correct, click **Change time zone**, select the correct time zone, and then click **OK**. - -5. Click **OK** again to save your settings and close the dialog box. diff --git a/WindowsServerDocs/remote/remote-desktop-services/index.yml b/WindowsServerDocs/remote/remote-desktop-services/index.yml index 1c3f9e16dc..fc2cac2015 100644 --- a/WindowsServerDocs/remote/remote-desktop-services/index.yml +++ b/WindowsServerDocs/remote/remote-desktop-services/index.yml @@ -7,8 +7,8 @@ metadata: title: Remote Desktop Services # Required; page title displayed in search results. Include the brand. < 60 chars. description: This topic provides an overview of Remote Desktop Services and its assorted features in Windows Server. # Required; article description that is displayed in search results. < 160 chars. ms.topic: landing-page # Required - ms.author: alalve - author: xelu86 + ms.author: roharwoo + author: robinharwood ms.date: 11/25/2024 #Required; mm/dd/yyyy format. # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | tutorial | overview | quickstart | reference | sample | tutorial | video | whats-new diff --git a/WindowsServerDocs/security/guarded-fabric-shielded-vm/guarded-fabric-initialize-hgs-ad-mode-bastion.md b/WindowsServerDocs/security/guarded-fabric-shielded-vm/guarded-fabric-initialize-hgs-ad-mode-bastion.md index 394d5fb82b..0cc51422fc 100644 --- a/WindowsServerDocs/security/guarded-fabric-shielded-vm/guarded-fabric-initialize-hgs-ad-mode-bastion.md +++ b/WindowsServerDocs/security/guarded-fabric-shielded-vm/guarded-fabric-initialize-hgs-ad-mode-bastion.md @@ -2,8 +2,8 @@ description: "Learn more about: Initialize the HGS cluster using AD mode in an existing bastion forest" title: Initialize the HGS cluster using AD mode in a bastion forest ms.topic: how-to -author: meaghanlewis -ms.author: mosagie +author: robinharwood +ms.author: roharwoo ms.date: 08/29/2018 --- diff --git a/WindowsServerDocs/storage/storage-replica/storage-replica-frequently-asked-questions.yml b/WindowsServerDocs/storage/storage-replica/storage-replica-frequently-asked-questions.yml index 65351865bb..69227d2359 100644 --- a/WindowsServerDocs/storage/storage-replica/storage-replica-frequently-asked-questions.yml +++ b/WindowsServerDocs/storage/storage-replica/storage-replica-frequently-asked-questions.yml @@ -2,12 +2,10 @@ metadata: title: "Storage Replica FAQ" description: Get answers to common questions for Storage Replica in Windows Server. - manager: siroy ms.author: roharwoo ms.topic: faq author: robinharwood ms.date: 04/15/2020 - ms.assetid: 12bc8e11-d63c-4aef-8129-f92324b2bf1b ms.service: windows-server title: Storage Replica FAQ summary: | diff --git a/WindowsServerDocs/virtualization/hyper-v/Best-Practices-for-running-Linux-on-Hyper-V.md b/WindowsServerDocs/virtualization/hyper-v/Best-Practices-for-running-Linux-on-Hyper-V.md index 9e206dad32..65f748fe15 100644 --- a/WindowsServerDocs/virtualization/hyper-v/Best-Practices-for-running-Linux-on-Hyper-V.md +++ b/WindowsServerDocs/virtualization/hyper-v/Best-Practices-for-running-Linux-on-Hyper-V.md @@ -87,10 +87,6 @@ After resizing a VHD or VHDX, administrators should use a utility like fdisk or * [Best practices for running FreeBSD on Hyper-V](Best-practices-for-running-FreeBSD-on-Hyper-V.md) -* [Deploy a Hyper-V Cluster](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj863389(v=ws.11)) - * [Create Linux Images for Azure](/azure/virtual-machines/linux/create-upload-generic) * [Optimize your Linux VM on Azure](/azure/virtual-machines/linux/optimization) - - diff --git a/WindowsServerDocs/virtualization/hyper-v/Hyper-V-feature-compatibility-by-generation-and-guest.md b/WindowsServerDocs/virtualization/hyper-v/Hyper-V-feature-compatibility-by-generation-and-guest.md index d57be63dac..0f505f50d1 100644 --- a/WindowsServerDocs/virtualization/hyper-v/Hyper-V-feature-compatibility-by-generation-and-guest.md +++ b/WindowsServerDocs/virtualization/hyper-v/Hyper-V-feature-compatibility-by-generation-and-guest.md @@ -17,65 +17,70 @@ Keep in mind that some features rely on hardware or other infrastructure. For ha ## Availability and backup -Feature | Generation | Guest operating system -------------- | ------------- | ----------- -Checkpoints | 1 and 2 | Any supported guest -Guest clustering | 1 and 2 | Guests that run cluster-aware applications and have iSCSI target software installed -Replication | 1 and 2 | Any supported guest -Domain Controller | 1 and 2 | Any supported Windows Server guest using only production checkpoints. See [Supported Windows Server guest operating systems](./supported-windows-guest-operating-systems-for-hyper-v-on-windows.md#supported-windows-server-guest-operating-systems) +| Feature | Generation | Guest operating system | +| ------- | ---------- | --------------------- | +| Checkpoints | 1 and 2 | Any supported guest | +| Guest clustering | 1 and 2 | Guests that run cluster-aware applications and have iSCSI target software installed | +| Replication | 1 and 2 | Any supported guest | +| Domain Controller | 1 and 2 | Any supported Windows Server guest using only production checkpoints. See [Supported Windows Server guest operating systems](./supported-windows-guest-operating-systems-for-hyper-v-on-windows.md#supported-windows-server-guest-operating-systems) | ## Compute -Feature | Generation | Guest operating system -------------- | ------------- | ----------- -Dynamic memory | 1 and 2 | Specific versions of supported guests. See [Hyper-V Dynamic Memory Overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831766(v=ws.11)) for versions older than Windows Server 2016 and Windows 10. -Hot add/removal of memory | 1 and 2 | Windows Server 2016, Windows 10 -Virtual NUMA | 1 and 2 | Any supported guest +| Feature | Generation | Guest operating system | +| ------- | ---------- | --------------------- | +| Dynamic memory | 1 and 2 | Specific versions of supported guests. See [Hyper-V Dynamic Memory Overview](dynamic-memory.md). | +| Hot add/removal of memory | 1 and 2 | Windows Server 2016, Windows 10 | +| Virtual NUMA | 1 and 2 | Any supported guest | ## Development and test -Feature | Generation | Guest operating system -------------- | ------------- | ----------- -COM/Serial ports | 1 and 2
        **Note:** For generation 2, use Windows PowerShell to configure. For details, see [Add a COM port for kernel debugging](plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v.md#add-a-com-port-for-kernel-debugging). | Any supported guest +| Feature | Generation | Guest operating system | +| ------- | ---------- | --------------------- | +| COM/Serial ports | 1 and 2 | Any supported guest | + +> [!NOTE] +> For generation 2 COM/Serial ports, use Windows PowerShell to configure. For details, see [Add a COM port for kernel debugging](plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v.md#add-a-com-port-for-kernel-debugging). ## Mobility -Feature | Generation | Guest operating system -------------- | ------------- | ----------- -Live migration | 1 and 2 | Any supported guest -Import/export | 1 and 2 | Any supported guest +| Feature | Generation | Guest operating system | +| ------- | ---------- | --------------------- | +| Live migration | 1 and 2 | Any supported guest | +| Import/export | 1 and 2 | Any supported guest | ## Networking -Feature | Generation | Guest operating system -------------- | ------------- | ----------- -Hot add/removal of virtual network adapter | 2 | Any supported guest -Legacy virtual network adapter | 1 | Any supported guest -Single root input/output virtualization (SR-IOV) | 1 and 2 | 64-bit Windows guests, starting with Windows Server 2012 and Windows 8. -Virtual machine multi queue (VMMQ) | 1 and 2 | Any supported guest +| Feature | Generation | Guest operating system | +| ------- | ---------- | --------------------- | +| Hot add/removal of virtual network adapter | 2 | Any supported guest | +| Legacy virtual network adapter | 1 | Any supported guest | +| Single root input/output virtualization (SR-IOV) | 1 and 2 | 64-bit Windows guests, starting with Windows Server 2012 and Windows 8. | +| Virtual machine multi queue (VMMQ) | 1 and 2 | Any supported guest | ## Remote connection experience -Feature | Generation | Guest operating system -------------- | ------------- | ----------- -Discrete device assignment (DDA) | 1 and 2 | Windows Server 2012 and later, Windows 10 and Windows 11
        -Enhanced session mode | 1 and 2 | Windows Server 2012 R2 and later, and Windows 8.1 and later, with Remote Desktop Services enabled
        **Note**: You might need to also configure the host. For details, see [Use local resources on Hyper-V virtual machine with VMConnect](./learn-more/Use-local-resources-on-Hyper-V-virtual-machine-with-VMConnect.md). -RemoteFx | 1 and 2 | Generation 1 on 32-bit and 64-bit Windows versions starting with Windows 8.
        Generation 2 on 64-bit Windows 10 and Windows 11 versions +| Feature | Generation | Guest operating system | +| ------- | ---------- | --------------------- | +| Discrete device assignment (DDA) | 1 and 2 | Windows Server 2012 and later, Windows 10 and Windows 11 | +| Enhanced session mode | 1 and 2 | Windows Server 2012 R2 and later, and Windows 8.1 and later, with Remote Desktop Services enabled. | +| RemoteFx | 1 and 2 | Generation 1 on 32-bit and 64-bit Windows versions starting with Windows 8; Generation 2 on 64-bit Windows 10 and Windows 11 versions | + +> [!NOTE] +> You might need to also configure the host for Enhanced session mode. For details, see [Use local resources on Hyper-V virtual machine with VMConnect](./learn-more/Use-local-resources-on-Hyper-V-virtual-machine-with-VMConnect.md). ## Security -Feature | Generation | Guest operating system -------------- | ------------- | ----------- -Secure boot | 2 | **Linux**: Ubuntu 14.04 and later, SUSE Linux Enterprise Server 12 and later, Red Hat Enterprise Linux 7.0 and later, and CentOS 7.0 and later
        **Windows**: All supported versions that can run on a generation 2 virtual machine -Shielded virtual machines | 2 | **Windows**: All supported versions that can run on a generation 2 virtual machine +| Feature | Generation | Guest operating system | +| ------- | ---------- | --------------------- | +| Secure boot | 2 | **Linux**: Ubuntu 14.04 and later, SUSE Linux Enterprise Server 12 and later, Red Hat Enterprise Linux 7.0 and later, and CentOS 7.0 and later; **Windows**: All supported versions that can run on a generation 2 virtual machine | +| Shielded virtual machines | 2 | **Windows**: All supported versions that can run on a generation 2 virtual machine | ## Storage -Feature | Generation | Guest operating system -------------- | ------------- | ----------- -Shared virtual hard disks (VHDX only) | 1 and 2 | Windows Server 2012 and later -SMB3 | 1 and 2 | All that support SMB3 -Storage spaces direct | 2 | Windows Server 2016 and later -Virtual Fibre Channel | 1 and 2 | Windows Server 2012 and later -VHDX format | 1 and 2 | Any supported guest - +| Feature | Generation | Guest operating system | +| ------- | ---------- | --------------------- | +| Shared virtual hard disks (VHDX only) | 1 and 2 | Windows Server 2012 and later | +| SMB3 | 1 and 2 | All that support SMB3 | +| Storage spaces direct | 2 | Windows Server 2016 and later | +| Virtual Fibre Channel | 1 and 2 | Windows Server 2012 and later | +| VHDX format | 1 and 2 | Any supported guest | diff --git a/WindowsServerDocs/virtualization/hyper-v/Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md b/WindowsServerDocs/virtualization/hyper-v/Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md index 8a74eebe87..5ea24da685 100644 --- a/WindowsServerDocs/virtualization/hyper-v/Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md +++ b/WindowsServerDocs/virtualization/hyper-v/Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md @@ -113,16 +113,6 @@ Following are the versions of Windows client that are supported as guest operati - **Integration Services**: Upgrade the integration services after you set up the guest operating system. - **Notes**: Ultimate, Enterprise, and Professional editions (32-bit and 64-bit). -## Guest operating system support on other versions of Windows - -The following table gives links to information about guest operating systems supported for Hyper-V on other versions of Windows. - -|Host operating system|Article| -|-------------------------|---------| -|Windows Server 2012 R2 and Windows 8.1|- [Supported Windows Guest Operating Systems for Hyper-V in Windows Server 2012 R2 and Windows 8.1](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn792027(v=ws.11))
        - [Linux and FreeBSD Virtual Machines on Hyper-V](Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md)| -|Windows Server 2012 and Windows 8|[Supported Windows Guest Operating Systems for Hyper-V in Windows Server 2012 and Windows 8](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn792028(v=ws.11))| -|Windows Server 2008 and Windows Server 2008 R2|[About Virtual Machines and Guest Operating Systems](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc794868(v=ws.10))| - ## Supported Linux and FreeBSD | Guest operating system | diff --git a/WindowsServerDocs/virtualization/hyper-v/deploy/Set-up-hosts-for-live-migration-without-Failover-Clustering.md b/WindowsServerDocs/virtualization/hyper-v/deploy/Set-up-hosts-for-live-migration-without-Failover-Clustering.md index 149ee2149d..8fc43f4cdd 100644 --- a/WindowsServerDocs/virtualization/hyper-v/deploy/Set-up-hosts-for-live-migration-without-Failover-Clustering.md +++ b/WindowsServerDocs/virtualization/hyper-v/deploy/Set-up-hosts-for-live-migration-without-Failover-Clustering.md @@ -135,7 +135,7 @@ This table describes how the performance options work. |--------|-------------| | TCP/IP | Copies the memory of the virtual machine to the destination server over a TCP/IP connection. | | Compression | Compresses the memory content of the virtual machine before copying it to the destination server over a TCP/IP connection. Compression is the **default** setting. | -| SMB | Copies the memory of the virtual machine to the destination server over an SMB 3.0 connection.
        - SMB Direct is used when the network adapters on the source and destination servers have Remote Direct Memory Access (RDMA) enabled.
        - SMB Multichannel automatically detects and uses multiple connections when a proper SMB Multichannel configuration is set up.
        For more information, see [Improve Performance of a File Server with SMB Direct](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj134210(v=ws.11)). | +| SMB | Copies the memory of the virtual machine to the destination server over an SMB 3.0 connection.
        - SMB Direct is used when the network adapters on the source and destination servers have Remote Direct Memory Access (RDMA) enabled.
        - SMB Multichannel automatically detects and uses multiple connections when a proper SMB Multichannel configuration is set up.
        For more information, see [Improve Performance of a File Server with SMB Direct](/windows-server/storage/file-server/smb-direct). | ## Next steps diff --git a/WindowsServerDocs/virtualization/hyper-v/dynamic-memory.md b/WindowsServerDocs/virtualization/hyper-v/dynamic-memory.md new file mode 100644 index 0000000000..5ee03ebde3 --- /dev/null +++ b/WindowsServerDocs/virtualization/hyper-v/dynamic-memory.md @@ -0,0 +1,92 @@ +--- +title: Dynamic Memory for Hyper-V Virtual Machines +description: Provides an overview of Dynamic Memory for Hyper-V virtual machines, including how it works and best practices. +ms.topic: conceptual +ms.author: daknappe +author: dknappettmsft +ms.date: 10/27/2025 +--- + +# Hyper-V Dynamic Memory Overview + +If you have idle or low-load virtual machines, such as in pooled Virtual Desktop Infrastructure (VDI) environments, Dynamic Memory enables you to increase consolidation and improve reliability for restart operations. You also gain agility in responding to requirement changes with these new capabilities. + +## Key benefits + +With Dynamic Memory, you can attain higher consolidation numbers with improved reliability for restart operations. This capability can lead to lower costs, especially in environments that have many idle or low-load virtual machines, such as pooled VDI environments. Dynamic Memory run-time configuration changes can reduce downtime and provide increased agility to respond to requirement changes. + +Hyper-V running on Windows Server automatically calculates an amount of memory to reserve for exclusive use by the management host operating system. This memory is used to run virtualization services. If the computer is part of a failover cluster, Hyper-V also reserves enough memory to run failover cluster services. + +## Technical overview + +Dynamic Memory defines startup memory as the minimum amount of memory that a virtual machine can have. However, Windows requires more memory during startup than the steady state. As a result, administrators sometimes assign extra memory to a virtual machine because Hyper-V can't reclaim memory from these virtual machines after startup. Dynamic Memory introduces a minimum memory setting, which allows Hyper-V to reclaim the unused memory from the virtual machines. This feature is reflected as increased virtual machine consolidation numbers, especially in Virtual Desktop Infrastructure (VDI) environments. + +Windows Server also introduced Smart Paging for reliable virtual machine restart operations. Although minimum memory increases virtual machine consolidation numbers, it also brings a challenge. If a virtual machine has a smaller amount of memory than its startup memory and if it's restarted, Hyper-V needs additional memory to restart the virtual machine. Due to host memory pressure or virtual machine states, Hyper-V might not always have additional memory available. This limitation can cause sporadic virtual machine restart failures. Smart Paging bridges the memory gap between minimum memory and startup memory, and allows virtual machines to restart reliably. + +### Minimum memory configuration with reliable restart operation + +As in the previous version of Dynamic Memory, you can configure a minimum memory amount for virtual machines, and Hyper-V continues to ensure that it always assigns this amount to running virtual machines. + +To provide a reliable restart experience for virtual machines configured with less minimum memory than startup memory, Hyper-V uses Smart Paging. This memory management method uses disk resources as additional, temporary memory when more memory is required to restart a virtual machine. This approach has advantages and drawbacks. It provides a reliable way to keep the virtual machines running when there's no available physical memory. However, it can degrade virtual machine performance because disk access speeds are much slower than memory access speeds. + +> [!IMPORTANT] +> When installing or upgrading the operating system of a virtual machine, the amount of memory that's available to the virtual machine during the installation and upgrade process is the value specified as **Startup RAM**. Even if you configure Dynamic Memory for the virtual machine, the virtual machine uses only the amount of memory configured in the **Startup RAM** setting. Ensure the **Startup RAM** value meets the minimum memory requirements of the operating system during the install or upgrade procedure. + +To minimize the performance impact of Smart Paging, Hyper-V uses it only when all of the following conditions occur: + +- The virtual machine is being restarted. +- There's no available physical memory. +- No memory can be reclaimed from other virtual machines running on the host. + +Hyper-V doesn't use Smart Paging when: + +- You start a virtual machine from an "off state" (instead of a restart). +- You oversubscribe memory for a running virtual machine. +- A virtual machine fails over in Hyper-V clusters. + +When you oversubscribe host memory, Hyper-V continues to rely on the paging operation in the guest operating system because it's more effective than Smart Paging. The paging operation in the guest operating system is performed by Windows Memory Manager. Windows Memory Manager has more information than the Hyper-V host about memory usage within the virtual machine, which means it can provide Hyper-V with better information to use when choosing the memory to be paged. Because of this, the system incurs less overhead compared to Smart Paging. + +To further reduce the impact of Smart Paging, Hyper-V removes memory from the virtual machine after it completes the start process. It accomplishes this goal by coordinating with Dynamic Memory components inside the guest operating system ("ballooning"), so the virtual machine stops using Smart Paging. With this technique, the use of Smart Paging is temporary and isn't expected to last longer than 10 minutes. + +Also note the following about how Hyper-V uses Smart Paging: + +- It creates Smart Paging files only when needed for a virtual machine. +- It deletes Smart Paging files after it removes the additional amount of memory. +- It doesn't use Smart Paging for this virtual machine again until another restart occurs and there's not enough physical memory. + +### Run-time Dynamic Memory configuration changes + +Hyper-V enables you to make the following configuration changes to Dynamic Memory when the virtual machine is running: + +- Increase the maximum memory. +- Decrease the minimum memory. + +## About the Dynamic Memory settings + +The following virtual machine settings in Hyper-V Manager allow you to configure Dynamic Memory. Review the following descriptions to understand how the features work and how they are related. + +| Setting | Description | +| --- | --- | +| Startup RAM | Specifies the amount of memory required to start the virtual machine. The value needs to be high enough to allow the guest operating system to start, but should be as low as possible to allow for optimal memory utilization and potentially higher consolidation ratios. | +| Minimum RAM | Specifies the minimum amount of memory that should be allocated to the virtual machine after the virtual machine starts. Set the value as low as 32 MB up to a maximum value equal to the **Startup RAM** value. | +| Maximum RAM | Specifies the maximum amount of memory that this virtual machine can use. Set the value from as low as the value for Startup RAM up to as high as 1 TB. However, a virtual machine can use only as much memory as the maximum amount supported by the guest operating system. For example, if you specify 64 GB for a virtual machine running a guest operating system that supports a maximum of 32 GB, the virtual machine can't use more than 32 GB. | +| Memory buffer | Specifies how much memory Hyper-V attempts to assign to the virtual machine compared to the amount of memory actually needed by the applications and services running inside the virtual machine. Memory buffer is specified as a percentage because the actual amount of memory that represents the buffer changes in response to changes in memory usage while the virtual machine is running. Hyper-V uses performance counters in the virtual machine that identify committed memory to determine the current memory requirements of the virtual machine and then calculates the amount of memory to add as a buffer. The buffer is determined using the following formula: Amount of memory buffer = how much memory the virtual machine actually needs / (memory buffer value / 100). For example, if the memory committed to the guest operating system is 1,000 MB and the memory buffer is 20%, Hyper-V attempts to allocate an additional 20% (200 MB) for a total of 1,200 MB of physical memory allocated to the virtual machine. **Note:** The buffer isn't maintained when there's not enough physical memory available in the computer to give every virtual machine its requested memory buffer. | +| Memory weight | Provides Hyper-V with a way to determine how to distribute memory among virtual machines if there's not enough physical memory available in the computer to give every virtual machine its requested amount of memory. | + +## Dynamic Memory / Hyper-V Memory Management FAQs + +The following are some frequently asked questions regarding Dynamic Memory. + +### Do I need to manually configure the size of the page file after installing the Hyper-V role? + +No, it's recommended to allow the system to manage the page file size when running Hyper-V. + +### How is the memory divided between the host operating system and running virtual machines? + +Hyper-V monitors the runtime health of the host operating system to determine how much memory it can safely allocate to virtual machines. + +### My virtual machine failed to start with the following error message “Not enough memory in the system to start the virtual machine” or “Could not initialize memory: Ran out of memory (0x8007000E)”. How can I tell how much memory is available for virtual machines? + +As described earlier, Hyper-V monitors the runtime health of the host operating system to determine how much memory it can safely allocate to virtual machines. + +You can view the current amount of memory available to virtual machines in the following Performance Monitor counter: **Hyper-V Dynamic Memory Balancer – Available Memory**. diff --git a/WindowsServerDocs/virtualization/hyper-v/failover-cluster-network-recommendations.md b/WindowsServerDocs/virtualization/hyper-v/failover-cluster-network-recommendations.md new file mode 100644 index 0000000000..88670c3a83 --- /dev/null +++ b/WindowsServerDocs/virtualization/hyper-v/failover-cluster-network-recommendations.md @@ -0,0 +1,383 @@ +--- +title: Network recommendations for a Hyper-V cluster +description: Best-practice guidance for planning, isolating, and optimizing networking for a Windows Server Hyper-V failover cluster, including QoS, NIC Teaming, VMQ, and converged networking. +author: dknappettmsft +ms.author: daknappe +ms.topic: best-practice +ms.date: 10/27/2025 +#CustomerIntent: As a virtualization admin, I want network configuration recommendations for a Windows Server Hyper-V cluster so I can design a reliable and performant environment. +--- + +# Network recommendations for Hyper-V in a failover cluster + +When you deploy a highly available Hyper-V solution, you must consider and plan for several different types of network traffic. Design your network configuration with the following goals in mind: + +- Ensure network quality of service +- Provide network redundancy +- Isolate traffic to defined networks +- Where applicable, take advantage of Server Message Block (SMB) Multichannel + +This topic provides network configuration recommendations that are specific to a Hyper-V cluster running Windows Server. It includes an overview of the different network traffic types, recommendations for how to isolate traffic, recommendations for features such as NIC Teaming, Quality of Service (QoS), and Virtual Machine Queue (VMQ), and a Windows PowerShell script that shows an example of converged networking, where the network traffic on a Hyper-V cluster routes through one external virtual switch. + +Windows Server supports the concept of converged networking, where different types of network traffic share the same Ethernet network infrastructure. Features such as Hyper-V QoS and the ability to add virtual network adapters to the management operating system enable you to consolidate the network traffic on fewer physical adapters. Combined with traffic isolation methods such as VLANs, you can isolate and control the network traffic. + +> [!NOTE] +> If you use System Center Virtual Machine Manager (VMM) to create or manage Hyper-V clusters, you must use VMM to configure the network settings that are described in this topic. + +## Overview of different network traffic types + +When you deploy a Hyper-V cluster, you must plan for several types of network traffic. The following table summarizes the different traffic types. + +| Network Traffic Type | Description | +| --- | --- | +| Management | Provides connectivity between the server that is running Hyper-V and basic infrastructure functionality. Use it to manage the Hyper-V management operating system and virtual machines. | +| Cluster | Use it for inter-node cluster communication such as the cluster heartbeat and Cluster Shared Volumes (CSV) redirection. | +| Live migration | Use it for virtual machine live migration. | +| Storage | Use it for SMB traffic or for iSCSI traffic. | +| Replica traffic | Use it for virtual machine replication through the Hyper-V Replica feature. | +| Virtual machine access | Use it for virtual machine connectivity. Typically requires external network connectivity to service client requests. | + +The following sections provide more detailed information about each network traffic type. + +### Management traffic + +A management network provides connectivity between the operating system of the physical Hyper-V host (also known as the *management operating system*) and basic infrastructure functionality such as Active Directory Domain Services (AD DS), Domain Name System (DNS), and Windows Server Update Services (WSUS). It also manages the server that is running Hyper-V and the virtual machines. + +The management network must have connectivity between all required infrastructure, and to any location from which you want to manage the server. + +### Cluster traffic + +A failover cluster monitors and communicates the cluster state between all members of the cluster. This communication is very important to maintain cluster health. If a cluster node doesn't communicate a regular health check (known as the *cluster heartbeat*), the cluster considers the node down and removes the node from cluster membership. The cluster then transfers the workload to another cluster node. + +Inter-node cluster communication also includes traffic that's associated with CSV. For CSV, where all nodes of a cluster can access shared block-level storage simultaneously, the nodes in the cluster must communicate to orchestrate storage-related activities. Also, if a cluster node loses its direct connection to the underlying CSV storage, CSV has resiliency features which redirect the storage I/O over the network to another cluster node that can access the storage. + +### Live migration traffic + +Live migration enables the transparent movement of running virtual machines from one Hyper-V host to another without a dropped network connection or perceived downtime. + +Use a dedicated network or VLAN for live migration traffic to ensure quality of service and for traffic isolation and security. Live migration traffic can saturate network links. This saturation can cause other traffic to experience increased latency. The time it takes to fully migrate one or more virtual machines depends on the throughput of the live migration network. Therefore, you must ensure that you configure the appropriate quality of service for this traffic. To provide the best performance, live migration traffic isn't encrypted. + +You can designate multiple networks as live migration networks in a prioritized list. For example, you might have one migration network for cluster nodes in the same cluster that is fast (10 GB), and a second migration network for cross-cluster migrations that is slower (1 GB). + +All Hyper-V hosts that can initiate or receive a live migration must have connectivity to a network that is configured to allow live migrations. Because live migration can occur between nodes in the same cluster, between nodes in different clusters, and between a cluster and a stand-alone Hyper-V host, make sure that all these servers can access a live migration-enabled network. + +### Storage traffic + +For a virtual machine to be highly available, all members of the Hyper-V cluster must access the virtual machine state. This state includes the configuration state and the virtual hard disks. To meet this requirement, you must have shared storage. + +In Windows Server, you can provide shared storage in two ways: + +- **Shared block storage**. Shared block storage options include Fibre Channel, Fibre Channel over Ethernet (FCoE), iSCSI, and shared Serial Attached SCSI (SAS). +- **File-based storage**. Remote file-based storage is provided through SMB 3.0. + +SMB 3.0 includes new functionality known as SMB Multichannel. SMB Multichannel automatically detects and uses multiple network interfaces to deliver high performance and highly reliable storage connectivity. + +By default, SMB Multichannel is enabled and requires no additional configuration. Use at least two network adapters of the same type and speed so that SMB Multichannel is in effect. Network adapters that support RDMA (Remote Direct Memory Access) are recommended but not required. + +SMB 3.0 also automatically discovers and takes advantage of available hardware offloads, such as RDMA. A feature known as SMB Direct supports the use of network adapters that have RDMA capability. SMB Direct provides the best performance possible while also reducing file server and client overhead. + +> [!NOTE] +> The NIC Teaming feature is incompatible with RDMA-capable network adapters. Therefore, if you intend to use the RDMA capabilities of the network adapter, don't team those adapters. + +Both iSCSI and SMB use the network to connect the storage to cluster members. Because reliable storage connectivity and performance are very important for Hyper-V virtual machines, use multiple networks (physical or logical) to ensure that these requirements are achieved. + +For more information about SMB Direct and SMB Multichannel, see [Improve Performance of a File Server with SMB Direct](/windows-server/storage/file-server/smb-direct). + +### Replica traffic + +Hyper-V Replica provides asynchronous replication of Hyper-V virtual machines between two hosting servers or Hyper-V clusters. Replica traffic occurs between the primary and Replica sites. + +Hyper-V Replica automatically discovers and uses available network interfaces to transmit replication traffic. To throttle and control the replica traffic bandwidth, define QoS policies with minimum bandwidth weight. + +If you use certificate-based authentication, Hyper-V Replica encrypts the traffic. If you use Kerberos-based authentication, traffic isn't encrypted. + +### Virtual machine access traffic + +Most virtual machines require some form of network or Internet connectivity. For example, workloads that run on virtual machines typically need external network connectivity to service client requests. This connectivity can include tenant access in a hosted cloud implementation. Because multiple subclasses of traffic exist, such as traffic that's internal to the datacenter and traffic that's external (for example, to a computer outside the datacenter or to the Internet), these virtual machines need one or more networks to communicate. + +To separate virtual machine traffic from the management operating system, use VLANs that aren't exposed to the management operating system. + +## How to isolate the network traffic on a Hyper-V cluster + +To provide the most consistent performance and functionality and to improve network security, isolate the different types of network traffic. + +> [!NOTE] +> If you want to have a physical or logical network that's dedicated to a specific traffic type, you must assign each physical or virtual network adapter to a unique subnet. For each cluster node, Failover Clustering recognizes only one IP address per subnet. + +### Isolate traffic on the management network + +Use a firewall or IPsec encryption, or both, to isolate management traffic. In addition, use auditing to ensure that only defined and allowed communication is transmitted through the management network. + +### Isolate traffic on the cluster network + +To isolate inter-node cluster traffic, configure a network to either allow cluster network communication or not to allow cluster network communication. For a network that allows cluster network communication, you can also configure whether to allow clients to connect through the network. This configuration includes client and management operating system access. + +A failover cluster can use any network that allows cluster network communication for cluster monitoring, state communication, and for CSV-related communication. + +To configure a network to allow or not to allow cluster network communication, use Failover Cluster Manager or Windows PowerShell. To use Failover Cluster Manager, select **Networks** in the navigation tree. In the **Networks** pane, right-click a network, then select **Properties**. + +:::image type="content" source="media/failover-cluster-network-recommendations/management-network-properties.png" alt-text="A screenshot of the Failover Cluster Manager Network Properties dialog showing options to allow cluster communication and client connectivity."::: + +The following Windows PowerShell example configures a network named *Management Network* to allow cluster and client connectivity. + +```powershell +(Get-ClusterNetwork -Name "Management Network").Role = 3 +``` + +The **Role** property has the following possible values. + +| Value | Network Setting | +| --- | --- | +| 0 | Do not allow cluster network communication | +| 1 | Allow cluster network communication only | +| 3 | Allow cluster network communication and client connectivity | + +The following table shows the recommended settings for each type of network traffic. Virtual machine access traffic isn't listed because you should isolate these networks from the management operating system by using VLANs that aren't exposed to the host. Therefore, virtual machine networks shouldn't appear in Failover Cluster Manager as cluster networks. + +| Network Type | Recommended Setting | +| --- | --- | +| Management | Both of the following: - Allow cluster network communication on this network - Allow clients to connect through this network | +| Cluster | Allow cluster network communication on this network **Note:** Clear the **Allow clients to connect through this network** check box. | +| Live migration | Allow cluster network communication on this network **Note:** Clear the **Allow clients to connect through this network** check box. | +| Storage | Do not allow cluster network communication on this network | +| Replica traffic | Both of the following: - Allow cluster network communication on this network - Allow clients to connect through this network | + +### Isolate traffic on the live migration network + +By default, live migration traffic uses the cluster network topology to discover available networks and to establish priority. However, you can manually configure live migration preferences to isolate live migration traffic to only the networks that you define. To do this, you can use Failover Cluster Manager or Windows PowerShell. To use Failover Cluster Manager, in the navigation tree, right-click **Networks**, then select **Live Migration Settings**. + +:::image type="content" source="media/failover-cluster-network-recommendations/live-migration-settings.png" alt-text="A screenshot of the Live Migration Settings dialog in Failover Cluster Manager listing available cluster networks and their priority order."::: + +The following Windows PowerShell example enables live migration traffic only on a network named *Migration_Network*. + +```powershell +Get-ClusterResourceType -Name "Virtual Machine" | Set-ClusterParameter -Name MigrationExcludeNetworks -Value ([String]::Join(";",(Get-ClusterNetwork | Where-Object {$_.Name -ne "Migration_Network"}).ID)) +``` + +### Isolate traffic on the storage network + +To isolate SMB storage traffic, use Windows PowerShell to set SMB Multichannel constraints. SMB Multichannel constraints restrict SMB communication between a given file server and the Hyper-V host to one or more defined network interfaces. + +For example, the following Windows PowerShell command sets a constraint for SMB traffic from the file server *FileServer1* to the network interfaces *SMB1*, *SMB2*, *SMB3*, and *SMB4* on the Hyper-V host from which you run this command. + +```powershell +New-SmbMultichannelConstraint -ServerName "FileServer1" -InterfaceAlias "SMB1", "SMB2", "SMB3", "SMB4" +``` + +> [!NOTE] +> +> - You must run this command on each node of the Hyper-V cluster. +> - To find the interface name, use the **Get-NetAdapter** cmdlet. + +For more information, see [New-SmbMultichannelConstraint](/powershell/module/smbshare/new-smbmultichannelconstraint). + +To isolate iSCSI traffic, configure the iSCSI target with interfaces on a dedicated network (logical or physical). Use the corresponding interfaces on the cluster nodes when you configure the iSCSI initiator. + +### Isolate traffic for replication + +To isolate Hyper-V Replica traffic, use a different subnet for the primary and Replica sites. + +If you want to isolate the replica traffic to a particular network adapter, define a persistent static route that redirects the network traffic to the defined network adapter. To specify a static route, use the following command: + +`route add mask if -p` + +For example, to add a static route to the 10.1.17.0 network (example network of the Replica site) that uses a subnet mask of 255.255.255.0, a gateway of 10.0.17.1 (example IP address of the primary site), where the interface number for the adapter that you want to dedicate to replica traffic is 8, run the following command: + +`route add 10.1.17.1 mask 255.255.255.0 10.0.17.1 if 8 -p` + +## NIC Teaming (LBFO) recommendations + +Team physical network adapters in the management operating system. This configuration provides bandwidth aggregation and network traffic failover if a network hardware failure or outage occurs. + +The NIC Teaming feature, also known as load balancing and failover (LBFO), provides two basic sets of algorithms for teaming. + +- **Switch-dependent modes**. Requires the switch to participate in the teaming process. Typically requires all the network adapters in the team to be connected to the same switch. +- **Switch-independent modes**. Doesn't require the switch to participate in the teaming process. Although not required, team network adapters can be connected to different switches. + +Both modes provide bandwidth aggregation and traffic failover if a network adapter failure or network disconnection occurs. However, in most cases only switch-independent teaming provides traffic failover for a switch failure. + +NIC Teaming also provides a traffic distribution algorithm that's optimized for Hyper-V workloads. This algorithm is referred to as the *Hyper-V port* load balancing mode. This mode distributes the traffic based on the MAC address of the virtual network adapters. The algorithm uses round robin as the load-balancing mechanism. For example, on a server that has two teamed physical network adapters and four virtual network adapters, the first and third virtual network adapter use the first physical adapter, and the second and fourth virtual network adapter use the second physical adapter. Hyper-V port mode also enables the use of hardware offloads such as virtual machine queue (VMQ) which reduces CPU overhead for networking operations. + +### NIC Teaming recommendations + +For a clustered Hyper-V deployment, use the following settings when you configure the additional properties of a team. + +| Property Name | Recommended Setting | +| --- | --- | +| Teaming mode | Switch Independent (the default setting) | +| Load balancing mode | Hyper-V Port | + +> [!NOTE] +> NIC teaming disables the RDMA capability of the network adapters. To use SMB Direct and the RDMA capability of the network adapters, don't use NIC Teaming. + +For more information about the NIC Teaming modes and how to configure NIC Teaming settings, see [Hyper-V Virtual Switch](/windows-server/virtualization/hyper-v/virtual-switch). + +## Quality of Service (QoS) recommendations + +Use QoS technologies that are available in Windows Server to meet the service requirements of a workload or an application. QoS provides the following features: + +- Measures network bandwidth, detects changing network conditions (such as congestion or availability of bandwidth), and prioritizes or throttles network traffic. +- Enables you to converge multiple types of network traffic on a single adapter. +- Includes a minimum bandwidth feature that guarantees a certain amount of bandwidth to a given type of traffic. + +Configure appropriate Hyper-V QoS on the virtual switch to ensure that network requirements are met for all appropriate types of network traffic on the Hyper-V cluster. + +> [!NOTE] +> You can use QoS to control outbound traffic, but not the inbound traffic. For example, with Hyper-V Replica, you can use QoS to control outbound traffic (from the primary server), but not the inbound traffic (from the Replica server). + +### QoS recommendations + +For a Hyper-V cluster, configure Hyper-V QoS that applies to the virtual switch. When you configure QoS, complete the following steps: + +- **Configure minimum bandwidth in weight mode instead of in bits per second.** Minimum bandwidth specified by weight is more flexible and it's compatible with other features, such as live migration and NIC Teaming. For more information, see the **MinimumBandwidthMode** parameter in [New-VMSwitch](/powershell/module/hyper-v/new-vmswitch). +- **Enable and configure QoS for all virtual network adapters.** Assign a weight to all virtual adapters. For more information, see [Set-VMNetworkAdapter](/powershell/module/hyper-v/set-vmnetworkadapter). To make sure that all virtual adapters have a weight, configure the **DefaultFlowMinimumBandwidthWeight** parameter on the virtual switch to a reasonable value. For more information, see [Set-VMSwitch](/powershell/module/hyper-v/set-vmswitch). + +The following table recommends some generic weight values. You can assign a value from 1 to 100. For guidelines to consider when you assign weight values, see [QoS minimum bandwidth best practices](network-quality-of-service-bandwidth-limits.md). + +| Network Classification | Weight | +| --- | --- | +| Default weight | 0 | +| Virtual machine access | 1, 3, or 5 (low, medium, and high-throughput virtual machines) | +| Cluster | 10 | +| Management | 10 | +| Replica traffic | 10 | +| Live migration | 40 | +| Storage | 40 | + +## Virtual machine queue (VMQ) recommendations + +Virtual machine queue (VMQ) is a feature that's available to computers that have VMQ-capable network hardware. VMQ uses hardware packet filtering to deliver packet data from an external virtual network directly to virtual network adapters. This feature reduces the overhead of routing packets. When you enable VMQ, a dedicated queue is established on the physical network adapter for each virtual network adapter that requests a queue. + +Not all physical network adapters support VMQ. Those that support VMQ have a fixed number of queues available, and the number varies. To determine whether a network adapter supports VMQ, and how many queues it supports, use the [Get-NetAdapterVmq](/powershell/module/netadapter/get-netadaptervmq) cmdlet. + +You can assign virtual machine queues to any virtual network adapter. This capability includes virtual network adapters that you expose to the management operating system. Assign queues according to a weight value, in a first-come first-serve manner. By default, all virtual adapters have a weight of 100. + +### VMQ recommendations + +Increase the VMQ weight for interfaces with heavy inbound traffic, such as storage and live migration networks. To do this, use the [Set-VMNetworkAdapter](/powershell/module/hyper-v/set-vmnetworkadapter) Windows PowerShell cmdlet. + +## Example of converged networking: routing traffic through one Hyper-V virtual switch + +The following Windows PowerShell script shows an example of how you can route traffic on a Hyper-V cluster through one Hyper-V external virtual switch. The example uses two physical 10 GB network adapters that are teamed by using the NIC Teaming feature. The script configures a Hyper-V cluster node with a management interface, a live migration interface, a cluster interface, and four SMB interfaces. After the script, there is more information about how to add an interface for Hyper-V Replica traffic. The following diagram shows the example network configuration. + +:::image type="content" source="media/failover-cluster-network-recommendations/converged-networking-diagram.png" alt-text="A diagram of a converged Hyper-V networking configuration using a teamed 10 Gb virtual switch with separate VLANs for management, cluster, live migration, and four SMB interfaces."::: + +The example also configures network isolation which restricts cluster traffic from the management interface, restricts SMB traffic to the SMB interfaces, and restricts live migration traffic to the live migration interface. + +```powershell +# Create a network team using switch independent teaming and Hyper-V port mode +New-NetLbfoTeam "PhysicalTeam" –TeamMembers "10GBPort1", "10GBPort2" –TeamNicName "PhysicalTeam" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm HyperVPort + +# Create a Hyper-V virtual switch connected to the network team +# Enable QoS in Weight mode +New-VMSwitch "TeamSwitch" –NetAdapterName "PhysicalTeam" –MinimumBandwidthMode Weight –AllowManagementOS $false + +# Configure the default bandwidth weight for the switch +# Ensures all virtual NICs have a weight +Set-VMSwitch -Name "TeamSwitch" -DefaultFlowMinimumBandwidthWeight 0 + +# Create virtual network adapters on the management operating system +# Connect the adapters to the virtual switch +# Set the VLAN associated with the adapter +# Configure the VMQ weight and minimum bandwidth weight +Add-VMNetworkAdapter –ManagementOS –Name "Management" –SwitchName "TeamSwitch" +Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Management" -Access -VlanId 10 +Set-VMNetworkAdapter -ManagementOS -Name "Management" -VmqWeight 80 -MinimumBandwidthWeight 10 + +Add-VMNetworkAdapter –ManagementOS –Name "Cluster" –SwitchName "TeamSwitch" +Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Cluster" -Access -VlanId 11 +Set-VMNetworkAdapter -ManagementOS -Name "Cluster" -VmqWeight 80 -MinimumBandwidthWeight 10 + +Add-VMNetworkAdapter –ManagementOS –Name "Migration" –SwitchName "TeamSwitch" +Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Migration" -Access -VlanId 12 +Set-VMNetworkAdapter -ManagementOS -Name "Migration" -VmqWeight 90 -MinimumBandwidthWeight 40 + +Add-VMNetworkAdapter –ManagementOS –Name "SMB1" –SwitchName "TeamSwitch" +Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "SMB1" -Access -VlanId 13 +Set-VMNetworkAdapter -ManagementOS -Name "SMB1" -VmqWeight 100 -MinimumBandwidthWeight 40 + +Add-VMNetworkAdapter –ManagementOS –Name "SMB2" –SwitchName "TeamSwitch" +Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "SMB2" -Access -VlanId 14 +Set-VMNetworkAdapter -ManagementOS -Name "SMB2" -VmqWeight 100 -MinimumBandwidthWeight 40 + +Add-VMNetworkAdapter –ManagementOS –Name "SMB3" –SwitchName "TeamSwitch" +Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "SMB3" -Access -VlanId 15 +Set-VMNetworkAdapter -ManagementOS -Name "SMB3" -VmqWeight 100 -MinimumBandwidthWeight 40 + +Add-VMNetworkAdapter –ManagementOS –Name "SMB4" –SwitchName "TeamSwitch" +Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "SMB4" -Access -VlanId 16 +Set-VMNetworkAdapter -ManagementOS -Name "SMB4" -VmqWeight 100 -MinimumBandwidthWeight 40 + +# Rename the cluster networks if desired +(Get-ClusterNetwork | Where-Object {$_.Address -eq "10.0.10.0"}).Name = "Management_Network" +(Get-ClusterNetwork | Where-Object {$_.Address -eq "10.0.11.0"}).Name = "Cluster_Network" +(Get-ClusterNetwork | Where-Object {$_.Address -eq "10.0.12.0"}).Name = "Migration_Network" +(Get-ClusterNetwork | Where-Object {$_.Address -eq "10.0.13.0"}).Name = "SMB_Network1" +(Get-ClusterNetwork | Where-Object {$_.Address -eq "10.0.14.0"}).Name = "SMB_Network2" +(Get-ClusterNetwork | Where-Object {$_.Address -eq "10.0.15.0"}).Name = "SMB_Network3" +(Get-ClusterNetwork | Where-Object {$_.Address -eq "10.0.16.0"}).Name = "SMB_Network4" + +# Configure the cluster network roles +(Get-ClusterNetwork -Name "Management_Network").Role = 3 +(Get-ClusterNetwork -Name "Cluster_Network").Role = 1 +(Get-ClusterNetwork -Name "Migration_Network").Role = 1 +(Get-ClusterNetwork -Name "SMB_Network1").Role = 0 +(Get-ClusterNetwork -Name "SMB_Network2").Role = 0 +(Get-ClusterNetwork -Name "SMB_Network3").Role = 0 +(Get-ClusterNetwork -Name "SMB_Network4").Role = 0 + +# Configure an SMB Multichannel constraint +# This ensures that SMB traffic from the named server only uses SMB interfaces +New-SmbMultichannelConstraint -ServerName "FileServer1" -InterfaceAlias "vEthernet (SMB1)", "vEthernet (SMB2)", "vEthernet (SMB3)", "vEthernet (SMB4)" + +# Configure the live migration network +Get-ClusterResourceType -Name "Virtual Machine" | Set-ClusterParameter -Name MigrationExcludeNetworks -Value ([String]::Join(";",(Get-ClusterNetwork | Where-Object {$_.Name -ne "Migration_Network"}).ID)) +``` + +### Hyper-V Replica considerations + +If you also use Hyper-V Replica in your environment, you can add another virtual network adapter to the management operating system for replica traffic. For example: + +```powershell +Add-VMNetworkAdapter –ManagementOS –Name "Replica" –SwitchName "TeamSwitch" +Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Replica" –Access –VlanId 17 +Set-VMNetworkAdapter -ManagementOS -Name "Replica" -VmqWeight 80 -MinimumBandwidthWeight 10 + +# If the host is clustered – configure the cluster name and role +(Get-ClusterNetwork | Where-Object {$_.Address -eq "10.0.17.0"}).Name = "Replica" +(Get-ClusterNetwork -Name "Replica").Role = 3 +``` + +> [!NOTE] +> If you're instead using policy-based QoS, where you can throttle outgoing traffic regardless of the interface on which it is sent, you can use either of the following methods to throttle Hyper-V Replica traffic: Create a QoS policy that is based on the destination port. In the following example, the network listener on the Replica server or cluster is configured to use port 8080 to receive replication traffic. + +## Appendix: Encryption + +### Cluster traffic encryption + +By default, cluster communication isn't encrypted. You can enable encryption if you want. However, encryption adds performance overhead. To enable encryption, use the following Windows PowerShell command to set the security level for the cluster. + +```powershell +(Get-Cluster). SecurityLevel = 2 +``` + +The following table shows the different security level values. + +| Security Description | Value | +| --- | --- | +| Clear text | 0 | +| Signed (default) | 1 | +| Encrypted | 2 | + +### Live migration traffic encryption + +Live migration traffic isn't encrypted. You can enable IPsec or other network layer encryption technologies if you want. However, encryption technologies typically affect performance. + +### SMB traffic + +By default, SMB traffic isn't encrypted. Therefore, use a dedicated network (physical or logical) or use encryption. For SMB traffic, you can use SMB encryption, layer-2, or layer-3 encryption. SMB encryption is the preferred method. + +### Replica traffic encryption + +If you use Kerberos-based authentication, Hyper-V Replica traffic isn't encrypted. Encrypt replication traffic that transits public networks over the WAN or the Internet. Use Secure Sockets Layer (SSL) encryption as the encryption method. You can also use IPsec. However, using IPsec might significantly affect performance. + diff --git a/WindowsServerDocs/virtualization/hyper-v/get-started/Create-a-virtual-machine-in-Hyper-V.md b/WindowsServerDocs/virtualization/hyper-v/get-started/Create-a-virtual-machine-in-Hyper-V.md index 58badc5829..b6e63b73e6 100644 --- a/WindowsServerDocs/virtualization/hyper-v/get-started/Create-a-virtual-machine-in-Hyper-V.md +++ b/WindowsServerDocs/virtualization/hyper-v/get-started/Create-a-virtual-machine-in-Hyper-V.md @@ -111,7 +111,7 @@ The following table lists the options you can pick when you create a virtual mac |--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| |**Specify Name and Location**|Name: New Virtual Machine.

        Location: **C:\ProgramData\Microsoft\Windows\Hyper-V\\**.|You can also enter your own name and choose another location for the virtual machine.

        This is where the virtual machine configuration files are stored.| |**Specify Generation**|Generation 1|You can also choose to create a Generation 2 virtual machine. For more information, see [Should I create a generation 1 or 2 virtual machine in Hyper-V?.](../plan/Should-I-create-a-generation-1-or-2-virtual-machine-in-Hyper-V.md)| -|**Assign Memory**|Startup memory: 1024 MB

        Dynamic memory: **not selected**|You can set the startup memory from 32 MB to 5902 MB.

        You can also choose to use Dynamic Memory. For more information, see [Hyper-V Dynamic Memory Overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831766(v=ws.11)).| +|**Assign Memory**|Startup memory: 1024 MB

        Dynamic memory: **not selected**|You can set the startup memory from 32 MB to 5902 MB.

        You can also choose to use Dynamic Memory. For more information, see [Hyper-V Dynamic Memory Overview](../dynamic-memory.md).| |**Configure Networking**|Not connected|You can select a network connection for the virtual machine to use from a list of existing virtual switches. See [Create a virtual switch for Hyper-V virtual machines](Create-a-virtual-switch-for-Hyper-V-virtual-machines.md).| |**Connect Virtual Hard Disk**|Create a virtual hard disk

        Name: <*vmname*>.vhdx

        **Location**: **C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\\**

        **Size**: 127 GB|You can also choose to use an existing virtual hard disk or wait and attach a virtual hard disk later.| |**Installation Options**|Install an operating system later|These options change the boot order of the virtual machine so that you can install from an .iso file, bootable floppy disk or a network installation service, like Windows Deployment Services (WDS).| diff --git a/WindowsServerDocs/virtualization/hyper-v/host-hardware-requirements.md b/WindowsServerDocs/virtualization/hyper-v/host-hardware-requirements.md index 5de438948d..adef0ea5f1 100644 --- a/WindowsServerDocs/virtualization/hyper-v/host-hardware-requirements.md +++ b/WindowsServerDocs/virtualization/hyper-v/host-hardware-requirements.md @@ -16,7 +16,7 @@ Hyper-V has specific hardware requirements, and some Hyper-V features have other Then review the [Windows Server catalog](https://www.windowsservercatalog.com/). Keep in mind that requirements for Hyper-V exceed the general minimum requirements for Windows Server because a virtualization environment requires more computing resources. -If you're already using Hyper-V, it's likely that you can use your existing hardware. The general hardware requirements have changed minimally from Windows Server 2012 R2, but you need newer hardware to use shielded virtual machines or discrete device assignment. Those features rely on specific hardware support, as described later in this article. Other than that, the main difference in hardware is that second-level address translation (SLAT) is now required instead of recommended. +If you're already using Hyper-V, it's likely that you can use your existing hardware. The general hardware requirements have changed minimally from Windows Server 2012 R2, but you need newer hardware to use shielded virtual machines or discrete device assignment. Those features rely on specific hardware support, as described later in this article. Other than that, the main difference in hardware is that second-level address translation (SLAT) is now required instead of recommended. For details about maximum supported configurations for Hyper-V, such as the number of running virtual machines, see [Plan for Hyper-V scalability in Windows Server](../hyper-v/maximum-scale-limits.md). The list of operating systems you can run in your virtual machines is covered in [Supported Windows guest operating systems for Hyper-V on Windows Server](Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md). diff --git a/WindowsServerDocs/virtualization/hyper-v/integration-services-data-exchange.md b/WindowsServerDocs/virtualization/hyper-v/integration-services-data-exchange.md new file mode 100644 index 0000000000..7e72541196 --- /dev/null +++ b/WindowsServerDocs/virtualization/hyper-v/integration-services-data-exchange.md @@ -0,0 +1,497 @@ +--- +title: "Data Exchange: Using key-value pairs to share information between the host and guest on Hyper-V" +description: Learn how the Hyper-V Data Exchange (KVP) integration service lets you share small bits of metadata between a virtual machine and the Hyper-V host using key-value pairs. +keywords: hyper-v, integration services, data exchange, kvp, key value pair +author: dknappettmsft +ms.author: daknappe +ms.date: 10/27/2025 +ms.topic: how-to +--- + +# Data Exchange: Using key-value pairs to share information between the host and guest on Hyper-V + +Data Exchange is an integration service (also known as key-value pair exchange or KVP) that can be used to share small pieces of information between a virtual machine (guest) and its Hyper-V host. General information about the virtual machine and host is automatically created and stored as key-value pairs. You can also create your own pairs to share custom data. + +Key-value pairs consist of a "key" and a "value". Both are strings; no other data types are supported. When a key-value pair is created or changed, it becomes visible to both the guest and the host. KVP data travels over the Hyper-V VMbus and doesn't require any network connectivity between the guest and host. + +Once created, key-value pairs remain until they're deleted. Any application that creates key-value pairs should delete them when they're no longer needed. Key-value pairs move with the virtual machine during Live Migration. + +## Windows guests + +On Windows guests, KVP data is stored in the registry under: + +```text +HKLM\SOFTWARE\Microsoft\Virtual Machine +``` + +The data is organized in these subkeys: + +- **Virtual Machine\\Auto** – Data describing the guest. Created by integration service drivers after they load. Visible to the host as intrinsic data. +- **Virtual Machine\\External** – Data pushed to the guest from the host by a user. +- **Virtual Machine\\Guest** – Data created on the guest. Visible to the host as non‑intrinsic data. +- **Virtual Machine\\Guest\\Parameter** – Data pushed to the guest from the host that describes the host. + +Adding values from within the guest is as simple as creating a new string value under `HKLM\SOFTWARE\Microsoft\Virtual Machine\Guest`. You must be an administrator in the guest to modify this location. You can use WMI (PowerShell or other tooling) from the host or a remote machine (with permissions) to retrieve the value. + +For information about registry size limits, see the (legacy) article [Registry Element Size Limits](https://msdn.microsoft.com/library/windows/desktop/ms724872.aspx). + +### Add a new key-value pair in the guest + +In this example, the value of **Status** is set to `Ready`: + +```powershell +$regPath = "HKLM:\SOFTWARE\Microsoft\Virtual Machine\Guest" +Set-ItemProperty -Path $regPath -Name "Status" -Value "Ready" -Type String +``` + +You can use the same syntax to change the value. + +### Query key-value pairs in the guest + +To query the value of the **External** subkey (data pushed to the guest from the host): + +```powershell +$regPath = "HKLM:\SOFTWARE\Microsoft\Virtual Machine\External" +Get-ItemProperty -Path $regPath -Name "Name" +``` + +## Linux guests + +Linux doesn't have a registry, so KVP items are stored in the file system. A daemon process, `hv_kvp_daemon`, must be running to handle processing. For most distributions with Linux Integration Services (LIS) or in-kernel drivers installed, this daemon starts automatically. In some cases, extra steps may be required to install and start the daemon. + +The Linux integration services implement data exchange with KVP pools. A KVP pool is a file stored in a specific path. There are four pool files: + +```text +/var/lib/hyperv/.kvp_pool_0 +/var/lib/hyperv/.kvp_pool_1 +/var/lib/hyperv/.kvp_pool_2 +/var/lib/hyperv/.kvp_pool_3 +``` + +These pool files map to the following Windows registry key sets: + +- Pool 0: `Virtual Machine\External` +- Pool 1: `Virtual Machine\Guest` +- Pool 2: `Virtual Machine\Auto` +- Pool 3: `Virtual Machine\Guest\Parameter` + +> [!NOTE] +> For more information about Linux KVP support, see [Linux and FreeBSD Virtual Machines on Hyper-V](Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md). +> +> The key-value pair infrastructure might not function correctly without a Linux software update. Contact your distribution vendor for an update if you encounter issues. + +### Pool structure + +Each pool file contains records with this structure: + +```c +struct kvp_record +{ + unsigned char key[ HV_KVP_EXCHANGE_MAK_KEY_SIZE ]; + unsigned char value[ HV_KVP_EXCHANGE_MAX_VALUE_SIZE ]; +}; +``` + +Those size constants are defined in `hyperv.h` (a kernel header distributed with the Linux kernel sources). + +### Read and display values from pool 0 + +This sample reads KVP values from pool 0 and displays them. + +```c +```c +#include +#include +#include +#include +#include +#include +#include "../include/linux/hyperv.h" + +typedef struct kvp_record +{ + unsigned char key [HV_KVP_EXCHANGE_MAX_KEY_SIZE]; + unsigned char value [HV_KVP_EXCHANGE_MAX_VALUE_SIZE]; +} KVP_RECORD; + +KVP_RECORD myRecords[200]; + +void KVPAcquireLock(int fd) +{ + struct flock fl = {F_RDLCK, SEEK_SET, 0, 0, 0}; + fl.l_pid = getpid(); + + if (-1 == fcntl(fd, F_SETLKW, &fl)) + { + perror("fcntl lock"); + exit (-10); + } +} + +void KVPReleaseLock(int fd) +{ + struct flock fl = {F_UNLCK, SEEK_SET, 0, 0, 0}; + fl.l_pid = getpid(); + + if (-1 == fcntl(fd, F_SETLK, &fl)) + { + perror("fcntl unlock"); + exit (-20); + } +} + +int main (int argc, char **argv) +{ + char poolName[] = "/var/lib/hyperv/.kvp_pool_0"; + int i; + int fd; + int bytesRead; + int numRecords; + + fd = open(poolName, O_RDONLY); + if (-1 == fd) + { + printf("Error: Unable to open pool file %s\n", poolName); + exit (-30); + } + + KVPAcquireLock(fd); + bytesRead = read(fd, myRecords, sizeof(myRecords)); + KVPReleaseLock(fd); + + numRecords = bytesRead / sizeof(struct kvp_record); + printf("Number of records : %d\n", numRecords); + + for (i = 0; i < numRecords; i++) + { + printf(" Key : %s\n Value: %s\n\n", myRecords[i].key, myRecords[i].value); + } + + close(fd); + + return 0; +} +``` + +### Create a KVP item in pool 1 + +```c +#include +#include +#include +#include +#include +#include +#include "../include/linux/hyperv.h" + +typedef struct kvp_record +{ + unsigned char key [HV_KVP_EXCHANGE_MAX_KEY_SIZE]; + unsigned char value [HV_KVP_EXCHANGE_MAX_VALUE_SIZE]; +} KVP_RECORD; + +void KVPAcquireWriteLock(int fd) +{ + struct flock fl = {F_WRLCK, SEEK_SET, 0, 0, 0}; + fl.l_pid = getpid(); + + if (-1 == fcntl(fd, F_SETLKW, &fl)) + { + perror("fcntl lock"); + exit (-10); + } +} + +void KVPReleaseLock(int fd) +{ + struct flock fl = {F_UNLCK, SEEK_SET, 0, 0, 0}; + fl.l_pid = getpid(); + + if (-1 == fcntl(fd, F_SETLK, &fl)) + { + perror("fcntl unlock"); + exit (-20); + } +} + +int main (int argc, char **argv) +{ + char poolName[] = "/var/lib/hyperv/.kvp_pool_1"; + int fd; + KVP_RECORD newKvp; + + if (3 != argc) + { + printf("Usage: WritePool keyName valueString\n\n"); + exit (-5); + } + + fd = open(poolName, O_WRONLY); + if (-1 == fd) + { + printf("Error: Unable to open pool file %s\n", poolName); + exit (-30); + } + + memset((void *)&newKvp, 0, sizeof(KVP_RECORD)); + memcpy(newKvp.key, argv[1], strlen(argv[1])); + memcpy(newKvp.value, argv[2], strlen(argv[2])); + + KVPAcquireWriteLock(fd); + write(fd, (void *)&newKvp, sizeof(KVP_RECORD)); + KVPReleaseLock(fd); + + close(fd); + + return 0; +} +``` + +### Delete a KVP item from pool 1 + +This sample deletes an item. + +```c +#include +#include +#include +#include +#include +#include +#include + +typedef struct kvp_record +{ + unsigned char key [HV_KVP_EXCHANGE_MAX_KEY_SIZE]; + unsigned char value [HV_KVP_EXCHANGE_MAX_VALUE_SIZE]; +} KVP_RECORD; + +void KVPAcquireWriteLock(int fd) +{ + struct flock fl = {F_WRLCK, SEEK_SET, 0, 0, 0}; + fl.l_pid = getpid(); + + if (-1 == fcntl(fd, F_SETLKW, &fl)) + { + perror("fcntl lock"); + exit (-10); + } +} + +void KVPReleaseLock(int fd) +{ + struct flock fl = {F_UNLCK, SEEK_SET, 0, 0, 0}; + fl.l_pid = getpid(); + + if (-1 == fcntl(fd, F_SETLK, &fl)) + { + perror("fcntl unlock"); + exit (-20); + } +} + +int find_record_offset(int fd, char *key) +{ + int bytesRead; + int offset = 0; + int retval = -1; + + KVP_RECORD kvpRec; + + while (1) + { + lseek(fd, offset, SEEK_SET); + bytesRead = read(fd, &kvpRec, sizeof(KVP_RECORD)); + if (0 == bytesRead) + { + break; + } + + if (0 == strcmp(key, (const char *) kvpRec.key)) + { + retval = offset; + break; + } + + offset += sizeof(KVP_RECORD); + } + + return retval; +} + +int main (int argc, char **argv) +{ + char poolName[] = "/var/lib/hyperv/.kvp_pool_1"; + int fd; + int exitVal = -1; + int bytesRead; + int bytesWritten; + int offset_to_delete; + int offset_last_record; + KVP_RECORD kvpRec; + + if (2 != argc) + { + printf("Usage: WritePool keyName valueString\n\n"); + exit (-5); + } + + fd = open(poolName, O_RDWR, 0644); + if (-1 == fd) + { + printf("Error: Unable to open pool file %s\n", poolName); + exit (-10); + } + + KVPAcquireWriteLock(fd); + offset_to_delete = find_record_offset(fd, argv[1]); + if (offset_to_delete < 0) + { + exitVal = -15; + goto cleanup2; + } + + offset_last_record = lseek(fd, -sizeof(KVP_RECORD), SEEK_END); + if (offset_last_record < 0) + { + exitVal = -20; + goto cleanup2; + } + + if (offset_last_record != offset_to_delete) + { + lseek(fd, offset_last_record, SEEK_SET); + bytesRead = read(fd, &kvpRec, sizeof(KVP_RECORD)); + lseek(fd, offset_to_delete, SEEK_SET); + bytesWritten = write(fd, &kvpRec, sizeof(KVP_RECORD)); + } + + ftruncate(fd, offset_last_record); + + exitVal = 0; + +cleanup2: + KVPReleaseLock(fd); + +cleanup1: + close(fd); + + return exitVal; +} +``` + +## Working with key-value pairs from the host using WMI + +The following examples use the WMI v2 namespace. For WMI v1 (older versions), remove the `\v2` segment from the namespace path. + +> [!NOTE] +> If you're using Windows 8 or Windows 8.1, install Client Hyper-V to get the namespaces. + +### Read the value from the host + +This example gets the value of the key `Status` from a VM named `Vm1`: + +```powershell +$vm = Get-WmiObject -Namespace root\virtualization\v2 -Class \ + Msvm_ComputerSystem -Filter {ElementName = 'Vm1'} +$vm.GetRelated("Msvm_KvpExchangeComponent").GuestExchangeItems | % { \ + $GuestExchangeItemXml = ([XML]$_).SelectSingleNode(\ + "/INSTANCE/PROPERTY[@NAME='Name']/VALUE[child::text() = 'Status']") + if ($GuestExchangeItemXml -ne $null) + { + $GuestExchangeItemXml.SelectSingleNode(\ + "/INSTANCE/PROPERTY[@NAME='Data']/VALUE/child::text()" ).Value + } +} +``` + +### Add or modify key-value pairs from the host + +To add a key-value pair from the host, get instances of both the management service and the VM and create a new instance of `Msvm_KvpExchangeDataItem`. When creating the new instance, specify the `Name`, `Data`, and `Source` (must be `0`). Then call `AddKvpItems`. + +Querying for host-created key-value pairs is similar to guest queries but requires an additional association hop to `Msvm_KvpExchangeComponentSettingData`. Modifying and deleting values works the same way—specify the same key name and call the appropriate `Modify` or `Remove` method. + +> [!IMPORTANT] +> The examples below use the v2 namespace. If you're using Windows Server 2008 or Windows Server 2008 R2, remove the `\v2` segment. + +### Add a new key-value pair + +```powershell +$VmMgmt = Get-WmiObject -Namespace root\virtualization\v2 -Class \ + Msvm_VirtualSystemManagementService +$vm = Get-WmiObject -Namespace root\virtualization\v2 -Class \ + Msvm_ComputerSystem -Filter {ElementName='VM1'} +$kvpDataItem = ([WMIClass][String]::Format("\\{0}\\{1}:{2}", \ + $VmMgmt.ClassPath.Server, \ + $VmMgmt.ClassPath.NamespacePath, \ + "Msvm_KvpExchangeDataItem")).CreateInstance() + +$kvpDataItem.Name = "Name" +$kvpDataItem.Data = "Data" +$kvpDataItem.Source = 0 + +$VmMgmt.AddKvpItems($Vm, $kvpDataItem.PSBase.GetText(1)) +``` + +### Query key-value pairs on the host + +```powershell +$VmMgmt = Get-WmiObject -Namespace root\virtualization\v2 -Class \ + Msvm_VirtualSystemManagementService +$vm = Get-WmiObject -Namespace root\virtualization\v2 -Class \ + Msvm_ComputerSystem -Filter {ElementName='VM1'} +($vm.GetRelated("Msvm_KvpExchangeComponent")[0] ).GetRelated("Msvm_KvpExchangeComponentSettingData").HostExchangeItems | % { \ + $GuestExchangeItemXml = ([XML]$_).SelectSingleNode(\ + "/INSTANCE/PROPERTY[@NAME='Name']/VALUE[child::text() = 'Name2']") + if ($GuestExchangeItemXml -ne $null) + { + $GuestExchangeItemXml.SelectSingleNode(\ + "/INSTANCE/PROPERTY[@NAME='Data']/VALUE/child::text()" ).Value + } +} +``` + +### Modify a key-value pair + +```powershell +$VmMgmt = Get-WmiObject -Namespace root\virtualization\v2 -Class \ + Msvm_VirtualSystemManagementService +$vm = Get-WmiObject -Namespace root\virtualization\v2 -Class \ + Msvm_ComputerSystem -Filter {ElementName='VM1'} +$kvpDataItem = ([WMIClass][String]::Format("\\{0}\\{1}:{2}", \ + $VmMgmt.ClassPath.Server, \ + $VmMgmt.ClassPath.NamespacePath, \ + "Msvm_KvpExchangeDataItem")).CreateInstance() + +$kvpDataItem.Name = "Name" +$kvpDataItem.Data = "Data2" +$kvpDataItem.Source = 0 + +$VmMgmt.ModifyKvpItems($Vm, $kvpDataItem.PSBase.GetText(1)) +``` + +### Remove a key-value pair + +```powershell +$VmMgmt = Get-WmiObject -Namespace root\virtualization\v2 -Class \ + Msvm_VirtualSystemManagementService +$vm = Get-WmiObject -Namespace root\virtualization\v2 -Class \ + Msvm_ComputerSystem -Filter {ElementName='VM1'} +$kvpDataItem = ([WMIClass][String]::Format("\\{0}\\{1}:{2}", \ + $VmMgmt.ClassPath.Server, \ + $VmMgmt.ClassPath.NamespacePath, \ + "Msvm_KvpExchangeDataItem")).CreateInstance() + +$kvpDataItem.Name = "Name" +$kvpDataItem.Data = [String]::Empty +$kvpDataItem.Source = 0 + +$VmMgmt.RemoveKvpItems($Vm, $kvpDataItem.PSBase.GetText(1)) +``` + +## See also + +- [Hyper-V integration services](integration-services.md) +- [Supported Linux and FreeBSD virtual machines for Hyper-V on Windows](Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md) +- [PowerShell Direct](powershell-direct.md) + diff --git a/WindowsServerDocs/virtualization/hyper-v/integration-services.md b/WindowsServerDocs/virtualization/hyper-v/integration-services.md index 39f3a5bd5d..13b1c4d7ec 100644 --- a/WindowsServerDocs/virtualization/hyper-v/integration-services.md +++ b/WindowsServerDocs/virtualization/hyper-v/integration-services.md @@ -10,23 +10,23 @@ ms.topic: concept-article # Hyper-V integration services -Integration services (often called integration components), are services that allow the virtual machine to communicate with the Hyper-V host. Many of these services are conveniences while others can be quite important to the virtual machine's ability to function correctly. +Integration services, often called integration components, are services that allow the virtual machine to communicate with the Hyper-V host. Many of these services are conveniences, while others are important to the virtual machine's ability to function correctly. -This article is a reference for each integration service available in Windows. It'll also act as a starting point for any information related to specific integration services or their history. +This article is a reference for each integration service available in Windows. It also acts as a starting point for information related to specific integration services or their history. -For more information, you can reference the Windows Server guide on [Managing integration services](/windows-server/virtualization/hyper-v/manage/Manage-Hyper-V-integration-services). +For more information, see the Windows Server guide on [Managing integration services](/windows-server/virtualization/hyper-v/manage/Manage-Hyper-V-integration-services). ## Quick reference | Name | Windows Service Name | Linux Daemon Name | Description | Impact on VM when disabled | |:---------|:---------|:---------|:---------|:---------| -| [Hyper-V Heartbeat Service](#hyper-v-heartbeat-service) | vmicheartbeat | hv_utils | Reports that the virtual machine is running correctly. | Varies | -| [Hyper-V Guest Shutdown Service](#hyper-v-guest-shutdown-service) | vmicshutdown | hv_utils | Allows the host to trigger virtual machines shutdown. | **High** | -| [Hyper-V Time Synchronization Service](#hyper-v-time-synchronization-service) | vmictimesync | hv_utils | Synchronizes the virtual machine's clock with the host computer's clock. | **High** | -| [Hyper-V Data Exchange Service (KVP)](#hyper-v-data-exchange-service-kvp) | vmickvpexchange | hv_kvp_daemon | Provides a way to exchange basic metadata between the virtual machine and the host. | Medium | -| [Hyper-V Volume Shadow Copy Requestor](#hyper-v-volume-shadow-copy-requestor) | vmicvss | hv_vss_daemon | Allows Volume Shadow Copy Service to back up the virtual machine with out shutting it down. | Varies | -| [Hyper-V Guest Service Interface](#hyper-v-powershell-direct-service) | vmicguestinterface | hv_fcopy_daemon | Provides an interface for the Hyper-V host to copy files to or from the virtual machine. | Low | -| [Hyper-V PowerShell Direct Service](#hyper-v-powershell-direct-service) | vmicvmsession | not available | Provides a way to manage virtual machine with PowerShell without a network connection. | Low | +| [Hyper-V Heartbeat Service](#hyper-v-heartbeat-service) | `vmicheartbeat` | `hv_utils` | Reports that the virtual machine is running correctly. | Varies | +| [Hyper-V Guest Shutdown Service](#hyper-v-guest-shutdown-service) | `vmicshutdown` | `hv_utils` | Allows the host to trigger virtual machines shutdown. | **High** | +| [Hyper-V Time Synchronization Service](#hyper-v-time-synchronization-service) | `vmictimesync` | `hv_utils` | Synchronizes the virtual machine's clock with the host computer's clock. | **High** | +| [Hyper-V Data Exchange Service (KVP)](#hyper-v-data-exchange-service-kvp) | `vmickvpexchange` | `hv_kvp_daemon` | Provides a way to exchange basic metadata between the virtual machine and the host. | Medium | +| [Hyper-V Volume Shadow Copy Requestor](#hyper-v-volume-shadow-copy-requestor) | `vmicvss` | `hv_vss_daemon` | Allows Volume Shadow Copy Service to back up the virtual machine without shutting it down. | Varies | +| [Hyper-V Guest Service Interface](#hyper-v-powershell-direct-service) | `vmicguestinterface` | `hv_fcopy_daemon` | Provides an interface for the Hyper-V host to copy files to or from the virtual machine. | Low | +| [Hyper-V PowerShell Direct Service](#hyper-v-powershell-direct-service) | `vmicvmsession` | not available | Provides a way to manage virtual machine with PowerShell without a network connection. | Low | ## Hyper-V heartbeat service @@ -34,11 +34,11 @@ For more information, you can reference the Windows Server guide on [Managing in **Linux Daemon Name:** hv_utils **Description:** Tells the Hyper-V host that the virtual machine has an operating system installed and that it booted correctly. **Added In:** Windows Server 2012, Windows 8 -**Impact:** When disabled, the virtual machine can't report that the operating system inside of the virtual machine is operating correctly. This may impact some kinds of monitoring and host-side diagnostics. +**Impact:** When disabled, the virtual machine can't report that the operating system inside of the virtual machine is operating correctly. This limitation might affect some kinds of monitoring and host-side diagnostics. The heartbeat service makes it possible to answer basic questions like "did the virtual machine boot?". -When Hyper-V reports that a virtual machine state is "running" (see the example below), it means Hyper-V set aside resources for a virtual machine; it does not mean that there is an operating system installed or functioning. This is where heartbeat becomes useful. The heartbeat service tells Hyper-V that the operating system inside the virtual machine has booted. +When Hyper-V reports that a virtual machine state is "running" (see the example in the following section), it means Hyper-V set aside resources for a virtual machine; it doesn't mean that an operating system is installed or functioning. This limitation is where heartbeat becomes useful. The heartbeat service tells Hyper-V that the operating system inside the virtual machine has booted. ### Check heartbeat with PowerShell @@ -60,43 +60,43 @@ The `Status` field is determined by the heartbeat service. ## Hyper-V guest shutdown service -**Windows Service Name:** vmicshutdown -**Linux Daemon Name:** hv_utils -**Description:** Allows the Hyper-V host to request that the virtual machine shutdown. The host can always force the virtual machine to turn off, but that is like flipping the power switch as opposed to selecting shutdown. +**Windows Service Name:** `vmicshutdown` +**Linux Daemon Name:** `hv_utils` +**Description:** Allows the Hyper-V host to request that the virtual machine shut down. The host can always force the virtual machine to turn off, but that action is like flipping the power switch as opposed to selecting shutdown. **Added In:** Windows Server 2012, Windows 8 -**Impact:** **High Impact** When disabled, the host can't trigger a friendly shutdown inside the virtual machine. All shutdowns will be a hard power-off, which could cause data loss or data corruption. +**Impact:** **High Impact** When disabled, the host can't trigger a friendly shutdown inside the virtual machine. All shutdowns are hard power-offs, which could cause data loss or data corruption. ## Hyper-V time synchronization service -**Windows Service Name:** vmictimesync -**Linux Daemon Name:** hv_utils +**Windows Service Name:** `vmictimesync` +**Linux Daemon Name:** `hv_utils` **Description:** Synchronizes the virtual machine's system clock with the system clock of the physical computer. **Added In:** Windows Server 2012, Windows 8 -**Impact:** **High Impact** When disabled, the virtual machine's clock will drift erratically. +**Impact:** **High Impact** When disabled, the virtual machine's clock drifts erratically. ## Hyper-V data exchange service (KVP) -**Windows Service Name:** vmickvpexchange -**Linux Daemon Name:** hv_kvp_daemon +**Windows Service Name:** `vmickvpexchange` +**Linux Daemon Name:** `hv_kvp_daemon` **Description:** Provides a mechanism to exchange basic metadata between the virtual machine and the host. **Added In:** Windows Server 2012, Windows 8 -**Impact:** When disabled, virtual machines running Windows 8 or Windows Server 2012 or earlier will not receive updates to Hyper-V integration services. Disabling data exchange may also impact some kinds of monitoring and host-side diagnostics. +**Impact:** When disabled, virtual machines running Windows 8 or Windows Server 2012 or earlier don't receive updates to Hyper-V integration services. Disabling data exchange might also affect some kinds of monitoring and host-side diagnostics. -The data exchange service (sometimes called KVP) shares small amounts of machine information between virtual machine and the Hyper-V host using key-value pairs (KVP) through the Windows registry. The same mechanism can also be used to share customized data between the virtual machine and the host. +The data exchange service (sometimes called KVP) shares small amounts of machine information between virtual machine and the Hyper-V host by using key-value pairs (KVP) through the Windows registry. You can also use the same mechanism to share customized data between the virtual machine and the host. -Key-value pairs consist of a “key” and a “value”. Both the key and the value are strings, no other data types are supported. When a key-value pair is created or changed, it is visible to the guest and the host. The key-value pair information is transferred across the Hyper-V VMbus and does not require any kind of network connection between the guest and the Hyper-V host. +Key-value pairs consist of a “key” and a “value”. Both the key and the value are strings, and no other data types are supported. When you create or change a key-value pair, both the guest and the host can see it. The key-value pair information transfers across the Hyper-V VMbus and doesn't require any kind of network connection between the guest and the Hyper-V host. -The data exchange service is a great tool for preserving information about the virtual machine -- for interactive data sharing or data transfer, use [PowerShell Direct](#hyper-v-powershell-direct-service). +The data exchange service is a great tool for preserving information about the virtual machine. For interactive data sharing or data transfer, use [PowerShell Direct](#hyper-v-powershell-direct-service). -Learn more about [Using key-value pairs to share information between the host and guest on Hyper-V](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn798287(v=ws.11)). +Learn more about [Using key-value pairs to share information between the host and guest on Hyper-V](integration-services-data-exchange.md). ## Hyper-V Volume Shadow Copy Requestor -**Windows Service Name:** vmicvss -**Linux Daemon Name:** hv_vss_daemon +**Windows Service Name:** `vmicvss` +**Linux Daemon Name:** `hv_vss_daemon` **Description:** Allows Volume Shadow Copy Service to back up applications and data on the virtual machine. **Added In:** Windows Server 2012, Windows 8 -**Impact:** When disabled, the virtual machine can not be backed up while running (using VSS). +**Impact:** When disabled, the virtual machine can't be backed up while running (using VSS). The Volume Shadow Copy Requestor integration service is required for Volume Shadow Copy Service ([VSS](/windows/desktop/VSS/overview-of-processing-a-backup-under-vss)). The Volume Shadow Copy Service (VSS) captures and copies images for backup on running systems, particularly servers, without unduly degrading the performance and stability of the services they provide. This integration service makes that possible by coordinating the virtual machine's workloads with the host's backup process. @@ -104,30 +104,30 @@ Read more about Volume Shadow Copy in [Backing Up and Restoring Virtual Machines ## Hyper-V Guest Service Interface -**Windows Service Name:** vmicguestinterface -**Linux Daemon Name:** hv_fcopy_daemon +**Windows Service Name:** `vmicguestinterface` +**Linux Daemon Name:** `hv_fcopy_daemon` **Description:** Provides an interface for the Hyper-V host to bidirectionally copy files to or from the virtual machine. **Added In:** Windows Server 2012 R2, Windows 8.1 -**Impact:** When disabled, the host can not copy files to and from the guest using `Copy-VMFile`. Read more about the [Copy-VMFile cmdlet](/powershell/module/hyper-v/copy-vmfile). +**Impact:** When disabled, the host can't copy files to and from the guest using `Copy-VMFile`. Read more about the [Copy-VMFile cmdlet](/powershell/module/hyper-v/copy-vmfile). **Notes:** Disabled by default. See [PowerShell Direct using Copy-Item](powershell-direct.md#copy-files-with-new-pssession-and-copy-item). ## Hyper-V PowerShell Direct Service -**Windows Service Name:** vmicvmsession +**Windows Service Name:** `vmicvmsession` **Linux Daemon Name:** n/a -**Description:** Provides a mechanism to manage virtual machine with PowerShell via VM session without a virtual network. +**Description:** Provides a mechanism to manage a virtual machine with PowerShell through a VM session without a virtual network. **Added In:** Windows Server TP3, Windows 10 -**Impact:** Disabling this service prevents the host from being able to connect to the virtual machine with PowerShell Direct. +**Impact:** If you disable this service, the host can't connect to the virtual machine with PowerShell Direct. **Notes:** -The service name was originally was Hyper-V VM Session Service. -PowerShell Direct is under active development and only available on Windows 10/Windows Server Technical Preview 3 or later hosts/guests. +The service name was originally Hyper-V VM Session Service. +PowerShell Direct is under active development and is only available on Windows 10/Windows Server Technical Preview 3 or later hosts and guests. -PowerShell Direct allows PowerShell management inside a virtual machine from the Hyper-V host regardless of any network configuration or remote management settings on either the Hyper-V host or the virtual machine. This makes it easier for Hyper-V Administrators to automate and script management and configuration tasks. +PowerShell Direct enables PowerShell management inside a virtual machine from the Hyper-V host, regardless of any network configuration or remote management settings on either the Hyper-V host or the virtual machine. This feature makes it easier for Hyper-V administrators to automate and script management and configuration tasks. -The following resources may be helpful for managing PowerShell Direct: +The following resources might be helpful for managing PowerShell Direct: - [PowerShell Direct](powershell-direct.md). - [Running script in a virtual machine](powershell-direct.md#run-a-script-or-command-with-invoke-command) diff --git a/WindowsServerDocs/virtualization/hyper-v/manage/live-migration-workgroup-cluster.md b/WindowsServerDocs/virtualization/hyper-v/manage/live-migration-workgroup-cluster.md index 550b65921e..3ea17f34b7 100644 --- a/WindowsServerDocs/virtualization/hyper-v/manage/live-migration-workgroup-cluster.md +++ b/WindowsServerDocs/virtualization/hyper-v/manage/live-migration-workgroup-cluster.md @@ -191,10 +191,9 @@ Finally, do a live migration to move a running virtual machine. ## Next steps -After completing a live migration, it's important to confirm that the migration works, and all virtual machines migrated were migrated successfully. If you notice any issues during or after a migration, it might be necessary to revisit the simultaneous migrations allowed or configure live migration performance options. +After completing a live migration, it's important to confirm that the migration works, and all virtual machines migrated were migrated successfully. If you notice any issues during or after a migration, it might be necessary to revisit the simultaneous migrations allowed or configure live migration performance options. To learn more about Live Migration performance options, see -[Virtual Machine Live Migration Overview](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831435(v=ws.11)) +[Virtual Machine Live Migration Overview](live-migration-overview.md). You can also read more about live migration performance in [Hyper-V Network I/O Performance](/windows-server/administration/performance-tuning/role/hyper-v-server/network-io-performance). - diff --git a/WindowsServerDocs/virtualization/hyper-v/media/failover-cluster-network-recommendations/converged-networking-diagram.png b/WindowsServerDocs/virtualization/hyper-v/media/failover-cluster-network-recommendations/converged-networking-diagram.png new file mode 100644 index 0000000000..96fab5d313 Binary files /dev/null and b/WindowsServerDocs/virtualization/hyper-v/media/failover-cluster-network-recommendations/converged-networking-diagram.png differ diff --git a/WindowsServerDocs/virtualization/hyper-v/media/failover-cluster-network-recommendations/live-migration-settings.png b/WindowsServerDocs/virtualization/hyper-v/media/failover-cluster-network-recommendations/live-migration-settings.png new file mode 100644 index 0000000000..c61749352e Binary files /dev/null and b/WindowsServerDocs/virtualization/hyper-v/media/failover-cluster-network-recommendations/live-migration-settings.png differ diff --git a/WindowsServerDocs/virtualization/hyper-v/media/failover-cluster-network-recommendations/management-network-properties.png b/WindowsServerDocs/virtualization/hyper-v/media/failover-cluster-network-recommendations/management-network-properties.png new file mode 100644 index 0000000000..02b482e0fc Binary files /dev/null and b/WindowsServerDocs/virtualization/hyper-v/media/failover-cluster-network-recommendations/management-network-properties.png differ diff --git a/WindowsServerDocs/virtualization/hyper-v/nested-virtualization.md b/WindowsServerDocs/virtualization/hyper-v/nested-virtualization.md index 1e7ca8295b..63c0171a16 100644 --- a/WindowsServerDocs/virtualization/hyper-v/nested-virtualization.md +++ b/WindowsServerDocs/virtualization/hyper-v/nested-virtualization.md @@ -63,7 +63,7 @@ While it might be possible for Hyper-V virtualization to run on non-Microsoft vi Azure Local is designed and tested to run on validated physical hardware. Azure Local can run nested in a virtual machine for evaluation, but production environments in a nested configuration aren't supported. -To learn more about Azure Local nested on Hyper-V VMs, see [Nested virtualization in Azure Local](/previous-versions/azure/azure-local/concepts/nested-virtualization). +To learn more about Azure Local nested on Hyper-V VMs, see [Nested virtualization in Azure Local](/azure/azure-local/manage/enable-nested-virtualization). ### Hyper-V isolated containers running nested on Hyper-V diff --git a/WindowsServerDocs/virtualization/hyper-v/network-quality-of-service-bandwidth-limits.md b/WindowsServerDocs/virtualization/hyper-v/network-quality-of-service-bandwidth-limits.md new file mode 100644 index 0000000000..cd2744b018 --- /dev/null +++ b/WindowsServerDocs/virtualization/hyper-v/network-quality-of-service-bandwidth-limits.md @@ -0,0 +1,125 @@ +--- +title: Network QoS Minimum Bandwidth Best Practices for Hyper-V +description: Guidance and best practices for configuring Hyper-V Quality of Service (QoS) minimum bandwidth on Windows Server. +author: dknappettmsft +ms.author: daknappe +ms.topic: best-practice +ms.date: 10/28/2025 +--- + +# Network QoS minimum bandwidth best practices for Hyper-V + +Use these best practices to configure Hyper‑V network Quality of Service (QoS) Minimum Bandwidth on Windows Server. The guidance helps you choose the appropriate mode (weight or bits per second), assign effective weights, and avoid configuration pitfalls with NIC Teaming and Data Center Bridging (DCB). + +The article covers: weight assignment strategy, when to prefer weight over absolute bandwidth, interaction with teaming algorithms, coexistence considerations for QoS and DCB, and mitigation techniques for uneven bandwidth distribution. + +## Guidelines for using Minimum Bandwidth + +Following are guidelines for configuring Minimum Bandwidth. + +1. **Keep the sum of the weights near or under 100**. The larger the value for weight, the higher rounding error or quantization error there is when QoS Packet Scheduler partitions the bandwidth among workloads. For example, if there are 20 VMs that you want to share the network bandwidth, rather than assigning a weight of 10 to each of them (sum would be 200), assign each VM a weight of 1. +1. **Assign a relatively large weight to critical workloads even if they don't require that percentage of bandwidth**. For example, management and cluster heartbeat traffic on a computer that is running Hyper-V rarely require more than 1–2% of bandwidth over a 10 GbE NIC—but they're critical. Instead of assigning them a weight of 1 or 2, assign each a weight of 5 or more. +1. **Gap the weight assignment to differentiate service levels**. Don't use consecutive numbers (1,2,3). For example, if you have VMs named Gold, Silver, and Bronze on the same Hyper-V virtual switch, assign weights 5 (Gold), 3 (Silver), 1 (Bronze) rather than 3,2,1. +1. **Account for unfiltered / catch‑all traffic**. For example, if Storage, Live Migration, and Cluster are filtered out with workload-specific filters, group the rest of the network traffic with a wildcard filter as a single flow that has a weight assignment. + +## Minimum Bandwidth modes + +When you create a Hyper-V virtual switch with PowerShell, choose one of two Minimum Bandwidth configuration modes. These modes determine how you quantify minimum bandwidth for a workload: + +- Weight (integer 1–100) +- Bits per second (BPS) + +> [!TIP] +> Configure Minimum Bandwidth by weight rather than BPS. Weight is more flexible and compatible with features such as Live Migration and NIC Teaming. + +Example scenario: A VM configured with a Minimum Bandwidth of 500 Mbps might fail Live Migration to a destination host that can't guarantee 500 Mbps spare bandwidth. If you specify Minimum Bandwidth by weight (for example, 3), the sum of weights simply increases by 3 and migration succeeds (assuming no other constraints). + +If you must specify minimum bandwidth in an absolute number (BPS), use these guidelines: + +- The minimum unit is 1% of link capacity. On a 10 GbE NIC, the minimum allocatable bandwidth per virtual network adapter is 100 Mbps. +- Values are rounded to the nearest percent point. For example, 234 Mbps rounds down to 200 Mbps (2% of a 10 GbE link). + +Use the `-MinimumBandwidthMode` parameter of `New-VMSwitch` to specify the mode: + +```powershell +New-VMSwitch "QoS Switch by Weight" -NetAdapterName "External NIC" -MinimumBandwidthMode Weight +``` + +```powershell +New-VMSwitch "QoS Switch by BPS" -NetAdapterName "External NIC" -MinimumBandwidthMode Absolute +``` + +For more information, see the PowerShell reference topic `New-VMSwitch`. + +## Minimum Bandwidth and Data Center Bridging (DCB) + +QoS Minimum Bandwidth (enforced by QoS Packet Scheduler in Windows) and Data Center Bridging (DCB, enforced by a capable NIC) both ensure a workload receives its fair share of bandwidth under congestion. They're **not** designed to work together for the same networking stack or NIC. + +> [!IMPORTANT] +> Don't enable both Minimum Bandwidth and DCB for workloads that share the same networking stack or NIC. + +You can enable both Minimum Bandwidth and DCB on one server only when they apply to separate networking stacks or separate NICs. + +## Configuring QoS and NIC Teaming + +NIC Teaming provides: + +- Bandwidth aggregation (distribution across team members) +- Traffic failover (maintains connectivity on component failure) + +NIC Teaming distribution algorithms: + +- Hyper-V virtual switch port (hash based on switch port of a VM or management OS virtual NIC) +- Address hashing (hash based on MAC, IP, and transport port fields) + +QoS interaction with NIC Teaming: + +- **Classification and Tagging** – Works seamlessly; traffic is tagged before hashing. +- **Priority-based Flow Control (PFC)** – Works seamlessly; ensure consistent enablement across all team members. +- **Bandwidth Management** – Details in the following section. + +### Maximum Bandwidth + +Works seamlessly: QoS Packet Scheduler throttles flows before NIC Teaming hashes them to team members. + +### Minimum Bandwidth (weight mode) + +QoS Packet Scheduler partitions bandwidth among flows by assigned weights before hashing. A problem can occur when the NIC Teaming algorithm is Hyper-V switch port: each VM (single vNIC) becomes a single flow. Teaming could hash high‑weight VMs to one member and low‑weight VMs to another, resulting in effective equal share rather than proportional share. + +This issue is less pronounced when: + +- Many VMs share the virtual switch +- The NIC Teaming algorithm is Address hashing (more granular flows – e.g., each TCP connection) + +Mitigation: script VM startup order so groups of same-weight VMs are brought up together. NIC Teaming hashes virtual NICs round‑robin; grouping preserves more even weight distribution. + +### Hardware enforced Minimum Bandwidth (DCB) + +The same uneven distribution issue can arise with multiple DCB-capable NICs if hashing is skewed. + +### Absolute (BPS) Minimum Bandwidth with NIC Teaming + +If a Hyper-V switch is bound to a two‑member 1 Gb NIC team (aggregate 2 Gb), you can't safely allocate more than 1 Gb to a VM—upon single NIC failure only 1 Gb remains. Weight mode avoids this complexity, as remaining bandwidth is repartitioned proportionally. + +> [!TIP] +> Prefer weight mode for most deployments; it gracefully handles migration, teaming, and failure scenarios. + +## Summary: QoS and NIC Teaming + +| QoS feature | Functionality with NIC Teaming | +|-------------|--------------------------------| +| Maximum Bandwidth | Works seamlessly | +| Minimum Bandwidth (weight) | Potential uneven enforcement if switch‑port algorithm skews distribution | +| Hardware enforced Minimum Bandwidth (DCB) | Potential uneven enforcement if traffic distribution is skewed | +| Classification and Tagging | Works seamlessly | +| Priority-based Flow Control | Works seamlessly | + +## See also + +- Hyper-V QoS overview (newer versions) *(add link when available)* +- `New-VMSwitch` PowerShell reference +- NIC Teaming overview + +> [!NOTE] +> This legacy content is retained for reference. Validate applicability before using these practices on later Windows Server versions. + diff --git a/WindowsServerDocs/virtualization/hyper-v/plan/Should-I-create-a-generation-1-or-2-virtual-machine-in-Hyper-V.md b/WindowsServerDocs/virtualization/hyper-v/plan/Should-I-create-a-generation-1-or-2-virtual-machine-in-Hyper-V.md index 292fd6eb0f..66b450ba59 100644 --- a/WindowsServerDocs/virtualization/hyper-v/plan/Should-I-create-a-generation-1-or-2-virtual-machine-in-Hyper-V.md +++ b/WindowsServerDocs/virtualization/hyper-v/plan/Should-I-create-a-generation-1-or-2-virtual-machine-in-Hyper-V.md @@ -10,7 +10,7 @@ ms.date: 06/18/2025 Creating a generation 1 or generation 2 virtual machine depends on which guest operating system you want to install and the boot method you want to use to deploy the virtual machine. We recommend you create a generation 2 virtual machines to take advantage of features like Secure Boot unless one of the following statements is true: -- You're using an existing, prebuilt virtual hard drive (VHD or VHDX files), which isn't [compatible with UEFI](/previous-versions/windows/it-pro/windows-8.1-and-8/hh824898(v=win.10)). +- You're using an existing, prebuilt virtual hard drive (VHD or VHDX files), which isn't [compatible with UEFI](/windows-hardware/manufacture/desktop/boot-to-uefi-mode-or-legacy-bios-mode). - Generation 2 doesn't support the operating system you want to run on the virtual machine. - Generation 2 doesn't support the boot method you want to use. @@ -24,12 +24,12 @@ Here are some of the advantages you get when you use a generation 2 virtual mach - **Secure Boot** - Use Secure Boot to help prevent unauthorized firmware, operating systems, or UEFI drivers from running at boot time. Secure Boot verifies the boot loader is signed by a trusted authority in the UEFI database. Secure Boot is enabled by default for generation 2 virtual machines. If you need to run a guest operating system that Secure Boot doesn't support, you can disable it after you create the virtual machine. For more information, see [Secure Boot](/previous-versions/windows/it-pro/windows-8.1-and-8/dn486875(v=ws.11)). + Use Secure Boot to help prevent unauthorized firmware, operating systems, or UEFI drivers from running at boot time. Secure Boot verifies the boot loader is signed by a trusted authority in the UEFI database. Secure Boot is enabled by default for generation 2 virtual machines. If you need to run a guest operating system that Secure Boot doesn't support, you can disable it after you create the virtual machine. For more information, see [Secure Boot](/windows-hardware/design/device-experiences/oem-secure-boot). To Secure Boot generation 2 Linux virtual machines, you need to choose the UEFI CA Secure Boot template when you create the virtual machine. - **Larger boot volume** - The maximum boot volume for generation 2 virtual machines is 64 TB. This maximum boot volume is the maximum disk size supported by a `.VHDX` For generation 1 virtual machines, the maximum boot volume is 2 TB for a `.VHDX`and 2040 GB for a `.VHD` For more information, see [Hyper-V Virtual Hard Disk Format Overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831446(v=ws.11)). + The maximum boot volume for generation 2 virtual machines is 64 TB. This maximum boot volume is the maximum disk size supported by a `.VHDX` For generation 1 virtual machines, the maximum boot volume is 2 TB for a `.VHDX`and 2040 GB for a `.VHD`. You might also see a slight improvement in virtual machine boot and installation times with generation 2 virtual machines. @@ -202,7 +202,7 @@ Virtual hard drives created on generation 1 and generation 2 VMs can be uploaded ### Attach or add a DVD drive -- You can't attach a physical CD or DVD drive to a generation 2 virtual machine. The virtual DVD drive in generation 2 virtual machines only supports ISO image files. To create an ISO image file of a Windows environment, you can use the *OScdimg* command line tool. For more information, see [Oscdimg Command-Line Options](/previous-versions/windows/it-pro/windows-8.1-and-8/hh824847(v=win.10)). +- You can't attach a physical CD or DVD drive to a generation 2 virtual machine. The virtual DVD drive in generation 2 virtual machines only supports ISO image files. To create an ISO image file of a Windows environment, you can use the *OScdimg* command line tool. For more information, see [Oscdimg Command-Line Options](/windows-hardware/manufacture/desktop/oscdimg-command-line-options). - When you create a new virtual machine with the `New-VM` Windows PowerShell cmdlet, the generation 2 virtual machine doesn't have a DVD drive. You can add a DVD drive while the virtual machine is running. ### Use UEFI firmware diff --git a/WindowsServerDocs/virtualization/hyper-v/plan/plan-hyper-v-networking-in-windows-server.md b/WindowsServerDocs/virtualization/hyper-v/plan/plan-hyper-v-networking-in-windows-server.md index 0a47458601..f3ce02181b 100644 --- a/WindowsServerDocs/virtualization/hyper-v/plan/plan-hyper-v-networking-in-windows-server.md +++ b/WindowsServerDocs/virtualization/hyper-v/plan/plan-hyper-v-networking-in-windows-server.md @@ -39,7 +39,7 @@ Virtual switch options: | Setting name | Description | |---|---| | Allow management operating system to share this network adapter | Allow the Hyper-V host to share the use of the virtual switch and NIC or NIC team with the virtual machine. With this enabled, the host can use any of the settings that you configure for the virtual switch, such as Quality of Service (QoS) settings, security settings, or other features of the Hyper-V virtual switch. | -| Enable single-root I/O virtualization (SR-IOV) | Allow virtual machine traffic to bypass the virtual machine switch and go directly to the physical NIC. SR-IOV is only available for virtual machines running Windows Server. For more information, see [Single-Root I/O Virtualization](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn641211(v=ws.11)#Sec4) in the Poster Companion Reference: Hyper-V Networking. | +| Enable single-root I/O virtualization (SR-IOV) | Allow virtual machine traffic to bypass the virtual machine switch and go directly to the physical NIC. SR-IOV is only available for virtual machines running Windows Server. For more information, see [Single-Root I/O Virtualization](/windows-hardware/drivers/network/overview-of-single-root-i-o-virtualization--sr-iov-). | Virtual network adapter types are: @@ -51,9 +51,8 @@ Virtual network adapter types are: Some features rely on specific networking configurations or do better under certain configurations. Consider these when planning or updating your network infrastructure. -**Failover clustering** - It's a best practice to isolate cluster traffic and use Hyper-V Quality of Service (QoS) on the virtual switch. For details, see [Network Recommendations for a Hyper-V Cluster](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn550728(v=ws.11)) +**Failover clustering** - It's a best practice to isolate cluster traffic and use Hyper-V Quality of Service (QoS) on the virtual switch. **Live migration** - Use performance options to reduce network and CPU usage and the time it takes to complete a live migration. For instructions, see [Set up hosts for live migration without Failover Clustering](../deploy/set-up-hosts-for-live-migration-without-failover-clustering.md). **Storage Spaces Direct** - This feature relies on the SMB3.0 network protocol and RDMA. For details, see [Storage Spaces Direct overview](/azure/azure-local/concepts/storage-spaces-direct-overview?context=/windows-server/context/windows-server-storage). - diff --git a/WindowsServerDocs/virtualization/hyper-v/plan/plan-hyper-v-security-in-windows-server.md b/WindowsServerDocs/virtualization/hyper-v/plan/plan-hyper-v-security-in-windows-server.md index 679524a126..eb79f308cd 100644 --- a/WindowsServerDocs/virtualization/hyper-v/plan/plan-hyper-v-security-in-windows-server.md +++ b/WindowsServerDocs/virtualization/hyper-v/plan/plan-hyper-v-security-in-windows-server.md @@ -24,7 +24,7 @@ Secure the Hyper-V host operating system, the virtual machines, configuration fi - Use a private/dedicated network for your live migration traffic. Consider enabling IPSec on this network to use encryption and secure your VM's data going over the network during migration. For more information, see [Set up hosts for live migration without Failover Clustering](../deploy/set-up-hosts-for-live-migration-without-failover-clustering.md). - **Secure storage migration traffic.** - Use SMB 3.0 for end-to-end encryption of SMB data and data protection tampering or eavesdropping on untrusted networks. Use a private network to access the SMB share contents to prevent man-in-the-middle attacks. For more information, see [SMB Security Enhancements](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn551363(v=ws.11)). + Use SMB 3.0 for end-to-end encryption of SMB data and data protection tampering or eavesdropping on untrusted networks. Use a private network to access the SMB share contents to prevent man-in-the-middle attacks. For more information, see [SMB Security Enhancements](/windows-server/storage/file-server/smb-security). - **Configure hosts to be part of a guarded fabric.** For more information, see [Guarded fabric](../../../security/guarded-fabric-shielded-vm/guarded-fabric-and-shielded-vms-top-node.md). diff --git a/WindowsServerDocs/virtualization/hyper-v/plan/virtual-fibre-channel-for-hyper-v.md b/WindowsServerDocs/virtualization/hyper-v/plan/virtual-fibre-channel-for-hyper-v.md index a1370314d7..35a731abd9 100644 --- a/WindowsServerDocs/virtualization/hyper-v/plan/virtual-fibre-channel-for-hyper-v.md +++ b/WindowsServerDocs/virtualization/hyper-v/plan/virtual-fibre-channel-for-hyper-v.md @@ -57,7 +57,7 @@ To support live migration of virtual machines across Hyper-V hosts while maintai ### Tape library support -Windows Server only supports virtual tape libraries configured with virtual Fibre Channel adapters when using System Center Data Protection Manager 2012 R2 U3 or later with certified hardware. You can check if your virtual Fibre Channel adapter supports a tape library by contacting the tape library hardware vendor. You can also check compatibility by running the Data Protection Management (DPM) Tape Library Compatibility Test tool on the virtual tape library in a guest VM. For more information about the DPM Tape Library Compatibility Test, see [Verify tape library compatibility](/previous-versions/system-center/system-center-2012-R2/jj733581(v=sc.12)). +Windows Server only supports virtual tape libraries configured with virtual Fibre Channel adapters when using System Center Data Protection Manager 2012 R2 U3 or later with certified hardware. You can check if your virtual Fibre Channel adapter supports a tape library by contacting the tape library hardware vendor. You can also check compatibility by running the Data Protection Management (DPM) Tape Library Compatibility Test tool on the virtual tape library in a guest VM. For more information about the DPM Tape Library Compatibility Test, see [System Center DPM Compatible Tape Libraries](/system-center/dpm/dpm-compatible-tape-libraries). ### MPIO functionality diff --git a/WindowsServerDocs/virtualization/hyper-v/powershell-direct.md b/WindowsServerDocs/virtualization/hyper-v/powershell-direct.md index 715d7220f8..8f3a55b3c5 100644 --- a/WindowsServerDocs/virtualization/hyper-v/powershell-direct.md +++ b/WindowsServerDocs/virtualization/hyper-v/powershell-direct.md @@ -8,7 +8,7 @@ ms.date: 05/02/2016 ms.topic: how-to --- -# Virtual Machine automation and management using PowerShell +# Virtual machine automation and management using PowerShell You can use PowerShell Direct to run arbitrary PowerShell in a Windows 10 or greater, or Windows Server 2016 or newer, virtual machine from your Hyper-V host. Use PowerShell Direct regardless of network configuration or remote management settings. @@ -25,11 +25,11 @@ Here are some ways you can run PowerShell Direct: * Host: Windows 10, Windows Server 2016, or later running Hyper-V. * Guest/Virtual Machine: Windows 10, Windows Server 2016, or later. -If you're managing older virtual machines, use Virtual Machine Connection (VMConnect) or [configure a virtual network for the virtual machine](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc816585(v=ws.10)). +If you're managing older virtual machines, use Virtual Machine Connection (VMConnect) or connect over a network connection. **Configuration requirements:** -* The virtual machine must be running locally on the host. +* The virtual machine must run locally on the host. * The virtual machine must be turned on and running with at least one configured user profile. * You must be logged into the host computer as a Hyper-V administrator. * You must supply valid user credentials for the virtual machine. @@ -51,7 +51,7 @@ When the session starts, the commands that you type run on the virtual machine, Enter-PSSession -VMId ``` - Provide credentials for the virtual machine when prompted. + Enter credentials for the virtual machine when prompted. 1. Run commands on your virtual machine. You should see the VMName as the prefix for your PowerShell prompt as the following: @@ -59,7 +59,7 @@ When the session starts, the commands that you type run on the virtual machine, [VMName]: PS C:\> ``` - Any command run will be running on your virtual machine. To test, you can run `ipconfig` or `hostname` to make sure that these commands are running in the virtual machine. + Any command you run executes on your virtual machine. To test, run `ipconfig` or `hostname` to make sure that these commands run in the virtual machine. 1. When you're done, run the following command to close the session: @@ -74,7 +74,7 @@ To learn more about these cmdlets, see [Enter-PSSession](/powershell/module/Micr ## Run a script or command with Invoke-Command -PowerShell Direct with Invoke-Command is perfect for situations where you need to run one command or one script on a virtual machine but do not need to continue interacting with the virtual machine beyond that point. +PowerShell Direct with Invoke-Command is perfect for situations where you need to run one command or one script on a virtual machine but don't need to continue interacting with the virtual machine beyond that point. **To run a single command:** @@ -87,9 +87,9 @@ PowerShell Direct with Invoke-Command is perfect for situations where you need t Invoke-Command -VMId -ScriptBlock { command } ``` - Provide credentials for the virtual machine when prompted. + Enter credentials for the virtual machine when prompted. - The command will execute on the virtual machine, if there is output to the console, it'll be printed to your console. The connection will be closed automatically as soon as the command runs. + The command runs on the virtual machine. If the command produces output, you see it in your console. The connection closes automatically as soon as the command runs. **To run a script:** @@ -102,11 +102,11 @@ PowerShell Direct with Invoke-Command is perfect for situations where you need t Invoke-Command -VMId -FilePath C:\host\script_path\script.ps1 ``` - Provide credentials for the virtual machine when prompted. + Enter credentials for the virtual machine when prompted. - The script will execute on the virtual machine. The connection will be closed automatically as soon as the command runs. + The script runs on the virtual machine. The connection closes automatically as soon as the command runs. -To learn more about this cmdlet, see [Invoke-Command](/powershell/module/Microsoft.PowerShell.Core/Invoke-Command). +For more information about this cmdlet, see [Invoke-Command](/powershell/module/Microsoft.PowerShell.Core/Invoke-Command). ## Copy files with New-PSSession and Copy-Item @@ -115,23 +115,23 @@ To learn more about this cmdlet, see [Invoke-Command](/powershell/module/Microso Persistent PowerShell sessions are incredibly useful when writing scripts that coordinate actions across one or more remote machines. Once created, persistent sessions exist in the background until you decide to delete them. This means you can reference the same session over and over again with `Invoke-Command` or `Enter-PSSession` without passing credentials. -By the same token, sessions hold state. Since persistent sessions persist, any variables created in a session or passed to a session will be preserved across multiple calls. There are a number of tools available for working with persistent sessions. For this example, we'll use [New-PSSession](/powershell/module/Microsoft.PowerShell.Core/New-PSSession) and [Copy-Item](/powershell/module/Microsoft.PowerShell.Management/Copy-Item) to move data from the host to a virtual machine and from a virtual machine to the host. +By the same token, sessions hold state. Since persistent sessions persist, any variables you create in a session or pass to a session are preserved across multiple calls. You can use a number of tools to work with persistent sessions. For this example, use [New-PSSession](/powershell/module/Microsoft.PowerShell.Core/New-PSSession) and [Copy-Item](/powershell/module/Microsoft.PowerShell.Management/Copy-Item) to move data from the host to a virtual machine and from a virtual machine to the host. **To create a session then copy files:** 1. On the Hyper-V host, open PowerShell as Administrator. -1. Run one of the following commands to create a persistent PowerShell session to the virtual machine using `New-PSSession`. +1. Run one of the following commands to create a persistent PowerShell session to the virtual machine by using `New-PSSession`. ```powershell $s = New-PSSession -VMName -Credential (Get-Credential) $s = New-PSSession -VMId -Credential (Get-Credential) ``` - Provide credentials for the virtual machine when prompted. + Enter credentials for the virtual machine when prompted. >[!WARNING] - > There's a bug in builds before 14500. If credentials aren't explicitly specified with `-Credential` flag, the service in the guest will crash and will need to be restarted. If you hit this issue, workaround instructions are available in the section [Error: A remote session might have ended](#error-a-remote-session-might-have-ended). + > There's a bug in builds before 14500. If you don't explicitly specify credentials with the `-Credential` flag, the service in the guest crashes and needs to be restarted. If you encounter this issue, see the section [Error: A remote session might have ended](#error-a-remote-session-might-have-ended) for workaround instructions. 1. Copy a file into the virtual machine. @@ -149,7 +149,7 @@ By the same token, sessions hold state. Since persistent sessions persist, any v Copy-Item -FromSession $s -Path C:\guest_path\data.txt -Destination C:\host_path\ ``` -1. Stop the persistent session using `Remove-PSSession`. +1. Stop the persistent session by using `Remove-PSSession`. ```powershell Remove-PSSession $s @@ -157,17 +157,17 @@ By the same token, sessions hold state. Since persistent sessions persist, any v ## Troubleshooting -There are a small set of common error messages surfaced through PowerShell Direct. The following sections describe the most common error messages, some causes, and tools for diagnosing issues. +PowerShell Direct surfaces a small set of common error messages. The following sections describe the most common error messages, some causes, and tools for diagnosing issues. ### -VMName or -VMID parameters don't exist **Problem:** -`Enter-PSSession`, `Invoke-Command`, or `New-PSSession` do not have a `-VMName` or `-VMId` parameter. +`Enter-PSSession`, `Invoke-Command`, or `New-PSSession` don't have a `-VMName` or `-VMId` parameter. **Potential causes:** -The most likely issue is that PowerShell Direct isn't supported by your host operating system. +The most likely issue is that your host operating system doesn't support PowerShell Direct. You can check your Windows build by running the following command: @@ -175,7 +175,7 @@ You can check your Windows build by running the following command: [System.Environment]::OSVersion.Version ``` -If you're running a supported build, it is also possible your version of PowerShell does not run PowerShell Direct. For PowerShell Direct and JEA, the major version must be 5 or later. +If you're running a supported build, it's also possible that your version of PowerShell doesn't support PowerShell Direct. For PowerShell Direct and JEA, the major version must be 5 or later. You can check your PowerShell version build by running the following command: @@ -186,51 +186,51 @@ $PSVersionTable.PSVersion ### Error: A remote session might have ended > [!NOTE] -> For Enter-PSSession between host builds 10240 and 12400, all errors below reported as "A remote session might have ended". +> For Enter-PSSession between host builds 10240 and 12400, all errors report as "A remote session might have ended". **Error message:** -Enter-PSSession : An error has occurred which Windows PowerShell cannot handle. A remote session might have ended. +Enter-PSSession : An error occurred that Windows PowerShell can't handle. A remote session might have ended. **Potential causes:** -* The virtual machine exists but is not running. -* The guest OS does not support PowerShell Direct. See [requirements](#requirements). +* The virtual machine exists but isn't running. +* The guest OS doesn't support PowerShell Direct. See [requirements](#requirements). * PowerShell isn't available in the guest yet * The operating system hasn't finished booting * The operating system can't boot correctly * Some boot time event needs user input -You can use the [Get-VM](/powershell/module/hyper-v/get-vm) cmdlet to check to see which VMs are running on the host. +Use the [Get-VM](/powershell/module/hyper-v/get-vm) cmdlet to check which VMs are running on the host. **Error message:** -New-PSSession : An error has occurred which Windows PowerShell cannot handle. A remote session might have ended. +New-PSSession : An error occurred that Windows PowerShell can't handle. A remote session might have ended. **Potential causes:** -* One of the reasons listed above -- they all are equally applicable to `New-PSSession` -* A bug in current builds where credentials must be explicitly passed with `-Credential`. When this happens, the entire service hangs in the guest operating system and needs to be restarted. You can check if the session is still available with Enter-PSSession. +* One of the reasons listed earlier -- they all apply to `New-PSSession` +* A bug in current builds where you must explicitly pass credentials with `-Credential`. When this bug occurs, the entire service hangs in the guest operating system and needs to be restarted. You can check if the session is still available with Enter-PSSession. -To work around the credential issue, log into the virtual machine using VMConnect, open PowerShell, and restart the vmicvmsession service using the following PowerShell: +To work around the credential issue, sign in to the virtual machine using VMConnect, open PowerShell, and restart the vmicvmsession service with the following PowerShell command: ```powershell Restart-Service -Name vmicvmsession ``` -### Error: Parameter set cannot be resolved +### Error: Parameter set can't be resolved **Error message:** -Enter-PSSession : Parameter set cannot be resolved using the specified named parameters. +Enter-PSSession : Parameter set can't be resolved by using the specified named parameters. **Potential causes:** -* `-RunAsAdministrator` is not supported when connecting to virtual machines. +* You can't use `-RunAsAdministrator` when connecting to virtual machines. - When connecting to a Windows container, the `-RunAsAdministrator` flag allows Administrator connections without explicit credentials. Since virtual machines do not give the host implied administrator access, you need to explicitly enter credentials. + When connecting to a Windows container, the `-RunAsAdministrator` flag allows Administrator connections without explicit credentials. Since virtual machines don't give the host implied administrator access, you need to explicitly enter credentials. -Administrator credentials can be passed to the virtual machine with the `-Credential` parameter or by entering them manually when prompted. +You can pass administrator credentials to the virtual machine with the `-Credential` parameter or by entering them manually when prompted. ### Error: The credential is invalid @@ -242,23 +242,23 @@ Enter-PSSession : The credential is invalid. * The guest credentials couldn't be validated * The supplied credentials were incorrect. - * There are no user accounts in the guest (the OS hasn't booted before) - * If connecting as Administrator: Administrator has not been set as an active user. Learn more in [Enable and Disable the Built-in Administrator Account](/previous-versions/windows/it-pro/windows-8.1-and-8/hh825104(v=win.10)). + * There are no user accounts in the guest (the OS didn't boot before) + * If connecting as Administrator: Administrator isn't set as an active user. For more information, see [Enable and Disable the Built-in Administrator Account](/windows-hardware/manufacture/desktop/enable-and-disable-the-built-in-administrator-account). -### Error: The input VMName parameter does not resolve to any virtual machine. +### Error: The input VMName parameter doesn't resolve to any virtual machine. **Error message:** -Enter-PSSession : The input VMName parameter does not resolve to any virtual machine. +Enter-PSSession : The input VMName parameter doesn't resolve to any virtual machine. **Potential causes:** -* You are not a Hyper-V Administrator. +* You're not a Hyper-V Administrator. * The virtual machine doesn't exist. -You can use the [Get-VM](/powershell/module/hyper-v/get-vm) cmdlet to check that the credentials you're using have the Hyper-V administrator role and to see which VMs are running locally on the host and booted. +Use the [Get-VM](/powershell/module/hyper-v/get-vm) cmdlet to check that the credentials you're using have the Hyper-V administrator role and to see which VMs are running locally on the host and booted. -## Samples and User Guides +## Samples and user guides PowerShell Direct supports Just Enough Administration (JEA). diff --git a/WindowsServerDocs/virtualization/hyper-v/powershell.md b/WindowsServerDocs/virtualization/hyper-v/powershell.md index 0345b0408c..3c345142bf 100644 --- a/WindowsServerDocs/virtualization/hyper-v/powershell.md +++ b/WindowsServerDocs/virtualization/hyper-v/powershell.md @@ -50,7 +50,7 @@ Use the `Get-VM` command to return a list of virtual machines. ![Screenshot of the Administrator Windows Power Shell screen showing the output after entering Get V M.](./media/powershell/get-vm.png) -1. To return a list of only powered on virtual machines add a filter to the `Get-VM` command. A filter can be added by using the `Where-Object` command. For more information on filtering, see [Using the Where-Object](/previous-versions/windows/it-pro/windows-powershell-1.0/ee177028(v=technet.10)) documentation. +1. To return a list of only powered on virtual machines add a filter to the `Get-VM` command. A filter can be added by using the `Where-Object` command. For more information on filtering, see [Using the Where-Object](/powershell/module/microsoft.powershell.core/where-object) documentation. ```powershell Get-VM | where {$_.State -eq 'Running'} diff --git a/WindowsServerDocs/virtualization/hyper-v/toc.yml b/WindowsServerDocs/virtualization/hyper-v/toc.yml index 1b6e8a5950..b09c47c509 100644 --- a/WindowsServerDocs/virtualization/hyper-v/toc.yml +++ b/WindowsServerDocs/virtualization/hyper-v/toc.yml @@ -28,9 +28,10 @@ items: href: plan/guest-operating-system-application-supportability.md - name: Supported Windows guest operating systems href: Supported-Windows-guest-operating-systems-for-Hyper-V-on-Windows.md - - name: Supported Linux and FreeBSD VMs - href: Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md + - name: Linux and FreeBSD VMs items: + - name: Supported Linux and FreeBSD VMs + href: Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md - name: CentOS and Red Hat Enterprise Linux VMs href: Supported-CentOS-and-Red-Hat-Enterprise-Linux-virtual-machines-on-Hyper-V.md - name: Debian VMs @@ -57,10 +58,15 @@ items: items: - name: Networking overview href: plan/plan-hyper-v-networking-in-windows-server.md + - name: Failover cluster network recommendations + href: failover-cluster-network-recommendations.md - name: Virtual switch href: virtual-switch.md - name: RDMA and SET href: /azure/azure-local/concepts/host-network-requirements?context=/windows-server/context/windows-server-virtualization + - name: Network Quality of Service and bandwidth limits + displayName: QoS + href: network-quality-of-service-bandwidth-limits.md - name: Security href: plan/plan-hyper-v-security-in-windows-server.md - name: GPU acceleration @@ -152,9 +158,8 @@ items: - name: Configure processor compatibility mode href: configure-processor-compatibility-mode.md - name: Move VMs with live migration - href: manage/Live-migration-overview.md items: - - name: Live Migration Overview + - name: Live migration overview href: manage/Live-migration-overview.md - name: Set up hosts for live migration href: deploy/Set-up-hosts-for-live-migration-without-Failover-Clustering.md @@ -162,8 +167,10 @@ items: href: manage/Use-live-migration-without-Failover-Clustering-to-move-a-virtual-machine.md - name: Use live migration with workgroup clusters href: manage/live-migration-workgroup-cluster.md - - name: Use PowerShell with Hyper-V - href: powershell.md + - name: Use PowerShell with Hyper-V + href: powershell.md + - name: Dynamic Memory + href: dynamic-memory.md - name: Virtual machines items: - name: Virtual Machine Connection overview @@ -180,8 +187,12 @@ items: items: - name: Hyper-V specification and API documentation href: /virtualization/hyper-v-on-windows/ - - name: Build an integration Service - href: make-integration-service.md + - name: Integration Services + items: + - name: Build an integration Service + href: make-integration-service.md + - name: Data exchange between the host and VM + href: integration-services-data-exchange.md - name: Move from Hyper-V WMI v1 to WMI v2 href: refactor-wmi-v1-to-wmi-v2.md - name: Reference diff --git a/WindowsServerDocs/virtualization/hyper-v/virtual-machine-connection.md b/WindowsServerDocs/virtualization/hyper-v/virtual-machine-connection.md index aac7412992..cb9605ba4c 100644 --- a/WindowsServerDocs/virtualization/hyper-v/virtual-machine-connection.md +++ b/WindowsServerDocs/virtualization/hyper-v/virtual-machine-connection.md @@ -35,7 +35,7 @@ You might find the following information helpful for using VMConnect: |Use a host's local resources on Hyper\-V virtual machine like a USB flash drive|Turn on enhanced session mode on the Hyper-V host, use VMConnect to connect to the virtual machine, and before you connect, choose the local resource that you want to use. For the specific steps, see [Use local resources on Hyper\-V virtual machine with VMConnect](use-local-resources-virtual-machine-connection.md).| |Change saved VMConnect settings for a virtual machine|Run the following command in Windows PowerShell or the command prompt:

        `VMConnect.exe /edit`| |Prevent a VMConnect user from taking over another user's VMConnect session|Not having enhanced session mode turned on might pose a security and privacy risk. If a user is connected and logged on to a virtual machine through VMConnect and another authorized user connects to the same virtual machine, the session is taken over by the second user and the first user loses the session. The second user will be able to view the first user's desktop, documents, and applications.| -|Manage integration services or components that allow the VM to communicate with the Hyper-V host| On Hyper-V hosts that run Windows 10 or Windows Server 2016, you can't manage integration services with VMConnect. See these articles:
        - [Turn on/turn off integration services from the Hyper-V host](manage/manage-hyper-v-integration-services.md#turn-an-integration-service-on-or-off-using-hyper-v-manager)
        - [Turn on/turn off integration services from a Windows virtual machine](manage/manage-hyper-v-integration-services.md#start-and-stop-an-integration-service-from-a-windows-guest)
        - [Turn on/turn off integration services from a Linux virtual machine](manage/manage-hyper-v-integration-services.md#start-and-stop-an-integration-service-from-a-linux-guest)
        - [Keep integration services updated for the virtual machine](manage/manage-hyper-v-integration-services.md#keep-integration-services-up-to-date)

        For hosts that run Windows Server 2012 or Windows Server 2012 R2, see [Integration Services](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn798297(v=ws.11)).| +|Manage integration services or components that allow the VM to communicate with the Hyper-V host| On Hyper-V hosts that run Windows 10 or Windows Server 2016, you can't manage integration services with VMConnect. See these articles:
        - [Turn on/turn off integration services from the Hyper-V host](manage/manage-hyper-v-integration-services.md#turn-an-integration-service-on-or-off-using-hyper-v-manager)
        - [Turn on/turn off integration services from a Windows virtual machine](manage/manage-hyper-v-integration-services.md#start-and-stop-an-integration-service-from-a-windows-guest)
        - [Turn on/turn off integration services from a Linux virtual machine](manage/manage-hyper-v-integration-services.md#start-and-stop-an-integration-service-from-a-linux-guest)
        - [Keep integration services updated for the virtual machine](manage/manage-hyper-v-integration-services.md#keep-integration-services-up-to-date).| |Resize the VMConnect window|You can change the size of the VMConnect window for generation 2 virtual machines that run a Windows operating system. To do this, you might need to turn on enhanced session mode on the Hyper-V host. For virtual machines that run Ubuntu, see [Changing Ubuntu Screen Resolution in a Hyper-V VM](/archive/blogs/virtual_pc_guy/changing-ubuntu-screen-resolution-in-a-hyper-v-vm).| ## Keyboard shortcuts diff --git a/includes/guarded-fabric-configure-fabric-dns.md b/includes/guarded-fabric-configure-fabric-dns.md index dcefb57fb1..4a913786d1 100644 --- a/includes/guarded-fabric-configure-fabric-dns.md +++ b/includes/guarded-fabric-configure-fabric-dns.md @@ -1,7 +1,7 @@ --- ms.topic: include -author: meaghanlewis -ms.author: mosagie +author: robinharwood +ms.author: roharwoo ms.date: 08/29/2018 ---