Hi All
Does anyone have any experience of packaging "Foglight Transaction Recorder" v5.2.2 or v5.2.4? We have been struggling to get this working for a few days now (amidst doing other things), although we can get it to install using the extracted msi and isscript etc, it just isn't playing ball in putting shortcuts etc quite where we want them to go. Any information gratefully received.
Cheers
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
it just isn't playing ball in putting shortcuts etc quite where we want them to go

not much info here

where are the shortcuts installing to
where do you want them to go

what does your log file say
Answered 08/19/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
It wouldn't be the first time that a vendor has shortcut creation handled by a Custom Action...check that out, too.
Answered 08/19/2009 by: VBScab
Red Belt

Please log in to comment
0
That's the whole point - the vendor has supplied an InstallShield .exe file which when you run that as an admin works absolutely perfectly. However, we run a tightly locked down estate, so all software is installed silently via SMS. The -s switch didn't work properly on the file they supplied (it wasnt at all silent) and the vendors suggested that we use the -r switch to install, thus creating a setup.iss file. Having created that we ran the installer using the resulting file and instead of the shortcuts being placed in ...Programs\Quest Software\Foglight Transaction Recorder, the shortcuts appear on the start menu just in Programs (which we don't allow on our PC estate).
We have switched on verbose logging and there is no mention anywhere on where the shortcuts are being written, or even at what point they are being written.
The logging tells us that the installer is calling other .msi files left right and centre, but when you look into them they are not that helpful. There are plenty of custom actions going on, but not one of them is commented so it's all getting a bit needle in a haystack!
Basically we can write a script to move the shortcuts once the install has finished, but before I went down that path was just wondering if anyone else has had any experience with this particular application.
Answered 08/19/2009 by: JillBA
Senior Yellow Belt

Please log in to comment
0
I had faced this kinda issue once...not with this app but with some other... We couldnt debug it so we had to rely on a script which deleted the shortcuts from strt->AllPrgs and placed them under the strt->Prgs->APPNAME...
I guess you will have to do same..
Answered 08/19/2009 by: PackDep
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: PackDep

I had faced this kinda issue once...not with this app but with some other... We couldnt debug it so we had to rely on a script which deleted the shortcuts from strt->AllPrgs and placed them under the strt->Prgs->APPNAME...
I guess you will have to do same..


We kinda figured that, but thought it was worth asking incase anyone else had a working solution.
If you don't ask you dont get etc.

Thanks
Answered 08/19/2009 by: JillBA
Senior Yellow Belt

Please log in to comment
0
oh well, so it's one of those annoying CA generated shortcuts
not much you can do then [:@]
Answered 08/19/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
Thanks for the responses. Sorry the initial post was so vague - I kinda wanted to see what came out of the woodwork without leading too far!
I guess we already knew the answer, but was hoping it wasn't what we thought it was.

[8D]
Answered 08/19/2009 by: JillBA
Senior Yellow Belt

Please log in to comment
0
not much you can do then [:@]Step through the MSI in your authoring tool's debugger. As soon as one of the shortcuts appears, the CA which just executed will be the culprit.
Answered 08/19/2009 by: VBScab
Red Belt

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