/build/static/layout/Breadcrumb_cap_w.png

mapped drive to local

i am looking for a way to address my problem. i have a captured msi that is mapped to a drive..if the drive is not mapped to the user pc it will display as an error and will not launch the msi. "we dont want the user to have access to the drive"!!! is there a way vbscript  or any custom action using installshield  to copy these files locally etc.....please be clear in answer also

GOAL: Copy files from mapped drive to local drive so msi can install w/o problems


0 Comments   [ + ] Show comments

Answers (3)

Posted by: samzeeco 10 years ago
10th Degree Black Belt
1

For vbscript, try:

Set FSO =CreateObject("scripting.FileSystemObject")
FSO.CopyFolder "\\<Server>\<folder>\", "C:\<Location files need to go>" ,True

I would use batch myself and just use xcopy to copy from the network location to the end users computer. Or even more than that, just have the install batch file copy the files from the install zip file to the location on the computer if it's not necessary to have them come straight from the server.


Comments:
  • My company does away with batch files....will be using install shield for custom action - ninjadeen 10 years ago
    • How do they feel about executables? You can convert a .bat file to a an executable. If you can create .bat files at all that is.

      Create a bat file called copy.bat with the xcopy line (test it to make sure it works). Once you have the bat file created open the start menu and type iexpress.exe and hit enter.
      b. At the Welcome page click Next
      c. At the package purpose screen click Next
      d. Title the package copy and click Next
      e. Click Next on confirmation prompt (left on No Prompt)
      f. Click Next on License agreement (left on Do No Display a license).
      g. Click Add and navigate to the copy.bat you created and click Next
      h. At Install Program to launch type cmd /c netmap.bat in Install Program and click Next
      i. Click Hidden on the Show Window page and click Next
      j. Click Next on Finished message (left on No Message)
      k. Browse to the location where you have the working files located and save the name netmap check Hide File extracting… and Store Files using Long… click Yes on the wizard’s warning and click Next.
      l. Click No Restart and click Next.
      m. Click Don’t Save on the Save SED page and click Next
      n. Click Next on create package.
      o. Click Finish and test copy.exe - samzeeco 10 years ago
  • Great thanks samzeeco ... I will use this as my last resort.. Because we use sccm2012 in our environment vbs will be best bet - ninjadeen 10 years ago
Posted by: anonymous_9363 10 years ago
Red Belt
1

>if the drive is not mapped to the user pc it will display as an error and will not launch the msi.
If it's captured, then someone *must* have added this "functionality" so it would be the work of moments to remove/bypass it!

>"we dont want the user to have access to the drive"!!!
One can only laugh heartily at the utter nonsense that this represents. However, as I'm always saying, sometimes one just cannot convince clients that they realy have no clue and are forced to comply so...in your script, why not just map the drive, run the MSI, then unmap it? And *please* don't ask for script samples! If you can't use Google, you may as well give up now.


Comments:
Posted by: mduiker 10 years ago
Orange Senior Belt
0

If we're talking about dirt, why not copying the required files over to a local drive, subst that folder to the required drive, run the msi and subst /d afterwards?


If that succeeds, google a bit and read about the 'wisesourcepath' table and use '.\' at the beginning of every file location.

 
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