deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Attempt to fix link by changing title

Browse Source
This commit is contained in:
Heidi Lohr
2018-08-20 16:34:44 -07:00
parent 7897db3184
commit 8a10955489
4 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md
View File

@ -22,7 +22,7 @@ Here's how to enable only administrators to publish or unpublish packages:
2. Enable the **Require publish as administrator** Group Policy setting.
To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending).
To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages:-userpending-and-globalpending).
## Have a suggestion for App-V?

4
windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md
View File

@ -50,8 +50,8 @@ To configure these cmdlets to require an elevated command prompt, use one of the
* Run the **Set-AppvClientConfiguration** cmdlet with the *-RequirePublishAsAdmin* parameter. For more information, see the following resources:
* [How to manage connection groups on a stand-alone computer by using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)
* [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending)
* Enable the “Require publish as administrator” Group Policy setting for App-V Clients. For more information, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md).
* [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages:-userpending-and-globalpending)
* Enable the **Require publish as administrator** Group Policy setting for App-V Clients. For more information, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md).
## Loading the Windows PowerShell cmdlets

6
windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md
View File

@ -39,7 +39,7 @@ $Contoso = Add-AppvClientPackage \\\\path\\to\\appv\\package.appv
## Publish a package
Use the **Publish-AppvClientPackage** cmdlet to publish a package that has been added to a specific user or globally to any user on the computer.
Use the **Publish-AppvClientPackage** cmdlet to publish a package that has been added to either a specific user or globally to any user on the computer.
Enter the cmdlet with the application name to publish it to the user.
@ -58,7 +58,7 @@ Publish-AppvClientPackage “ContosoApplication” -Global
>[!NOTE]  
>You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
An administrator can publish a package to a specific user by specifying the optional *–UserSID* parameter with the **Publish-AppvClientPackage** cmdlet, where **-UserSID** represents the end user’s security identifier (SID).
An administrator can publish a package to a specific user by specifying the optional *–UserSID* parameter with the **Publish-AppvClientPackage** cmdlet, where *-UserSID* represents the end user’s security identifier (SID).
To use this parameter:
@ -143,7 +143,7 @@ Set-AppvClientConfiguration –RequirePublishAsAdmin1
To use the App-V Management console to set this configuration, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md).
## Understanding pending packages: UserPending and GlobalPending
## About pending packages: UserPending and GlobalPending
Starting in App-V 5.0 SP2, if you run a Windows PowerShell cmdlet that affects a package currently in use, the task you're trying to perform is placed in a pending state. For example, if you try to publish a package when an application in that package is being used, and then run **Get-AppvClientPackage**, the pending status appears in the cmdlet output as follows:

2
windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md
View File

@ -38,7 +38,7 @@ The ability to enable only administrators to publish or unpublish packages (desc
2. Enable the **Require publish as administrator** Group Policy setting.
To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending).
To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages:-userpending-and-globalpending).
## Have a suggestion for App-V?