mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge pull request #154 from JanKeller1/8442312
Formatting fixes & typo fixes from visual test pass
This commit is contained in:
Elizabeth Ross
GitHub
commit
5b6a5d1151
@ -23,8 +23,8 @@ Use one of the following methods to allow only administrators to enable or disab
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
<col width="30%" />
|
||||
<col width="70%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
|
||||
@ -232,7 +232,7 @@ The Package Store contains a pristine copy of the package files that have been s
|
||||
|
||||
### 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.
|
||||
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
|
||||
|
||||
|
||||
@ -40,7 +40,7 @@ For more about adding or upgrading packages, see [How to Add or Upgrade Packages
|
||||
|
||||
1. Create the connection group XML document.
|
||||
|
||||
2. For the package to be upgraded, set the **Package** tag attribute **VersionID** to an asterisk (**\***).
|
||||
2. For the package to be upgraded, set the **Package** tag attribute **VersionID** to an asterisk (<strong>*</strong>).
|
||||
|
||||
3. Use the following cmdlet to add the connection group, and include the path to the connection group XML document:
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ Use the following procedure to connect to the App-V Management Console.
|
||||
|
||||
**To connect to the App-V Management Console**
|
||||
|
||||
1. Open Internet Explorer browser and type the address for the App-V. For example, **http://\<_management server name_\>:\<_management service port number_\>/console.html**.
|
||||
1. Open Internet Explorer browser and type the address for the App-V Management server. For example, **http://\<_management server name_\>:\<_management service port number_\>/console.html**.
|
||||
|
||||
2. To view different sections of the console, click the desired section in the navigation pane.
|
||||
|
||||
|
||||
@ -203,87 +203,60 @@ The virtual application Microsoft Outlook is running in virtual environment **XY
|
||||
|
||||
## <a href="" id="bkmk-va-conn-configs"></a>Supported virtual application connection configurations
|
||||
|
||||
The following application connection configurations are supported.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Configuration</th>
|
||||
<th align="left">Example scenario</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>An. exe file and plug-in (.dll)</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>You want to distribute Microsoft Office to all users, but distribute a Microsoft Excel plug-in to only a subset of users.</p></li>
|
||||
<li><p>Enable the connection group for the appropriate users.</p></li>
|
||||
<li><p>Update each package individually as required.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>An. exe file and a middleware application</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>You have an application requires a middleware application, or several applications that all depend on the same middleware runtime version.</p></li>
|
||||
<li><p>All computers that require one or more of the applications receive the connection groups with the application and middleware application runtime.</p></li>
|
||||
<li><p>You can optionally combine multiple middleware applications into a single connection group.</p>
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Example</th>
|
||||
<th align="left">Example description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Virtual application connection group for the financial division</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Middleware application 1</p></li>
|
||||
<li><p>Middleware application 2</p></li>
|
||||
<li><p>Middleware application 3</p></li>
|
||||
<li><p>Middleware application runtime</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Virtual application connection group for HR division</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Middleware application 5</p></li>
|
||||
<li><p>Middleware application 6</p></li>
|
||||
<li><p>Middleware application runtime</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>An. exe file and an .exe file</p></td>
|
||||
<td align="left"><p>You have an application that relies on another application, and you want to keep the packages separate for operational efficiencies, licensing restrictions, or rollout timelines.</p>
|
||||
<p><strong>Example:</strong></p>
|
||||
<p>If you are deploying Microsoft Lync 2010, you can use three packages:</p>
|
||||
<ul>
|
||||
<li><p>Microsoft Office 2010</p></li>
|
||||
<li><p>Microsoft Communicator 2007</p></li>
|
||||
<li><p>Microsoft Lync 2010</p></li>
|
||||
</ul>
|
||||
<p>You can manage the deployment using the following connection groups:</p>
|
||||
<ul>
|
||||
<li><p>Microsoft Office 2010 and Microsoft Communicator 2007</p></li>
|
||||
<li><p>Microsoft Office 2010 and Microsoft Lync 2010</p></li>
|
||||
</ul>
|
||||
<p>When the deployment has completed, 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 by using a connection group.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
- **An. exe file and plug-in (.dll)**. For example, you might want to distribute Microsoft Office to all users, but distribute a Microsoft Excel plug-in to only a subset of users.
|
||||
|
||||
Enable the connection group for the appropriate users. Update each package individually as required.
|
||||
|
||||
- **An. exe file and a middleware application**. You might 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.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Example</th>
|
||||
<th align="left">Example description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Virtual application connection group for the financial division</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Middleware application 1</p></li>
|
||||
<li><p>Middleware application 2</p></li>
|
||||
<li><p>Middleware application 3</p></li>
|
||||
<li><p>Middleware application runtime</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Virtual application connection group for HR division</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Middleware application 5</p></li>
|
||||
<li><p>Middleware application 6</p></li>
|
||||
<li><p>Middleware application runtime</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
- **An. exe file and an .exe file**. You might have an application that relies on another application, and 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<br><br>
|
||||
|
||||
You can manage the deployment using the following connection groups:
|
||||
- Microsoft Office 2010 and Microsoft Communicator 2007
|
||||
- Microsoft Office 2010 and Microsoft Lync 2010<br><br>
|
||||
|
||||
When the deployment has completed, 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 by using a connection group.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
@ -14,61 +14,44 @@ ms.prod: w10
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
|
||||
**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.
|
||||
|
||||
|
||||
|
||||
Use the following procedure to create a virtual application package with the App-V Package Accelerator.
|
||||
|
||||
**Note**
|
||||
Before you start this procedure, copy the required Package Accelerator locally to the computer that runs the App-V Sequencer. You should also copy all required installation files for the package to a local directory on the computer that runs the Sequencer. This is the directory that you have to specify in step 5 of this procedure.
|
||||
|
||||
|
||||
> **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.
|
||||
|
||||
**To create a virtual application package with an App-V Package Accelerator**
|
||||
|
||||
1. To start the App-V Sequencer, on the computer that runs the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
|
||||
1. Be sure that the required Package Accelerator has been copied locally to the computer that runs the App-V Sequencer. Also copy all required installation files for the package to a local folder on the computer that runs the Sequencer. This is the folder that you have to specify in step 6 of this procedure.
|
||||
|
||||
2. To start the **Create New Package Wizard**, click **Create a New Virtual Application Package**. To create the package, select the **Create Package using a Package Accelerator** check box, and then click **Next**.
|
||||
2. To start the App-V Sequencer, on the computer that runs the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
3. To specify the package accelerator that will be used to create the new virtual application package, click **Browse** on the **Select Package Accelerator** page. Click **Next**.
|
||||
3. To start the **Create New Package Wizard**, click **Create a New Virtual Application Package**. To create the package, select the **Create Package using a Package Accelerator** check box, and then click **Next**.
|
||||
|
||||
**Important**
|
||||
If the publisher of the package accelerator cannot be verified and does not contain a valid digital signature, then before you click **Run**, you must confirm that you trust the source of the package accelerator. Confirm your choice in the **Security Warning** dialog box.
|
||||
4. To specify the package accelerator that will be used to create the new virtual application package, click **Browse** on the **Select Package Accelerator** page. Click **Next**.
|
||||
|
||||
|
||||
> **Important** If the publisher of the package accelerator cannot be verified and does not contain a valid digital signature, then before you click **Run**, you must confirm that you trust the source of the package accelerator. Confirm your choice in the **Security Warning** dialog box.
|
||||
|
||||
4. 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, click **Export** and specify the location where the file should be saved, and then click **Next**.
|
||||
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, click **Export** and specify the location where the file should be saved, and then click **Next**.
|
||||
|
||||
5. On the **Select Installation Files** page, click **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, click **Browse** to select the folder.
|
||||
6. On the **Select Installation Files** page, click **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, click **Browse** to select the folder.
|
||||
|
||||
Alternatively, if you have already copied the installation files to a directory on this computer, click **Make New Folder**, browse to the folder that contains the installation files, and then click **Next**.
|
||||
|
||||
**Note**
|
||||
You can specify the following types of supported installation files:
|
||||
> **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.
|
||||
|
||||
- Windows Installer files (**.msi**)
|
||||
7. If the package accelerator requires an application to be installed before you apply the Package Accelerator, and if you have already installed the required application, select **I have installed all applications**, and then click **Next** on the **Local Installation** page.
|
||||
|
||||
- Cabinet files (.cab)
|
||||
8. On the **Package Name** page, specify a name that will be associated with the package. The name that you specify identifies the package in the App-V Management Console. Click **Next**.
|
||||
|
||||
- Compressed files with a .zip file name extension
|
||||
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 that is 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 when the package size exceeds 4 GB.
|
||||
|
||||
- The actual application files
|
||||
10. To create the package, click **Create**. After the package is created, click **Next**.
|
||||
|
||||
The following file types are not supported: **.msp** and **.exe** files. If you specify an **.exe** file, you must extract the installation files manually.
|
||||
|
||||
|
||||
|
||||
If the package accelerator requires an application to be installed before you apply the Package Accelerator, and if you have already installed the required application, select **I have installed all applications**, and then click **Next** on the **Local Installation** page.
|
||||
|
||||
6. On the **Package Name** page, specify a name that will be associated with the package. The name that you specify identifies the package in the App-V Management Console. Click **Next**.
|
||||
|
||||
7. 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 that is 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 when the package size exceeds 4 GB.
|
||||
|
||||
To create the package, click **Create**. After the package is created, click **Next**.
|
||||
|
||||
8. On the **Configure Software** page, to enable the Sequencer to configure the applications that are contained in the package, select **Configure Software**. In this step you can configure any associated tasks that must be completed in order to run the application on the target computers. For example, you can configure any associated license agreements.
|
||||
11. On the **Configure Software** page, to enable the Sequencer to configure the applications that are contained in the package, select **Configure Software**. In this step you can configure any associated tasks that must be completed in order to run the application on the target computers. For example, you can configure any associated license agreements.
|
||||
|
||||
If you select **Configure Software**, the following items can be configured using the Sequencer as part of this step:
|
||||
|
||||
@ -80,9 +63,9 @@ Before you start this procedure, copy the required Package Accelerator locally t
|
||||
|
||||
- **Primary Feature Block**. The Sequencer optimizes the package for streaming by rebuilding the primary feature block.
|
||||
|
||||
If you do not want to configure the applications, click **Skip this step**, and to go to step 9 of this procedure, and then click **Next**.
|
||||
If you do not want to configure the applications, click **Skip this step**, and then click **Next**.
|
||||
|
||||
9. On the **Completion** page, after you review the information that is displayed in the **Virtual Application Package Report** pane, click **Close**.
|
||||
12. On the **Completion** page, after you review the information that is displayed in the **Virtual Application Package Report** pane, click **Close**.
|
||||
|
||||
The package is now available in the Sequencer. To edit the package properties, click **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).
|
||||
|
||||
|
||||
@ -16,10 +16,7 @@ ms.prod: w10
|
||||
|
||||
You can use an App-V project template to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment. Using a project template can streamline the process of creating virtual application packages.
|
||||
|
||||
**Note**
|
||||
You can, and often should apply an App-V project template during a package upgrade. For example, if you sequenced an application with a custom exclusion list, it is recommended that an associated template is created and saved for later use while upgrading the sequenced application.
|
||||
|
||||
|
||||
> **Note** You can, and often should apply an App-V project template during a package upgrade. For example, if you sequenced an application with a custom exclusion list, it is recommended that an associated template is created and saved for later use while upgrading the sequenced application.
|
||||
|
||||
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.
|
||||
|
||||
@ -29,25 +26,19 @@ Use the following procedures to create and apply a new template.
|
||||
|
||||
1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. **Note**
|
||||
If the virtual application package is currently open in the App-V Sequencer console, skip to step 3 of this procedure.
|
||||
> **Note** If the virtual application package is currently open in the App-V Sequencer console, skip to step 3 of this procedure.
|
||||
|
||||
|
||||
|
||||
To open the existing virtual application package that contains the settings you want to save with the App-V project template, click **File** / **Open**, and then click **Edit Package**. On the **Select Package** page, click **Browse** and locate the virtual application package that you want to open. Click **Edit**.
|
||||
2. To open the existing virtual application package that contains the settings you want to save with the App-V project template, click **File** / **Open**, and then click **Edit Package**. On the **Select Package** page, click **Browse** and locate the virtual application package that you want to open. Click **Edit**.
|
||||
|
||||
3. In the App-V Sequencer console, to save the template file, click **File** / **Save As Template**. After you have reviewed the settings that will be saved with the new template, click **OK**. Specify a name that will be associated with the new App-V project template. Click Save.
|
||||
|
||||
The new App-V project template is saved in the directory specified in step 3 of this procedure.
|
||||
The new App-V project template is saved in the folder you specified.
|
||||
|
||||
**To apply a project template**
|
||||
|
||||
1. **Important**
|
||||
Creating a virtual application package using a project template in conjunction with a Package Accelerator is not supported.
|
||||
> **Important** Creating a virtual application package using a project template in conjunction with a Package Accelerator is not supported.
|
||||
|
||||
|
||||
|
||||
To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
|
||||
1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. To create or upgrade a new virtual application package by using an App-V project template, click **File** / **New From Template**.
|
||||
|
||||
|
||||
@ -69,8 +69,8 @@ Use the following information to publish a package that has been added to a spec
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
<col width="30%" />
|
||||
<col width="70%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
@ -176,18 +176,12 @@ App-V cmdlets have been assigned to variables for the previous examples for clar
|
||||
|
||||
## <a href="" id="bkmk-admins-pub-pkgs"></a>To enable only administrators to publish or unpublish packages
|
||||
|
||||
|
||||
**Note**
|
||||
**This feature is supported starting in App-V 5.0 SP3.**
|
||||
|
||||
|
||||
|
||||
Use the following cmdlet and parameter to enable only administrators (not end users) to publish or unpublish packages:
|
||||
Starting in App-V 5.0 SP3, you can use the following cmdlet and parameter to enable only administrators (not end users) to publish or unpublish packages:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
<col width="30%" />
|
||||
<col width="70%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
@ -218,8 +212,8 @@ To use the App-V Management console to set this configuration, see [How to Publi
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
<col width="30%" />
|
||||
<col width="70%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
|
||||
@ -19,9 +19,7 @@ Connection groups enable the applications within a package to interact with each
|
||||
**Note**
|
||||
In some previous versions of App-V, connection groups were referred to as Dynamic Suite Composition.
|
||||
|
||||
|
||||
|
||||
**In this topic:**
|
||||
**In this section:**
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -53,7 +51,14 @@ In some previous versions of App-V, connection groups were referred to as Dynami
|
||||
<td align="left"><p>[How to Publish a Connection Group](appv-publish-a-connection-group.md)</p></td>
|
||||
<td align="left"><p>Explains how to publish a connection group.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Make a Connection Group Ignore the Package Version](appv-configure-connection-groups-to-ignore-the-package-version.md)</p></td>
|
||||
<td align="left"><p>Explains how to configure a connection group to accept any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Allow Only Administrators to Enable Connection Groups](appv-allow-administrators-to-enable-connection-groups.md)</p></td>
|
||||
<td align="left"><p>Explains how to configure the App-V client so that only administrators (not end users) can enable or disable connection groups.</p></td>
|
||||
</tr></tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
@ -30,8 +30,8 @@ You can also use the `–OSDsToIncludeInPackage` parameter with the `ConvertFrom
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">New in App-V</th>
|
||||
<th align="left">Prior to App-V</th>
|
||||
<th align="left">New in App-V for Windows 10</th>
|
||||
<th align="left">Prior to App-V for Windows 10</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
|
||||
@ -27,7 +27,7 @@ You should read and understand the following information before reading this doc
|
||||
- [App-V Sequencing Guide](https://www.microsoft.com/en-us/download/details.aspx?id=27760)
|
||||
|
||||
**Note**
|
||||
Some terms used in this document may have different meanings depending on external source and context. For more information about terms used in this document followed by an asterisk **\*** review the [Application Virtualization Performance Guidance Terminology](#bkmk-terms1) section of this document.
|
||||
Some terms used in this document may have different meanings depending on external source and context. For more information about terms used in this document followed by an asterisk <strong>*</strong> review the [Application Virtualization Performance Guidance Terminology](#bkmk-terms1) section of this document.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -113,7 +113,7 @@ Use the following example syntax, and substitute the name of your package for **
|
||||
|
||||
`Start-AppvVirtualProcess -AppvClientObject $AppVName cmd.exe`
|
||||
|
||||
If you don’t know the exact name of your package, you can use the command line **Get-AppvClientPackage \*executable\***, where **executable** is the name of the application, for example: Get-AppvClientPackage \*Word\*.
|
||||
If you don’t know the exact name of your package, you can use the command line <strong>Get-AppvClientPackage \*executable\*</strong>, where **executable** is the name of the application, for example:<br>Get-AppvClientPackage \*Word\*
|
||||
|
||||
## <a href="" id="bkmk-cl-switch-appvpid"></a>Command line switch /appvpid:<PID>
|
||||
|
||||
@ -143,7 +143,7 @@ To get the package GUID and version GUID of your application, run the **Get-Appv
|
||||
|
||||
- Version ID of the desired package
|
||||
|
||||
If you don’t know the exact name of your package, use the command line **Get-AppvClientPackage \*executable\***, where **executable** is the name of the application, for example: Get-AppvClientPackage \*Word\*.
|
||||
If you don’t know the exact name of your package, use the command line <strong>Get-AppvClientPackage \*executable\*</strong>, where **executable** is the name of the application, for example:<br>Get-AppvClientPackage \*Word\*
|
||||
|
||||
This method lets you launch any command within the context of an App-V package, regardless of whether the package is currently running.
|
||||
|
||||
|
||||
@ -41,8 +41,8 @@ The client management console contains the following described main tabs.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
<col width="20%" />
|
||||
<col width="80%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user