# VirtualVibes

Thamim Karim on a virtual vibe...

# App-V 5.0 Standalone Mode - Adding and Publishing a Package

### App-V 5.0 Standalone Mode - Adding and Publishing a Package

Rate This

Deploying a package in standalone mode in App-V 5.0 is really really simple! I recommend having a standalone client somewhere to everyone I talk to regardless of infrastructure choices because it is the easiest way to quickly test a package before deploying to an environment.

There are two main steps to stand alone package delivery in App-V 5.0; adding and publishing.

Adding a package will register it with the client however will not make the package available to user or computer.

Firstly lets import the appvclient module:

``Import-Module Appvclient``

``Add-AppvClientPackage -Path C:\Packages\iTunes\iTunes.appv``

The –Path parameter simply specifies where your .appv package exists.

An additional parameter we can use when adding a package is –DynamicDeploymentConfiguration whereby we can specify the location of a dynamic configuration file.

# Publishing

Next step is to now publish the package we have just added by running the following command:

``Publish-AppvClientPackage -Name iTunes``

As you will notice the command we issued publishes the package to the user. Now the application is ready to be used!

Another switch we can use when publishing is –DynamicUserConfigurationPath which will allow us to specify a user configuration xml.

If we want to publish a package globally to a machine all we have to do is add a –Global to our command:

``Publish-AppvClientPackage -Name iTunes –Global``

• Great post. Very useful for testing App-V packages.

• This post has been particularly in helping me test sequenced applications.

• Thanks, great to know it has been useful!

• Thamim,

For the life of me, i cannot get this to work. i keep getting a 0c80070057 error, application virtualization service failed to complete requested operation. operation attempted: configure appv package.

Error module: streaming manager. internal error detail: 4c401c0c80070057. the forums at microsoft do not have a fix. these errors hardly come up on search engines. people still have this issue. i have no idea why i cannot get the clients to download and install update publish packages. clients are unsuccessful. ive taken every troubleshooting measure and applied it and still same result.

• Hi,

Can you confirm when you get this error? At add or at publish? Also are you using the -DynamicUserConfigurationPath argument?

Please paste me the commands you are using so I can verify....

• In App-v 4 there were some registry entrires that needed to be modified.  Is this not the case with App-v 5.0?  Also, is standalone mode supported for production use?

• Hi Pat, your right that in App-V 4.x we had the "AllowIndependentFileStreaming" key in registry which had to be set to 1 in order to stream directly from a file location. This is no longer the case in 5.0. Standalone mode in App-V 4.x and 5.0 is fully supported for production use and we have seen some customers really embrace standalone mode beyond just testing packages.

I know some customers using SCCM 2007 are using the methods described above to publish App-V 5.0 packages too.

• Hi Thamim,

I'm also got the same error "0c80070057 " during installation.(standalone mode installation).any solution on this?

• Can you confirm that this is for more than one package or is this issue package specific? Also have you installed the hotfix here: support.microsoft.com/.../2799153

• Hello Thamim,

I too am getting the aforementioned 0C80070057 error.

Commands so far:

PS C:\Windows\system32> Set-ExecutionPolicy Unrestricted -Scope CurrentUser

PS C:\Windows\system32> Import-Module Appvclient

PS C:\Windows\system32> Add-AppvClientPackage -Path '\\domain\software\public\App-V 5.0 Packages\AppTest_1.10.0_x64\AppTest_1.10.0_x64.appv'

Add-AppvClientPackage : Application Virtualization Service failed to complete requested operation.

Operation attempted: Configure AppV Package.

AppV Error Code: 0C80070057.

Error module: Streaming Manager. Internal error detail: 4C401C0C80070057.

Please consult AppV Client Event Log for more details.

At line:1 char:1

+ Add-AppvClientPackage -Path '\\domain\software\public\App-V 5.0 Packages\App ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException

The package was sequenced using App-V 5.0 SP1 using a clean VM running a fully patched instance of Windows 7 Enterprise SP1 (64-bit).

The 'client' machine is also a fully patched instance of Windows 7 Enterprise SP1 (64-bit) and is running the App-V 5.0 SP1 Client.

So far as I can tell hotfix KB2799153 is superseded by SP1.

Any nudges in the right direction would be gratefully received... :)

• PS: I did check the AppV Client Event Log but all it contained was:

<Event xmlns="schemas.microsoft.com/.../event">

- <System>

<Provider Name="Microsoft-AppV-Client" Guid="{E4F68870-5AE8-4E5B-9CE7-CA9ED75B0245}" />

<EventID>1008</EventID>

<Version>1</Version>

<Level>2</Level>

<Opcode>0</Opcode>

<Keywords>0x8000000000000100</Keywords>

<TimeCreated SystemTime="2013-05-08T14:20:06.383335300Z" />

<EventRecordID>2</EventRecordID>

<Correlation ActivityID="{02AB7C68-F800-0005-46C3-7170EF4BCE01}" />

<Computer>win7sp1-x64</Computer>

<Security UserID="<REMOVED>" />

</System>

- <EventData>

<Data Name="Package">{3E2480EF-37C9-4B17-84BC-1B38A8D751EB}</Data>

<Data Name="Version">{47C75130-7167-4297-B60C-C7F2101F5B62}</Data>

<Data Name="Folder">C:\ProgramData\App-V\3E2480EF-37C9-4B17-84BC-1B38A8D751EB\47C75130-7167-4297-B60C-C7F2101F5B62</Data>

<Data Name="ErrorHigh">1279269900</Data>

<Data Name="ErrorLow">2147942487</Data>

</EventData>

</Event>

• Hi Luke,

Is this application specific or are you seeing it across different packages?

• So far I've just tried the one package: a small open-source application called Workrave (http://www.workrave.org)

I chose it as I believed, perhaps erroneously, that it was a nice and simple application that I'd have no issues sequencing.

I will try something even simpler and let you know how I get on.

• Hmm... I've just sequenced a small utility I wrote (an executable and a manifest packaged as a .msi) and that seems to have worked just fine...

PackageId            : 32aa1202-f82c-44ee-8095-aee6e34edc70

VersionId            : 37de4c04-a147-4b16-a1c1-c0bc25a40db2

Name                 : MyIP_1.0_x86

Version              : 0.0.0.1

Path                 : \\domain\software\public\MyIP_1.0_x86\MyIP_1.0_x86.appv

IsPublishedToUser    : False

UserPending          : False

IsPublishedGlobally  : False

GlobalPending        : False

InUse                : False

InUseByCurrentUser   : False

PackageSize          : 548047

HasAssetIntelligence : False

PS C:\Windows\system32> Publish-AppvClientPackage MyIP_1.0_x86

PackageId            : 32aa1202-f82c-44ee-8095-aee6e34edc70

VersionId            : 37de4c04-a147-4b16-a1c1-c0bc25a40db2

Name                 : MyIP_1.0_x86

Version              : 0.0.0.1

Path                 : \\domain\software\public\MyIP_1.0_x86\MyIP_1.0_x86.appv

IsPublishedToUser    : True

UserPending          : False

IsPublishedGlobally  : False

GlobalPending        : False

InUse                : False

InUseByCurrentUser   : False

PackageSize          : 548047

HasAssetIntelligence : True

Maybe the issue is with the application I am trying to package?  I shall have to try a few others and see if I've just randomly picked one that has an issue...

Luke

PS: Thanks for taking the time to reply!  :)

• Now that's interesting, I have just sequenced the same application and delivered it via standalone mode and hit the same exact error! Looks like this issue is specific to some apps, I will investigate further...

Page 1 of 2 (27 items) 12