Software Deployment

Perhaps you could re-post, this time with even LESS information? :)

- Have you logged the install, for example? If so, what does that tell you? If not, that's the first step.
- How are you deploying? Group Policy? SMS/SCCM? Radia? Altiris? ZenWorks?
- Does it install correctly outside of your deployment mechanism?

Hello friend,

1 I do not think so. How would I do this?

2 I make use of Group Policy for this purpose.

3 But of course.

Many thanks in advance.

Rupal

1 I do not think so. How would I do this?
2 I make use of Group Policy for this purpose.In that case, you simply set up the local GP to enable it. You then end up with files prefixed with "MSI", followed by a random alphanumeric name, with the extension ".LOG" in the folder %SystemRoot%\TEMP. Note that this is NOT the user's TEMP folder.

Because the filenames are random, you have no way of knowing which one has logged the Office install So, you then search those files for some unique text (the ProductCode is an obvious candidate). Once you find the log, find the FIRST instance of the text "Return value 3. " This is the value returned by any action which has failed. In the dozen or so lines either side of that line, you should be able to identify the reason for its failure.

Remember to disable logging once you're done: it's an all or nothing policy and will log EVERYTHING, including any advertising installs.

Hello Friend,

Many thanks for you wonderful help, I am sure that I shall conquer this unruly software!

Many thanks in advance.

Rupal