Software Deployment

I was using the naitive installs, neither is an MSI.

My first try went like this;

1. Boot up clean machine, start new Wise project for Oracle ADI. Capture install.
2. Boot up second clean machine, start new Wise project for SAPgui 7.1. Capture install (Application Watch did not work with this install)
3. Run Conflict Manager to look for any cross-over.

That did not yeild a result.

My next attempt this evening is going to be to run a comparison of the two machines using other tools, a reg comparison tool, a file system comparison tool, etc.

Any other thoughts? Am I running noobishly down a path of failure?

are you planning to recapture and deploy these apps @ all, or are you planning to use the native installs, & were doing the wise captures just to troubleshoot?

if ApplicationWatch does not work, try and use setupcapture to create an install...

I've surprised myself by not responding in my now time-honoured way, i.e. recommending the use of ProcMon:

- install Oracle ADI (from vendor's media)
- install SAP GUI (ditto)
- run ProcMon
- attempt to start Oracle tool

ProcMon will show you straight away what's happening, in terms of files being opened (or an open attempted, with error(s)), registry data being read and written and processes started.

VBScab, I like the proc mon idea, good call. Do you filter the display at all or do you run it wide open? seems like it would have to run wide open in order to not miss anyhting.

Kiptek, I only did these captures as a troubleshooting step. I will end up creating an Oracle ADI capture install at some point, but this is not the day. I did see that others here like doing a capture on the SAPgui 7.1 but have issues with DLL self-regs, I have found that with a couple scripts and my altiris job, I don't need to repackage it.

ORIGINAL: klug
VBScab, I like the proc mon idea, good call. Do you filter the display at all or do you run it wide open? seems like it would have to run wide open in order to not miss anyhting.Oh, trust me, you'll want to filter stuff! For example, you're not in the least bit interested in what Explorer's doing, nor your AV executable, nor SVCHOST.EXE, etc, etc.

Great, I'll give that a shot, that should be able to nail down what's up.

Apologies...I *should* have added that filters can be saved. I have a default bunch set up, along with various others, all exported into suitably-named .REGs, ready to be sucked into whichever machine I happen to be using.You can find them in the 'Filter[whatever]' values under 'HKEY_CURRENT_USER\Software\Sysinternals\Process Monitor'

conflict manager in Wise perhaps..?

ORIGINAL: kiptek
conflict manager in Wise perhaps..? That assumes the OP is using Wise but the point is made. IS has conflict management, too so either will do the job.

In might be quicker, though, to do an admin install of both packages and then fire up a duplicate file finder and set it off against the two installation folders. If admin installs are not an option, I'd install to 2 VMs/VPCs and do the same exercise. The latter might take longer than a capture/conflict test, though.

Even your wise "visual diff" tool would be helpful to analyse on files and registries which are present in both MSI packages. Hope this helps!!

The VM idea might work pretty well, that would be a good comparison set. I did try using the Wise conflict manager, but it did not show anything. The SAP 7.1 installer would not work with the Application Watch active, so I could only do a basic Setup Capture, which may have limited what was seen. I'll try the VM meathod and see where that goes.

Thanks!

If you have captured & created both installs into an MSI using Wise, surely your conflict exists somewhere within the MSIs, unless you are installing using the native installs, in which case, trying to use Wise to find the conflict is... well, just is...

so question 1:
are the native installs stepping on each other, or is it your MSIs-from-capture installs?