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

fixed formatting issues

Browse Source
This commit is contained in:
Brian Lich 2016-08-01 13:22:22 -07:00
parent 574cec20a6
commit 619e329786
2 changed files with 44 additions and 73 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
windows/manage/appv-convert-a-package-created-in-a-previous-version-of-appv.md
View File

@ -11,18 +11,17 @@ ms.prod: w10
# How to Convert a Package Created in a Previous Version of App-V # How to Convert a Package Created in a Previous Version of App-V
You can use the package converter utility to upgrade virtual application packages that have been created with previous versions of App-V. You can use the package converter utility to upgrade virtual application packages that have been created with previous versions of App-V.
**Note**   > [!NOTE]
If you are running a computer with a 64-bit architecture, you must use the x86 version of PowerShell. > 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 that were created by using the App-V 4.5 sequencer or a subsequent version. Packages that were created using a version prior to App-V 4.5 must be upgraded to the App-V 4.5 or App-V 4.6 format before conversion. The package converter can only directly convert packages that were created by using the App-V 4.5 sequencer or later. Packages that were created using a version prior to App-V 4.5 must be upgraded to at least App-V 4.5 before conversion.
The following information provides direction for converting existing virtual application packages. The following information provides direction for converting existing virtual application packages.
**Important**   > [!IMPORTANT]
You must configure the package converter to always save the package ingredients file to a secure location and directory. A secure location is accessible only by an administrator. Additionally, when you deploy the package, you should save the package to a location that is secure, or make sure that no other user is allowed to be logged in during the conversion process. > You must configure the package converter to always save the package ingredients file to a secure location and directory. A secure location is accessible only by an administrator. Additionally, when you deploy the package, you should save the package to a location that is secure, or make sure that no other user is allowed to be logged in during the conversion process.
## App-V 4.6 installation folder is redirected to virtual file system root ## App-V 4.6 installation folder is redirected to virtual file system root
@ -42,7 +41,8 @@ When you convert packages from App-V 4.6 to App-V for Windows 10, the App-V for
Additionally, the package converter optimizes performance of packages in App-V for Windows 10 by setting the package to stream fault the App-V package.  This 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. Additionally, the package converter optimizes performance of packages in App-V for Windows 10 by setting the package to stream fault the App-V package.  This 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. > [!NOTE]
> Before you specify the output directory, you must create the output directory.
### Advanced Conversion Tips ### Advanced Conversion Tips
@ -58,4 +58,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics ## Related topics
[Operations for App-V](appv-operations.md) - [Operations for App-V](appv-operations.md)

101
windows/manage/appv-deploy-appv-databases-with-sql-scripts.md
View File

@ -11,15 +11,14 @@ ms.prod: w10
# How to Deploy the App-V Databases by Using SQL Scripts # 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: 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]
If you have already deployed the App-V 5.0 SP3 database, the SQL scripts are not required to upgrade to App-V. > 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.
## How to install the App-V databases by using SQL scripts ## How to install the App-V databases by using SQL scripts
@ -29,51 +28,36 @@ If you have already deployed the App-V 5.0 SP3 database, the SQL scripts are not
3. From a command prompt, run **appv\_server\_setup.exe** and specify a temporary location for extracting the database scripts. 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:\\&lt;temporary location path&gt; 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: 4. Browse to the temporary location that you created, open the extracted **DatabaseScripts** folder, and review the appropriate readme.txt file for instructions:
<table> | Database | Location of readme.txt file to use
<colgroup> | - | - |
<col width="50%" /> | Management database | ManagementDatabase subfolder |
<col width="50%" /> | Reporting database | ReportingDatabase subfolder |
</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**&nbsp;&nbsp;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. > [!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**&nbsp;&nbsp;The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3.<br>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. > [!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 ``` 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:
1.Review the Microsoft Application Virtualization Server 5.0 license terms.
2.Print and retain a copy of the license terms for your records.
By running the Microsoft Application Virtualization Database Scripts you agree to such license terms. If you do not accept them, do not use the software.
******************************************************************
- 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. Steps to install "AppVManagement" schema in SQL SERVER.
## PREREQUISITES: ## PREREQUISITES:
1. Review the installation package. The following files MUST exist: 1. Review the installation package. The following files MUST exist:
@ -90,10 +74,7 @@ Steps to install "AppVManagement" schema in SQL SERVER.
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 necessary SQL Server client software is installed and available from
the specified location. Specifically, the "osql" command must the specified location. Specifically, the "osql" command must be supported for these scripts to run.
## be supported for these scripts to run.
## PREPARATION: ## PREPARATION:
@ -104,10 +85,7 @@ Steps to install "AppVManagement" schema in SQL SERVER.
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 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 for setting up read and write access on the database. Note: Default settings in the file will not work.
## in the file will not work.
## INSTALLATION: ## INSTALLATION:
@ -121,23 +99,24 @@ Steps to install "AppVManagement" schema in SQL SERVER.
CreateTables.sql CreateTables.sql
CreateStoredProcs.sql CreateStoredProcs.sql
UpdateTables.sql UpdateTables.sql
## Permissions.sql Permissions.sql
``` ```
### Updated reporting database README file content ### Updated reporting 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:
1.Review the Microsoft Application Virtualization Server 5.0 license terms.
2.Print and retain a copy of the license terms for your records. - Review the license terms.
By running the Microsoft Application Virtualization Database Scripts you agree to such license terms. If you do not accept them, do not use the software. - 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. Steps to install "AppVReporting" schema in SQL SERVER.
## PREREQUISITES: ## PREREQUISITES:
1. Review the installation package. The following files MUST exist: 1. Review the installation package. The following files MUST exist:
@ -157,10 +136,7 @@ Steps to install "AppVReporting" schema in SQL SERVER.
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 executable from necessary SQL Server client software is installed and executable from
the location you have chosen. Specifically, the "osql" command must the location you have chosen. Specifically, the "osql" command must be supported for these scripts to run.
## be supported for these scripts to run.
## PREPARATION: ## PREPARATION:
@ -176,10 +152,7 @@ Steps to install "AppVReporting" schema in SQL SERVER.
3. Review the ScheduleReportingJob.sql file and make sure that the stored proc schedule 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). 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 If this time is not suitable, you can change this to a more suitable time. The time is in the format HHMMSS.
## in the format HHMMSS.
## INSTALLATION: ## INSTALLATION:
@ -197,8 +170,7 @@ Steps to install "AppVReporting" schema in SQL SERVER.
CreateStoredProcs.sql CreateStoredProcs.sql
CreateViews.sql CreateViews.sql
Permissions.sql Permissions.sql
## ScheduleReportingJob.sql ScheduleReportingJob.sql
``` ```
## Have a suggestion for App-V? ## Have a suggestion for App-V?
@ -207,6 +179,5 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## 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)