Have to deploy my msi to a networkdrive
I need to repackage an application which get installed to a networkdrive.
I try to make a capture including the networkdrive to watch. After the capture i can see it has included the networkpath in the summary box
but then deploy the package on a other computer it install this application locally and not on the network drive
Any idea why?
I try to make a capture including the networkdrive to watch. After the capture i can see it has included the networkpath in the summary box
but then deploy the package on a other computer it install this application locally and not on the network drive
Any idea why?
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Firstly, to clarify, this is nothing to do with Wise per se, but the Windows Installer engine.
Second, when I refer to "server" (in quotes), I don't mean a machine running a server OS, simply a machine with a share on it.
Lastly, take a look here http://msdn.microsoft.com/en-us/library/aa371372(VS.85).aspx
Second, when I refer to "server" (in quotes), I don't mean a machine running a server OS, simply a machine with a share on it.
Lastly, take a look here http://msdn.microsoft.com/en-us/library/aa371372(VS.85).aspx
Posted by:
anonymous_9363
15 years ago
Posted by:
Bankeralle
15 years ago
install to the drive, I imagine that you would have similar
ORIGINAL: VBScab
If you have sufficient privileges to install to the drive, I imagine that you would have similar privileges to install the package "locally" to the "server" in question, so why not simply RDP to it and run the MSI? Or use PSExec?
oYes i have sufficent privilges to install to the drive, but somehow it only gets installed locally?
If i look under installation expert-file it says under my computer only Apps. But it should be the networkdrive:\Apps
so why not simply RDP to it and run the MSI? Or use PSExec? - please explain a bit more as i dont understand what you are talking about
Posted by:
anonymous_9363
15 years ago
RDP - Remote Desktop Protocol (as Googling for 'RDP' would have shown you...)
This allows you to connect and log in to the remote machine, as if it were in front of you. I can't believe a packager wouldn't know about RDP!
PSExec - a free d/l from SysInternals (as Googling for 'PSExec' would have shown you...)
This allows you to run commands on remote machines from a command line.
Anyone doing this job ought to have already downloaded (and be intimately familiar with) practically EVERY SysInternals tool - they're just too useful to NOT have them...
This allows you to connect and log in to the remote machine, as if it were in front of you. I can't believe a packager wouldn't know about RDP!
PSExec - a free d/l from SysInternals (as Googling for 'PSExec' would have shown you...)
This allows you to run commands on remote machines from a command line.
Anyone doing this job ought to have already downloaded (and be intimately familiar with) practically EVERY SysInternals tool - they're just too useful to NOT have them...
Posted by:
Bankeralle
15 years ago
Well my point is why dosent wise install the package on the network-drive but only on local drive. (And Yes i have mapped the network drive, and yes i have the permissions).
I dont want to deploy the package on the network server, only on the client. The client installation should update the server though. ot is this impossible to accomplish
I dont want to deploy the package on the network server, only on the client. The client installation should update the server though. ot is this impossible to accomplish
Posted by:
Jamie B
15 years ago
Posted by:
anonymous_9363
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.