Issue with Wise Studio 5
Hi all, new to the site but not MSI repackaging..
Did a search here and on wise.com and am looking for some advice.
Trying to repackage Remedy User client 6.03 with WPS, after the initial scan and reboot, when I try to complete the setup capture, Wise starts to search the drive and bombs out. I am able to create other packages without issues.. just this one app giving me grief..[:'(]
So I am wondering, is there a specific file or service being installed by Remedy that could be causing the setup capture to fail?
The last time I repackaged Remedy, was for version 5.1.2 and I used Walls and Orca and did not have any issues like this... matter of fact I don't think I have ever had a setup capture just fail like this before...
Any guidance or suggestions would be greatly appriciated!!
Did a search here and on wise.com and am looking for some advice.
Trying to repackage Remedy User client 6.03 with WPS, after the initial scan and reboot, when I try to complete the setup capture, Wise starts to search the drive and bombs out. I am able to create other packages without issues.. just this one app giving me grief..[:'(]
So I am wondering, is there a specific file or service being installed by Remedy that could be causing the setup capture to fail?
The last time I repackaged Remedy, was for version 5.1.2 and I used Walls and Orca and did not have any issues like this... matter of fact I don't think I have ever had a setup capture just fail like this before...
Any guidance or suggestions would be greatly appriciated!!
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
wiseapp
19 years ago
Hi Seja:
Well sorry for replying late! Anyways if you keep the source files of the setup outside and program your MSI in a such a way that it should call the setup from those external folders(give a relative UNC Path). Now whereas the pushing the software thru AD is concerned just deploy the MSI and put the external folder along with the MSI on a network share, at the time of installation the MSI will automatically resolve the UNC path and will then start the setup.
Well sorry for replying late! Anyways if you keep the source files of the setup outside and program your MSI in a such a way that it should call the setup from those external folders(give a relative UNC Path). Now whereas the pushing the software thru AD is concerned just deploy the MSI and put the external folder along with the MSI on a network share, at the time of installation the MSI will automatically resolve the UNC path and will then start the setup.
Posted by:
sejacru
19 years ago
Posted by:
Balir
19 years ago
Posted by:
Jojo
19 years ago
Posted by:
wiseapp
19 years ago
Posted by:
wiseapp
19 years ago
Posted by:
sejacru
19 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.