| 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: |
-For more information on ActiveX controls, refer to [ActiveX Control API Reference](https://msdn.microsoft.com/library/office/ms440037(v=office.14).aspx). |
-- |
Groove.SiteClient |
-Active X Control |
-- |
PortalConnect.PersonalSite |
-Active X Control |
-- |
SharePoint.openDocuments |
-Active X Control |
-- |
SharePoint.ExportDatabase |
-Active X Control |
-- |
SharePoint.SpreadSheetLauncher |
-Active X Control |
-- |
SharePoint.StssyncHander |
-Active X Control |
-- |
SharePoint.DragUploadCtl |
-Active X Control |
-- |
SharePoint.DragDownloadCtl |
-Active X Control |
-- |
Sharpoint.OpenXMLDocuments |
-Active X Control |
-- |
Sharepoint.ClipboardCtl |
-Active X control |
-- |
WinProj.Activator |
-Active X Control |
-- |
Name.NameCtrl |
-Active X Control |
-- |
STSUPld.CopyCtl |
-Active X Control |
-- |
CommunicatorMeetingJoinAx.JoinManager |
-Active X Control |
-- |
LISTNET.Listnet |
-Active X Control |
-- |
OneDrive Pro Browser Helper |
-Active X Control] |
-- |
OneDrive Pro Icon Overlays |
-Windows explorer shell icon overlays when users look at folders OneDrive Pro folders |
-- |
- Supported deployment types like desktop, personal Virtual Desktop Infrastructure (VDI), and pooled VDI
- Office licensing options.| |[Planning for using App-V with coexisting versions of Office](appv-planning-for-using-appv-with-office.md#bkmk-plan-coexisting)|Considerations for installing different versions of Office on the same computer.| -
| Information to review | -Description | -
|---|---|
[Supported versions of Microsoft Office](appv-planning-for-using-appv-with-office.md#bkmk-office-vers-supp-appv) |
-
|
-
[Planning for using App-V with coexisting versions of Office](appv-planning-for-using-appv-with-office.md#bkmk-plan-coexisting) |
-Considerations for installing different versions of Office on the same computer |
-
In App-V and later, you must use the Office Deployment Tool to create packages. The Sequencer doesn't support package creation.
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](#bkmk-deploy-visio-project).| |Publishing|You can only publish one Office package per client computer.
You must publish the Office package globally, not to the user.| -|Deploying Office 365 ProPlus, 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](https://docs.microsoft.com/en-us/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus).
You don’t 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.| - -
| Task | -Requirement | -
|---|---|
Packaging |
-
|
-
Publishing |
-
|
-
Deploying any of the following products to a shared computer, for example, by using Remote Desktop Services: -
|
-You must enable [shared computer activation](https://docs.microsoft.com/en-us/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus). -You don’t use shared computer activation if you’re deploying a volume licensed product, such as: -
|
-
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 @@ -116,36 +44,7 @@ The following table describes the recommended methods for excluding specific Off |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.
For more information, see [ExcludeApp element](https://docs.microsoft.com/en-us/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ui=en-US&rs=en-US&ad=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.
For more information, see [Disabling Office 2013 applications](#bkmk-disable-office-apps).| - -
| Task | -Details | -
|---|---|
Use the ExcludeApp setting when you create the package by using the Office Deployment Tool. |
-
|
-
Modify the DeploymentConfig.xml file |
-
|
-
For more information, see [Disabling Office 2013 applications](#bkmk-disable-office-apps).| ## Creating an Office 2013 package for App-V with the Office Deployment Tool @@ -160,35 +59,9 @@ Before you start, make sure that the computer on which you are installing the Of |Prerequisite|Description| |---|---| -|Prerequisite software|.Net Framework 4| +|Prerequisite software|.NET Framework 4| |Supported operating systems|64-bit version of Windows 8 or later
64-bit version of Windows 7| -
| Prerequisite | -Description | -
|---|---|
Prerequisite software |
-.Net Framework 4 |
-
Supported operating systems |
-
|
-
|
- This is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml. |
-
|
- This is the Office Deployment Tool. |
-
|
- This 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. |
-
|
- This passes the XML configuration file required to complete the download process. In this example, the file used is customconfig.xml. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example \\Server\Office2013. |
-
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):
Specifies the location where the applications will be saved to.|```Sourcepath="\Server\Office2013”```| -
| Input and description | -Example | -
|---|---|
Add element: |
-N/A |
-
OfficeClientEdition (attribute of Add element): |
-
|
-
Product element: |
-
|
-
Language element: |
-
|
-
Version (attribute of Add element): |
-
|
-
SourcePath (attribute of Add element): |
-
|
-
VisioProVolume|O365ProPlusRetail
VisioProRetail| |Office 2013 with Visio 2013 and Project 2013|ProPlusVolume
VisioProVolume
ProjectProVolume|O365ProPlusRetail
VisioProRetail
ProjectProRetail| -
| Product ID | -Volume Licensing | -Subscription Licensing | -
|---|---|---|
Office 2013 |
-ProPlusVolume |
-O365ProPlusRetail |
-
Office 2013 with Visio 2013 |
-ProPlusVolume -VisioProVolume |
-O365ProPlusRetail -VisioProRetail |
-
Office 2013 with Visio 2013 and Project 2013 |
-ProPlusVolume -VisioProVolume -ProjectProVolume |
-O365ProPlusRetail -VisioProRetail -ProjectProRetail |
-
|
- This is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, which in this example is named |
-
|
- This is the Office Deployment Tool. |
-
|
- This creates the Office 2013 App-V package with Volume Licensing as specified in the Customconfig.xml file. |
-
|
- This passes the configuration XML file, which in this example is named "Customconfig," that has been prepared for the packaging stage. |
-
|
- This specifies the location of the newly created Office App-V package. |
-
@@ -517,32 +253,6 @@ Deploy the App-V package for Office 2013 by using the same methods you use for a |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:
```Set-AppvClientConfiguration –EnablePackageScripts 1```| |Publish the Office 2013 package globally.|Extension points in the Office App-V package require installation at the computer level.
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.| -
| 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: - |
-
Publish the Office 2013 package globally |
-Extension points in the Office App-V package require installation at the computer level. -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. |
-
A package that contains only Office—deploy to computers whose users need only Office.
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:
1. Create a package that contains Office, Visio, and Project.
2. Deploy the package to all users.
3. Use [AppLocker](https://docs.microsoft.com/en-us/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project.| -
| Goal | -Method | -
|---|---|
Create two different packages and deploy each one to a different group of users |
-Create and deploy the following packages: -
|
-
If you want only one package for the whole organization, or if you have users who share computers: |
-Follows these steps: -
|
-
VisioProRetail | +| Product ID | Subscription licensing | +|---|---| +| Office 2016| O365ProPlusRetail | +| Office 2016 with Visio 2016 | O365ProPlusRetail
VisioProRetail | | Office 2016 with Visio 2016 and Project 2016 | O365ProPlusRetail
VisioProRetail
ProjectProRetail | #### How to convert the Office applications into an App-V package @@ -268,7 +268,7 @@ To manage your Office App-V packages, use the same operations as you would for a 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. -To enable plug-ins for Office App-V packages: +#### Enable plug-ins for Office App-V packages 1. Add a Connection Group through App-V Server, System Center 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 Office 365 ProPlus (non-virtual) on the sequencing computer when sequencing Office 2016 plug-ins. @@ -294,7 +294,7 @@ You can also disable specific applications in your Office App-V package. For exa >[!NOTE] >To exclude specific Office applications when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting. -#### To disable an Office 2016 application +#### 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. @@ -324,7 +324,7 @@ You can also disable specific applications in your Office App-V package. For exa 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. -#### To disable shortcuts for Office 2016 applications +#### 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 `
| - | Task | -References | -Notes | -
|---|---|---|---|
 |
-Review the getting started information about App-V to gain a basic understanding of the product before beginning deployment planning. |
-[Getting started with App-V](appv-getting-started.md) |
-- |
|
-Plan for App-V deployment prerequisites and prepare your computing environment. |
-[App-V prerequisites](appv-prerequisites.md) |
-- |
|
-If you plan to use the App-V management server, plan for the required roles. |
-[Planning for the App-V server deployment](appv-planning-for-appv-server-deployment.md) |
-- |
|
-Plan for the App-V sequencer and client to create and run virtualized applications. |
-[Planning for the App-V Sequencer and client deployment](appv-planning-for-sequencer-and-client-deployment.md) |
-- |
|
-If applicable, review the options and steps for migrating from a previous version of App-V. |
-[Migrating to App-V from a previous version](appv-migrating-to-appv-from-a-previous-version.md) |
-- |
|
-Decide whether to configure App-V clients in Shared Content Store mode. |
-[Deploying the App-V Sequencer and configuring the client](appv-deploying-the-appv-sequencer-and-client.md) |
-- |
| Office version | -Relevant guide links | -
|---|---|
Office 2016 |
-[How to use Outlook 2016 or 2013 and an earlier version of Outlook installed on the same computer](https://support.microsoft.com/kb/2782408) |
-
Office 2013 |
-[How to use Office 2013 suites and programs (MSI deployment) on a computer running another version of Office](http://support.microsoft.com/kb/2784668) |
-
Office 2010 |
-[How to use Office 2010 suites and programs on a computer running another version of Office](http://support.microsoft.com/kb/2121447) |
-
Static content
Default document
Application development:
ASP.NET
.NET Extensibility
ISAPI Extensions
ISAPI Filters
Security:
Windows Authentication
Request Filtering
Management Tools:
IIS Management Console| +|Web Server Role Services|Common HTTP features:
- Static content
- Default document
Application development:
- ASP.NET
- .NET Extensibility
- ISAPI Extensions
- ISAPI Filters
Security:
- Windows Authentication
- Request Filtering
Management Tools:
- IIS Management Console| |Default installation location|%PROGRAMFILES%\Microsoft Application Virtualization Server| |Location of the Management database|SQL Server database name, SQL Server database instance name, and database name.| -|Management console and Management database permissions|A user or group that can access the Management console and database after the deployment is complete. Only these users or groups will have access to the Management console and database unless additional administrators are added by using the Management console.| +|Management console and Management database permissions|A user or group that can access the Management console and database after the deployment is complete. Only these users or groups can access the Management console and database unless the Management console is used to add additional administrators.| |Management service website name|Name for the Management console website.| |Management service port binding|Unique port number for the Management service. This port cannot be used by another process on the computer.| -
| Prerequisites and required settings | -Details | -
|---|---|
Supported version of SQL Server |
-For supported versions, see [App-V supported configurations](appv-supported-configurations.md). |
-
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
-- |
[Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595) |
-Installing Windows PowerShell 3.0 requires a restart. |
-
Download and install [KB2533623](http://support.microsoft.com/kb/2533623) |
-Applies to Windows 7 only. |
-
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
-- |
64-bit ASP.NET registration |
-- |
Windows Server Web Server Role |
-This role must be added to a server operating system that is supported for the Management server. |
-
Web Server (IIS) Management Tools |
-Click IIS Management Scripts and Tools. |
-
Web Server Role Services |
-Common HTTP features: -
Application development: -
Security: -
Management tools: -
|
-
Default installation location |
-%PROGRAMFILES%\Microsoft Application Virtualization Server |
-
Location of the Management database |
-SQL Server database name, SQL Server database instance name, and database name. |
-
Management console and Management database permissions |
-A user or group that can access the Management console and database after the deployment is complete. Only these users or groups will have access to the Management console and database unless additional administrators are added by using the Management console. |
-
Management service website name |
-Name for the Management console website. |
-
Management service port binding |
-Unique port number for the Management service. This port cannot be used by another process on the computer. |
-
This format assumes that the installation is on the local computer.
If you specify the name with the format **SVR\INSTANCE**, the installation will fail.| |Custom database name (if applicable)|Unique database name.
Default: AppVManagement| -|Management server location|Machine account on which the Management server is deployed.
Format to use: Domain\MachineAccount| -|Management server installation administrator|Account used to install the Management server.
Format to use: Domain\AdministratorLoginName| +|Management server location|Machine account on which the Management server is deployed.
Format to use: **Domain\MachineAccount**| +|Management server installation administrator|Account used to install the Management server.
Format to use: **Domain\AdministratorLoginName**| |Microsoft SQL Server Service Agent|Configure the Management database computer so that the Microsoft SQL Server Agent service is restarted automatically. For instructions, see [Configure SQL Server Agent to restart services automatically](http://technet.microsoft.com/magazine/gg313742.aspx).| - -
| Prerequisites and required settings | -Details | -
|---|---|
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
-- |
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
-- |
Default installation location |
-%PROGRAMFILES%\Microsoft Application Virtualization Server |
-
Custom SQL Server instance name (if applicable) |
-Format to use: INSTANCENAME -This format assumes that the installation is on the local computer. -If you specify the name with the format SVR\INSTANCE, the installation will fail. |
-
Custom database name (if applicable) |
-Unique database name. -Default: AppVManagement |
-
Management server location |
-Machine account on which the Management server is deployed. -Format to use: Domain\MachineAccount |
-
Management server installation administrator |
-Account used to install the Management server. -Format to use: Domain\AdministratorLoginName |
-
Microsoft SQL Server Service Agent |
-Configure the Management database computer so that the Microsoft SQL Server Agent service is restarted automatically. For instructions, see [Configure SQL Server Agent to restart services automatically](http://technet.microsoft.com/magazine/gg313742.aspx). |
-
Static content
Default document
Application development:
ASP.NET
.NET Extensibility
ISAPI Extensions
ISAPI Filters
Security:
Windows Authentication
Request Filtering
Management Tools:
IIS Management Console| +|Web Server Role Services|Common HTTP features:
- Static content
- Default document
Application development:
- ASP.NET
- .NET Extensibility
- ISAPI Extensions
- ISAPI Filters
Security:
- Windows Authentication
- Request Filtering
Management Tools:
- IIS Management Console| |Default installation location|%PROGRAMFILES%\Microsoft Application Virtualization Server| -|Management service URL|URL of the App-V Management service. This is the port with which the Publishing server communicates.
Management server and Publishing server are installed on the same server, use the format http://localhost:12345.
If the Management server and Publishing server are installed on different servers, use the format http://MyAppvServer.MyDomain.com.| +|Management service URL|URL of the App-V Management service. This is the port with which the Publishing server communicates.
Management server and Publishing server are installed on the same server, use the format **http://localhost:12345**.
If the Management server and Publishing server are installed on different servers, use the format **http://MyAppvServer.MyDomain.com**.| |Publishing service website name|Name for the Publishing website.| |Publishing service port binding|Unique port number for the Publishing service. This port cannot be used by another process on the computer.| -
| Prerequisites and required settings | -Details | -||||||
|---|---|---|---|---|---|---|---|
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
-- | ||||||
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
-- | ||||||
64-bit ASP.NET registration |
-- | ||||||
Web Server role |
-This role must be added to a server operating system that is supported for the Management server. |
-||||||
Web Server (IIS) Management Tools |
-Click IIS Management Scripts and Tools. |
-||||||
Web Server Role Services |
-Common HTTP reatures: -
Application development: -
Security: -
Management Tools: -
|
-||||||
Default installation location |
-%PROGRAMFILES%\Microsoft Application Virtualization Server |
-||||||
Management service URL |
-URL of the App-V Management service. This is the port with which the Publishing server communicates. -
- |
-||||||
Publishing service website name |
-Name for the Publishing website |
-||||||
Publishing service port binding |
-Unique port number for the Publishing service. This port cannot be used by another process on the computer. |
-
Common HTTP features:
Static content
Default document
Application development:
ASP.NET
.NET Extensibility
ISAPI Extensions
ISAPI Filters
Security:
Windows Authentication
Request Filtering
Management Tools:
IIS Management Console| +|Web Server Role Services|To reduce the risk of unwanted or malicious data being sent to the Reporting server, you should restrict access to the Reporting Web Service per your corporate security policy.
Common HTTP features:
- Static content
- Default document
Application development:
- ASP.NET
- .NET Extensibility
- ISAPI Extensions
- ISAPI Filters
Security:
- Windows Authentication
- Request Filtering
- Management Tools:
- IIS Management Console| |Default installation location|%PROGRAMFILES%\Microsoft Application Virtualization Server| |Reporting service website name|Name for the Reporting website.| |Reporting service port binding|Unique port number for the Reporting service. This port cannot be used by another process on the computer.| -
| Prerequisites and required settings | -Details | -
|---|---|
Supported version of SQL Server |
-For supported versions, see [App-V supported configurations](appv-supported-configurations.md). |
-
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
-- |
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
-- |
64-bit ASP.NET registration |
-- |
Windows Server Web Server role |
-This role must be added to a server operating system that is supported for the Management server. |
-
Web Server (IIS) Management Tools |
-Click IIS Management Scripts and Tools. |
-
Web Server role services |
-To reduce the risk of unwanted or malicious data being sent to the Reporting server, you should restrict access to the Reporting Web Service per your corporate security policy. -Common HTTP features: -
Application development: -
Security: -
Management tools: -
|
-
Default installation location |
-%PROGRAMFILES%\Microsoft Application Virtualization Server |
-
Reporting service website name |
-Name for the Reporting website. |
-
Reporting service port binding |
-Unique port number for the Reporting service. This port cannot be used by another process on the computer. |
-
his format assumes that the installation is on the local computer.
If you specify the name with the format **SVR\INSTANCE**, the installation will fail.| |Custom database name (if applicable)|Unique database name.
Default: AppVReporting| -|Reporting server location|The Reporting server will be deployed on this machine account.
Format to use: Domain\MachineAccount| -|Reporting server installation administrator|Account used to install the Reporting server.
Format to use: Domain\AdministratorLoginName| +|Reporting server location|The Reporting server will be deployed on this machine account.
Format to use: **Domain\MachineAccount**| +|Reporting server installation administrator|Account used to install the Reporting server.
Format to use: **Domain\AdministratorLoginName**| |Microsoft SQL Server Service and Microsoft SQL Server Service Agent|Configure these services to be associated with user accounts that have access to query AD DS.| -
| Prerequisites and required settings | -Details | -
|---|---|
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
-- |
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
-- |
Default installation location |
-%PROGRAMFILES%\Microsoft Application Virtualization Server |
-
Custom SQL Server instance name (if applicable) |
-Format to use: INSTANCENAME -This format assumes that the installation is on the local computer. -If you specify the name with the format SVR\INSTANCE, the installation will fail. |
-
Custom database name (if applicable) |
-Unique database name. -Default: AppVReporting |
-
Reporting server location |
-The Reporting server will be deployed on this machine account. -Format to use: Domain\MachineAccount |
-
Reporting server installation administrator |
-Account used to install the Reporting server. -Format to use: Domain\AdministratorLoginName |
-
Microsoft SQL Server Service and Microsoft SQL Server Service Agent |
-Configure these services to be associated with user accounts that have access to query AD DS. |
-
| Prerequisite | -Details | -
|---|---|
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
-- |
[Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595) - |
-Installing Windows PowerShell 3.0 requires a restart. |
-
[KB2533623](http://support.microsoft.com/kb/2533623) |
-Applies to Windows 7 only: download and install the KB. |
-
| With a reporting server | -Without a reporting server | -
|---|---|
If you have an existing App-V reporting server, create a customized scheduled task or script. Specify that the client sends the data to the specified location at the desired frequency. |
-If you do not have an existing App-V reporting Server, use the –URL parameter to send the data to a specified share. For example: -
The previous example will send the reporting data to \\MyShare\MyData\ location indicated by the -URL parameter. After the data has been sent, the cache is cleared. -
-Note
-
-If a location other than the Reporting Server is specified, the data is sent using .xml format with no additional processing. -
-
- |
-
| Group name | -Details | -
|---|---|
App-V Management Admin group |
-Used to manage the App-V management server. This group is created during the App-V Management Server installation. -
-Important
-
-The management console can't create a new group after installation is complete. -
-
- |
-
Database read/write for Management Service account |
-Provides read/write access to the management database. This account should be created during App-V management database installation. |
-
App-V Management Service install admin account -
-Note
-
-This is only required if the management database is being installed separately from the service. -
-
- |
-Provides public access to schema-version table in management database. This account should be created during App-V management database installation. |
-
App-V Reporting Service install admin account -
-Note
-
-This is only required if reporting database is being installed separately from the service. -
-
- |
-Public access to schema-version table in reporting database. This account should be created during the App-V reporting database installation. |
-
| SQL Server version | -Service pack | -System architecture | -
|---|---|---|
Microsoft SQL Server 2014 |
-- | 32-bit or 64-bit |
-
Microsoft SQL Server 2012 |
-SP2 |
-32-bit or 64-bit |
-
Microsoft SQL Server 2008 R2 |
-SP3 |
-32-bit or 64-bit |
-
| SQL Server version | -Service pack | -System architecture | -
|---|---|---|
Microsoft SQL Server 2014 |
-- | 32-bit or 64-bit |
-
Microsoft SQL Server 2012 |
-SP2 |
-32-bit or 64-bit |
-
Microsoft SQL Server 2008 R2 |
-SP3 |
-32-bit or 64-bit |
-
| Operating system | -Service pack | -System architecture | -
|---|---|---|
Microsoft Windows Server 2012 R2 |
-- | 64-bit |
-
Microsoft Windows Server 2012 |
-- | 64-bit |
-
Microsoft Windows Server 2008 R2 |
-SP1 |
-64-bit |
-
Microsoft Windows 10 |
-- | 32-bit and 64-bit |
-
Microsoft Windows 8.1 |
-- | 32-bit and 64-bit |
-
Microsoft Windows 8 |
-- | 32-bit and 64-bit |
-
Microsoft Windows 7 |
-SP1 |
-32-bit and 64-bit |
-