Repair when s/c points to a URL
For good or ill, my client is installing all apps per-user via Group Policy.
My problem concerns an app which comprises a couple of DLLs, a config file and a shortcut which points to a URL. When user A logs in, the app installs, as expected. Ditto for user B. Now, when user B is removed from the group and logs in, the app is uninstalled, also as expected. However, when user A logs in, because the s/c points to a URL, no repair takes place.
I initially thought I could simply create a conventional s/c and point it at the .URL file but of course Windows sees that activity and makes the new shortcut point directly to the URL, making the whole exercise pointless.
So, what's the best way to construct the installation so that repair takes place?
My problem concerns an app which comprises a couple of DLLs, a config file and a shortcut which points to a URL. When user A logs in, the app installs, as expected. Ditto for user B. Now, when user B is removed from the group and logs in, the app is uninstalled, also as expected. However, when user A logs in, because the s/c points to a URL, no repair takes place.
I initially thought I could simply create a conventional s/c and point it at the .URL file but of course Windows sees that activity and makes the new shortcut point directly to the URL, making the whole exercise pointless.
So, what's the best way to construct the installation so that repair takes place?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
fosteky
17 years ago
I've had the same problem before, I wrote a VBScript to launch the whatever on the network and used Primal script to compile the VBScript to an EXE and put that EXE right into the package, set as a key file. Made an advertised shortcut to the local EXE, and if that EXE's been uninstalled by some other user then it self repairs and it works.
Posted by:
anonymous_9363
17 years ago
I had more or less the same idea, except w/o the compiling part. It works for user 1 but, when user 2 logs in, the s/c is empty and user gets 'No parameter was given' (or something like that - I'm at home now, not in the office) when they try to execute it. Oddly, then returning to my packaging machine and executing the MSI there (local admin rights, obviously) everything's hunky-dory. Clean the testing box, re-run the MSI for user 1 - all good. Log in user 2, empty s/c! What in God's name is going on there?!?!?! Could it be connected with the custom ICO I'm using? The users want the vendor's icon, not the generic IE one which I'd normally use.
Tomorrow, I'm going to create a different shortcut, pointing to IE with the URL as an argument and see if that improves my chances.
Tomorrow, I'm going to create a different shortcut, pointing to IE with the URL as an argument and see if that improves my chances.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.