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!!
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
What is the setupcapture methodology (smartmonitor, snapshot or the smartmonitor/ snapshot option).
Maybe you could try to switch yout methodology.
Answered 08/10/2005 by: sejacru
Second Degree Blue Belt

Please log in to comment
0
Didn't think of that.. using only snapshot, so I will try it with smartmonitor. Thanks!
Answered 08/10/2005 by: Balir
Yellow Belt

Please log in to comment
0
That worked, such a simple thing... thank you very much!! [:D]
Answered 08/10/2005 by: Balir
Yellow Belt

Please log in to comment
0
youre welcome
Answered 08/10/2005 by: sejacru
Second Degree Blue Belt

Please log in to comment
0
Thanks for this posting - I too was having problems with packaging Remedy User 6.* and was at the end of my tether, but have now tried using smartmonitor and it's worked for me too! [:)] Bizarre though, isn't it!? [8|]
Answered 08/17/2005 by: Jojo
Yellow Belt

Please log in to comment
0
Hi,

Well Sejacru that was a quick one, gr8 man. Anyways I wanted to say that its better to create a wrapper for the same, what do you think Sejacru? since that's the safest way to repackage
Answered 08/17/2005 by: wiseapp
Second Degree Green Belt

Please log in to comment
0
explain this it to me please.....
Answered 08/17/2005 by: sejacru
Second Degree Blue Belt

Please log in to comment
0
Dear Sejacru:

I meant we could create a wrapper that will call the setup of Remedy in a silent mode and would then install the same on the end user. Since that does not require any sort of repackaging and hence would be the safest method to install Remedy or any other software.
Answered 08/18/2005 by: wiseapp
Second Degree Green Belt

Please log in to comment
0
Oke i get it....that is also possible.

But how do you push the software...through the AD?
Answered 08/18/2005 by: sejacru
Second Degree Blue Belt

Please log in to comment
2
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.
Answered 08/24/2005 by: wiseapp
Second Degree Green Belt

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