Mapping a drive from an msi package
Has anyone been able to create a custom action that maps a drive if it is not found. I keep getting 1720 errors.
This should be simple but I am stumped
This should be simple but I am stumped
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
aogilmor
17 years ago
Posted by:
SeaWall
17 years ago
i realize it is not a best practice but i need to be able to map a drive if the user is a system user. We install some user files to a p drive in a couple of apps. We need to be able to deploy remotely using the system account which does not have a p drive mapped. I am using an embedded vbs script but it does not appear to like the shell or network object. that is what the 1720 error messageis from.
Posted by:
aogilmor
17 years ago
Before you go any further, you definitely can't install user files on a network drive with an MSI. You can probably script a drive mapping/file copy in a custom action, but not with Windows Installer's InstallFiles action. It only works on local drives.
Secondly, if I were to do something like that I'd probably do a cmd shell rather than a vbscript, something like this,
"%comspec% /c "if not exist p:\*.* net use p: \\server\share ""
Third, you won't be able to map a network drive under system context unless you do a runas and provide a domain username/pw. Not sure of the feasibility of doing this in the MSI. Not real good security either.
Secondly, if I were to do something like that I'd probably do a cmd shell rather than a vbscript, something like this,
"%comspec% /c "if not exist p:\*.* net use p: \\server\share ""
Third, you won't be able to map a network drive under system context unless you do a runas and provide a domain username/pw. Not sure of the feasibility of doing this in the MSI. Not real good security either.

so that the conversation will remain readable.