deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 21:37:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Finished "SQL scripts" article, created and did first sweep of "install the publishing server on a remote computer" article.

Browse Source
This commit is contained in:
Heidi Lohr 2018-02-12 10:51:09 -08:00
parent d91dc0162d
commit 3755dbb102
2 changed files with 79 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
windows/application-management/app-v/appv-deploy-appv-databases-with-sql-scripts.md
View File

@ -8,14 +8,13 @@ ms.sitesec: library
ms.prod: w10 ms.prod: w10
ms.date: 04/19/2017 ms.date: 04/19/2017
--- ---
# How to Deploy the App-V Databases by Using SQL Scripts # How to deploy the App-V databases by using SQL scripts
>Applies to Windows Server 2016. >Applies to Windows Server 2016.
Use the following instructions to use SQL scripts, rather than the Windows Installer, to: Use the following instructions to use SQL scripts, rather than the Windows Installer, to:
* Install the App-V databases * Install the App-V databases
* Upgrade the App-V databases to a later version * Upgrade the App-V databases to a later version
>[!NOTE] >[!NOTE]
@ -23,31 +22,28 @@ Use the following instructions to use SQL scripts, rather than the Windows Insta
## How to install the App-V databases by using SQL scripts ## 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. 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 the **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.
2. Copy the **appv\_server\_setup.exe** from the App-V release media to a temporary location. For 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:
3. From a command prompt, run **appv\_server\_setup.exe** and specify a temporary location for extracting the database scripts. | Database | Location of **readme.txt** file to use |
|---|---|
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:
| Database | Location of readme.txt file to use
| - | - |
| Management database | ManagementDatabase subfolder | | Management database | ManagementDatabase subfolder |
| Reporting database | ReportingDatabase subfolder | | Reporting database | ReportingDatabase subfolder |
> [!CAUTION] >[!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. >The **readme.txt** file in the ManagementDatabase subfolder is out of date. The information in the following updated readme files is the most current and should supersede the readme information provided in the **DatabaseScripts** folders.
> [!IMPORTANT] >[!IMPORTANT]
> The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3. > 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. > 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 ```syntax
*********************************************************************************************************** ***********************************************************************************************************
Before you install and use the Application Virtualization Database Scripts, you must: Before you install and use the Application Virtualization Database Scripts, you must:
@ -101,7 +97,6 @@ Steps to install "AppVManagement" schema in SQL SERVER.
CreateStoredProcs.sql CreateStoredProcs.sql
UpdateTables.sql UpdateTables.sql
Permissions.sql Permissions.sql
``` ```
### Updated reporting database README file content ### Updated reporting database README file content
@ -180,5 +175,5 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt
## Related topics ## Related topics
- [Deploying the App-V Server](appv-deploying-the-appv-server.md) * [Deploying the App-V server](appv-deploying-the-appv-server.md)
- [How to Deploy the App-V Server](appv-deploy-the-appv-server.md) * [How to deploy the App-V server](appv-deploy-the-appv-server.md)

63
windows/application-management/app-v/revision-heidi/appv-install-the-publishing-server-on-a-remote-computer.md Normal file
View File

@ -0,0 +1,63 @@
---
title: How to Install the Publishing Server on a Remote Computer (Windows 10)
description: How to Install the App-V Publishing Server on a Remote Computer
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
---
# How to Install the Publishing Server on a Remote Computer
>Applies to Windows Server 2016.
Use the following procedure to install the publishing server on a separate computer. Before you perform the following procedure, ensure the database and management server are available.
## Installing the publishing server on a separate computer
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation, run **appv\_server\_setup.exe** as an administrator, then select **Install**.
2. On the **Getting started** page, review and accept the license terms, then select **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 Update, select **I don’t want to use Microsoft Update**. Click **Next**.
4. On the **Feature selection** page, select the **Publishing Server** checkbox, then select **Next**.
5. On the **Installation location** page, accept the default location, then select **Next**.
6. On the **Configure publishing server configuration** page, specify the following items:
* The URL for the management service that the publishing server will connect to. For example, **http://ManagementServerName:12345**.
* Specify the website name that you want to use for the publishing service. If you don't have a custom name, then use the default name.
* For the **Port binding**, specify a unique port number that will be used by App-V. For example, **54321**.
7. On the **Ready to install** page, select **Install**.
8. After the installation is complete, the publishing server must be registered with the management server. In the App-V management console, use the following steps to register the server:
1. Open the App-V management server console.
2. In the left pane, select **Servers**, then select **Register New Server**.
3. Enter the server name and a description (if required), then select **Add**.
9. To verify that the publishing server is running correctly, you should import a package to the management server, entitle that package to an AD group, then publish it. Using an internet browser, open the following URL: **http://publishingserver:pubport**. If the server is running correctly, information like the following example should appear.
```SQL
<Publishing Protocol="1.0">
<Packages>
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />
</Packages>
<NoGroup>
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />
</NoGroup>
</Publishing>
```
## Have a suggestion for App-V?
Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
## Related topics
* [Deploying App-V](appv-deploying-appv.md)