mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
fix merge conflict, update wording
This commit is contained in:
Meghan Stewart
commit
90b6688134
@ -234,6 +234,78 @@
|
||||
"source_path": "education/windows/configure-windows-for-education.md",
|
||||
"redirect_url": "/education/windows",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
|
||||
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/configure-device-apps.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/configure-device-apps",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/configure-device-settings.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/configure-device-settings",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/configure-devices-overview.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/configure-devices-overview",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/enroll-autopilot.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/enroll-autopilot",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/enroll-entra-join.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/enroll-entra-join",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/enroll-overview.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/enroll-overview",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/enroll-package.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/enroll-package",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/index.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/introduction",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/manage-overview.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/manage-overview",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/manage-surface-devices.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/manage-surface-devices",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/reset-wipe.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/reset-wipe",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/set-up-microsoft-entra-id.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/set-up-microsoft-entra-id",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/set-up-microsoft-intune.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/set-up-microsoft-intune",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "education/windows/tutorial-school-deployment/troubleshoot-overview.md",
|
||||
"redirect_url": "/mem/intune/industry/education/tutorial-school-deployment/troubleshoot-overview",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
@ -34,6 +34,506 @@
|
||||
"source_path": "windows/application-management/add-apps-and-features.md",
|
||||
"redirect_url": "/windows/client-management/client-tools/add-remove-hide-features",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-about-appv.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-about-appv",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-add-or-remove-an-administrator-with-the-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-add-or-remove-an-administrator-with-the-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-add-or-upgrade-packages-with-the-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-add-or-upgrade-packages-with-the-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-administering-appv-with-powershell.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-administering-appv-with-powershell",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-administering-virtual-applications-with-the-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-administering-virtual-applications-with-the-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-allow-administrators-to-enable-connection-groups.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-allow-administrators-to-enable-connection-groups",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-application-publishing-and-client-interaction.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-application-publishing-and-client-interaction",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-apply-the-deployment-configuration-file-with-powershell.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-apply-the-deployment-configuration-file-with-powershell",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-apply-the-user-configuration-file-with-powershell.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-apply-the-user-configuration-file-with-powershell",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-auto-batch-sequencing.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-auto-batch-sequencing",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-auto-batch-updating.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-auto-batch-updating",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-auto-clean-unpublished-packages.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-auto-clean-unpublished-packages",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-auto-provision-a-vm.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-auto-provision-a-vm",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-available-mdm-settings.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-available-mdm-settings",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-capacity-planning.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-capacity-planning",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-client-configuration-settings.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-client-configuration-settings",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-configure-access-to-packages-with-the-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-configure-access-to-packages-with-the-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-configure-connection-groups-to-ignore-the-package-version.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-configure-connection-groups-to-ignore-the-package-version",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-configure-the-client-to-receive-updates-from-the-publishing-server.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-configure-the-client-to-receive-updates-from-the-publishing-server",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-connection-group-file.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-connection-group-file",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-connection-group-virtual-environment.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-connection-group-virtual-environment",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-connect-to-the-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-connect-to-the-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-create-a-connection-group.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-create-a-connection-group",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-create-a-custom-configuration-file-with-the-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-create-and-use-a-project-template.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-create-and-use-a-project-template",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-create-a-package-accelerator.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-create-a-package-accelerator",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-create-a-package-accelerator-with-powershell",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-create-a-virtual-application-package-package-accelerator.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-create-a-virtual-application-package-package-accelerator",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-creating-and-managing-virtualized-applications.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-creating-and-managing-virtualized-applications",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-customize-virtual-application-extensions-with-the-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-customize-virtual-application-extensions-with-the-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-delete-a-connection-group.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-delete-a-connection-group",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-delete-a-package-with-the-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-deploy-appv-databases-with-sql-scripts.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-deploy-appv-databases-with-sql-scripts",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-deploying-appv.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-deploying-appv",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-deploying-microsoft-office-2010-wth-appv.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-deploying-microsoft-office-2010-wth-appv",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-deploying-microsoft-office-2013-with-appv.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-deploying-microsoft-office-2013-with-appv",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-deploying-microsoft-office-2016-with-appv",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-deploying-the-appv-sequencer-and-client",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-deploying-the-appv-server.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-deploying-the-appv-server",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-deployment-checklist.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-deployment-checklist",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-deploy-the-appv-server.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-deploy-the-appv-server",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-deploy-the-appv-server-with-a-script.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-deploy-the-appv-server-with-a-script",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-dynamic-configuration.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-dynamic-configuration",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-enable-reporting-on-the-appv-client-with-powershell.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-enable-reporting-on-the-appv-client-with-powershell",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-enable-the-app-v-desktop-client",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-evaluating-appv.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-evaluating-appv",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-for-windows.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-for-windows",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-getting-started.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-getting-started",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-high-level-architecture.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-high-level-architecture",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-install-the-management-server-on-a-standalone-computer.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-install-the-management-server-on-a-standalone-computer",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-install-the-publishing-server-on-a-remote-computer.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-install-the-publishing-server-on-a-remote-computer",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-install-the-reporting-server-on-a-standalone-computer",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-install-the-sequencer.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-install-the-sequencer",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-maintaining-appv.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-maintaining-appv",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-managing-connection-groups.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-managing-connection-groups",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-migrating-to-appv-from-a-previous-version.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-migrating-to-appv-from-a-previous-version",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-modify-an-existing-virtual-application-package.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-modify-an-existing-virtual-application-package",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-modify-client-configuration-with-powershell.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-modify-client-configuration-with-powershell",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-move-the-appv-server-to-another-computer.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-move-the-appv-server-to-another-computer",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-operations.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-operations",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-performance-guidance.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-performance-guidance",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-planning-checklist.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-planning-checklist",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-planning-folder-redirection-with-appv.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-planning-folder-redirection-with-appv",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-planning-for-appv.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-planning-for-appv",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-planning-for-appv-server-deployment.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-planning-for-appv-server-deployment",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-planning-for-high-availability-with-appv.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-planning-for-high-availability-with-appv",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-planning-for-sequencer-and-client-deployment.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-planning-for-sequencer-and-client-deployment",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-planning-for-using-appv-with-office.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-planning-for-using-appv-with-office",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-planning-to-deploy-appv.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-planning-to-deploy-appv",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-preparing-your-environment.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-preparing-your-environment",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-prerequisites.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-prerequisites",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-publish-a-connection-group.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-publish-a-connection-group",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-publish-a-packages-with-the-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-register-and-unregister-a-publishing-server-with-the-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-register-and-unregister-a-publishing-server-with-the-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-release-notes-for-appv-for-windows.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-release-notes-for-appv-for-windows",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-release-notes-for-appv-for-windows-1703.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-release-notes-for-appv-for-windows-1703",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-reporting.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-reporting",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-running-locally-installed-applications-inside-a-virtual-environment.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-running-locally-installed-applications-inside-a-virtual-environment",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-security-considerations.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-security-considerations",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-sequence-a-new-application.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-sequence-a-new-application",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-sequence-a-package-with-powershell.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-sequence-a-package-with-powershell",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-supported-configurations.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-supported-configurations",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-technical-reference.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-technical-reference",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-troubleshooting.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-troubleshooting",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-using-the-client-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-using-the-client-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/app-v/appv-viewing-appv-server-publishing-metadata.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/app-v/appv-viewing-appv-server-publishing-metadata",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@ -347,7 +347,12 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/kiosk-prepare.md",
|
||||
"redirect_url": "/windows/configuration/kiosk/recommendations",
|
||||
"redirect_url": "/windows/configuration/assigned-access/recommendations",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/kiosk/recommendations.md",
|
||||
"redirect_url": "/windows/configuration/assigned-access/recommendations",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -462,7 +467,12 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/windows-spotlight.md",
|
||||
"redirect_url": "/windows/configuration/lock-screen/windows-spotlight",
|
||||
"redirect_url": "/windows/configuration/windows-spotlight/index",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/lock-screen/windows-spotlight.md",
|
||||
"redirect_url": "/windows/configuration/windows-spotlight",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
@ -889,6 +899,141 @@
|
||||
"source_path": "windows/configuration/start/start-secondary-tiles.md",
|
||||
"redirect_url": "/windows/configuration/start/layout",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-administering-uev-with-windows-powershell-and-wmi.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-administering-uev-with-windows-powershell-and-wmi",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-administering-uev.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-administering-uev",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-application-template-schema-reference.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-application-template-schema-reference",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-changing-the-frequency-of-scheduled-tasks.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-changing-the-frequency-of-scheduled-tasks",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-configuring-uev-with-group-policy-objects.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-configuring-uev-with-group-policy-objects",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-configuring-uev-with-system-center-configuration-manager.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-configuring-uev-with-system-center-configuration-manager",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-deploy-required-features.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-deploy-required-features",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-deploy-uev-for-custom-applications.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-deploy-uev-for-custom-applications",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-for-windows.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-for-windows",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-getting-started.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-getting-started",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-manage-administrative-backup-and-restore.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-manage-administrative-backup-and-restore",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-manage-configurations.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-manage-configurations",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-managing-settings-location-templates-using-windows-powershell-and-wmi.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-managing-settings-location-templates-using-windows-powershell-and-wmi",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-managing-uev-agent-and-packages-with-windows-powershell-and-wmi.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-managing-uev-agent-and-packages-with-windows-powershell-and-wmi",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-migrating-settings-packages.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-migrating-settings-packages",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-prepare-for-deployment.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-prepare-for-deployment",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-release-notes-1607.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-release-notes-1607",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-security-considerations.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-security-considerations",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-sync-methods.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-sync-methods",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-sync-trigger-events.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-sync-trigger-events",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-synchronizing-microsoft-office-with-uev.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-synchronizing-microsoft-office-with-uev",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-technical-reference.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-technical-reference",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-troubleshooting.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-troubleshooting",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-upgrade-uev-from-previous-releases.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-upgrade-uev-from-previous-releases",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-using-uev-with-application-virtualization-applications.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-using-uev-with-application-virtualization-applications",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-whats-new-in-uev-for-windows.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-whats-new-in-uev-for-windows",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/ue-v/uev-working-with-custom-templates-and-the-uev-generator.md",
|
||||
"redirect_url": "/microsoft-desktop-optimization-pack/ue-v/uev-working-with-custom-templates-and-the-uev-generator",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
|
||||
@ -791,8 +791,8 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview",
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-overview.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
@ -806,8 +806,8 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-communications.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-communications",
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-communications.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-communications",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
@ -816,8 +816,8 @@
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-end-user-exp.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-end-user-exp",
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-end-user-exp.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-end-user-exp",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
@ -826,8 +826,8 @@
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-overview",
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-overview.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
@ -836,13 +836,13 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-signals.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-signals",
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-signals.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-signals",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-summary-dashboard.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-summary-dashboard",
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-summary-dashboard.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-summary-dashboard",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
@ -1139,6 +1139,46 @@
|
||||
"source_path": "windows/deployment/volume-activation/activate-windows-10-clients-vamt.md",
|
||||
"redirect_url": "/windows/deployment/volume-activation/activate-windows-clients-vamt",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-manage-windows-feature-update-release.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-manage-windows-feature-update-releases",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-trending-report.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-trending-report",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-update-status-report.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-status-report",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-update.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-customize-windows-update-settings",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-status-report.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-status-report",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-summary-dashboard.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-status-report",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-feature-update-trending-report.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-trending-report",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-and-feature-update-reports-overview",
|
||||
"redirect_document_id": true
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@ -9169,6 +9169,16 @@
|
||||
"source_path": "windows/security/threat-protection/security-policy-settings/user-rights-assignment.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/user-rights-assignment",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/cloud-security/index.md",
|
||||
"redirect_url": "/windows/security/cloud-services",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/identity-protection/hello-for-business/hello-feature-dual-enrollment.md",
|
||||
"redirect_url": "/windows/security/identity-protection/hello-for-business/dual-enrollment",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@ -1,28 +0,0 @@
|
||||
<!-- This file is generated automatically each week. Changes made to this file will be overwritten.-->
|
||||
|
||||
|
||||
|
||||
## Week of January 29, 2024
|
||||
|
||||
|
||||
| Published On |Topic title | Change |
|
||||
|------|------------|--------|
|
||||
| 1/30/2024 | [Microsoft 365 Education Documentation](/education/index) | modified |
|
||||
|
||||
|
||||
## Week of January 15, 2024
|
||||
|
||||
|
||||
| Published On |Topic title | Change |
|
||||
|------|------------|--------|
|
||||
| 1/16/2024 | Deployment recommendations for school IT administrators | removed |
|
||||
| 1/16/2024 | Microsoft Entra join with Set up School PCs app | removed |
|
||||
| 1/16/2024 | [Set up School PCs app technical reference overview](/education/windows/set-up-school-pcs-technical) | modified |
|
||||
| 1/16/2024 | Set up student PCs to join domain | removed |
|
||||
| 1/16/2024 | Provision student PCs with apps | removed |
|
||||
| 1/16/2024 | Set up Windows devices for education | removed |
|
||||
| 1/16/2024 | [Configure applications with Microsoft Intune](/education/windows/tutorial-school-deployment/configure-device-apps) | modified |
|
||||
| 1/16/2024 | [Configure and secure devices with Microsoft Intune](/education/windows/tutorial-school-deployment/configure-device-settings) | modified |
|
||||
| 1/16/2024 | [Configure devices with Microsoft Intune](/education/windows/tutorial-school-deployment/configure-devices-overview) | modified |
|
||||
| 1/16/2024 | [Set up Microsoft Entra ID](/education/windows/tutorial-school-deployment/set-up-microsoft-entra-id) | modified |
|
||||
| 1/16/2024 | Windows 10 editions for education customers | removed |
|
||||
@ -215,14 +215,6 @@ A multiple activation key activates either individual computers or a group of co
|
||||
|
||||
| Scenario | Ownership | MAK | KMS | AD based activation | Subscription Activation |
|
||||
|-|-|:-:|:-:|:-:|:-:|
|
||||
| **Workplace join (add work or school account)** | Personal (or student-owned) | X | | | |
|
||||
| **Microsoft Entra join** | Organization | X | X | | X |
|
||||
| **Microsoft Entra hybrid join** | Organization | X | X | X | X |
|
||||
|
||||
## Related links
|
||||
|
||||
- [Windows 10 edition upgrade (Windows 10)](/windows/deployment/upgrade/windows-10-edition-upgrades)
|
||||
- [Windows 10/11 Subscription Activation](/windows/deployment/windows-10-subscription-activation)
|
||||
- [Equip Your Students with Windows 11 Education - Kivuto](https://kivuto.com/windows-11-student-use-benefit/)
|
||||
- [Upgrade Windows Home to Windows Pro (microsoft.com)](https://support.microsoft.com/windows/upgrade-windows-home-to-windows-pro-ef34d520-e73f-3198-c525-d1a218cc2818)
|
||||
- [Partner Center: Upgrade Education customers from Windows 10 Home to Windows 10 Education](/partner-center/upgrade-windows-to-education)
|
||||
| **Workplace join (add work or school account)** | Personal (or student-owned) | ✅ | | | |
|
||||
| **Microsoft Entra join** | Organization | ✅ | ✅ | | ✅ |
|
||||
| **Microsoft Entra hybrid join** | Organization | ✅ | ✅ | ✅ | ✅ |
|
||||
|
||||
@ -63,10 +63,8 @@ productDirectory:
|
||||
- title: Learn how to manage Windows devices
|
||||
imageSrc: /media/common/i_management.svg
|
||||
links:
|
||||
- url: tutorial-school-deployment/manage-overview.md
|
||||
- url: /mem/intune/industry/education/tutorial-school-deployment/manage-overview
|
||||
text: Manage devices with Microsoft Intune
|
||||
- url: tutorial-school-deployment/manage-surface-devices.md
|
||||
text: Management functionalities for Surface devices
|
||||
- url: /education/windows/get-minecraft-for-education
|
||||
text: Get and deploy Minecraft Education
|
||||
- url: /windows/client-management
|
||||
|
||||
@ -4,8 +4,6 @@ items:
|
||||
- name: Tutorials
|
||||
expanded: true
|
||||
items:
|
||||
- name: Deploy and manage Windows devices in a school
|
||||
href: tutorial-school-deployment/toc.yml
|
||||
- name: Deploy applications to Windows 11 SE
|
||||
href: tutorial-deploy-apps-winse/toc.yml
|
||||
- name: Concepts
|
||||
|
||||
@ -1,77 +0,0 @@
|
||||
---
|
||||
title: Configure applications with Microsoft Intune
|
||||
description: Learn how to configure applications with Microsoft Intune in preparation for device deployment.
|
||||
ms.date: 01/16/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
# Configure applications with Microsoft Intune
|
||||
|
||||
With Intune for Education, school IT administrators have access to diverse applications to help students unlock their learning potential. This section discusses tools and resources for adding apps to Intune for Education.
|
||||
|
||||
Applications can be assigned to groups:
|
||||
|
||||
- If you target apps to a **group of users**, the apps will be installed on any managed devices that the users sign into
|
||||
- If you target apps to a **group of devices**, the apps will be installed on those devices and available to any user who signs in
|
||||
|
||||
> [!div class="checklist"]
|
||||
>In this section you will:
|
||||
>
|
||||
> - Add apps to Intune for Education
|
||||
> - Assign apps to groups
|
||||
> - Review some considerations for Windows 11 SE devices
|
||||
|
||||
## Add apps to Intune for Education
|
||||
|
||||
Intune for Education supports the deployment of two types of Windows applications: **web apps** and **desktop apps**.
|
||||
|
||||
:::image type="content" source="./images/intune-education-apps.png" alt-text="Intune for Education - Apps" lightbox="./images/intune-education-apps.png" border="true":::
|
||||
|
||||
### Desktop apps
|
||||
|
||||
The addition of desktop applications to Intune should be carried out by repackaging the apps, and defining the commands to silently install them. The process is described in the article [Add, assign, and monitor a Win32 app in Microsoft Intune][MEM-1].
|
||||
|
||||
### Web apps
|
||||
|
||||
To create web applications in Intune for Education:
|
||||
|
||||
1. Sign in to the <a href="https://intuneeducation.portal.azure.com/" target="_blank"><b>Intune for Education portal</b></a>
|
||||
1. Select **Apps**
|
||||
1. Select **New app** > **New web app**
|
||||
1. Provide a URL for the web app, a name and, optionally, an icon and description
|
||||
1. Select **Save**
|
||||
|
||||
For more information, see [Add web apps][INT-2].
|
||||
|
||||
## Assign apps to groups
|
||||
|
||||
To assign applications to a group of users or devices:
|
||||
|
||||
1. Sign in to the <a href="https://intuneeducation.portal.azure.com/" target="_blank"><b>Intune for Education portal</b></a>
|
||||
1. Select **Groups** > Pick a group to manage
|
||||
1. Select **Apps**
|
||||
1. Select either **Web apps** or **Windows apps**
|
||||
1. Select the apps you want to assign to the group > Save
|
||||
|
||||
## Considerations for Windows 11 SE
|
||||
|
||||
Windows 11 SE prevents the installation and execution of third party applications with a technology called **Windows Defender Application Control** (WDAC).
|
||||
WDAC applies an *allowlist* policy, which ensures that unwanted apps don't run or get installed. However, it also prevents IT admins from deploying apps to Windows 11 SE devices, unless they're included in the E Mode policy.
|
||||
|
||||
To learn more about which apps are supported in Windows 11 SE, and how to deploy them, see the tutorial [Deploy applications to Windows 11 SE with Intune][EDU-1].
|
||||
|
||||
## Next steps
|
||||
|
||||
With the applications configured, you can now deploy students' and teachers' devices.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Next: Deploy devices >](enroll-overview.md)
|
||||
|
||||
<!-- Reference links in article -->
|
||||
|
||||
[EDU-1]: ../tutorial-deploy-apps-winse/index.md
|
||||
|
||||
[MEM-1]: /mem/intune/apps/apps-win32-add
|
||||
|
||||
[INT-1]: /intune-education/express-configuration-intune-edu
|
||||
[INT-2]: /intune-education/add-web-apps-edu
|
||||
@ -1,133 +0,0 @@
|
||||
---
|
||||
title: Configure and secure devices with Microsoft Intune
|
||||
description: Learn how to configure policies with Microsoft Intune in preparation for device deployment.
|
||||
ms.date: 01/16/2024
|
||||
ms.topic: tutorial
|
||||
ms.collection: essentials-manage
|
||||
---
|
||||
|
||||
# Configure and secure devices with Microsoft Intune
|
||||
|
||||
With Intune for Education, you can configure settings for devices in the school, to ensure that they comply with specific policies.
|
||||
For example, you may need to secure your devices, ensuring that they are kept up to date. Or you may need to configure all the devices with the same look and feel.
|
||||
|
||||
Settings can be assigned to groups:
|
||||
|
||||
- If you target settings to a **group of users**, those settings will apply, regardless of what managed devices the targeted users sign in to
|
||||
- If you target settings to a **group of devices**, those settings will apply regardless of who is using the devices
|
||||
|
||||
There are two ways to manage settings in Intune for Education:
|
||||
|
||||
- **Express Configuration.** This option is used to configure a selection of settings that are commonly used in school environments
|
||||
- **Group settings.** This option is used to configure all settings that are offered by Intune for Education
|
||||
|
||||
> [!NOTE]
|
||||
> Express Configuration is ideal when you are getting started. Settings are pre-configured to Microsoft-recommended values, but can be changed to fit your school's needs. It is recommended to use Express Configuration to initially set up your Windows devices.
|
||||
|
||||
|
||||
> [!div class="checklist"]
|
||||
>In this section you will:
|
||||
>
|
||||
> - Configure settings with Express Configuration
|
||||
> - Configure group settings
|
||||
> - Create Windows Update policies
|
||||
> - Configure security policies
|
||||
|
||||
## Configure settings with Express Configuration
|
||||
|
||||
With Express Configuration, you can get Intune for Education up and running in just a few steps. You can select a group of devices or users, select applications to distribute, and choose settings from the most commonly used in schools.
|
||||
|
||||
> [!TIP]
|
||||
> To learn more, and practice step-by-step Express Configuration in Intune for Education, try <a href="https://www.microsoft.com/en-us/education/interactive-demos/deploy-apps-and-policies" target="_blank"><u>this interactive demo</u></a>.
|
||||
|
||||
## Configure group settings
|
||||
|
||||
Groups are used to manage users and devices with similar management needs, allowing you to apply changes to many devices or users at once. To review the available group settings:
|
||||
|
||||
1. Sign in to the <a href="https://intuneeducation.portal.azure.com/" target="_blank"><b>Intune for Education portal</b></a>
|
||||
1. Select **Groups** > Pick a group to manage
|
||||
1. Select **Windows device settings**
|
||||
1. Expand the different categories and review information about individual settings
|
||||
|
||||
Settings that are commonly configured for student devices include:
|
||||
|
||||
- Wallpaper and lock screen background. See: [Lock screen and desktop][INT-7]
|
||||
- Wi-Fi connections. See: [Add Wi-Fi profiles][INT-8]
|
||||
- Enablement of the integrated testing and assessment solution *Take a Test*. See: [Add Take a Test profile][INT-9]
|
||||
|
||||
For more information, see [Windows device settings in Intune for Education][INT-3].
|
||||
|
||||
## Create Windows Update policies
|
||||
|
||||
It is important to keep Windows devices up to date with the latest security updates. You can create Windows Update policies using Intune for Education.
|
||||
|
||||
To create a Windows Update policy:
|
||||
|
||||
1. Select **Groups** > Pick a group to manage
|
||||
1. Select **Windows device settings**
|
||||
1. Expand the category **Update and upgrade**
|
||||
1. Configure the required settings as needed
|
||||
|
||||
For more information, see [Updates and upgrade][INT-6].
|
||||
|
||||
> [!NOTE]
|
||||
> If you require a more complex Windows Update policy, you can create it in Microsoft Intune. For more information:
|
||||
> - [<u>What is Windows Update for Business?</u>][WIN-1]
|
||||
> - [<u>Manage Windows software updates in Intune</u>][MEM-1]
|
||||
|
||||
## Configure security policies
|
||||
|
||||
It is critical to ensure that the devices you manage are secured using the different security technologies available in Windows.
|
||||
Intune for Education provides different settings to secure devices.
|
||||
|
||||
To create a security policy:
|
||||
|
||||
1. Select **Groups** > Pick a group to manage
|
||||
1. Select **Windows device settings**
|
||||
1. Expand the category **Security**
|
||||
1. Configure the required settings as needed, including
|
||||
- Windows Defender
|
||||
- Windows Encryption
|
||||
- Windows SmartScreen
|
||||
|
||||
For more information, see [Security][INT-4].
|
||||
|
||||
> [!NOTE]
|
||||
> If you require more sophisticated security policies, you can create them in Microsoft Intune. For more information:
|
||||
> - [<u>Antivirus</u>][MEM-2]
|
||||
> - [<u>Disk encryption</u>][MEM-3]
|
||||
> - [<u>Firewall</u>][MEM-4]
|
||||
> - [<u>Endpoint detection and response</u>][MEM-5]
|
||||
> - [<u>Attack surface reduction</u>][MEM-6]
|
||||
> - [<u>Account protection</u>][MEM-7]
|
||||
|
||||
---
|
||||
|
||||
## Next steps
|
||||
|
||||
With the Intune service configured, you can configure policies and applications to deploy to your students' and teachers' devices.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Next: Configure applications >](configure-device-apps.md)
|
||||
|
||||
<!-- Reference links in article -->
|
||||
|
||||
[EDU-1]: /education/windows/windows-11-se-overview
|
||||
|
||||
[INT-2]: /intune-education/express-configuration-intune-edu
|
||||
[INT-3]: /intune-education/all-edu-settings-windows
|
||||
[INT-4]: /intune-education/all-edu-settings-windows#security
|
||||
[INT-6]: /intune-education/all-edu-settings-windows#updates-and-upgrade
|
||||
[INT-7]: /intune-education/all-edu-settings-windows#lock-screen-and-desktop
|
||||
[INT-8]: /intune-education/add-wi-fi-profile
|
||||
[INT-9]: /intune-education/take-a-test-profiles
|
||||
|
||||
[WIN-1]: /windows/deployment/update/waas-manage-updates-wufb
|
||||
|
||||
[MEM-1]: /mem/intune/protect/windows-update-for-business-configure
|
||||
[MEM-2]: /mem/intune/protect/endpoint-security-antivirus-policy
|
||||
[MEM-3]: /mem/intune/protect/encrypt-devices
|
||||
[MEM-4]: /mem/intune/protect/endpoint-security-firewall-policy
|
||||
[MEM-5]: /mem/intune/protect/endpoint-security-edr-policy
|
||||
[MEM-6]: /mem/intune/protect/endpoint-security-asr-policy
|
||||
[MEM-7]: /mem/intune/protect/endpoint-security-account-protection-policy
|
||||
@ -1,61 +0,0 @@
|
||||
---
|
||||
title: Configure devices with Microsoft Intune
|
||||
description: Learn how to configure policies and applications in preparation for device deployment.
|
||||
ms.date: 11/09/2023
|
||||
ms.topic: tutorial
|
||||
ms.collection: essentials-manage
|
||||
---
|
||||
|
||||
# Configure settings and applications with Microsoft Intune
|
||||
|
||||
Before distributing devices to your users, you must ensure that the devices will be configured with the required policies, settings, and applications as they get enrolled in Intune.
|
||||
Microsoft Intune uses Microsoft Entra groups to assign policies and applications to devices.
|
||||
With Microsoft Intune for Education, you can conveniently create groups and assign policies and applications to them.
|
||||
|
||||
|
||||
> [!div class="checklist"]
|
||||
>In this section you will:
|
||||
>
|
||||
> - Create groups
|
||||
> - Create and assign policies to groups
|
||||
> - Create and assign applications to groups
|
||||
|
||||
## Create groups
|
||||
|
||||
By organizing devices, students, classrooms, or learning curricula into groups, you can provide students with the resources and configurations they need.
|
||||
|
||||
By default, Intune for Education creates two default groups: *All devices* and *All users*.
|
||||
Two additional groups are pre-created if you use **Microsoft School Data Sync (SDS)**: *All teachers* and *All students*. SDS can also be configured to automatically create and maintain groups of students and teachers for each school.
|
||||
|
||||
:::image type="content" source="./images/intune-education-groups.png" alt-text="Intune for Education - Groups blade" border="true":::
|
||||
|
||||
Beyond the defaults, groups can be customized to suit various needs. For example, if you have both *Windows 10* and *Windows 11 SE* devices in your school, you can create groups, such as *Windows 10 devices* and *Windows 11 SE devices*, to assign different policies and applications to.
|
||||
|
||||
Two group types can be created:
|
||||
|
||||
- **Assigned groups** are used when you want to manually add users or devices to a group
|
||||
- **Dynamic groups** reference rules that you create to assign students or devices to groups, which automate the membership's maintenance of those groups
|
||||
|
||||
> [!TIP]
|
||||
> If you target applications and policies to a *device dynamic group*, they will be applied to the devices as soon as they are enrolled in Intune, before users signs in. This can be useful in bulk enrollment scenarios, where devices are enrolled without requiring users to sign in. Devices can be configured and prepared in advance, before distribution.
|
||||
|
||||
For more information, see:
|
||||
|
||||
- [Create groups in Intune for Education][EDU-1]
|
||||
- [Manually add or remove users and devices to an existing assigned group][EDU-2]
|
||||
- [Edit dynamic group rules to accommodate for new devices, locations, or school years][EDU-3]
|
||||
|
||||
________________________________________________________
|
||||
|
||||
## Next steps
|
||||
|
||||
With the groups created, you can configure policies and applications to deploy to your groups.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Next: Configure policies >](configure-device-settings.md)
|
||||
|
||||
<!-- Reference links in article -->
|
||||
|
||||
[EDU-1]: /intune-education/create-groups
|
||||
[EDU-2]: /intune-education/edit-groups-intune-for-edu
|
||||
[EDU-3]: /intune-education/edit-groups-intune-for-edu#edit-dynamic-group-rules
|
||||
@ -1,148 +0,0 @@
|
||||
---
|
||||
title: Enrollment in Intune with Windows Autopilot
|
||||
description: Learn how to join Microsoft Entra ID and enroll in Intune using Windows Autopilot.
|
||||
ms.date: 01/16/2024
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
# Windows Autopilot
|
||||
|
||||
Windows Autopilot is designed to simplify all parts of Windows devices lifecycle, from initial deployment through end of life. Using cloud-based services, Windows Autopilot can reduce the overall costs for deploying, managing, and retiring devices.
|
||||
|
||||
Traditionally, IT pros spend a significant amount of time building and customizing images that will later be deployed to devices. Windows Autopilot introduces a new, simplified approach. Devices don't need to be reimaged, rather they can be deployed with the OEM image, and customized using cloud-based services.
|
||||
|
||||
From the user's perspective, it only takes a few simple operations to make their device ready to use. The only interaction required from the end user is to set their language and regional settings, connect to a network, and verify their credentials. Everything beyond that is automated.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before setting up Windows Autopilot, consider these prerequisites:
|
||||
|
||||
- **Software requirements.** Ensure your school and devices meet the [software, networking, licensing, and configuration requirements][WIN-1] for Windows Autopilot
|
||||
- **Devices ordered and registered.** Ensure your school IT administrator or Microsoft partner has ordered the devices from an original equipment manufacturer (OEM) and registered them for the Autopilot deployment service. To connect with a partner, you can use the [Microsoft Partner Center][MSFT-1] and work with them to register your devices
|
||||
- **Networking requirements.** Ensure students know to connect to the school network during OOBE setup. For more information on managing devices behind firewalls and proxy servers, see [Network endpoints for Microsoft Intune][MEM-1]
|
||||
|
||||
> [!NOTE]
|
||||
> Where not explicitly specified, both HTTPS (443) and HTTP (80) must be accessible. If you are auto-enrolling your devices into Microsoft Intune or deploying Microsoft Office, follow the networking guidelines for [<u>Microsoft Intune</u>][INT-1] and [<u>Microsoft 365</u>][M365-1].
|
||||
|
||||
## Register devices to Windows Autopilot
|
||||
|
||||
Before deployment, devices must be registered in the Windows Autopilot service. Each device's unique hardware identity (known as a *hardware hash*) must be uploaded to the Autopilot service. In this way, the Autopilot service can recognize which tenant devices belong to, and which OOBE experience it should present. There are three main ways to register devices to Autopilot:
|
||||
|
||||
- **OEM registration process.** When you purchase devices from an OEM or Reseller, that company can automatically register devices to Windows Autopilot and associate them to your tenant. Before this registration can happen, a *Global Administrator* must grant the OEM/Reseller permissions to register devices. For more information, see [OEM registration][MEM-2]
|
||||
> [!NOTE]
|
||||
> For **Microsoft Surface registration**, collect the details shown in this [<u>documentation table</u>][SURF-1] and follow the instruction to submit the request form to Microsoft Support.
|
||||
- **Cloud Solution Provider (CSP) registration process.** As with OEMs, CSP partners must be granted permission to register devices for a school. For more information, see [Partner registration][MEM-5]
|
||||
> [!TIP]
|
||||
> Try the <a href="https://cloudpartners.transform.microsoft.com/resources/autopilot-in-edu-setup-english" target="_blank"><u>Microsoft Partner Center clickable demo</u></a>, which provides detailed steps to establish a partner relationship and register devices.
|
||||
- **Manual registration.** To manually register a device, you must first capture its hardware hash. Once this process has been completed, the hardware hash can be uploaded to the Windows Autopilot service using [Microsoft Intune][MEM-6]
|
||||
> [!IMPORTANT]
|
||||
> **Windows 11 SE** devices do not support the use of Windows PowerShell or Microsoft Configuration Manager to capture hardware hashes. Hardware hashes can only be captured manually. We recommend working with an OEM, partner, or device reseller to register devices.
|
||||
|
||||
## Create groups for Autopilot devices
|
||||
|
||||
**Windows Autopilot deployment profiles** determine the Autopilot *deployment mode* and define the out-of-box experience of your devices. A device group is required to assign a Windows Autopilot deployment profile to the devices.
|
||||
For this task, it's recommended to create dynamic device groups using Autopilot attributes.
|
||||
|
||||
Here are the steps for creating a dynamic group for the devices that have an assigned Autopilot group tag:
|
||||
|
||||
1. Sign in to the <a href="https://intuneeducation.portal.azure.com/" target="_blank"><b>Intune for Education portal</b></a>
|
||||
1. Select **Groups** > **Create group**
|
||||
1. Specify a **Group name** and select **Dynamic**
|
||||
1. Under **Rules**, select **I want to manage: Devices** and use the clause **Where: Device group tag starts with**, specifying the required tag value
|
||||
1. Select **Create group**
|
||||
:::image type="content" source="./images/intune-education-autopilot-group.png" alt-text="Intune for Education - creation of a dynamic group for Autopilot devices" border="true":::
|
||||
|
||||
More advanced dynamic membership rules can be created from Microsoft Intune admin center. For more information, see [Create an Autopilot device group using Intune][MEM-3].
|
||||
|
||||
> [!TIP]
|
||||
> You can use these dynamic groups not only to assign Autopilot profiles, but also to target applications and settings.
|
||||
|
||||
## Create Autopilot deployment profiles
|
||||
|
||||
For Autopilot devices to offer a customized OOBE experience, you must create **Windows Autopilot deployment profiles** and assign them to a group containing the devices.
|
||||
A deployment profile is a collection of settings that determine the behavior of the device during OOBE. Among other settings, a deployment profile specifies a **deployment mode**, which can either be:
|
||||
|
||||
1. **User-driven:** devices with this profile are associated with the user enrolling the device. User credentials are required to complete the Microsoft Entra join process during OOBE
|
||||
1. **Self-deploying:** devices with this profile aren't associated with the user enrolling the device. User credentials aren't required to complete the Microsoft Entra join process. Rather, the device is joined automatically and, for this reason, specific hardware requirements must be met to use this mode
|
||||
|
||||
To create an Autopilot deployment profile:
|
||||
|
||||
1. Sign in to the <a href="https://intuneeducation.portal.azure.com/" target="_blank"><b>Intune for Education portal</b></a>
|
||||
1. Select **Groups** > Select a group from the list
|
||||
1. Select **Windows device settings**
|
||||
1. Expand the **Enrolment** category
|
||||
1. From **Configure Autopilot deployment profile for device** select **User-driven**
|
||||
1. Ensure that **User account type** is configured as **Standard**
|
||||
1. Select **Save**
|
||||
|
||||
While Intune for Education offers simple options for Autopilot configurations, more advanced deployment profiles can be created from Microsoft Intune admin center. For more information, see [Windows Autopilot deployment profiles][MEM-4].
|
||||
|
||||
### Configure an Enrollment Status Page
|
||||
|
||||
An Enrollment Status Page (ESP) is a greeting page displayed to users while enrolling or signing in for the first time to Windows devices. The ESP displays provisioning progress, showing applications and profiles installation status.
|
||||
|
||||
:::image type="content" source="./images/win11-oobe-esp.gif" alt-text="Windows OOBE - enrollment status page animation." border="false":::
|
||||
|
||||
> [!NOTE]
|
||||
> Some Windows Autopilot deployment profiles **require** the ESP to be configured.
|
||||
|
||||
To deploy the ESP to devices, you need to create an ESP profile in Microsoft Intune.
|
||||
|
||||
> [!TIP]
|
||||
> While testing the deployment process, you can configure the ESP to:
|
||||
> - allow the reset of the devices in case the installation fails
|
||||
> - allow the use of the device if installation error occurs
|
||||
>
|
||||
> This enables you to troubleshoot the installation process in case any issues arise and to easily reset the OS. You can turn these settings off once you are done testing.
|
||||
|
||||
For more information, see [Set up the Enrollment Status Page][MEM-3].
|
||||
|
||||
> [!CAUTION]
|
||||
> The Enrollment Status Page (ESP) is compatible with Windows 11 SE. However, due to the E Mode policy, devices may not complete the enrollment. For more information, see [Enrollment Status Page][EDU-3].
|
||||
|
||||
### Autopilot end-user experience
|
||||
|
||||
Once configuration is complete and devices are distributed, students and teachers are able to complete the out-of-box experience with Autopilot. They can set up their devices at home, at school, or wherever there's a reliable Internet connection.
|
||||
When a Windows device is turned on for the first time, the end-user experience with Windows Autopilot is as follows:
|
||||
|
||||
1. Identify the language and region
|
||||
1. Select the keyboard layout and decide on the option for a second keyboard layout
|
||||
1. Connect to the internet: if connecting through Wi-Fi, the user will be prompted to connect to a wireless network. If the device is connected through an ethernet cable, Windows will skip this step
|
||||
1. Apply updates: the device will look for and apply required updates
|
||||
1. Windows will detect if the device has an Autopilot profile assigned to it. If so, it will proceed with the customized OOBE experience. If the Autopilot profile specifies a naming convention for the device, the device will be renamed, and a reboot will occur
|
||||
1. The user authenticates to Microsoft Entra ID, using the school account
|
||||
1. The device joins Microsoft Entra ID, enrolls in Intune and all the settings and applications are configured
|
||||
|
||||
> [!NOTE]
|
||||
> Some of these steps may be skipped, depending on the Autopilot profile configuration and if the device is using a wired connection.
|
||||
|
||||
:::image type="content" source="./images/win11-login-screen.png" alt-text="Windows 11 login screen" border="false":::
|
||||
|
||||
________________________________________________________
|
||||
## Next steps
|
||||
|
||||
With the devices joined to Microsoft Entra tenant and managed by Intune, you can use Intune to maintain them and report on their status.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Next: Manage devices >](manage-overview.md)
|
||||
|
||||
<!-- Reference links in article -->
|
||||
|
||||
[MEM-1]: /mem/intune/fundamentals/intune-endpoints
|
||||
[MEM-2]: /mem/autopilot/oem-registration
|
||||
[MEM-3]: /mem/autopilot/enrollment-autopilot#create-an-autopilot-device-group-using-intune
|
||||
[MEM-4]: /mem/autopilot/profiles
|
||||
[MEM-5]: /mem/autopilot/partner-registration
|
||||
[MEM-6]: /mem/autopilot/add-devices
|
||||
|
||||
[WIN-1]: /windows/deployment/windows-autopilot/windows-autopilot-requirements
|
||||
|
||||
[MSFT-1]: https://partner.microsoft.com/
|
||||
|
||||
[INT-1]: /intune/network-bandwidth-use
|
||||
|
||||
[M365-1]: https://support.office.com/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2
|
||||
|
||||
[EDU-3]: ../tutorial-deploy-apps-winse/considerations.md#enrollment-status-page
|
||||
|
||||
[SURF-1]: /surface/surface-autopilot-registration-support
|
||||
@ -1,32 +0,0 @@
|
||||
---
|
||||
title: Enrollment in Intune with standard out-of-box experience (OOBE)
|
||||
description: Learn how to join devices to Microsoft Entra ID from OOBE and automatically get them enrolled in Intune.
|
||||
ms.date: 11/09/2023
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
# Automatic Intune enrollment via Microsoft Entra join
|
||||
|
||||
If you're setting up a Windows device individually, you can use the out-of-box experience to join it to your school's Microsoft Entra tenant, and automatically enroll it in Intune.
|
||||
With this process, no advance preparation is needed:
|
||||
|
||||
1. Follow the on-screen prompts for region selection, keyboard selection, and network connection
|
||||
1. Wait for updates. If any updates are available, they'll be installed at this time
|
||||
:::image type="content" source="./images/win11-oobe-updates.png" alt-text="Windows 11 OOBE - updates page" border="true":::
|
||||
1. When prompted, select **Set up for work or school** and authenticate using your school's Microsoft Entra account
|
||||
:::image type="content" source="./images/win11-oobe-auth.png" alt-text="Windows 11 OOBE - authentication page" border="true":::
|
||||
1. The device will join Microsoft Entra ID and automatically enroll in Intune. All settings defined in Intune will be applied to the device
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you configured enrollment restrictions in Intune blocking personal Windows devices, this process will not complete. You will need to use a different enrollment method, or ensure that the devices are registered in Autopilot.
|
||||
|
||||
:::image type="content" source="./images/win11-login-screen.png" alt-text="Windows 11 login screen" border="false":::
|
||||
|
||||
---
|
||||
|
||||
## Next steps
|
||||
|
||||
With the devices joined to Microsoft Entra tenant and managed by Intune, you can use Intune to maintain them and report on their status.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Next: Manage devices >](manage-overview.md)
|
||||
@ -1,31 +0,0 @@
|
||||
---
|
||||
title: Device enrollment overview
|
||||
description: Learn about the different options to enroll Windows devices in Microsoft Intune
|
||||
ms.date: 11/09/2023
|
||||
ms.topic: overview
|
||||
---
|
||||
|
||||
# Device enrollment overview
|
||||
|
||||
There are three main methods for joining Windows devices to Microsoft Entra ID and getting them enrolled and managed by Intune:
|
||||
|
||||
- **Automatic Intune enrollment via Microsoft Entra join** happens when a user first turns on a device that is in out-of-box experience (OOBE), and selects the option to join Microsoft Entra ID. In this scenario, the user can customize certain Windows functionalities before reaching the desktop, and becomes a local administrator of the device. This option isn't an ideal enrollment method for education devices
|
||||
- **Bulk enrollment with provisioning packages.** Provisioning packages are files that can be used to set up Windows devices, and can include information to connect to Wi-Fi networks and to join a Microsoft Entra tenant. Provisioning packages can be created using either **Set Up School PCs** or **Windows Configuration Designer** applications. These files can be applied during or after the out-of-box experience
|
||||
- **Enrollment via Windows Autopilot.** Windows Autopilot is a collection of cloud services to configure the out-of-box experience, enabling light-touch or zero-touch deployment scenarios. Windows Autopilot simplifies the Windows device lifecycle, from initial deployment to end of life, for OEMs, resellers, IT administrators and end users
|
||||
|
||||
## Choose the enrollment method
|
||||
|
||||
**Windows Autopilot** and the **Set up School PCs** app are usually the most efficient options for school environments.
|
||||
This [table][INT-1] describes the ideal scenarios for using either option. It's recommended to review the table when planning your enrollment and deployment strategies.
|
||||
|
||||
:::image type="content" source="./images/enroll.png" alt-text="The device lifecycle for Intune-managed devices - enrollment" border="false":::
|
||||
|
||||
Select one of the following options to learn the next steps about the enrollment method you chose:
|
||||
> [!div class="op_single_selector"]
|
||||
> - [Automatic Intune enrollment via Microsoft Entra join](enroll-entra-join.md)
|
||||
> - [Bulk enrollment with provisioning packages](enroll-package.md)
|
||||
> - [Enroll devices with Windows Autopilot](enroll-autopilot.md)
|
||||
|
||||
<!-- Reference links in article -->
|
||||
|
||||
[INT-1]: /intune-education/add-devices-windows#when-to-use-set-up-school-pcs-vs-windows-autopilot
|
||||
@ -1,65 +0,0 @@
|
||||
---
|
||||
title: Enrollment of Windows devices with provisioning packages
|
||||
description: Learn about how to enroll Windows devices with provisioning packages using SUSPCs and Windows Configuration Designer.
|
||||
ms.date: 11/09/2023
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
# Enrollment with provisioning packages
|
||||
|
||||
Enrolling devices with provisioning packages is an efficient way to deploy a large number of Windows devices. Some of the benefits of provisioning packages are:
|
||||
|
||||
- There are no particular hardware dependencies on the devices to complete the enrollment process
|
||||
- Devices don't need to be registered in advance
|
||||
- Enrollment is a simple task: just open a provisioning package and the process is automated
|
||||
|
||||
You can create provisioning packages using either **Set Up School PCs** or **Windows Configuration Designer** applications, which are described in the following sections.
|
||||
|
||||
## Set up School PCs
|
||||
|
||||
With Set up School PCs, you can create a package containing the most common device configurations that students need, and enroll devices in Intune. The package is saved on a USB stick, which can then be plugged into devices during OOBE. Applications and settings will be automatically applied to the devices, including the Microsoft Entra join and Intune enrollment process.
|
||||
|
||||
### Create a provisioning package
|
||||
|
||||
The Set Up School PCs app guides you through configuration choices for school-owned devices.
|
||||
|
||||
:::image type="content" source="./images/supcs-win11se.png" alt-text="Configure device settings in Set Up School PCs app" border="false":::
|
||||
|
||||
> [!CAUTION]
|
||||
> If you are creating a provisioning package for **Windows 11 SE** devices, ensure to select the correct *OS version* in the *Configure device settings* page.
|
||||
|
||||
Set Up School PCs will configure many settings, allowing you to optimize devices for shared use and other scenarios.
|
||||
|
||||
For more information on prerequisites, configuration, and recommendations, see [Use the Set Up School PCs app][EDU-1].
|
||||
|
||||
> [!TIP]
|
||||
> To learn more and practice with Set up School PCs, try the <a href="https://www.microsoft.com/en-us/education/interactive-demos/enroll-devices-at-scale" target="_blank"><u>Set Up School PCs demo</u></a>, which provides detailed steps to create a provisioning package and deploy a device.
|
||||
## Windows Configuration Designer
|
||||
|
||||
Windows Configuration Designer is especially useful in scenarios where a school needs to provision packages for both bring-you-own devices and school-owned devices. Differently from Set Up School PCs, Windows Configuration Designer doesn't offer a guided experience, and allows granular customizations, including the possibility to embed scripts in the package.
|
||||
|
||||
:::image type="content" source="./images/wcd.png" alt-text="Set up device page in Windows Configuration Designer" border="false":::
|
||||
|
||||
For more information, see [Install Windows Configuration Designer][WIN-1], which provides details about the app, its provisioning process, and considerations for its use.
|
||||
|
||||
## Enroll devices with the provisioning package
|
||||
|
||||
To provision Windows devices with provisioning packages, insert the USB stick containing the package during the out-of-box experience. The devices will read the content of the package, join Microsoft Entra ID and automatically enroll in Intune.
|
||||
All settings defined in the package and in Intune will be applied to the device, and the device will be ready to use.
|
||||
|
||||
:::image type="content" source="./images/win11-oobe-ppkg.gif" alt-text="Windows 11 OOBE - enrollment with provisioning package animation." border="false":::
|
||||
|
||||
---
|
||||
|
||||
## Next steps
|
||||
|
||||
With the devices joined to Microsoft Entra tenant and managed by Intune, you can use Intune to maintain them and report on their status.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Next: Manage devices >](manage-overview.md)
|
||||
|
||||
<!-- Reference links in article -->
|
||||
|
||||
[EDU-1]: /education/windows/use-set-up-school-pcs-app
|
||||
|
||||
[WIN-1]: /windows/configuration/provisioning-packages/provisioning-install-icd
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 122 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 224 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 136 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 80 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 214 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 84 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 143 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 257 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 173 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 155 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 167 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 89 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 113 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 95 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 224 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 86 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 187 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 218 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 76 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 212 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 155 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 193 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 106 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 133 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 249 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 146 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 599 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 299 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.5 MiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.1 MiB |
Binary file not shown.
|
Before Width: | Height: | Size: 260 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 55 KiB |
@ -1,81 +0,0 @@
|
||||
---
|
||||
title: Introduction to the tutorial deploy and manage Windows devices in a school
|
||||
description: Introduction to deployment and management of Windows devices in education environments.
|
||||
ms.date: 11/09/2023
|
||||
ms.topic: tutorial
|
||||
ms.collection: essentials-get-started
|
||||
---
|
||||
|
||||
# Tutorial: deploy and manage Windows devices in a school
|
||||
|
||||
This guide introduces the tools and services available from Microsoft to deploy, configure and manage Windows devices in an education environment.
|
||||
|
||||
## Audience and user requirements
|
||||
|
||||
This tutorial is intended for education professionals responsible for deploying and managing Windows devices, including:
|
||||
|
||||
- School leaders
|
||||
- IT administrators
|
||||
- Teachers
|
||||
- Microsoft partners
|
||||
|
||||
This content provides a comprehensive path for schools to deploy and manage new Windows devices with Microsoft Intune. It includes step-by-step information how to manage devices throughout their lifecycle, and specific guidance for **Windows 11 SE** and **Surface devices**.
|
||||
|
||||
> [!NOTE]
|
||||
> Depending on your school setup scenario, you may not need to implement all steps.
|
||||
|
||||
## Device lifecycle management
|
||||
|
||||
Historically, school IT administrators and educators have struggled to find an easy-to-use, flexible, and secure way to manage the lifecycle of the devices in their schools. In response, Microsoft has developed integrated suites of products for streamlined, cost-effective device lifecycle management.
|
||||
|
||||
Microsoft 365 Education provides tools and services that enable simplified management of all devices through Microsoft Intune services. With Microsoft's solutions, IT administrators have the flexibility to support diverse scenarios, including school-owned devices and bring-your-own devices.
|
||||
Microsoft Intune services include:
|
||||
|
||||
- [Microsoft Intune][MEM-1]
|
||||
- [Microsoft Intune for Education][INT-1]
|
||||
- [Configuration Manager][MEM-2]
|
||||
- [Desktop Analytics][MEM-3]
|
||||
- [Windows Autopilot][MEM-4]
|
||||
- [Surface Management Portal][MEM-5]
|
||||
|
||||
These services are part of the Microsoft 365 stack to help secure access, protect data, and manage risk.
|
||||
|
||||
## Why Intune for Education?
|
||||
|
||||
Windows devices can be managed with Intune for Education, enabling simplified management of multiple devices from a single point.
|
||||
From enrollment, through configuration and protection, to resetting, Intune for Education helps school IT administrators manage and optimize the devices throughout their lifecycle:
|
||||
|
||||
:::image type="content" source="./images/device-lifecycle.png" alt-text="The device lifecycle for Intune-managed devices" border="false":::
|
||||
|
||||
- **Enroll:** to enable remote device management, devices must be enrolled in Intune with an account in your Microsoft Entra tenant. Some enrollment methods require an IT administrator to initiate enrollment, while others require students to complete the initial device setup process. This document discusses the facets of various device enrollment methodologies
|
||||
- **Configure:** once the devices are enrolled in Intune, applications and settings will be applied, as defined by the IT administrator
|
||||
- **Protect and manage:** in addition to its configuration capabilities, Intune for Education helps protect devices from unauthorized access or malicious attacks. For example, adding an extra layer of authentication with Windows Hello can make devices more secure. Policies are available that let you control settings for Windows Firewall, Endpoint Protection, and software updates
|
||||
- **Retire:** when it's time to repurpose a device, Intune for Education offers several options, including resetting the device, removing it from management, or wiping school data. In this document, we cover different device return and exchange scenarios
|
||||
|
||||
## Four pillars of modern device management
|
||||
|
||||
In the remainder of this document, we'll discuss the key concepts and benefits of modern device management with Microsoft 365 solutions for education. The guidance is organized around the four main pillars of modern device management:
|
||||
|
||||
- **Identity management:** setting up and configuring the identity system, with Microsoft 365 Education and Microsoft Entra ID, as the foundation for user identity and authentication
|
||||
- **Initial setup:** setting up the Intune for Education environment for managing devices, including configuring settings, deploying applications, and defining updates cadence
|
||||
- **Device enrollment:** Setting up Windows devices for deployment and enrolling them in Intune for Education
|
||||
- **Device reset:** Resetting managed devices with Intune for Education
|
||||
|
||||
---
|
||||
|
||||
## Next steps
|
||||
|
||||
Let's begin with the creation and configuration of your Microsoft Entra tenant and Intune environment.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Next: Set up Microsoft Entra ID >](set-up-microsoft-entra-id.md)
|
||||
|
||||
<!-- Reference links in article -->
|
||||
|
||||
[MEM-1]: /mem/intune/fundamentals/what-is-intune
|
||||
[MEM-2]: /mem/configmgr/core/understand/introduction
|
||||
[MEM-3]: /mem/configmgr/desktop-analytics/overview
|
||||
[MEM-4]: /mem/autopilot/windows-autopilot
|
||||
[MEM-5]: /mem/autopilot/dfci-management
|
||||
|
||||
[INT-1]: /intune-education/what-is-intune-for-education
|
||||
@ -1,59 +0,0 @@
|
||||
---
|
||||
title: Manage devices with Microsoft Intune
|
||||
description: Overview of device management capabilities in Intune for Education, including remote actions, remote assistance and inventory/reporting.
|
||||
ms.date: 11/09/2023
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
# Manage devices with Microsoft Intune
|
||||
|
||||
Microsoft Intune offers a streamlined remote device management experience throughout the school year. IT administrators can optimize device settings, deploy new applications, updates, ensuring that security and privacy are maintained.
|
||||
|
||||
:::image type="content" source="./images/protect-manage.png" alt-text="The device lifecycle for Intune-managed devices - protect and manage devices" border="false":::
|
||||
|
||||
## Remote device management
|
||||
|
||||
With Intune for Education, there are several ways to manage students' devices. Groups can be created to organize devices and students, to facilitate remote management. You can determine which applications students have access to, and fine tune device settings and restrictions. You can also monitor which devices students sign in to, and troubleshoot devices remotely.
|
||||
|
||||
### Remote actions
|
||||
|
||||
Intune fo Education allows you to perform actions on devices without having to sign in to the devices. For example, you can send a command to a device to restart or to turn off, or you can locate a device.
|
||||
|
||||
:::image type="content" source="./images/remote-actions.png" alt-text="Remote actions available in Intune for Education when selecting a Windows device" lightbox="./images/remote-actions.png" border="true":::
|
||||
|
||||
With bulk actions, remote actions can be performed on multiple devices at once.
|
||||
|
||||
To learn more about remote actions in Intune for Education, see [Remote actions][EDU-1].
|
||||
|
||||
## Remote assistance
|
||||
|
||||
With devices managed by Intune for Education, you can remotely assist students and teachers that are having issues with their devices.
|
||||
|
||||
For more information, see [Remote assistance for managed devices - Intune for Education][EDU-2].
|
||||
|
||||
## Device inventory and reporting
|
||||
|
||||
With Intune for Education, it's possible view and report on current devices, applications, settings, and overall health. You can also download reports to review or share offline.
|
||||
|
||||
Here are the steps for generating reports in Intune for Education:
|
||||
|
||||
1. Sign in to the <a href="https://intuneeducation.portal.azure.com/" target="_blank"><b>Intune for Education portal</b></a>
|
||||
1. Select **Reports**
|
||||
1. Select between one of the report types:
|
||||
- Device inventory
|
||||
- Device actions
|
||||
- Application inventory
|
||||
- Settings errors
|
||||
- Windows Defender
|
||||
- Autopilot deployment
|
||||
1. If needed, use the search box to find specific devices, applications, and settings
|
||||
1. To download a report, select **Download**. The report will download as a comma-separated value (CSV) file, which you can view and modify in a spreadsheet app like Microsoft Excel.
|
||||
:::image type="content" source="./images/inventory-reporting.png" alt-text="Reporting options available in Intune for Education when selecting the reports blade" border="true":::
|
||||
|
||||
To learn more about reports in Intune for Education, see [Reports in Intune for Education][EDU-3].
|
||||
|
||||
<!-- Reference links in article -->
|
||||
|
||||
[EDU-1]: /intune-education/edu-device-remote-actions
|
||||
[EDU-2]: /intune-education/remote-assist-mobile-devices
|
||||
[EDU-3]: /intune-education/what-are-reports
|
||||
@ -1,44 +0,0 @@
|
||||
---
|
||||
title: Management functionalities for Surface devices
|
||||
description: Learn about the management capabilities offered to Surface devices, including firmware management and the Surface Management Portal.
|
||||
ms.date: 11/09/2023
|
||||
ms.topic: tutorial
|
||||
appliesto:
|
||||
- ✅ <b>Surface devices</b>
|
||||
---
|
||||
|
||||
# Management functionalities for Surface devices
|
||||
|
||||
Microsoft Surface devices offer advanced management functionalities, including the possibility to manage firmware settings and a web portal designed for them.
|
||||
|
||||
## Manage device firmware for Surface devices
|
||||
|
||||
Surface devices use a Unified Extensible Firmware Interface (UEFI) setting that allows you to enable or disable built-in hardware components, protect UEFI settings from being changed, and adjust device boot configuration. With [Device Firmware Configuration Interface profiles built into Intune][INT-1], Surface UEFI management extends the modern management capabilities to the hardware level. Windows can pass management commands from Intune to UEFI for Autopilot-deployed devices.
|
||||
|
||||
DFCI supports zero-touch provisioning, eliminates BIOS passwords, and provides control of security settings for boot options, cameras and microphones, built-in peripherals, and more. For more information, see [Manage DFCI on Surface devices][SURF-1] and [Manage DFCI with Windows Autopilot][MEM-1], which includes a list of requirements to use DFCI.
|
||||
|
||||
:::image type="content" source="./images/dfci-profile.png" alt-text="Creation of a DFCI profile from Microsoft Intune" lightbox="./images/dfci-profile-expanded.png" border="true":::
|
||||
|
||||
## Microsoft Surface Management Portal
|
||||
|
||||
Located in the Microsoft Intune admin center, the Microsoft Surface Management Portal enables you to self-serve, manage, and monitor your school's Intune-managed Surface devices at scale. Get insights into device compliance, support activity, warranty coverage, and more.
|
||||
|
||||
When Surface devices are enrolled in cloud management and users sign in for the first time, information automatically flows into the Surface Management Portal, giving you a single pane of glass for Surface-specific administration activities.
|
||||
|
||||
To access and use the Surface Management Portal:
|
||||
|
||||
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431)
|
||||
1. Select **All services** > **Surface Management Portal**
|
||||
:::image type="content" source="./images/surface-management-portal.png" alt-text="Surface Management Portal within Microsoft Intune" lightbox="./images/surface-management-portal-expanded.png" border="true":::
|
||||
1. To obtain insights for all your Surface devices, select **Monitor**
|
||||
- Devices that are out of compliance or not registered, have critically low storage, require updates, or are currently inactive, are listed here
|
||||
1. To obtain details on each insights category, select **View report**
|
||||
- This dashboard displays diagnostic information that you can customize and export
|
||||
1. To obtain the device's warranty information, select **Device warranty and coverage**
|
||||
1. To review a list of support requests and their status, select **Support requests**
|
||||
|
||||
<!-- Reference links in article -->
|
||||
|
||||
[INT-1]: /intune/configuration/device-firmware-configuration-interface-windows
|
||||
[MEM-1]: /mem/autopilot/dfci-management
|
||||
[SURF-1]: /surface/surface-manage-dfci-guide
|
||||
@ -1,111 +0,0 @@
|
||||
---
|
||||
title: Reset and wipe Windows devices
|
||||
description: Learn about the reset and wipe options for Windows devices using Intune for Education, including scenarios when to delete devices.
|
||||
ms.date: 11/09/2023
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
# Device reset options
|
||||
|
||||
There are different scenarios that require a device to be reset, for example:
|
||||
|
||||
- The device isn't responding to commands
|
||||
- The device is lost or stolen
|
||||
- It's the end of the life of the device
|
||||
- It's the end of the school year and you want to prepare the device for a new school year
|
||||
- The device has hardware problems and you want to send it to the service center
|
||||
|
||||
:::image type="content" source="./images/retire.png" alt-text="The device lifecycle for Intune-managed devices - retirement" border="false":::
|
||||
|
||||
Intune for Education provides two device reset functionalities that enable IT administrators to remotely execute them:
|
||||
|
||||
- **Factory reset** (also known as **wipe**) is used to wipe all data and settings from the device, returning it to the default factory settings
|
||||
- **Autopilot reset** is used to return the device to a fully configured or known IT-approved state
|
||||
|
||||
## Factory reset (wipe)
|
||||
|
||||
A factory reset, or a wipe, reverts a device to the original settings when it was purchased. All settings, applications and data installed on the device after purchase are removed. The device is also removed from Intune management.
|
||||
|
||||
Once the wipe is completed, the device will be in out-of-box experience.
|
||||
|
||||
Here are the steps to perform a factory reset from Intune for Education:
|
||||
|
||||
1. Sign in to the <a href="https://intuneeducation.portal.azure.com/" target="_blank"><b>Intune for Education portal</b></a>
|
||||
1. Select **Devices**
|
||||
1. Select the device you want to reset > **Factory reset**
|
||||
1. Select **Factory reset** to confirm the action
|
||||
|
||||
:::image type="content" source="./images/win11-wipe.png" alt-text="Three screenshots showing the device being wiped, ending up in OOBE" lightbox="./images/win11-wipe.png" border="false":::
|
||||
|
||||
Consider using factory reset in the following example scenarios:
|
||||
|
||||
- The device isn't working properly, and you want to reset it without reimaging it
|
||||
- It's the end of school year and you want to prepare the device for a new school year
|
||||
- You need to reassign the device to a different student, and you want to reset the device to its original settings
|
||||
- You're returning a device to the service center, and you want to remove all data and settings from the device
|
||||
|
||||
> [!TIP]
|
||||
> Consider that once the device is wiped, the new user will go through OOBE. This option may be ideal if the device is also registered in Autopilot to make the OOBE experience seamless, or if you plan to use a provisioning package to re-enroll the device.
|
||||
|
||||
## Autopilot Reset
|
||||
|
||||
Autopilot Reset is ideal when all data on a device needs to be wiped, but the device remains enrolled in your tenant.
|
||||
|
||||
Once the Autopilot reset action is completed, the device will ask to chose region and keyboard layout, then it will display the sign-in screen.
|
||||
|
||||
Here are the steps to perform an Autopilot reset from Intune for Education:
|
||||
|
||||
1. Sign in to the <a href="https://intuneeducation.portal.azure.com/" target="_blank"><b>Intune for Education portal</b></a>
|
||||
1. Select **Devices**
|
||||
1. Select the device you want to reset > **Autopilot reset**
|
||||
1. Select **Autopilot reset** to confirm the action
|
||||
|
||||
:::image type="content" source="./images/win11-autopilot-reset.png" alt-text="Three screenshots showing the device being wiped, ending up in the login screen" border="false":::
|
||||
|
||||
Consider using Autopilot reset in the following example scenarios:
|
||||
|
||||
- The device isn't working properly, and you want to reset it without reimaging it
|
||||
- It's the end of school year and you want to prepare the device for a new school year
|
||||
- You need to reassign the device to a different student, and you want to reset the device to without requiring the student to go through OOBE
|
||||
|
||||
> [!TIP]
|
||||
> Consider that the end user will **not** go through OOBE, and the association of the user to the device in Intune doesn't change. For this reason, this option may be ideal for devices that have been enrolled in Intune as *shared devices* (for example, a device that was enrolled with a provisioning package or using Autopilot self-deploying mode).
|
||||
|
||||
## Wiping and deleting a device
|
||||
|
||||
There are scenarios that require a device to be deleted from your tenant, for example:
|
||||
|
||||
- The device is lost or stolen
|
||||
- It's the end of the life of the device
|
||||
- The device has been replaced with a new device or has its motherboard replaced
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The following actions should only be performed for devices that are no longer going to be used in your tenant.
|
||||
|
||||
To completely remove a device, you need to perform the following actions:
|
||||
|
||||
1. If possible, perform a **factory reset (wipe)** of the device. If the device can't be wiped, delete the device from Intune using [these steps][MEM-1]
|
||||
1. If the device is registered in Autopilot, delete the Autopilot object using [these steps][MEM-2]
|
||||
1. Delete the device from Microsoft Entra ID using [these steps][MEM-3]
|
||||
|
||||
## Autopilot considerations for a motherboard replacement scenario
|
||||
|
||||
Repairing Autopilot-enrolled devices can be complex, as OEM requirements must be balanced with Autopilot requirements. If a motherboard replacement is needed on an Autopilot device, it's suggested the following process:
|
||||
|
||||
1. Deregister the device from Autopilot
|
||||
1. Replace the motherboard
|
||||
1. Capture a new device ID (4K HH)
|
||||
1. Re-register the device with Autopilot
|
||||
> [!IMPORTANT]
|
||||
> For DFCI management, the device must be re-registered by a partner or OEM. Self-registration of devices is not supported with DFCI management.
|
||||
1. Reset the device
|
||||
1. Return the device
|
||||
|
||||
For more information, see [Autopilot motherboard replacement scenario guidance][MEM-4].
|
||||
|
||||
<!-- Reference links in article -->
|
||||
|
||||
[MEM-1]: /mem/intune/remote-actions/devices-wipe#delete-devices-from-the-intune-portal
|
||||
[MEM-2]: /mem/intune/remote-actions/devices-wipe#delete-devices-from-the-intune-portal
|
||||
[MEM-3]: /mem/intune/remote-actions/devices-wipe#delete-devices-from-the-azure-active-directory-portal
|
||||
[MEM-4]: /mem/autopilot/autopilot-mbr
|
||||
@ -1,173 +0,0 @@
|
||||
---
|
||||
title: Set up Microsoft Entra ID
|
||||
description: Learn how to create and prepare your Microsoft Entra tenant for an education environment.
|
||||
ms.date: 01/16/2024
|
||||
ms.topic: tutorial
|
||||
appliesto:
|
||||
---
|
||||
|
||||
# Set up Microsoft Entra ID
|
||||
|
||||
The Microsoft platform for education simplifies the management of Windows devices with Intune for Education and Microsoft 365 Education. The first, fundamental step, is to configure the identity infrastructure to manage user access and permissions for your school.
|
||||
|
||||
Microsoft Entra ID, which is included with the Microsoft 365 Education subscription, provides authentication and authorization to any Microsoft cloud services. Identity objects are defined in Microsoft Entra ID for human identities, like students and teachers, as well as non-human identities, like devices, services, and applications. Once users get Microsoft 365 licenses assigned, they'll be able to consume services and access resources within the tenant. With Microsoft 365 Education, you can manage identities for your teachers and students, assign licenses to devices and users, and create groups for the classrooms.
|
||||
|
||||
> [!div class="checklist"]
|
||||
>In this section you will:
|
||||
>
|
||||
> - Set up a Microsoft 365 Education tenant
|
||||
> - Add users, create groups, and assign licenses
|
||||
> - Configure school branding
|
||||
> - Enable bulk enrollment
|
||||
|
||||
## Create a Microsoft 365 tenant
|
||||
|
||||
If you don't already have a Microsoft 365 tenant, you'll need to create one.
|
||||
|
||||
For more information, see [Create your Office 365 tenant account][M365-1]
|
||||
|
||||
> [!TIP]
|
||||
> To learn more, and practice how to configure the Microsoft 365 tenant for your school, try <a href="https://www.microsoft.com/en-us/education/interactive-demos/set-up-Microsoft-365" target="_blank"><u>this interactive demo</u></a>.
|
||||
### Explore the Microsoft 365 admin center
|
||||
|
||||
The **Microsoft 365 admin center** is the hub for all administrative consoles for the Microsoft 365 cloud. To access the <a href="https://entra.microsoft.com" target="_blank"><u>Microsoft Entra admin center</u></a>, sign in with the same global administrator account when you [created the Microsoft 365 tenant](#create-a-microsoft-365-tenant).
|
||||
|
||||
From the Microsoft 365 admin center, you can access different administrative dashboards: Microsoft Entra ID, Microsoft Intune, Intune for Education, and others:
|
||||
|
||||
:::image type="content" source="./images/m365-admin-center.png" alt-text="*All admin centers* page in *Microsoft 365 admin center*" lightbox="./images/m365-admin-center.png" border="true":::
|
||||
|
||||
For more information, see [Overview of the Microsoft 365 admin center][M365-2].
|
||||
|
||||
> [!NOTE]
|
||||
> Setting up your school's basic cloud infrastructure does not require you to complete the rest of the Microsoft 365 setup. For this reason, we will skip directly to adding students and teachers as users in the Microsoft 365 tenant.
|
||||
|
||||
## Add users, create groups, and assign licenses
|
||||
|
||||
With the Microsoft 365 tenant in place, it's time to add users, create groups, and assign licenses. All students and teachers need a user account before they can sign in and access the different Microsoft 365 services. There are multiple ways to do this, including using School Data Sync (SDS), synchronizing an on-premises Active Directory, manually, or a combination of the above.
|
||||
|
||||
> [!NOTE]
|
||||
> Synchronizing your Student Information System (SIS) with School Data Sync is the preferred way to create students and teachers as users in a Microsoft 365 Education tenant. However, if you want to integrate an on-premises directory and synchronize accounts to the cloud, skip to [Microsoft Entra Connect Sync](#microsoft-entra-connect-sync) below.
|
||||
|
||||
### School Data Sync
|
||||
|
||||
School Data Sync (SDS) imports and synchronizes SIS data to create classes in Microsoft 365, such as Microsoft 365 groups and class teams in Microsoft Teams. SDS can be used to create new, cloud-only, identities or to evolve existing identities. Users evolve into *students* or *teachers* and are associated with a *grade*, *school*, and other education-specific attributes.
|
||||
|
||||
For more information, see [Overview of School Data Sync][SDS-1].
|
||||
|
||||
> [!TIP]
|
||||
> To learn more and practice with School Data Sync, follow the <a href="https://interactiveguides-schooldatasync.azurewebsites.net/" target="_blank"><u>Microsoft School Data Sync demo</u></a>, which provides detailed steps to access, configure, and deploy School Data Sync in your Microsoft 365 Education tenant.
|
||||
|
||||
> [!NOTE]
|
||||
> You can perform a test deployment by cloning or downloading sample SDS CSV school data from the [<u>O365-EDU-Tools GitHub site</u>](https://github.com/OfficeDev/O365-EDU-Tools).
|
||||
>
|
||||
> Remember that you should typically deploy test SDS data (users, groups, and so on) in a separate test tenant, not your school production environment.
|
||||
|
||||
### Microsoft Entra Connect Sync
|
||||
|
||||
To integrate an on-premises directory with Microsoft Entra ID, you can use **Microsoft Entra Connect** to synchronize users, groups, and other objects. Microsoft Entra Connect lets you configure the authentication method appropriate for your school, including:
|
||||
|
||||
- [Password hash synchronization][AAD-1]
|
||||
- [Pass-through authentication][AAD-2]
|
||||
- [Federated authentication][AAD-3]
|
||||
|
||||
For more information, see [Set up directory synchronization for Microsoft 365][O365-1].
|
||||
|
||||
### Create users manually
|
||||
|
||||
In addition to the above methods, you can manually add users and groups, and assign licenses through the Microsoft 365 admin center.
|
||||
|
||||
There are two options for adding users manually, either individually or in bulk:
|
||||
|
||||
1. To add students and teachers as users in Microsoft 365 Education *individually*:
|
||||
- Sign in to the <a href="https://entra.microsoft.com" target="_blank"><b>Microsoft Entra admin center</b></a>
|
||||
- Select **Microsoft Entra ID** > **Users** > **All users** > **New user** > **Create new user**
|
||||
For more information, see [Add users and assign licenses at the same time][M365-3].
|
||||
1. To add *multiple* users to Microsoft 365 Education:
|
||||
- Sign in to the <a href="https://entra.microsoft.com" target="_blank"><b>Microsoft Entra admin center</b></a>
|
||||
- Select **Microsoft Entra ID** > **Users** > **All users** > **Bulk operations** > **Bulk create**
|
||||
|
||||
For more information, see [Add multiple users in the Microsoft 365 admin center][M365-4].
|
||||
|
||||
### Create groups
|
||||
|
||||
Creating groups is important to simplify multiple tasks, like assigning licenses, delegating administration, deploy settings, applications or to distribute assignments to students. To create groups:
|
||||
|
||||
1. Sign in to the <a href="https://entra.microsoft.com" target="_blank"><b>Microsoft Entra admin center</b></a>
|
||||
1. Select **Microsoft Entra ID** > **Groups** > **All groups** > **New group**
|
||||
1. On the **New group** page, select **Group type** > **Security**
|
||||
1. Provide a group name and add members, as needed
|
||||
1. Select **Next**
|
||||
|
||||
For more information, see [Create a group in the Microsoft 365 admin center][M365-5].
|
||||
|
||||
### Assign licenses
|
||||
|
||||
The recommended way to assign licenses is through group-based licensing. With this method, Microsoft Entra ID ensures that licenses are assigned to all members of the group. Any new members who join the group are assigned the appropriate licenses, and when members leave, their licenses are removed.
|
||||
|
||||
To assign a license to a group:
|
||||
|
||||
1. Sign in to the <a href="https://entra.microsoft.com" target="_blank"><b>Microsoft Entra admin center</b></a>
|
||||
1. Select **Microsoft Entra ID** > **Show More** > **Billing** > **Licenses**
|
||||
1. Select the required products that you want to assign licenses for > **Assign**
|
||||
1. Add the groups to which the licenses should be assigned
|
||||
|
||||
:::image type="content" source="images/entra-assign-licenses.png" alt-text="Assign licenses from Microsoft Entra admin center." lightbox="images/entra-assign-licenses.png":::
|
||||
|
||||
For more information, see [Group-based licensing using Microsoft Entra admin center][AAD-4].
|
||||
|
||||
## Configure school branding
|
||||
|
||||
Configuring your school branding enables a more familiar Autopilot experience to students and teachers. With a custom school branding, you can define a custom logo and a welcome message, which will appear during the Windows out-of-box experience.
|
||||
|
||||
To configure your school's branding:
|
||||
|
||||
1. Sign in to the <a href="https://entra.microsoft.com" target="_blank"><b>Microsoft Entra admin center</b></a>
|
||||
1. Select **Microsoft Entra ID** > **Show More** > **User experiences** > **Company branding**
|
||||
1. You can specify brand settings like background image, logo, username hint and a sign-in page text
|
||||
:::image type="content" source="images/entra-branding.png" alt-text="Configure Microsoft Entra ID branding from Microsoft Entra admin center." lightbox="images/entra-branding.png":::
|
||||
1. To adjust the school tenant's name displayed during OOBE, select **Microsoft Entra ID** > **Overview** > **Properties**
|
||||
1. In the **Name** field, enter the school district or organization's name > **Save**
|
||||
:::image type="content" alt-text="Configure Microsoft Entra tenant name from Microsoft Entra admin center." source="images/entra-tenant-name.png" lightbox="images/entra-tenant-name.png":::
|
||||
|
||||
For more information, see [Add branding to your directory][AAD-5].
|
||||
|
||||
## Enable bulk enrollment
|
||||
|
||||
If you decide to enroll Windows devices using provisioning packages instead of Windows Autopilot, you must ensure that the provisioning packages can join Windows devices to the Microsoft Entra tenant.
|
||||
|
||||
To allow provisioning packages to complete the Microsoft Entra join process:
|
||||
|
||||
1. Sign in to the <a href="https://entra.microsoft.com" target="_blank"><b>Microsoft Entra admin center</b></a>
|
||||
1. Select **Microsoft Entra ID** > **Devices** > **Device Settings**
|
||||
1. Under **Users may join devices to Microsoft Entra ID**, select **All**
|
||||
> [!NOTE]
|
||||
> If it is required that only specific users can join devices to Microsoft Entra ID, select **Selected**. Ensure that the user account that will create provisioning packages is included in the list of users.
|
||||
1. Select Save
|
||||
:::image type="content" source="images/entra-device-settings.png" alt-text="Configure device settings from Microsoft Entra admin center." lightbox="images/entra-device-settings.png":::
|
||||
|
||||
---
|
||||
|
||||
## Next steps
|
||||
|
||||
With users and groups created, and licensed for Microsoft 365 Education, you can now configure Microsoft Intune.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Next: Set up Microsoft Intune >](set-up-microsoft-intune.md)
|
||||
|
||||
<!-- Reference links in article -->
|
||||
|
||||
[AAD-1]: /azure/active-directory/hybrid/whatis-phs
|
||||
[AAD-2]: /azure/active-directory/hybrid/how-to-connect-pta
|
||||
[AAD-3]: /azure/active-directory/hybrid/how-to-connect-fed-whatis
|
||||
[AAD-4]: /azure/active-directory/enterprise-users/licensing-groups-assign
|
||||
[AAD-5]: /azure/active-directory/fundamentals/customize-branding
|
||||
|
||||
[M365-1]: /microsoft-365/education/deploy/create-your-office-365-tenant
|
||||
[M365-2]: /microsoft-365/admin/admin-overview/admin-center-overview
|
||||
[M365-3]: /microsoft-365/admin/add-users/add-users
|
||||
[M365-4]: /microsoft-365/enterprise/add-several-users-at-the-same-time
|
||||
[M365-5]: /microsoft-365/admin/create-groups/create-groups
|
||||
|
||||
[O365-1]: /office365/enterprise/set-up-directory-synchronization
|
||||
|
||||
[SDS-1]: /schooldatasync/overview-of-school-data-sync
|
||||
@ -1,97 +0,0 @@
|
||||
---
|
||||
title: Set up device management
|
||||
description: Learn how to configure the Intune service and set up the environment for education.
|
||||
ms.date: 01/16/2024
|
||||
ms.topic: tutorial
|
||||
appliesto:
|
||||
---
|
||||
|
||||
# Set up Microsoft Intune
|
||||
|
||||
Without the proper tools and resources, managing hundreds or thousands of devices in a school environment can be a complex and time-consuming task. Microsoft Intune is a collection of services that simplifies the management of devices at scale.
|
||||
|
||||
The Microsoft Intune service can be managed in different ways, and one of them is **Intune for Education**, a web portal designed for education environments.
|
||||
|
||||
:::image type="content" source="./images/intune-education-portal.png" alt-text="Intune for Education dashboard" lightbox="./images/intune-education-portal.png" border="true":::
|
||||
|
||||
**Intune for Education** supports the entire device lifecycle, from the enrollment phase through retirement. IT administrators can start managing classroom devices with bulk enrollment options and a streamlined deployment. At the end of the school year, IT admins can reset devices, ensuring they're ready for the next year.
|
||||
|
||||
For more information, see [Intune for Education documentation][INT-1].
|
||||
|
||||
> [!div class="checklist"]
|
||||
>In this section you will:
|
||||
>
|
||||
> - Review Intune's licensing prerequisites
|
||||
> - Configure the Intune service for education devices
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before configuring settings with Intune for Education, consider the following prerequisites:
|
||||
|
||||
- **Intune subscription.** Microsoft Intune is licensed in three ways:
|
||||
- As a standalone service
|
||||
- As part of [Enterprise Mobility + Security][MSFT-1]
|
||||
- As part of a [Microsoft 365 Education subscription][MSFT-2]
|
||||
- **Device platform.** Intune for Education can manage devices running a supported version of Windows 10, Windows 11, Windows 11 SE, iOS, and iPad OS
|
||||
|
||||
For more information, see [Intune licensing][MEM-1] and [this comparison sheet][MSFT-3], which includes a table detailing the *Microsoft Modern Work Plan for Education*.
|
||||
|
||||
## Configure the Intune service for education devices
|
||||
|
||||
The Intune service can be configured in different ways, depending on the needs of your school. In this section, you'll configure the Intune service using settings commonly implemented by K-12 school districts.
|
||||
|
||||
### Configure enrollment restrictions
|
||||
|
||||
With enrollment restrictions, you can prevent certain types of devices from being enrolled and therefore managed by Intune. For example, you can prevent the enrollment of devices that are not owned by the school.
|
||||
|
||||
To block personally owned Windows devices from enrolling:
|
||||
|
||||
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
1. Select **Devices** > **Enroll devices** > **Enrollment device platform restrictions**
|
||||
1. Select the **Windows restrictions** tab
|
||||
1. Select **Create restriction**
|
||||
1. On the **Basics** page, provide a name for the restriction and, optionally, a description > **Next**
|
||||
1. On the **Platform settings** page, in the **Personally owned devices** field, select **Block** > **Next**
|
||||
:::image type="content" source="./images/enrollment-restrictions.png" alt-text="This screenshot is of the device enrollment restriction page in Microsoft Intune admin center." lightbox="./images/enrollment-restrictions.png":::
|
||||
1. Optionally, on the **Scope tags** page, add scope tags > **Next**
|
||||
1. On the **Assignments** page, select **Add groups**, and then use the search box to find and choose groups to which you want to apply the restriction > **Next**
|
||||
1. On the **Review + create** page, select **Create** to save the restriction
|
||||
|
||||
For more information, see [Create a device platform restriction][MEM-2].
|
||||
|
||||
### Disable Windows Hello for Business
|
||||
|
||||
Windows Hello for Business is a biometric authentication feature that allows users to sign in to their devices using a PIN, password, or fingerprint. Windows Hello for Business is enabled by default on Windows devices, and to set it up, users must perform for multi-factor authentication (MFA). As a result, this feature may not be ideal for students, who may not have MFA enabled.
|
||||
It's suggested to disable Windows Hello for Business on Windows devices at the tenant level, and enabling it only for devices that need it, for example for teachers and staff devices.
|
||||
To disable Windows Hello for Business at the tenant level:
|
||||
|
||||
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
1. Select **Devices** > **Windows** > **Windows Enrollment**
|
||||
1. Select **Windows Hello for Business**
|
||||
1. Ensure that **Configure Windows Hello for Business** is set to **disabled**
|
||||
1. Select **Save**
|
||||
|
||||
:::image type="content" source="./images/whfb-disable.png" alt-text="Disablement of Windows Hello for Business from Microsoft Intune admin center." lightbox="./images/whfb-disable.png":::
|
||||
|
||||
For more information how to enable Windows Hello for Business on specific devices, see [Create a Windows Hello for Business policy][MEM-4].
|
||||
|
||||
---
|
||||
|
||||
## Next steps
|
||||
|
||||
With the Intune service configured, you can configure policies and applications in preparation to the deployment of students' and teachers' devices.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Next: Configure devices >](configure-devices-overview.md)
|
||||
|
||||
<!-- Reference links in article -->
|
||||
|
||||
[MEM-1]: /mem/intune/fundamentals/licenses
|
||||
[MEM-2]: /mem/intune/enrollment/enrollment-restrictions-set
|
||||
[MEM-4]: /mem/intune/protect/windows-hello#create-a-windows-hello-for-business-policy
|
||||
|
||||
[INT-1]: /intune-education/what-is-intune-for-education
|
||||
|
||||
[MSFT-1]: https://www.microsoft.com/microsoft-365/enterprise-mobility-security
|
||||
[MSFT-2]: https://www.microsoft.com/licensing/product-licensing/microsoft-365-education
|
||||
[MSFT-3]: https://edudownloads.azureedge.net/msdownloads/Microsoft-Modern-Work-Plan-Comparison-Education_11-2021.pdf
|
||||
@ -1,38 +0,0 @@
|
||||
items:
|
||||
- name: Introduction
|
||||
href: index.md
|
||||
- name: 1. Prepare your tenant
|
||||
items:
|
||||
- name: Set up Microsoft Entra ID
|
||||
href: set-up-microsoft-entra-id.md
|
||||
- name: Set up Microsoft Intune
|
||||
href: set-up-microsoft-intune.md
|
||||
- name: 2. Configure settings and applications
|
||||
items:
|
||||
- name: Overview
|
||||
href: configure-devices-overview.md
|
||||
- name: Configure policies
|
||||
href: configure-device-settings.md
|
||||
- name: Configure applications
|
||||
href: configure-device-apps.md
|
||||
- name: 3. Deploy devices
|
||||
items:
|
||||
- name: Overview
|
||||
href: enroll-overview.md
|
||||
- name: Enroll devices via Microsoft Entra join
|
||||
href: enroll-entra-join.md
|
||||
- name: Enroll devices with provisioning packages
|
||||
href: enroll-package.md
|
||||
- name: Enroll devices with Windows Autopilot
|
||||
href: enroll-autopilot.md
|
||||
- name: 4. Manage devices
|
||||
items:
|
||||
- name: Overview
|
||||
href: manage-overview.md
|
||||
- name: Management functionalities for Surface devices
|
||||
href: manage-surface-devices.md
|
||||
- name: Reset and wipe devices
|
||||
href: reset-wipe.md
|
||||
- name: 5. Troubleshoot and get help
|
||||
href: troubleshoot-overview.md
|
||||
|
||||
@ -1,56 +0,0 @@
|
||||
---
|
||||
title: Troubleshoot Windows devices
|
||||
description: Learn how to troubleshoot Windows devices from Intune and contact Microsoft Support for issues related to Intune and other services.
|
||||
ms.date: 11/09/2023
|
||||
ms.topic: tutorial
|
||||
---
|
||||
|
||||
# Troubleshoot Windows devices
|
||||
|
||||
Microsoft Intune provides many tools that can help you troubleshoot Windows devices.
|
||||
Here's a collection of resources to help you troubleshoot Windows devices managed by Intune:
|
||||
|
||||
- [Troubleshooting device enrollment in Intune][MEM-2]
|
||||
- [Troubleshooting Windows Autopilot][MEM-9]
|
||||
- [Troubleshoot Windows Wi-Fi profiles][MEM-6]
|
||||
- [Troubleshooting policies and profiles in Microsoft Intune][MEM-5]
|
||||
- [Troubleshooting BitLocker with the Intune encryption report][MEM-4]
|
||||
- [Troubleshooting CSP custom settings][MEM-8]
|
||||
- [Troubleshooting Win32 app installations with Intune][MEM-7]
|
||||
- [Troubleshooting device actions in Intune][MEM-3]
|
||||
- [**Collect diagnostics**][MEM-10] is a remote action that lets you collect and download Windows device logs without interrupting the user
|
||||
:::image type="content" source="./images/intune-diagnostics.png" alt-text="Intune for Education dashboard" lightbox="./images/intune-diagnostics.png" border="true":::
|
||||
|
||||
## How to contact Microsoft Support
|
||||
|
||||
Microsoft provides global technical, pre-sales, billing, and subscription support for cloud-based device management services. This support includes Microsoft Intune, Configuration Manager, Windows 365, and Microsoft Managed Desktop.
|
||||
|
||||
Follow these steps to obtain support in Microsoft Intune provides many tools that can help you troubleshoot Windows devices:
|
||||
|
||||
- Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431)
|
||||
- Select **Troubleshooting + support** > **Help and support**
|
||||
:::image type="content" source="images/advanced-support.png" alt-text="Screenshot that shows how to obtain support from Microsoft Intune." lightbox="images/advanced-support.png":::
|
||||
- Select the required support scenario: Configuration Manager, Intune, Co-management, or Windows 365
|
||||
- Above **How can we help?**, select one of three icons to open different panes: *Find solutions*, *Contact support*, or *Service requests*
|
||||
- In the **Find solutions** pane, use the text box to specify a few details about your issue. The console may offer suggestions based on what you've entered. Depending on the presence of specific keywords, the console provides help like:
|
||||
- Run diagnostics: start automated tests and investigations of your tenant from the console to reveal known issues. When you run a diagnostic, you may receive mitigation steps to help with resolution
|
||||
- View insights: find links to documentation that provides context and background specific to the product area or actions you've described
|
||||
- Recommended articles: browse suggested troubleshooting topics and other content related to your issue
|
||||
- If needed, use the *Contact support* pane to file an online support ticket
|
||||
> [!IMPORTANT]
|
||||
> When opening a case, be sure to include as many details as possible in the *Description* field. Such information includes: timestamp and date, device ID, device model, serial number, OS version, and any other details relevant to the issue.
|
||||
- To review your case history, select the **Service requests** pane. Active cases are at the top of the list, with closed issues also available for review
|
||||
|
||||
For more information, see [Microsoft Intune support page][MEM-1]
|
||||
|
||||
<!-- Reference links in article -->
|
||||
[MEM-1]: /mem/get-support
|
||||
[MEM-2]: /troubleshoot/mem/intune/troubleshoot-device-enrollment-in-intune
|
||||
[MEM-3]: /troubleshoot/mem/intune/troubleshoot-device-actions
|
||||
[MEM-4]: /troubleshoot/mem/intune/troubleshoot-bitlocker-admin-center
|
||||
[MEM-5]: /troubleshoot/mem/intune/troubleshoot-policies-in-microsoft-intune
|
||||
[MEM-6]: /troubleshoot/mem/intune/troubleshoot-wi-fi-profiles#troubleshoot-windows-wi-fi-profiles
|
||||
[MEM-7]: /troubleshoot/mem/intune/troubleshoot-win32-app-install
|
||||
[MEM-8]: /troubleshoot/mem/intune/troubleshoot-csp-custom-settings
|
||||
[MEM-9]: /mem/autopilot/troubleshooting
|
||||
[MEM-10]: /mem/intune/remote-actions/collect-diagnostics
|
||||
@ -2,7 +2,7 @@
|
||||
title: Windows 11 SE settings list
|
||||
description: Windows 11 SE automatically configures settings in the operating system. Learn more about the settings you can control and manage, and the settings you can't change.
|
||||
ms.topic: reference
|
||||
ms.date: 08/18/2023
|
||||
ms.date: 05/06/2024
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11 SE</a>
|
||||
ms.collection:
|
||||
|
||||
@ -1,21 +0,0 @@
|
||||
<!-- This file is generated automatically each week. Changes made to this file will be overwritten.-->
|
||||
|
||||
|
||||
|
||||
## Week of July 10, 2023
|
||||
|
||||
|
||||
| Published On |Topic title | Change |
|
||||
|------|------------|--------|
|
||||
| 7/14/2023 | [Microsoft Store for Business and Education release history](/microsoft-store/release-history-microsoft-store-business-education) | modified |
|
||||
| 7/14/2023 | [Whats new in Microsoft Store for Business and Education](/microsoft-store/whats-new-microsoft-store-business-education) | modified |
|
||||
| 7/14/2023 | [Prerequisites for Microsoft Store for Business and Education (Windows 10)](/microsoft-store/prerequisites-microsoft-store-for-business) | modified |
|
||||
|
||||
|
||||
## Week of June 26, 2023
|
||||
|
||||
|
||||
| Published On |Topic title | Change |
|
||||
|------|------------|--------|
|
||||
| 6/29/2023 | [Microsoft Store for Business and Education release history](/microsoft-store/release-history-microsoft-store-business-education) | modified |
|
||||
| 6/29/2023 | [Whats new in Microsoft Store for Business and Education](/microsoft-store/whats-new-microsoft-store-business-education) | modified |
|
||||
@ -1,68 +0,0 @@
|
||||
---
|
||||
title: What's new in App-V for Windows 10, version 1703 and earlier (Windows 10)
|
||||
description: Information about what's new in App-V for Windows 10, version 1703 and earlier.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/08/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# What's new in App-V for Windows 10, version 1703 and earlier
|
||||
|
||||
>Applies to: Windows 10, version 1703 and earlier
|
||||
|
||||
Microsoft Application Virtualization (App-V) for Windows 10 delivers Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service in real time and on an as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally.
|
||||
|
||||
## What's new in App-V Windows 10, version 1703
|
||||
|
||||
### Auto-sequence and update your App-V packages singly or as a batch
|
||||
|
||||
Previous versions of the App-V Sequencer required manual sequencing and updating of app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces the App-V Auto-Sequencer, which automatically sequences your app packages, improving your overall experience by streamlining prerequisite environment provisioning, automating app installation, and expediting package updating setup.
|
||||
|
||||
Using the automatic sequencer to package your apps gives you the following benefits:
|
||||
|
||||
* **Automatic virtual machine (VM) sequencing environment provisioning**. To learn more, see [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md).
|
||||
* **Package batch-sequencing**. This benefit denotes that multiple apps can be sequenced at the same time, in a single group. To learn more, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md).
|
||||
* **Package batch-updating**. This benefit denotes that multiple apps can be updated at the same time, in a single group. To learn more, see [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md).
|
||||
|
||||
### Updates to the App-V project template
|
||||
|
||||
Starting with Windows 10, version 1703, you can now save an App-V project template (.appvt) file as part of a sequenced App-V package. This file will automatically load every time you open the package for edits or updates. Your template can include general option settings, file exclusion list settings, and target operating system settings. To learn more, see [Create and apply an App-V project template to a sequenced App-V package](../app-v/appv-create-and-use-a-project-template.md).
|
||||
|
||||
### Automatically clean up unpublished App-V packages from the App-V client
|
||||
|
||||
Previous versions of App-V have required you to manually remove your unpublished packages from your client devices, to free up more storage space. Windows 10, version 1703 introduces the ability to use PowerShell or Group Policy settings to automatically clean up your unpublished packages after a device restart. To learn more, see [Automatically clean up unpublished packages on the App-V client](../app-v/appv-auto-clean-unpublished-packages.md).
|
||||
|
||||
## What's new in App-V in Windows 10, version 1607
|
||||
|
||||
### App-V is now a feature in Windows 10
|
||||
|
||||
With Windows 10, version 1607 and later releases, App-V is now included with [Windows 10 for Enterprise and Windows 10 for Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home) and is no longer part of the Microsoft Desktop Optimization Pack.
|
||||
|
||||
To learn more about earlier versions of App-V, see [MDOP Information Experience](/microsoft-desktop-optimization-pack/index).
|
||||
|
||||
The changes in App-V for Windows 10, version 1607 impact existing implementations of App-V in the following ways:
|
||||
|
||||
* The App-V client is installed on user devices automatically with Windows 10, version 1607, and no longer has to be deployed separately. Performing an in-place upgrade to Windows 10, version 1607, on user devices automatically installs the App-V client.
|
||||
* In previous releases of App-V, the application sequencer was included in the Microsoft Desktop Optimization Pack. Although you’ll need to use the new application sequencer to create new virtualized applications, existing virtualized applications will continue to work. The App-V application sequencer is available from the [Windows 10 Assessment and Deployment Kit (ADK)](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit).
|
||||
|
||||
> [!NOTE]
|
||||
>If you're already using App-V 5.x, you don't need to redeploy the App-V server components, as they haven't changed since App-V 5.0's release.
|
||||
|
||||
For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](../app-v/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md) and [Migrating to App-V for Windows 10 from a previous version](../app-v/appv-migrating-to-appv-from-a-previous-version.md).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You can only upgrade your existing App-V installation to Windows 10, version 1607 if it's version 5.0 SP2 or higher. If you're using an older version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you can upgrade to Windows 10, version 1607.
|
||||
|
||||
## Support for System Center
|
||||
|
||||
App-V supports System Center 2016 and Configuration Manager SP1. See [Planning for App-V Integration with Configuration Manager](/previous-versions/system-center/system-center-2012-R2/jj822982(v=technet.10)) to learn more about how to integrate your App-V environment with Configuration Manager.
|
||||
|
||||
## Related articles
|
||||
|
||||
* [Release Notes for App-V for Windows 10, version 1607](../app-v/appv-release-notes-for-appv-for-windows.md)
|
||||
* [Release Notes for App-V for Windows 10, version 1703](../app-v/appv-release-notes-for-appv-for-windows-1703.md)
|
||||
@ -1,37 +0,0 @@
|
||||
---
|
||||
title: How to Add or Remove an Administrator by Using the Management Console (Windows 10/11)
|
||||
description: Add or remove an administrator on the Microsoft Application Virtualization (App-V) server by using the Management Console.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/08/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# How to add or remove an administrator by using the Management Console
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedures to add or remove an administrator on the Microsoft Application Virtualization (App-V) server.
|
||||
|
||||
## Add an administrator using the Management Console
|
||||
|
||||
1. Open the Microsoft Application Virtualization (App-V) Management Console and select **Administrators** in the navigation pane. The navigation pane will display a list of Access Directory (AD) users and groups that currently have administrative access to the Microsoft Application Virtualization (App-V) server.
|
||||
2. To add a new administrator, select **Add Administrator**. Enter the name of the administrator that you want to add in the **Active Directory Name** field. Make sure to also provide the associated user account domain name. For example, **Domain** \\ **UserName**.
|
||||
3. Select the account you want to add and select **Add**. The new account should now appear in the list of server administrators.
|
||||
|
||||
## Remove an administrator using the Management Console
|
||||
|
||||
1. Open the Microsoft Application Virtualization (App-V) Management Console and select **Administrators** in the navigation pane. The navigation pane displays a list of AD users and groups that currently have administrative access to the Microsoft Application Virtualization (App-V) server.
|
||||
2. Right-click the account to be removed from the list of administrators and select **Remove**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
* [Operations for App-V](appv-operations.md)
|
||||
@ -1,47 +0,0 @@
|
||||
---
|
||||
title: How to Add or Upgrade Packages by Using the Management Console (Windows 10/11)
|
||||
description: Add or upgrade packages on the Microsoft Application Virtualization (App-V) server by using the Management Console.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/08/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# How to add or upgrade packages by using the Management Console
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can use the following procedure to add or upgrade a package to the App-V Management Console. To upgrade a package that already exists in the Management Console, use the following steps and import the upgraded package using the same package **Name**.
|
||||
|
||||
## Add a package to the Management Console
|
||||
|
||||
1. Select the **Packages** tab in the navigation pane of the Management Console display.
|
||||
|
||||
The console displays the list of packages that have been added to the server along with status information about each package. When a package is selected, detailed information about the package is displayed in the **PACKAGES** pane.
|
||||
|
||||
Select the **Ungrouped** drop-down list box and specify how the packages are to be displayed in the console. You can also click the associated column header to sort the packages.
|
||||
|
||||
2. Select **Add or Upgrade Packages** to specify which package you want to add.
|
||||
|
||||
3. Enter the full path to the package that you want to add. Use the UNC or HTTP path format, for example **\\\\servername\\sharename\\foldername\\packagename.appv** or **http<span></span>://server.1234/file.appv**, and then select **Add**.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You must select a package with the **.appv** file name extension.
|
||||
|
||||
4. The page displays the status message **Adding <Packagename>**. Select **IMPORT STATUS** to check the status of a package that you have imported.
|
||||
|
||||
Select **OK** to add the package and close the **Add Package** page. If there was an error during the import, select **Detail** on the **Package Import** page for more information. The newly added package is now available in the **PACKAGES** pane.
|
||||
|
||||
5. Select **Close** to close the **Add or Upgrade Packages** page.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
* [Operations for App-V](appv-operations.md)
|
||||
@ -1,56 +0,0 @@
|
||||
---
|
||||
title: Administering App-V by using Windows PowerShell (Windows 10/11)
|
||||
description: Administer App-V by using Windows PowerShell and learn where to find more information about PowerShell for App-V.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/08/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# Administering App-V by using Windows PowerShell
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Microsoft Application Virtualization (App-V) supports Windows PowerShell cmdlets that give administrators a quick and easy way to manage App-V. The following sections will tell you more about how to use Windows PowerShell with App-V.
|
||||
|
||||
## How to administer App-V with Windows PowerShell
|
||||
|
||||
The following table lists articles that will tell you more about how to use PowerShell for App-V.
|
||||
|
||||
|Name|Description|
|
||||
|---|---|
|
||||
|[How to load the Windows PowerShell cmdlets for App-V and get cmdlet help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md)|Describes how to install the Windows PowerShell cmdlets and find cmdlet help and examples.|
|
||||
|[How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md)|Describes how to manage the client package lifecycle on a stand-alone computer with Windows PowerShell.|
|
||||
|[How to manage connection groups on a stand-alone computer by using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)|Describes how to manage connection groups with Windows PowerShell.|
|
||||
|[How to modify client configuration by using Windows PowerShell](appv-modify-client-configuration-with-powershell.md)|Describes how to modify the client with Windows PowerShell.|
|
||||
|[How to apply the user configuration file by using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)|Describes how to apply a user configuration file with Windows PowerShell.|
|
||||
|[How to apply the deployment configuration file by using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)|Describes how to apply a deployment configuration file with Windows PowerShell.|
|
||||
|[How to sequence a package by using Windows PowerShell](appv-sequence-a-package-with-powershell.md)|Describes how to create a new package with Windows PowerShell.|
|
||||
|[How to create a package accelerator by using Windows PowerShell](appv-create-a-package-accelerator-with-powershell.md)|Describes how to create a package accelerator with Windows PowerShell. You can use package accelerators to automatically sequence large, complex applications.|
|
||||
|[How to enable reporting on the App-V client by using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)|Describes how to enable the computer running the App-V Client to send reporting information.|
|
||||
|[How to install the App-V databases and convert the associated security identifiers by using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md)|Describes how to take an array of account names and to convert each of them to the corresponding SID in standard and hexadecimal formats.|
|
||||
|[How to configure the client to receive package and connection groups updates from the publishing server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)|Describes how to use Windows PowerShell to configure a client after you have deployed the App-V management and publishing servers and added the required packages and connection groups.|
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Make sure that any script you execute with your App-V packages matches the execution policy that you have configured for Windows PowerShell.
|
||||
|
||||
## Windows PowerShell error handling
|
||||
|
||||
The following table describes Windows PowerShell error handling for App-V.
|
||||
|
||||
|Event|Action|
|
||||
|---|---|
|
||||
|Using the **RollbackOnError** attribute with embedded scripts|When you use the **RollbackOnError** attribute with embedded scripts, the attribute is ignored for the following events:<br>- Removing a package<br>- Unpublishing a package<br>- Terminating a virtual environment<br>- Terminating a process|
|
||||
|Package name contains **$**|If a package name contains the character \$\, you must use a single-quote ( **'** ). <br>For example:<br>```Add-AppvClientPackage 'Contoso$App.appv'```|
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
* [Operations for App-V](appv-operations.md)
|
||||
@ -1,63 +0,0 @@
|
||||
---
|
||||
title: Administering App-V Virtual Applications by using the Management Console (Windows 10/11)
|
||||
description: Administering App-V Virtual Applications by using the Management Console
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/08/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# Administering App-V Virtual Applications by using the Management Console
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the Microsoft Application Virtualization (App-V) management server to manage packages, connection groups, and package access in your environment. The server publishes application icons, shortcuts, and file type associations to authorized computers running the App-V client. One or more management servers typically share a common data store for configuration and package information.
|
||||
|
||||
The management server uses Active Directory Domain Services (AD DS) groups to manage user authorization and has SQL Server installed to manage the database and data store.
|
||||
|
||||
Because the management servers stream applications to end users on demand, these servers are ideally suited for system configurations that have reliable, high-bandwidth LANs. The management server consists of the following components:
|
||||
|
||||
- The **management server** manages packages and connection groups.
|
||||
- The **publishing server** deploys packages to computers running the App-V Client.
|
||||
- The **management database** manages the package access publishes the server’s synchronization with the management server.
|
||||
|
||||
## Management Console tasks
|
||||
|
||||
Here are some articles that can show you how to perform the most common tasks that the App-V Management Console is used for:
|
||||
|
||||
- [How to connect to the Management Console](appv-connect-to-the-management-console.md)
|
||||
- [How to add or upgrade packages by using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md)
|
||||
- [How to configure access to packages by using the Management Console](appv-configure-access-to-packages-with-the-management-console.md)
|
||||
- [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md)
|
||||
- [How to delete a package in the Management Console](appv-delete-a-package-with-the-management-console.md)
|
||||
- [How to add or remove an administrator by using the Management Console](appv-add-or-remove-an-administrator-with-the-management-console.md)
|
||||
- [How to register and unregister a publishing server by using the Management Console](appv-register-and-unregister-a-publishing-server-with-the-management-console.md)
|
||||
- [How to create a custom configuration file by using the App-V Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md)
|
||||
- [How to transfer access and configurations to another version of a package by using the Management Console](appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md)
|
||||
- [How to customize virtual application extensions for a specific AD group by using the Management Console](appv-customize-virtual-application-extensions-with-the-management-console.md)
|
||||
- [How to view and configure applications and default virtual application extensions by using the Management Console](appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md)
|
||||
|
||||
The main elements of the App-V Management Console are:
|
||||
|
||||
|Management Console tab|Description|
|
||||
|---|---|
|
||||
|Packages tab|Use the **Packages** tab to add or upgrade packages.|
|
||||
|Connection Groups tab|Use the **Connection Groups** tab to manage connection groups.|
|
||||
|Servers tab|Use the **Servers** tab to register a new server.|
|
||||
|Administrators tab|Use the **Administrators** tab to register, add, or remove administrators in your App-V environment.|
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The browser you're using to open the Web Management Console must have JavaScript enabled.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Other resources for this App-V deployment
|
||||
|
||||
- [Application Virtualization (App-V) overview](appv-for-windows.md)
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
@ -1,36 +0,0 @@
|
||||
---
|
||||
title: Only Allow Admins to Enable Connection Groups (Windows 10/11)
|
||||
description: Configure the App-V client so that only administrators, not users, can enable or disable connection groups.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/08/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# How to allow only administrators to enable connection groups
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can configure the App-V client so that only administrators, not users, can enable or disable connection groups. In earlier versions of App-V, there was no way to restrict access to disabling connection groups to users.
|
||||
|
||||
>[!NOTE]
|
||||
>This feature is supported starting in App-V 5.0 SP3.
|
||||
|
||||
Use one of the following methods to allow only administrators to enable or disable connection groups.
|
||||
|
||||
|Method|Steps|
|
||||
|---|---|
|
||||
|Group Policy setting|Enable the “Require publish as administrator” Group Policy setting, which is located in the following Group Policy Object node:<br><br>**Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Publishing**|
|
||||
|Windows PowerShell cmdlet|Run the **Set-AppvClientConfiguration** cmdlet with the *-RequirePublishAsAdmin* parameter. <br><br>Parameter values:<br>- **0** – False<br>- **1** – True<br><br>Example: ```Set-AppvClientConfiguration -RequirePublishAsAdmin 1```|
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
@ -1,899 +0,0 @@
|
||||
---
|
||||
title: Application Publishing and Client Interaction (Windows 10/11)
|
||||
description: Learn technical information about common App-V Client operations and their integration with the local operating system.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/08/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# Application publishing and client interaction
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
This article provides technical information about common App-V Client operations and their integration with the local operating system.
|
||||
|
||||
## App-V package files created by the Sequencer
|
||||
|
||||
The Sequencer creates App-V packages and produces a virtualized application. The sequencing process creates the following files:
|
||||
|
||||
|File|Description|
|
||||
|---|---|
|
||||
|.appv|- The primary package file, which contains captured assets and state information from the sequencing process.<br>- Architecture of the package file, publishing information, and registry in a tokenized form that can be reapplied to a machine and to a specific user upon delivery.|
|
||||
|.MSI|Executable deployment wrapper that you can use to deploy .appv files manually or by using a third-party deployment platform.|
|
||||
|_DeploymentConfig.XML|File used to customize the default publishing parameters for all applications in a package that is deployed globally to all users on a computer that is running the App-V Client.|
|
||||
|_UserConfig.XML|File used to customize the publishing parameters for all applications in a package that is a deployed to a specific user on a computer that is running the App-V Client.|
|
||||
|Report.xml|Summary of messages resulting from the sequencing process, including omitted drivers, files, and registry locations.|
|
||||
|.CAB|Optional: Package accelerator file used to automatically rebuild a previously sequenced virtual application package.|
|
||||
|.appvt|Optional: Sequencer template file used to retain commonly reused Sequencer settings.|
|
||||
|
||||
To learn more about sequencing, see [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).
|
||||
|
||||
## What’s in the appv file?
|
||||
|
||||
The appv file is a container that stores XML and non-XML files together in a single entity. This file is built from the AppX format, which is based on the Open Packaging Conventions (OPC) standard.
|
||||
|
||||
To view the appv file contents, make a copy of the package, and then rename the copied file to a .zip extension.
|
||||
|
||||
The appv file contains the following folder and files, which are used when creating and publishing a virtual application:
|
||||
|
||||
| Name | Type | Description |
|
||||
|---|---|---|
|
||||
| Root | File folder | Directory that contains the file system for the virtualized application captured during sequencing. |
|
||||
| [Content_Types].xml | XML File | List of the core content types in the appv file (for example, DLL, EXE, BIN). |
|
||||
| AppxBlockMap.xml | XML File | Layout of the appv file, which uses File, Block, and BlockMap elements that enable location and validation of files in the App-V package.|
|
||||
| AppxManifest.xml | XML File | Metadata for the package that contains the required information for adding, publishing, and launching the package. Includes extension points (file type associations and shortcuts) and the names and GUIDs associated with the package.|
|
||||
| FilesystemMetadata.xml | XML File | List of the files captured during sequencing, including attributes (such as directories, files, opaque directories, empty directories, and long and short names). |
|
||||
| PackageHistory.xml | XML File | Information about the sequencing computer (operating system version, Internet Explorer version, .Net Framework version) and process (upgrade, package version).|
|
||||
| Registry.dat | DAT File | Registry keys and values captured during the sequencing process for the package.|
|
||||
| StreamMap.xml | XML File | List of files for the primary and publishing feature block. The publishing feature block contains the ICO files and required portions of files (EXE and DLL) for publishing the package. When present, the primary feature block includes files that have been optimized for streaming during the sequencing process.|
|
||||
|
||||
## App-V Client data storage locations
|
||||
|
||||
The App-V Client performs tasks to keep virtual applications running properly and working like locally installed applications. The process of opening and running virtual applications requires mapping from the virtual file system and registry to ensure the application has the required components of a traditional application expected by users. This section describes the assets that are required to run virtual applications and lists the location where App-V stores the assets.
|
||||
|
||||
| Name | Location | Description |
|
||||
|---|---|---|
|
||||
| Package Store | %ProgramData%\App-V| Default location for read-only package files.|
|
||||
| Machine Catalog | %ProgramData%\Microsoft\AppV\Client\Catalog| Contains per-machine configuration documents.|
|
||||
| User Catalog | %AppData%\Microsoft\AppV\Client\Catalog| Contains per-user configuration documents.|
|
||||
| Shortcut Backups | %AppData%\Microsoft\AppV\Client\Integration\ShortCutBackups| Stores previous integration points that enable restore on package unpublish.|
|
||||
| Copy on Write (COW) Roaming | %AppData%\Microsoft\AppV\Client\VFS| Writeable roaming location for package modification.|
|
||||
| Copy on Write (COW) Local | %LocalAppData%\Microsoft\AppV\Client\VFS| Writeable non-roaming location for package modification.|
|
||||
| Machine Registry | HKLM\Software\Microsoft\AppV| Contains package state information, including VReg for machine or globally published packages (Machine hive).|
|
||||
| User Registry | HKCU\Software\Microsoft\AppV| Contains user package state information including VReg.|
|
||||
| User Registry Classes | HKCU\Software\Classes\AppV| Contains more user package state information.|
|
||||
|
||||
More details for the table are provided in the section below and throughout the document.
|
||||
|
||||
### Package store
|
||||
|
||||
The App-V Client manages the applications assets mounted in the package store. This default storage location is %ProgramData%\App-V, but you can configure it during or after setup by using the **Set-AppVClientConfiguration** Windows PowerShell cmdlet, which modifies the local registry (**PackageInstallationRoot** value under the HKLM\Software\Microsoft\AppV\Client\Streaming key). The package store must be located at a local path on the client operating system. The individual packages are stored in the package store in subdirectories named after the Package GUID and Version GUID.
|
||||
|
||||
The following is an example of a path to a specific application:
|
||||
|
||||
```syntax
|
||||
C:\ProgramData\App-V\PackGUID\VersionGUID
|
||||
```
|
||||
|
||||
To change the default location of the package store during setup, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
|
||||
|
||||
### Shared Content Store
|
||||
|
||||
If the App-V Client is configured in Shared Content Store mode, no data is written to disk when a stream fault occurs, which means that the packages require minimal local disk space (publishing data). In VDI environments where local storage can be limited, it's important to use as little disk space as possible. You can minimize disk space usage by streaming applications from a high-performance network location (such as a SAN). For more information, see [Shared Content Store in Microsoft App-V 5.0 - Behind the Scenes](/archive/blogs/appv/shared-content-store-in-microsoft-app-v-5-0-behind-the-scenes).
|
||||
|
||||
>[!NOTE]
|
||||
>The machine and package store must be located on a local drive, even when you’re using Shared Content Store configurations for the App-V Client.
|
||||
|
||||
### Package catalogs
|
||||
|
||||
The App-V Client manages the following file-based locations:
|
||||
|
||||
- **Catalogs (user and machine).**
|
||||
- **Registry locations**—depends on how the package is targeted for publishing. There's a Catalog (data store) for the computer, and a catalog for each individual user. The Machine catalog stores global information applicable to all users or any specific user, and the User catalog stores information applicable to a specific user. The catalog is a collection of Dynamic Configurations and manifest files; there's discrete data for both file and registry per package version.
|
||||
|
||||
### Machine catalog
|
||||
|
||||
The locations described in this table can be found in the %programdata%\Microsoft\AppV\Client\Catalog\ folder.
|
||||
|
||||
| | Location |
|
||||
|:---|:---|
|
||||
|**Description**|Stores package documents that are available to users on the machine when packages are added and published. However, if a package is “global” at publishing time, the integrations are available to all users.<br></br>If a package is non-global, the integrations are published only for specific users, but there are still global resources that are modified and visible to anyone on the client computer (such as when the package directory is in a shared disk location).<br></br>If a package is available to a user on the computer (global or non-global), the manifest is stored in the Machine Catalog. When a package is published globally, there's a Dynamic Configuration file, stored in the Machine Catalog; therefore, the determination of whether a package is global is defined according to whether there's a policy file (UserDeploymentConfiguration file) in the Machine Catalog.|
|
||||
|**Default storage location**|%programdata%\Microsoft\AppV\Client\Catalog\<br></br>This location isn't the same as the Package Store location. The Package Store is the golden or pristine copy of the package files.|
|
||||
|**Files in the machine catalog**|- Manifest.xml<br>- DeploymentConfiguration.xml<br>- UserManifest.xml (Globally Published Package)<br>- UserDeploymentConfiguration.xml (Globally Published Package)|
|
||||
|**Additional machine catalog location, used when the package is part of a connection group**|The following location is in addition to the specific package location mentioned previously as the default storage location:<br></br>%programdata%\Microsoft\AppV\Client\Catalog\PackageGroups\ConGroupGUID\ConGroupVerGUID|
|
||||
|**Additional files in the machine catalog when the package is part of a connection group**|- PackageGroupDescriptor.xml<br>- UserPackageGroupDescriptor.xml (globally published Connection Group)|
|
||||
|
||||
### User catalog
|
||||
|
||||
The locations described in this table can be found in the appdata\roaming\Microsoft\AppV\Client\Catalog\ folder.
|
||||
|
||||
|| Location |
|
||||
|:---|:---|
|
||||
|**Description**|Created during the publishing process. Contains information used for publishing the package, and for making sure that a package is provisioned to a specific user at launch. Created in a roaming location and includes user-specific publishing information.<br></br>When a package is published for a user, the policy file is stored in the User Catalog. At the same time, a copy of the manifest is also stored in the User Catalog. When a package entitlement is removed for a user, the relevant package files are removed from the User Catalog. Looking at the user catalog, an administrator can view the presence of a Dynamic Configuration file, which indicates that the package is entitled for that user.<br></br>For roaming users, the User Catalog needs to be in a roaming or shared location to preserve the legacy App-V behavior of targeting users by default. Entitlement and policy are tied to a user, not a computer, so they should roam with the user once they're provisioned.|
|
||||
|**Default storage location**|appdata\roaming\Microsoft\AppV\Client\Catalog\Packages\PkgGUID\VerGUID|
|
||||
|**Files in the user catalog**|- UserManifest.xml<br>- DynamicConfiguration.xml or UserDeploymentConfiguration.xml|
|
||||
|**Additional user catalog location, used when the package is part of a connection group**|The following location is in addition to the specific package location mentioned above:<br></br>appdata\roaming\Microsoft\AppV\Client\Catalog\PackageGroups\PkgGroupGUID\PkgGroupVerGUID|
|
||||
|**Additional file in the machine catalog when the package is part of a connection group**|UserPackageGroupDescriptor.xml|
|
||||
|
||||
### Shortcut backups
|
||||
|
||||
During the publishing process, the App-V Client backs up any shortcuts and integration points to %AppData%\Microsoft\AppV\Client\Integration\ShortCutBackups. This backup lets integration points restore to the previous versions when the package is unpublished.
|
||||
|
||||
### Copy on Write files
|
||||
|
||||
The Package Store contains a pristine copy of the package files that have been streamed from the publishing server. During normal operation of an App-V application, the user or service may require changes to the files. However, these changes aren't made in the package store to preserve your ability to repair the application, which removes these changes. These locations, called Copy on Write (COW), support both roaming and non-roaming locations. The location where the modifications are stored depends where the application has been programmed to write changes to in a native experience.
|
||||
|
||||
### COW roaming
|
||||
|
||||
The COW Roaming location described above stores changes to files and directories that are targeted to the typical %AppData% location or \\Users\\*<username>*\\AppData\\Roaming location. These directories and files are then roamed based on the operating system settings.
|
||||
|
||||
### COW local
|
||||
|
||||
The COW Local location is similar to the roaming location, but the directories and files aren't roamed to other computers, even if roaming support has been configured. The COW Local location described above stores changes applicable to typical windows and not the %AppData% location. The directories listed will vary but there will be two locations for any typical Windows locations (for example, Common AppData and Common AppDataS). The **S** signifies the restricted location when the virtual service requests the change as a different elevated user from the signed-in users. The non-**S** location stores user-based changes.
|
||||
|
||||
## Package registry
|
||||
|
||||
Before an application can access the package registry data, the App-V Client must make the package registry data available to the applications. The App-V Client uses the real registry as a backing store for all registry data.
|
||||
|
||||
When a new package is added to the App-V Client, a copy of the REGISTRY.DAT file from the package is created at %ProgramData%\Microsoft\AppV\Client\VREG\{Version GUID}.dat. The name of the file is the version GUID with the .DAT extension. The reason this copy is made is to ensure that the actual hive file in the package is never in use, which would prevent the removal of the package at a later time.
|
||||
|
||||
**Registry.dat from Package Store** > **%ProgramData%\Microsoft\AppV\Client\Vreg\\{VersionGUID}.dat**
|
||||
|
||||
When the first application from the package is launched on the client, the client stages or copies the contents out of the hive file, re-creating the package registry data in an alternate location under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Packages\PackageGuid\Versions\VersionGUID\REGISTRY. The staged registry data has two distinct types of machine data and user data. Machine data is shared across all users on the machine. User data is staged for each user to a user-specific location HKCU\Software\Microsoft\AppV\Client\Packages\PackageGUID\Registry\User. The machine data is ultimately removed at package removal time, and the user data is removed on a user unpublish operation.
|
||||
|
||||
### Package registry staging vs. connection group registry staging
|
||||
|
||||
When connection groups are present, the previous process of staging the registry holds true, but instead of having one hive file to process, there are more than one. The files are processed in the order in which they appear in the connection group XML, with the first writer winning any conflicts.
|
||||
|
||||
The staged registry persists the same way as in the single package case. Staged user registry data remains for the connection group until it's disabled; staged machine registry data is removed on connection group removal.
|
||||
|
||||
### Virtual registry
|
||||
|
||||
The purpose of the virtual registry (VREG) is to provide a single merged view of the package registry and the native registry to applications. It also provides copy-on-write (COW) functionality—that is, any changes made to the registry from the context of a virtual process are made to a separate COW location. This functionality means that the VREG must combine up to three separate registry locations into a single view based on the populated locations in the **registry COW** > **package** > **native**. When a request is made for a registry data it will locate in order until it finds the data it was requesting. Meaning if there's a value stored in a COW location it will not proceed to other locations, however, if there's no data in the COW location it will proceed to the Package and then Native location until it finds the appropriate data.
|
||||
|
||||
### Registry locations
|
||||
|
||||
There are two package registry locations and two connection group locations where the App-V Client stores registry information, depending on whether the Package is published individually or as part of a connection group. There are three COW locations for packages and three for connection groups, which are created and managed by the VREG. Settings for packages and connection groups aren't shared:
|
||||
|
||||
#### Single Package VReg
|
||||
|
||||
The registries in the following table are located in the Registry\Client\Packages\PkgGUID\ folder.
|
||||
|
||||
|Location|Description|
|
||||
|---|---|
|
||||
|COW|- Machine Registry\Client\Packages\PkgGUID\REGISTRY (Only elevate process can write)<br>- User Registry\Client\Packages\PkgGUID\REGISTRY (User Roaming anything written under HKCU except Software\Classes<br>- User Registry Classes\Client\Packages\PkgGUID\REGISTRY (HKCU\Software\Classes writes and HKLM for non-elevated process)|
|
||||
|Package|- Machine Registry\Client\Packages\PkgGUID\Versions\VerGuid\Registry\Machine<br>- User Registry Classes\Client\Packages\PkgGUID\Versions\VerGUID\Registry|
|
||||
|Native|- Native application registry location|
|
||||
|
||||
#### Connection Group VReg
|
||||
|
||||
The registries in the following table are located in the Machine Registry\Client\PackageGroups\GrpGUID\ and User Registry Classes\Client\PackageGroups\GrpGUID\ folders.
|
||||
|
||||
|Location|Description|
|
||||
|---|---|
|
||||
|COW|- Machine Registry\Client\PackageGroups\GrpGUID\REGISTRY (only elevate process can write)<br>- User Registry\Client\PackageGroups\GrpGUID\REGISTRY (Anything written to HKCU except Software\Classes)<br>- User Registry Classes\Client\PackageGroups\GrpGUID\REGISTRY|
|
||||
|Package|- Machine Registry\Client\PackageGroups\GrpGUID\Versions\VerGUID\REGISTRY<br>- User Registry Classes\Client\PackageGroups\GrpGUID\Versions\VerGUID\REGISTRY|
|
||||
|Native|- Native application registry location|
|
||||
|
||||
There are two COW locations for HKLM: elevated and non-elevated processes. Elevated processes always write HKLM changes to the secure COW under HKLM. Non-elevated processes always write HKLM changes to the non-secure COW under HKCU\\Software\\Classes. When an application reads changes from HKLM, elevated processes will read changes from the secure COW under HKLM. Non-elevated reads from both, favoring the changes made in the unsecure COW first.
|
||||
|
||||
### Pass-through keys
|
||||
|
||||
An administrator can use pass-through keys to configure certain keys to only be read from the native registry, bypassing the Package and COW locations. Pass-through locations are global to the machine (not package-specific) and can be configured by adding the path to the key, which should be treated as pass-through to the **REG\_MULTI\_SZ** value called **PassThroughPaths** of the key HKLM\Software\Microsoft\AppV\Subsystem\VirtualRegistry. Any key that appears under this multi-string value (and their children) will be treated as pass-through.
|
||||
|
||||
The following locations are configured as pass-through locations by default:
|
||||
|
||||
- HKEY\_CURRENT\_USER\\SOFTWARE\\Classes\\Local Settings\\Software\\Microsoft\\Windows\\CurrentVersion\\AppModel
|
||||
|
||||
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Classes\\Local Settings\\Software\\Microsoft\\Windows\\CurrentVersion\\AppModel
|
||||
|
||||
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\WINEVT
|
||||
|
||||
- HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\services\\eventlog\\Application
|
||||
|
||||
- HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\WMI\\Autologger
|
||||
|
||||
- HKEY\_CURRENT\_USER\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Internet Settings
|
||||
|
||||
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Perflib
|
||||
|
||||
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Policies
|
||||
|
||||
- HKEY\_CURRENT\_USER\\SOFTWARE\\Policies
|
||||
|
||||
The purpose of pass-through keys is to ensure that a virtual application doesn't write registry data in the VReg that is required for non-virtual applications for successful operation or integration. The Policies key ensures that Group Policy-based settings set by the administrator are utilized and not per package settings. The AppModel key is required for integration with Windows Modern UI-based applications. Administers ideally shouldn't modify any of the default pass-through keys, but in some instances, the admin may need to add more pass-through keys to adjust application behavior.
|
||||
|
||||
## App-V package store behavior
|
||||
|
||||
App-V manages the Package Store, which is the location where the expanded asset files from the appv file are stored. By default, this location is stored at %ProgramData%\\App-V, and is limited in terms of storage capabilities only by free disk space. The package store is organized by the GUIDs for the package and version as mentioned in the previous section.
|
||||
|
||||
### Add packages
|
||||
|
||||
App-V Packages are staged upon addition to the computer with the App-V Client. The App-V Client provides on-demand staging. When publishing or manually entering the **Add-AppVClientPackage** cmdlet, the data structure is built in the package store (C:\\programdata\\App-V\\{PkgGUID}\\{VerGUID}). The package files identified in the publishing block defined in the StreamMap.xml file are added to the system, and the top level folders and child files are staged to ensure proper application assets exist at launch.
|
||||
|
||||
### Mounting packages
|
||||
|
||||
Packages can be explicitly loaded by entering the **Mount-AppVClientPackage** PowerShell cmdlet or by using the **App-V Client UI** to download a package. This operation completely loads the entire package into the package store.
|
||||
|
||||
### Streaming packages
|
||||
|
||||
The App-V Client can be configured to change the default behavior of streaming. All streaming policies are stored under the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\Streaming. Policies are set by entering the **Set-AppvClientConfiguration** PowerShell cmdlet. The following policies apply to streaming:
|
||||
|
||||
|Policy|Description|
|
||||
|---|---|
|
||||
|AllowHighCostLaunch|Allows streaming over 3G and cellular networks|
|
||||
|AutoLoad|Specifies the Background Load setting:<br>0 – Disabled<br>1 – Previously Used Packages only<br>2 – All Packages|
|
||||
|PackageInstallationRoot|The root folder for the package store in the local machine|
|
||||
|PackageSourceRoot|The root override where packages should be streamed from|
|
||||
|SharedContentStoreMode|Enables the use of Shared Content Store for VDI scenarios|
|
||||
|
||||
These settings affect the behavior of streaming App-V package assets to the client. By default, App-V only downloads the assets required after downloading the initial publishing and primary feature blocks. There are three specific behaviors in streaming packages that are important to understand:
|
||||
|
||||
- Background Streaming
|
||||
- Optimized Streaming
|
||||
- Stream Faults
|
||||
|
||||
### Background streaming
|
||||
|
||||
The Windows PowerShell cmdlet **Get-AppvClientConfiguration** can be used to determine the current mode for background streaming with the AutoLoad setting and modified with either the **Set-AppvClientConfiguration** cmdlet or from the registry (HKLM\\SOFTWARE\\Microsoft\\AppV\\ClientStreaming key). Background streaming is a default setting where the Autoload setting is set to download previously used packages. The behavior based on default setting (value=1) downloads App-V data blocks in the background after the application has been launched. This setting can either be disabled altogether (value=0) or enabled for all packages (value=2), regardless of whether they've been launched.
|
||||
|
||||
### Optimized streaming
|
||||
|
||||
App-V packages can be configured with a primary feature block during sequencing. This setting allows the sequencing engineer to monitor launch files for a specific application, or applications, and mark the blocks of data in the App-V package for streaming at first launch of any application in the package.
|
||||
|
||||
### Stream faults
|
||||
|
||||
After the initial stream of any publishing data and the primary feature block, requests for more files perform stream faults. These blocks of data are downloaded to the package store on an as-needed basis. This flexibility allows a user to download only a small part of the package, typically enough to launch the package and run normal tasks. All other blocks are downloaded when a user initiates an operation that requires data not currently in the package store.
|
||||
|
||||
### Package upgrades
|
||||
|
||||
App-V Packages require updating throughout the lifecycle of the application. App-V Package upgrades are like the package publish operation, as each version will be created in its own PackageRoot location: %ProgramData%\App-V\{PkgGUID}\{newVerGUID}. The upgrade operation is optimized by creating hard links to identical and streamed files from other versions of the same package.
|
||||
|
||||
### Package removal
|
||||
|
||||
The App-V Client's behavior when packages are removed depends on the package removal method. Using an App-V full infrastructure to unpublish the application, the user catalog files (machine catalog for globally published applications) are removed, but the package store location and COW locations remain. When the **Remove-AppVClientPackge** Windows PowerShell cmdlet is used to remove an App-V Package, the package store location is cleaned. Remember that unpublishing an App-V Package from the Management Server doesn't perform a Remove operation. Neither operation will remove the Package Store package files.
|
||||
|
||||
## Roaming registry and data
|
||||
|
||||
App-V is able to provide a near-native experience when roaming, depending on how the application being used is written. By default, App-V roams AppData that is stored in the roaming location, based on the roaming configuration of the operating system. Other locations for storage of file-based data don't roam from computer to computer, since they're in locations that aren't roamed.
|
||||
|
||||
### Roaming requirements and user catalog data storage
|
||||
|
||||
App-V stores data, which represents the state of the user’s catalog, in the form of:
|
||||
|
||||
- Files under %appdata%\\Microsoft\\AppV\\Client\\Catalog
|
||||
- Registry settings under HKEY_CURRENT_USER\Software\Microsoft\AppV\Client\Packages
|
||||
|
||||
Together, these files and registry settings represent the user’s catalog, so either both must be roamed, or neither must be roamed for a given user. App-V doesn't support roaming %AppData%, but not roaming the user’s profile (registry), or vice versa.
|
||||
|
||||
>[!NOTE]
|
||||
>The **Repair-AppvClientPackage** cmdlet doesn't repair the publishing state of packages where the user’s App-V state under HKEY_CURRENT_USER is missing or mismatched with the data in %appdata%.
|
||||
|
||||
### Registry-based data
|
||||
|
||||
App-V registry roaming falls into two scenarios, as shown in the following table.
|
||||
|
||||
|Scenario|Description|
|
||||
|---|---|
|
||||
|Applications that are run as standard users|When a standard user launches an App-V application, both HKLM and HKCU for App-V applications are stored in the HKCU hive on the machine. This scenario presents two distinct paths:<br><br>- HKLM's location is HKCU\SOFTWARE\Classes\AppV\Client\Packages\\{PkgGUID}\REGISTRY\MACHINE\SOFTWARE<br>- HKCU's location is HKCU\SOFTWARE\Microsoft\AppV\Client\Packages\\{PkgGUID}\REGISTRY\USER\\{UserSID}\SOFTWARE<br><br>The locations are enabled for roaming based on the operating system settings.|
|
||||
|Applications that are run with elevation|When an application is launched with elevation:<br><br>- HKLM data is stored in the HKLM hive on the local computer<br>- HKCU data is stored in the User Registry location<br><br>In this scenario, these settings aren't roamed with normal operating system roaming configurations, and the resulting registry keys and values are stored in the following locations:<br><br>- HKLM's location is HKLM\SOFTWARE\Microsoft\AppV\Client\Packages\\{PkgGUID}\\{UserSID}\REGISTRY\MACHINE\SOFTWARE<br>- HKCU's location is HKCU\SOFTWARE\Microsoft\AppV\Client\Packages\\{PkgGUID}\\Registry\User\\{UserSID}\SOFTWARE|
|
||||
|
||||
### App-V and folder redirection
|
||||
|
||||
App-V supports folder redirection of the roaming AppData folder (%AppData%). When the virtual environment is started, the roaming AppData state from the user’s roaming AppData directory is copied to the local cache. Conversely, when the virtual environment is shut down, the local cache that is associated with a specific user’s roaming AppData is transferred to the actual location of that user’s roaming AppData directory.
|
||||
|
||||
A typical package has several locations mapped in the user’s backing store for settings in both AppData\\Local and AppData\\Roaming. These locations are the Copy on Write locations that are stored per user in the user’s profile, and that are used to store changes made to the package VFS directories and to protect the default package VFS.
|
||||
|
||||
The following table shows local and roaming locations when folder redirection hasn't been implemented.
|
||||
|
||||
| VFS directory in package | Mapped location of backing store |
|
||||
|---|---|
|
||||
| ProgramFilesX86 | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\ProgramFilesX86 |
|
||||
| SystemX86 | C:\Users\username\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\SystemX86 |
|
||||
| Windows | C:\Users\username\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\Windows |
|
||||
| appv\_ROOT | C:\Users\username\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\appv_ROOT|
|
||||
| AppData | C:\Users\username\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\AppData |
|
||||
|
||||
The following table shows local and roaming locations when folder redirection has been implemented for %AppData% and the location has been redirected (typically to a network location).
|
||||
|
||||
| VFS directory in package | Mapped location of backing store |
|
||||
|---|---|
|
||||
| ProgramFilesX86 | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\ProgramFilesX86 |
|
||||
| SystemX86 | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\SystemX86 |
|
||||
| Windows | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\Windows |
|
||||
| appv_ROOT | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\appv\_ROOT |
|
||||
| AppData | \\Fileserver\users\Local\roaming\Microsoft\AppV\Client\VFS\\<GUID>\AppData |
|
||||
|
||||
The current App-V Client VFS driver can't write to network locations, so the App-V Client detects the presence of folder redirection and copies the data on the local drive during publishing and when the virtual environment starts. After the user closes the App-V application and the App-V Client closes the virtual environment, the local storage of the VFS AppData is copied back to the network, enabling roaming to more machines, where the process will be repeated. Here's what happens during the process:
|
||||
|
||||
1. During publishing or virtual environment startup, the App-V Client detects the location of the AppData directory.
|
||||
2. If the roaming AppData path is local or no AppData\\Roaming location is mapped, nothing happens.
|
||||
3. If the roaming AppData path isn't local, the VFS AppData directory is mapped to the local AppData directory.
|
||||
|
||||
This process solves the problem of a non-local %AppData% that isn't supported by the App-V Client VFS driver. However, the data stored in this new location isn't roamed with folder redirection. All changes during the running of the application happen to the local AppData location and must be copied to the redirected location. The process does the following things:
|
||||
|
||||
1. Shuts down the App-V application, which also shuts down the virtual environment.
|
||||
2. Compresses the local cache of the roaming AppData location and store it in a .zip file.
|
||||
3. Uses the time stamp at the end of the .zip packaging process to name the file.
|
||||
4. Records the time stamp in the HKEY\_CURRENT\_USER\\Software\\Microsoft\\AppV\\Client\\Packages\\<GUID>\\AppDataTime registry as the last known AppData time stamp.
|
||||
5. Calls the folder redirection process to evaluate and initiate the .zip file uploaded to the roaming AppData directory.
|
||||
|
||||
The time stamp is used to determine a “last writer wins” scenario if there's a conflict and is used to optimize the download of the data when the App-V application is published, or the virtual environment is started. Folder redirection will make the data available from any other clients covered by the supporting policy and will initiate the process of storing the AppData\\Roaming data to the local AppData location on the client. Here's what happens during the process:
|
||||
|
||||
1. The user starts an application, which also starts the virtual environment.
|
||||
2. The application’s virtual environment checks for the most recent time stamped .zip file, if present.
|
||||
3. The virtual environment checks the registry for the last known uploaded time stamp, if present.
|
||||
4. The virtual environment downloads the most recent .zip file unless the local last known upload time stamp is greater than or equal to the time stamp from the .zip file.
|
||||
5. If the local last known upload time stamp is earlier than that of the most recent .zip file in the roaming AppData location, the virtual environment extracts the .zip file to the local temp directory in the user’s profile.
|
||||
6. After the .zip file is successfully extracted, the local cache of the roaming AppData directory is renamed and the new data moved into place.
|
||||
7. The renamed directory is deleted and the application opens with the most recently saved roaming AppData data.
|
||||
|
||||
This process completes the successful roaming of application settings that are present in AppData\\Roaming locations. The only other condition that must be addressed is a package repair operation. The process does the following things:
|
||||
|
||||
1. During repair, detects if the path to the user’s roaming AppData directory isn't local.
|
||||
2. Maps the non-local roaming AppData path targets, recreating the expected roaming and local AppData locations.
|
||||
3. Deletes the time stamp stored in the registry, if present.
|
||||
|
||||
This process will recreate both the local and network locations for AppData and remove the registry record of the time stamp.
|
||||
|
||||
## App-V Client application lifecycle management
|
||||
|
||||
In an App-V Full Infrastructure, after applications are sequenced, they're managed and published to users or computers through the App-V Management and Publishing servers. This section details the operations that occur during the common App-V application lifecycle operations (Add, publishing, launch, upgrade, and removal) and the file and registry locations that are changed and modified from the App-V Client perspective. The App-V Client operations are input as PowerShell commands on the computer running the App-V Client.
|
||||
|
||||
This document focuses on App-V Full Infrastructure solutions. For specific information on App-V Integration with Microsoft Configuration Manager, see [Deploy App-V virtual applications with Configuration Manager](/mem/configmgr/apps/get-started/deploying-app-v-virtual-applications).
|
||||
|
||||
The App-V application lifecycle tasks are triggered at user sign in (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured (after the client is enabled) with Windows PowerShell commands. See [App-V Client Configuration Settings: Windows PowerShell](appv-client-configuration-settings.md#app-v-client-configuration-settings-windows-powershell).
|
||||
|
||||
### Publishing refresh
|
||||
|
||||
The publishing refresh process comprises several smaller operations that are performed on the App-V Client. Since App-V is an application virtualization technology and not a task scheduling technology, the Windows Task Scheduler is utilized to enable the process when the user signs in, the machine turns on, and at scheduled intervals. The client configuration during setup listed in the previous section is the preferred method when distributing the client to a large group of computers with the correct settings. These client settings can be configured with the following Windows PowerShell cmdlets:
|
||||
|
||||
- **Add-AppVPublishingServer** configures the client with an App-V Publishing Server that provides App-V packages.
|
||||
- **Set-AppVPublishingServer** modifies the current settings for the App-V Publishing Server.
|
||||
- **Set-AppVClientConfiguration** modifies the currents settings for the App-V Client.
|
||||
- **Sync-AppVPublishingServer** initiates an App-V Publishing Refresh process manually. This process is also utilized in the scheduled tasks created during configuration of the publishing server.
|
||||
|
||||
The following sections will elaborate what goes on during the publishing refresh process.
|
||||
|
||||
#### Adding an App-V package
|
||||
|
||||
Adding an App-V package to the client is the first step of the publishing refresh process. The end result is the same as the **Add-AppVClientPackage** cmdlet in Windows PowerShell, except the publishing refresh add process contacts the configured publishing server and passes a high-level list of applications back to the client to pull more detailed information, rather than just doing a single package add operation.
|
||||
|
||||
The process then configures the client for package or connection group additions or updates, then accesses the appv file. Next, the contents of the appv file are expanded and placed on the local operating system in the appropriate locations. The following steps are a detailed workflow of the process, assuming the package is configured for Fault Streaming.
|
||||
|
||||
#### How to add an App-V package
|
||||
|
||||
1. Initiate installation manually through Windows PowerShell or Task Sequence initiation of the Publishing Refresh process.
|
||||
|
||||
1. The App-V Client makes an HTTP connection and requests a list of applications based on the target. The Publishing refresh process supports targeting machines or users.
|
||||
|
||||
2. The App-V Publishing Server uses the identity of the initiating target, user or machine, and queries the database for a list of entitled applications. The list of applications is provided as an XML response, which the client uses to send more requests to the server for more information on a per-package basis.
|
||||
|
||||
2. The Publishing Agent on the App-V Client will evaluate any connection groups that are unpublished or disabled, since package version updates that are part of the connection group can't be processed.
|
||||
|
||||
3. Configure the packages by identifying the **Add** or **Update** operations.
|
||||
|
||||
1. The App-V Client utilizes the AppX API from Windows and accesses the appv file from the publishing server.
|
||||
|
||||
2. The package file is opened and the **AppXManifest.xml** and **StreamMap.xml** files are downloaded to the Package Store.
|
||||
|
||||
3. Completely stream publishing block data defined in the **StreamMap.xml** file. Publishing block data is stored in Package Store\\PkgGUID\\VerGUID\\Root.
|
||||
|
||||
- Icons: Targets of extension points.
|
||||
- Portable Executable Headers (PE Headers): Targets of extension points that contain the base information about the image need on disk, accessed directly or through file types.
|
||||
- Scripts: Download scripts directory for use throughout the publishing process.
|
||||
|
||||
4. Populate the Package store by performing the following sub-steps:
|
||||
|
||||
1. Create sparse files on disk that represent the extracted package for any directories listed.
|
||||
|
||||
2. Stage top-level files and directories under root.
|
||||
|
||||
All other files are created when the directory is listed as sparse on disk and streamed on demand.
|
||||
|
||||
5. Create the machine catalog entries. Create the **Manifest.xml** and **DeploymentConfiguration.xml** files from the package files (if no **DeploymentConfiguration.xml** file in the package a placeholder is created).
|
||||
|
||||
6. Create location of the package store in the registry **HKLM\\Software\\Microsoft\\AppV\\Client\\Packages\\PkgGUID\\Versions\\VerGUID\\Catalog**.
|
||||
|
||||
7. Create the **Registry.dat** file from the package store to **%ProgramData%\\Microsoft\\AppV\\Client\\VReg\\{VersionGUID}.dat**.
|
||||
|
||||
8. Register the package with the App-V Kernel Mode Driver at **HKLM\\Microsoft\\Software\\AppV\\MAV**.
|
||||
|
||||
9. Invoke scripting from the **AppxManifest.xml** or **DeploymentConfig.xml** file for Package Add timing.
|
||||
|
||||
4. Configure Connection Groups by adding and enabling or disabling.
|
||||
|
||||
5. Remove objects that aren't published to the target (user or machine).
|
||||
|
||||
> [!NOTE]
|
||||
>This will not perform a package deletion but rather remove integration points for the specific target (user or machine) and remove user catalog files (machine catalog files for globally published).
|
||||
|
||||
6. Invoke background load mounting based on client configuration.
|
||||
|
||||
7. Packages that already have publishing information for the machine or user are immediately restored.
|
||||
|
||||
> [!NOTE]
|
||||
>This condition occurs as a product of removal without unpublishing with background addition of the package.
|
||||
|
||||
This process completes an App-V package add for the publishing refresh process. The next step is publishing the package to a specific target (machine or user).
|
||||
|
||||
|
||||
|
||||
**Package add file and registry data**
|
||||
|
||||
#### Publishing an App-V package
|
||||
|
||||
During the Publishing Refresh operation, the specific publishing operation, **Publish-AppVClientPackage**, adds entries to the user catalog, maps entitlement to the user, identifies the local store, and finishes by completing any integration steps.
|
||||
|
||||
#### How to publish an App-V package
|
||||
|
||||
1. Package entries are added to the user catalog
|
||||
|
||||
1. User targeted packages: the **UserDeploymentConfiguration.xml** and **UserManifest.xml** files are placed on the machine in the User Catalog.
|
||||
|
||||
2. Machine targeted (global) packages: the **UserDeploymentConfiguration.xml** is placed in the Machine Catalog.
|
||||
|
||||
2. Register the package with the kernel mode driver for the user at **HKLM\\Software\\Microsoft\\AppV\\MAV**.
|
||||
|
||||
3. Perform integration tasks.
|
||||
|
||||
1. Create extension points.
|
||||
|
||||
2. Store backup information in the user’s registry and roaming profile (Shortcut Backups).
|
||||
|
||||
> [!NOTE]
|
||||
>This enables restore extension points if the package is unpublished.
|
||||
|
||||
3. Run scripts targeted for publishing timing.
|
||||
|
||||
Publishing an App-V Package that is part of a Connection Group is similar to the above process. For connection groups, the path that stores the specific catalog information includes PackageGroups as a child of the Catalog Directory. Review the Machine and User Catalog information in the preceding sections for details.
|
||||
|
||||
|
||||
|
||||
**Package add file and registry data—global**
|
||||
|
||||
### Application launch
|
||||
|
||||
After the Publishing Refresh process, the user launches and then relaunches an App-V application. The App-V Client checks the path to the user catalog for files created during publishing. After establishing rights to launch the package, the App-V Client creates a virtual environment, begins streaming any necessary data, and applies the appropriate manifest and deployment configuration files during virtual environment creation. Once the virtual environment created and configured for the specific package and application, the application starts. This might seem like a lot, but the process in action is fast, and is optimized to minimize network traffic.
|
||||
|
||||
#### How to launch App-V applications
|
||||
|
||||
1. User launches the application by selecting a shortcut or file type invocation.
|
||||
|
||||
2. The App-V Client verifies existence in the User Catalog for the following files
|
||||
|
||||
- **UserDeploymentConfiguration.xml**
|
||||
- **UserManifest.xml**
|
||||
|
||||
3. If the files are present, the application is entitled for that specific user and the application will start the process for launch. There's no network traffic at this point.
|
||||
|
||||
4. Next, the App-V Client checks that the path for the package registered for the App-V Client service is found in the registry.
|
||||
|
||||
5. Upon finding the path to the package store, the virtual environment is created.
|
||||
|
||||
If this process execution is the first launch, the Primary Feature Block downloads if present.
|
||||
|
||||
6. After downloading, the App-V Client service consumes the manifest and deployment configuration files to configure the virtual environment and all App-V subsystems are loaded.
|
||||
|
||||
7. The Application launches. For any missing files in the package store (sparse files), App-V will stream fault the files on an as-needed basis.
|
||||
|
||||
|
||||
|
||||
**Package add file and registry data—stream**
|
||||
|
||||
### Upgrading an App-V package
|
||||
|
||||
The current version of App-V's package upgrade process differs from the older versions in its storage optimization. App-V supports multiple versions of the same package on a machine entitled to different users. Package versions can be added at any time, as the package store and catalogs are updated with the new resources. During an upgrade in the new version, only new files are added to the new version store location, and hard links are created for unchanged files. Such results reduce overall storage by only presenting the file on one disk location, then projecting it into all folders with a file location entry on the disk.
|
||||
|
||||
#### How to upgrade an App-V package
|
||||
|
||||
1. The App-V Client performs a Publishing Refresh and discovers a newer version of an App-V Package.
|
||||
|
||||
2. Package entries are added to the appropriate catalog for the new version.
|
||||
|
||||
1. User targeted packages: the **UserDeploymentConfiguration.xml** and **UserManifest.xml** files are placed on the machine in the user catalog at **appdata\\roaming\\Microsoft\\AppV\\Client\\Catalog\\Packages\\PkgGUID\\VerGUID**.
|
||||
|
||||
2. Machine targeted (global) packages: the **UserDeploymentConfiguration.xml** is placed in the machine catalog at **%programdata%\\Microsoft\\AppV\\Client\\Catalog\\Packages\\PkgGUID\\VerGUID**.
|
||||
|
||||
3. Register the package with the kernel mode driver for the user at **HKLM\\Software\\Microsoft\\AppV\\MAV**.
|
||||
|
||||
4. Perform integration tasks.
|
||||
|
||||
1. Integrate extensions points (EP) from the Manifest and Dynamic Configuration files.
|
||||
|
||||
2. File based EP data is stored in the AppData folder utilizing Junction Points from the package store.
|
||||
|
||||
3. Version 1 EPs already exist when a new version becomes available.
|
||||
|
||||
4. The extension points are switched to the Version 2 location in machine or user catalogs for any newer or updated extension points.
|
||||
|
||||
5. Run scripts targeted for publishing timing.
|
||||
|
||||
6. Install Side-by-Side assemblies as required.
|
||||
|
||||
### Upgrading an in-use App-V package
|
||||
|
||||
If you try to upgrade a package that is currently in use, the upgrade task is placed in a pending state. The upgrade will run later, according to the following rules:
|
||||
|
||||
| Task type | Applicable rule |
|
||||
|---|---|
|
||||
| User-based tasks, such as publishing a package to a user | The pending task will be performed after the user signs out and then signs back in. |
|
||||
| Globally based tasks, such as enabling a connection group globally | The pending task will be performed when the computer is shut down and then restarted. |
|
||||
|
||||
When a task is placed in a pending state, the App-V Client also generates a registry key for the pending task, as follows:
|
||||
|
||||
| User-based or globally based task | Where the registry key is generated |
|
||||
|---|---|
|
||||
| User-based tasks | HKEY\_CURRENT\_USER\Software\Microsoft\AppV\Client\PendingTasks |
|
||||
| Globally based tasks | HKEY\_LOCAL\_MACHINE\Software\Microsoft\AppV\Client\PendingTasks |
|
||||
|
||||
The following operations must be completed before users can use the newer version of the package:
|
||||
|
||||
| Task | Details |
|
||||
|---|---|
|
||||
| Add the package to the computer | This task is computer-specific and you can perform it at any time by completing the steps in [How to add an App-V package](#how-to-add-an-app-v-package). |
|
||||
| Publish the package | See the Package Publishing section above for steps. This process requires that you update extension points on the system. You can't complete this task while the application is in use. |
|
||||
|
||||
Use the following example scenarios as a guide for updating packages.
|
||||
|
||||
| Scenario | Requirements |
|
||||
|---|---|
|
||||
| App-V package isn't in use when you try to upgrade | None of the following components of the package can be in use: virtual application, COM server, or shell extensions.<br/><br/>The administrator publishes a newer version of the package and the upgrade works the next time a component or application inside the package is launched. The new version of the package is streamed and ran. |
|
||||
| App-V package is in use when the administrator publishes a newer version of the package | The App-V Client sets the operation to "pending," which means that it's queued and will be carried out later when the package isn't in use.<br/><br/>If the package application is in use, the user shuts down the virtual application, after which the upgrade can occur.<br/><br/>If the package has shell extensions, which are permanently loaded by Windows Explorer, the user won't be able to sign in. Users must sign off and then sign back in to initiate the App-V package upgrade.|
|
||||
|
||||
### Global vs. user publishing
|
||||
|
||||
App-V Packages can be published in one of two ways; as user, which entitles an App-V package to a specific user or group of users, or as global, which entitles the App-V package to the entire machine for all users of the machine. Once a package upgrade has been pended and the App-V package isn't in use, consider the two types of publishing:
|
||||
|
||||
- Global publishing is when the application is published to a machine; all users on that machine can use it. The upgrade will happen when the App-V Client Service starts, which effectively means a machine restart.
|
||||
- User publishing is when the application is published to a user. If there are multiple users on the machine, the application can be published to a subset of the users. The upgrade will happen when the user signs in or when it's published again (periodically, ConfigMgr Policy refresh and evaluation, or an App-V periodic publishing/refresh, or explicitly through Windows PowerShell commands).
|
||||
|
||||
### Removing an App-V package
|
||||
|
||||
Removing App-V applications in a Full Infrastructure is an unpublish operation and doesn't perform a package removal. The process is the same as the publish process above, but instead of adding the removal process reverses the changes that have been made for App-V Packages.
|
||||
|
||||
### Repairing an App-V package
|
||||
|
||||
The repair operation is easy to do but may affect many locations on the machine. The previously mentioned Copy on Write (COW) locations are removed, and extension points are deintegrated and then reintegrated. Before repairing, please review where the COW data placement locations are registered in the registry. To perform a Repair operation, all you need to do is initiate it from the App-V Client Console or through the **Repair-AppVClientPackage** PowerShell cmdlet. After that, the operation is completed automatically.
|
||||
|
||||
## Integration of App-V packages
|
||||
|
||||
The App-V Client and package architecture provides specific integration with the local operating system during the addition and publishing of packages. Three files define the integration or extension points for an App-V Package:
|
||||
|
||||
- AppXManifest.xml is stored inside of the package with fallback copies stored in the package store and the user profile. Contains the options created during the sequencing process.
|
||||
- DeploymentConfig.xml provides configuration information of computer- and user-based integration extension points.
|
||||
- UserConfig.xml is a subset of the Deploymentconfig.xml file that only provides user-based configurations and only targets user-based extension points.
|
||||
|
||||
### Rules of integration
|
||||
|
||||
When App-V applications are published to a computer with the App-V Client, some specific actions take place as described in the following list:
|
||||
|
||||
- Global Publishing: Shortcuts are stored in the All Users profile location and other extension points are stored in the registry in the HKLM hive.
|
||||
- User Publishing: Shortcuts are stored in the current user account profile and other extension points are stored in the registry in the HKCU hive.
|
||||
- Backup and Restore: Existing native application data and registry (such as FTA registrations) are backed up during publishing.
|
||||
|
||||
1. App-V packages are given ownership based on the last integrated package where the ownership is passed to the newest published App-V application.
|
||||
2. Ownership transfers from one App-V package to another when the owning App-V package is unpublished. This transfer won't initiate a restore of the data or registry.
|
||||
3. Restore the backed-up data when the last package is unpublished or removed on a per-extension point basis.
|
||||
|
||||
### Extension points
|
||||
|
||||
The App-V publishing files (manifest and dynamic configuration) provide several extension points to integrate the application with the local operating system. These extension points perform typical application installation tasks, such as placing shortcuts, creating file type associations, and registering components. As these are virtualized applications that aren't installed in the same manner a traditional application, there are some differences. The following is a list of extension points covered in this section:
|
||||
|
||||
- Shortcuts
|
||||
- File type associations
|
||||
- Shell extensions
|
||||
- COM
|
||||
- Software clients
|
||||
- Application capabilities
|
||||
- URL Protocol handler
|
||||
- AppPath
|
||||
- Virtual application
|
||||
|
||||
### Shortcuts
|
||||
|
||||
The shortcut is one of the basic elements of integration with the OS and is the interface for direct user launch of an App-V application. During the publishing and unpublishing of App-V applications.
|
||||
|
||||
From the package manifest and dynamic configuration XML files, the path to a specific application executable can be found in a section as shown in the following example:
|
||||
|
||||
```XML
|
||||
<Extension Category="AppV.Shortcut">
|
||||
<Shortcut>
|
||||
<File>[{Common Desktop}]\Adobe Reader.lnk</File>
|
||||
<Target>[{AppVPackageRoot}]\Reader\AcroRd32.exe</Target>
|
||||
<Icon>[{Windows}]\Installer\{AC76BA86-7AD7-1033-7B44-A94000000001}\SC_Reader.ico</Icon>
|
||||
<Arguments />
|
||||
<WorkingDirectory />
|
||||
<ShowCommand>1</ShowCommand>
|
||||
<ApplicationId>[{AppVPackageRoot}]\Reader\AcroRd32.exe</ApplicationId>
|
||||
</Shortcut>
|
||||
</Extension>
|
||||
```
|
||||
|
||||
As mentioned previously, the App-V shortcuts are placed by default in the user’s profile based on the refresh operation. Global refresh places shortcuts in the All Users profile and user refresh stores them in the specific user’s profile. The actual executable is stored in the Package Store. The location of the ICO file is a tokenized location in the App-V package.
|
||||
|
||||
### File type associations
|
||||
|
||||
Users can use file type invocations or open a file with a registered extension (.docx) to start an App-V application because the App-V Client manages the local operating system File Type Associations during publishing. File type associations are present in the manifest and dynamic configuration files, as shown in the following example:
|
||||
|
||||
```XML
|
||||
<Extension Category="AppV.FileTypeAssociation">
|
||||
<FileTypeAssociation>
|
||||
<FileExtension MimeAssociation="true">
|
||||
<Name>.xdp</Name>
|
||||
<ProgId>AcroExch.XDPDoc</ProgId>
|
||||
<ContentType>application/vnd.adobe.xdp+xml</ContentType>
|
||||
</FileExtension>
|
||||
<ProgId>
|
||||
<Name>AcroExch.XDPDoc</Name>
|
||||
<Description>Adobe Acrobat XML Data Package File</Description>
|
||||
<EditFlags>65536</EditFlags>
|
||||
<DefaultIcon>[{Windows}]\Installer\{AC76BA86-7AD7-1033-7B44-A94000000001}\XDPFile_8.ico</DefaultIcon>
|
||||
<ShellCommands>
|
||||
<DefaultCommand>Read</DefaultCommand>
|
||||
<ShellCommand>
|
||||
<ApplicationId>[{AppVPackageRoot}]\Reader\AcroRd32.exe</ApplicationId>
|
||||
<Name>Open</Name>
|
||||
<CommandLine>"[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1"</CommandLine>
|
||||
</ShellCommand>
|
||||
<ShellCommand>
|
||||
<ApplicationId>[{AppVPackageRoot}]\Reader\AcroRd32.exe</ApplicationId>
|
||||
<Name>Printto</Name>
|
||||
<CommandLine>"[{AppVPackageRoot}]\Reader\AcroRd32.exe" /t "%1" "%2" "%3" "%4"</CommandLine>
|
||||
</ShellCommand>
|
||||
<ShellCommand>
|
||||
<ApplicationId>[{AppVPackageRoot}]\Reader\AcroRd32.exe</ApplicationId>
|
||||
<Name>Read</Name>
|
||||
<FriendlyName>Open with Adobe Reader</FriendlyName>
|
||||
<CommandLine>"[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1"</CommandLine>
|
||||
</ShellCommand>
|
||||
</ShellCommands>
|
||||
</ProgId>
|
||||
</FileTypeAssociation>
|
||||
</Extension>
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
>In this example:
|
||||
>- `<Name>.xdp</Name>` is the extension
|
||||
>- `<Name>AcroExch.XDPDoc</Name>` is the ProgId value (which points to the adjoining ProgId)
|
||||
>- `<CommandLine>"[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1"</CommandLine>` is the command line, which points to the application executable
|
||||
|
||||
### Shell extensions
|
||||
|
||||
Shell extensions are embedded in the package automatically during the sequencing process. When the package is published globally, the shell extension gives users the same functionality as if the application were locally installed. The application requires no extra setup or configuration on the client to enable the shell extension functionality.
|
||||
|
||||
#### Requirements for using shell extensions
|
||||
|
||||
- Packages that contain embedded shell extensions must be published globally.
|
||||
- The “bitness” of the application, Sequencer, and App-V Client must match, or the shell extensions won’t work. The following example configuration fulfills the matching requirement:
|
||||
- The version of the application is 64-bit.
|
||||
- The Sequencer is running on a 64-bit computer.
|
||||
- The package is being delivered to a 64-bit App-V Client computer.
|
||||
|
||||
The following table displays the supported shell extensions.
|
||||
|
||||
| Handler | Description |
|
||||
|---|---|
|
||||
| Context menu handler | Adds menu items to the context menu. it's called before the context menu is displayed. |
|
||||
| Drag-and-drop handler | Controls the action upon right-click drag-and-drop and modifies the context menu that appears. |
|
||||
| Drop target handler | Controls the action after a data object is dragged-and-dropped over a drop target, such as a file.|
|
||||
| Data object handler| Controls the action after a file is copied to the clipboard or dragged-and-dropped over a drop target. It can provide more clipboard formats to the drop target.|
|
||||
| Property sheet handler| Replaces or adds pages to the property sheet dialog box of an object.|
|
||||
| Infotip handler| Allows retrieving flags and infotip information for an item and displaying it inside a popup tooltip upon mouse-hover.|
|
||||
| Column handler| Allows creating and displaying custom columns in Windows Explorer *Details view*. It can be used to extend sorting and grouping.|
|
||||
| Preview handler| Enables a preview of a file to be displayed in the Windows Explorer Preview Pane.|
|
||||
|
||||
### COM
|
||||
|
||||
The App-V Client supports publishing applications with support for COM integration and virtualization. COM integration allows the App-V Client to register COM objects on the local operating system and virtualization of the objects. For the purposes of this document, the integration of COM objects requires more details.
|
||||
|
||||
App-V supports registering COM objects from the package to the local operating system with two process types: Out-of-process and In-process. Registering COM objects is accomplished with one or a combination of multiple modes of operation for a specific App-V package that includes Off, Isolated, and Integrated. Integrated mode is configured for either the Out-of-process or In-process type. Configuration of COM modes and types is accomplished with dynamic configuration files (deploymentconfig.xml or userconfig.xml).
|
||||
|
||||
For details on App-V integration, see [Microsoft Application Virtualization 5.0 Integration](/archive/blogs/appv/microsoft-application-virtualization-5-0-integration).
|
||||
|
||||
### Software clients and application capabilities
|
||||
|
||||
App-V supports specific software clients and application capabilities extension points to register virtualized applications with the operating system's software client. This specific support means users can select default programs for operations like email, instant messaging, and using the media player. This operation is performed in the control panel with **Set Program Access** and **Computer Defaults**, and is configured during sequencing in the manifest or dynamic configuration files. Application capabilities are only supported when the App-V applications are published globally.
|
||||
|
||||
The following example illustrates a software client registration of an App-V-based mail client.
|
||||
|
||||
```XML
|
||||
<SoftwareClients Enabled="true">
|
||||
<ClientConfiguration EmailEnabled="true" />
|
||||
<Extensions>
|
||||
<Extension Category="AppV.SoftwareClient">
|
||||
<SoftwareClients>
|
||||
<EMail MakeDefault="true">
|
||||
<Name>Mozilla Thunderbird</Name>
|
||||
<Description>Mozilla Thunderbird</Description>
|
||||
<DefaultIcon>[{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe,0</DefaultIcon>
|
||||
<InstallationInformation>
|
||||
<RegistrationCommands>
|
||||
<Reinstall>"[{ProgramFilesX86}]\Mozilla Thunderbird\uninstall\helper.exe" /SetAsDefaultAppGlobal</Reinstall>
|
||||
<HideIcons>"[{ProgramFilesX86}]\Mozilla Thunderbird\uninstall\helper.exe" /HideShortcuts</HideIcons>
|
||||
<ShowIcons>"[{ProgramFilesX86}]\Mozilla Thunderbird\uninstall\helper.exe" /ShowShortcuts</ShowIcons>
|
||||
</RegistrationCommands>
|
||||
<IconsVisible>1</IconsVisible>
|
||||
<OEMSettings />
|
||||
</InstallationInformation>
|
||||
<ShellCommands>
|
||||
<ApplicationId>[{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe</ApplicationId>
|
||||
<Open>"[{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe" -mail</Open>
|
||||
</ShellCommands>
|
||||
<MAPILibrary>[{ProgramFilesX86}]\Mozilla Thunderbird\mozMapi32_InUse.dll</MAPILibrary>
|
||||
<MailToProtocol>
|
||||
<Description>Thunderbird URL</Description>
|
||||
<EditFlags>2</EditFlags>
|
||||
<DefaultIcon>[{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe,0</DefaultIcon>
|
||||
<ShellCommands>
|
||||
<ApplicationId>[{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe</ApplicationId>
|
||||
<Open>"[{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe" -osint -compose "%1"</Open>
|
||||
</ShellCommands>
|
||||
</MailToProtocol>
|
||||
</EMail>
|
||||
</SoftwareClients>
|
||||
</Extension>
|
||||
</Extensions>
|
||||
</SoftwareClients>
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
>In this example:
|
||||
>- `<ClientConfiguration EmailEnabled="true" />` is the overall Software Clients setting to integrate Email clients.
|
||||
>- `<EMail MakeDefault="true">` is the flag to set a particular Email client as the default Email client.
|
||||
>- `<MAPILibrary>[{ProgramFilesX86}]\Mozilla Thunderbird\mozMapi32_InUse.dll</MAPILibrary>` is the MAPI dll registration.
|
||||
|
||||
### URL Protocol handler
|
||||
|
||||
Virtual applications don't always specifically utilize file type invocation. For, example, in an application that supports embedding a mailto: link inside a document or web page, the user selects the link expecting to access their registered mail client. App-V supports URL Protocol handlers that can be registered on a per-package basis with the local operating system. During sequencing, the URL Protocol handlers are automatically added to the package.
|
||||
|
||||
For situations where there's more than one application that could register the specific URL Protocol handler, the dynamic configuration files can be utilized to modify the behavior and suppress or disable this feature for an application that shouldn't be the primary application launched.
|
||||
|
||||
### AppPath
|
||||
|
||||
The AppPath extension point supports calling App-V applications directly from the operating system. Administrators can provide access to App-V applications from operating system commands or scripts without calling the specific path to the executable from either the Run or Start Screen, depending on the operating system. It therefore avoids modifying the system path environment variable on all systems, as it's accomplished during publishing.
|
||||
|
||||
The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For more information on AppPath review: [App Paths - A Virtual Application Extension in App-V 5.0](/archive/blogs/virtualworld/app-paths-a-virtual-application-extension-in-app-v-5-0).
|
||||
|
||||
### Virtual application
|
||||
|
||||
This subsystem provides a list of applications captured during sequencing which is consumed by other App-V components. Integration of extension points belonging to a specific application can be disabled using dynamic configuration files. For example, if a package contains two applications, you can disable all extension points belonging to one application to only allow integration of extension points for the other application.
|
||||
|
||||
### Extension point rules
|
||||
|
||||
The previously described extension points are integrated into the operating system based on how the packages have been published. Global publishing places extension points in public machine locations, where user publishing places extension points in user locations. For example, a shortcut created on the desktop and published globally will result in the file data for the shortcut (%Public%\\Desktop) and the registry data (HKLM\\Software\\Classes). The same shortcut would have file data (%UserProfile%\\Desktop) and registry data (HKCU\\Software\\Classes).
|
||||
|
||||
Extension points aren't all published the same way, where some extension points will require global publishing and others require sequencing on the specific operating system and architecture where they're delivered. Below is a table that describes these two key rules.
|
||||
|
||||
|Virtual Extension|Requires target OS sequencing|Requires global publishing|
|
||||
|---|:---:|:---:|
|
||||
|Shortcut|||
|
||||
|File Type Association|||
|
||||
|URL Protocols|X||
|
||||
|AppPaths|X||
|
||||
|COM Mode|||
|
||||
|Software Client|X||
|
||||
|Application Capabilities|X|X|
|
||||
|Context Menu Handler|X|X|
|
||||
|Drag-and-drop Handler|X||
|
||||
|Data Object Handler|X||
|
||||
|Property Sheet Handler|X||
|
||||
|Infotip Handler|X||
|
||||
|Column Handler|X||
|
||||
|Shell Extensions|X||
|
||||
|Browser Helper Object|X|X|
|
||||
|Active X Object|X|X|
|
||||
|
||||
## Dynamic configuration processing
|
||||
|
||||
Deploying App-V packages to a single machine or user is simple. However, as organizations deploy App-V applications across business lines and geographic and political boundaries, it becomes impossible to sequence all applications with the same settings. App-V was designed to overcome this problem by capturing specific settings and configurations during sequencing in the Manifest file while also supporting modification with Dynamic Configuration files.
|
||||
|
||||
App-V dynamic configuration lets you specify a package policy at either the machine or user levels. Sequencing engineers can use Dynamic Configuration files to modify the configuration of a package post-sequencing to address the needs of individual groups of users or machines. In some instances, it may be necessary to modify the application to provide proper functionality within the App-V environment. For example, you may need to modify the \_\*config.xml files to allow certain actions to be performed at a specified time while executing the application, like disabling a mailto extension to prevent a virtualized application from overwriting that extension from another application.
|
||||
|
||||
App-V packages contain the Manifest file inside of the App-V Package file, which is representative of sequencing operations and is the policy of choice unless Dynamic Configuration files are assigned to a specific package. Post-sequencing, the Dynamic Configuration files can be modified to allow an application to be published to different desktops or users with different extension points. The two Dynamic Configuration files are the Dynamic Deployment Configuration (DDC) and Dynamic User Configuration (DUC) files. This section focuses on the combination of the manifest and dynamic configuration files.
|
||||
|
||||
### Examples of dynamic configuration files
|
||||
|
||||
The following example shows the combination of the Manifest, Deployment Configuration, and User Configuration files after publishing and during normal operation. These examples are abbreviated examples of each of the files. The purpose is to show the combination of the files only, not to be a complete description of the specific categories available in each file. For more information, download the [App-V Sequencing Guide](https://www.microsoft.com/download/details.aspx?id=27760).
|
||||
|
||||
#### Manifest
|
||||
|
||||
```XML
|
||||
<appv:Extension Category="AppV.Shortcut">
|
||||
<appv:Shortcut>
|
||||
<appv:File>[{Common Programs}]\7-Zip\7-Zip File Manager.lnk</appv:File>
|
||||
<appv:Target>[{AppVPackageRoot}]\7zFM.exe</appv:Target>
|
||||
<appv:Icon>[{AppVPackageRoot}]\7zFM exe.O.ico</appv:Icon>
|
||||
</appv:Shortcut>
|
||||
</appv:Extension>
|
||||
```
|
||||
|
||||
#### Deployment Configuration
|
||||
|
||||
```XML
|
||||
<MachineConfiguration>
|
||||
<Subsystems>
|
||||
<Registry>
|
||||
<Include>
|
||||
<Key Path= "\REGISTRY\Machine\Software\7zip">
|
||||
<Value Type="REG_SZ" Name="Config" Data="1234"/>
|
||||
</Key>
|
||||
</Include>
|
||||
</Registry>
|
||||
</Subsystems>
|
||||
```
|
||||
|
||||
#### User Configuration
|
||||
|
||||
```XML
|
||||
<UserConfiguration>
|
||||
<Subsystems>
|
||||
<appv:ExtensionCategory="AppV.Shortcut">
|
||||
<appv:Shortcut>
|
||||
<appv:File>[{Desktop}]\7-Zip\7-Zip File Manager.lnk</appv:File>
|
||||
<appv:Target>[{AppVPackageRoot}]\7zFM.exe</appv:Target>
|
||||
<appv:Icon>[{AppVPackageRoot}]\7zFM exe.O.ico</appv:Icon>
|
||||
</appv:Shortcut>
|
||||
</appv:Extension>
|
||||
</Subsystems>
|
||||
<UserConfiguration>
|
||||
<Subsystems>
|
||||
<appv:Extension Category="AppV.Shortcut">
|
||||
<appv:Shortcut>
|
||||
<appv:Fìle>[{Desktop}]\7-Zip\7-Zip File Manager.lnk</appv:File>
|
||||
<appv:Target>[{AppVPackageRoot}]\7zFM.exe</appv:Target>
|
||||
<appv:Icon>[{AppVPackageRoot}]\7zFM.exe.O.ico</appv:Icon>
|
||||
</appv:Shortcut>
|
||||
<appv:Shortcut>
|
||||
<appv:File>[{Common Programs}]\7-Zip\7-Zip File Manager.Ink</appv:File>
|
||||
<appv:Target>[{AppVPackageRoot}]\7zFM.exe</appv:Target>
|
||||
<appv:Icon>[{AppVPackageRoot)]\7zFM.exe.O.ico</appv: Icon>
|
||||
</appv:Shortcut>
|
||||
</appv:Extension>
|
||||
</Subsystems>
|
||||
<MachineConfiguration>
|
||||
<Subsystems>
|
||||
<Registry>
|
||||
<Include>
|
||||
<Key Path="\REGISTRY\Machine\Software\7zip">
|
||||
<Value Type=”REG_SZ" Name="Config" Data="1234"/>
|
||||
</Include>
|
||||
</Registry>
|
||||
</Subsystems>
|
||||
```
|
||||
|
||||
## Side-by-side assemblies
|
||||
|
||||
App-V supports automatic packaging of side-by-side assemblies during sequencing and deployment on the client during virtual application publishing. App-V also supports capturing side-by-side assemblies during sequencing for assemblies not present on the sequencing machine. For assemblies consisting of Visual C++ (Version 8 and newer) or MSXML run-time, the Sequencer will automatically detect and capture these dependencies even if they weren't installed during monitoring.
|
||||
|
||||
The side-by-side assemblies feature removes the limitations of previous versions of App-V, where the App-V Sequencer didn't capture assemblies already present on the sequencing workstation, and privatized the assemblies, which limited it to a bit version per package. This behavior resulted in App-V applications being deployed to clients missing the required side-by-side assemblies, which led to application launch failures. This failure forced the packaging process to document and ensure that all assemblies required for packages were locally installed on the user’s client operating system. This task was both a management and implementation challenge due to the number of assemblies and the lack of application documentation for the required dependencies.
|
||||
|
||||
Side-by-side assembly support in App-V has the following features:
|
||||
|
||||
- Automatic captures of side-by-side assembly during sequencing, regardless of whether the assembly was already installed on the sequencing workstation.
|
||||
- The App-V Client automatically installs required side-by-side assemblies to the client computer at publishing time if they aren't already installed.
|
||||
- The Sequencer reports the VC run-time dependency in Sequencer reporting mechanism.
|
||||
- The Sequencer allows opting to not package assemblies already installed on the Sequencer, supporting scenarios where the assemblies have previously been installed on the target computers.
|
||||
|
||||
### Automatic publishing of side-by-side assemblies
|
||||
|
||||
During publishing of an App-V package with side-by-side assemblies, the App-V Client will check for the presence of the assembly on the machine. If it doesn't detect an assembly, the client will deploy the assembly to the machine. Packages that are part of connection groups will rely on the side-by-side assembly installations in the base packages, as the connection groups don't contain any information about assembly installation.
|
||||
|
||||
>[!NOTE]
|
||||
>Unpublishing or removing a package with an assembly doesn't remove the assemblies for that package.
|
||||
|
||||
## Client logging
|
||||
|
||||
The App-V Client logs information to the Windows Event log in standard ETW format. The specific App-V events can be found in the event viewer under **Applications and Services Logs\\Microsoft\\AppV\\Client**.
|
||||
|
||||
There're three specific categories of events recorded:
|
||||
|
||||
- **Admin** logs events for configurations applied to the App-V Client and also contains the primary warnings and errors.
|
||||
- **Operational** logs the general App-V execution and usage of individual components, creating an audit log of the App-V Client's completed App-V operations.
|
||||
- **Virtual Application** logs virtual application launches and use of virtualization subsystems.
|
||||
@ -1,49 +0,0 @@
|
||||
---
|
||||
title: Apply deployment config file via Windows PowerShell (Windows 10/11)
|
||||
description: How to apply the deployment configuration file by using Windows PowerShell for Windows 10/11.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/15/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# How to apply the deployment configuration file by using Windows PowerShell
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
When you add or set a package to a computer running the App-V client before it's been published, a dynamic deployment configuration file is applied to it. The dynamic deployment configuration file configures the default settings for the package that all users share on the computer running the App-V client. This section will tell you how to use a deployment configuration file.
|
||||
|
||||
## Apply the deployment configuration file with Windows PowerShell
|
||||
|
||||
> [!NOTE]
|
||||
> The following example cmdlet uses the following two file paths for the package and configuration files:
|
||||
>
|
||||
> * C:\\Packages\\Contoso\\MyApp.appv
|
||||
> * C:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml
|
||||
>
|
||||
> If your package and configuration files use different file paths than the example, feel free to replace them as needed.
|
||||
|
||||
To specify a new default set of configurations for all users who will run the package on a specific computer, in a Windows PowerShell console, enter the following cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Add-AppVClientPackage -Path C:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration C:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
>This command captures the resulting object into $pkg. If the package is already present on the computer, you can use the **Set-AppVclientPackage** cmdlet to apply the deployment configuration document:
|
||||
>
|
||||
> ```PowerShell
|
||||
> Set-AppVClientPackage -Name Myapp -Path C:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration C:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml
|
||||
> ```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
* [Operations for App-V](appv-operations.md)
|
||||
@ -1,48 +0,0 @@
|
||||
---
|
||||
title: How to apply the user configuration file by using Windows PowerShell (Windows 10/11)
|
||||
description: How to apply the user configuration file by using Windows PowerShell (Windows 10/11).
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/15/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# How to apply the user configuration file by using Windows PowerShell
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
When you publish a package to a specific user, you'll also need to specify a dynamic user configuration file to tell that package how to run.
|
||||
|
||||
## Apply a user configuration file
|
||||
|
||||
Here's how to specify a user-specific configuration file:
|
||||
|
||||
> [!NOTE]
|
||||
> The following example cmdlets use this example file path for its package:
|
||||
>
|
||||
> * C:\\Packages\\Contoso\\MyApp.appv.
|
||||
>
|
||||
> If your package file uses a different file path than the example, feel free to replace it as needed.
|
||||
|
||||
1. Enter the following cmdlet in Windows PowerShell to add the package to the computer:
|
||||
|
||||
```PowerShell
|
||||
Add-AppVClientPackage C:\Packages\Contoso\MyApp.appv
|
||||
```
|
||||
2. Enter the following cmdlet to publish the package to the user and specify the updated the dynamic user configuration file:
|
||||
|
||||
```PowerShell
|
||||
Publish-AppVClientPackage $pkg -DynamicUserConfigurationPath C:\Packages\Contoso\config.xml
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
* [Operations for App-V](appv-operations.md)
|
||||
@ -1,103 +0,0 @@
|
||||
---
|
||||
title: Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10/11)
|
||||
description: How to automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer).
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Sequencing multiple apps at the same time requires you to install and start Microsoft Application Virtualization Sequencer (App-V Sequencer), and to install the necessary apps to collect any changes made to the operating system during the installation and building of the App-V package.
|
||||
|
||||
Starting with Windows 10 version 1703, running the App-V Sequencer automatically captures and stores your customizations as an App-V project template (.appvt) file. If you want to make changes to this package later, your customizations will be automatically loaded from this template file. This automatic customization load is applicable to all of the sequencing scenarios:
|
||||
|
||||
- Using the **New-BatchAppVSequencerPackages** cmdlet
|
||||
- Using the App-V Sequencer interface
|
||||
- Using the **New-AppVSequencerPackage** cmdlet
|
||||
|
||||
>[!NOTE]
|
||||
>If you're trying to update multiple apps at the same time, see [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md).
|
||||
|
||||
### Sequence multiple apps with a PowerShell cmdlet
|
||||
|
||||
Sequencing multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of sequencing. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations.
|
||||
|
||||
#### Create your ConfigFile for use by the PowerShell cmdlet
|
||||
|
||||
1. Determine the apps that need to be included in your App-V sequencing package, and then open a text editor, such as Notepad.
|
||||
|
||||
2. Add the following required XML info for each app:
|
||||
|
||||
- ```<AppName>```. The name of the app you're adding to the package.
|
||||
- ```<InstallerFolder>```. The file path to the folder with the app installer.
|
||||
- ```<Installer>```. The file name for the app executable. This file will typically be an .exe or .msi file.
|
||||
- ```<InstallerOptions>```. The command-line options required for the app installation.
|
||||
- ```<TimeoutInMinutes>```. The maximum amount of time, in minutes, that the cmdlet should wait for sequencing to complete. You can enter a different value for each app, based on the size and complexity of the app itself.
|
||||
- ```<Cmdlet>```. Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based sequencing, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps.
|
||||
- ```<Enabled>```. Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them.
|
||||
|
||||
**Example:**
|
||||
|
||||
```XML
|
||||
<?xml version="1.0"?>
|
||||
<Applications>
|
||||
<Application>
|
||||
<AppName>Skype for Windows</AppName>
|
||||
<InstallerFolder>D:\Install\New\SkypeforWindows</InstallerFolder>
|
||||
<Installer>SkypeSetup.exe</Installer>
|
||||
<InstallerOptions>/S</InstallerOptions>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>True</Cmdlet>
|
||||
<Enabled>True</Enabled>
|
||||
</Application>
|
||||
<Application>
|
||||
<AppName>Power BI</AppName>
|
||||
<InstallerFolder>D:\Install\New\MicrosoftPowerBI</InstallerFolder>
|
||||
<Installer>PBIDesktop.msi</Installer>
|
||||
<InstallerOptions>/S</InstallerOptions>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>True</Cmdlet>
|
||||
<Enabled>True</Enabled>
|
||||
</Application>
|
||||
</Applications>
|
||||
</xml>
|
||||
```
|
||||
3. Save your completed file, using the name **ConfigFile**.
|
||||
|
||||
#### Start the App-V Sequencer interface and app installation process
|
||||
|
||||
Open PowerShell as an admin on the Host computer and run the following commands to start the batch sequencing:
|
||||
|
||||
```PowerShell
|
||||
New-BatchAppVSequencerPackages –ConfigFile <path_to_configfile> –VMName <name_of_vm> -OutputPath <path_to_your_output>
|
||||
```
|
||||
|
||||
Where ```<name_of_vm>``` is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch sequencing, and ```<path_to_your_output>``` is the full path to where the sequenced packages should be copied.
|
||||
|
||||
The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and sequencing of the app begins from the command-line. After the sequencing and package creation for the first app on the VM is completed, the package is copied from the VM to the Host computer, specified in the *OutputPath* parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off.
|
||||
|
||||
### Review the log files
|
||||
|
||||
There are three types of log files that occur when you sequence multiple apps at the same time:
|
||||
|
||||
- **New-BatchAppVSequencerPackages-<*time_stamp*>.txt**. Located in the %temp%\AutoSequencer\Logs directory. This log contains info about the sequencing activities for each app, such as "Copying installer to VM," "Scheduling sequencing task," and so on. Additionally, if an app times out, this log contains the failure along with the checkpoint for troubleshooting the problem.
|
||||
- **New-BatchAppVSequencerPackages-report-<*time_stamp*>.txt**. Located in the **OutputPath** folder you specified earlier. This log contains info about the connections made to the VM, showing if there were any failures. Additionally, it briefly includes success or failure info for all of the apps.
|
||||
- **Log.txt file**. Located in the **Output Package** folder. This file contains all code included in the NewAppVSequencerPackage cmdlet, including the allowed parameters.
|
||||
|
||||
### Related articles
|
||||
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
- [Learn about Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server)
|
||||
- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
|
||||
- [Manually sequence a single app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
|
||||
- [Automatically clean up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
|
||||
@ -1,157 +0,0 @@
|
||||
---
|
||||
title: Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10/11)
|
||||
description: How to automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer).
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Updating multiple apps at the same time follows a similar process to the one used for [automatically sequencing multiple apps at the same time](appv-auto-batch-sequencing.md). However, when updating, you'll also have to pass your previously created app package files to the App-V Sequencer cmdlet.
|
||||
|
||||
Starting with Windows 10 version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
|
||||
|
||||
>[!NOTE]
|
||||
>If you're trying to sequence multiple apps at the same time, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md).
|
||||
|
||||
## Update multiple apps with a PowerShell cmdlet
|
||||
|
||||
Updating multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of updating. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations.
|
||||
|
||||
### Create your ConfigFile for use by the PowerShell cmdlet
|
||||
|
||||
1. Determine the apps that need to be included in your app package, and then open a text editor, such as Notepad.
|
||||
|
||||
2. Add the following XML info for each app:
|
||||
|
||||
- ```<AppName>```. The name of the app you're adding to the package.
|
||||
- ```<InstallerFolder>```. The file path to the folder with the app installer.
|
||||
- ```<Installer>```. The file name for the app executable. This file will typically be an .exe or .msi file.
|
||||
- ```<InstallerOptions>```. The command-line options required for the app installation.
|
||||
- ```<Package>```. The file path to the location of your App-V packages. These packages were created when you sequenced your apps.
|
||||
- ```<TimeoutInMinutes>```. The maximum amount of time, in minutes, that the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself.
|
||||
- ```<Cmdlet>```. Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based updating, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps.
|
||||
- ```<Enabled>```. Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them.
|
||||
|
||||
**Example:**
|
||||
```XML
|
||||
<?xml version="1.0"?>
|
||||
<Applications>
|
||||
<Application>
|
||||
<AppName>Skype for Windows Update</AppName>
|
||||
<InstallerFolder>D:\Install\Update\SkypeforWindows</InstallerFolder>
|
||||
<Installer>SkypeSetup.exe</Installer>
|
||||
<InstallerOptions>/S</InstallerOptions>
|
||||
<Package>C:\App-V_Package\Microsoft_Apps\skypeupdate.appv</Package>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>true</Cmdlet>
|
||||
<Enabled>true</Enabled>
|
||||
</Application>
|
||||
<Application>
|
||||
<AppName>Microsoft Power BI Update</AppName>
|
||||
<InstallerFolder>D:\Install\Update\PowerBI</InstallerFolder>
|
||||
<Installer>PBIDesktop.msi</Installer>
|
||||
<InstallerOptions>/S</InstallerOptions>
|
||||
<Package>C:\App-V_Package\MS_Apps\powerbiupdate.appv</Package>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>true</Cmdlet>
|
||||
<Enabled>true</Enabled>
|
||||
</Application>
|
||||
</Applications>
|
||||
```
|
||||
|
||||
3. Save your completed file under the name **ConfigFile**.
|
||||
|
||||
### Start the App-V Sequencer interface and app installation process
|
||||
|
||||
- Open PowerShell as an admin on the Host computer and run the following commands to start the batch updating:
|
||||
|
||||
```PowerShell
|
||||
New-BatchAppVSequencerPackages –ConfigFile <path_to_configfile> –VMName <name_of_vm> -OutputPath <path_to_your_output>
|
||||
```
|
||||
Where ```<name_of_vm>``` is the name of the virtual machine (VM) with the App-V Sequencer installed that you'll run the batch updating on, and ```<path_to_your_output>``` is the full path to where the updated packages should be copied.
|
||||
|
||||
The cmdlet creates a "clean" checkpoint on the VM. After the checkpoint is created, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM. This copy-operation opens a new session of the VM (through VMConnect), allowing app updates to begin from the command-line. After the update and package creation for the first app on the VM is completed, the package is copied from the VM to the Host computer, specified in the OutputPath parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off.
|
||||
|
||||
## Update multiple apps with the App-V Sequencer interface
|
||||
|
||||
Updating multiple apps at the same time requires that you create a **ConfigFile** to collect all of the info related to each round of updating. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM.
|
||||
|
||||
### Create your ConfigFile for use by the App-V Sequencer interface
|
||||
|
||||
1. Determine the apps that need to be updated and then open a text editor, such as Notepad.
|
||||
|
||||
2. Add the following XML info for each app:
|
||||
|
||||
- ```<AppName>```. The name of the app you're adding to the package.
|
||||
- ```<InstallerFolder>```. The file path to the folder with the app installer.
|
||||
- ```<Installer>```. The file name for the app executable. This file will typically be an .exe or .msi file.
|
||||
- ```<Package>```. The file path to the location of your App-V packages. These packages were created when you sequenced your apps.
|
||||
- ```<TimeoutInMinutes>```. The maximum amount of time, in minutes, the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself.
|
||||
- ```<Cmdlet>```. Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based updating, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps.
|
||||
- ```<Enabled>```. Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them.
|
||||
|
||||
**Example:**
|
||||
|
||||
```XML
|
||||
<?xml version="1.0"?>
|
||||
<Applications>
|
||||
<Application>
|
||||
<AppName>Skype for Windows Update</AppName>
|
||||
<InstallerFolder>D:\Install\Update\SkypeforWindows</InstallerFolder>
|
||||
<Installer>SkypeSetup.exe</Installer>
|
||||
<InstallerOptions>/S</InstallerOptions>
|
||||
<Package>C:\App-V_Package\Microsoft_Apps\skypeupdate.appv</Package>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>false</Cmdlet>
|
||||
<Enabled>true</Enabled>
|
||||
</Application>
|
||||
<Application>
|
||||
<AppName>Microsoft Power BI Update</AppName>
|
||||
<InstallerFolder>D:\Install\Update\PowerBI</InstallerFolder>
|
||||
<Installer>PBIDesktop.msi</Installer>
|
||||
<InstallerOptions>/S</InstallerOptions>
|
||||
<Package>C:\App-V_Package\MS_Apps\powerbiupdate.appv</Package>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>false</Cmdlet>
|
||||
<Enabled>true</Enabled>
|
||||
</Application>
|
||||
</Applications>
|
||||
```
|
||||
|
||||
### Start the App-V Sequencer interface and app installation process
|
||||
|
||||
- Open PowerShell as an admin on the Host computer and run the following commands to start the batch updating:
|
||||
|
||||
```PowerShell
|
||||
New-BatchAppVSequencerPackages –ConfigFile <path_to_configfile> –VMName <name_of_vm> -OutputPath <path_to_your_output>
|
||||
```
|
||||
Where ```<name_of_vm>``` is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch updating, and ```<path_to_your_output>``` is the full path to where the updated packages should be copied.
|
||||
|
||||
This cmdlet creates a "clean" checkpoint on the VM. After the checkpoint is created, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM. This opens a new session of the VM (through VMConnect) and app updating begins from the command-line. After the updating and package creation for the first app on the VM is completed, the package is copied from the VM to the Host computer specified in the *OutputPath* parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted to a "clean" checkpoint and turned off.
|
||||
|
||||
### Review the log files
|
||||
|
||||
There are three types of log files that occur when you sequence multiple apps at the same time:
|
||||
|
||||
- **New-BatchAppVSequencerPackages-<*time_stamp*>.txt**. Located in the %temp%\AutoSequencer\Logs directory. This log contains info about updating activities for each app, such as "Copying installer to VM," "Scheduling updating task," and so on. Additionally, if an app times out, this log contains the failure along with the checkpoint for troubleshooting the problem.
|
||||
- **New-BatchAppVSequencerPackages-report-<*time_stamp*>.txt**. Located in the **OutputPath** folder you specified earlier. This log contains info about the connections made to the VM, showing if there were any failures. Additionally, it briefly includes success or failure info for all of the apps.
|
||||
- **Log.txt file**. Located in the **Output Package** folder. This file contains all code included in the **NewAppVSequencerPackage** cmdlet, including the allowed parameters.
|
||||
|
||||
### Related articles
|
||||
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
- [Learn about Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server)
|
||||
- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
|
||||
- [Manually sequence a single app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
|
||||
- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
|
||||
@ -1,65 +0,0 @@
|
||||
---
|
||||
title: Auto-remove unpublished packages on App-V client (Windows 10/11)
|
||||
description: How to automatically clean up any unpublished packages on your App-V client devices.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/15/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# Automatically clean up unpublished packages on the App-V client
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
If you wanted to free up additional storage space in previous versions of App-V, you would have had to manually remove your unpublished packages from your client devices. Starting with Windows 10 version 1703, use PowerShell or Group Policy settings to automatically clean up your unpublished packages after restarting your device.
|
||||
|
||||
## Clean up with PowerShell cmdlets
|
||||
|
||||
You can enter PowerShell cmdlets to turn on the **AutoCleanupEnabled** setting, which will automatically clean up your unpublished App-V packages from your App-V client devices.
|
||||
|
||||
### Turn on the AutoCleanupEnabled option
|
||||
|
||||
1. Open PowerShell as an admin and enter the following cmdlet to turn on the automatic package cleanup functionality:
|
||||
|
||||
```PowerShell
|
||||
Set-AppvClientConfiguration -AutoCleanupEnabled 1
|
||||
```
|
||||
|
||||
After running the cmdlet, you should see the following info on the PowerShell screen:
|
||||
|
||||
|Name|Value|SetbyGroupPolicy|
|
||||
|---|---|---|
|
||||
|AutoCleanupEnabled|1|False|
|
||||
|
||||
1. Run the following cmdlet to check if the configuration has the cleanup setting turned on.
|
||||
|
||||
```PowerShell
|
||||
Get-AppvClientConfiguration
|
||||
```
|
||||
If the **AutoCleanupEnabled** option shows a value of **1** in the configuration list, that means the setting is turned on.
|
||||
|
||||
## Clean up with Group Policy settings
|
||||
|
||||
Using Group Policy, you can turn on the **Enable automatic cleanup of unused App-V packages** setting to automatically clean up your unpublished App-V packages from your App-V client devices.
|
||||
|
||||
### Turn on the Enable automatic cleanup of unused App-V packages setting
|
||||
|
||||
1. Open your Group Policy editor and select the **Administrative Templates\System\App-V\PackageManagement\Enable automatic cleanup of unused App-V packages** setting.
|
||||
|
||||
2. Select **Enabled**, then select **OK**.
|
||||
|
||||
After your Group Policy updates and you reset the client, the setting will clean up any unpublished App-V packages on the App-V client.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
- [Deploying App-V for Windows client](appv-deploying-appv.md)
|
||||
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
|
||||
@ -1,129 +0,0 @@
|
||||
---
|
||||
title: Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10/11)
|
||||
description: How to automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) PowerShell cmdlet or the user interface.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Previous versions of the App-V Sequencer have required you to manually create your sequencing environment. Starting with Windows 10 version 1703, the `New-AppVSequencerVM` and `Connect-AppvSequencerVM` Windows PowerShell cmdlets are available, which automatically create your sequencing environment for you, including provisioning your virtual machine.
|
||||
|
||||
## Automatic VM provisioning of the sequencing environment
|
||||
|
||||
You have two options for provisioning a VM for auto-sequencing:
|
||||
|
||||
1. Using a Virtual Hard Disk (VHD)
|
||||
2. Updating an existing VM
|
||||
|
||||
You can only choose one option.
|
||||
|
||||
>[!NOTE]
|
||||
>We have reduced the number of environmental checks performed by the App-V Sequencer, narrowing down the list of apps that need to be disabled or turned off for a clean sequencing experience. We've also suppressed antivirus and other similar app warnings.
|
||||
|
||||
### Provision a new VM with a VHD file
|
||||
|
||||
Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer.
|
||||
|
||||
#### Create a VHD file
|
||||
|
||||
For this process to work, you must have a base operating system available as a VHD image file, we recommend using the [Convert-WindowsImage.ps1](https://www.powershellgallery.com/packages/Convert-WindowsImage/10.0) command-line tool.
|
||||
|
||||
#### Create a VHD file with the Convert-WindowsImage command-line tool
|
||||
|
||||
1. Open PowerShell as an admin and run the **Convert-WindowsImage** tool, using the following commands:
|
||||
|
||||
```ps1
|
||||
Convert-WindowsImage -SourcePath "<path_to_iso_image>" -VHDFormat "VHD" -VHDPartitionStyle "MBR"
|
||||
```
|
||||
Where ```<path_to_iso_image>``` is the full path to your ISO image.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You must specify the *VHDPartitionStyle* as **MBR**. If you use the default value, **GPT**, will cause a boot failure in your VHD image.
|
||||
|
||||
#### Provision your VM with your VHD file
|
||||
|
||||
After you have a VHD file, you must provision your VM for auto-sequencing.
|
||||
|
||||
1. On the Host device, install the Windows client and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server).
|
||||
3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters:
|
||||
|
||||
```PowerShell
|
||||
New-AppVSequencerVM -VMName "<name_of_new_vm>" -ADKPath "<path_to_adk_install_folder>" -VHDPath "<path_to_vhd_file>" -VMMemory "<vm_memory_size>" -VMSwitch "<name_of_network_switch>"
|
||||
```
|
||||
|
||||
This command creates a new Hyper-V VM file using the provided VHD file and also creates a "clean" checkpoint, from where all sequencing and updating will start.
|
||||
|
||||
### Provision an existing VM for auto-sequencing
|
||||
|
||||
If your apps require custom prerequisites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM.
|
||||
|
||||
#### Connect to your existing VM
|
||||
|
||||
- Open PowerShell as an admin and run the following commands on your existing VM:
|
||||
|
||||
- **Set the network category of your connection profile on the VM to _Private_:**
|
||||
|
||||
```PowerShell
|
||||
Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private
|
||||
```
|
||||
|
||||
- **Enable firewall rules for _Remote Desktop_ and _Windows Remote Management_:**
|
||||
|
||||
```PowerShell
|
||||
Enable-NetFirewallRule -DisplayGroup “Remote Desktop”
|
||||
Enable-NetFirewallRule -DisplayGroup “Windows Remote Management”
|
||||
```
|
||||
|
||||
- **Set the VM to receive remote commands without a confirmation prompt:**
|
||||
|
||||
```PowerShell
|
||||
Enable-PSRemoting –Force
|
||||
```
|
||||
|
||||
#### Provision an existing VM
|
||||
|
||||
1. On the Host device, install the Windows client and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
2. Open PowerShell as an admin and run the **Connect-AppvSequencerVM** cmdlet, using the following parameters:
|
||||
|
||||
```ps1
|
||||
Connect-AppvSequencerVM -VMName "<name_of_vm>"
|
||||
```
|
||||
|
||||
Where ```<name_of_vm>``` is the name of the VM as shown in the Hyper-V Manager tool.
|
||||
|
||||
This command connects to an existing Hyper-V VM using the provided VM name for auto-sequencing.
|
||||
|
||||
### Review the provisioning log files
|
||||
|
||||
The two types of provisioning log files, located at %temp%\AutoSequencer\Logs, are:
|
||||
|
||||
- **New-AppVSequencerVM-<time_stamp>.txt**. Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on.
|
||||
- **Connect-AppvSequencerVM-report-<time_stamp>.txt**. Includes info about the connections made to the VM, showing whether there were any failures.
|
||||
|
||||
### Next steps
|
||||
|
||||
After provisioning your sequencing environment, you must sequence your apps, either as a group or individually. For more info about sequencing your apps, see the following articles
|
||||
|
||||
- [Manually sequence a single new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
|
||||
- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
|
||||
|
||||
After you sequence your packages, you can automatically clean up any unpublished packages on the App-V client. To learn more, see [Automatically clean up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md).
|
||||
|
||||
### Related articles
|
||||
|
||||
- [Download the **Convert-WindowsImage** tool](https://www.powershellgallery.com/packages/Convert-WindowsImage/10.0)
|
||||
- [Download the Windows ADK](/windows-hardware/get-started/adk-install)
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
- [Learn about Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server)
|
||||
@ -1,34 +0,0 @@
|
||||
---
|
||||
title: Available Mobile Device Management (MDM) settings for App-V (Windows 10/11)
|
||||
description: Learn the available Mobile Device Management (MDM) settings you can use to configure App-V on Windows 10.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/15/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# Available Mobile Device Management (MDM) settings for App-V
|
||||
|
||||
Starting with Windows 10 version 1703, you can configure, deploy, and manage your App-V apps with the following Mobile Device Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](/windows/client-management/mdm/enterpriseappvmanagement-csp) page.
|
||||
|
||||
|Policy name|Supported versions|URI full path|Data type|Values|
|
||||
|---|---|---|---|---|
|
||||
|Name|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/Name|String|Read-only data, provided by your App-V packages.|
|
||||
|Version|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/Version|String|Read-only data, provided by your App-V packages.|
|
||||
|Publisher|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/Publisher|String|Read-only data, provided by your App-V packages.|
|
||||
|InstallLocation|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/InstallLocation|String|Read-only data, provided by your App-V packages.|
|
||||
|InstallDate|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/InstallDate|String|Read-only data, provided by your App-V packages.|
|
||||
|Users|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/Users|String|Read-only data, provided by your App-V packages.|
|
||||
|AppVPackageID|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/AppVPackageID|String|Read-only data, provided by your App-V packages.|
|
||||
|AppVVersionID|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/AppVVersionID|String|Read-only data, provided by your App-V packages.|
|
||||
|AppVPackageUri|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/AppVPackageUri|String|Read-only data, provided by your App-V packages.|
|
||||
|LastError|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVPublishing/LastSync/LastError|String|Read-only data, provided by your App-V packages.|
|
||||
|LastErrorDescription|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/LastErrorDescription|String|- **0**: No errors returned during publish.<br>- **1**: Unpublish groups failed during publish.<br>- **2**: Publish no-group packages failed during publish.<br>- **3**: Publish group packages failed during publish.<br>- **4**: Unpublish packages failed during publish.<br>- **5**: New policy write failed during publish.<br>- **6**: Multiple non-fatal errors occurred during publish.|
|
||||
|SyncStatusDescription|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/SyncStatusDescription|String|- **0**: App-V publishing is idle.<br>- **1**: App-V connection groups publish in progress.<br>- **2**: App-V packages (non-connection group) publish in progress.<br>- **3**: App-V packages (connection group) publish in progress.<br>- **4**: App-V packages unpublish in progress.|
|
||||
|SyncProgress|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/SyncProgress|String|- **0**: App-V Sync is idle.<br>- **1**: App-V Sync is initializing.<br>- **2**: App-V Sync is in progress.<br>- **3**: App-V Sync is complete.<br>- **4**: App-V Sync requires device reboot.|
|
||||
|PublishXML|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVPublishing/Sync/PublishXML|String|Custom value, entered by admin.|
|
||||
|Policy|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVDynamicPolicy/configurationid/Policy|String|Custom value, entered by admin.|
|
||||
@ -1,198 +0,0 @@
|
||||
---
|
||||
title: App-V Capacity Planning (Windows 10/11)
|
||||
description: Use these recommendations as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V infrastructure.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# App-V Capacity Planning
|
||||
|
||||
>Applies to: Windows Server 2016
|
||||
|
||||
The following recommendations can be used as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V infrastructure.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Use the information in this section only as a general guide for planning your App-V deployment. Your system capacity requirements will depend on the specific details of your hardware and application environment. Additionally, the performance numbers displayed in this document are examples and your results may vary.
|
||||
|
||||
## Determine the project scope
|
||||
|
||||
Before you design the App-V infrastructure, determining which applications will be available virtually, and also identify the target users and their locations. This information will determine what type of App-V infrastructure your project should implement. You should base your decisions about your project's scope on your organization's specific needs.
|
||||
|
||||
|Task|More information|
|
||||
|----|----------------|
|
||||
|Determine application scope|The App-V infrastructure can be set up in different ways depending on which applications you want to virtualize. This customization in set up means your first task is to define which applications you want to virtualize.|
|
||||
|Determine location scope|"Location scope" refers to the physical locations where you plan to run the virtualized applications (for example, enterprise-wide or a specific geographic location). It can also refer to the user population that will run the virtual applications (for example, a single department). You should obtain a network map that includes the connection paths, the available bandwidth for each location, the number of users using virtualized applications, and the WAN link speed.|
|
||||
|
||||
## Determine which App-V infrastructure is required
|
||||
|
||||
You can also manage your App-V environment using an electronic software distribution (ESD) solution such as Microsoft Systems Center Configuration Manager. For more information, see [How to deploy App-V packages using electronic software distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
* **Standalone model**—The standalone model allows virtual applications to be Windows Installer-enabled for distribution without streaming. App-V in Standalone mode only needs the sequencer and the client; no extra components are required. Applications are prepared for virtualization using a process called sequencing. For more information, see [Planning for the App-V Sequencer and Client deployment](appv-planning-for-sequencer-and-client-deployment.md). The standalone model is recommended for the following scenarios:
|
||||
|
||||
* When there are disconnected remote users who can't connect to the App-V infrastructure.
|
||||
* When you're running a software management system, such as Configuration Manager.
|
||||
* When network bandwidth limitations inhibit electronic software distribution.
|
||||
* **Full infrastructure model**—The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V full infrastructure model consists of one or more App-V management servers that can be used to publish applications to all clients. Publishing places the virtual application icons and shortcuts on the target computer. It can also stream applications to local users. For more information about how to install the management server, see [Planning for App-V Server deployment](appv-planning-for-appv-server-deployment.md). The full infrastructure model is recommended for the following scenarios:
|
||||
|
||||
* When you want to use the Management Server to publish the application to target computers.
|
||||
* For rapid provisioning of applications to target computers.
|
||||
* When you want to use App-V reporting.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The App-V full infrastructure model requires Microsoft SQL Server to store configuration data. For more information, see [App-V supported configurations](appv-supported-configurations.md).
|
||||
|
||||
## End-to-end server sizing guidance
|
||||
|
||||
The following section describes end-to-end App-V sizing and planning. For more specific information, refer to the subsequent sections.
|
||||
|
||||
>[!NOTE]
|
||||
>Round trip response time on the client is the time taken by the computer running the App-V client to receive a successful notification from the publishing server. Round trip response time on the publishing server is the time taken by the computer running the publishing server to receive a successful package metadata update from the management server.
|
||||
|
||||
* 20,000 clients can target a single publishing server to obtain the package refreshes in an acceptable round trip time (<3 seconds).
|
||||
* A single management server can support up to 50 publishing servers for package metadata refreshes in an acceptable round trip time (<5 seconds).
|
||||
|
||||
## App-V Management Server capacity planning recommendations
|
||||
|
||||
The App-V publishing servers require the management server for package refresh requests and package refresh responses. The management server then sends the information to the management database to retrieve information. For more information about App-V management server supported configurations, see [App-V supported configurations](appv-supported-configurations.md).
|
||||
|
||||
>[!NOTE]
|
||||
>The default refresh time on the App-V publishing server is ten minutes.
|
||||
|
||||
When multiple simultaneous publishing servers contact a single management server for package metadata refreshes, the following three factors will influence the publishing server's round-trip response time:
|
||||
|
||||
1. The number of publishing servers making simultaneous requests.
|
||||
2. The number of connection groups configured on the management server.
|
||||
3. The number of access groups configured on the management server.
|
||||
|
||||
The following table describes each factor that impacts round-trip time in more detail.
|
||||
|
||||
>[!NOTE]
|
||||
>Round trip response time is the time taken by the computer running the App-V publishing server to receive a successful package metadata update from the management server.
|
||||
|
||||
|Factors impacting round-trip response time|Description|
|
||||
|------------------------------------------|-----------|
|
||||
|The number of publishing servers simultaneously requesting package metadata refreshes.|A single management server can respond to up to 320 publishing servers simultaneously requesting publishing metadata. For example, in a case with 30 publishing servers simultaneously requesting publishing metadata, the round-trip response time is about 40 seconds, while for less than 50 servers it's less than 5 seconds. From 50 to 320 publishing servers, response team increases linearly (approximately 2×).|
|
||||
|The number of connection groups configured on the management server.|For up to 100 connection groups, there's no significant change in the round-trip response time on the publishing server. For 100–400 connection groups, there's a minor linear increase in the round-trip response time.|
|
||||
|The number of access groups configured on the management server.|For up to 40 access groups, there's a linear (approximately 3×) increase in the round-trip response time on the publishing server.|
|
||||
|
||||
The following table displays sample values for each of the previous factors. In each variation, 120 packages are refreshed from the App-V management server.
|
||||
|
||||
|Scenario|Variation|Number of connection groups|Number of access groups|Number of publishing servers|Network connection type|Round-trip response time (seconds)|Management server CPU utilization|
|
||||
|---|---|---|---|---|---|---|---|
|
||||
|Publishing servers contact management server for publishing metadata at same time|Number of publishing servers.|0<br>0<br>0<br>0<br>0<br>0|1<br>1<br>1<br>1<br>1<br>1|50<br>100<br>200<br>300<br>315<br>320|LAN|5<br>10<br>19<br>32<br>30<br>37|17<br>17<br>17<br>15<br>17<br>15|
|
||||
|Publishing metadata contains connection groups|Number of connection groups|10<br>20<br>100<br>150<br>300<br>400|1<br>1<br>1<br>1<br>1<br>1|100<br>100<br>100<br>100<br>100<br>100|LAN|10<br>11<br>11<br>16<br>22<br>25|17<br>19<br>22<br>19<br>20<br>20|
|
||||
|Publishing metadata contains access groups|Number of access groups|0<br>0<br>0<br>0|1<br>10<br>20<br>40|100<br>100<br>100<br>100|LAN|10<br>43<br>153<br>535|17<br>26<br>24<br>24|
|
||||
|
||||
The CPU utilization of the computer running the management server is around 25% irrespective of the number of publishing servers targeting it. The Microsoft SQL Server database transactions/sec, batch requests/sec and user connections are identical irrespective of the number of publishing servers. For example, transactions/sec is approximately 30, batch requests approximately 200, and user connects approximately six.
|
||||
|
||||
Through a geographically distributed deployment, where the management server and publishing servers utilize a slow link network between them, the round-trip response time on the publishing servers is within acceptable time limits (<5 seconds), even for 100 simultaneous requests on a single management server.
|
||||
|
||||
|Scenario|Variation|Number of connection groups|Number of access groups|Number of publishing servers|Network connection type|Round-trip response time (seconds)|Management server CPU utilization (in %)|
|
||||
|---|---|---|---|---|---|---|---|
|
||||
|Network connection between the publishing server and management server|1.5 Mbps Slow link Network|0<br>0|1<br>1|50<br>100|1.5 Mbps Cable DSL|4<br>5|1<br>2|
|
||||
|Network connection between the publishing server and management server|LAN/WiFi Network|0<br>0|1<br>1|100<br>200|WiFi|11<br>20|15<br>17|
|
||||
|
||||
Whether the management server and publishing servers are connected over a slow link network, or a high speed network, the management server can handle approximately 15,000 package refresh requests in 30 minutes.
|
||||
|
||||
## App-V Reporting Server capacity planning recommendations
|
||||
|
||||
App-V clients send reporting data to the reporting server. The reporting server then records the information in the Microsoft SQL Server database and returns a successful notification back to the computer running App-V client. For more information about the App-V Reporting Server's supported configurations, see [App-V supported configurations](appv-supported-configurations.md).
|
||||
|
||||
>[!NOTE]
|
||||
>Round-trip response time is the time taken by the computer running the App-V client to send the reporting information to the reporting server and receive a successful notification from the reporting server.
|
||||
|
||||
|Scenario|Summary|
|
||||
|---|---|
|
||||
|Multiple App-V clients send reporting information to the reporting server simultaneously.|Round-trip response time from the reporting server is 2.6 seconds for 500 clients. Round-trip response time from the reporting server is 5.65 seconds for 1000 clients. Round-trip response time increases linearly depending on number of clients.|
|
||||
|Requests per second processed by the reporting server.|A single reporting server and a single database can process a maximum of 139 requests per second. The average is 121 requests/second. With the help of two reporting servers that report to the same Microsoft SQL Server database, the average requests/second, like a single reporting server, is about 127, with a max of 278 requests/second. A single reporting server can process 500 concurrent/active connections. A single reporting server can process a maximum 1,500 concurrent connections.|
|
||||
|Reporting database.|Lock contention on the computer running Microsoft SQL Server is the limiting factor for requests/second. Throughput and response time are independent of database size.|
|
||||
|
||||
### Calculating random delay
|
||||
|
||||
The random delay specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between **0** and **ReportingRandomDelay** and will wait the specified duration before sending data.
|
||||
|
||||
*Random delay = 4 × number of clients/average requests per second*.
|
||||
|
||||
Example: Random delay for 500 clients with 120 requests per second is *4 × 500/120 = about 17 minutes*.
|
||||
|
||||
## App-V publishing server capacity planning recommendations
|
||||
|
||||
Computers running the App-V client connect to the App-V publishing server to send a publishing refresh request and receive a response. Round trip response time is measured on the computer running the App-V client, while processor time is measured on the publishing server. For more information about App-V Publishing Server supported configurations, see [App-V supported configurations](appv-supported-configurations.md).
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The following list displays the main factors to consider when setting up the App-V publishing server:
|
||||
> * The number of clients connecting simultaneously to a single publishing server.
|
||||
> * The number of packages in each refresh.
|
||||
> * The available network bandwidth in your environment between the client and the App-V publishing server.
|
||||
|
||||
|Scenario|Summary|
|
||||
|---|---|
|
||||
|Multiple App-V clients connect to a single publishing server simultaneously.|A publishing server running dual core processors can respond to at most 5000 clients requesting a refresh simultaneously. For 5,000–10,000 clients, the publishing server requires a minimum quad core. For 10,000–20,000 clients, the publishing server should have dual quad cores for more efficient response times. A publishing server with a quad core can refresh up to 10,000 packages within three seconds. (Supports 10,000 simultaneous clients.)|
|
||||
|Number of packages in each refresh.|Increasing number of packages will increase response time by about 40% (up to 1,000 packages).|
|
||||
|Network between the App-V client and the publishing server.|Across a slow network (1.5-Mbps bandwidth), there's a 97% increase in response time compared to LAN (up to 1,000 users).|
|
||||
|
||||
>[!NOTE]
|
||||
>The publishing server CPU usage is always high during the time interval when it must process simultaneous requests (>90% in most cases). The publishing server can handle about 1,500 client requests in one second.
|
||||
|
||||
|Scenario|Variation|Number of App-V clients|Number of packages|Processor configuration on publishing server|Network connection type|App-V client round-trip time (in seconds)|Publishing server CPU utilization (in %)|
|
||||
|---|---|---|---|---|---|---|---|
|
||||
|App-V client sends publishing refresh request and receives response, each request containing 120 packages|Number of clients|100<br>1,000<br>5,000<br>10,000|120<br>120<br>120<br>120|Dual Core<br>Dual Core<br>Quad Core<br>Quad Core|LAN|1<br>2<br>2<br>3|100<br>99<br>89<br>77|
|
||||
|Multiple packages in each refresh.|Number of packages|1,000<br>1,000|500<br>1,000|Quad Core|LAN|2<br>3|92<br>91|
|
||||
|Network between client and publishing server.|1.5 Mbps Slow link network|100<br>500<br>1,000|120<br>120<br>120|Quad Core|1.5-Mbps intra-continental network|3<br>10 (0.2% failure rate)<br>7 (1% failure rate)||
|
||||
|
||||
## App-V streaming capacity planning recommendations
|
||||
|
||||
Computers running the App-V client stream the virtual application package from the streaming server. Round trip response time is measured on the computer running the App-V client, and is the time taken to stream the entire package.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The following list identifies the main factors to consider when setting up the App-V streaming server:
|
||||
> * The number of clients streaming application packages simultaneously from a single streaming server.
|
||||
> * The size of the package being streamed.
|
||||
> * The available network bandwidth in your environment between the client and the streaming server.
|
||||
|
||||
|Scenario|Summary|
|
||||
|---|---|
|
||||
|Multiple App-V clients stream applications from a single streaming server simultaneously.|If the number of clients simultaneously streaming from the same server increases, there's a linear relationship with the package download/streaming time.|
|
||||
|Size of the package being streamed.|The package size has a significant impact on the streaming/download time only for larger packages with a size of about 1 GB. For package sizes ranging from 3 MB to 100 MB, the streaming time ranges from 20 seconds to 100 seconds, with 100 simultaneous clients.|
|
||||
|Network between the App-V client and the streaming server.|Across a slow network (1.5-Mbps bandwidth), there's a 70–80% increase in response time compared to LAN (up to 100 users).|
|
||||
|
||||
The following table displays sample values for each of the factors in the previous list:
|
||||
|
||||
|Scenario|Variation|Number of App-V clients|Size of each package|Network connection type|Round-trip time on the App-V client (in seconds)|
|
||||
|---|---|---|---|---|---|
|
||||
|Multiple App-V clients streaming virtual application packages from a streaming server.|Number of clients.|100<br>200<br>1,000<br>100<br>200<br>1,000|3.5 MB<br>3.5 MB<br>3.5 MB<br>5 MB<br>5 MB<br>5 MB|LAN|29<br>39<br>391<br>35<br>68<br>461|
|
||||
|Size of each package being streamed.|Size of each package.|100<br>200<br>100<br>200|21 MB<br>21 MB<br>109 MB<br>109 MB|LAN|33<br>83<br>100<br>160|
|
||||
|Network connection between client and App-V streaming server.|1.5 Mbps Slow link network.|100<br>100|3.5 MB<br>5 MB|1.5-Mbps intra-continental network|102<br>121|
|
||||
|
||||
Each App-V streaming server should be able to handle a minimum of 200 clients concurrently streaming virtualized applications.
|
||||
|
||||
>[!NOTE]
|
||||
>The actual time to it will take to stream is determined primarily by the number of clients streaming simultaneously, number of packages, package size, the server’s network activity, and network conditions.
|
||||
|
||||
For example, an average user can stream a 100-MB package in less than 2 minutes, when 100 simultaneous clients are streaming from the server. However, a package of size 1 GB could take up to 30 minutes. In most real-world environments, streaming demand isn't uniformly distributed, you'll need to understand the approximate peak streaming requirements present in your environment to properly size the number of required streaming servers.
|
||||
|
||||
The number of clients a streaming server can support can be increased and the peak streaming requirements reduced if you pre-cache your applications. You can also increase the number of clients a streaming server can support by using on-demand streaming delivery and stream optimized packages.
|
||||
|
||||
## Combining App-V server roles
|
||||
|
||||
Discounting scaling and fault-tolerance requirements, the minimum number of servers that a location with Active Directory connectivity needs to function is 1. This server will host the management server, management server service, and Microsoft SQL Server roles. This coverage means that you can arrange server roles in any combination you like, as they don't conflict with one another.
|
||||
|
||||
Notwithstanding scaling requirements, the minimum number of servers that a fault-tolerant implementation needs to function is four. The management server and Microsoft SQL Server roles support placement in fault-tolerant configurations. The management server service can be combined with any of the roles, but remains a single point of failure.
|
||||
|
||||
Although there are many fault-tolerance strategies and technologies you can use, not all are applicable to a given service. Additionally, if App-V roles are combined, the resulting incompatibilities could cause certain fault-tolerance options to stop working.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
* [App-V supported configurations](appv-supported-configurations.md)
|
||||
* [Planning for high availability with App-V](appv-planning-for-high-availability-with-appv.md)
|
||||
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
@ -1,114 +0,0 @@
|
||||
---
|
||||
title: About Client Configuration Settings (Windows 10/11)
|
||||
description: Learn about the App-V client configuration settings and how to use Windows PowerShell to modify the client configuration settings.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# About Client Configuration Settings
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
The Microsoft Application Virtualization (App-V) client stores its configuration in the registry. Understanding how the register's format for data works can help you better understand the client, as you can configure many client actions by changing registry entries. This topic lists the App-V client configuration settings and explains their uses. You can use Windows PowerShell to modify the client configuration settings. For more information about using Windows PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).
|
||||
|
||||
You can use Group Policy to configure App-V client settings by navigating to the **Group Policy management console** at **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
|
||||
|
||||
## App-V Client Configuration Settings: Windows PowerShell
|
||||
|
||||
The following table provides information about App-V client configuration settings that can be configured through Windows PowerShell cmdlets:
|
||||
|
||||
|
||||
| Windows PowerShell cmdlet or cmdlets,<br>**Option**<br>Type | Description | Disabled policy state keys and values |
|
||||
|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-PackageInstallationRoot**<br>String | Specifies directory where all new applications and updates will be installed. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-PackageSourceRoot**<br>String | Overrides source location for downloading package content. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-AllowHighCostLaunch**<br>True (enabled); False (Disabled state) | This setting controls whether virtualized applications are launched on Windows client machines connected by a metered network connection (for example, 4G). | 0 |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReestablishmentRetries**<br>Integer (0–99) | Specifies the number of times to retry a dropped session. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReestablishmentInterval**<br>Integer (0–3600) | Specifies the number of seconds between attempts to reestablish a dropped session. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-LocationProvider**<br>String | Specifies the CLSID for a compatible implementation of the IAppvPackageLocationProvider interface. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-CertFilterForClientSsl**<br>String | Specifies the path to a valid certificate in the certificate store. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-VerifyCertificateRevocationList**<br>True (enabled); False (Disabled state) | Verifies Server certificate revocation status before streaming with HTTPS. | 0 |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-SharedContentStoreMode**<br>True (enabled); False (Disabled state) | Specifies that streamed package contents will not be saved to the local hard disk. | 0 |
|
||||
| Set-AppvPublishingServer<br><br>**-Name**<br>String | Displays the name of publishing server. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvPublishingServer<br><br>**-URL**<br>String | Displays the URL of publishing server. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvPublishingServer<br><br>**-GlobalRefreshEnabled**<br>True (enabled); False (Disabled state) | Enables global publishing refresh (Boolean) | False |
|
||||
| Set-AppvPublishingServer<br><br>**-GlobalRefreshOnLogon**<br>True (enabled); False (Disabled state) | Triggers a global publishing refresh on sign in. (Boolean) | False |
|
||||
| Set-AppvPublishingServer<br><br>**-GlobalRefreshInterval**<br>Integer (0–744) | Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, specify 0. | 0 |
|
||||
| Set-AppvPublishingServer<br><br>**-GlobalRefreshIntervalUnit** <br>0 for hour, 1 for day | Specifies the interval unit (Hour 0–23, Day 0–31). | 1 |
|
||||
| Set-AppvPublishingServer<br><br>**-UserRefreshEnabled**<br>True (enabled); False (Disabled state) | Enables user publishing refresh (Boolean) | False |
|
||||
| Set-AppvPublishingServer<br><br>**-UserRefreshOnLogon**<br>True (enabled); False (Disabled state) | Triggers a user publishing refresh on sign in. (Boolean) Word count (with spaces): 60 | False |
|
||||
| Set-AppvPublishingServer<br><br>**-UserRefreshInterval**<br>Word count (with spaces): 85<br>Integer (0–744 Hours) | Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0. | 0 |
|
||||
| Set-AppvPublishingServer<br><br>**-UserRefreshIntervalUnit**<br>0 for hour, 1 for day | Specifies the interval unit (Hour 0–23, Day 0–31). | 1 |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-MigrationMode**<br>True (enabled state); False (Disabled state) | Migration mode allows the App-V client to modify shortcuts and FTAs for packages created by a previous version of App-V. | |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-EnablePackageScripts**<br>True (enabled); False (Disabled state) | Enables scripts defined in the package manifest of configuration files that should run. | |
|
||||
| Set-AppvClientConfiguration<br><br>**-RoamingFileExclusions**<br>String | Specifies the file paths relative to %userprofile% that don't roam with a user's profile. For example, ```/ROAMINGFILEEXCLUSIONS='desktop;my pictures'``` | |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-RoamingRegistryExclusions**<br>String | Specifies the registry paths that don't roam with a user profile. For example, ```/ROAMINGREGISTRYEXCLUSIONS=software\\classes;software\\clients``` | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-IntegrationRootUser**<br>String | Specifies the location to create symbolic links associated with the current version of a per-user published package. All virtual application extensions, such as shortcuts and file type associations, will point to this path. If you don't specify a path, symbolic links won't be used when you publish the package. For example, ```%localappdata%\\Microsoft\\AppV\\Client\\Integration```. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-IntegrationRootGlobal**<br>String | Specifies the location to create symbolic links associated with the current version of a globally published package. All virtual application extensions, such as shortcuts and file type associations, will point to this path. If you don't specify a path, symbolic links won't be used when you publish the package. For example, ```%allusersprofile%\\Microsoft\\AppV\\Client\\Integration```. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-VirtualizableExtensions**<br>String | A comma-delineated list of file name extensions that can be used to determine if a locally installed application can be run in the virtual environment. When shortcuts, FTAs, and other extension points are created during publishing, App-V will compare the file name extension to the list if the application associated with the extension point is locally installed. If the extension is located, the **RunVirtual** command-line parameter will be added, and the application will run virtually. For more information about the **RunVirtual** parameter, see [Running a locally installed application inside a virtual environment with virtualized applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md). | Policy value not written |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingEnabled**<br>True (enabled); False (Disabled state) | Returns information to a reporting server. | False |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingServerURL**<br>String | Specifies the location on the reporting server where client information is saved. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingDataCacheLimit**<br>Integer \[0–1024\] | Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. Set between 0 and 1024. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingDataBlockSize**<br>Integer \[1024 - Unlimited\] | Specifies the maximum size in bytes to transmit to the server for reporting upload requests. This limit can help avoid permanent transmission failures when the log has reached a significant size. Set between 1024 and unlimited. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingStartTime**<br>Integer (0–23) | Specifies the time to initiate the client to send data to the reporting server. You must specify a valid integer between 0–23 corresponding to the hour of the day. By default the **ReportingStartTime** will start on the current day at 10 P.M.or 22.<br>**Note** You should configure this setting to a time when computers running the App-V client are least likely to be offline. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingInterval**<br>Integer | Specifies the retry interval that the client will use to resend data to the reporting server. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingRandomDelay**<br>Integer \[0 - ReportingRandomDelay\] | Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and **ReportingRandomDelay** and will wait the specified duration before sending data. This method can help to prevent collisions on the server. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br><strong>-EnableDynamicVirtualization<br></strong>1 (Enabled), 0 (Disabled) | Enables supported Shell Extensions, Browser Helper Objects, and Active X controls to be virtualized and run with virtual applications. | |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-EnablePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Enables the publishing refresh progress bar for the computer running the App-V Client. | |
|
||||
| Sync-AppvPublishingServer<br><br>**-HidePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Hides the publishing refresh progress bar. | |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ProcessesUsingVirtualComponents**<br>String | Specifies a list of process paths (that may contain wildcards) that are candidates for using dynamic virtualization (such as supported shell extensions, browser helper objects, and ActiveX controls). Only processes whose full path matches one of these items can use dynamic virtualization. | Empty string. |
|
||||
|
||||
## App-V client configuration settings: registry keys
|
||||
|
||||
The following table provides information about App-V client configuration settings that can be configured through the registry:
|
||||
|
||||
|
||||
| **Setting name**<br>Type | Registry key value | Disabled policy state keys and values |
|
||||
|--------------------------------------------------------------------------------|-------------------------------------------------------------------------|---------------------------------------------------|
|
||||
| **PackageInstallationRoot**<br>String | Streaming\\PackageInstallationRoot | Policy value not written (same as Not Configured) |
|
||||
| **PackageSourceRoot**<br>String | Streaming\\PackageSourceRoot | Policy value not written (same as Not Configured) |
|
||||
| **AllowHighCostLaunch**<br>True (Enabled); False (Disabled state) | Streaming\\AllowHighCostLaunch | 0 |
|
||||
| **ReestablishmentRetries**<br>Integer (0–99) | Streaming\\ReestablishmentRetries | Policy value not written (same as Not Configured) |
|
||||
| **ReestablishmentInterval**<br>Integer (0–3600) | Streaming\\ReestablishmentInterval | Policy value not written (same as Not Configured) |
|
||||
| **LocationProvider**<br>String | Streaming\\LocationProvider | Policy value not written (same as Not Configured) |
|
||||
| **CertFilterForClientSsl**<br>String | Streaming\\CertFilterForClientSsl | Policy value not written (same as Not Configured) |
|
||||
| **VerifyCertificateRevocationList**<br>True (Enabled); False (Disabled state) | Streaming\\VerifyCertificateRevocationList | 0 |
|
||||
| **SharedContentStoreMode**<br>True (Enabled); False (Disabled state) | Streaming\\SharedContentStoreMode | 0 |
|
||||
| **Name**<br>String | Publishing\\Servers{serverId}\\FriendlyName | Policy value not written (same as Not Configured) |
|
||||
| **URL**<br>String | Publishing\\Servers{serverId}\\URL | Policy value not written (same as Not Configured) |
|
||||
| **GlobalRefreshEnabled**<br>True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\GlobalEnabled | False |
|
||||
| **GlobalRefreshOnLogon**<br>True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\GlobalLogonRefresh | False |
|
||||
| **GlobalRefreshInterval**<br>Integer (0–744) | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshInterval | 0 |
|
||||
| **GlobalRefreshIntervalUnit** <br>0 for hour, 1 for day | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshIntervalUnit | 1 |
|
||||
| **UserRefreshEnabled**<br>True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\UserEnabled | False |
|
||||
| **UserRefreshOnLogon**<br>True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\UserLogonRefresh | False |
|
||||
| **UserRefreshInterval**<br>Word count (with spaces): 85; Integer (0–744 Hours) | Publishing\\Servers{serverId}\\UserPeriodicRefreshInterval | 0 |
|
||||
| **UserRefreshIntervalUnit**<br>0 for hour, 1 for day | Publishing\\Servers{serverId}\\UserPeriodicRefreshIntervalUnit | 1 |
|
||||
| **MigrationMode**<br>True(Enabled state); False (Disabled state) | Coexistence\\MigrationMode | |
|
||||
| **EnablePackageScripts**<br>True (Enabled); False (Disabled state) | \\Scripting\\EnablePackageScripts | |
|
||||
| **RoamingFileExclusions**<br>String | | |
|
||||
| **RoamingRegistryExclusions**<br>String | Integration\\RoamingRegistryExclusions | Policy value not written (same as Not Configured) |
|
||||
| **IntegrationRootUser**<br>String | Integration\\IntegrationRootUser | Policy value not written (same as Not Configured) |
|
||||
| **IntegrationRootGlobal**<br>String | Integration\\IntegrationRootGlobal | Policy value not written (same as Not Configured) |
|
||||
| **VirtualizableExtensions**<br>String | Integration\\VirtualizableExtensions | Policy value not written |
|
||||
| **ReportingEnabled**<br>True (Enabled); False (Disabled state) | Reporting\\EnableReporting | False |
|
||||
| **ReportingServerURL**<br>String | Reporting\\ReportingServer | Policy value not written (same as Not Configured) |
|
||||
| **ReportingDataCacheLimit**<br>Integer \[0–1024\] | Reporting\\DataCacheLimit | Policy value not written (same as Not Configured) |
|
||||
| **ReportingDataBlockSize**<br>Integer \[1024–Unlimited\] | Reporting\\DataBlockSize | Policy value not written (same as Not Configured) |
|
||||
| **ReportingStartTime**<br>Integer (0–23) | Reporting\\ StartTime | Policy value not written (same as Not Configured) |
|
||||
| **ReportingInterval**<br>Integer | Reporting\\RetryInterval | Policy value not written (same as Not Configured) |
|
||||
| **ReportingRandomDelay**<br>Integer \[0 - ReportingRandomDelay\] | Reporting\\RandomDelay | Policy value not written (same as Not Configured) |
|
||||
| <strong>EnableDynamicVirtualization<br></strong>1 (Enabled), 0 (Disabled) | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Virtualization | |
|
||||
| **EnablePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Publishing | |
|
||||
| **HidePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | | |
|
||||
| **ProcessesUsingVirtualComponents**<br>String | Virtualization\\ProcessesUsingVirtualComponents | Empty string. |
|
||||
|
||||
## Related topics
|
||||
|
||||
* [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
@ -1,63 +0,0 @@
|
||||
---
|
||||
title: How to configure access to packages by using the Management Console (Windows 10/11)
|
||||
description: How to configure access to packages by using the App-V Management Console.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# How to configure access to packages by using the Management Console
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Before you deploy an App-V virtualized package, you must configure the Active Directory Domain Services (AD DS) security groups that will be allowed to access and run the applications. The security groups may contain computers or users. Entitling a package to a computer group publishes the package globally to all computers in the group.
|
||||
|
||||
Use the following procedure to configure access to virtualized packages.
|
||||
|
||||
## Grant access to an App-V package
|
||||
|
||||
1. Find the package you want to configure:
|
||||
|
||||
1. Open the App-V Management console.
|
||||
|
||||
1. Right-click the package to be configured, then select **Edit active directory access** to display the **AD Access** page. Alternatively, select the package and select **Edit** in the **AD Access** pane.
|
||||
|
||||
2. Provision a security group for the package:
|
||||
|
||||
1. Go to the **Find valid Active Directory names and grant access** page.
|
||||
|
||||
1. Using the format **mydomain** \\ **groupname**, enter the name or part of the name of an Active Directory group object, then select **Check**.
|
||||
|
||||
> [!NOTE]
|
||||
> Ensure that you provide an associated domain name for the group that you are searching for.
|
||||
|
||||
3. Grant access to the package by first selecting the desired group, then selecting **Grant Access**. The newly added group is displayed in the **AD entities with access** pane.
|
||||
|
||||
4. Select **Close** to accept the default configuration settings and close the AD Access page.
|
||||
|
||||
To customize configurations for a specific group, select the **Assigned configurations** drop-down menu, then select **Custom**. To make changes to your custom configurations, select **Edit**. After you grant access, select **Close**.
|
||||
|
||||
## Remove access to an App-V package
|
||||
|
||||
1. Find the package you want to configure:
|
||||
|
||||
1. Open the App-V Management console.
|
||||
|
||||
1. To display the **AD Access** page, right-click the package to be configured, then select **Edit active directory access**. Alternatively, select the package, then select **Edit** in the **AD Access** pane.
|
||||
|
||||
2. Select the group you want to remove, then select **Delete**.
|
||||
|
||||
3. Select **Close**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
* [Operations for App-V](appv-operations.md)
|
||||
@ -1,68 +0,0 @@
|
||||
---
|
||||
title: How to make a connection group ignore the package version (Windows 10/11)
|
||||
description: Learn how to make a connection group ignore the package version with the App-V Server Management Console.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# How to make a connection group ignore the package version
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can use Application Virtualization (App-V) to configure a connection group to use any version of a package, simplifying package upgrades and reducing the number of connection groups you need to create.
|
||||
|
||||
You can also configure a connection group to accept any version of a package, so that you can upgrade the package without having to disable the connection group.
|
||||
|
||||
- If the connection group has access to multiple versions of a package, App-V will use the latest version.
|
||||
|
||||
- If the connection group contains an optional package with an incorrect version, App-V ignores the package and won't block the connection group's virtual environment from being created.
|
||||
|
||||
- If the connection group contains a non-optional package that has an incorrect version, App-V won't be able to create the connection group's virtual environment.
|
||||
|
||||
## Make a connection group ignore the package version with the App-V Server Management Console
|
||||
|
||||
1. In the Management Console, select **Connection Groups**.
|
||||
|
||||
2. Select the correct connection group from the Connection Groups library.
|
||||
|
||||
3. Select **Edit** in the Connected Packages pane.
|
||||
|
||||
4. Select the **Use Any Version** check box next to the package name, then select **Apply**.
|
||||
|
||||
For more about adding or upgrading packages, see [How to add or upgrade packages by using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md).
|
||||
|
||||
## Make a connection group ignore the package version from the App-V client on a stand-alone computer
|
||||
|
||||
1. Create the connection group XML document.
|
||||
|
||||
2. Set the **Package** tag attribute **VersionID** to an asterisk (<strong>*</strong>) to upgrade the package.
|
||||
|
||||
3. Enter the following cmdlet (including the path to the connection group XML document) to add the connection group:
|
||||
|
||||
```PowerShell
|
||||
Add-AppvClientConnectionGroup
|
||||
```
|
||||
|
||||
For more information about how to use the **Add-AppvClientConnectionGroup** cmdlet, see [**Add-AppvClientConnectionGroup**](/powershell/module/appvclient/add-appvclientconnectiongroup).
|
||||
|
||||
4. When you upgrade a package, use the following cmdlets to remove the old package, add the upgraded package, and publish the upgraded package:
|
||||
|
||||
- [**Remove-AppvClientPackage**](/powershell/module/appvclient/remove-appvclientpackage)
|
||||
- [**Add-AppvClientPackage**](/powershell/module/appvclient/add-appvclientpackage)
|
||||
- [**Publish-AppvClientPackage**](/powershell/module/appvclient/publish-appvclientpackage)
|
||||
|
||||
For more information, see [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Managing connection groups](appv-managing-connection-groups.md)
|
||||
@ -1,67 +0,0 @@
|
||||
---
|
||||
title: How to configure the client to receive package and connection groups updates from the publishing server (Windows 10/11)
|
||||
description: How to configure the client to receive package and connection groups updates from the publishing server.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/25/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# How to configure the client to receive package and connection groups updates from the publishing server
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
The App-V publishing server's single-point management and high scalability lets you deploy packages and connection groups and keep them up to date.
|
||||
|
||||
This article will tell you how to configure the App-V client to receive updates from the publishing server.
|
||||
|
||||
>[!NOTE]
|
||||
>The following example has the management server installed on a computer named **MyMgmtSrv**, and the publishing server installed on a computer named **MyPubSrv**. If the computers you'll be configuring the App-V client on have different names, you should replace the example's names with your computer's names.
|
||||
|
||||
## Configure the App-V client to receive updates from the publishing server
|
||||
|
||||
1. Deploy the App-V management and publishing servers, and add the required packages and connection groups. For more information about adding packages and connection groups, see [How to add or upgrade packages by using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md) and [How to create a connection group](appv-create-a-connection-group.md).
|
||||
2. To open the management console, open a web browser and enter the following URL: `https://MyMgmtSrv/AppvManagement/Console.html`. Import, publish, and entitle all packages and connection groups that your users will need.
|
||||
3. On the computer running the App-V client, open an elevated Windows PowerShell command prompt, and run the following command:
|
||||
|
||||
```PowerShell
|
||||
Add-AppvPublishingServer -Name ABC -URL https://MyPubSrv/AppvPublishing
|
||||
```
|
||||
|
||||
This command will configure the specified publishing server. You should see output similar to the following:
|
||||
|
||||
```PowerShell
|
||||
Id : 1
|
||||
SetByGroupPolicy : False
|
||||
Name : ABC
|
||||
URL : https://MyPubSrv/AppvPublishing
|
||||
GlobalRefreshEnabled : False
|
||||
GlobalRefreshOnLogon : False
|
||||
GlobalRefreshInterval : 0
|
||||
GlobalRefreshIntervalUnit : Day
|
||||
UserRefreshEnabled : True
|
||||
UserRefreshOnLogon : True
|
||||
UserRefreshInterval : 0
|
||||
UserRefreshIntervalUnit : Day
|
||||
```
|
||||
|
||||
4. On the computer running the App-V client, open a Windows PowerShell command prompt and enter the following cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Sync-AppvPublishingServer -ServerId 1
|
||||
```
|
||||
|
||||
This cmdlet will query the publishing server for which packages and connection groups need to be added or removed for this particular client based on your configured entitlements for the packages and connection groups on the management server.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related article
|
||||
|
||||
* [Operations for App-V](appv-operations.md)
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
title: How to connect to the Management Console (Windows 10/11)
|
||||
description: In this article, learn the procedure for connecting to the App-V Management Console through your web browser.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/25/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# How to connect to the Management Console
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to connect to the App-V Management Console.
|
||||
|
||||
## Connect to the App-V Management Console
|
||||
|
||||
1. Open your web browser and enter the address for the App-V Management server. For example, **https://\<_management server name_\>:\<_management service port number_\>/console.html**.
|
||||
|
||||
2. To view different sections of the console, select your desired section in the navigation pane.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
@ -1,146 +0,0 @@
|
||||
---
|
||||
title: About the connection group file (Windows 10/11)
|
||||
description: A summary of what the connection group file is and how to configure it.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/25/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# About the connection group file
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
## Connection group file overview
|
||||
|
||||
### What is a connection group?
|
||||
|
||||
A connection group is an App-V feature that can group packages together to create a virtual environment where applications within that package group can interact with each other.
|
||||
|
||||
For example, let's say you want to use plug-ins with Microsoft Office. You can create one package that contains the plug-ins and another package that contains Office, and then add both packages to the same connection group to enable Office to use those plug-ins.
|
||||
|
||||
### How a connection group file works
|
||||
|
||||
When you apply an App-V connection group file, all packages specified in the file will be combined at runtime into a single virtual environment. Use the Microsoft Application Virtualization (App-V) connection group file to configure existing App-V connection groups.
|
||||
|
||||
An example file path for a package file would be %APPDATA%\Microsoft\AppV\Client\Catalog\PackageGroups\{6CCC7575-162E-4152-9407-ED411DA138F4}\{4D1E16E1-8EF8-41ED-92D5-8910A8527F96}.
|
||||
|
||||
## Structure of the connection group XML file
|
||||
|
||||
This section will tell you more about the components of the connection group XML file.
|
||||
|
||||
### Parameters that define the connection group
|
||||
|
||||
The following table describes the parameters in the XML file that define the connection group itself, not the packages.
|
||||
|
||||
|Field|Description|
|
||||
|-----|-----------|
|
||||
|Schema name|Name of the schema.</br>If you want to use the “optional packages” and “use any version” features described in this table, you must specify the following schema in the XML file:</br>`xmlns="https://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup"`|
|
||||
|AppConnectionGroupId|Unique GUID identifier for this connection group. The connection group state is associated with this identifier. Specify this identifier only when you create the connection group.</br>You can create a new GUID by entering **[Guid]::NewGuid()**.|
|
||||
|VersionId|Version GUID identifier for this version of the connection group.</br>When you update a connection group (for example, by adding or updating a new package), you must update the version GUID to reflect the new version.|
|
||||
|DisplayName|Display name of the connection group.|
|
||||
|Priority|Optional priority field for the connection group.</br>A value of **0** indicates the highest priority.</br>If a priority is required but has not been configured, the package will fail because it can't determine the correct connection group to use.|
|
||||
|
||||
### Parameters that define the packages in the connection group
|
||||
|
||||
In the **<Packages>** section of the connection group XML file, you list the member packages in the connection group by specifying each package’s unique package identifier and version identifier, as described in the following table. The first package in the list has the highest precedence.
|
||||
|
||||
|Field|Description|
|
||||
|---|---|
|
||||
|PackageId|Unique GUID identifier for this package. This GUID doesn’t change when newer versions of the package are published.|
|
||||
|VersionId|Unique GUID identifier for the version of the package. </br>If you specify “*” for the package version, the GUID of the latest available package version is dynamically inserted.|
|
||||
|IsOptional|Parameter that enables you to make a package optional within the connection group. Valid entries are:</br>- “**true**”—package is optional in the connection group</br>- “**false**”—package is required in the connection group|
|
||||
|
||||
### App-V example connection group XML file
|
||||
|
||||
The following example connection group XML file shows examples of the fields listed in the previous tables.
|
||||
|
||||
```XML
|
||||
<?xml version="1.0" encoding="UTF-16"?>
|
||||
<appv:AppConnectionGroup
|
||||
xmlns="http://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup"
|
||||
xmlns:appv="http://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup"
|
||||
AppConnectionGroupId="61BE9B14-D2B4-41CE-A6E3-A1B658DE7000"
|
||||
VersionId="E6B6AA57-F2A7-49C9-ADF8-F2B5B3C8A42F"
|
||||
Priority="0"
|
||||
DisplayName="Sample Connection Group">
|
||||
<appv:Packages>
|
||||
<appv:Package
|
||||
PackageId="1DC709C8-309F-4AB4-BD47-F75926D04276"
|
||||
VersionId="*"
|
||||
IsOptional=”true”
|
||||
/>
|
||||
<appv:Package
|
||||
PackageId="04220DCA-EE77-42BE-A9F5-96FD8E8593F2"
|
||||
VersionId="E15EFFE9-043D-4C01-BC52-AD2BD1E8BAFA"
|
||||
IsOptional=”false”
|
||||
/>
|
||||
</appv:Packages>
|
||||
```
|
||||
|
||||
## Configuring the priority of packages in a connection group
|
||||
|
||||
Package precedence is configured using the package list order. The first package in the document has the highest precedence. Subsequent packages in the list have descending priority.
|
||||
|
||||
Package precedence is the resolution for otherwise inevitable resource collisions during virtual environment initialization. For example, if two packages that are opening in the same virtual environment define the same registry DWORD value, the package with the highest precedence determines the value that is set.
|
||||
|
||||
You can use the connection group file to configure each connection group by using the following methods:
|
||||
|
||||
- Specify runtime priorities for connection groups. To edit priority by using the App-V Management Console, select the connection group and then select **Edit**.
|
||||
|
||||
> [!NOTE]
|
||||
>A package only requires priority if it's associated with more than one connection group.
|
||||
- Specify package precedence within the connection group.
|
||||
|
||||
The priority field is required when a running virtual application initiates from a native application request, such as Microsoft Windows Explorer. The App-V client uses the priority to determine which connection group virtual environment the application should run in. This situation occurs if a virtual application is part of multiple connection groups.
|
||||
|
||||
If a virtual application is opened using another virtual application, the client will use the original virtual application's virtual environment. The priority field is not used in this case.
|
||||
|
||||
The following is an example of priority configuration:
|
||||
|
||||
The virtual application Microsoft Outlook is running in virtual environment **XYZ**. When you open an attached Microsoft Word document, a virtualized version Microsoft Word opens in the virtual environment **XYZ**, regardless of the virtualized Microsoft Word’s associated connection groups or runtime priorities.
|
||||
|
||||
## Supported virtual application connection configurations
|
||||
|
||||
App-V supports the following application connection configurations.
|
||||
|
||||
- **An .exe file and plug-in (.dll)**. For example, you might want to distribute Microsoft Office to all users, but only distribute a Microsoft Excel plug-in to a small subset of those users.
|
||||
|
||||
Enable the connection group for the appropriate users. Update each package individually as required.
|
||||
|
||||
- **An .exe file and a middleware application**. This is for cases where you have an application that requires a middleware application, or several applications that all depend on the same middleware runtime version.
|
||||
|
||||
All computers that require one or more of the applications receive the connection groups with the application and middleware application runtime. You can optionally combine multiple middleware applications into a single connection group.
|
||||
|
||||
|Example|Example description|
|
||||
|---|---|
|
||||
|Virtual application connection group for the financial division|- Middleware application 1</br>- Middleware application 2</br>- Middleware application 3</br>- Middleware application runtime|
|
||||
|Virtual application connection group for HR division|- Middleware application 5</br>- Middleware application 6</br>- Middleware application runtime|
|
||||
|
||||
- **An. exe file and an .exe file**. This is for cases where you have an application that relies on another application, but you want to keep the packages separate for operational efficiencies, licensing restrictions, or rollout timelines.
|
||||
|
||||
For example, if you are deploying Microsoft Lync 2010, you can use three packages:
|
||||
|
||||
- Microsoft Office 2010
|
||||
- Microsoft Communicator 2007
|
||||
- Microsoft Lync 2010
|
||||
|
||||
You can manage the deployment with the following connection groups:
|
||||
|
||||
- Microsoft Office 2010 and Microsoft Communicator 2007
|
||||
- Microsoft Office 2010 and Microsoft Lync 2010
|
||||
|
||||
After deployment, you can either create a single new Microsoft Office 2010 + Microsoft Lync 2010 package or keep and maintain them as separate packages and deploy them with a connection group.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Managing connection groups](appv-managing-connection-groups.md)
|
||||
@ -1,85 +0,0 @@
|
||||
---
|
||||
title: About the connection group virtual environment (Windows 10/11)
|
||||
description: Learn how the connection group virtual environment works and how package priority is determined.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 06/25/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# About the connection group virtual environment
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
## How package priority is determined
|
||||
|
||||
The virtual environment and its current state are associated with the connection group, not with the individual packages. If you remove an App-V package from the connection group, the state that existed as part of the connection group won't migrate with the package.
|
||||
|
||||
If the same package is a part of two different connection groups, you have to indicate which connection group App-V should use. For example, you might have two packages in a connection group wherein each defines the same registry DWORD value.
|
||||
|
||||
The connection group that is used is based on the order in which a package appears inside the **AppConnectionGroup** XML document:
|
||||
|
||||
- The first package has the highest precedence.
|
||||
- The second package has the second highest precedence.
|
||||
|
||||
Consider the following example section:
|
||||
|
||||
```XML
|
||||
<appv:Packages>
|
||||
<appv:Package
|
||||
PackageId="A8731008-4523-4713-83A4-CD1363907160"
|
||||
VersionId="E889951B-7F30-418B-A69C-B37283BC0DB9"
|
||||
/>
|
||||
<appv:Package
|
||||
PackageId="1DC709C8-309F-4AB4-BD47-F75926D04276"
|
||||
VersionId="01F1943B-C778-40AD-BFAD-AC34A695DF3C"
|
||||
/>
|
||||
<appv:Package
|
||||
PackageId="04220DCA-EE77-42BE-A9F5-96FD8E8593F2"
|
||||
VersionId="E15EFFE9-043D-4C01-BC52-AD2BD1E8BAFA"
|
||||
/>
|
||||
</appv:Packages>
|
||||
```
|
||||
|
||||
Assume that same DWORD value ABC (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region) is defined in the first and third package.
|
||||
|
||||
For this example, the DWORD value definition would be as shown below:
|
||||
|
||||
- Package 1 (A8731008-4523-4713-83A4-CD1363907160): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5
|
||||
- Package 3 (04220DCA-EE77-42BE-A9F5-96FD8E8593F2): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=10
|
||||
|
||||
Since Package 1 appears first, the AppConnectionGroup's virtual environment will have the single DWORD value of 5 (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5). This result means that the virtual applications in Package 1, Package 2, and Package 3 will all see the value 5 when they query for HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region.
|
||||
|
||||
Other virtual environment resources are resolved in a similar way, but usually collisions occur in the registry.
|
||||
|
||||
## Merging identical package paths into one virtual directory in connection groups
|
||||
|
||||
If two or more packages in a connection group contain identical directory paths, the paths are merged into a single virtual directory inside the connection group's virtual environment. Merging these paths allows an application in one package to access files that are in a different package.
|
||||
|
||||
When you remove a package from a connection group, the removed package's applications can no longer access files from packages in the connection group it was removed from.
|
||||
|
||||
App-V looks up a file’s name in the connection group in the order App-V packages are listed in the connection group manifest file.
|
||||
|
||||
The following example shows the order and relationship of a file name lookup in a connection group for **Package A** and **Package B**.
|
||||
|
||||
|Package A|Package B|
|
||||
|---|---|
|
||||
|C:\Windows\System32|C:\Windows\System32|
|
||||
|C:\AppTest|C:\AppTest|
|
||||
|
||||
When a virtualized application tries to find a specific file, App-V will search for a matching file path in Package A. If it doesn't find a matching path in Package A, it will then search Package B using the following mapping rules:
|
||||
|
||||
- If a file named **test.txt** exists in the same virtual folder hierarchy in both application packages, App-V will use the first matching file.
|
||||
- If a file named **bar.txt** exists in the virtual folder hierarchy of one application package, but not in the other, App-V will use the first matching file.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
@ -1,93 +0,0 @@
|
||||
---
|
||||
title: How to convert a package created in a previous version of App-V (Windows 10/11)
|
||||
description: Use the package converter utility to convert a virtual application package created in a previous version of App-V.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# How to convert a package created in a previous version of App-V
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can use the package converter utility to upgrade virtual application packages created by previous versions of App-V. This section will tell you how to convert existing virtual application packages for upgrade.
|
||||
|
||||
>[!NOTE]
|
||||
>If you are running a computer with a 64-bit architecture, you must use the x86 version of Windows PowerShell.
|
||||
|
||||
The package converter can only directly convert packages created by an App-V sequencer version 4.5 or later. Packages created with an App-V version earlier than 4.5 must be upgraded to at least App-V 4.5 before conversion.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>In order to keep your files secure, you must configure the package converter to always save the package ingredients file to a secure location and directory that can only be accessed by an administrator. When you deploy the package, you should either save the package to a secure location or make sure that no other users can sign in during the conversion process.
|
||||
|
||||
## App-V 4.6 installation folder is redirected to virtual file system root
|
||||
|
||||
When you convert packages from App-V 4.6 to App-V for Windows 10/11, the App-V for Windows client package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive is drive Q.)
|
||||
|
||||
The App-V package converter will save the App-V 4.6 installation root folder and short folder names in the FilesystemMetadata.xml file in the **Filesystem** element. When the App-V for Windows client creates the virtual process, it will map requests from the App-V 4.6 installation root to the virtual file system root.
|
||||
|
||||
## Getting started
|
||||
|
||||
1. Install the App-V Sequencer on a computer in your environment. For information about how to install the Sequencer, see [How to install the Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
2. You can enter the following cmdlets to check or convert packages:
|
||||
|
||||
- **Test-AppvLegacyPackage**—This cmdlet checks packages. It will return information about any failures with the package such as missing **.sft** files, an invalid source, **.osd** file errors, or invalid package version. This cmdlet won't parse the **.sft** file or do any in-depth validation. For information about options and basic functionality for this cmdlet, using Windows PowerShell, enter the following cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Test-AppvLegacyPackage -?
|
||||
```
|
||||
|
||||
- **ConvertFrom-AppvLegacyPackage**—This cmdlet converts packages from legacy versions to updated versions. To convert an existing package, enter the following cmdlet:
|
||||
|
||||
```PowerShell
|
||||
ConvertFrom-AppvLegacyPackage C:\contentStore C:\convertedPackages
|
||||
```
|
||||
|
||||
In this cmdlet, `C:\contentStore` represents the location of the existing package and `C:\convertedPackages` is the output directory to which the resulting App-V for Windows client virtual application package file will be saved. By default, if you don't specify a new name, the old package name will be used.
|
||||
|
||||
Additionally, the package converter optimizes performance of packages in App-V for Windows client by setting the package to stream fault the App-V package. This definition of setting is more performant than the primary feature block and fully downloading the package. The flag **DownloadFullPackageOnFirstLaunch** allows you to convert the package and set the package to be fully downloaded by default.
|
||||
|
||||
> [!NOTE]
|
||||
> Before you specify the output directory, you must create the output directory.
|
||||
|
||||
### Advanced Conversion Tips
|
||||
|
||||
- Piping—Windows PowerShell supports piping. Piping allows you to enter cmdlets like this example:
|
||||
|
||||
```PowerShell
|
||||
dir C:\contentStore\myPackage | Test-AppvLegacyPackage
|
||||
```
|
||||
|
||||
In this example, the directory object that represents `myPackage` will be given as input to the **Test-AppvLegacyPackage** cmdlet and bound to the *-Source* parameter. Piping like this is especially useful when you want to batch commands together, such as in the following example cmdlet:
|
||||
|
||||
```PowerShell
|
||||
dir .\ | Test-AppvLegacyPackage | ConvertFrom-AppvLegacyAppvPackage -Target .\ConvertedPackages
|
||||
```
|
||||
|
||||
This piped example command tests packages, then passes the objects on for conversion. You can also apply a filter on packages without errors or only specify a directory that contains an **.sprj** file or pipe them to another cmdlet that adds the filtered package to the server or publishes them to the App-V client.
|
||||
|
||||
- Batching—The Windows PowerShell command enables batching. More specifically, the cmdlets support taking a string\[\] object for the *-Source* parameter that represents a list of directory paths. This feature allows you to enter the following cmdlets together:
|
||||
|
||||
```PowerShell
|
||||
$packages = dir C:\contentStore
|
||||
ConvertFrom-AppvLegacyAppvPackage-Source $packages -Target C:\ConvertedPackages
|
||||
```
|
||||
|
||||
Alternatively, you can use piping like this:
|
||||
|
||||
```PowerShell
|
||||
dir C:\ContentStore | ConvertFrom-AppvLegacyAppvPackage -Target C:\ConvertedPackages
|
||||
```
|
||||
|
||||
- Other functionality—Windows PowerShell has other built-in functionality for features such as aliases, lazy-binding, .NET Object, and many others. These features can help you create advanced scenarios for the Package Converter.
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
@ -1,66 +0,0 @@
|
||||
---
|
||||
title: How to create a connection croup with user-published and globally published packages (Windows 10/11)
|
||||
description: How to create a connection croup with user-published and globally published packages.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# How to create a connection croup with user-published and globally published packages
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can create user-entitled connection groups that contain both user-published and globally published packages, using either of the following methods:
|
||||
|
||||
- [How to use Windows PowerShell cmdlets to create user-entitled connection groups](#how-to-use-windows-powershell-cmdlets-to-create-user-entitled-connection-groups)
|
||||
- [How to use the App-V Server to create user-entitled connection groups](#how-to-use-the-app-v-server-to-create-user-entitled-connection-groups)
|
||||
|
||||
## Unsupported scenarios and potential issues
|
||||
|
||||
Here are some important things to know before you get started:
|
||||
|
||||
- If you add user-published packages in globally entitled connection groups, the connection group will fail.
|
||||
- Track the connection groups where you've used a non-optional package before removing it with the **Unpublish-AppvClientPackage <</span>package> -global** cmdlet.
|
||||
|
||||
In situations where you have a globally published package that's listed as non-optional in a user-published connection group that also appears in other packages, running **Unpublish-AppvClientPackage <</span>package> -global** cmdlet can unpublish the package from every connection group containing that package. Tracking connection groups can help you avoid unintentionally unpublishing non-optional packages.
|
||||
|
||||
## How to use Windows PowerShell cmdlets to create user-entitled connection groups
|
||||
|
||||
1. Add and publish packages by using the following commands:
|
||||
|
||||
```PowerShell
|
||||
Add-AppvClientPackage <Package1_AppV_file_Path>
|
||||
Add-AppvClientPackage <Package2_AppV_file_Path>
|
||||
Publish-AppvClientPackage -PackageId <Package1_ID> -VersionId <Package1_Version_ID> -Global
|
||||
Publish-AppvClientPackage -PackageId <Package2_ID> -VersionId <Package2_Version_ID>
|
||||
```
|
||||
|
||||
2. Create the connection group XML file. For more information, see [About the connection group file](appv-connection-group-file.md).
|
||||
|
||||
3. Add and publish the connection group by using the following commands:
|
||||
|
||||
```PowerShell
|
||||
Add-AppvClientConnectionGroup <Connection_Group_XML_file_Path>
|
||||
Enable-AppvClientConnectionGroup -GroupId <CG_Group_ID> -VersionId <CG_Version_ID>
|
||||
```
|
||||
|
||||
## How to use the App-V Server to create user-entitled connection groups
|
||||
|
||||
1. Open the App-V Management Console.
|
||||
|
||||
2. Follow the instructions in [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md) to publish packages globally and to the user.
|
||||
|
||||
3. Follow the instructions in [How to create a connection group](appv-create-a-connection-group.md) to create the connection group and add the user-published and globally published packages.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
@ -1,50 +0,0 @@
|
||||
---
|
||||
title: How to create a connection group (Windows 10/11)
|
||||
description: Learn how to create a connection group with the App-V Management Console and where to find information about managing connection groups.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# How to create a connection group
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use these steps to create a connection group by using the App-V Management Console. To use Windows PowerShell to create connection groups, see [How to manage connection groups on a stand-alone computer by using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md).
|
||||
|
||||
When you place packages in a connection group, their package root paths merge. If you remove packages, only the remaining packages maintain the merged root.
|
||||
|
||||
## Create a connection group
|
||||
|
||||
1. In the App-V Management Console, select **CONNECTION GROUPS** to display the Connection Groups library.
|
||||
|
||||
2. Select **ADD CONNECTION GROUP** to create a new connection group.
|
||||
|
||||
3. In the **New Connection Group** pane, enter a description for the group.
|
||||
|
||||
4. Select **EDIT** in the **CONNECTED PACKAGES** pane to add a new application to the connection group.
|
||||
|
||||
5. In the **PACKAGES Entire Library** pane, select the application to be added, then select the arrow to add the application.
|
||||
|
||||
To remove an application, select the application to be removed in the **PACKAGES IN** pane and select the arrow.
|
||||
|
||||
To reprioritize the applications in your connection group, use the arrows in the **PACKAGES IN** pane.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>By default, the Active Directory Domain Services access configurations that are associated with a specific application are not added to the connection group. To transfer the Active Directory access configuration, select **ADD PACKAGE ACCESS TO GROUP ACCESS**, which is located in the **PACKAGES IN** pane.
|
||||
|
||||
6. After adding all the applications and configuring Active Directory access, select **Apply**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
- [Managing connection groups](appv-managing-connection-groups.md)
|
||||
@ -1,39 +0,0 @@
|
||||
---
|
||||
title: How to create a custom configuration file by using the App-V Management Console (Windows 10/11)
|
||||
description: How to create a custom configuration file by using the App-V Management Console.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# How to create a custom configuration file by using the App-V Management Console
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can use a dynamic configuration to customize an App-V package for a specific user. However, you must first create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use the files. Creation of the file is an advanced manual operation. For general information about dynamic user configuration files, see [About App-V dynamic configuration](appv-dynamic-configuration.md).
|
||||
|
||||
You can create a dynamic user configuration file with the App-V Management Console by following the steps in this article.
|
||||
|
||||
## Create a dynamic user configuration file
|
||||
|
||||
1. Right-click the name of the package that you want to view and select **Edit active directory access** to view the configuration that is assigned to a given user group. Alternatively, select the package, and click **Edit**.
|
||||
|
||||
2. Using the list of **AD Entities with Access**, select the AD group that you want to customize. Select **Custom** from the drop-down list. A link named **Edit** will appear.
|
||||
|
||||
3. Select **Edit**. The Dynamic User Configuration assigned to the AD Group will appear.
|
||||
|
||||
4. Select **Advanced**, and then select **Export Configuration**. Enter a file name and select **Save**. Now you can edit the file to configure a package for a user.
|
||||
|
||||
> [!NOTE]
|
||||
> If you want to export a configuration while running on Windows Server, make sure to disable the IE Enhanced Security Configuration setting. If this setting is enalbed and set to block downloads, you won't be able to download anything from the App-V Server.
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
@ -1,50 +0,0 @@
|
||||
---
|
||||
title: How to create a package accelerator by using Windows PowerShell (Windows 10/11)
|
||||
description: Learn how to create an App-v Package Accelerator by using Windows PowerShell. App-V Package Accelerators automatically sequence large, complex applications.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# How to create a package accelerator by using Windows PowerShell
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
App-V Package Accelerators automatically sequence large, complex applications. Also, when you apply an App-V Package Accelerator, you don't have to manually install an application to create the virtualized package.
|
||||
|
||||
## Create a package accelerator
|
||||
|
||||
1. Install the App-V sequencer. For more information about installing the sequencer, see [How to install the sequencer](appv-install-the-sequencer.md).
|
||||
2. To open a Windows PowerShell console, select **Start** and enter **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**.
|
||||
3. Ensure there's the App-V package to create an accelerator from the installation media or installation files. You can also optionally use a readme file for the accelerator's users to reference.
|
||||
4. Enter the **New-AppvPackageAccelerator** cmdlet.
|
||||
|
||||
The following parameters are required to use the package accelerator cmdlet:
|
||||
|
||||
- *InstalledFilesPath* specifies the application installation path.
|
||||
- *Installer* specifies the path to the application installer media.
|
||||
- *InputPackagePath* specifies the path to the App-V package.
|
||||
- *Path* specifies the output directory for the package.
|
||||
|
||||
The following example cmdlet shows how you can create a package accelerator with the App-V package and the installation media:
|
||||
|
||||
```PowerShell
|
||||
New-AppvPackageAccelerator -InputPackagePath <path to the .appv file> -Installer <path to the installer executable> -Path <directory of the output path>
|
||||
```
|
||||
|
||||
You can also use the following optional parameter with the **New-AppvPackageAccelerator** cmdlet:
|
||||
|
||||
- *AcceleratorDescriptionFile* specifies the path to user-created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be included in the package created by the package accelerator.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
@ -1,81 +0,0 @@
|
||||
---
|
||||
title: How to create a package accelerator (Windows 10/11)
|
||||
description: Learn how to create App-V Package Accelerators to automatically generate new virtual application packages.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# How to create a package accelerator
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
App-V Package Accelerators automatically generate new virtual application packages.
|
||||
|
||||
>[!NOTE]
|
||||
>You can use Windows PowerShell to create a package accelerator. For more information, see [How to create a package accelerator by using Windows PowerShell](appv-create-a-package-accelerator-with-powershell.md).
|
||||
|
||||
Use the following procedure to create a package accelerator.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>
|
||||
>- Because package accelerators can contain password and user-specific information, you should save package accelerators and the associated installation media in a secure location, and you should also digitally sign the package accelerator after creating it so that you can verify the publisher when applying the App-V Package Accelerator.
|
||||
>- Before you begin creating a package accelerator, do the following:
|
||||
> - Copy the virtual application package that you will use to create the package accelerator locally to the computer running the sequencer.
|
||||
> - Copy all required installation files associated with the virtual application package to the computer running the sequencer.
|
||||
>- The App-V Sequencer does not grant any license rights to the software application you are using to create the package accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a package accelerator with the App-V sequencer.
|
||||
|
||||
## Create a package accelerator
|
||||
|
||||
1. To start the App-V sequencer on the computer running the sequencer, select **Start** > **All Programs** > **Microsoft Application Virtualization** > **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. To start the App-V **Create Package Accelerator** wizard, in the App-V sequencer console, select **Tools** > **Create Accelerator**.
|
||||
|
||||
3. On the **Select Package** page, select **Browse** to specify an existing virtual application package to use to create the package accelerator, then locate the existing virtual application package (it will appear as an .appv file).
|
||||
|
||||
>[!TIP]
|
||||
>Copy the files associated with the virtual application package you plan to use locally to the computer running the Sequencer.
|
||||
|
||||
Select **Next**.
|
||||
|
||||
4. Go to the **Installation Files** page and select **Browse**, then select the directory that contains the installation files to specify the folder containing the original virtual package's installation files.
|
||||
|
||||
>[!TIP]
|
||||
>Copy the folder that contains the required installation files to the computer running the Sequencer.
|
||||
|
||||
5. If the application is already installed on the computer running the sequencer, then select **Files installed on local system** to specify the installation file. To use this option, the application must already be installed in the default installation location.
|
||||
|
||||
6. On the **Gathering Information** page, review the files that you couldn't find in the location specified by the **Installation Files** page. If the files displayed aren't required, select **Remove these files**, then select **Next**. If the files are required, select **Previous** and copy the required files to the directory specified on the **Installation Files** page.
|
||||
|
||||
> [!NOTE]
|
||||
>You must either remove the unrequired files or select **Previous** and locate the required files to advance to the next page of this wizard.
|
||||
|
||||
7. On the **Select Files** page, carefully review the detected files. Clear any file the package accelerator doesn't need to run successfully and select only the files that the application requires. When you're done, select **Next**.
|
||||
|
||||
8. Confirm that the **Verify Applications** page displays all installation files required to build the package. The package accelerator requires all installation files displayed in the **Applications** pane in order to create the package.
|
||||
|
||||
If you need to add more Installer files, select **Add**. To remove unnecessary installation files, select the **Installer file**, then select **Delete**. To edit the properties associated with an installer, select **Edit**. The package accelerator requires the installation files specified in this step to create a new virtual application package. After you've confirmed the information displayed, select **Next**.
|
||||
|
||||
9. On the **Select Guidance** page, select **Browse** to specify the file that will provide the package accelerator with application instructions. For example, this file can contain information about how the computer running the Sequencer should be configured, application prerequisite information for target computers, and general notes. You should provide all required information for successful package accelerator application. The file you select must be in rich text (.rtf) or text file (.txt) format. After specifying the file, select **Next**.
|
||||
|
||||
10. On the **Create Package Accelerator** page, select **Browse** and select the directory where you want to save the package accelerator.
|
||||
|
||||
11. On the **Completion** page, select **Close**.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You should always digitally sign the package accelerator to ensure that it is secure and can be verified by a publisher during application.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
- [How to create a virtual application package using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md)
|
||||
@ -1,80 +0,0 @@
|
||||
---
|
||||
title: How to create a virtual application package using an App-V Package Accelerator (Windows 10/11)
|
||||
description: How to create a virtual application package using an App-V Package Accelerator.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# How to create a virtual application package using an App-V Package Accelerator
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to create a virtual application package with the App-V Package Accelerator.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The App-V Sequencer does not grant any license rights to the software application that you use to create the package accelerator. You must abide by all end user license terms for the application that you use. It is your responsibility to make sure that the software application’s license terms allow you to create a package accelerator with the App-V Sequencer.
|
||||
|
||||
## Create a virtual application package with an App-V Package Accelerator
|
||||
|
||||
1. Make sure you've copied the required package accelerator locally to the computer running the App-V Sequencer. Also make sure to copy all required installation files for the package to a local folder on the computer running the Sequencer. This is the folder that you have to specify in step 6 of this procedure.
|
||||
|
||||
2. To start the App-V Sequencer on the computer that runs the Sequencer, go to **Start** > **All Programs** > **Microsoft Application Virtualization** > **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
3. Select **Create a New Virtual Application Package**. To create the package, select the **Create Package using a Package Accelerator** check box, then select **Next**.
|
||||
|
||||
4. To specify the package accelerator that will be used to create the new virtual application package, select **Browse** on the **Select Package Accelerator** page. Select **Next**.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If the publisher of the package accelerator cannot be verified and does not contain a valid digital signature, then before you select **Run**, you must confirm that you trust the source of the package accelerator. Confirm your choice in the **Security Warning** dialog box.
|
||||
|
||||
5. On the **Guidance** page, review the publishing guidance information that is displayed in the information pane. This information was added when the package accelerator was created and it contains guidance about how to create and publish the package. To export the guidance information to a text (.txt) file, select **Export** and specify the location where the file should be saved, and then select **Next**.
|
||||
|
||||
6. On the **Select Installation Files** page, select **Make New Folder** to create a local folder that contains all required installation files for the package, and specify where the folder should be saved. You must also specify a name to be assigned to the folder. You must then copy all required installation files to the location that you specified. If the folder that contains the installation files already exists on the computer that runs the Sequencer, select **Browse** to select the folder.
|
||||
|
||||
Alternatively, if you have already copied the installation files to a directory on this computer, select **Make New Folder**, browse to the folder that contains the installation files, then select **Next**.
|
||||
|
||||
> [!NOTE]
|
||||
>You can specify the following types of supported installation files:
|
||||
> - Windows Installer files (**.msi**)
|
||||
> - Cabinet files (.cab)
|
||||
> - Compressed files with a .zip file name extension
|
||||
> - The actual application files
|
||||
> The following file types are not supported: **.msp** and **.exe** files. If you specify an **.exe** file, you must extract the installation files manually.
|
||||
|
||||
7. If the package accelerator requires you to install an application before you apply the package accelerator and you have already installed the required application, select **I have installed all applications**, then select **Next** on the **Local Installation** page.
|
||||
|
||||
8. On the **Package Name** page, specify a name that will be associated with the package. The name you choose will identify the package in the App-V Management Console. Select **Next**.
|
||||
|
||||
9. On the **Create Package** page, provide comments that will be associated with the package. The comments should contain identifying information about the package that you are creating. To confirm the location where the package is created, review the information displayed in **Save Location**. To compress the package, select **Compress Package**. Select the **Compress Package** check box if the package will be streamed across the network or the package size exceeds 4 GB.
|
||||
|
||||
10. To create the package, select **Create**. After the package is created, select **Next**.
|
||||
|
||||
11. On the **Configure Software** page, to enable the Sequencer to configure the applications contained within the package, select **Configure Software**. **Configure Software** will let you configure any associated tasks required to run the application on the target computers. For example, you can configure any associated license agreements.
|
||||
|
||||
The following items can be configured using the Sequencer as part of this step:
|
||||
|
||||
- **Load Package** loads files associated with the package. It can take several seconds to an hour to decode the package.
|
||||
- **Run Each Program** optionally runs programs contained within the package. This step can help you complete associated license or configuration tasks that must be completed before deploying and running the package on target computers. To run all the programs at once, select at least one program, and then select **Run All**. To run specific programs, select the program or programs that you want to run, and then select **Run Selected**. Complete the required configuration tasks, then close the applications. It can take several minutes for all programs to run. Select **Next**.
|
||||
- **Save Package** saves the package.
|
||||
- **Primary Feature Block** optimizes the package for streaming by rebuilding the primary feature block.
|
||||
|
||||
If you don't want to configure the applications, select **Skip this step**, then select **Next**.
|
||||
|
||||
12. On the **Completion** page, after you review the information that is displayed in the **Virtual Application Package Report** pane, select **Close**.
|
||||
|
||||
The package is now available in the Sequencer. To edit the package properties, select **Edit \[Package Name\]**. For more information about how to modify a package, see [How to modify an existing virtual application package](appv-modify-an-existing-virtual-application-package.md).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
@ -1,59 +0,0 @@
|
||||
---
|
||||
title: Create and apply an App-V project template to a sequenced App-V package (Windows 10/11)
|
||||
description: Steps for how to create and apply an App-V project template (.appvt) to a sequenced App-V package.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# Create and apply an App-V project template to a sequenced App-V package
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can use an App-V Project Template (.appvt) file to save commonly applied settings associated with an existing virtual application package. You can then apply these settings whenever you create new virtual application packages in your environment, streamlining the package creation process. App-V Project Templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V Project Templates can be applied to multiple applications. To learn more about package accelerators, see [How to create a package accelerator](appv-create-a-package-accelerator.md).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Starting with Windows 10 version 1703, running the **New-AppvSequencerPackage** or the **Update-AppvSequencerPackage** cmdlets will automatically capture and store your customizations as an App-V Project Template. If you want to make changes to this package later, you can automatically load your customizations from this template file. If you have an auto-saved template and you attempt to load another template through the *TemplateFilePath* parameter, the customization value from the parameter will override the auto-saved template.
|
||||
|
||||
## Create a project template
|
||||
|
||||
You must first create and save a project template, including a virtual app package with settings to be used by the template.
|
||||
|
||||
1. On the device running the App-V Sequencer, select **Start**, select **All Programs**, select **Microsoft Application Virtualization**, and then select **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
> [!NOTE]
|
||||
>If the virtual app package is currently open in the App-V Sequencer console, skip to Step 3 of this procedure.
|
||||
|
||||
2. On the **File** menu, select **Open**, select **Edit Package**, browse for the virtual app package that includes the settings you want to save with the App-V Project Template, and then select **Edit** to change any of the settings or info included in the file.
|
||||
|
||||
3. On the **File** menu, select **Save As Template**, review the settings associated with the new template, select **OK**, name your new template, and then select **Save**.
|
||||
|
||||
The new App-V Project Template is saved in the folder you specified.
|
||||
|
||||
## Apply a project template
|
||||
|
||||
After creating the template, you can apply it to all of your new virtual app packages, automatically including all of the settings.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Virtual app packages don't support using both a project template and a package accelerator at the same time.
|
||||
|
||||
1. On the device running the App-V Sequencer, select **Start** > **All Programs** > **Microsoft Application Virtualization** > **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. On the **File** menu, select **New From Template**, browse to your newly created project template and select **Open**.
|
||||
|
||||
3. Create your new virtual app package. The settings saved with your template are automatically applied.
|
||||
|
||||
### Related articles
|
||||
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
- [Learn about Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server)
|
||||
- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
|
||||
- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
|
||||
- [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
@ -1,156 +0,0 @@
|
||||
---
|
||||
title: Creating and managing App-V virtualized applications (Windows 10/11)
|
||||
description: Create and manage App-V virtualized applications to monitor and record the installation process for an application to be run as a virtualized application.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# Creating and managing App-V virtualized applications
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
After you've properly deployed the Microsoft Application Virtualization (App-V) sequencer, you can use it to monitor and record the installation and setup process for an application to be run as a virtualized application.
|
||||
|
||||
For more information about configuring the App-V sequencer, sequencing best practices, and an example of creating and updating a virtual application, see the [Microsoft Application Virtualization 5.0 Sequencing Guide](https://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V%205.0%20Sequencing%20Guide.docx).
|
||||
|
||||
>[!NOTE]
|
||||
>The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated.
|
||||
|
||||
## Sequencing an application
|
||||
|
||||
You can use the App-V Sequencer to perform the following tasks:
|
||||
|
||||
- Create virtual packages that can be deployed to computers running the App-V client.
|
||||
- Upgrade existing packages. You can expand an existing package onto the computer running the sequencer and then upgrade the application to create a newer version.
|
||||
- Edit configuration information associated with an existing package. For example, you can add a shortcut or modify a file type association.
|
||||
|
||||
> [!NOTE]
|
||||
>You must create shortcuts and save them to an available network location to allow roaming. If a shortcut is created and saved in a private location, the package must be published locally to the computer running the App-V client.
|
||||
|
||||
- Convert existing virtual packages.
|
||||
|
||||
The sequencer uses the **%TMP% \\ Scratch** or **%TEMP% \\ Scratch** directory and the **Temp** directory to store temporary files during sequencing. On the computer that runs the sequencer, you should configure these directories with free disk space equivalent to the estimated application installation requirements. Configuring the temp directories and the Temp directory on different hard drive partitions can help improve performance during sequencing.
|
||||
|
||||
When you use the sequencer to create a new virtual application, the following listed files are created. These files comprise the App-V package.
|
||||
|
||||
- **.msi file**. This Windows Installer (.msi) file is created by the sequencer and is used to install the virtual package on target computers.
|
||||
- **Report.xml file**. In this file, the sequencer saves all issues, warnings, and errors that were discovered during sequencing. It displays the information after the package has been created. You can us this report for diagnosing and troubleshooting.
|
||||
- **.appv file**. This file is the virtual application file.
|
||||
- **Deployment configuration file**. The deployment configuration file determines how the virtual application will be deployed to target computers.
|
||||
- **User configuration file**. The user configuration file determines how the virtual application will run on target computers.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You must configure the %TMP% and %TEMP% folders that the package converter uses to be a secure location and directory. A secure location is only accessible by an administrator. Additionally, when you sequence the package, you should either save the package to a secure location or make sure that no other user is allowed to log in during the conversion and monitoring process.
|
||||
|
||||
The **Options** dialog box in the sequencer console contains the following tabs:
|
||||
|
||||
- **General**. Use this tab to enable Microsoft Updates to run during sequencing. Select **Append Package Version to Filename** to configure the sequence to add a version number to the virtualized package that is being sequenced. Select **Always trust the source of Package Accelerators** to create virtualized packages using a package accelerator without being prompted for authorization.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Package Accelerators created using App-V 4.6 are not supported by App-V.
|
||||
|
||||
- **Parse Items**. This tab displays the associated file path locations that will be parsed or tokenized into in the virtual environment. Tokens are useful for adding files using the **Package Files** tab in **Advanced Editing**.
|
||||
- **Exclusion Items**. Use this tab to specify which folders and directories shouldn't be monitored during sequencing. To add local application data that is saved in the Local App Data folder in the package, click **New** and specify the location and the associated **Mapping Type**. This option is required for some packages.
|
||||
|
||||
App-V supports applications that include Microsoft Windows Services. If an application includes a Windows service, the service will be included in the sequenced virtual package as long as it's installed while being monitored by the sequencer. If a virtual application creates a Windows service when it initially runs, then after installation, the application must be run while the sequencer is monitoring for the Windows Service to be included in the package. Only services running under the Local System account are supported. Services configured for AutoStart or Delayed AutoStart are started before the first virtual application in a package runs inside the package’s Virtual Environment. Windows Services that are configured to be started on demand by an application are started when the virtual application inside the package starts the Service via API call.
|
||||
|
||||
- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
|
||||
- [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md)
|
||||
- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
|
||||
|
||||
## App-V shell extension support
|
||||
|
||||
App-V supports shell extensions. Shell extensions will be detected and embedded in the package during sequencing.
|
||||
|
||||
Shell extensions are automatically embedded in the package during the sequencing process. When the package is published, the shell extension gives users the same functionality as if the application were locally installed.
|
||||
|
||||
### Requirements for using shell extensions
|
||||
|
||||
- Packages that contain embedded shell extensions must be published globally. The application requires no extra setup or configuration on the client to enable the shell extension functionality.
|
||||
- The “bitness” of the application, Sequencer, and App-V client must match, or the shell extensions won’t work. For example:
|
||||
- The version of the application is 64-bit.
|
||||
- The Sequencer is running on a 64-bit computer.
|
||||
- The package is being delivered to a 64-bit App-V client computer.
|
||||
|
||||
The following table lists the supported shell extensions:
|
||||
|
||||
|Handler|Description|
|
||||
|---|---|
|
||||
|Context menu handler|Adds menu items to the context menu. It's called before the context menu is displayed.|
|
||||
|Drag-and-drop handler|Controls the action where right-click, drag and drop, and modifies the context menu that appears.|
|
||||
|Drop target handler|Controls the action after a data object is dragged and dropped over a drop target such as a file.|
|
||||
|Data object handler|Controls the action after a file is copied to the clipboard or dragged and dropped over a drop target. It can provide more clipboard formats to the drop target.|
|
||||
|Property sheet handler|Replaces or adds pages to the property sheet dialog box of an object.|
|
||||
|Infotip handler|Allows retrieving flags and infotip information for an item and displaying it inside a pop-up tooltip upon mouse hover.|
|
||||
|Column handler|Allows creating and displaying custom columns in **Windows Explorer Details view**. It can be used to extend sorting and grouping.|
|
||||
|Preview handler|Enables a preview of a file to be displayed in the Windows Explorer Preview pane.|
|
||||
|
||||
## Copy on Write (CoW) file extension support
|
||||
|
||||
Copy on write (CoW) file extensions allow App-V to dynamically write to specific locations contained in the virtual package while it's being used.
|
||||
|
||||
The following list shows the file types that can exist in a virtual package under the VFS directory, since App-V 5.1, but which can't be updated on the computer running the App-V client. All other files and directories can be modified.
|
||||
|
||||
- .com
|
||||
- .exe
|
||||
- .dll
|
||||
- .ocx
|
||||
|
||||
## Modifying an existing virtual application package
|
||||
|
||||
You can use the sequencer to modify an existing package. The computer on which you do this modification should match the chip architecture of the computer you used to create the application. For example, if you initially sequenced a package using a computer running a 64-bit operating system, you should modify the package using a computer running a 64-bit operating system.
|
||||
|
||||
For more information, see [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md).
|
||||
|
||||
## Creating a project template
|
||||
|
||||
An App-V project template (.appvt) file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings. App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you can't use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V project template:
|
||||
|
||||
A template can specify and store multiple settings as follows:
|
||||
|
||||
- **Advanced Monitoring Options**. Enables Microsoft Update to run during monitoring. Saves allow local interaction option settings
|
||||
- **General Options**. Enables the use of **Windows Installer**, **Append Package Version to Filename**.
|
||||
- **Exclusion Items.** Contains the Exclusion pattern list.
|
||||
|
||||
Starting with Windows 10 version 1703, running the **new-appvsequencerpackage** or **update-appvsequencepackage** cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If you attempt to load another template through the *_TemplateFilePath_* parameter while already having an auto-saved template, the customization value from the parameter will override the auto-saved template.
|
||||
|
||||
For more information, see [How to Create and Use a Project Template](appv-create-and-use-a-project-template.md).
|
||||
|
||||
## Creating a package accelerator
|
||||
|
||||
>[!NOTE]
|
||||
>Package accelerators created using a previous version of App-V must be recreated using App-V.
|
||||
|
||||
You can use App-V package accelerators to automatically generate a new virtual application package. After you've successfully created a package accelerator, you can reuse and share the package accelerator.
|
||||
|
||||
In some situations, to create the package accelerator, you might have to install the application locally on the computer that runs the sequencer. In such cases, you should first try to create the package accelerator with the installation media. If multiple missing files are required, you should install the application locally to the computer that runs the sequencer, and then create the package accelerator.
|
||||
|
||||
After you've successfully created a Package Accelerator, you can reuse and share the Package Accelerator. Creating App-V Package Accelerators is an advanced task. Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied.
|
||||
|
||||
For more information, see the following articles:
|
||||
|
||||
- [How to Create a Package Accelerator](appv-create-a-package-accelerator.md)
|
||||
- [How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md)
|
||||
|
||||
## Sequencer error reporting
|
||||
|
||||
The App-V Sequencer can detect common sequencing issues during sequencing. The **Installation Report** page at the end of the sequencing wizard displays diagnostic messages categorized into **Errors**, **Warnings**, and **Info** depending on the severity of the issue.
|
||||
|
||||
You can also find additional information about sequencing errors using the Windows Event Viewer.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
@ -1,40 +0,0 @@
|
||||
---
|
||||
title: How to customize virtual application extensions for a specific AD group by using the Management Console (Windows 10/11)
|
||||
description: How to customize virtual application extensions for a specific AD group by using the Management Console.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
# How to customize virtual applications extensions for a specific AD group by using the Management Console
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to customize the virtual application extensions for an Active Directory (AD) group.
|
||||
|
||||
## Customize virtual applications extensions for an AD group
|
||||
|
||||
1. To view the package that you want to configure, open the App-V Management Console. To view the configuration assigned to a given user group, select the package, then right-click the package name and select **Edit active directory access**. Alternatively, select the package and select **EDIT** in the **AD ACCESS** pane.
|
||||
|
||||
2. To customize an AD group, you can find the group from the list of **AD Entities with Access**. Then, using the drop-down box in the **Assigned Configuration** pane, select **Custom**, and then select **EDIT**.
|
||||
|
||||
3. To disable all extensions for a given application, clear **ENABLE**.
|
||||
|
||||
To add a new shortcut for the selected application, right-click the application in the **SHORTCUTS** pane, and select **Add new shortcut**. To remove a shortcut, right-click the application in the **SHORTCUTS** pane and select **Remove Shortcut**. To edit an existing shortcut, right-click the application and select **Edit Shortcut**.
|
||||
|
||||
4. To view any other application extensions, select **Advanced**, and select **Export Configuration**. Enter a filename and select **Save**. You can view all application extensions that are associated with the package using the configuration file.
|
||||
|
||||
5. To edit additional application extensions, modify the configuration file and select **Import and Overwrite this Configuration**. Select the modified file and select **Open**. In the dialog, select **Overwrite** to complete the process.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
@ -1,34 +0,0 @@
|
||||
---
|
||||
title: How to delete a connection group (Windows 10/11)
|
||||
description: Learn how to delete an existing App-V connection group in the App-V Management Console and where to find information about managing connection groups.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# How to delete a connection group
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to delete an existing App-V connection group.
|
||||
|
||||
## Delete a connection group
|
||||
|
||||
1. Open the App-V Management Console and select **CONNECTION GROUPS**.
|
||||
|
||||
2. Right-click the connection group to be removed and select **delete**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
- [Managing connection groups](appv-managing-connection-groups.md)
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
title: How to delete a package in the Management Console (Windows 10/11)
|
||||
description: Learn how to delete a package in the App-V Management Console and where to find information about operations for App-V.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# How to delete a package in the Management Console
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to delete an App-V package.
|
||||
|
||||
## Delete a package in the Management Console
|
||||
|
||||
1. To view the package you want to delete, open the App-V Management Console and select **Packages**. Select the package to be removed.
|
||||
|
||||
2. Select or right-click the package, then select **Delete** to remove the package.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
@ -1,188 +0,0 @@
|
||||
---
|
||||
title: How to Deploy the App-V Databases by Using SQL Scripts (Windows 10/11)
|
||||
description: Learn how to use SQL scripts to install the App-V databases and upgrade the App-V databases to a later version.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# How to deploy the App-V databases by using SQL scripts
|
||||
|
||||
>Applies to: Windows Server 2016
|
||||
|
||||
Use the following instructions to use SQL scripts, rather than the Windows Installer, to:
|
||||
|
||||
* Install the App-V databases
|
||||
* Upgrade the App-V databases to a later version
|
||||
|
||||
>[!NOTE]
|
||||
>If you have already deployed an App-V 5.0 SP3 database or later, the SQL scripts are not required to upgrade to App-V for Windows.
|
||||
|
||||
## How to install the App-V databases by using SQL scripts
|
||||
|
||||
1. Before you install the database scripts, review and keep a copy of the App-V license terms. By running the database scripts, you are agreeing to the license terms. If you do not accept them, you should not use this software.
|
||||
|
||||
2. Copy **appv\_server\_setup.exe** from the App-V release media to a temporary location.
|
||||
|
||||
3. From a command prompt, run **appv\_server\_setup.exe** and specify a temporary location for extracting the database scripts.
|
||||
|
||||
```sql
|
||||
appv\_server\_setup.exe /layout c:\\_<temporary location path>_
|
||||
```
|
||||
|
||||
4. Browse to the temporary location that you created, open the extracted **DatabaseScripts** folder, and review the appropriate **readme.txt** file for instructions:
|
||||
|
||||
| Database | Location of readme.txt file to use|
|
||||
|---|---|
|
||||
| Management database | ManagementDatabase subfolder |
|
||||
| Reporting database | ReportingDatabase subfolder |
|
||||
|
||||
>[!CAUTION]
|
||||
>The readme.txt file in the ManagementDatabase subfolder is out of date. The information in the updated readme files below is the most current and should supersede the readme information provided in the **DatabaseScripts** folders.
|
||||
|
||||
>[!IMPORTANT]
|
||||
> The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3.
|
||||
|
||||
### Updated management database README file content
|
||||
|
||||
```syntax
|
||||
***********************************************************************************************************
|
||||
Before you install and use the Application Virtualization Database Scripts, you must:
|
||||
|
||||
- Review the license terms.
|
||||
- Print and retain a copy of the license terms for your records.
|
||||
|
||||
By running the App-V you agree to such license terms. If you do not accept them, do not use the software.
|
||||
***********************************************************************************************************
|
||||
|
||||
Steps to install "AppVManagement" schema in SQL SERVER.
|
||||
|
||||
## PREREQUISITES:
|
||||
|
||||
1. Review the installation package. The following files MUST exist:
|
||||
|
||||
SQL files
|
||||
---------
|
||||
Database.sql
|
||||
CreateTables.sql
|
||||
CreateStoredProcs.sql
|
||||
UpdateTables.sql
|
||||
Permissions.sql
|
||||
|
||||
2. Ensure the target SQL Server instance and SQL Server Agent service are running.
|
||||
|
||||
3. If you are not running the scripts directly on the server, ensure the
|
||||
necessary SQL Server client software is installed and available from
|
||||
the specified location. Specifically, the "osql" command must be supported for these scripts to run.
|
||||
|
||||
## PREPARATION:
|
||||
|
||||
1. Review the database.sql file and modify as necessary. Although the
|
||||
defaults are likely sufficient, it is suggested that the following
|
||||
settings be reviewed:
|
||||
|
||||
DATABASE - ensure name is satisfactory - default is "AppVManagement".
|
||||
|
||||
2. Review the Permissions.sql file and provide all the necessary account information
|
||||
for setting up read and write access on the database. Note: Default settings in the file will not work.
|
||||
|
||||
## INSTALLATION:
|
||||
|
||||
1. Run the database.sql against the "master" database. Your user
|
||||
credential must have the ability to create databases.
|
||||
This script will create the database.
|
||||
|
||||
2. Run the following scripts against the "AppVManagement" database using the
|
||||
same account as above in order.
|
||||
|
||||
CreateTables.sql
|
||||
CreateStoredProcs.sql
|
||||
UpdateTables.sql
|
||||
Permissions.sql
|
||||
|
||||
```
|
||||
|
||||
### Updated reporting database README file content
|
||||
|
||||
```syntax
|
||||
***********************************************************************************************************
|
||||
Before you install and use the Application Virtualization Database Scripts, you must:
|
||||
|
||||
- Review the license terms.
|
||||
- Print and retain a copy of the license terms for your records.
|
||||
|
||||
By running the App-V you agree to such license terms. If you do not accept them, do not use the software.
|
||||
***********************************************************************************************************
|
||||
|
||||
Steps to install "AppVReporting" schema in SQL SERVER.
|
||||
|
||||
## PREREQUISITES:
|
||||
|
||||
1. Review the installation package. The following files MUST exist:
|
||||
|
||||
SQL files
|
||||
---------
|
||||
Database.sql
|
||||
UpgradeDatabase.sql
|
||||
CreateTables.sql
|
||||
CreateReportingStoredProcs.sql
|
||||
CreateStoredProcs.sql
|
||||
CreateViews.sql
|
||||
Permissions.sql
|
||||
ScheduleReportingJob.sql
|
||||
|
||||
2. Ensure the target SQL Server instance and SQL Server Agent service are running.
|
||||
|
||||
3. If you are not running the scripts directly on the server, ensure the
|
||||
necessary SQL Server client software is installed and executable from
|
||||
the location you have chosen. Specifically, the "osql" command must be supported for these scripts to run.
|
||||
|
||||
## PREPARATION:
|
||||
|
||||
1. Review the database.sql file and modify as necessary. Although the
|
||||
defaults are likely sufficient, it is suggested that the following
|
||||
settings be reviewed:
|
||||
|
||||
DATABASE - ensure name is satisfactory - default is "AppVReporting".
|
||||
|
||||
2. Review the Permissions.sql file and provide all the necessary account information
|
||||
for setting up read and write access on the database. Note: Default settings
|
||||
in the file will not work.
|
||||
|
||||
3. Review the ScheduleReportingJob.sql file and make sure that the stored proc schedule
|
||||
time is acceptable. The default stored proc schedule time is at 12.01 AM (line 84).
|
||||
If this time is not suitable, you can change this to a more suitable time. The time is in the format HHMMSS.
|
||||
|
||||
## INSTALLATION:
|
||||
|
||||
1. Run the database.sql against the "master" database. Your user
|
||||
credential must have the ability to create databases.
|
||||
This script will create the database.
|
||||
|
||||
2. If upgrading the database, run UpgradeDatabase.sql This will upgrade database schema.
|
||||
|
||||
2. Run the following scripts against the "AppVReporting" database using the
|
||||
same account as above in order.
|
||||
|
||||
CreateTables.sql
|
||||
CreateReportingStoredProcs.sql
|
||||
CreateStoredProcs.sql
|
||||
CreateViews.sql
|
||||
Permissions.sql
|
||||
ScheduleReportingJob.sql
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
* [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
* [How to deploy the App-V Server](appv-deploy-the-appv-server.md)
|
||||
@ -1,49 +0,0 @@
|
||||
---
|
||||
title: How to deploy App-V packages using electronic software distribution (Windows 10/11)
|
||||
description: Learn how to use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# How to deploy App-V packages using electronic software distribution
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients.
|
||||
|
||||
For component requirements and options for using an ESD to deploy App-V packages, see [Planning to deploy App-V with an electronic software distribution system](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
Use one of the following methods to publish packages to App-V client computers with an ESD:
|
||||
|
||||
- Use the functionality in a third-party ESD.
|
||||
- Install the application on the target client computer with the associated Windows Installer (.msi) file that's created when you initially sequence the application. The .msi file contains the associated App-V package file information used to configure a package and copies the required package files to the client.
|
||||
- Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using Windows PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).
|
||||
|
||||
| Method | Description |
|
||||
|---|---|
|
||||
| Functionality provided by a third-party ESD | Use the functionality in a third-party ESD.|
|
||||
| Stand-alone Windows Installer | Install the application on the target client computer by using the associated Windows Installer (.msi) file that is created when you initially sequence an application. The Windows Installer file contains the associated App-V package file information used to configure a package and copies the required package files to the client. |
|
||||
| Windows PowerShell | Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using Windows PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).|
|
||||
|
||||
## Deploy App-V packages with an ESD
|
||||
|
||||
1. Install the App-V Sequencer on a computer in your environment. For more information about installing the sequencer, see [How to install the Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
2. Use the App-V Sequencer to create a virtual application. To learn more about creating virtual applications, see [Creating and managing App-V virtualized applications](appv-creating-and-managing-virtualized-applications.md).
|
||||
|
||||
3. After you create the virtual application, deploy the package by using your ESD solution.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
@ -1,526 +0,0 @@
|
||||
---
|
||||
title: How to Deploy the App-V Server Using a Script (Windows 10/11)
|
||||
description: 'Learn how to deploy the App-V server by using a script (appv_server_setup.exe) from the command line.'
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# How to deploy the App-V server using a script
|
||||
|
||||
>Applies to: Windows Server 2016
|
||||
|
||||
In order to complete the **appv_server_setup.exe** server setup successfully using the command line, you must specify and combine multiple parameters.
|
||||
|
||||
## To install the App-V server using a script
|
||||
|
||||
Use the following lists and tables for more information about installing the App-V server using the command line.
|
||||
|
||||
The information in the following lists and tables can also be accessed through the command line by entering the following command: ```appv\_server\_setup.exe /?```.
|
||||
|
||||
## How to use common parameters to install the Management server and Management database on a local machine
|
||||
|
||||
The following examples will show you how to install the Management server and database on a local machine.
|
||||
|
||||
### Parameters for a default instance of Microsoft SQL Server for a new installation on a local machine
|
||||
|
||||
To use the default instance of Microsoft SQL Server, use the following parameters:
|
||||
|
||||
* */MANAGEMENT_SERVER*
|
||||
* */MANAGEMENT_ADMINACCOUNT*
|
||||
* */MANAGEMENT_WEBSITE_NAME*
|
||||
* */MANAGEMENT_WEBSITE_PORT*
|
||||
* */DB_PREDEPLOY_MANAGEMENT*
|
||||
* */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT*
|
||||
* */MANAGEMENT_DB_NAME*
|
||||
|
||||
### Parameters for a custom instance of Microsoft SQL Server for a new installation on a local machine
|
||||
|
||||
To use a custom instance of Microsoft SQL Server, use the following parameters:
|
||||
|
||||
* */MANAGEMENT_SERVER*
|
||||
* */MANAGEMENT_ADMINACCOUNT*
|
||||
* */MANAGEMENT_WEBSITE_NAME*
|
||||
* */MANAGEMENT_WEBSITE_PORT*
|
||||
* */DB_PREDEPLOY_MANAGEMENT*
|
||||
* */MANAGEMENT_DB_CUSTOM_SQLINSTANCE*
|
||||
* */MANAGEMENT_DB_NAME*
|
||||
|
||||
### Example parameters for using a custom instance of Microsoft SQL Server for a new installation on a local machine
|
||||
|
||||
```SQL
|
||||
/appv_server_setup.exe /QUIET
|
||||
/MANAGEMENT_SERVER
|
||||
/MANAGEMENT_ADMINACCOUNT="Domain\AdminGroup"
|
||||
/MANAGEMENT_WEBSITE_NAME="Microsoft AppV Management Service"
|
||||
/MANAGEMENT_WEBSITE_PORT="8080"
|
||||
/DB_PREDEPLOY_MANAGEMENT
|
||||
/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
|
||||
/MANAGEMENT_DB_NAME="AppVManagement"
|
||||
```
|
||||
|
||||
## How to use common parameters to install the Management server using an existing Management database on a local machine
|
||||
|
||||
The following examples will show you how to install the Management server on a local machine with an existing Management database.
|
||||
|
||||
### Default instance of Microsoft SQL Server for installation with an existing Management database on a local machine
|
||||
|
||||
To use the default instance of Microsoft SQL Server, use the following parameters:
|
||||
|
||||
* */MANAGEMENT_SERVER*
|
||||
* */MANAGEMENT_ADMINACCOUNT*
|
||||
* */MANAGEMENT_WEBSITE_NAME*
|
||||
* */MANAGEMENT_WEBSITE_PORT*
|
||||
* */EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL*
|
||||
* */EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT*
|
||||
* */EXISTING_MANAGEMENT_DB_NAME*
|
||||
|
||||
### Custom instance of Microsoft SQL Server for installation with an existing Management database on a local machine
|
||||
|
||||
To use a custom instance of Microsoft SQL Server, use these parameters:
|
||||
|
||||
* */MANAGEMENT_SERVER*
|
||||
* */MANAGEMENT_ADMINACCOUNT*
|
||||
* */MANAGEMENT_WEBSITE_NAME*
|
||||
* */MANAGEMENT_WEBSITE_PORT*
|
||||
* */EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL*
|
||||
* */EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE*
|
||||
* */EXISTING_MANAGEMENT_DB_NAME*
|
||||
|
||||
### Example parameters for using a custom instance of Microsoft SQL Server for installation with an existing Management database on a local machine
|
||||
|
||||
```SQL
|
||||
/appv_server_setup.exe /QUIET
|
||||
/MANAGEMENT_SERVER
|
||||
/MANAGEMENT_ADMINACCOUNT="Domain\AdminGroup"
|
||||
/MANAGEMENT_WEBSITE_NAME="Microsoft AppV Management Service"
|
||||
/MANAGEMENT_WEBSITE_PORT="8080"
|
||||
/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL
|
||||
/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE ="SqlInstanceName"
|
||||
/EXISTING_MANAGEMENT_DB_NAME ="AppVManagement"
|
||||
```
|
||||
|
||||
## How to install the Management server with an existing Management database on a remote machine
|
||||
|
||||
### Default instance of Microsoft SQL Server with an existing Management database on a remote machine
|
||||
|
||||
To use the default instance of Microsoft SQL Server, use the following parameters:
|
||||
|
||||
* */MANAGEMENT_SERVER*
|
||||
* */MANAGEMENT_ADMINACCOUNT*
|
||||
* */MANAGEMENT_WEBSITE_NAME*
|
||||
* */MANAGEMENT_WEBSITE_PORT*
|
||||
* */EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME*
|
||||
* */EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT*
|
||||
* */EXISTING_MANAGEMENT_DB_NAME*
|
||||
|
||||
### Custom instance of Microsoft SQL Server with an existing Management database on a remote machine
|
||||
|
||||
To use a custom instance of Microsoft SQL Server, use these parameters:
|
||||
|
||||
* */MANAGEMENT_SERVER*
|
||||
* */MANAGEMENT_ADMINACCOUNT*
|
||||
* */MANAGEMENT_WEBSITE_NAME*
|
||||
* */MANAGEMENT_WEBSITE_PORT*
|
||||
* */EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME*
|
||||
* */EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE*
|
||||
* */EXISTING_MANAGEMENT_DB_NAME*
|
||||
|
||||
### Example for using a custom instance of Microsoft SQL Server with an existing Management database on a remote machine
|
||||
|
||||
```SQL
|
||||
/appv_server_setup.exe /QUIET
|
||||
/MANAGEMENT_SERVER
|
||||
/MANAGEMENT_ADMINACCOUNT="Domain\AdminGroup"
|
||||
/MANAGEMENT_WEBSITE_NAME="Microsoft AppV Management Service"
|
||||
/MANAGEMENT_WEBSITE_PORT="8080"
|
||||
/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME="SqlServermachine.domainName"
|
||||
/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE ="SqlInstanceName"
|
||||
/EXISTING_MANAGEMENT_DB_NAME ="AppVManagement"
|
||||
```
|
||||
|
||||
## Installing the Management database and the Management Server on the same computer
|
||||
|
||||
The following examples will show you how to install the Management server and database on the same computer.
|
||||
|
||||
### Default instance of Microsoft SQL Server for installation on the same computer
|
||||
|
||||
To use the default instance of Microsoft SQL Server, use these parameters:
|
||||
|
||||
* */DB_PREDEPLOY_MANAGEMENT*
|
||||
* */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT*
|
||||
* */MANAGEMENT_DB_NAME*
|
||||
* */MANAGEMENT_SERVER_MACHINE_USE_LOCAL*
|
||||
* */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT*
|
||||
|
||||
### Custom instance of Microsoft SQL Server for installation on the same computer
|
||||
|
||||
To use a custom instance of Microsoft SQL Server, use these parameters:
|
||||
|
||||
* */DB_PREDEPLOY_MANAGEMENT*
|
||||
* */MANAGEMENT_DB_CUSTOM_SQLINSTANCE*
|
||||
* */MANAGEMENT_DB_NAME*
|
||||
* */MANAGEMENT_SERVER_MACHINE_USE_LOCAL*
|
||||
* */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT*
|
||||
|
||||
### Example for using a custom instance of Microsoft SQL Server for installation on the same computer
|
||||
|
||||
```SQL
|
||||
/appv_server_setup.exe /QUIET
|
||||
/DB_PREDEPLOY_MANAGEMENT
|
||||
/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
|
||||
/MANAGEMENT_DB_NAME="AppVManagement"
|
||||
/MANAGEMENT_SERVER_MACHINE_USE_LOCAL
|
||||
/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount"
|
||||
```
|
||||
|
||||
## Installing the Management database on a different computer than the Management server
|
||||
|
||||
The following examples will show you how to install the Management database and server on different computers.
|
||||
|
||||
### Default instance of Microsoft SQL Server for installing the Management database on a different computer than the Management server
|
||||
|
||||
To use the default instance of Microsoft SQL Server, use the following parameters:
|
||||
|
||||
* */DB_PREDEPLOY_MANAGEMENT*
|
||||
* */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT*
|
||||
* */MANAGEMENT_DB_NAME*
|
||||
* */MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT*
|
||||
* */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT*
|
||||
|
||||
### Custom instance of Microsoft SQL Server for installing the Management database on a different computer than the Management server
|
||||
|
||||
To use a custom instance of Microsoft SQL Server, use these parameters:
|
||||
|
||||
* */DB_PREDEPLOY_MANAGEMENT*
|
||||
* */MANAGEMENT_DB_CUSTOM_SQLINSTANCE*
|
||||
* */MANAGEMENT_DB_NAME*
|
||||
* */MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT*
|
||||
* */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT*
|
||||
|
||||
### Example for using a custom instance of Microsoft SQL Server for installing the Management database on a different computer than the Management server
|
||||
|
||||
```SQL
|
||||
/appv_server_setup.exe /QUIET
|
||||
/DB_PREDEPLOY_MANAGEMENT
|
||||
/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
|
||||
/MANAGEMENT_DB_NAME="AppVManagement"
|
||||
/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT="Domain\MachineAccount"
|
||||
/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount"
|
||||
```
|
||||
|
||||
## Installing the Publishing server
|
||||
|
||||
The following examples will show you how to install the Publishing server.
|
||||
|
||||
### Default instance of Microsoft SQL Server for installing the Publishing server
|
||||
|
||||
To use the default instance of Microsoft SQL Server, use the following parameters:
|
||||
|
||||
* */PUBLISHING_SERVER*
|
||||
* */PUBLISHING_MGT_SERVER*
|
||||
* */PUBLISHING_WEBSITE_NAME*
|
||||
* */PUBLISHING_WEBSITE_PORT*
|
||||
|
||||
### Example for installing the Publishing server
|
||||
|
||||
```SQL
|
||||
/appv_server_setup.exe /QUIET
|
||||
/PUBLISHING_SERVER
|
||||
/PUBLISHING_MGT_SERVER="http://ManagementServerName:ManagementPort"
|
||||
/PUBLISHING_WEBSITE_NAME="Microsoft AppV Publishing Service"
|
||||
/PUBLISHING_WEBSITE_PORT="8081"
|
||||
```
|
||||
|
||||
## Installing the Reporting server and Reporting database on a local machine
|
||||
|
||||
The following examples will show you how to install the Reporting server and database on a local machine.
|
||||
|
||||
### Default instance of Microsoft SQL Server for installing the Reporting server and Reporting database on a local machine
|
||||
|
||||
To use the default instance of Microsoft SQL Server, use the following parameters:
|
||||
|
||||
* */REPORTING_SERVER*
|
||||
* */REPORTING_WEBSITE_NAME*
|
||||
* */REPORTING_WEBSITE_PORT*
|
||||
* */DB_PREDEPLOY_REPORTING*
|
||||
* */REPORTING_DB_SQLINSTANCE_USE_DEFAULT*
|
||||
* */REPORTING_DB_NAME*
|
||||
|
||||
### Custom instance of Microsoft SQL Server for installing the Reporting server and Reporting database on a local machine
|
||||
|
||||
To use a custom instance of Microsoft SQL Server, use these parameters:
|
||||
|
||||
* */REPORTING_SERVER*
|
||||
* */REPORTING_ADMINACCOUNT*
|
||||
* */REPORTING_WEBSITE_NAME*
|
||||
* */REPORTING_WEBSITE_PORT*
|
||||
* */DB_PREDEPLOY_REPORTING*
|
||||
* */REPORTING_DB_CUSTOM_SQLINSTANCE*
|
||||
* */REPORTING_DB_NAME*
|
||||
|
||||
### Example for using a custom instance of Microsoft SQL Server for installing the Reporting server and Reporting database on a local machine
|
||||
|
||||
```SQL
|
||||
/appv_server_setup.exe /QUIET
|
||||
/REPORTING_SERVER
|
||||
/REPORTING_WEBSITE_NAME="Microsoft AppV Reporting Service"
|
||||
/REPORTING_WEBSITE_PORT="8082"
|
||||
/DB_PREDEPLOY_REPORTING
|
||||
/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
|
||||
/REPORTING_DB_NAME="AppVReporting"
|
||||
```
|
||||
|
||||
## Installing the Reporting server using an existing Reporting database on a local machine
|
||||
|
||||
The following examples will show you how to install the reporting machine on a local machine with an existing Reporting database.
|
||||
|
||||
### Default instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a local machine
|
||||
|
||||
To use the default instance of Microsoft SQL Server, use the following parameters:
|
||||
|
||||
* */REPORTING_SERVER*
|
||||
* */REPORTING_WEBSITE_NAME*
|
||||
* */REPORTING_WEBSITE_PORT*
|
||||
* */EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL*
|
||||
* */EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT*
|
||||
* */EXISTING_REPORTING_DB_NAME*
|
||||
|
||||
### Custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a local machine
|
||||
|
||||
To use a custom instance of Microsoft SQL Server, use these parameters:
|
||||
|
||||
* */REPORTING_SERVER*
|
||||
* */REPORTING_ADMINACCOUNT*
|
||||
* */REPORTING_WEBSITE_NAME*
|
||||
* */REPORTING_WEBSITE_PORT*
|
||||
* */EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL*
|
||||
* */EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE*
|
||||
* */EXISTING_REPORTING_DB_NAME*
|
||||
|
||||
### Example for using a custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a local machine
|
||||
|
||||
```SQL
|
||||
/appv_server_setup.exe /QUIET
|
||||
/REPORTING_SERVER
|
||||
/REPORTING_WEBSITE_NAME="Microsoft AppV Reporting Service"
|
||||
/REPORTING_WEBSITE_PORT="8082"
|
||||
/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL
|
||||
/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
|
||||
/EXITING_REPORTING_DB_NAME="AppVReporting"
|
||||
```
|
||||
|
||||
## Installing the Reporting server using an existing Reporting database on a remote machine
|
||||
|
||||
The following examples will show you how to install the Reporting server and on a remote machine with an existing database.
|
||||
|
||||
### Default instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a remote machine
|
||||
|
||||
To use the default instance of Microsoft SQL Server, use the following parameters:
|
||||
|
||||
* */REPORTING_SERVER*
|
||||
* */REPORTING_WEBSITE_NAME*
|
||||
* */REPORTING_WEBSITE_PORT*
|
||||
* */EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME*
|
||||
* */EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT*
|
||||
* */EXISTING_REPORTING_DB_NAME*
|
||||
|
||||
### Custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a remote machine
|
||||
|
||||
To use a custom instance of Microsoft SQL Server, use these parameters:
|
||||
|
||||
* */REPORTING_SERVER*
|
||||
* */REPORTING_ADMINACCOUNT*
|
||||
* */REPORTING_WEBSITE_NAME*
|
||||
* */REPORTING_WEBSITE_PORT*
|
||||
* */EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME*
|
||||
* */EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE*
|
||||
* */EXISTING_REPORTING_DB_NAME*
|
||||
|
||||
### Example using a custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a remote machine
|
||||
|
||||
```SQL
|
||||
/appv_server_setup.exe /QUIET
|
||||
/REPORTING_SERVER
|
||||
/REPORTING_WEBSITE_NAME="Microsoft AppV Reporting Service"
|
||||
/REPORTING_WEBSITE_PORT="8082"
|
||||
/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME="SqlServerMachine.DomainName"
|
||||
/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
|
||||
/EXITING_REPORTING_DB_NAME="AppVReporting"
|
||||
```
|
||||
|
||||
## Installing the Reporting database on the same computer as the Reporting server
|
||||
|
||||
The following examples will show you how to install the Reporting database and server on the same computer.
|
||||
|
||||
### Default instance of Microsoft SQL Server for installing the Reporting database on the same computer as the Reporting server
|
||||
|
||||
To use the default instance of Microsoft SQL Server, use the following parameters:
|
||||
|
||||
* */DB_PREDEPLOY_REPORTING*
|
||||
* */REPORTING_DB_SQLINSTANCE_USE_DEFAULT*
|
||||
* */REPORTING_DB_NAME*
|
||||
* */REPORTING_SERVER_MACHINE_USE_LOCAL*
|
||||
* */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT*
|
||||
|
||||
### Custom instance of Microsoft SQL Server for installing the Reporting database on the same computer as the Reporting server
|
||||
|
||||
To use a custom instance of Microsoft SQL Server, use these parameters:
|
||||
|
||||
* */DB_PREDEPLOY_REPORTING*
|
||||
* */REPORTING_DB_CUSTOM_SQLINSTANCE*
|
||||
* */REPORTING_DB_NAME*
|
||||
* */REPORTING_SERVER_MACHINE_USE_LOCAL*
|
||||
* */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT*
|
||||
|
||||
### Example for using a custom instance of Microsoft SQL Server for installing the Reporting database on the same computer as the Reporting server
|
||||
|
||||
```SQL
|
||||
/appv_server_setup.exe /QUIET
|
||||
/DB_PREDEPLOY_REPORTING
|
||||
/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
|
||||
/REPORTING_DB_NAME="AppVReporting"
|
||||
/REPORTING_SERVER_MACHINE_USE_LOCAL
|
||||
/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount"
|
||||
```
|
||||
|
||||
## Installing the Reporting database on a different computer than the Reporting server
|
||||
|
||||
The following examples will show you how to install the Reporting database and server on different computers.
|
||||
|
||||
### Default instance of Microsoft SQL Server for installing the Reporting database on a different computer than the Reporting server
|
||||
|
||||
To use the default instance of Microsoft SQL Server, use the following parameters:
|
||||
|
||||
* */DB_PREDEPLOY_REPORTING*
|
||||
* */REPORTING_DB_SQLINSTANCE_USE_DEFAULT*
|
||||
* */REPORTING_DB_NAME*
|
||||
* */REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT*
|
||||
* */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT*
|
||||
|
||||
### Custom instance of Microsoft SQL Server for installing the Reporting database on a different computer than the Reporting server
|
||||
|
||||
To use a custom instance of Microsoft SQL Server, use these parameters:
|
||||
|
||||
* */DB_PREDEPLOY_REPORTING*
|
||||
* */REPORTING_DB_CUSTOM_SQLINSTANCE*
|
||||
* */REPORTING_DB_NAME*
|
||||
* */REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT*
|
||||
* */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT*
|
||||
|
||||
### Example for using a custom instance of Microsoft SQL Server for installing the Reporting database on a different computer than the Reporting server
|
||||
|
||||
```SQL
|
||||
/appv_server_setup.exe /QUIET
|
||||
/DB_PREDEPLOY_REPORTING
|
||||
/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
|
||||
/REPORTING_DB_NAME="AppVReporting"
|
||||
/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT="Domain\MachineAccount"
|
||||
/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount"
|
||||
```
|
||||
|
||||
## Parameter definitions
|
||||
|
||||
* [General parameters](#parameter-definitions-for-general-parameters)
|
||||
* [Management Server installation parameters](#parameter-definitions-for-management-server-installation-parameters)
|
||||
* [Management Server Database parameters](#parameter-definitions-for-the-management-server-database)
|
||||
* [Publishing Server installation parameters](#parameter-definitions-for-publishing-server-installation-parameters)
|
||||
* [Reporting Server parameters](#parameter-definitions-for-reporting-server)
|
||||
* [Parameters for using an existing Reporting Server database](#parameters-for-using-an-existing-reporting-server-database)
|
||||
* [Reporting Server database installation parameters](#parameter-definitions-for-reporting-server-database-installation)
|
||||
* [Parameters for using an existing Management Server database](#parameters-for-using-an-existing-management-server-database)
|
||||
|
||||
### Parameter definitions for general parameters
|
||||
|
||||
| Parameter | Description |
|
||||
|-----------|-------------|
|
||||
| */QUIET* | Specifies silent install. |
|
||||
| */UNINSTALL* | Specifies an uninstall. |
|
||||
| */LAYOUT* | Specifies layout action. This extracts the MSIs and script files to a folder without installing the actual product. No value is expected. |
|
||||
| */LAYOUTDIR* | Specifies the layout directory with a string. For example, ```/LAYOUTDIR="C:\Application Virtualization Server"```. |
|
||||
| */INSTALLDIR* | Specifies the installation directory with a string. For example, ```/INSTALLDIR="C:\Program Files\Application Virtualization\Server"```. |
|
||||
| */MUOPTIN* | Enables Microsoft Update. No value is expected. |
|
||||
| */ACCEPTEULA* | Accepts the license agreement. This is required for an unattended installation. For example, ```/ACCEPTEULA``` or ```/ACCEPTEULA=1```. |
|
||||
|
||||
### Parameter definitions for Management Server installation parameters
|
||||
|
||||
| Parameter | Description |
|
||||
|-----------|-------------|
|
||||
| */MANAGEMENT_SERVER* | Specifies that the management server will be installed. No value is expected. |
|
||||
| */MANAGEMENT_ADMINACCOUNT* | Specifies the account that will be allowed administrator access to the management server. This account can be an individual user account or a group. For example, ```/MANAGEMENT_ADMINACCOUNT="mydomain\admin"```. If **/MANAGEMENT_SERVER** isn't specified, this parameter will be ignored.|
|
||||
| */MANAGEMENT_WEBSITE_NAME* | Specifies name of the website that will be created for the management service. For example, ```/MANAGEMENT_WEBSITE_NAME="Microsoft App-V Management Service"``` |
|
||||
| */MANAGEMENT_WEBSITE_PORT* | Specifies the port number that will be used by the management service will use. For example, ```/MANAGEMENT_WEBSITE_PORT=82```. |
|
||||
|
||||
### Parameter definitions for the Management Server Database
|
||||
|
||||
| Parameter | Description |
|
||||
|-----------|-------------|
|
||||
| */DB\_PREDEPLOY\_MANAGEMENT* | Specifies that the management database will be installed. You must have sufficient database permissions to complete this installation. No value is expected. |
|
||||
| */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT* | Indicates that the default SQL instance should be used. No value is expected. |
|
||||
| */MANAGEMENT_DB_CUSTOM_SQLINSTANCE* | Specifies the name of the custom SQL instance that should be used to create a new database. For example, ```/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this parameter will be ignored. |
|
||||
| */MANAGEMENT_DB_NAME* | Specifies the name of the new management database that should be created. For example, ```/MANAGEMENT_DB_NAME="AppVMgmtDB"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. |
|
||||
| */MANAGEMENT_SERVER_MACHINE_USE_LOCAL* | Indicates if the management server that will be accessing the database is installed on the local server. This is a switch parameter, so no value is expected. |
|
||||
| */MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT* | Specifies the machine account of the remote machine that the management server will be installed on. For example, ```/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT="domain\computername"```. |
|
||||
| */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT* | Indicates the Administrator account that will be used to install the management server. For example, ```/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT ="domain\alias"```. |
|
||||
|
||||
### Parameter definitions for Publishing Server installation parameters
|
||||
|
||||
| Parameter | Description |
|
||||
|-----------|-------------|
|
||||
| */PUBLISHING_SERVER* | Specifies that the publishing server will be installed. No value is expected. |
|
||||
| */PUBLISHING_MGT_SERVER* | Specifies the URL to Management Service the Publishing server will connect to. For example, ```http://<management server name>;<Management server port number>```. If **/PUBLISHING_SERVER** isn't used, this parameter will be ignored. |
|
||||
| */PUBLISHING_WEBSITE_NAME* | Specifies name of the website that will be created for the publishing service. For example, ```/PUBLISHING_WEBSITE_NAME="Microsoft App-V Publishing Service"```. |
|
||||
| */PUBLISHING_WEBSITE_PORT* | Specifies the port number used by the publishing service. For example, ```/PUBLISHING_WEBSITE_PORT=83```. |
|
||||
|
||||
### Parameter definitions for Reporting Server
|
||||
|
||||
| Parameter | Description |
|
||||
|-----------|-------------|
|
||||
| */REPORTING_SERVER* | Specifies that the Reporting Server will be installed. No value is expected. |
|
||||
| */REPORTING_WEBSITE_NAME* | Specifies name of the website that will be created for the Reporting Service. For example, ```/REPORTING_WEBSITE_NAME="Microsoft App-V ReportingService"```. |
|
||||
| */REPORTING_WEBSITE_PORT* | Specifies the port number that the Reporting Service will use. For example, ```/REPORTING_WEBSITE_PORT=82```. |
|
||||
|
||||
### Parameters for using an existing Reporting Server database
|
||||
|
||||
| Parameter | Description |
|
||||
|-----------|-------------|
|
||||
| */EXISTING\_REPORTING\_DB_SQL_SERVER_USE_LOCAL* | Indicates that the Microsoft SQL Server is installed on the local server. This is a switch parameter, so no value is expected. |
|
||||
| */EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME* | Specifies the name of the remote computer that SQL Server is installed on. Takes a string. For example, ```/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME="mycomputer1"```. |
|
||||
| */EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT* | Indicates that the default SQL instance is to be used. This is a switch parameter, so no value is expected. |
|
||||
| */EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE* | Specifies the name of the custom SQL instance that should be used. Takes a string. For example, ```/EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. |
|
||||
| */EXISTING_REPORTING_DB_NAME* | Specifies the name of the existing Reporting database that should be used. Takes a string. For example, ```/EXISTING_REPORTING_DB_NAME="AppVReporting"```. |
|
||||
|
||||
### Parameter definitions for Reporting Server database installation
|
||||
|
||||
| Parameter | Description |
|
||||
|-----------|-------------|
|
||||
| */DB\_PREDEPLOY\_REPORTING* | Specifies that the Reporting Database will be installed. DBA permissions are required for this installation. No value is expected. |
|
||||
| */REPORTING_DB_SQLINSTANCE_USE_DEFAULT* | Specifies the name of the custom SQL instance that should be used. Takes a string. For example, ```/REPORTING_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. |
|
||||
| */REPORTING_DB_NAME* | Specifies the name of the new Reporting database that should be created. Takes a string. For example, ```/REPORTING_DB_NAME="AppVMgmtDB"```. |
|
||||
| */REPORTING_SERVER_MACHINE_USE_LOCAL* | Indicates that the Reporting server that will be accessing the database is installed on the local server. This is a switch parameter, so no value is expected. |
|
||||
| */REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT* | Specifies the machine account of the remote machine that the Reporting server will be installed on. Takes a string. For example, ```/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT = "domain\computername"```. |
|
||||
| */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT* | Indicates the Administrator account that will be used to install the App-V Reporting Server. Takes a string. For example, ```/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT = "domain\alias"```. |
|
||||
|
||||
### Parameters for using an existing Management Server database
|
||||
|
||||
| Parameter | Description |
|
||||
|-----------|-------------|
|
||||
| */EXISTING\_MANAGEMENT\_DB_SQL_SERVER_USE_LOCAL* | Indicates that the SQL Server is installed on the local server. Switch parameter so no value is expected. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this variable will be ignored. |
|
||||
| */EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME* | Specifies the name of the remote computer that SQL Server is installed on. Takes a string. For example, ```/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME="mycomputer1"```. |
|
||||
| */EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT* | Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this variable will be ignored. |
|
||||
| */EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE* | Specifies the name of the custom SQL instance that will be used. For example, ```/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE="AppVManagement"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. |
|
||||
| */EXISTING_MANAGEMENT_DB_NAME* | Specifies the name of the existing management database that should be used. For example, ```/EXISTING_MANAGEMENT_DB_NAME="AppVMgmtDB"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. |
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
* [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
@ -1,115 +0,0 @@
|
||||
---
|
||||
title: How to Deploy the App-V Server (Windows 10/11)
|
||||
description: Use these instructions to deploy the Application Virtualization (App-V) Server in App-V for Windows 10/11.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# How to Deploy the App-V Server (new installation)
|
||||
|
||||
>Applies to: Windows Server 2016
|
||||
|
||||
## Before you start
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released.
|
||||
|
||||
* Ensure that you’ve installed required software. See [App-V prerequisites](appv-prerequisites.md).
|
||||
* Review the server section of [App-V security considerations](appv-security-considerations.md).
|
||||
* Specify a port where each component will be hosted.
|
||||
* Add firewall rules to allow incoming requests to access the specified ports.
|
||||
* If you use SQL scripts instead of the Windows Installer to set up the Management database or Reporting database, you must run the required SQL scripts before installing the Management Server or Reporting Server. See [How to deploy the App-V databases by using SQL scripts](appv-deploy-appv-databases-with-sql-scripts.md).
|
||||
|
||||
## Installing the App-V server
|
||||
|
||||
1. Download the App-V server components. All five App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from either of the following locations:
|
||||
|
||||
* The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download the MDOP ISO package from this site.
|
||||
* The [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx) if you're using [Windows client for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home).
|
||||
|
||||
2. Copy the App-V server installation files to the computer on which you want to install it.
|
||||
|
||||
3. Start the App-V server installation by right-clicking and running **appv\_server\_setup.exe** as an administrator, and then click **Install**.
|
||||
|
||||
4. Review and accept the license terms, and choose whether to enable Microsoft updates.
|
||||
|
||||
5. On the **Feature Selection** page, select all components listed in the following table.
|
||||
|
||||
| Component | Description |
|
||||
|---|---|
|
||||
| Management server | Provides overall management functionality for the App-V infrastructure. |
|
||||
| Management database | Facilitates database predeployments for App-V management. |
|
||||
| Publishing server | Provides hosting and streaming functionality for virtual applications. |
|
||||
| Reporting server | Provides App-V reporting services. |
|
||||
| Reporting database | Facilitates database predeployments for App-V reporting. |
|
||||
|
||||
6. On the **Installation Location** page, accept the default location where the selected components will be installed, or change the location by typing a new path on the **Installation Location** line.
|
||||
|
||||
7. On the initial **Create New Management Database** page, configure the **Microsoft SQL Server instance** and **Management Server database** by selecting the appropriate option below.
|
||||
|
||||
| Method | What you need to do |
|
||||
|---|---|
|
||||
| You are using a custom Microsoft SQL Server instance. | Select **Use the custom instance**, then specify the instance name.<br/>Use the format **INSTANCENAME**. The assumed installation location is the local computer.<br/>Not supported: A server name using the format **ServerName**\\**INSTANCE**.|
|
||||
| You are using a custom database name. | Select **Custom configuration** and type the database name.<br/>The database name must be unique, or the installation will fail.|
|
||||
|
||||
8. On the **Configure** page, accept the default value, **Use this local computer**.
|
||||
|
||||
> [!NOTE]
|
||||
> If you're installing the Management server and Management database side-by-side, the appropriate options are selected by default and cannot be changed.
|
||||
|
||||
9. On the initial **Create New Reporting Database** page, configure the **Microsoft SQL Server instance** and **Reporting Server database** by selecting the appropriate option below.
|
||||
|
||||
| Method | What you need to do |
|
||||
|---|---|
|
||||
| You are using a custom Microsoft SQL Server instance. | Select **Use the custom instance**, and type the name of the instance.<br/>Use the format **INSTANCENAME**. The assumed installation location is the local computer.<br/>Not supported: A server name using the format **ServerName**\\**INSTANCE**.|
|
||||
| You are using a custom database name. | Select **Custom configuration** and type the database name.<br/>The database name must be unique, or the installation will fail.|
|
||||
|
||||
10. On the **Configure** page, accept the default value: **Use this local computer**.
|
||||
|
||||
> [!NOTE]
|
||||
> If you're installing the Management server and Management database side-by-side, the appropriate options are selected by default and cannot be changed.
|
||||
|
||||
11. On the **Configure** (Management Server Configuration) page, specify the following:
|
||||
|
||||
| Item to configure | Description and examples |
|
||||
|---|---|
|
||||
| Specify AD group | Specify the AD group with sufficient permissions to manage the App-V environment. Example: MyDomain\MyUser<br><br/>After installation, you can add users or groups on the management console. However, global security groups and Active Directory Domain Services (AD DS) distribution groups are not supported. You must use <strong>Domain local</strong> or <strong>Universal</strong> groups to perform this action.|
|
||||
|Website name | Specify the custom name that will be used to run the publishing service.<br>If you do not have a custom name, you don't have to change it.|
|
||||
|Port binding | Specify a unique port number that will be used by App-V. Example: **12345**<br>Ensure that the port specified is not being used by another website. |
|
||||
|
||||
12. On the **Configure Publishing Server Configuration** page, specify the following:
|
||||
|
||||
| Item to configure | Description and examples |
|
||||
|---|---|
|
||||
| Specify the management service URL | Example: http:<span></span>//localhost:12345 |
|
||||
| Website name | Specify the custom website name that will be used to run the publishing service. <br>If you do not have a custom name, do not make any changes. |
|
||||
| Port binding | Specify a unique port number that will be used by App-V. Example: 54321<br>Ensure that the port specified is not being used by another website. |
|
||||
|
||||
13. On the **Reporting Server** page, specify the following:
|
||||
|
||||
| Item to configure | Description and examples |
|
||||
|---|---|
|
||||
| Website name | Specify the custom name that will be used to run the Reporting Service. <br>If you do not have a custom name, do not make any changes. |
|
||||
| Port binding | Specify a unique port number that will be used by App-V. Example: 55555<br/>Ensure that the port specified is not being used by another website.|
|
||||
|
||||
14. To start the installation, click **Install** on the **Ready** page, and then click **Close** on the **Finished** page.
|
||||
|
||||
15. To verify that the setup completed successfully, open a web browser, and type the following URL with the bracketed variables adjusted according to your specifications in the earlier steps:
|
||||
|
||||
`http://<Management server machine name>:<Management service port number>/console.html`
|
||||
|
||||
Example: `http://localhost:12345/console.html`. If the installation succeeded, the App-V Management console will display with no errors.
|
||||
|
||||
## Related articles
|
||||
|
||||
* [Deploying App-V](appv-deploying-appv.md)
|
||||
* [How to install the management and reporting databases on separate computers from the management and reporting services](appv-install-the-management-and-reporting-databases-on-separate-computers.md)
|
||||
* [How to install the publishing server on a remote computer](appv-install-the-publishing-server-on-a-remote-computer.md)
|
||||
* [How to deploy the App-V server using a script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
@ -1,50 +0,0 @@
|
||||
---
|
||||
title: Deploying App-V (Windows 10/11)
|
||||
description: App-V supports several different deployment options. Learn how to complete App-V deployment at different stages in your App-V deployment.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# Deploying App-V for Windows client
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
App-V supports several different deployment options. Review this article for information about the tasks that you must complete at different stages in your deployment.
|
||||
|
||||
## App-V Deployment Information
|
||||
|
||||
* [Deploying the App-V Sequencer and configuring the client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
This section describes how to install the App-V sequencer used to virtualize applications, and how to enable the App-V client that runs on target computers to facilitate virtualized packages.
|
||||
* [Deploying the App-V server](appv-deploying-the-appv-server.md)
|
||||
|
||||
This section provides information about installing the App-V management, publishing, database, and reporting severs.
|
||||
* [App-V deployment checklist](appv-deployment-checklist.md)
|
||||
|
||||
This section provides a deployment checklist that can be used to assist with installing App-V.
|
||||
|
||||
The following sections describe how to use App-V to deliver Microsoft Office as a virtualized application to computers in your organization.
|
||||
|
||||
* [Deploying Microsoft Office 2016 by using App-V](appv-deploying-microsoft-office-2016-with-appv.md)
|
||||
* [Deploying Microsoft Office 2013 by using App-V](appv-deploying-microsoft-office-2013-with-appv.md)
|
||||
* [Deploying Microsoft Office 2010 by using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
|
||||
|
||||
## Other App-V deployment resources
|
||||
|
||||
* [Application Virtualization (App-V) overview](appv-for-windows.md)
|
||||
* [Getting started with App-V](appv-getting-started.md)
|
||||
* [Planning for App-V](appv-planning-for-appv.md)
|
||||
* [Operations for App-V](appv-operations.md)
|
||||
* [Troubleshooting App-V](appv-troubleshooting.md)
|
||||
* [Technical reference for App-V](appv-technical-reference.md)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,78 +0,0 @@
|
||||
---
|
||||
title: Deploying Microsoft Office 2010 by Using App-V
|
||||
description: Create Office 2010 packages for Microsoft Application Virtualization (App-V) using the App-V Sequencer or the App-V Package Accelerator.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# Deploying Microsoft Office 2010 by Using App-V
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can create Office 2010 packages for Microsoft Application Virtualization (App-V) using one of the following methods:
|
||||
|
||||
* Application Virtualization (App-V) Sequencer
|
||||
* Application Virtualization (App-V) Package Accelerator
|
||||
|
||||
## App-V support for Office 2010
|
||||
|
||||
The following table shows the App-V versions, methods of Office package creation, supported licensing, and supported deployments for Office 2010.
|
||||
|
||||
|Supported item|Support level|
|
||||
|---|---|
|
||||
|Package creation|- Sequencing<br>- Package Accelerator<br>- Office Deployment Kit|
|
||||
|Supported licensing|Volume Licensing|
|
||||
|Supported deployments|- Desktop<br>- Personal VDI<br>- RDS|
|
||||
|
||||
## Creating Office 2010 App-V using the sequencer
|
||||
|
||||
Sequencing Office 2010 is one of the main methods for creating an Office 2010 package on App-V. For more information, see [How to Sequence a New Application with App-V 5.0](/microsoft-desktop-optimization-pack/appv-v5/how-to-sequence-a-new-application-with-app-v-50-beta-gb18030).
|
||||
|
||||
## Deploying the Microsoft Office package for App-V
|
||||
|
||||
You can deploy Office 2010 packages by using any of the following App-V deployment methods:
|
||||
|
||||
* Microsoft Configuration Manager
|
||||
* App-V server
|
||||
* Stand-alone through Windows PowerShell commands
|
||||
|
||||
## Office App-V package management and customization
|
||||
|
||||
Office 2010 packages can be managed like any other App-V packages through known package management mechanisms. No special instructions are needed, for example, to add, publish, unpublish, or remove Office packages.
|
||||
|
||||
## Microsoft Office integration with Windows
|
||||
|
||||
The following table provides a full list of supported integration points for Office 2010.
|
||||
|
||||
(POPULATE THE THIRD COLUMN)
|
||||
|
||||
|Extension Point|Description|Office 2010|
|
||||
|---|---|---|
|
||||
|Lync meeting Join Plug-in for Firefox and Chrome|User can join Lync meetings from Firefox and Chrome||
|
||||
|Sent to OneNote Print Driver|User can print to OneNote|Yes|
|
||||
|OneNote Linked Notes|OneNote Linked Notes||
|
||||
|Send to OneNote Internet Explorer Add-In|User can send to OneNote from IE||
|
||||
|Firewall Exception for Lync and Outlook|Firewall Exception for Lync and Outlook||
|
||||
|MAPI Client|Native apps and add-ins can interact with virtual Outlook through MAPI||
|
||||
|SharePoint Plugin for Firefox|User can use SharePoint features in Firefox||
|
||||
|Mail Control Panel Applet|User gets the mail control panel applet in Outlook|Yes|
|
||||
|Primary Interop Assemblies|Support managed add-ins||
|
||||
|Office Document Cache Handler|Allows Document Cache for Office applications||
|
||||
|Outlook Protocol Search handler|User can search in Outlook|Yes|
|
||||
|Active X Controls:<br>- Groove.SiteClient<br>- PortalConnect.PersonalSite<br>- SharePoint.openDocuments<br>- SharePoint.ExportDatabase<br>- SharePoint.SpreadSheetLauncher<br>- SharePoint.StssyncHander<br>- SharePoint.DragUploadCtl<br>- SharePoint.DragDownloadCtl<br>- Sharpoint.OpenXMLDocuments<br> - Sharepoint.ClipboardCtl<br>- WinProj.Activator<br>- Name.NameCtrl<br>- STSUPld.CopyCtl<br>- CommunicatorMeetingJoinAx.JoinManager<br>- LISTNET.Listnet<br>- OneDrive Pro Browser Helper|Active X Control. <br><br>For more information about ActiveX controls, see the [ActiveX Control API Reference](/previous-versions/office/developer/sharepoint-2010/ms440037(v=office.14)).||
|
||||
|OneDrive Pro Icon Overlays|Windows explorer shell icon overlays when users look at folders OneDrive Pro folders||
|
||||
|
||||
### Connection Groups
|
||||
|
||||
* [Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
|
||||
### Dynamic Configuration
|
||||
|
||||
* [About App-V Dynamic Configuration](appv-dynamic-configuration.md)
|
||||
@ -1,430 +0,0 @@
|
||||
---
|
||||
title: Deploying Microsoft Office 2013 by Using App-V (Windows 10/11)
|
||||
description: Use Application Virtualization (App-V) to deliver Microsoft Office 2013 as a virtualized application to computers in your organization.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# Deploying Microsoft Office 2013 by Using App-V
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the information in this article to use Application Virtualization (App-V) to deliver Microsoft Office 2013 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md). To successfully deploy Office 2013 with App-V, you need to be familiar with Office 2013 and App-V.
|
||||
|
||||
## What to know before you start
|
||||
|
||||
Before you deploy Office 2013 with App-V, review the following planning information.
|
||||
|
||||
### Supported Office versions and Office coexistence
|
||||
|
||||
The following table will direct you to more information about which versions of Office App-V supports and how to run App-V with coexisting versions of Office.
|
||||
|
||||
|Information to review|Description|
|
||||
|---|---|
|
||||
|[Supported versions of Microsoft Office](appv-planning-for-using-appv-with-office.md#supported-versions-of-microsoft-office)|- Supported versions of Office<br>- Supported deployment types like desktop, personal Virtual Desktop Infrastructure (VDI), and pooled VDI<br>- Office licensing options.|
|
||||
|[Planning for using App-V with coexisting versions of Office](appv-planning-for-using-appv-with-office.md#before-you-implement-office-coexistence)|Considerations for installing different versions of Office on the same computer.|
|
||||
|
||||
### Packaging, publishing, and deployment requirements
|
||||
|
||||
Before you deploy Office with App-V, review the following requirements.
|
||||
|
||||
|Task|Requirement|
|
||||
|---|---|
|
||||
|Packaging|All Office applications you wish to deploy to users must be in a single package.<br>In App-V and later, you must use the Office Deployment Tool to create packages. The Sequencer doesn't support package creation.<br>If you're deploying Microsoft Visio 2013 and Microsoft Project 2013 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2013 and Project 2013 with Office](#deploying-visio-2013-and-project-2013-with-office).|
|
||||
|Publishing|You can only publish one Office package per client computer.<br>You must publish the Office package globally, not to the user.|
|
||||
|Deploying Microsoft 365 Apps for enterprise, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer using Remote Desktop Services.|You must enable [shared computer activation](/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus).<br>You don’t need to use shared computer activation if you’re deploying a volume licensed product, such as Office Professional Plus 2013, Visio Professional 2013, or Project Professional 2013.|
|
||||
|
||||
### Excluding Office applications from a package
|
||||
|
||||
The following table describes the recommended methods for excluding specific Office applications from a package.
|
||||
|
||||
|Task|Details|
|
||||
|---|---|
|
||||
|Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool.|Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.<br>For more information, see [ExcludeApp element](/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ad=US&rs=en-US&ui=en-US#excludeapp-element).|
|
||||
|Modify the **DeploymentConfig.xml** file|Modify the **DeploymentConfig.xml** file after creating the package. This file contains the default package settings for all users on a computer running the App-V Client.<br>For more information, see [Disabling Office 2013 applications](#disabling-office-2013-applications).|
|
||||
|
||||
## Creating an Office 2013 package for App-V with the Office Deployment Tool
|
||||
|
||||
Complete the following steps to create an Office 2013 package for App-V or later.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>In App-V and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
|
||||
|
||||
### Review prerequisites for using the Office Deployment Tool
|
||||
|
||||
Before you start, ensure that the computer on which you're installing the Office Deployment Tool has the following prerequisites fulfilled:
|
||||
|
||||
|Prerequisite|Description|
|
||||
|---|---|
|
||||
|Prerequisite software|.NET Framework 4|
|
||||
|Supported operating systems|64-bit version of Windows 8 or later<br>64-bit version of Windows 7|
|
||||
|
||||
>[!NOTE]
|
||||
>In this topic, the term “Office 2013 App-V package” refers to subscription licensing and volume licensing.
|
||||
|
||||
### Create Office 2013 App-V packages using Office Deployment Tool
|
||||
|
||||
You create Office 2013 App-V packages with the Office Deployment Tool. The following instructions explain how to create an Office 2013 App-V package with Volume Licensing or Subscription Licensing.
|
||||
|
||||
Create Office 2013 App-V packages on 64-bit Windows computers. Once created, the Office 2013 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10/11 computers.
|
||||
|
||||
### Download the Office Deployment Tool
|
||||
|
||||
Office 2013 App-V Packages are created using the Office Deployment Tool, which generates an Office 2013 App-V Package. The App-V sequencer can't create or modify packages. To create a package:
|
||||
|
||||
1. Download the [Office 2013 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=36778).
|
||||
2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
|
||||
|
||||
Example: \\\\Server\\Office2013
|
||||
3. Check that a **setup.exe** and a **configuration.xml** file exist and are in the location you specified.
|
||||
|
||||
### Download Office 2013 applications
|
||||
|
||||
After you download the Office Deployment Tool, you can use it to get the latest Office 2013 applications. You can create the Office 2013 App-V package after getting all the Office applications.
|
||||
|
||||
The XML file included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.
|
||||
|
||||
1. **Customize the sample XML configuration file:** Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:
|
||||
|
||||
1. Open the sample XML file in Notepad or your favorite text editor.
|
||||
|
||||
2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2013 applications. The following example denotes a configuration.xml file:
|
||||
|
||||
```XML
|
||||
<Configuration>
|
||||
<Add SourcePath= ”\\Server\Office2013” OfficeClientEdition="32" >
|
||||
<Product ID="O365ProPlusRetail ">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
<Product ID="VisioProRetail">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
</Add>
|
||||
</Configuration>
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
>The configuration XML is a sample XML file. This file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file.
|
||||
|
||||
The previous example of an XML configuration file specifies that Office 2013 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2013, which is the location where Office applications will be saved to. The Product ID of the applications won't affect the final licensing of Office. Office 2013 App-V packages with various licensing can be created from the same applications by specifying licensing in a later stage. For more information, see [Customizable attributes and elements of the XML file](#customizable-attributes-and-elements-of-the-xml-file), later in this topic.
|
||||
|
||||
After editing the configuration.xml file to specify the desired product, languages, and also the location that the Office 2013 applications will be saved onto, you can save the configuration file, for example, as Customconfig.xml.
|
||||
2. **Download the applications into the specified location:** Use an elevated command prompt and a 64-bit operating system to download the Office 2013 applications that will later be converted into an App-V package. An example command is:
|
||||
|
||||
```PowerShell
|
||||
\\server\Office2013\setup.exe /download \\server\Office2013\Customconfig.xml
|
||||
```
|
||||
|
||||
The following table describes each element of the command:
|
||||
|
||||
|Element|Description|
|
||||
|---|---|
|
||||
|```\\server\Office2013```|This network share location is the one that contains the Office Deployment Tool and the custom Configuration.xml file, **Customconfig.xml**.|
|
||||
|```setup.exe```|This element is the Office Deployment Tool.|
|
||||
|```/download```|This element downloads the Office 2013 applications that you specify in the **Customconfig.xml** file. These bits can be later converted in an Office 2013 App-V package with Volume Licensing.|
|
||||
|```\\server\Office2013\Customconfig.xml```|This element passes the XML configuration file required to complete the download process. In this example, the file used is **Customconfig.xml**. After the download command is used, Office applications should be found in the location specified in the XML configuration file, which in this example is ```\\Server\Office2013```.|
|
||||
|
||||
#### Customizable attributes and elements of the XML file
|
||||
|
||||
|Input and description|Example|
|
||||
|---|---|
|
||||
|Add element:<br>Specifies the products and languages to include in the package.|N/A|
|
||||
|OfficeClientEdition (attribute of Add element):<br>Specifies the edition of Office 2013 product to use: 32-bit or 64-bit. The operation fails if **OfficeClientEdition** isn't set to a valid value.|```OfficeClientEdition="32"```<br>```OfficeClientEdition="64"```|
|
||||
|Product element:<br>Specifies the application. Project 2013 and Visio 2013 must be specified here as an added product to be included in the applications.|```Product ID="O365ProPlusRetail"```<br>```Product ID="VisioProRetail"```<br>```Product ID="ProjectProRetail"```<br>```Product ID="ProPlusVolume"```<br>```Product ID="ProjectProVolume"```|
|
||||
|Language element:<br>Specifies the language supported in the applications.|```Language ID="en-us"```|
|
||||
|Version (attribute of Add element):<br>Optional. Specifies a build to use for the package. Defaults to latest advertised build (as defined in v32.CAB at the Office source).|```15.1.2.3```|
|
||||
|SourcePath (attribute of Add element):<br>Specifies the location where the applications will be saved to.|```Sourcepath="\Server\Office2013”```|
|
||||
|
||||
### Convert the Office applications into an App-V package
|
||||
|
||||
After you download the Office 2013 applications through the Office Deployment Tool, use the Office Deployment Tool to convert them into an Office 2013 App-V package. You'll need to make sure to have the right procedure depending on your licensing model.
|
||||
|
||||
#### What you'll need to do
|
||||
|
||||
* Create the Office 2013 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8, and Windows 10/11 computers.
|
||||
* Create an Office App-V package for either the Subscription Licensing package or Volume Licensing by using the Office Deployment Tool, then modify the **Customconfig.xml** configuration file.
|
||||
|
||||
The following table summarizes the values you need to enter in the **Customconfig.xml** file for the licensing model you’re using. The steps in the sections that follow the table will specify the exact entries you need to make.
|
||||
|
||||
|Product ID|Volume Licensing|Subscription Licensing|
|
||||
|---|---|---|
|
||||
|Office 2013|ProPlusVolume|O365ProPlusRetail|
|
||||
|Office 2013 with Visio 2013|ProPlusVolume<br>VisioProVolume|O365ProPlusRetail<br>VisioProRetail|
|
||||
|Office 2013 with Visio 2013 and Project 2013|ProPlusVolume<br>VisioProVolume<br>ProjectProVolume|O365ProPlusRetail<br>VisioProRetail<br>ProjectProRetail|
|
||||
|
||||
#### How to convert the Office applications into an App-V package
|
||||
|
||||
1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
|
||||
|
||||
* **SourcePath**: Point to the Office applications downloaded earlier.
|
||||
* **ProductID**: Specify the type of licensing, as shown in the following examples:
|
||||
* Subscription Licensing:
|
||||
```XML
|
||||
<Configuration>
|
||||
<Add SourcePath= "\\server\Office 2013" OfficeClientEdition="32" >
|
||||
<Product ID="O365ProPlusRetail">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
<Product ID="VisioProRetail">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
</Add>
|
||||
</Configuration>
|
||||
```
|
||||
In this example, the following changes were made to create a package with Subscription licensing:
|
||||
|
||||
* **SourcePath** is the path, which was changed to point to the Office applications that were downloaded earlier.
|
||||
* **Product ID** for Office was changed to `O365ProPlusRetail`.
|
||||
* **Product ID** for Visio was changed to `VisioProRetail`.
|
||||
* Volume Licensing
|
||||
```XML
|
||||
<Configuration>
|
||||
<Add SourcePath= "\\Server\Office2013" OfficeClientEdition="32" >
|
||||
<Product ID="ProPlusVolume">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
<Product ID="VisioProVolume">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
</Add>
|
||||
</Configuration>
|
||||
```
|
||||
In this example, the following changes were made to create a package with Volume licensing:
|
||||
|
||||
* **SourcePath** is the source's path, which was changed to point to the Office applications that were downloaded earlier.
|
||||
* **Product ID** for Office was changed to `ProPlusVolume`.
|
||||
* **Product ID** for Visio was changed to `VisioProVolume`.
|
||||
* **ExcludeApp** (optional) lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.
|
||||
* **PACKAGEGUID** (optional)—By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.
|
||||
|
||||
An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users.
|
||||
|
||||
> [!NOTE]
|
||||
>Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
|
||||
2. Use the **/packager** command to convert the Office applications to an Office 2013 App-V package.
|
||||
|
||||
For example:
|
||||
|
||||
```PowerShell
|
||||
\\server\Office2013\setup.exe /packager \\server\Office2013\Customconfig.xml \\server\share\Office2013AppV
|
||||
```
|
||||
|
||||
In the example:
|
||||
|
||||
|Element|Description|
|
||||
|---|---|
|
||||
|```\\server\Office2013```|This network share location is the one that contains the Office Deployment Tool and the custom Configuration.xml file, which in this example is named **Customconfig.xml**.|
|
||||
|```setup.exe```|This element is the Office Deployment Tool.|
|
||||
|```/packager```|This element creates the Office 2013 App-V package with Volume Licensing as specified in the **Customconfig.xml** file.|
|
||||
|```\\server\Office2013\Customconfig.xml```|This element passes the configuration XML file, which in this example is named "Customconfig," that has been prepared for the packaging stage.|
|
||||
|```\\server\share\Office2013AppV```|This element specifies the location of the newly created Office App-V package.|
|
||||
|
||||
After you run the **/packager** command, the following folders will appear in the directory where you specified the package should be saved:
|
||||
|
||||
* **App-V Packages**, which contains an Office 2013 App-V package and two deployment configuration files.<br>
|
||||
* **WorkingDir**
|
||||
|
||||
> [!NOTE]
|
||||
>To troubleshoot any issues, see the log files in the %temp% directory (default).
|
||||
3. Verify that the Office 2013 App-V package works correctly:
|
||||
|
||||
1. Publish the Office 2013 App-V package that you created globally to a test computer and verify that the Office 2013 shortcuts appear.
|
||||
2. Start a few Office 2013 applications, such as Excel or Word, to test that your package is working as expected.
|
||||
|
||||
## Publishing the Office package for App-V
|
||||
|
||||
Use the following information to publish an Office package.
|
||||
|
||||
### Methods for publishing Office App-V packages
|
||||
|
||||
Deploy the App-V package for Office 2013 by using the same methods you use for any other package:
|
||||
|
||||
* Microsoft Configuration Manager
|
||||
* App-V Server
|
||||
* Stand-alone through Windows PowerShell commands
|
||||
|
||||
### Publishing prerequisites and requirements
|
||||
|
||||
|Prerequisite or requirement|Details|
|
||||
|---|---|
|
||||
|Enable Windows PowerShell scripting on the App-V clients.|To publish Office 2013 packages, you must run a script. Package scripts are disabled by default on App-V clients. To enable scripting, run the following Windows PowerShell command:<br>```Set-AppvClientConfiguration –EnablePackageScripts 1```|
|
||||
|Publish the Office 2013 package globally.|Extension points in the Office App-V package require installation at the computer level.<br>When you publish at the computer level, no prerequisite actions or redistributables are needed, and the Office 2013 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages.|
|
||||
|
||||
### How to publish an Office package
|
||||
|
||||
Run the following command to publish an Office package globally, with the bracketed value replaced by the path to the App-V package:
|
||||
|
||||
```PowerShell
|
||||
Add-AppvClientPackage <Path_to_AppV_Package> | Publish-AppvClientPackage –global
|
||||
```
|
||||
|
||||
* From the Web Management Console on the App-V Server, you can add permissions to a group of computers instead of to a user group to enable packages to be published globally to the computers in the corresponding group.
|
||||
|
||||
## Customizing and managing Office App-V packages
|
||||
|
||||
To manage your Office App-V packages, use the same operations as you would for any other package, but there are a few exceptions, as outlined in the following sections.
|
||||
|
||||
* [Enabling Office plug-ins by using connection groups](#enabling-office-plug-ins-by-using-connection-groups)
|
||||
* [Disabling Office 2013 applications](#disabling-office-2013-applications)
|
||||
* [Disabling Office 2013 shortcuts](#disabling-office-2013-shortcuts)
|
||||
* [Managing Office 2013 package upgrades](#managing-office-2013-package-upgrades)
|
||||
* [Managing Office 2013 licensing upgrades](#managing-office-2013-licensing-upgrades)
|
||||
* [Deploying Visio 2013 and Project 2013 with Office](#deploying-visio-2013-and-project-2013-with-office)
|
||||
|
||||
### Enabling Office plug-ins by using connection groups
|
||||
|
||||
Use the steps in this section to enable Office plug-ins with your Office package. To use Office plug-ins, you must use the App-V Sequencer to create a separate package that contains just the plug-ins. You can't use the Office Deployment Tool to create the plug-ins package. You then create a connection group that contains the Office package and the plug-ins package, as described in the following steps.
|
||||
|
||||
#### To enable plug-ins for Office App-V packages
|
||||
|
||||
1. Add a Connection Group through App-V Server, Microsoft Configuration Manager, or a Windows PowerShell cmdlet.
|
||||
2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2013 is installed on the computer being used to sequence the plug-in. It's a good idea to use Microsoft 365 Apps for enterprise (non-virtual) on the sequencing computer when you sequence Office 2013 plug-ins.
|
||||
3. Create an App-V package that includes the desired plug-ins.
|
||||
4. Add a Connection Group through App-V Server, Configuration Manager, or a Windows PowerShell cmdlet.
|
||||
5. Add the Office 2013 App-V package and the plug-ins package you sequenced to the Connection Group you created.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2013 App-V package first, then add the plug-in App-V package.
|
||||
6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match the global settings of the published Office 2013 App-V package.
|
||||
7. Verify that the Deployment Configuration File of the plug-in package has the same settings that the Office 2013 App-V package has.
|
||||
|
||||
Since the Office 2013 App-V package is integrated with the operating system, the plug-in package settings should match. You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as **Integrated** and that both **InProcessEnabled** and **OutOfProcessEnabled** match the settings of the Office 2013 App-V package you published.
|
||||
8. Open the Deployment Configuration File and set the value for **Objects Enabled** to **false**.
|
||||
9. If you made any changes to the Deployment Configuration file after sequencing, ensure that the plug-in package is published with the updated file.
|
||||
10. Ensure that the Connection Group you created is enabled onto your desired computer. The Connection Group created will likely “pend” if the Office 2013 App-V package is in use when the Connection Group is enabled. If that happens, you'll have to reboot to successfully enable the Connection Group.
|
||||
11. After you successfully publish both packages and enable the Connection Group, start the target Office 2013 application and verify that the plug-in you published and added to the Connection Group works as expected.
|
||||
|
||||
### Disabling Office 2013 applications
|
||||
|
||||
You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You don't have to re-sequence the application. When you change the Deployment Configuration File after the Office 2013 App-V package has been published, you'll save the changes, add the Office 2013 App-V package, then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 App-V Package applications.
|
||||
|
||||
>[!NOTE]
|
||||
>To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting. For more information, see [Reference for Click-to-Run configuration.xml file](/DeployOffice/configuration-options-for-the-office-2016-deployment-tool#excludeapp-element).
|
||||
|
||||
#### To disable an Office 2013 application
|
||||
|
||||
1. Open a Deployment Configuration File with a text editor such as **Notepad** and search for “Applications."
|
||||
2. Search for the Office application you want to disable, for example, Access 2013.
|
||||
3. Change the value of "Enabled" from "true" to "false."
|
||||
4. Save the Deployment Configuration File.
|
||||
5. Add the Office 2013 App-V Package with the new Deployment Configuration File.
|
||||
|
||||
``` XML
|
||||
<Application Id="[{AppVPackageRoot)]\officefl5\INFOPATH.EXE" Enabled="true">
|
||||
<VisualElements>
|
||||
<Name>InfoPath Filler 2013</Name>
|
||||
<Icon />
|
||||
<Description />
|
||||
</VisualElements>
|
||||
</Application>
|
||||
<Application Id="[{AppVPackageRoot}]\office15\lync.exe" Enabled="true">
|
||||
<VisualElements>
|
||||
<Name>Lync 2013</Name>
|
||||
<Icon />
|
||||
<Description />
|
||||
</VisualElements>
|
||||
</Application>
|
||||
<Application Id="[(AppVPackageRoot}]\office15\MSACCESS.EXE" Enabled="true">
|
||||
<VisualElements>
|
||||
<Name>Access 2013</Name>
|
||||
<Icon />
|
||||
<Description />
|
||||
</VisualElements>
|
||||
</Application>
|
||||
```
|
||||
6. Re-add the Office 2013 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 App-V Package applications.
|
||||
|
||||
### Disabling Office 2013 shortcuts
|
||||
|
||||
You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.
|
||||
|
||||
1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
|
||||
2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. For example, in the example below, delete the Microsoft Access shortcuts, while keeping the subsystems <shortcut> </shortcut> intact to disable the Microsoft Access shortcut.
|
||||
|
||||
```XML
|
||||
Shortcuts
|
||||
|
||||
-->
|
||||
<Shortcuts Enabled="true">
|
||||
<Extensions>
|
||||
<Extension Category="AppV.Shortcut">
|
||||
<Shortcut>
|
||||
<File>[{Common Programs}]\Microsoft Office 2013\Access 2013.lnk</File>
|
||||
<Target>[{AppvPackageRoot}])office15\MSACCESS.EXE</Target>
|
||||
<Icon>[{Windows}]\Installer\{90150000-000F-0000-0000-000000FF1CE)\accicons.exe.Ø.ico</Icon>
|
||||
<Arguments />
|
||||
<WorkingDirectory />
|
||||
<AppuserModelId>Microsoft.Office.MSACCESS.EXE.15</AppUserModelId>
|
||||
<AppUserModelExcludeFromShowInNewInstall>true</AppUserModelExcludeFromShowInNewInstall>
|
||||
<Description>Build a professional app quickly to manage data.</Description>
|
||||
<ShowCommand>l</ShowCommand>
|
||||
<ApplicationId>[{AppVPackageRoot}]\office15\MSACCESS.EXE</ApplicationId>
|
||||
</Shortcut>
|
||||
```
|
||||
3. Save the Deployment Configuration File.
|
||||
4. Republish Office 2013 App-V Package with new Deployment Configuration File.
|
||||
|
||||
Many more settings can be changed through modifying the Deployment Configuration for App-V packages, for example, file type associations, Virtual File System, and more. For additional information on how to use Deployment Configuration Files to change App-V package settings, refer to the additional resources section at the end of this document.
|
||||
|
||||
### Managing Office 2013 package upgrades
|
||||
|
||||
To upgrade an Office 2013 package, use the Office Deployment Tool. To upgrade a previously deployed Office 2013 package, perform the following steps.
|
||||
|
||||
#### How to upgrade a previously deployed Office 2013 package
|
||||
|
||||
1. Create a new Office 2013 package through the Office Deployment Tool that uses the most recent Office 2013 application software. The most recent Office 2013 bits can always be obtained through the download stage of creating an Office 2013 App-V Package. The newly created Office 2013 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
|
||||
|
||||
> [!NOTE]
|
||||
> Office App-V packages have two Version IDs:
|
||||
> * An Office 2013 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
|
||||
> * A second App-V Package Version ID, x.x.x.x for example, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2013 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect that the Office version itself has changed. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2013 package.
|
||||
2. Globally publish the newly created Office 2013 App-V Packages onto computers where you would like to apply the new updates. Since the new package has the same lineage of the older Office 2013 App-V Package, publishing the new package with the updates will only apply the new changes to the old package, and thus will be fast.
|
||||
3. Upgrades will be applied in the same manner of any globally published App-V Packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.
|
||||
|
||||
### Managing Office 2013 licensing upgrades
|
||||
|
||||
If a new Office 2013 App-V Package has a different license than the Office 2013 App-V Package currently deployed. For instance, the Office 2013 package deployed is a subscription based Office 2013 and the new Office 2013 package is Volume Licensing based, the following instructions must be followed to ensure smooth licensing upgrade:
|
||||
|
||||
#### How to upgrade an Office 2013 License
|
||||
|
||||
1. Unpublish the already deployed Office 2013 Subscription Licensing App-V package.
|
||||
2. Remove the unpublished Office 2013 Subscription Licensing App-V package.
|
||||
3. Restart the computer.
|
||||
4. Add the new Office 2013 App-V Package Volume Licensing.
|
||||
5. Publish the added Office 2013 App-V Package with Volume Licensing.
|
||||
|
||||
An Office 2013 App-V Package with your chosen licensing will be successfully deployed.
|
||||
|
||||
### Deploying Visio 2013 and Project 2013 with Office
|
||||
|
||||
This section describes the requirements and options for deploying Visio 2013 and Project 2013 with Office.
|
||||
|
||||
* **To package and publish Visio 2013 and Project 2013 with Office**: Include Visio 2013 and Project 2013 in the same package with Office. If you aren’t deploying Office, you can create a package that contains Visio and/or Project.
|
||||
* **To deploy Visio 2013 and Project 2013 to specific users**: Use one of the following methods:
|
||||
|
||||
|Goal|Method|
|
||||
|---|---|
|
||||
|Create two different packages and deploy each one to a different group of users|Create and deploy the following packages:<br>A package that contains only Office—deploy to computers whose users need only Office.<br>A package that contains Office, Visio, and Project—deploy to computers whose users need all three applications.|
|
||||
|Create just one package for the whole organization, or for users who share computers|Follow these steps:<br>1. Create a package that contains Office, Visio, and Project.<br>2. Deploy the package to all users.<br>3. Use [AppLocker](/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project.|
|
||||
|
||||
## Additional resources
|
||||
|
||||
### Additional resources for Office 2013 App-V Packages
|
||||
|
||||
* [Office 2013 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=36778)
|
||||
|
||||
### Additional resources for Connection Groups
|
||||
|
||||
* [Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
* [Connection groups on the App-V team blog](/archive/blogs/gladiator/app-v-5-more-on-connection-groups)
|
||||
|
||||
### Additional resources for Dynamic Configuration
|
||||
|
||||
* [About App-V Dynamic Configuration](appv-dynamic-configuration.md)
|
||||
@ -1,383 +0,0 @@
|
||||
---
|
||||
title: Deploying Microsoft Office 2016 by using App-V (Windows 10/11)
|
||||
description: Use Application Virtualization (App-V) to deliver Microsoft Office 2016 as a virtualized application to computers in your organization.
|
||||
author: aczechowski
|
||||
ms.service: windows-client
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: aaroncz
|
||||
ms.collection: must-keep
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-apps
|
||||
---
|
||||
|
||||
# Deploying Microsoft Office 2016 by using App-V
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the information in this article to use Application Virtualization (App-V) to deliver Microsoft Office 2016 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2013, see [Deploying Microsoft Office 2013 by using App-V](appv-deploying-microsoft-office-2013-with-appv.md). For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by using App-V](appv-deploying-microsoft-office-2010-wth-appv.md).
|
||||
|
||||
## What to know before you start
|
||||
|
||||
Before you deploy Office 2016 with App-V, review the following planning information.
|
||||
|
||||
### Supported Office versions and Office coexistence
|
||||
|
||||
Use the following table to get information about supported versions of Office and running coexisting versions of Office.
|
||||
|
||||
|Information to review|Description|
|
||||
|---|---|
|
||||
|[Supported versions of Microsoft Office](appv-planning-for-using-appv-with-office.md#supported-versions-of-microsoft-office)|Supported versions of Office and deployment types (for example, desktop, personal Virtual Desktop Infrastructure (VDI), and pooled VDI), and Office licensing options.|
|
||||
|[Planning for using App-V with coexisting versions of Office](appv-planning-for-using-appv-with-office.md#before-you-implement-office-coexistence)|Considerations for installing different versions of Office on the same computer.|
|
||||
|
||||
### Packaging, publishing, and deployment requirements
|
||||
|
||||
Before you deploy Office with App-V, review the following requirements.
|
||||
|
||||
|Task|Requirement|
|
||||
|-----------|-------------------|
|
||||
| Packaging. | All Office applications that you deploy to users must be in a single package.<br>In App-V 5.0 and later, you must use the Office Deployment Tool to create packages. The Sequencer doesn't support package creation.<br>If you're deploying Microsoft Visio 2016 and Microsoft Project 2016 at the same time as Office, you must put them all in the same package. For more information, see [Deploying Visio 2016 and Project 2016 with Office](#deploying-visio-2016-and-project-2016-with-office). |
|
||||
| Publishing. | You can only publish one Office package per client computer.<br>You must publish the Office package globally, not to the user. |
|
||||
| Deploying Microsoft 365 Apps for enterprise, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer with Remote Desktop Services. | You must enable [shared computer activation](/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus). |
|
||||
|
||||
### Excluding Office applications from a package
|
||||
|
||||
The following table describes the recommended methods for excluding specific Office applications from a package.
|
||||
|
||||
|Task|Details|
|
||||
|-------------|---------------|
|
||||
| Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool. | With this setting, you can exclude specific Office applications from the package that the Office Deployment Tool creates. For example, you can use this setting to create a package that contains only Microsoft Word.<br>For more information, see [ExcludeApp element](/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ad=US&rs=en-US&ui=en-US#excludeapp-element). |
|
||||
| Modify the DeploymentConfig.xml file | Modify the DeploymentConfig.xml file after the package has been created. This file contains the default package settings for all users on a computer that is running the App-V Client.<br>For more information, see [Disabling Office 2016 applications](#disabling-office-2016-applications). |
|
||||
|
||||
## Creating an Office 2016 package for App-V with the Office Deployment Tool
|
||||
|
||||
Complete the following steps to create an Office 2016 package for App-V.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>In App-V 5.0 and later, you must use the Office Deployment Tool to create a package. You can't use the Sequencer to create packages.
|
||||
|
||||
### Review prerequisites for using the Office Deployment Tool
|
||||
|
||||
The computer on which you're installing the Office Deployment Tool must have the following:
|
||||
|
||||
| Prerequisite | Description |
|
||||
|----------------------|--------------------|
|
||||
| Prerequisite software | .NET Framework 4 |
|
||||
| Supported operating systems | 64-bit version of Windows 10/11<br>64-bit version of Windows 8 or 8.1<br>64-bit version of Windows 7 |
|
||||
|
||||
>[!NOTE]
|
||||
>In this topic, the term “Office 2016 App-V package” refers to subscription licensing.
|
||||
|
||||
### Create Office 2016 App-V packages with the Office Deployment Tool
|
||||
|
||||
You create Office 2016 App-V packages by using the Office Deployment Tool. The following instructions explain how to create an Office 2016 App-V package with subscription licensing.
|
||||
|
||||
Create Office 2016 App-V packages on 64-bit Windows computers. Once created, the Office 2016 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10/11 computers.
|
||||
|
||||
### Download the Office Deployment Tool
|
||||
|
||||
Office 2016 App-V packages are created using the Office Deployment Tool, which generates an Office 2016 App-V Package. The package can't be created or modified through the App-V sequencer. To begin package creation, follow these steps:
|
||||
|
||||
1. Download the [Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You must use the Office 2016 Deployment Tool to create Office 2016 App-V Packages.
|
||||
2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
|
||||
|
||||
Example location: \\\\Server\\Office2016
|
||||
3. Check that the **setup.exe** and **configuration.xml** files exist and are in the location you specified.
|
||||
|
||||
### Download Office 2016 applications
|
||||
|
||||
After you download the Office Deployment Tool, you can use it to get the latest Office 2016 applications. After getting the Office applications, you create the Office 2016 App-V package.
|
||||
|
||||
The XML file included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.
|
||||
|
||||
1. **Customize the sample XML configuration file:** Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:
|
||||
1. Open the sample XML file in Notepad or your favorite text editor.
|
||||
2. With the sample **configuration.xml** file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2016 applications. The following is a basic example of the **configuration.xml** file:
|
||||
|
||||
```XML
|
||||
<Configuration>
|
||||
<Add SourcePath= ”\\Server\Office2016” OfficeClientEdition="32" >
|
||||
<Product ID="O365ProPlusRetail ">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
<Product ID="VisioProRetail">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
</Add>
|
||||
</Configuration>
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
>The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. To uncomment these lines, remove the ```<! - -``` from the beginning of the line, and the ```-- >``` from the end of the line.
|
||||
|
||||
The previous example of an XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office2016 location where Office applications will be saved. The Product ID of the applications won't affect Office's final licensing. You can create Office 2016 App-V packages with various licensing from the same applications by specifying licensing in a later stage. The following table summarizes the XML file's customizable attributes and elements:
|
||||
|
||||
| Input | Description | Example |
|
||||
|--------------|----------------------------|----------------|
|
||||
| Add element | Specifies which products and languages the package will include. | N/A |
|
||||
| **OfficeClientEdition** (attribute of **Add** element) | Specifies whether Office 2016 32-bit or 64-bit edition will be used. **OfficeClientEdition** must be set to a valid value for the operation to succeed. | `OfficeClientEdition="32"`<br>`OfficeClientEdition="64"` |
|
||||
| Product element | Specifies the application. Project 2016 and Visio 2016 must be specified here as added products to include them in the applications.<br>For more information about Product IDs, see [Product IDs that are supported by the Office Deployment Tool for Click-to-Run](/office365/troubleshoot/installation/product-ids-supported-office-deployment-click-to-run). | `Product ID ="O365ProPlusRetail"`<br>`Product ID ="VisioProRetail"`<br>`Product ID ="ProjectProRetail"` |
|
||||
| Language element | Specifies which language the applications support. | `Language ID="en-us"` |
|
||||
| Version (attribute of **Add** element) | Optional. Specifies which build the package will use.<br>Defaults to latest advertised build (as defined in v32.CAB at the Office source). | `16.1.2.3` |
|
||||
| SourcePath (attribute of **Add** element) | Specifies the location the applications will be saved to. | `Sourcepath = "\\Server\Office2016"` |
|
||||
| Channel (part of **Add** element) | Optional. Defines which channel will be used to update Office after installation.<br>The default is **Deferred** for Microsoft 365 Apps for enterprise and **Current** for Visio Pro for Office 365 and Project Desktop Client. <br>For more information about update channels, see [Overview of update channels for Microsoft 365 Apps for enterprise](/DeployOffice/overview-of-update-channels-for-office-365-proplus). | `Channel="Current"`<br>`Channel="Deferred"`<br>`Channel="FirstReleaseDeferred"`<br>`Channel="FirstReleaseCurrent"` |
|
||||
|
||||
After editing the **configuration.xml** file to specify the desired product, languages, and the location where the Office 2016 applications will be saved to, you can save the configuration file under a name of your choice, such as "Customconfig.xml."
|
||||
2. **Download the applications into the specified location:** Use an elevated command prompt and a 64-bit operating system to download the Office 2016 applications that will later be converted into an App-V package. An example command is:
|
||||
|
||||
`\\server\Office2016\setup.exe /download \\server\Office2016\Customconfig.xml`
|
||||
|
||||
The following table describes the example command's elements:
|
||||
|
||||
| Element | Description |
|
||||
|-------------------------------|--------------------------------------|
|
||||
| ```\\server\Office2016``` | This network share location is the one that contains the Office Deployment Tool and the custom **Configuration.xml** file, which in this example is **Customconfig.xml**. |
|
||||
| ``Setup.exe`` | This element is the Office Deployment Tool. |
|
||||
| ```/download``` | Downloads the Office 2016 applications that you specify in the **Customconfig.xml** file. |
|
||||
| ```\\server\Office2016\Customconfig.xml```| This element passes the XML configuration file required to complete the download process. In this example, the file used is **Customconfig.xml**. After the download command is used, Office applications should be found in the location specified in the configuration file, which in this example is ```\\Server\Office2016```. |
|
||||
|
||||
### Convert the Office applications into an App-V package
|
||||
|
||||
After you download the Office 2016 applications through the Office Deployment Tool, use the Office Deployment Tool to convert them into an Office 2016 App-V package. Complete the steps that correspond to your licensing model.
|
||||
|
||||
#### What you’ll need to do
|
||||
|
||||
* Create the Office 2016 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8 or 8.1, and Windows 10/11 computers.
|
||||
* Create an Office App-V package for either Subscription Licensing package by using the Office Deployment Tool, and then modify the **Customconfig.xml** configuration file.
|
||||
|
||||
The following table summarizes the values you need to enter in the **Customconfig.xml** file. The steps in the sections that follow the table will specify the exact entries you need to make.
|
||||
|
||||
>[!NOTE]
|
||||
>You can use the Office Deployment Tool to create App-V packages for Microsoft 365 Apps for enterprise. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported.
|
||||
|
||||
| Product ID | Subscription licensing |
|
||||
|---|---|
|
||||
| Office 2016| O365ProPlusRetail |
|
||||
| Office 2016 with Visio 2016 | O365ProPlusRetail<br>VisioProRetail |
|
||||
| Office 2016 with Visio 2016 and Project 2016 | O365ProPlusRetail<br>VisioProRetail<br>ProjectProRetail |
|
||||
|
||||
#### How to convert the Office applications into an App-V package
|
||||
|
||||
1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
|
||||
|
||||
* **SourcePath**: Change to the location where you saved the Office applications you downloaded during setup.
|
||||
* **ProductID**: Specify the type of licensing, as shown in the following example:
|
||||
|
||||
* Subscription Licensing:
|
||||
```XML
|
||||
<Configuration>
|
||||
<Add SourcePath= "\\server\Office 2016" OfficeClientEdition="32" >
|
||||
<Product ID="O365ProPlusRetail">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
<Product ID="VisioProRetail">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
</Add>
|
||||
</Configuration>
|
||||
```
|
||||
This example made the following changes to create this Subscription Licensing package:
|
||||
|
||||
* **SourcePath** was changed to point to the Office applications that were downloaded earlier.
|
||||
* **Product ID** for Office was changed to `O365ProPlusRetail`.
|
||||
* **Product ID** for Visio was changed to `VisioProRetail`.
|
||||
* **ExcludeApp** (optional): Lets you specify Office programs that you don’t want included in the App-V package created by the Office Deployment Tool. For example, you can exclude Access.
|
||||
* **PACKAGEGUID** (optional): By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use **PACKAGEGUID** to specify a different package ID for each package, which allows you to publish multiple App-V packages created by the Office Deployment Tool, and then manage your published packages with the App-V Server.
|
||||
|
||||
An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2016 for some users, and create another package with Office 2016 and Visio 2016 for another set of users.
|
||||
|
||||
> [!NOTE]
|
||||
>Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
|
||||
2. Use the /packager command to convert the Office applications to an Office 2016 App-V package.
|
||||
|
||||
An example packager command is:
|
||||
|
||||
```syntax
|
||||
\\server\Office2016\setup.exe /packager \\server\Office2016\Customconfig.xml \\server\share\Office2016AppV
|
||||
```
|
||||
|
||||
The following table describes each element used in the example command:
|
||||
|
||||
| Element | Description |
|
||||
|-------------------------------|--------------------------------------|
|
||||
|```\\server\Office2016```|This network share location is the one that contains the Office Deployment Tool and the custom Configuration.xml file, which in this example is Customconfig.xml.|
|
||||
|```Setup.exe```|This element is the Office Deployment Tool.|
|
||||
|```/packager```|This command creates the Office 2016 App-V package with the license type specified in the Customconfig.xml file.|
|
||||
|```\\server\Office2016\Customconfig.xml```|This element passes the configuration XML file that has been prepared for the packaging stage. In this example, the file is Customconfig.xml.|
|
||||
|```\\server\share\Office2016AppV```|This element specifies the location of the newly created Office App-V package.|
|
||||
|
||||
After you run the **/packager** command, the following folders appear up in the directory where you specified the package should be saved:
|
||||
|
||||
* **App-V Packages**—contains an Office 2016 App-V package and two deployment configuration files.
|
||||
* **WorkingDir**
|
||||
|
||||
> [!NOTE]
|
||||
>To troubleshoot any issues, see the log files in the %temp% directory (default).
|
||||
3. Verify that the Office 2016 App-V package works correctly:
|
||||
|
||||
1. Publish the Office 2016 App-V package that you created globally to a test computer and verify that the Office 2016 shortcuts appear.
|
||||
2. Start a few Office 2016 applications, such as Excel or Word, to ensure that your package is working as expected.
|
||||
|
||||
## Publishing the Office package for App-V
|
||||
|
||||
Use the following information to publish an Office package.
|
||||
|
||||
### Methods for publishing Office App-V packages
|
||||
|
||||
Deploy the App-V package for Office 2016 by using the same methods as the other packages that you've already deployed:
|
||||
|
||||
* Microsoft Configuration Manager
|
||||
* App-V Server
|
||||
* Stand-alone through Windows PowerShell commands
|
||||
|
||||
### Publishing prerequisites and requirements
|
||||
|
||||
| Prerequisite or requirement | Details |
|
||||
|---------------------------------------|--------------------|
|
||||
| Enable Windows PowerShell scripting on the App-V clients. | To publish Office 2016 packages, you must run a script. However, package scripts are disabled by default on App-V clients. To enable scripting, run the following Windows PowerShell command:<br>`Set-AppvClientConfiguration -EnablePackageScripts 1` |
|
||||
| Publish the Office 2016 package globally. | Extension points in the Office App-V package require installation at the computer level.<br>When you publish at the computer level, no prerequisite actions or redistributables are needed. The Office 2016 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages. |
|
||||
|
||||
### How to publish an Office package
|
||||
|
||||
Run the following command to publish an Office package globally:
|
||||
|
||||
```PowerShell
|
||||
Add-AppvClientPackage <Path_to_AppV_Package > | Publish-AppvClientPackage -global
|
||||
```
|
||||
|
||||
* You can add permissions to a group of computers instead of just a user group through the Web Management Console on the App-V Server. This feature lets packages be published globally to the computers in the corresponding group.
|
||||
|
||||
## Customizing and managing Office App-V packages
|
||||
|
||||
To manage your Office App-V packages, use the same operations as you would for any other package, with a few exceptions as outlined in the following sections.
|
||||
|
||||
* [Enabling Office plug-ins by using connection groups](#enabling-office-plug-ins-by-using-connection-groups)
|
||||
* [Disabling Office 2016 applications](#disabling-office-2016-applications)
|
||||
* [Disabling Office 2016 shortcuts](#disabling-office-2016-shortcuts)
|
||||
* [Managing Office 2016 package upgrades](#managing-office-2016-package-upgrades)
|
||||
* [Deploying Visio 2016 and Project 2016 with Office](#deploying-visio-2016-and-project-2016-with-office)
|
||||
|
||||
### Enabling Office plug-ins by using connection groups
|
||||
|
||||
The following steps will tell you how to enable Office plug-ins with your Office package. To use Office plug-ins, you must use the App-V Sequencer to create a separate package that only contains the plug-ins (you can't use the Office Deployment Tool to create the plug-ins package). After that, create a connection group that contains the Office package and the plug-ins package.
|
||||
|
||||
#### Enable plug-ins for Office App-V packages
|
||||
|
||||
1. Add a Connection Group through App-V Server, Microsoft Configuration Manager, or a Windows PowerShell cmdlet.
|
||||
2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2016 is installed on the computer that will be used to sequence the plug-in. We recommend that you use Microsoft 365 Apps for enterprise (non-virtual) on the sequencing computer when sequencing Office 2016 plug-ins.
|
||||
3. Create an App-V package that includes the plug-ins you want.
|
||||
4. Add a Connection Group through the App-V Server, Configuration Manager, or a Windows PowerShell cmdlet.
|
||||
5. Add the Office 2016 App-V package and the plug-ins package you sequenced to the Connection Group you created.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2016 App-V package first, and then add the plug-in App-V package.
|
||||
6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match published Office 2016 App-V package's global settings.
|
||||
7. Verify that the plug-in package's Deployment Configuration file has the same settings as the Office 2016 App-V package.
|
||||
|
||||
The Office 2016 App-V plug-in package's settings must match those of the operating system to allow for integration. You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as “Integrated” and that both "InProcessEnabled" and "OutOfProcessEnabled" match the settings of the Office 2016 App-V package you published.
|
||||
8. Open the Deployment Configuration File and set the value for **Objects Enabled** to **false**.
|
||||
9. If you made any changes to the Deployment Configuration file after sequencing, ensure that the plug-in package is published with the file.
|
||||
10. Ensure that the Connection Group you created on your desired computer is enabled. The Connection Group created will be shown as "pending" if the Office 2016 App-V package is being used while the Connection Group is enabled. If that happens, you'll have to reboot the computer to successfully enable the Connection Group.
|
||||
11. After you successfully publish both packages and enable the Connection Group, verify the plug-ins you published on the Connection Group work as expected.
|
||||
|
||||
### Disabling Office 2016 applications
|
||||
|
||||
You can also disable specific applications in your Office App-V package. For example, if you don't want to use Access, you can disable Access while leaving all other Office applications available. When you disable an application, the user will no longer see its shortcut icon. You don't need to re-sequence the application to disable it. When you change the Deployment Configuration File after the Office 2016 App-V package has been published, just save the changes and add the Office 2016 App-V package, then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.
|
||||
|
||||
>[!NOTE]
|
||||
>To exclude specific Office applications when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting.
|
||||
|
||||
#### Disable an Office 2016 application
|
||||
|
||||
1. Open a Deployment Configuration File with a text editor such as **Notepad** and search for “Applications."
|
||||
2. Search for the Office application you want to disable, for example, Access 2016.
|
||||
3. Change the value of **Enabled** to **false**.
|
||||
4. Save the Deployment Configuration File.
|
||||
5. Add the Office 2016 App-V Package with the new Deployment Configuration File.
|
||||
|
||||
```XML
|
||||
<Application Id="[{AppVPackageRoot}]\office16\lync.exe" Enabled="true">
|
||||
<VisualElements>
|
||||
<Name>Lync 2016</Name>
|
||||
<Icon />
|
||||
<Description />
|
||||
</VisualElements>
|
||||
</Application>
|
||||
<Application Id="[(AppVPackageRoot}]\office16\MSACCESS.EXE" Enabled="true">
|
||||
<VisualElements>
|
||||
<Name>Access 2016</Name>
|
||||
<Icon />
|
||||
<Description />
|
||||
</VisualElements>
|
||||
</Application>
|
||||
```
|
||||
6. Re-add the Office 2016 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.
|
||||
|
||||
### Disabling Office 2016 shortcuts
|
||||
|
||||
You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.
|
||||
|
||||
#### Disable shortcuts for Office 2016 applications
|
||||
|
||||
1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
|
||||
2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. The following example shows how to delete the Microsoft Access shortcuts while keeping the subsystems `<shortcut> </shortcut>` intact.
|
||||
|
||||
``` XML
|
||||
Shortcuts
|
||||
|
||||
-->
|
||||
<Shortcuts Enabled="true">
|
||||
<Extensions>
|
||||
<Extension Category="AppV.Shortcut">
|
||||
<Shortcut>
|
||||
<File>[{Common Programs}]\Microsoft Office 2016\Access 2016.lnk</File>
|
||||
<Target>[{AppvPackageRoot}])office16\MSACCESS.EXE</Target>
|
||||
<Icon>[{Windows}]\Installer\{90150000-000F-0000-0000-000000FF1CE)\accicons.exe.Ø.ico</Icon>
|
||||
<Arguments />
|
||||
<WorkingDirectory />
|
||||
<AppuserModelId>Microsoft.Office.MSACCESS.EXE.16</AppUserModelId>
|
||||
<AppUserModelExcludeFromShowInNewInstall>true</AppUserModelExcludeFromShowInNewInstall>
|
||||
<Description>Build a professional app quickly to manage data.</Description>
|
||||
<ShowCommand>l</ShowCommand>
|
||||
<ApplicationId>[{AppVPackageRoot}]\office16\MSACCESS.EXE</ApplicationId>
|
||||
</Shortcut>
|
||||
```
|
||||
3. Save the Deployment Configuration File.
|
||||
4. Republish the Office 2016 App-V Package with the new Deployment Configuration File.
|
||||
|
||||
Many more settings can be changed through modifying the Deployment Configuration for App-V packages, for example, file type associations, Virtual File System, and more. For additional information on how to use Deployment Configuration Files to change App-V package settings, refer to the additional resources section at the end of this document.
|
||||
|
||||
### Managing Office 2016 package upgrades
|
||||
|
||||
To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a previously deployed Office 2016 package, perform the steps outlined in the following section.
|
||||
|
||||
#### How to upgrade a previously deployed Office 2016 package
|
||||
|
||||
1. Create a new Office 2016 package through the Office Deployment Tool that uses the most recent Office 2016 application software. The most recent Office 2016 bits can always be obtained through the download stage of creating an Office 2016 App-V Package. The newly created Office 2016 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
|
||||
|
||||
> [!NOTE]
|
||||
>Office App-V packages have two Version IDs:
|
||||
>* An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
|
||||
>* A second App-V Package Version ID, formatted as X.X.X.X, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2016 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect the new version of Office. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2016 package.
|
||||
2. Globally publish the newly created Office 2016 App-V Packages onto the computers you want to apply the new updates to. Since the new package has the same lineage as the older Office 2016 App-V Package, publishing will be fast, as publishing the new package with the updates only applies the new changes to the old package.
|
||||
3. Upgrades will be applied in the same manner of any globally published App-V packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.
|
||||
|
||||
### Deploying Visio 2016 and Project 2016 with Office
|
||||
|
||||
The following table describes the requirements and options for deploying Visio 2016 and Project 2016 with Office.
|
||||
|
||||
| Task | Details |
|
||||
|---------------------|---------------|
|
||||
| How do I package and publish Visio 2016 and Project 2016 with Office? | You must include Visio 2016 and Project 2016 in the same package with Office.<br>If you're not deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the packaging, publishing, and deployment requirements described in this topic. |
|
||||
| How can I deploy Visio 2016 and Project 2016 to specific users? | Use one of the following methods:<br>**To create two different packages and deploy each one to a different group of users**:<br>Create and deploy the following packages:<br>- A package that contains only Office—deploy to computers whose users need only Office.<br>- A package that contains Office, Visio, and Project—deploy to computers whose users need all three applications.<br><br>**To create only one package for the whole organization, or to create a package intended for users who share computers**:<br>1. Create a package that contains Office, Visio, and Project.<br>2. Deploy the package to all users.<br>3. Use [AppLocker](/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project. |
|
||||
|
||||
## Related articles
|
||||
|
||||
* [Deploying App-V for Windows client](appv-deploying-appv.md)
|
||||
* [Deploying Microsoft Office 2013 by using App-V](appv-deploying-microsoft-office-2013-with-appv.md)
|
||||
* [Deploying Microsoft Office 2010 by using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
|
||||
* [Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117)
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user