Scripting appv 5

this is my first attempt to embed a script in appv
the app I sequenced requires that I validate the licence for each computer. I would like to automate that process in the package. there is a validate file that I can run at the command line that will validate the computer. it goes like this "validate.exe
-online -serial 123 123 123 -silent". I copied the validate.exe in the virtual file folder called scripts. I am using the ace tool to configure the deploymentconfig.xml file. has anyone done this type of process or any suggestions on when\ where I should
run the script?
thanks

My suggestion would be to just focus on the manual steps it takes to get the package working, and THEN worry about how to put it into a script that runs automatically.
Right now there are a lot of variables we need to work out.  Try this:
Make sure you are not running any scripts (at add package, publish, startVE, etc).
For testing purposes, log in as an admin, and set the powershell execution policy to unrestricted (info here)
Add and Publish the package
Lauch the app once and make sure it doesn't work
Close down the app
Access the VE (virtual environment; sometimes called bubble) by running the below powershell code:
$name = Read-Host 'Package name'
Start-AppvVirtualProcess -AppvClientObject (Get-AppvClientPackage $name) cmd.exe
The script will ask you for the package name. 
Once the CMD window is open, in the powershell window runGet-AppvClientPackage $name and make sure it says your package is in use.
In this CMD window, run validate.exe from a local drive, for example C:\validate.exe (NOT a network drive...just makes things easier for right now trust me run C:\validate.exe)
In the CMD window, run regedit.exe - make sure it is not already opened.  Do you see the keys you expect to see?
Try to relaunch the app via the published shortcut.
Does the app work at this point?  Did you get any obvious errors running validate.exe?
Once you can get the package working at all, we can work on how to run it automatically, where should it go, etc, but you want to take a step back and work on the manual steps first. 

Similar Messages

  • Office 2013 VL and app-v 5 SP2 on RDS server - package add fails with script error

    We have used the MS Office Depolyment Tool for click-to-run to download the latest Office 365 version, and flatten it into an app-v 5 package - not a problem.
    When we try to add the package to our client machine (Server 2008R2 running the app-v 5 SP2 client software), it fails with an message that a script has failed and not returned a 0 code.  We have not added any scripting to this automatically created
    package, so it seems that the app-v client does not like the "official" package.  Any hints and tips gratefully accepted, thanks
    App-v client has scripting enabled.
    The powershell command line we are using is:
    PS C:\windows\system32> Set-ExecutionPolicy Unrestricted
    PS C:\windows\system32> Add-AppvClientPackage -path file://hostname/app-v/o365-noaccess/ProPlusVolume_en-us_zh-cn_x86.appv -DynamicDeploymentConfiguration \
    \hostname\app-v\O365-NoAccess\ProPlusVolume_en-us_zh-cn_x86_DeploymentConfig.xml
    with a result of:
    Add-AppvClientPackage : Embedded Script process exited with an error code indicating failure (return code other than 0). Please ensure that Embedded
    Script process can complete successfully and exits with 0.
    Operation attempted: Configure AppV Package.
    AppV Error Code: 100000000C.
    Please consult AppV Client Event Log for more details.
    At line:1 char:1
    + Add-AppvClientPackage -path
    file://hostname/app-v/o365-noaccess/ProPlusVolum ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~
        + CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException
        + FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage
    and these are the error messages we see in the debug app-v client logs:
    Script Launcher successfully waited for script with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe" /I /Msi /License /AppV PackageGUID=D24C3BDD-8FAD-44d3-998C-933F8F053682
    PackageRoot="C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
    PRIDName=ProPlusVolume'.
    and...
    Package {d24c3bdd-8fad-44d3-998c-933f8f053682} version {cd9725ce-4503-4932-863b-4fcda3f9551d} failed configuration in folder 'C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D' with error 0x79100E10-0xC.
    and...
    machine script for event AddPackage with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe"'
    exited with failure error code: The extended attributes are inconsistent.. Because Rollback is set to true in the script definition, the current AppV Client operation was rolled back.
    We believe this last error message is the kicker, but can't debug any further.

    Just to validate the problem, I started again.
    I have just downloaded the latest ODT from MS, and then downloaded the latest Office 2013 packaged - volume license.  Then created the app-v package - all went perfectly, no error messages.  Uploaded the package to the app-v 5 server and published
    it.  I have made NO changes to any of the files.
    I have just built a brand new Windows Server 2008R2 Datacentre VM, patched it to the hilt, and installed the RDS role, powershell 3 and appv 5.0 SP2 client for RDS.
    I then use powershell as above:
              scripting unrestricted
              app v client scripting enabled
             app v server added
              global and user update enabled
             add-appvclient package  "url of office package.appv"
                 and received exactly the same error message.  
    It is not complaining that scripting is not allowed, it is complaining that the script is invalid.
    Help!!!!

  • App-v 5 and Office2013 Volume Licence Edition - package fails to install with script error

    We have used the MS Office Depolyment Tool for click-to-run to download the latest Office 365 version, and flatten it into an app-v 5 package - not a problem.
    When we try to add the package to our client machine (running the app-v 5 SP2 client software), it fails with an message that a script has failed and not returned a 0 code.  We have not added any scripting to this automatically created package, so it
    seems that the app-v client does not like the "official" package.  Any hints and tips gratefully accepted, thanks
    The powershell command line we are using is:
    PS C:\windows\system32> Set-ExecutionPolicy Unrestricted
    PS C:\windows\system32> Add-AppvClientPackage -path file://hostname/app-v/o365-noaccess/ProPlusVolume_en-us_zh-cn_x86.appv -DynamicDeploymentConfiguration \
    \hostname\app-v\O365-NoAccess\ProPlusVolume_en-us_zh-cn_x86_DeploymentConfig.xml
    with a result of:
    Add-AppvClientPackage : Embedded Script process exited with an error code indicating failure (return code other than 0). Please ensure that Embedded
    Script process can complete successfully and exits with 0.
    Operation attempted: Configure AppV Package.
    AppV Error Code: 100000000C.
    Please consult AppV Client Event Log for more details.
    At line:1 char:1
    + Add-AppvClientPackage -path
    file://hostname/app-v/o365-noaccess/ProPlusVolum ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~
        + CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException
        + FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage
     and these are the error messages we see in the debug app-v client logs:
     Script Launcher successfully waited for script with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe" /I /Msi /License /AppV PackageGUID=D24C3BDD-8FAD-44d3-998C-933F8F053682
    PackageRoot="C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
    PRIDName=ProPlusVolume'.
    Package {d24c3bdd-8fad-44d3-998c-933f8f053682} version {cd9725ce-4503-4932-863b-4fcda3f9551d} failed configuration in folder 'C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D' with error 0x79100E10-0xC.
    machine script for event AddPackage with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe"' exited with failure error code: The extended attributes are
    inconsistent.. Because Rollback is set to true in the script definition, the current AppV Client operation was rolled back.

    I'd like to reply to this that I also have (or had) the same issue. The "AppV Error Code: 100000000C."
    For me it was a script that I tried to call from a network drive:
        <MachineScripts>
          <AddPackage>
            <Path>powershell.exe</Path>
            <Arguments>K:\someFolder\copy.ps1</Arguments>
            <Wait RollbackOnError="true" Timeout="30"/>
          </AddPackage>
        </MachineScripts>
    I tried using the sharename, I tried using vbs instead of ps, I tried to rename the files it was copying (it was a dll) I tried a different destination (it was Windows\sysWoW64)
    In the end it seems to be the AppV client does not have access to the drive/share, even though 'everyone' had read rights. 
    When I changed the location of my script and file to C:\users\administrator\Desktop\copy.ps1 the appv added just fine.
    I'm looking at what to do, probably give all domain computers access to the share\folder because AppV client seems to use the system account for it's actions (also apparant if you call the var %username% from within the appv!), and because my destination is
    sysWoW64 users are not allowed to write there (so the userConfig.xml is not an option)
    So in short: for me it was a NTFS rights issue, the AppV client is not allowed to go and load the .ps1 that is defined in the deploymentConfig.xml
    Check your
    ProPlusVolume_en-us_zh-cn_x86_DeploymentConfig.xml, it probably calls something that the system account has no access to

  • App-v 5 + Script Deployment type not fully installing.

    Hello, 
    I have 1 applications that has 2 Deployment types,1st one is a Driver and the 2nd is a App-v packages ( the driver is needed for the app-v packages ) 
    Priority  Technology Dependencies  
    1     
    Script
                                 No
    2 App-v 5
                  yes 
    However, the higher priority Script installs fine, however the App-v packages dose not.  
    The app-v packages has a dependency that the Scipt deployment must be installed 1st.
    AppDiscovery.log 
    The package with GUID 752cff88-0ecc-4bb4-8e78-616acc09e61e is not installed on this machine yet
    +++ App-V 5.X package cymap 2014 not installed. [AppDT ID : ScopeId_16370CC1-E6FE-4F00-B29F-CE1780416708/DeploymentType_9d03d051-5ca1-4618-9e5f-47d62a248eb8, Revision: 2, AppV Package GUID: 752cff88-0ecc-4bb4-8e78-616acc09e61e, AppV Version GUID:
    c15d888b-a61a-4e6c-9203-68ee8bf69aed]
    I have had similar issues using application model having more then 1 deployment types so i try to avowed them, but this realy should just work.
    Any help welcome.
    Cheers  

    Like Torsten says, you can't install two DT's from the same Application.
    The first DT with all requirements meet, will be installed.
    You need to create 2 Applications, otherwise it wont Work.
    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
    www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
    @ronnipedersen

  • Running Permission Scripts for App-V packages in VDI environment

    Hi
    We use App-V 5.0 SP1 in VDI environment.
    We have a major problem with packages' permissions
    Our users don't have administrative privileges on their machines.
    As the option for "Security Descriptors" is discontinued, the only way to give permissions to a folder in a package is to use the VFSCACLS.vbs as a startup script of a package.
    This way the first time users launch an application they're prompt to reopen it, and the second time they can use the application with the needed permissions.
    The problem:
    The script saves those permission changes under LOCALAPPDATA\AppV...
    Therefore, everytime the users logoff the folder is deleted (VDI...) and again, they must run the script for the first  again to get the permissions back after logon!
    We cannot roam the LOCALAPPDATA\AppV folder as its size can be dozens of GBs...
    Folder permissions with group policy is also not a solution, as the folder name changes everytime we upgrade a package and it's impossible to follow with hundreds of packages.
    So it's either we're missing something critical in the architecture with VDI environment or there's a normal solution for these situations.
    Would love to get some help
    Thanks
    Tamir Levy

    Hi Nicke
    that's what I did! the problem is that I find my self over and over again want to sequence packages in App-V 5.0 and forced to sequence it in App-V 4.6.
    I really hope that it wasn't App-V team's goal. announcing App-V 5.0 and tell us it doesn't support many things so we will still need App-V 4.6 forever.
    I have to maintain 2 different App-V environments with 4 different servers , 4 different sequencers and 2 clients on each computer. it doesn't make any sense for me to forced to stay with both of the versions forever.
    correct me if I'm wrong but App-V 4.6 is a legacy application. the new versions cover only support on newer operating systems and nothing more. I won't be surprised if in the next version of MDOP won't come with App-V 4.6 anymore and Microsoft will announced
    it's unsupported very soon.
    Every time I open a ticket with MS Support the best thing I get is "It's a known issue, we can't tell when it will be fixed"
    can you help me more ? move it forward to other people from the inside? at least agree with me that something is not as expected in App-V 5.0... :(
    I love the technology, I believe in it, I'm kinda depend on it and I only want it to be better
    Tamir Levy

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

    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?

    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

  • App-V 4.6 Powershell script deleteting all shortcuts

    Hello,
    °not sure if this is more of a powershell issue or app-v issue, feel free to move my topic to the right forum°
    Now we have a nice script in production that is supposed to delete all obsolote App-v shortcuts, once  a pc starts.
    this does very well based on the following function: function Remove-InvalidAppVFTAS()
    and  $rlist = get-childitem -path $FTARegRoot |?{($_.PSChildName  -like ".*") -and ($_.property -contains "SoftgridSource")}
    and so on....
    BUT if the app-v client is not reachable for example it will still consider as the items are obsolete and delete everything.
    Now I would like to achive , that shortcuts are only deleted if the app-v apps are obsolete.
    according to the following:
     if ($activeapps -notcontains($appv))
                    $lnk.delete()
                    if(test-path $lnk.fullname)
    the script will delete the shortcuts if the paramater is on inactive, but ofcourse if the app-v client is unreachable, the app is set to inactive, then in an unecessary manner our shortcuts are deleted.

    Sorry, I misread this! By the way, does this happen often and what is the cause of the client-server connection going down?
    You could have your script also read from the App-V logs for any instances of an error. For more info on the logs, take a look here:
    http://blogs.technet.com/b/gladiatormsft/archive/2013/11/13/app-v-on-operational-troubleshooting-of-the-v5-client.aspx
    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
    rorymon.com Twitter: @Rorymon

  • App-V 5 and scripts in user context

    Hello,
    I'm trying to figure out how scripting works in App-V 5, and I'm having an issue with it.
    I've read
    Scripting and Embedded Scripting for AppV 5.0 (Dynamic Deployment and User Configuration Scripting) and
    About Scripts in App-V 5.0, but still have a question about scripting in version 5.
    Via the UserConfig.xml I start a StartVirtualEnvironment and a StartProcess, just to test the behavior:  
    <UserScripts> 
    <StartVirtualEnvironment  RunInVirtualEnvironment="false">
      <Path>cmd.exe</Path>
      <Arguments>/c "\\servername\content$\batchtest_StartVirtualEnvironment.cmd"</Arguments>
      <Wait RollbackOnError="false"/>
    </StartVirtualEnvironment> <StartProcess RunInVirtualEnvironment="false">
    <Path>cmd.exe</Path>
    <Arguments>/c "\\servername\content$\batchtest_StartProcess.cmd"</Arguments>
    <Wait RollbackOnError="false"/>
    <ApplicationId>[{AppVPackageRoot}]\7zFM.exe</ApplicationId>
    </StartProcess>
    </UserScripts>
    This is one of the batch scripts that is triggered using the UserConfig.xml-file:
    REM batchtest_StartVirtualEnvironment
    echo username: %username% > c:\temp\AppV5ScriptTest.txt
    echo hostname: %computername% >> c:\temp\AppV5ScriptTest.txt
    echo userdomain: %userdomain% >> c:\temp\AppV5ScriptTest.txt
    echo ALLUSERSPROFILE: %ALLUSERSPROFILE% >> c:\temp\AppV5ScriptTest.txt
    echo USERPROFILE: %USERPROFILE% >> c:\temp\AppV5ScriptTest.txt
    echo APPDATA: %APPDATA% >> c:\temp\AppV5ScriptTest.txt
    echo LOCALAPPDATA: %LOCALAPPDATA% >> c:\temp\AppV5ScriptTest.txt
    After starting the app on the client, this is the output of both batch scripts:
    username: MachineName$
    hostname: MachineName
    userdomain: DomainName
    ALLUSERSPROFILE: C:\ProgramData
    USERPROFILE: C:\Windows\system32\config\systemprofile
    APPDATA: C:\Windows\system32\config\systemprofile\AppData\Roaming
    LOCALAPPDATA: C:\Windows\system32\config\systemprofile\AppData\Local
    Only %userdomain% and %hostname% are correct. It seams that all other things are running in SYSTEM context? For example %AppData% isn't pointing to C:\USERS\ ..
    I'm I doing something wrong here?
    (I'm on Windows 7 x64 SP1 as client with App-V 5.0 RTM, sequencing machine is a Win7x86 SP1) 

    We experience the following:
    When creating a App-V 5.0 package for a network application we receive the following error
    Environment:
    Windows 7 x86 Sequencer
    Sequencer: 5.0.285.0
    Sequencing the application
    Start the sequencer
    Give the package a name
    Set the PVAD to C:\Users\Administrator\Desktop
    Create a shortcut on the desktop to
    \\server\share\application.exe
    Set 3 HKLM keys in the registery under HKLM/Software/Vendor/Application
    Save the package.
    Results
    When starting the package we receive the following error message:
    Toepassingspop-up: Ats.exe - Toepassingsfout : Kan de toepassing niet correct starten (0xc0000142). Klik op OK om de toepassing te sluiten.
    Also the following notification is presented in the App-V/Admin event logs:
    The virtual application '\\FQDN\SHARE$\PROGRAM.exe' could not be started because the App-V Subsystem 'Virtual Shell' could not be initialized. {error: 0x8DC02325-0x5}
    Seems like the same issue...

  • App-V'ed program knows it's running in c:\programdata\microsoft\appv\guid

    I have a package for some software called RelayCare.  It sequences fine, and the package runs, 99% of the functionality works.
    One part does not work - there's a .rpt viewer built in, might be Crystal, not 100% sure.  The rpt files regularly get updated so I do not want them in the package.
    The primary application virtual directory is c:\program files (x86)\relaycare
    In relaycare\cecclient\reports, those .rpt files sit.
    So, if I delete the folder when packaging, the report folder gets excluded.  
    I can copy the files to the local PC running the published appv package, to c:\program files(x86)\relaycare\cecclient\reports
    The app, however, does not see the files.  When I try to run a report, it says xxx.rpt file not found in c:\programdata\microsoft\appv\guid\root\relaycare\cecclient\reports 
    How the heck does it know where it's running? 
    If I run cmd /appvve:guid_vid, I can see that the files are merging properly in 
    c:\program files(x86)\relaycare\cecclient\reports - the local folder is taking precedence as desired
    Long story short, how does this app know about the c:\programdata folder, is that avoidable, so it looks in the right place for the reports?  
    If it's not avoidable, can the appv programdata package folder have files dropped in there?  If I try - I get permission denied even as an administrator.  
    The .rpt files really can't go into the package, they change too much.
    Figured I'd try to ask here, I'm out of ideas...
    Thanks!

    Is there a setting that you know of to change the report directory?  What do you do in a traditional install?  Do you ACL the report folder for the user and they can drop in new reports whenever they want?  Do you not have to update the package
    now when the reports update?
    Even though App-V sets up a virtual environment, that doesn't mean an exe can't know where it is.  I believe the term is called  reflection, but if the exe basically asks where it is, it gets the literal path, ie C:\Programdata\....
    What could be happening is the exe is always assuming that a subfolder (a relative path) to itself has the reports.
    If you can package the software to VFS that may solve the issue... I don't know off the top of my head if App-V redirects calls made to the non-virtualized path (C:\Programdata\....\root\VFS\PROGRAMFILES86 as a bad example) and treats them like calls made
    to the VE.   My gut is no, that if the app tries to write that way it will get an access denied it has to go to the virtualized path of C:\Program Files (x86)\....
    Also about including the reports in the package... how are users expected to update the report files?  If the user typically (for example) goes into Windows explorer, and drags new report files into the dir that won't be user friendly anymore.
    However if the software itself has an import where the user selects new files and then the program puts them where it wants, that may work.
    Obviously this is all theoretically speaking, my main point is you have to consider the user interaction that is appropriate before you can determine what you do next.  A good place to start that conversation is what do they do normally, outside of
    App-V.  People have had success create a junction point inside the VE to redirect reads/writes to a different location.  I haven't done so myself but that may also help you out.
    Worst come to worst, you might be able to drop the exe onto the real file system, and treat it like an outside application.  We had to do this for an app with a similar problem...it wanted to write to a subfolder and used its own current directory as the
    starting point, and you can't write to C:\Programdata\...
    We used the Add package scripting to drop the exe 'outside', and because the exe is now outside, App-V will create the shortcut like app.exe /appvve:guid_vid, and if the exe looks at its own location it will see where you drop it to, not the virtualised
    path.
    EDIT: Just thought of this...I wonder if you could use a shim to trick the app into believing it is launching from C:\Program Files instead of the C:\Programdata location.

  • Adding script into DynamicConfig.xml in App-V 5.0

    Hi,
    In App-V 4.6, to add a script, we’d open the relevant .osd file & add it under the dependency tags.
    In case of App-V 5.0, this is an example of CS6-Flash_DeploymentConfig.xml
    Where would I insert this script & how?
    <SCRIPT TIMING=”PRE” EVENT=”LAUNCH” WAIT=”TRUE” PROTECT=”TRUE”>
    <SCRIPTBODY>
    C:\CS6-Flash\CS6-Flash-Serial\AdobeSerialization.exe adobe_prtk ––tool=VolumeSerialize ––provfile=C:\CS6-Flash\CS6-Flash-Serial\prov.xml
    < /SCRIPTBODY>
    < /SCRIPT>

    http://www.tmurgent.com/TmBlog/?p=1154 and
    http://blogs.technet.com/b/appv/archive/2012/12/10/scripting-and-embedded-scripting-for-appv-5-0-dynamic-deployment-and-user-configuration-scripting.aspx 
    cover this quite good
    Falko
    Twitter
    @kirk_tn   |  Blog
    kirxblog   |  Web
    kirx.org

  • AppV client default paths

    I want to know if i can publish a package that was created in the sequencer to another path then the default path on the APPV client machine defined in the registry PackageInstallationRoot.
    which by default goes to the hidden folder "c:\ProgramData\APPV\".
    I know I can change the path in the registry, but I want to know if there is a way I can create a package that when I add and publish on
    the client machine it deploys to a path that I define instead of the default path defined in the client registry.

    You mean it can't find itself because the file DIR has the hidden attribute?  Haven't seen an app do that before.
    I have bad news this is about the best I can come up with.  Let me know if I'm not clear on anything.
    Is the app writing its location to a registry key or ini file that you can manipulate?
    What would happen if you put C:\Programdata into your package?  Wonder if it would read the attributes differently. 
    If the exe is evaluating its own location to determine where it is, you may be short on options....this is the best I can come up with:
    Copy the exe out of the bubble into the real file system, essentially treating it the same way you would with a locally installed IE.  The App-V shortcut will turn into C:\Program Files\12345\abcde.exe /appvve:pGUID_vGUID (for example).  We had to
    do this with an application and it did work pretty well.  We used the add scripting event to create the needed dir structure, copy the exe, and permission if needed. 
    Outside of that maybe you could get a shim to trick the app into believing it is in the 'traditionally' installed path, ie  C:\Program Files\12345\?

  • What prevents a package from pre-loading into the AppV cache (using SCCM)

    This could be an App-V issue or an SCCM issue, not entirely sure...
    When SCCM deploys AppV apps to clients we always set to download and run locally.  With this set SCCM will always cache the entire package in the AppV cache immediately so it can be used offline.
    I've got a package where this just isn't working.  It is set to download and run locally but after it is deployed the PercentLoaded value shows 0.  If a user then runs it you are looking at a delay whilst it then unpacks from the SCCM cache to
    the AppV cache.  This package includes a script which executes when published so could this be the culprit?

    Mmm the mount seems to be failing...
    AppVManageClient5X::MountAppVPackage() failed for package [530ecc6a-26db-487f-9ab8-5bd3c427a9d1]. (0x87d0128f)
    Looking in the App-V Event viewer we have events like:
    Microsoft AppV Streaming Manager LoadAll failed with status The system cannot find the file specified., Package Version {b83b67b9-56a8-4862-aaa0-16d27c2036ab}
    and
    Could not read the streaming information from file \ProgramData\App-V\0CD3D585-5851-4242-B9E5-A8F49ABC04B5\b83b67b9-56a8-4862-aaa0-16d27c2036ab\Root\commons-logging-1.0.4.jar. Failure status 0xc0000275. - VERBOSE MESSAGE NOT AN ERROR
    0xc0000275 means nothing to me so a quick Google shows The file or directory does not have a reparse
    point.
    Perhaps an issue with the package then?  It is still residing inside the SCCM cache and if a user runs the software it starts mounting more of it...

  • App-V 5.0 SP3 SQL Script modifications (KB3031340) Required for both Management and Reporting Databases?

    Can anyone confirm if I need to modify the InsertVersionInfo.sql and Permisioins.sql scripts for both the APP-V Management and Reporting databases?  KB3031340 only references the Management Database, but I suspect it is required for both.
    Thank You!

    It should only apply to Management Database. There weren't any changes to the Reporting DB AFAIK.
    Steve Thomas, Senior Consultant, Microsoft
    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat
    http://blogs.technet.com/gladiatormsft/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/
    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

  • PVS 7.x, Citrix UPM, XA 6.5, & AppV 5.0 SP2 HF4 for Stateless Shared Desktop

    Note:  I have read and followed this tech net recommendation closely as the basis for my technical design (I have also read many other articles, Citrix recommendations for UPM, Microsoft Performance Guide, etc):
    http://social.technet.microsoft.com/wiki/contents/articles/25318.app-v-a-configuration-template-for-deploying-to-stateless-rds-clients-on-citrix-published-desktops-with-citrix-upm-for-profile-management.aspx
    I have a few questions and I'd be interested in community thought:
    1.  In this design they are placing the PackageInstallationRoot on a persistent locally attached drive, which they then have to spend time wiping at every startup.  This can be incredibly time consuming to do all the icalcs commands if the AppV
    Package Cache has a lot of apps (~10 minutes for my environment with 6 apps).  Is there a flaw with placing this within Non-Persistent space instead (i.e. RAM Write-Cache with Disk backing in PVS 7.6).  Rationale:
    A) It is a much quicker wipe than the linked approach.  PackageInstallationRoot gets completely wiped instantly upon PVS Target reboot.
    B) I could place this on my persistent volume and do the lengthy cleanup on startup, but this is the same SAN-attached persistent volume that PVS Ram Cache with Disk Overflow uses so I am not sure I see the benefit.  Perhaps there is a bit more overhead
    to run to PackageInstallationRoot through PVS WriteCache overhead instead of direct filesystem call to SAN Volume, but that is the only thing I can think of.
    2.  Direction talks about the exclusion to AppData\Microsoft\AppV, but for environments that use Folder Redirection for AppData I don't believe this is possible?  I'm guessing they are using UPM for AppData and LocalAppData.  I have implemented
    all other exclusions (LocalAppData, HKCU Registry, etc) except for AppData and don't see any problems.
    3.  Author states apps are available for users immediately, but there has to be overhead for the very first user for each app after every reboot in order to re-populate PackageInstallationRoot and Re-Publish the app.  The only way I can think to
    reduce this burden a bit would be to either A) Cache (Add-AppV) application into the master image (not ideal for us), or B) have a script that caches (Add-AppV) application whenever a PVS Target boots.  This would just leave the user having to publish,
    which appears to be quicker based on my testing.
    Thanks

    I would not recommend this and keep the package cache and the client on the same non-persistent drive and enable the Shared Content Store. If you separate the cache and the App-V client they could get out of sync and strange behaviour can occur. 
    You can use a temporary local profile with Citrix UPM or UE-V and specify what to roam/save.
    You can use the Shared Content Store so packages will stream over the network. When the user logs on there is a publishing phase where shortcuts etc are created for the user, this will take some time.
    Are you using the App-V full infrastructure?
    Are you using a boot disk, partition or PXE in combination with PVS?

  • Files within appv 5 have new timestamp

    Hello,
    When seqeuncing with appv 5.2 the following occurs.
    The original timestamp of files are being changed to timestamp of the day seqeuncing.
    we do not want this because the software on the server then is telling us to update because of the difference in
    files. (timestamp)
    How to resolve?

    By the way, what kind of files are you updating? App-V 5 prevents users from writing to executable files (see http://blogs.technet.com/b/gladiatormsft/archive/2013/10/24/app-v-5-on-that-issue-with-firefox-where-you-cannot-save-preferences.aspx), so
    if that is going to be a problem, no point spending effort trying to solve the first one!
    It may be possible to write a script to save all the timestamps to a text file after you've finished sequencing, then a reverse script to apply those timestamps after publishing. You could run the script outside the bubble to modify the actual files under
    ProgramData, or run the script in the bubble which would result in placing modified copies of the file under the user's profile. The latter would take up extra disk space by cloning every file in the package, but this might not be a problem if most of those
    files are going to be updated anyway.
    Dan Gough - packageology.com
    Twitter (@packageologist) LinkedIn

Maybe you are looking for