Installing on Network Drivers
I'm absolutely new to the world of packaging and was hoping I could get some help.
I'm packaging an installer for IHSEnergy Accumap V16. I made the package using Installshield Adminstudio V7 Standard and Microsoft Virtual PC. The application will then be pushed SMS.
My package requires at the moment requires that an H:\ be mapped as that is where the destination folder is going to be.
The problem is SMS is an automated service with its own login and does not have drives mapped. I'm wondering if someone tell me if its possible to rebuild or modify my package so that some how SMS will be able to comply with this package
Thanks.
I'm packaging an installer for IHSEnergy Accumap V16. I made the package using Installshield Adminstudio V7 Standard and Microsoft Virtual PC. The application will then be pushed SMS.
My package requires at the moment requires that an H:\ be mapped as that is where the destination folder is going to be.
The problem is SMS is an automated service with its own login and does not have drives mapped. I'm wondering if someone tell me if its possible to rebuild or modify my package so that some how SMS will be able to comply with this package
Thanks.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
jonasm
18 years ago
Hi!
I once heard that you can solve this kinda problems with setting a custom action that changes the value to the network drive before the Sequence that makes the check, and then changes it back when installation is done.
I have never tried this, so I don't know if it's working.
Another thing I would guess work, is to create a custom action that runs a cmd /c subst h: c:\temp\, for example and then deletes it afterwards.
If its a shortcut that points to a network drive, I would have created the shortcut on a "real" machine, and then copy the lnk-file and add it as a file to your project.
/Jonas
I once heard that you can solve this kinda problems with setting a custom action that changes the value to the network drive before the Sequence that makes the check, and then changes it back when installation is done.
I have never tried this, so I don't know if it's working.
Another thing I would guess work, is to create a custom action that runs a cmd /c subst h: c:\temp\, for example and then deletes it afterwards.
If its a shortcut that points to a network drive, I would have created the shortcut on a "real" machine, and then copy the lnk-file and add it as a file to your project.
/Jonas
Posted by:
meping
18 years ago
I realized aftewards it would be possible for me to achieve this. Well assuming windows even read the command, they automated system for deploying the software doesn't have an H:\ or would even know what user %username% would represent as there will always be more then one cashed set of credentials in the c:\documents & settings
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.