Publish-AppvClientPackage

Publish-AppvClientPackage is accessible with the help of AppVClient module. To configure AppVClient, go through this link.

Synopsis

Publishes the App-V package.

Description

The Publish-AppvClientPackage cmdlet publishes the appropriate extension points of a set of Microsoft Application Virtualization (App-V) packages. Examples of common extension points include shortcuts and FTAs. You can publish the package to the current user or to all users that log into the targeted computer. You can also provide a Dynamic User Configuration file for the package.

Parameters

-DynamicUserConfigurationPath

Specifies the path of a Dynamic User configuration file for the specified App-V package to be added. The cmdlet uses the Dynamic User Configuration file to override the default behavior provided in the user section of the package manifest or the Dynamic Deployment Configuration.

Type:String
Position:2
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-DynamicUserConfigurationType

Specifies what should be done without a defined dynamic user configuration file. The acceptable values for this parameter are:

  • UseDeploymentConfiguration. The package uses the user configuration part of deployment configuration.
  • UseNoConfiguration. Clear any previous configuration and use settings from the manifest.
  • UseExistingConfiguration. Make no changes to the configuration and use the last published configuration.

If you do not specify this parameter, this cmdlet uses UseExistingConfiguration if the package is already published or UseDeploymentConfiguration if it is not.

Use this parameter only during user publishing. It is not valid for global publish.

Type:DynamicUserConfiguration
Accepted values:UseDeploymentConfiguration, UseNoConfiguration, UseExistingConfiguration
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-Global

Indicates that the provided package is published to all users that log into the targeted computer. Otherwise, the packages are only published to the currently running user.

Type:SwitchParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-Name

Specifies the name of the package given when it was sequenced. This value is obtained from the package manifest.

Type:String
Position:0
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-Package

Specifies an App-V package.

Type:AppvClientPackage
Position:0
Default value:None
Accept pipeline input:True (ByValue)
Accept wildcard characters:False

-PackageId

Specifies a GUID that identifies the package. The information can be found in the package manifest or by opening the package in the App-V sequencer. The package ID is shared by all versions of a package.

Type:Guid
Position:0
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-UserSID

Specifies the SID of the intended user. This parameter requires elevated rights to run.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-Version

Specifies the version of an App-V package in a lineage. If you do not specify this parameter, the cmdlet operates on the latest of the package on the computer running the App-V client.

Type:String
Position:1
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-VersionId

Specifies a GUID that differentiates a package version from other versions. If you do not specify this parameter, the cmdlet operates on the latest version of the package.

Type:Guid
Position:1
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Syntax

Publish-AppvClientPackage [-Global] [-UserSID <String>] [[-DynamicUserConfigurationPath] <String>] [-DynamicUserConfigurationType <DynamicUserConfiguration>] [-PackageId] <Guid> [-VersionId] <Guid> [<CommonParameters>]

Publish-AppvClientPackage [-Global] [-UserSID <String>] [[-DynamicUserConfigurationPath] <String>] [-DynamicUserConfigurationType <DynamicUserConfiguration>] [-Package] <AppvClientPackage> [<CommonParameters>]

Publish-AppvClientPackage [-Global] [-UserSID <String>] [[-DynamicUserConfigurationPath] <String>] [-DynamicUserConfigurationType <DynamicUserConfiguration>] [-Name] <String> [[-Version] <String>] [<CommonParameters>]

——————-Example 1——————-
Publish a version of a package to all users
PS C:\> Publish-AppvClientPackage -Name “VApp” -Version 1 -Global -DynamicUserConfiguration “C:\Virtual\policies\VApp.policy”
This command publishes version 1 of the package named VApp to all users on the computer and applies the Dynamic User Configuration policy file.

——————-Example 2——————-
Publish a version of a package to a user
PS C:\> Publish-AppvClientPackage -Name “VApp” -Version 1 -UserPolicy “C:\Virtual\policies\VAppConfiguration.xml”
This command publishes version 1 of the package named “VApp” to the user and applies the Dynamic User Configuration policy file.

——————-Example 3——————-
Publish the latest version of a package to all users
PS C:\> Publish-AppvClientPackage -Name “VApp” -Global
This command publishes the package named VApp to all users on the computer.

You can check the Version, CommandType and Source of this cmdlet by giving below command.

Get-Command Publish-AppvClientPackage

Get-Command Publish-AppvClientPackage powershell script command cmdlet appv client

You can also read about

  • Add-AppvClientPackage
  • Get-AppvClientPackage
  • Mount-AppvClientPackage
  • Remove-AppvClientPackage
  • Repair-AppvClientPackage
  • Set-AppvClientPackage
  • Stop-AppvClientPackage
  • Unpublish-AppvClientPackage

To know more PowerShell cmdlets(Commands) on AppVClient click here

Click on this Link for an Single place where you get all the PowerShell cmdlet sorted based on the modules.

You can also refer other blogs on PowerShell at link

You can also refer other blogs on Microsoft at link

And also if you required any technology you want to learn, let us know below we will publish them in our site http://tossolution.com/

Like our page in Facebook and follow us for New technical information.

References are taken from Microsoft

Leave a Reply

Your email address will not be published. Required fields are marked *