mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 20:03:40 +00:00
Merge branch 'master' into jreeds-offline
This commit is contained in:
Jeff Reeds (Aquent LLC)
@ -13,37 +13,27 @@ ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
# Deploying the App-V 5.1 Server
|
||||
|
||||
|
||||
You can install the Microsoft Application Virtualization (App-V) 5.1 server features by using different deployment configurations, which described in this topic. Before you install the server features, review the server section of [App-V 5.1 Security Considerations](app-v-51-security-considerations.md).
|
||||
|
||||
For information about deploying the App-V Server, see [About App-V 5.1](about-app-v-51.md#bkmk-migrate-to-51).
|
||||
|
||||
**Important**
|
||||
Before you install and configure the App-V 5.1 servers, you must specify a port where each component will be hosted. You must also add the associated firewall rules to allow incoming requests to access the specified ports. The installer does not modify firewall settings.
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Before you install and configure the App-V 5.1 servers, you must specify a port where each component will be hosted. You must also add the associated firewall rules to allow incoming requests to access the specified ports. The installer does not modify firewall settings.
|
||||
|
||||
## <a href="" id="---------app-v-5-1-server-overview"></a> App-V 5.1 Server overview
|
||||
|
||||
|
||||
The App-V 5.1 Server is made up of five components. Each component serves a different purpose within the App-V 5.1 environment. Each of the five components is briefly described here:
|
||||
|
||||
- Management Server – provides overall management functionality for the App-V 5.1 infrastructure.
|
||||
|
||||
- Management Database – facilitates database predeployments for App-V 5.1 management.
|
||||
|
||||
- Publishing Server – provides hosting and streaming functionality for virtual applications.
|
||||
|
||||
- Reporting Server – provides App-V 5.1 reporting services.
|
||||
|
||||
- Reporting Database – facilitates database predeployments for App-V 5.1 reporting.
|
||||
- Management Server – provides overall management functionality for the App-V 5.1 infrastructure.
|
||||
- Management Database – facilitates database predeployments for App-V 5.1 management.
|
||||
- Publishing Server – provides hosting and streaming functionality for virtual applications.
|
||||
- Reporting Server – provides App-V 5.1 reporting services.
|
||||
- Reporting Database – facilitates database predeployments for App-V 5.1 reporting.
|
||||
|
||||
## <a href="" id="---------app-v-5-1-stand-alone-deployment"></a> App-V 5.1 stand-alone deployment
|
||||
|
||||
|
||||
The App-V 5.1 standalone deployment provides a good topology for a small deployment or a test environment. When you use this type of implementation, all server components are deployed to a single computer. The services and associated databases will compete for the resources on the computer that runs the App-V 5.1 components. Therefore, you should not use this topology for larger deployments.
|
||||
|
||||
[How to Deploy the App-V 5.1 Server](how-to-deploy-the-app-v-51-server.md)
|
||||
@ -52,7 +42,6 @@ The App-V 5.1 standalone deployment provides a good topology for a small deploym
|
||||
|
||||
## <a href="" id="---------app-v-5-1-server-distributed-deployment"></a> App-V 5.1 Server distributed deployment
|
||||
|
||||
|
||||
The distributed deployment topology can support a large App-V 5.1 client base and it allows you to more easily manage and scale your environment. When you use this type of deployment, the App-V 5.1 Server components are deployed across multiple computers, based on the structure and requirements of the organization.
|
||||
|
||||
[How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](how-to-install-the-management-and-reporting-databases-on-separate-computers-from-the-management-and-reporting-services51.md)
|
||||
@ -67,19 +56,15 @@ The distributed deployment topology can support a large App-V 5.1 client base an
|
||||
|
||||
## Using an Enterprise Software Distribution (ESD) solution and App-V 5.1
|
||||
|
||||
|
||||
You can also deploy the App-V 5.1 clients and packages by using an ESD without having to deploy App-V 5.1. The full capabilities for integration will vary depending on the ESD that you use.
|
||||
|
||||
**Note**
|
||||
The App-V 5.1 reporting server and reporting database can still be deployed alongside the ESD to collect the reporting data from the App-V 5.1 clients. However, the other three server components should not be deployed, because they will conflict with the ESD functionality.
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> The App-V 5.1 reporting server and reporting database can still be deployed alongside the ESD to collect the reporting data from the App-V 5.1 clients. However, the other three server components should not be deployed, because they will conflict with the ESD functionality.
|
||||
|
||||
[Deploying App-V 5.1 Packages by Using Electronic Software Distribution (ESD)](deploying-app-v-51-packages-by-using-electronic-software-distribution--esd-.md)
|
||||
|
||||
## <a href="" id="---------app-v-5-1-server-logs"></a> App-V 5.1 Server logs
|
||||
|
||||
|
||||
You can use App-V 5.1 server log information to help troubleshoot the server installation and operational events while using App-V 5.1. The server-related log information can be reviewed with the **Event Viewer**. The following line displays the specific path for Server-related events:
|
||||
|
||||
**Event Viewer \\ Applications and Services Logs \\ Microsoft \\ App V**
|
||||
@ -92,14 +77,11 @@ In App-V 5.0 SP3, some logs were consolidated and moved. See [About App-V 5.0 SP
|
||||
|
||||
## <a href="" id="---------app-v-5-1-reporting"></a> App-V 5.1 reporting
|
||||
|
||||
|
||||
App-V 5.1 reporting allows App-V 5.1 clients to collect data and then send it back to be stored in a central repository. You can use this information to get a better view of the virtual application usage within your organization. The following list displays some of the types of information the App-V 5.1 client collects:
|
||||
|
||||
- Information about the computer that runs the App-V 5.1 client.
|
||||
|
||||
- Information about virtualized packages on a specific computer that runs the App-V 5.1 client.
|
||||
|
||||
- Information about package open and shutdown for a specific user.
|
||||
- Information about the computer that runs the App-V 5.1 client.
|
||||
- Information about virtualized packages on a specific computer that runs the App-V 5.1 client.
|
||||
- Information about package open and shutdown for a specific user.
|
||||
|
||||
The reporting information will be maintained until it is successfully sent to the reporting server database. After the data is in the database, you can use Microsoft SQL Server Reporting Services to generate any necessary reports.
|
||||
|
||||
@ -111,19 +93,4 @@ Use the following link for more information [About App-V 5.1 Reporting](about-ap
|
||||
|
||||
## Other resources for the App-V server
|
||||
|
||||
|
||||
[Deploying App-V 5.1](deploying-app-v-51.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -13,75 +13,42 @@ ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
# How to Deploy the App-V Databases by Using SQL Scripts
|
||||
|
||||
|
||||
Use the following instructions to use SQL scripts, rather than the Windows Installer, to:
|
||||
|
||||
- Install the App-V 5.1 databases
|
||||
- Install the App-V 5.1 databases
|
||||
- Upgrade the App-V databases to a later version
|
||||
|
||||
- Upgrade the App-V databases to a later version
|
||||
> [!NOTE]
|
||||
> If you have already deployed the App-V 5.0 SP3 database, the SQL scripts are not required to upgrade to App-V 5.1.
|
||||
|
||||
**Note**
|
||||
If you have already deployed the App-V 5.0 SP3 database, the SQL scripts are not required to upgrade to App-V 5.1.
|
||||
## 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.
|
||||
1. Copy the **appv\_server\_setup.exe** from the App-V release media to a temporary location.
|
||||
1. From a command prompt, run **appv\_server\_setup.exe** and specify a temporary location for extracting the database scripts.
|
||||
|
||||
Example: appv\_server\_setup.exe /layout c:\\<_temporary location path_>
|
||||
|
||||
**How to install the App-V databases by using SQL scripts**
|
||||
1. Browse to the temporary location that you created, open the extracted **DatabaseScripts** folder, and review the appropriate Readme.txt file for instructions:
|
||||
|
||||
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.
|
||||
| Database | Location of Readme.txt file to use |
|
||||
|--|--|
|
||||
| Management database | ManagementDatabase subfolder |
|
||||
| Reporting database | ReportingDatabase subfolder |
|
||||
|
||||
2. Copy the **appv\_server\_setup.exe** from the App-V release media to a temporary location.
|
||||
> [!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.
|
||||
|
||||
3. From a command prompt, run **appv\_server\_setup.exe** and specify a temporary location for extracting the database scripts.
|
||||
|
||||
Example: 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:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Database</th>
|
||||
<th align="left">Location of Readme.txt file to use</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Management database</p></td>
|
||||
<td align="left"><p>ManagementDatabase subfolder</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Reporting database</p></td>
|
||||
<td align="left"><p>ReportingDatabase subfolder</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
~~~
|
||||
**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.
|
||||
> [!IMPORTANT]
|
||||
> The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3.
|
||||
|
||||
The Permissions.sql script should be updated according to **Step 2** in [KB article 3031340](https://support.microsoft.com/kb/3031340). **Step 1** is not required for versions of App-V later than App-V 5.0 SP3.
|
||||
~~~
|
||||
|
||||
## Updated management database README file content
|
||||
|
||||
|
||||
**Updated management database README file content**
|
||||
|
||||
``` syntax
|
||||
```plaintext
|
||||
******************************************************************
|
||||
Before you install and use the Application Virtualization Database Scripts you must:
|
||||
1.Review the Microsoft Application Virtualization Server 5.0 license terms.
|
||||
@ -107,7 +74,7 @@ Steps to install "AppVManagement" schema in SQL SERVER.
|
||||
|
||||
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
|
||||
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.
|
||||
@ -120,7 +87,7 @@ Steps to install "AppVManagement" schema in SQL SERVER.
|
||||
defaults are likely sufficient, it is suggested that the following
|
||||
settings be reviewed:
|
||||
|
||||
DATABASE - ensure name is satisfactory - default is "AppVManagement".
|
||||
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
|
||||
@ -130,23 +97,23 @@ Steps to install "AppVManagement" schema in SQL SERVER.
|
||||
|
||||
## INSTALLATION:
|
||||
|
||||
1. Run the database.sql against the "master" database. Your user
|
||||
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
|
||||
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
|
||||
## Permissions.sql
|
||||
|
||||
```
|
||||
|
||||
**Updated reporting database README file content**
|
||||
## Updated reporting database README file content
|
||||
|
||||
``` syntax
|
||||
```plaintext
|
||||
******************************************************************
|
||||
Before you install and use the Application Virtualization Database Scripts you must:
|
||||
1.Review the Microsoft Application Virtualization Server 5.0 license terms.
|
||||
@ -188,7 +155,7 @@ Steps to install "AppVReporting" schema in SQL SERVER.
|
||||
defaults are likely sufficient, it is suggested that the following
|
||||
settings be reviewed:
|
||||
|
||||
DATABASE - ensure name is satisfactory - default is "AppVReporting".
|
||||
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
|
||||
@ -203,13 +170,13 @@ Steps to install "AppVReporting" schema in SQL SERVER.
|
||||
|
||||
## INSTALLATION:
|
||||
|
||||
1. Run the database.sql against the "master" database. Your user
|
||||
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
|
||||
2. Run the following scripts against the "AppVReporting" database using the
|
||||
same account as above in order.
|
||||
|
||||
CreateTables.sql
|
||||
@ -222,20 +189,10 @@ Steps to install "AppVReporting" schema in SQL SERVER.
|
||||
|
||||
```
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
**Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Deploying the App-V 5.1 Server](deploying-the-app-v-51-server.md)
|
||||
|
||||
[How to Deploy the App-V 5.1 Server](how-to-deploy-the-app-v-51-server.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -13,19 +13,17 @@ ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
# How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell
|
||||
|
||||
|
||||
Use the following PowerShell procedure to convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by Microsoft SQL Server when running SQL scripts.
|
||||
|
||||
Before attempting this procedure, you should read and understand the information and examples displayed in the following list:
|
||||
|
||||
- **.INPUTS** – The account or accounts used to convert to SID format. This can be a single account name or an array of account names.
|
||||
- **.INPUTS** – The account or accounts used to convert to SID format. This can be a single account name or an array of account names.
|
||||
|
||||
- **.OUTPUTS** - A list of account names with the corresponding SID in standard and hexadecimal formats.
|
||||
- **.OUTPUTS** - A list of account names with the corresponding SID in standard and hexadecimal formats.
|
||||
|
||||
- **Examples** -
|
||||
- **Examples** -
|
||||
|
||||
**.\\ConvertToSID.ps1 DOMAIN\\user\_account1 DOMAIN\\machine\_account1$ DOMAIN\\user\_account2 | Format-List**.
|
||||
|
||||
@ -33,13 +31,10 @@ Before attempting this procedure, you should read and understand the information
|
||||
|
||||
**.\\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\\SIDs.txt -Width 200**
|
||||
|
||||
\#>
|
||||
|
||||
**To convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs)**
|
||||
## To convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs)
|
||||
|
||||
1. Copy the following script into a text editor and save it as a PowerShell script file, for example **ConvertToSIDs.ps1**.
|
||||
|
||||
2. To open a PowerShell console click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**.
|
||||
1. To open a PowerShell console click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**.
|
||||
|
||||
```powershell
|
||||
<#
|
||||
@ -61,7 +56,7 @@ Before attempting this procedure, you should read and understand the information
|
||||
function ConvertSIDToHexFormat
|
||||
{
|
||||
|
||||
param(\[System.Security.Principal.SecurityIdentifier\]$sidToConvert)
|
||||
param([System.Security.Principal.SecurityIdentifier]$sidToConvert)
|
||||
|
||||
$sb = New-Object System.Text.StringBuilder
|
||||
[int] $binLength = $sidToConvert.BinaryLength
|
||||
@ -79,7 +74,7 @@ Before attempting this procedure, you should read and understand the information
|
||||
|
||||
[string]::Format("{0}====== Description ======{0}{0}" +
|
||||
" Converts any number of user or machine account names to string and hexadecimal SIDs.{0}" +
|
||||
" Pass the account(s) as space separated command line parameters. (For example 'ConvertToSID.exe DOMAIN\\Account1 DOMAIN\\Account2 ...'){0}" +
|
||||
" Pass the account(s) as space separated command line parameters. (For example 'ConvertToSID.ps1 DOMAIN\Account1 DOMAIN\Account2 ...'){0}" +
|
||||
" The output is written to the console in the format 'Account name SID as string SID as hexadecimal'{0}" +
|
||||
" And can be written out to a file using standard PowerShell redirection{0}" +
|
||||
" Please specify user accounts in the format 'DOMAIN\username'{0}" +
|
||||
@ -131,17 +126,21 @@ Before attempting this procedure, you should read and understand the information
|
||||
Write-Output $SIDs
|
||||
}
|
||||
}
|
||||
3. Run the script you saved in step one of this procedure passing the accounts to convert as arguments.
|
||||
```
|
||||
|
||||
1. Run the script you saved in step one of this procedure passing the accounts to convert as arguments.
|
||||
|
||||
For example,
|
||||
|
||||
**.\\ConvertToSID.ps1 DOMAIN\\user\_account1 DOMAIN\\machine\_account1$ DOMAIN\\user\_account2 | Format-List” or “$accountsArray = @("DOMAIN\\user\_account1", "DOMAIN\\machine\_account1$", "DOMAIN\_user\_account2")**
|
||||
**.\\ConvertToSID.ps1 DOMAIN\\user\_account1 DOMAIN\\machine\_account1$ DOMAIN\\user\_account2 | Format-List**
|
||||
|
||||
or
|
||||
|
||||
**$accountsArray = @("DOMAIN\\user\_account1", "DOMAIN\\machine\_account1$", "DOMAIN\_user\_account2")**
|
||||
**.\\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\\SIDs.txt -Width 200**
|
||||
|
||||
**.\\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\\SIDs.txt -Width 200”**
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
**Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Administering App-V 5.1 by Using PowerShell](administering-app-v-51-by-using-powershell.md)
|
||||
|
||||
@ -13,114 +13,74 @@ ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
# How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
|
||||
|
||||
|
||||
Use the following procedure to install the database server and management server on different computers. The computer you plan to install the database server on must be running a supported version of Microsoft SQL or the installation will fail.
|
||||
|
||||
**Note**
|
||||
After you complete the deployment, the **Microsoft SQL Server name**, **instance name** and **database name** will be required by the administrator installing the service to be able to connect to these databases.
|
||||
> [!NOTE]
|
||||
> After you complete the deployment, the **Microsoft SQL Server name**, **instance name** and **database name** will be required by the administrator installing the service to be able to connect to these databases.
|
||||
|
||||
## To install the management database and the management server on separate computers
|
||||
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
1. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
1. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft updates, select **Use Microsoft Update when I check for updates (recommended).** To disable Microsoft updates, select **I don't want to use Microsoft Update**. Click **Next**.
|
||||
1. On the **Feature Selection** page, select the components you want to install by selecting the **Management Server Database** checkbox and click **Next**.
|
||||
1. On the **Installation Location** page, accept the default location and click **Next**.
|
||||
1. On the initial **Create New Management Server Database page**, accept the default selections if appropriate, and click **Next**.
|
||||
|
||||
**To install the management database and the management server on separate computers**
|
||||
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
|
||||
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
|
||||
3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft updates, select **Use Microsoft Update when I check for updates (recommended).** To disable Microsoft updates, select **I don’t want to use Microsoft Update**. Click **Next**.
|
||||
|
||||
4. On the **Feature Selection** page, select the components you want to install by selecting the **Management Server Database** checkbox and click **Next**.
|
||||
|
||||
5. On the **Installation Location** page, accept the default location and click **Next**.
|
||||
|
||||
6. On the initial **Create New Management Server Database page**, accept the default selections if appropriate, and click **Next**.
|
||||
|
||||
If you are using a custom SQL Server instance, then select **Use a custom instance** and type the name of the instance.
|
||||
|
||||
If you are using a custom SQL Server instance, then select **Use a custom instance** and type the name of the instance.\
|
||||
If you are using a custom database name, then select **Custom configuration** and type the database name.
|
||||
|
||||
7. On the next **Create New Management Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**.
|
||||
1. On the next **Create New Management Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**.
|
||||
|
||||
**Note**
|
||||
If you plan to deploy the management server on the same computer you must select **Use this local computer**.
|
||||
> [!NOTE]
|
||||
> If you plan to deploy the management server on the same computer you must select **Use this local computer**.
|
||||
|
||||
1. Specify the user name for the management server **Install Administrator** using the following format: **Domain\\AdministratorLoginName**. Click **Next**.
|
||||
1. To start the installation, click **Install**.
|
||||
|
||||
## To install the reporting database and the reporting server on separate computers
|
||||
|
||||
~~~
|
||||
Specify the user name for the management server **Install Administrator** using the following format: **Domain\\AdministratorLoginName**. Click **Next**.
|
||||
~~~
|
||||
|
||||
8. To start the installation, click **Install**.
|
||||
|
||||
**To install the reporting database and the reporting server on separate computers**
|
||||
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
|
||||
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
|
||||
3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft updates, select **Use Microsoft Update when I check for updates (recommended).** To disable Microsoft updates, select **I don’t want to use Microsoft Update**. Click **Next**.
|
||||
|
||||
4. On the **Feature Selection** page, select the components you want to install by selecting the **Reporting Server Database** checkbox and click **Next**.
|
||||
|
||||
5. On the **Installation Location** page, accept the default location and click **Next**.
|
||||
|
||||
6. On the initial **Create New Reporting Server Database** page, accept the default selections if appropriate, and click **Next**.
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
1. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
1. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft updates, select **Use Microsoft Update when I check for updates (recommended).** To disable Microsoft updates, select **I don't want to use Microsoft Update**. Click **Next**.
|
||||
1. On the **Feature Selection** page, select the components you want to install by selecting the **Reporting Server Database** checkbox and click **Next**.
|
||||
1. On the **Installation Location** page, accept the default location and click **Next**.
|
||||
1. On the initial **Create New Reporting Server Database** page, accept the default selections if appropriate, and click **Next**.
|
||||
|
||||
If you are using a custom SQL Server instance, then select **Use a custom instance** and type the name of the instance.
|
||||
|
||||
If you are using a custom database name, then select **Custom configuration** and type the database name.
|
||||
|
||||
7. On the next **Create New Reporting Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**.
|
||||
1. On the next **Create New Reporting Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**.
|
||||
|
||||
**Note**
|
||||
If you plan to deploy the reporting server on the same computer you must select **Use this local computer**.
|
||||
> [!NOTE]
|
||||
> If you plan to deploy the reporting server on the same computer you must select **Use this local computer**.
|
||||
|
||||
1. Specify the user name for the reporting server **Install Administrator** using the following format: **Domain\\AdministratorLoginName**. Click **Next**.
|
||||
1. To start the installation, click **Install**.
|
||||
|
||||
## To install the management and reporting databases using App-V 5.1 database scripts
|
||||
|
||||
~~~
|
||||
Specify the user name for the reporting server **Install Administrator** using the following format: **Domain\\AdministratorLoginName**. Click **Next**.
|
||||
~~~
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on.
|
||||
1. To extract the App-V 5.1 database scripts, open a command prompt and specify the location where the installation files are saved and run the following command:
|
||||
|
||||
8. To start the installation, click **Install**.
|
||||
**appv\_server\_setup.exe** **/LAYOUT** **/LAYOUTDIR="InstallationExtractionLocation"**.
|
||||
|
||||
**To install the management and reporting databases using App-V 5.1 database scripts**
|
||||
1. After the extraction has been completed, to access the App-V 5.1 database scripts and instructions readme file:
|
||||
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on.
|
||||
- The App-V 5.1 Management Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Management Database**.
|
||||
- The App-V 5.1 Reporting Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Reporting Database**.
|
||||
|
||||
2. To extract the App-V 5.1 database scripts, open a command prompt and specify the location where the installation files are saved and run the following command:
|
||||
1. For each database, copy the scripts to a share and modify them following the instructions in the readme file.
|
||||
|
||||
**appv\_server\_setup.exe** **/LAYOUT** **/LAYOUTDIR=”InstallationExtractionLocation”**.
|
||||
> [!NOTE]
|
||||
> For more information about modifying the required SIDs contained in the scripts, see [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](how-to-install-the-app-v-databases-and-convert-the-associated-security-identifiers--by-using-powershell51.md).
|
||||
|
||||
3. After the extraction has been completed, to access the App-V 5.1 database scripts and instructions readme file:
|
||||
1. Run the scripts on the computer running Microsoft SQL Server.
|
||||
|
||||
- The App-V 5.1 Management Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Management Database**.
|
||||
|
||||
- The App-V 5.1 Reporting Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Reporting Database**.
|
||||
|
||||
4. For each database, copy the scripts to a share and modify them following the instructions in the readme file.
|
||||
|
||||
**Note**
|
||||
For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](how-to-install-the-app-v-databases-and-convert-the-associated-security-identifiers--by-using-powershell51.md).
|
||||
|
||||
|
||||
|
||||
5. Run the scripts on the computer running Microsoft SQL Server.
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
**Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Deploying App-V 5.1](deploying-app-v-51.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user