diff --git a/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md b/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md index 9fb4652fa5..62d2a67615 100644 --- a/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md +++ b/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md @@ -239,68 +239,10 @@ The XML file that is included in the Office Deployment Tool specifies the produc ``` - **Note**   + **Note**
The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. -   - - The above XML configuration file specifies that Office 2013 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2013, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2013 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
InputDescriptionExample

Add element

Specifies the products and languages to include in the package.

N/A

OfficeClientEdition (attribute of Add element)

Specifies the edition of Office 2013 product to use: 32-bit or 64-bit. The operation fails if OfficeClientEdition is not set to a valid value.

OfficeClientEdition="32"

-

OfficeClientEdition="64"

Product element

Specifies the application. Project 2013 and Visio 2013 must be specified here as an added product to be included in the applications.

Product ID ="O365ProPlusRetail "

-

Product ID ="VisioProRetail"

-

Product ID ="ProjectProRetail"

-

Product ID ="ProPlusVolume"

-

Product ID ="VisioProVolume"

-

Product ID = "ProjectProVolume"

Language element

Specifies the language supported in the applications

Language ID="en-us"

Version (attribute of Add element)

Optional. Specifies a build to use for the package

-

Defaults to latest advertised build (as defined in v32.CAB at the Office source).

15.1.2.3

SourcePath (attribute of Add element)

Specifies the location in which the applications will be saved to.

Sourcepath = "\\Server\Office2013”

- -   + The above XML configuration file specifies that Office 2013 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2013, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2013 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. For more information, see [Customizable attributes and elements of the XML file](#customizable-attributes-and-elements-of-the-XML-file), later in this topic. After editing the configuration.xml file to specify the desired product, languages, and also the location which the Office 2013 applications will be saved onto, you can save the configuration file, for example, as Customconfig.xml. @@ -319,25 +261,72 @@ The XML file that is included in the Office Deployment Tool specifies the produc -

\\server\Office2013

+

\\\\server\Office2013

is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.

-

Setup.exe

+

setup.exe

is the Office Deployment Tool.

-

/download

+

/download

downloads the Office 2013 applications that you specify in the customConfig.xml file. These bits can be later converted in an Office 2013 App-V package with Volume Licensing.

-

\\server\Office2013\Customconfig.xml

+

\\\\server\Office2013\Customconfig.xml

passes the XML configuration file required to complete the download process, in this example, customconfig.xml. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example \\Server\Office2013.

-   +#### Customizable attributes and elements of the XML file + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input and descriptionExample

Add element:
Specifies the products and languages to include in the package.

N/A

OfficeClientEdition (attribute of Add element):
Specifies the edition of Office 2013 product to use: 32-bit or 64-bit. The operation fails if OfficeClientEdition is not set to a valid value.

OfficeClientEdition="32"

+

OfficeClientEdition="64"

Product element:
Specifies the application. Project 2013 and Visio 2013 must be specified here as an added product to be included in the applications.

Product ID ="O365ProPlusRetail "

+

Product ID ="VisioProRetail"

+

Product ID ="ProjectProRetail"

+

Product ID ="ProPlusVolume"

+

Product ID ="VisioProVolume"

+

Product ID = "ProjectProVolume"

Language element:
Specifies the language supported in the applications.

Language ID="en-us"

Version (attribute of Add element):
Optional. Specifies a build to use for the package. Defaults to latest advertised build (as defined in v32.CAB at the Office source).

15.1.2.3

SourcePath (attribute of Add element):
Specifies the location in which the applications will be saved to.

Sourcepath = "\\Server\Office2013”

+ +   ### Convert the Office applications into an App-V package @@ -389,122 +378,58 @@ After you download the Office 2013 applications through the Office Deployment To -  - -**How to convert the Office applications into an App-V package** +#### How to convert the Office applications into an App-V package 1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterWhat to change the value to

SourcePath

Point to the Office applications downloaded earlier.

ProductID

Specify the type of licensing, as shown in the following examples:

-
    -

  • Subscription Licensing

    - 
    <Configuration>
-       <Add SourcePath= "\\server\Office 2013" OfficeClientEdition="32" >
-        <Product ID="O365ProPlusRetail">
-          <Language ID="en-us" />
-        </Product>
-        <Product ID="VisioProRetail">
-          <Language ID="en-us" />
-        </Product>
-      </Add>  
-    </Configuration>
    -

    In this example, the following changes were made to create a package with Subscription licensing:

    - - - - - - - - - - - - - - - - - - - -

    SourcePath

    is the path, which was changed to point to the Office applications that were downloaded earlier.

    Product ID

    for Office was changed to O365ProPlusRetail.

    Product ID

    for Visio was changed to VisioProRetail.

    -

     

    -

    • -

  • Volume Licensing

    - 
    <Configuration>
-       <Add SourcePath= "\\Server\Office2013" OfficeClientEdition="32" >
-        <Product ID="ProPlusVolume">
-          <Language ID="en-us" />
-        </Product>
-        <Product ID="VisioProVolume">
-          <Language ID="en-us" />
-        </Product>
-      </Add>  
-    </Configuration>
    -

    In this example, the following changes were made to create a package with Volume licensing:

    - - - - - - - - - - - - - - - - - - - -

    SourcePath

    is the path, which was changed to point to the Office applications that were downloaded earlier.

    Product ID

    for Office was changed to ProPlusVolume.

    Product ID

    for Visio was changed to VisioProVolume.

    -

     

    -

    • -

ExcludeApp (optional)

Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.

PACKAGEGUID (optional)

By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.

-

An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users.

-
- Note   -

Even if you use unique package IDs, you can still deploy only one App-V package to a single device.

-
-
-   -
- -   + - **SourcePath**: Point to the Office applications downloaded earlier. + + - **ProductID**: Specify the type of licensing, as shown in the following examples: + - Subscription Licensing: + ``` + + + + + + + + + + + ``` + In this example, the following changes were made to create a package with Subscription licensing: + + **SourcePath** is the path, which was changed to point to the Office applications that were downloaded earlier.
+ **Product ID** for Office was changed to `O365ProPlusRetail`.
+ **Product ID** for Visio was changed to `VisioProRetail`. + + - Volume Licensing + ``` + + + + + + + + + + + ``` + In this example, the following changes were made to create a package with Volume licensing: + + **SourcePath** is the path, which was changed to point to the Office applications that were downloaded earlier.
+ **Product ID** for Office was changed to `ProPlusVolume`.
+ **Product ID** for Visio was changed to `VisioProVolume`. + + - **ExcludeApp** (optional): Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath. + + - **PACKAGEGUID** (optional): By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server. + + An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users. + + **Note**  Even if you use unique package IDs, you can still deploy only one App-V package to a single device. 2. Use the /packager command to convert the Office applications to an Office 2013 App-V package. @@ -523,40 +448,33 @@ After you download the Office 2013 applications through the Office Deployment To -

\\server\Office2013

+

\\\\server\Office2013

is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.

-

Setup.exe

+

setup.exe

is the Office Deployment Tool.

-

/packager

+

/packager

creates the Office 2013 App-V package with Volume Licensing as specified in the customConfig.xml file.

-

\\server\Office2013\Customconfig.xml

+

\\\\server\Office2013\Customconfig.xml

passes the configuration XML file (in this case customConfig) that has been prepared for the packaging stage.

-

\\server\share\Office 2013AppV

+

\\\\server\share\Office2013AppV

specifies the location of the newly created Office App-V package.

-   - After you run the **/packager** command, the following folders appear up in the directory where you specified the package should be saved: - - - **App-V Packages** – contains an Office 2013 App-V package and two deployment configuration files. - - - **WorkingDir** - - **Note**   - To troubleshoot any issues, see the log files in the %temp% directory (default). - -   + **App-V Packages** – contains an Office 2013 App-V package and two deployment configuration files.
+ **WorkingDir** + + **Note**  To troubleshoot any issues, see the log files in the %temp% directory (default). 3. Verify that the Office 2013 App-V package works correctly: @@ -577,7 +495,7 @@ Deploy the App-V package for Office 2013 by using the same methods you use for a - App-V Server -- Stand-alone through PowerShell commands +- Stand-alone through Windows PowerShell commands ### Publishing prerequisites and requirements @@ -594,9 +512,9 @@ Deploy the App-V package for Office 2013 by using the same methods you use for a -

Enable PowerShell scripting on the App-V clients

+

Enable Windows PowerShell scripting on the App-V clients

To publish Office 2013 packages, you must run a script.

-

Package scripts are disabled by default on App-V clients. To enable scripting, run the following PowerShell command:

+

Package scripts are disabled by default on App-V clients. To enable scripting, run the following Windows PowerShell command:

Set-AppvClientConfiguration –EnablePackageScripts 1
@@ -640,20 +558,17 @@ Use the steps in this section to enable Office plug-ins with your Office package **To enable plug-ins for Office App-V packages** -1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a PowerShell cmdlet. +1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a Windows PowerShell cmdlet. 2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2013 is installed on the computer being used to sequence the plug-in. It is recommended you use Office 365 ProPlus(non-virtual) on the sequencing computer when you sequence Office 2013 plug-ins. 3. Create an App-V package that includes the desired plug-ins. -4. Add a Connection Group through App-V server, System Center Configuration Manager, or a PowerShell cmdlet. +4. Add a Connection Group through App-V server, System Center Configuration Manager, or a Windows PowerShell cmdlet. 5. Add the Office 2013 App-V package and the plug-ins package you sequenced to the Connection Group you created. - **Important**   - The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2013 App-V package first, and then add the plug-in App-V package. - -   + **Important**  The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2013 App-V package first, and then add the plug-in App-V package. 6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match the global settings of the published Office 2013 App-V package. @@ -794,7 +709,11 @@ An Office 2013 App-V Package with your chosen licensing will be successfully dep ### Deploying Visio 2013 and Project 2013 with Office -The following table describes the requirements and options for deploying Visio 2013 and Project 2013 with Office. +This section describes the requirements and options for deploying Visio 2013 and Project 2013 with Office. + +- **To package and publish Visio 2013 and Project 2013 with Office**: Include Visio 2013 and Project 2013 in the same package with Office. If you aren’t deploying Office, you can create a package that contains Visio and/or Project. + +- **To deploy Visio 2013 and Project 2013 to specific users**: Use one of the following methods: @@ -803,28 +722,8 @@ The following table describes the requirements and options for deploying Visio 2 - - - - - - - - - - - - - - -
TaskDetails

How do I package and publish Visio 2013 and Project 2013 with Office?

You must include Visio 2013 and Project 2013 in the same package with Office.

-

If you aren’t deploying Office, you can create a package that contains Visio and/or Project.

How can I deploy Visio 2013 and Project 2013 to specific users?

Use one of the following methods:

- ---- - - - - + + @@ -842,17 +741,11 @@ The following table describes the requirements and options for deploying Visio 2

  1. Create a package that contains Office, Visio, and Project.

  2. Deploy the package to all users.

    3. -

  3. Use [AppLocker](https://technet.microsoft.com/en-us/itpro/windows/keep-secure/applocker-overview) to prevent specific users from using Visio and Project.

    4. +

  4. Use [AppLocker](https://technet.microsoft.com/itpro/windows/keep-secure/applocker-overview) to prevent specific users from using Visio and Project.

If you want to......then use this methodGoalMethod
-

 

- -  ## Additional resources diff --git a/windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md b/windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md index 787a0bfe6c..b231f0d973 100644 --- a/windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md +++ b/windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md @@ -1,6 +1,6 @@ --- -title: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell (Windows 10) -description: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell +title: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell (Windows 10) +description: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,11 +9,11 @@ ms.prod: w10 --- -# How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell +# How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 -Use the following PowerShell procedure to convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by Microsoft SQL Server when running SQL scripts. +Use the following Windows PowerShell procedure to convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by Microsoft SQL Server when running SQL scripts. Before attempting this procedure, you should read and understand the information and examples displayed in the following list: @@ -33,336 +33,97 @@ Before attempting this procedure, you should read and understand the information **To convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs)** -1. Copy the following script into a text editor and save it as a PowerShell script file, for example **ConvertToSIDs.ps1**. +1. Copy the following script into a text editor and save it as a Windows PowerShell script file, for example **ConvertToSIDs.ps1**. -2. To open a PowerShell console click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**. +2. To open a Windows PowerShell console, click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**. ``` syntax <# - ``` - - ``` syntax .SYNOPSIS - ``` - - ``` syntax - This PowerShell script will take an array of account names and try to convert each of them to the corresponding SID in standard and hexadecimal formats. - ``` - - ``` syntax + This Windows PowerShell script will take an array of account names and try to convert each of them to the corresponding SID in standard and hexadecimal formats. .DESCRIPTION - ``` - - ``` syntax - This is a PowerShell script that converts any number of Active Directory (AD) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by SQL server when running SQL scripts. - ``` - - ``` syntax + This is a Windows PowerShell script that converts any number of Active Directory (AD) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by SQL server when running SQL scripts. .INPUTS - ``` - - ``` syntax The account(s) to convert to SID format. This can be a single account name or an array of account names. Please see examples below. - ``` - - ``` syntax .OUTPUTS - ``` - - ``` syntax A list of account names with the corresponding SID in standard and hexadecimal formats - ``` - - ``` syntax .EXAMPLE - ``` - - ``` syntax .\ConvertToSID.ps1 DOMAIN\user_account1 DOMAIN\machine_account1$ DOMAIN\user_account2 | Format-List - ``` - - ``` syntax .EXAMPLE - ``` - - ``` syntax $accountsArray = @("DOMAIN\user_account1", "DOMAIN\machine_account1$", "DOMAIN_user_account2") - ``` - - ``` syntax .\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\SIDs.txt -Width 200 - ``` - - ``` syntax -#> - ``` - - ``` syntax - ``` + #> []() []() - - ``` syntax function ConvertSIDToHexFormat - ``` - { - -    param(\[System.Security.Principal.SecurityIdentifier\]$sidToConvert) - - ``` syntax - ``` - - ``` syntax +    param([System.Security.Principal.SecurityIdentifier]$sidToConvert)    $sb = New-Object System.Text.StringBuilder - ``` - - ``` syntax     [int] $binLength = $sidToConvert.BinaryLength - ``` - - ``` syntax     [Byte[]] $byteArray = New-Object Byte[] $binLength - ``` - - ``` syntax    $sidToConvert.GetBinaryForm($byteArray, 0) - ``` - - ``` syntax    foreach($byte in $byteArray) - ``` - - ``` syntax    { - ``` - - ``` syntax    $sb.Append($byte.ToString("X2")) |Out-Null - ``` - - ``` syntax    } - ``` - - ``` syntax    return $sb.ToString() - ``` - - ``` syntax } - ``` - - ``` syntax [string[]]$myArgs = $args - ``` - - ``` syntax if(($myArgs.Length -lt 1) -or ($myArgs[0].CompareTo("/?") -eq 0)) - ``` - { - - ``` syntax [string]::Format("{0}====== Description ======{0}{0}" + - ``` - - ``` syntax "  Converts any number of user or machine account names to string and hexadecimal SIDs.{0}" + - ``` - - ``` syntax                "  Pass the account(s) as space separated command line parameters. (For example 'ConvertToSID.exe DOMAIN\\Account1 DOMAIN\\Account2 ...'){0}" + - ``` - - ``` syntax                "  The output is written to the console in the format 'Account name    SID as string   SID as hexadecimal'{0}" + - ``` - - ``` syntax -                "  And can be written out to a file using standard PowerShell redirection{0}" + - ``` - - ``` syntax +                "  And can be written out to a file using standard Windows PowerShell redirection{0}" +                "  Please specify user accounts in the format 'DOMAIN\username'{0}" + - ``` - - ``` syntax                "  Please specify machine accounts in the format 'DOMAIN\machinename$'{0}" + - ``` - - ``` syntax                "  For more help content, please run 'Get-Help ConvertToSID.ps1'{0}" + - ``` - - ``` syntax                "{0}====== Arguments ======{0}" + - ``` - - ``` syntax                "{0}  /?    Show this help message", [Environment]::NewLine) - ``` - - ``` syntax { - ``` - - ``` syntax else - ``` - - ``` syntax {      #If an array was passed in, try to split it - ``` - - ``` syntax     if($myArgs.Length -eq 1) - ``` - - ``` syntax     { - ``` - - ``` syntax         $myArgs = $myArgs.Split(' ') - ``` - - ``` syntax     } - ``` - - ``` syntax     #Parse the arguments for account names - ``` - - ``` syntax     foreach($accountName in $myArgs) - ``` - - ``` syntax     {    - ``` - - ``` syntax         [string[]] $splitString = $accountName.Split('\')  # We're looking for the format "DOMAIN\Account" so anything that does not match, we reject - ``` - - ``` syntax         if($splitString.Length -ne 2) - ``` - - ``` syntax         { - ``` - - ``` syntax             $message = [string]::Format("{0} is not a valid account name. Expected format 'Domain\username' for user accounts or 'DOMAIN\machinename$' for machine accounts.", $accountName) - ``` - - ``` syntax             Write-Error -Message $message - ``` - - ``` syntax             continue - ``` - - ``` syntax         } - ``` - - ``` syntax -         - ``` - - ``` syntax         #Convert any account names to SIDs - ``` - - ``` syntax         try - ``` - - ``` syntax         { - ``` - - ``` syntax             [System.Security.Principal.NTAccount] $account = New-Object System.Security.Principal.NTAccount($splitString[0], $splitString[1]) - ``` - - ``` syntax             [System.Security.Principal.SecurityIdentifier] $SID = [System.Security.Principal.SecurityIdentifier]($account.Translate([System.Security.Principal.SecurityIdentifier])) - ``` - - ``` syntax         } - ``` - - ``` syntax         catch [System.Security.Principal.IdentityNotMappedException] - ``` - - ``` syntax         { - ``` - - ``` syntax             $message = [string]::Format("Failed to translate account object '{0}' to a SID. Please verify that this is a valid user or machine account.", $account.ToString()) - ``` - - ``` syntax             Write-Error -Message $message - ``` - - ``` syntax             continue - ``` - - ``` syntax         } - ``` - - ``` syntax         #Convert regular SID to binary format used by SQL - ``` - - ``` syntax         $hexSIDString = ConvertSIDToHexFormat $SID - ``` - - ``` syntax -                 $SIDs = New-Object PSObject - ``` - - ``` syntax         $SIDs | Add-Member NoteProperty Account $accountName - ``` - - ``` syntax         $SIDs | Add-Member NoteProperty SID $SID.ToString() - ``` - - ``` syntax         $SIDs | Add-Member NoteProperty Hexadecimal $hexSIDString - ``` - - ``` syntax         Write-Output $SIDs - ``` - - ``` syntax     } - ``` - - ``` syntax } ``` @@ -374,18 +135,10 @@ Before attempting this procedure, you should read and understand the information **.\\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\\SIDs.txt -Width 200”** - **Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +## Have a suggestion for App-V? + +Add or vote on suggestions [here](http://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). ## Related topics - [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md) - -  - -  - - - - - diff --git a/windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index d96ba47b0a..166f2987a4 100644 --- a/windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -1,6 +1,6 @@ --- -title: How to Load the PowerShell Cmdlets and Get Cmdlet Help (Windows 10) -description: How to Load the App-V PowerShell Cmdlets and Get Cmdlet Help +title: How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help (Windows 10) +description: How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,24 +9,24 @@ ms.prod: w10 --- -# How to Load the PowerShell Cmdlets and Get Cmdlet Help +# How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help Applies to: Windows 10, version 1607 What this topic covers: -- [Requirements for using PowerShell cmdlets](#bkmk-reqs-using-posh) +- [Requirements for using Windows PowerShell cmdlets](#bkmk-reqs-using-posh) -- [Loading the PowerShell cmdlets](#bkmk-load-cmdlets) +- [Loading the Windows PowerShell cmdlets](#bkmk-load-cmdlets) -- [Getting help for the PowerShell cmdlets](#bkmk-get-cmdlet-help) +- [Getting help for the Windows PowerShell cmdlets](#bkmk-get-cmdlet-help) -- [Displaying the help for a PowerShell cmdlet](#bkmk-display-help-cmdlet) +- [Displaying the help for a Windows PowerShell cmdlet](#bkmk-display-help-cmdlet) -## Requirements for using PowerShell cmdlets +## Requirements for using Windows PowerShell cmdlets -Review the following requirements for using the App-V PowerShell cmdlets: +Review the following requirements for using the Windows PowerShell cmdlets: @@ -72,42 +72,23 @@ Review the following requirements for using the App-V PowerShell cmdlets:

  • Unpublish-AppvClientPackage

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

    -
    ---- - - - - - - - - - - - - - - - - -
    MethodMore resources

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

      -

    • [How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md#bkmk-admin-only-posh-topic-cg)

      • -

    • [How to Manage App-V Packages Running on a Stand-Alone Computer by Using 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.

    [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md#bkmk-admin-pub-pkg-only-posh)

    -

     

    + +   -## Loading the PowerShell cmdlets +## Loading the Windows PowerShell cmdlets -To load the PowerShell cmdlet modules: +To load the Windows PowerShell cmdlet modules: 1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). @@ -142,30 +123,12 @@ To load the PowerShell cmdlet modules:   -## Getting help for the PowerShell cmdlets - +## Getting help for the Windows PowerShell cmdlets Starting in App-V 5.0 SP3, cmdlet help is available in two formats: - ---- - - - - - - - - - - - - - - - - -
    FormatDescription

    As a downloadable module

    To download the latest help after downloading the cmdlet module:

    -
      -

    1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE).

      2. -

    2. Type one of the following commands to load the cmdlets for the module you want:

      3. -
    +- **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: + @@ -192,33 +155,21 @@ Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
    -

     

    On TechNet as web pages

    See the App-V node under [Microsoft Desktop Optimization Pack Automation with Windows PowerShell](http://technet.microsoft.com/library/dn520245.aspx).

    - -  - -## Displaying the help for a PowerShell cmdlet -To display help for a specific PowerShell cmdlet: + +- **On TechNet as web pages**: See the App-V node under [Microsoft Desktop Optimization Pack Automation with Windows PowerShell](http://technet.microsoft.com/library/dn520245.aspx). + +## 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. Type **Get-Help** <*cmdlet*>, for example, **Get-Help Publish-AppvClientPackage**. -**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). - -  - -  - - - +## Have a suggestion for App-V? +Add or vote on suggestions [here](http://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).