/build/static/layout/Breadcrumb_cap_w.png

APPV 4.6 converting to APPV 5.0 help

Hi,

I am in the process of converting our virtualised applications from APPV 4.6 to APPV 5.0.

Some of the applications are converting without a problem. However, there are a few others that aren't converting as a result of having some date in the <DEPENDENCY> area of the OSD.

For example

<DEPENDENCY>
  <CLIENTVERSION VERSION="4.6.0.0"/>
  <SCRIPT TIMING="PRE" EVENT="LAUNCH" WAIT="TRUE" PROTECT="TRUE">
   <HREF>cmd.exe /c del /q /f "%HOMEDRIVE%%HOMEPATH%Windows\plclient.ini"</HREF>
  </SCRIPT>
  <SCRIPT EVENT="LAUNCH" TIMING="PRE" PROTECT="FALSE" WAIT="TRUE">
   <HREF>REG.EXE ADD "HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" /v "Y:\Powlog36.054\plclient.exe" /t REG_SZ /d "WINXPSP3" /f</HREF>
  </SCRIPT>
 </DEPENDENCY>

I have a couple of questions. Firstly, can this be converted? I am thinking if I were to remove this information from the OSD that it would probable convert ok. But I would need this information in my APPV 5.0 package. Which leads to my second question. How would I achieve the same result in my APPV 5.0 configuration files? Where do I eidt in my config files?

I was thinking I needed to input my information in the Deployment_config.xml file in the Machine Scripts area, under something like this

<AddPackage>
 
<Path>powershell.exe </Path>
 
<Arguments>-ExecutionPolicy ByPass -File installDriver.ps1 arg1 arg2</Arguments>
 
</AddPackage >
__________________________________________
<PublishPackage>
 
<Path>powershell.exe </Path>
 
<Arguments>.\Scripts\InstallDriver.ps1 </Arguments> OR can be <Arguments>[{AppVPackageRoot}]\..\Scripts\InstallDriver.ps1 </Arguments>
 
<Wait RollbackOnError="true" (Doesn't continue if script fails) Timeout="120"/> A timeout of ‘0’ means “wait indefinitely” for the process to exit
 
</PublishPackage> 

I am new to APPV 5.0 and so I'm not sure where I'm supposed to edit the configuration files to get the same result as when I edited the OSD files in APPV 4.6

Any tips would be greatly appreciated.

Thanks,

Mark

 


0 Comments   [ + ] Show comments

Answers (1)

Posted by: dunnpy 11 years ago
Red Belt
0

I guess it won't convert because there is not OSD scripting in App-V 5.0 - it's in Dynamic Configuration Files - http://www.tmurgent.com/TmBlog/?p=1154

Confirmed by this article:

Limitations:

Package Conversion
The package converter will not convert scripts, packages with dependencies, and/or other certain customizations.  It also only directly converts 4.5 packages and later.  We highly recommend testing App-V 5.0 by sequencing your critical apps first when performing a pilot.  A future post will come out to highlight the limitations of the package converter, and assist you through a straightforward and successful conversion experience.

http://blogs.technet.com/b/appv/archive/2013/07/03/how-to-prepare-for-a-migration-to-app-v-5-0.aspx

 

It's a shame that they couldn't provide backwards compatibilty support in the client for sequences created in 4.6 - like they did for all previous 4.x versions.

Not sure how you'd go about adding your scripts in 5.0 - I've not used it in anger myself - this link may help: http://technet.microsoft.com/en-us/library/jj713466.aspx

 

Dunnpy

 

 

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ