diff --git a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index fe19df8b7f..78d1788c7a 100644 --- a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -14,74 +14,9 @@ ms.date: 04/19/2017 ## Requirements for using Windows PowerShell cmdlets -Review the following requirements for using the Windows PowerShell cmdlets: - -|Requirement|Details| -|---|---| -||| -||| -||| - - ---- - - - - - - - - - - - - - - - - - - - - -
RequirementDetails

Users can run App-V Server cmdlets only if you grant them access by using one of the following methods:

    -

  • When you are deploying and configuring the App-V Server:

    -

    Specify an Active Directory group or individual user that has permissions to manage the App-V environment. See [How to Deploy the App-V Server](appv-deploy-the-appv-server.md).

    • -

  • After you’ve deployed the App-V Server:

    -

    Use the App-V Management console to add an additional Active Directory group or user. See [How to Add or Remove an Administrator by Using the Management Console](appv-add-or-remove-an-administrator-with-the-management-console.md).

    • -

Cmdlets that require an elevated command prompt

    -

  • Add-AppvClientPackage

    • -

  • Remove-AppvClientPackage

    • -

  • Set-AppvClientConfiguration

    • -

  • Add-AppvClientConnectionGroup

    • -

  • Remove-AppvClientConnectionGroup

    • -

  • Add-AppvPublishingServer

    • -

  • Remove-AppvPublishingServer

    • -

  • Send-AppvClientReport

    • -

  • Set-AppvClientMode

    • -

  • Set-AppvClientPackage

    • -

  • Set-AppvPublishingServer

    • -

Cmdlets that end users can run, unless you configure them to require an elevated command prompt

    -

  • Publish-AppvClientPackage

    • -

  • Unpublish-AppvClientPackage

    • -
-

To configure these cmdlets to require an elevated command prompt, use one of the following methods:

-
    -

  • Run the Set-AppvClientConfiguration cmdlet with the -RequirePublishAsAdmin parameter.

    -

    For more information, see:
    [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)
    [How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).

    • -

  • 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)

    • -
-
- -Alt: - This section will tell you what you'll need to use the PowerShell cmdlets. -### How to let users use cmdlets +### How to let users access PowerShell cmdlets You can grant your users access to PowerShell cmdlets through one of the following methods: @@ -92,28 +27,28 @@ You can grant your users access to PowerShell cmdlets through one of the followi You'll need an elevated command prompt to run the following cmdlets: -* Add-AppvClientPackage -* Remove-AppvClientPackage -* Set-AppvClientConfiguration -* Add-AppvClientConnectionGroup -* Remove-AppvClientConnectionGroup -* Add-AppvPublishingServer -* Remove-AppvPublishingServer -* Send-AppvClientReport -* Set-AppvClientMode -* Set-AppvClientPackage -* Set-AppvPublishingServer +* **Add-AppvClientPackage** +* **Remove-AppvClientPackage** +* **Set-AppvClientConfiguration** +* **Add-AppvClientConnectionGroup** +* **Remove-AppvClientConnectionGroup** +* **Add-AppvPublishingServer** +* **Remove-AppvPublishingServer** +* **Send-AppvClientReport** +* **Set-AppvClientMode** +* **Set-AppvClientPackage** +* **Set-AppvPublishingServer** ### Other cmdlets The following cmdlets are ones that end-users can run unless you configure them to require an elevated command prompt. -* Publish-AppvClientPackage -* Unpublish-AppvClientPackage +* **Publish-AppvClientPackage** +* **Unpublish-AppvClientPackage** To configure these cmdlets to require an elevated command prompt, use one of the following methods: -* Run the **Set-AppvClientConfiguration** cmdlet with the *-RequirePublishAsAdmin* parameter. For more information, see the following articles: +* 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) * [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs) * 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). @@ -131,83 +66,30 @@ To load the Windows PowerShell cmdlet modules: |App-V Sequencer|**Import-Module AppvSequencer**| |App-V Client|**Import-Module AppvClient**| - ---- - - - - - - - - - - - - - - - - - - - - -
App-V componentCommand to type

App-V Server

Import-Module AppvServer

App-V Sequencer

Import-Module AppvSequencer

App-V Client

Import-Module AppvClient

- ## Getting help for the Windows PowerShell cmdlets Starting in App-V 5.0 SP3, cmdlet help is available in two formats: -* **As a downloadable module**: To download the latest help after downloading the cmdlet module, open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE), and type one of the following commands: +* As a downloadable module in PowerShell. To access the module, open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE) and enter one of the cmdlets from the following table. |App-v component|Cmdlet to enter| |---|---| -||| -||| -||| +|App-V Server|**Update-Help -Module AppvServer**| +|App-V Sequencer|**Update-Help -Module AppvSequencer**| +|App-V Client|**Update-Help -Module AppvClient**| - ---- - - - - - - - - - - - - - - - - - - - - -
App-V componentCommand to type

App-V Server

Update-Help -Module AppvServer

App-V Sequencer

Update-Help -Module AppvSequencer

App-V Client

Update-Help -Module AppvClient

- -
- -* **On TechNet as web pages**: See the App-V node under [Microsoft Desktop Optimization Pack Automation with Windows PowerShell](https://technet.microsoft.com/library/dn520245.aspx). +* Online in the [Microsoft Desktop Optimization Pack](https://docs.microsoft.com/en-us/powershell/mdop/get-started?view=win-mdop2-ps). ## Displaying the help for a Windows PowerShell cmdlet To display help for a specific Windows PowerShell cmdlet: 1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). -2. Enter **Get-Help** <*cmdlet*>, for example, **Get-Help Publish-AppvClientPackage**. +2. Enter **Get-Help** followed by the cmdlet you need help with. For example: + ```PowerShell + Get-Help Publish-AppvClientPackage + ``` ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](https://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). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). \ No newline at end of file diff --git a/windows/application-management/app-v/appv-maintaining-appv.md b/windows/application-management/app-v/appv-maintaining-appv.md index 3db885c191..6e1292f604 100644 --- a/windows/application-management/app-v/appv-maintaining-appv.md +++ b/windows/application-management/app-v/appv-maintaining-appv.md @@ -8,43 +8,26 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- - - # Maintaining App-V -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 After you have deployed App-V for Windows 10, you can use the following information to maintain the App-V infrastructure. ## Moving the App-V server -The App-V server connects to the App-V database. Therefore you can install the management component on any computer on the network and then connect it to the App-V database. - -[How to Move the App-V Server to Another Computer](appv-move-the-appv-server-to-another-computer.md) - -## Determine if an App-V Application is Running Virtualized +The App-V server connects to the App-V database. Therefore you can install the management component on any computer on the network and then connect it to the App-V database. For more information, see [How to move the App-V server to another computer](appv-move-the-appv-server-to-another-computer.md). +## Determine if an App-V application is running virtualized Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V should open a named object called **AppVVirtual-<PID>** in the default namespace. For example, Windows API **GetCurrentProcessId()** can be used to obtain the current process's ID, for example 4052, and then if a named Event object called **AppVVirtual-4052** can be successfully opened using **OpenEvent()** in the default namespace for read access, then the application is virtual. If the **OpenEvent()** call fails, the application is not virtual. -Additionally, ISV’s who want to explicitly virtualize or not virtualize calls on specific API’s with App-V 5.1 and later, can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module. These provide a way of hinting at a downstream component that the call should or should not be virtualized. +Additionally, ISV’s who want to explicitly virtualize or not virtualize calls on specific APIs with App-V 5.1 and later, can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module. These provide a way of hinting at a downstream component that the call should or should not be virtualized. ## Have a suggestion for App-V? - -Add or vote on suggestions on the [Application Virtualization feedback site](https://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). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). ## Other resources for maintaining App-V - -[Operations for App-V](appv-operations.md) - -  - -  - - - - - +* [Operations for App-V](appv-operations.md) \ No newline at end of file