locked
Drive Mapping issue using OSD RRS feed

  • Question

  • I have an application that is custom made to fit our needs.  This application is normally run by calling a batch file that maps the drive to the data directory, then launches the application.  the application is set to look in the particular mapped drive (S:, T:, or whatever the letter is for the particular environment).  The application sequences just fine. The trouble I am having is that once sequenced it enters a value in the <WORKINGDIR> field of \\server path\ and the application itself is expecting the drive letter (I: in this case).  How do i get the app-v package to see the I: drive that gets mapped as the I: drive and not the exact path?

    After launching the application I end up with error "The directory name is invalid" and error code 4625DD4-1F701639-0000010B.


    My network drive is not mapped via pre launch. If I manually map the drive app works fine.

    Here is my OSD.

    <?xml version="1.0" standalone="no"?>
    <SOFTPKG GUID="398F67C8-7063-4FE6-9BF4-55601E235055" NAME="Integra" VERSION="1.0">
    <IMPLEMENTATION>
    <CODEBASE HREF="RTSP://AppV:554/Integra_07.08.04.09_VFS/Integra_07.08.04.09_VFS.sft" GUID="3201C57A-0304-4F88-A15E-80823502DBD1" PARAMETERS="integra.exe" FILENAME="I:\Lib\QSSLOAD.EXE" SYSGUARDFILE="Integra_07.08.04.09_VFS\osguard.cp" SIZE="62094880"/>
    <VIRTUALENV TERMINATECHILDREN="FALSE">
    <POLICIES>
    <LOCAL_INTERACTION_ALLOWED>TRUE</LOCAL_INTERACTION_ALLOWED>
    </POLICIES>
    <ENVLIST>
    <ENVIRONMENT VARIABLE="PATH">%CSIDL_PROGRAM_FILES%\Microsoft Application Virtualization Sequencer\;%PATH%;I:\Lib\bin;</ENVIRONMENT>
    <ENVIRONMENT VARIABLE="INCLUDE">I:\LIB\BIN\INCLUDE</ENVIRONMENT>
    </ENVLIST>
    </VIRTUALENV>
    <WORKINGDIR>I:\LIB\<WORKINGDIR/>
    <VM VALUE="Win32">
    <SUBSYSTEM VALUE="windows"/>
    </VM>
    </IMPLEMENTATION>
    <DEPENDENCY>
    <CLIENTVERSION VERSION="4.6.0.0"/>
    <SCRIPT TIMING="PRE" EVENT="LAUNCH" WAIT="TRUE" PROTECT="FALSE">
    <SCRIPTBODY> @echo on \n
    net use I: /delete /y \n
    net use I: \\\\Server\\Integra$ \n 
    </SCRIPTBODY>
    </SCRIPT>
    <DEPENDENCY/>
    <PACKAGE NAME="Integra_07.08.04.09_VFS"/>
    <ABSTRACT/>
    <MGMT_SHORTCUTLIST>
    <SHORTCUT LOCATION="%CSIDL_DESKTOPDIRECTORY%" FILENAME="Integra.lnk" OVERRIDDEN="FALSE" DISPLAY="Integra" ICON="%SFT_MIME_SOURCE%/Integra_07.08.04.09_VFS Icons/Integra.ico"/>
    <SHORTCUT LOCATION="%CSIDL_PROGRAMS%" FILENAME="Integra.lnk" OVERRIDDEN="FALSE" DISPLAY="Integra" ICON="%SFT_MIME_SOURCE%/Integra_07.08.04.09_VFS Icons/Integra.ico"/>
    </MGMT_SHORTCUTLIST>
    <MGMT_FILEASSOCIATIONS>
    <PROGIDLIST/>
    <FILEEXTENSIONLIST/>
    </MGMT_FILEASSOCIATIONS>
    </SOFTPKG>


    Friday, November 22, 2013 5:28 PM

Answers

  • After you modify the cache, it only take effect for the cached OSD file. If you change the OSD files outside of the MSI, the changes wont occur when you redeploy via the MSI as the OSD files are embedded inside the MSI file. You have to actually open it up in the sequencer and edit the osd using the sequencer editor then resave the file.


    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.”

    • Proposed as answer by znack Monday, November 25, 2013 12:12 PM
    • Marked as answer by David WoltersModerator Friday, January 10, 2014 2:39 PM
    Saturday, November 23, 2013 6:48 AM

All replies

  • Hello,

    If you add a line with the cmd "pause" at the end of the script - does the script tell you why it didn't map the drive?


    Nicke Källén | The Knack| Twitter: @Znackattack

    Friday, November 22, 2013 5:41 PM
  • Hello,

    If you add a line with the cmd "pause" at the end of the script - does the script tell you why it didn't map the drive?


    Nicke, the application closes before the drives are mapped. Can't even see why it is not mapping the drive?


    Friday, November 22, 2013 5:49 PM
  • Hello,

    If executing a script, the script window will flash by (how long depends on the execution time of your script).
    If adding a pause, the script will pause and thereby halt the window.

    If it is not pausing, it is not executing.

    Have you ensured that the client has received the latest update versionen of the OSD-file?

    You can right-click the application in the App-V Client Mgt Console and select Properties to verify the path of the OSD-file and check the contents of the file.


    Nicke Källén | The Knack| Twitter: @Znackattack


    • Edited by znack Friday, November 22, 2013 5:58 PM spell-check
    Friday, November 22, 2013 5:56 PM
  • Nicke,

               this is the first time am encountering this issue. To my surprise, I happened to check the OSD cache location ( C:\program Files\Microsoft Application Virtualization\Global\Softgrid client\OSD Cache) and I don't have the drive mapping there, in the script.

    Any suggestion. I edited the OSD manually before running the .msi.

    All the time I have been streaming .osd's and the changes were affected based on .osd.

     This is the first time I took of installing the App-V app via .msi

    Suggestions please. 


    Friday, November 22, 2013 8:10 PM
  • After you modify the cache, it only take effect for the cached OSD file. If you change the OSD files outside of the MSI, the changes wont occur when you redeploy via the MSI as the OSD files are embedded inside the MSI file. You have to actually open it up in the sequencer and edit the osd using the sequencer editor then resave the file.


    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.”

    • Proposed as answer by znack Monday, November 25, 2013 12:12 PM
    • Marked as answer by David WoltersModerator Friday, January 10, 2014 2:39 PM
    Saturday, November 23, 2013 6:48 AM
  • If you add a pause in your OSD script, like Nicke suggested. What error message do you see in the DOS box?
    Saturday, November 23, 2013 9:07 AM
  • What happens if you map the drive outside your package (so remove it from the scriptbody, and set the drive-mapping first).
    What happens of you change

    <SCRIPT TIMING="PRE" EVENT="LAUNCH" WAIT="TRUE" PROTECT="FALSE">

    to

    <SCRIPT TIMING="STREAM" EVENT="LAUNCH" WAIT="TRUE" PROTECT="FALSE">
    Monday, November 25, 2013 9:13 AM