Making sure PowerShell has Windows in front of it

This commit is contained in:
JanKeller1
2016-08-17 15:21:33 -07:00
parent 2e636b86d0
commit 02f1e34ce1
28 changed files with 208 additions and 408 deletions

View File

@ -23,7 +23,7 @@ Use any of the following methods to open a local application inside the App-V vi
- [RunVirtual registry key](#bkmk-runvirtual-regkey)
- [Get-AppvClientPackage PowerShell cmdlet](#bkmk-get-appvclientpackage-posh)
- [Get-AppvClientPackage Windows PowerShell cmdlet](#bkmk-get-appvclientpackage-posh)
- [Command line switch /appvpid:<PID>](#bkmk-cl-switch-appvpid)
@ -101,7 +101,7 @@ Starting with App-V 5.0 SP3, when using RunVirtual, you can publish packages glo
@="aaaaaaaa-bbbb-cccc-dddd-eeeeeeee_11111111-2222-3333-4444-555555555
```
## <a href="" id="bkmk-get-appvclientpackage-posh"></a>Get-AppvClientPackage PowerShell cmdlet
## <a href="" id="bkmk-get-appvclientpackage-posh"></a>Get-AppvClientPackage Windows PowerShell cmdlet
You can use the **Start-AppVVirtualProcess** cmdlet to retrieve the package name and then start a process within the specified package's virtual environment. This method lets you launch any command within the context of an App-V package, regardless of whether the package is currently running.