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?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
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?
Answered 12/17/2008 by: VBScab
Red Belt

Please log in to comment
0
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
Answered 12/17/2008 by: Bankeralle
Second Degree Blue Belt

Please log in to comment
0
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...
Answered 12/17/2008 by: VBScab
Red Belt

Please log in to comment
0
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
Answered 12/17/2008 by: Bankeralle
Second Degree Blue Belt

Please log in to comment
1
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
Answered 12/17/2008 by: VBScab
Red Belt

Please log in to comment
0
thx m8, Just the answer i was looking for
Answered 12/17/2008 by: Bankeralle
Second Degree Blue Belt

Please log in to comment
0
Bear in mind setting ROOTDRIVE wont redirect "shell" folders - ie if you are installing under [ProgramFilesFolder] for instance. As you are installing to NetDrive:\Apps you should be fine.
Answered 12/17/2008 by: Jamie B
Orange Senior Belt

Please log in to comment
0
Just figured it out m8. But thx anyway
Answered 12/17/2008 by: Bankeralle
Second Degree Blue Belt

Please log in to comment
0
I know this might come across as "Grumpy Old Man" but please try and remember that AD has an international user base so, if we can avoid text-speak, it would help enormously those for whom English is not their first language.
Answered 12/17/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity