Software Deployment

Open the .mst in orca or wise and see if it changes anything in the shortcuts or icons table, WiseInstallTailer sometimes includes unnecessary information.

I've checked that but cannot see any problems. I've also tried installing the package manually and the icons are fine, the problem only occurs when I use AD deployment.

I've also tried chaning the icons to a completely different image. Again, this works fine when installing manually but as soon as I try it with AD I get the default windows exe icon.

Never had a problem like this before. Any suggestions?

Shortcuts are advertising shortcuts, that's the reason the shorcut icon links are pointing to the windows installer cache...
Delete the old shortcuts and create a new shortcuts in the Transform....

Make sure that you have the same ProductCode in the MSI and in Transform..

Thanks for your reply. I checked the shortcuts and "advertised" was set to no, however I still tried deleting them and recreating them just to make sure, but I still get the same problem of an incorrect icon and error message when I click the "change icon" button under shortcut properties.

The error has changed slightly, presumably as a result of recreating the shortuct:
"Windows cannot find the file %systemroot%\installer\{5B782FFA-6A95-480D-8E0A-0954A14693D6}\NewIcon.exe."

However, in the AD GPO editor, I set photoshop elements to "redeploy", and after it had reinstalled on the test machine the icons were fine. I then wiped the test machine and started from scratch. After a first install of photoshop elements I had the icon problem but after a redeploy it was ok.

Does anyone have other suggestions? It looks like some part of the install doesn't work properly through AD the first time, since a manual install works fine and an AD redeploy fixes it.

Hi

When you repackage a msi file, you have always the same Pb.

Your package can be have too the darwins descriptors, the darwins descriptors are the stronges keys (use a package validation, you must have many errors about the ice03). This keys reference the old package MSI for the repair.

For the extension, you have mainly two keys. The HKCR\.ext and the HKCR\ProgId. The ProgId is determined by the value default under the key HKCR\.ext.

I think what you must verify if you don't have this keys (darwins descriptors) under :

HCKR\ProgId\DefaultIcon -> icon associated with the extension
HKCR\ProgId\Shell\Command_Verb\Command -> you can have two value, the default value (reference the path of the exe) and the command value (darwins descriptors used for the repair, because when you have this command value you don't launch the executable file but you launch Windows Installer which verify your configuration. If you keep this value, the repair is based on the old msi file - BIG ERROR)

You can find too the darwins descriptors under the Improcserver, localserver .

Ciao

Eric

Thanks for your input. I didn't quite understand the darwin stuff but I put the base msi (not using my mst) through the validation routine in installshield 10.5. I got 0 failures, 51 errors, 420 warnings.

After wasting two weeks trying to sort this plus another couple of weeks before that on photoshop cs2, I'm now on the verge of giving up on adobe products. No other installers have give me as much hassle. I think PSP9 must be worth a shot.

If anyone else has any other suggestions, please let me know.