Issues with running permission scripts on Hoted desktop via Citrix and when deploying via SCCM

Question

I am running a permissioning VBScript which runs when I do a standalone insallation manually running the power shell commands to add and publish the application.
This only runs vis SCCM when a machine installation is acrried out but not a per user installation. Any ideas?
The same script seems to run sometimes & sometimes does not on a hosted desktop with aps publish via citrix from the appv server. Any ideas?. A coppy of my Deploymentconfig.xml file userscript section that calls the script is below
<UserScripts>
      <StartProcess RunInVirtualEnvironment="true">
        <ApplicationId>[{AppVPackageRoot}]\Adobe Photoshop CS6 (64 Bit)\Photoshop.exe</ApplicationId>
        <Path>[{AppVPackageRoot}]\..\Scripts\AdobeSerialization.exe</Path>
        <Arguments>adobe_prtk --tool=VolumeSerialize --provfile=[{AppVPackageRoot}]\..\Scripts\prov.xml</Arguments>
        <Wait RollbackOnError="false" />
      </StartProcess>
      <StartVirtualEnvironment>
        <Path>WSCRIPT.EXE</Path>
        <Arguments>[{AppVPackageRoot}]\..\Scripts\VFSCACLS.vbs -guid 6d0756af-b755-493b-8cee-4299e8666978 -error -name "Adobe Photoshop CS6"</Arguments>
        <Wait RollbackOnError="false" />
      </StartVirtualEnvironment>
    </UserScripts>
The guys in the build team reckon this is an application issues but I can't see how it can be if the applications runs when manually calling the powersehell commands. Also like I said on the Hosted desktop one minutes the script runs and one minute it does
not.
Can someone help please?

Answer 1

Hello,
If deploying the application to the user, and the configuration file is updated as part of the content and distributed to the DPs, and then downloaded to the client and the client is enabled to run scripts - no I never had that issue.
If I had something which didn't work I would usually verify what is on the Distribution Point?
You can download the SCCM 2012 R2 toolkit to verify what is on the DPs;
http://www.microsoft.com/en-us/download/details.aspx?id=36213
If it is deployed to the client - it means you can read the client log-file from SCCM. See the AppEnforce.log as a potential candidate;
http://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_AppManageLog
If it gets properly parsed by the App-V Client you can check the App-V event logs, see Tim Mangans blog post about enabling further debug-logs;
http://www.tmurgent.com/TMBlog/?p=1247
As I can't see what is happening within your Environment I would redo all the steps and verify what the results were of each step. If one step fails, I would then post what step I had performed up until that point, what the result were of each step and what
was happening within the final step that I would consider a failure.
Nicke Källén | The Knack| Twitter:
@Znackattack