/build/static/layout/Breadcrumb_cap_w.png

Acrobat 6.0.1 again..! No luck

Hi,

I know there are already several threads about acrobat 6.0.1, but I'm still a bit lost...
I want to distribute 6.0.1 but so far:
- No matter if published or assigned or to user, will only install if clicked on by user in control panel
- Even if I do use this method (which I can live with) reader 6.0.0 is still installed.. is there any way to remove it first?
- If I assign it to computers, it says it's installing at startup, but then is no-where to be seen.

I've tried including various transforms but nothing has made any difference...
Is there some way to assign to computers so that a user logs on and it's there? Also is there any way to remove 6.0.0 first so that there isn't two programs taking up space?

Any help would be much appreciated!! :D

Thanks,

Tania [:)]

0 Comments   [ + ] Show comments

Answers (7)

Posted by: kaspianx 20 years ago
Senior Yellow Belt
0
Are there any clues in the event log as to why the assigned install might have failed?
Posted by: tan 20 years ago
Senior Yellow Belt
0
For the most part I get the message:

The installation source for this product is not available. Verify that the source exists and that you can access it.

From what I've read this is to do with permissions? But if it's assigned to the user, not the computer, and the domain users all have access to the share with the install files, why does this still fail? :(
Posted by: tan 20 years ago
Senior Yellow Belt
0
Sorry, just to add there, that is error ID 102.

Before that, it says: "The assignment of application Adobe Reader 6.0.1 from policy Default Domain succeeded. " (301) so it does get assigned correctly by the looks of things.

Any ideas would be much appreciated!

Tania :D
Posted by: plourenco 20 years ago
Senior Yellow Belt
0
Hi Tania,

Is your package located in a Windows 2000 cluster ?
If yes, you will need to activate the cluster Kerberos (by default it is deactivated) in order to apply a software installation to a computer.

Cheers
Posted by: kirkpatrick 20 years ago
Yellow Belt
0
Hi!

I had the same thing.
I was working on a contract and accepted the location for the MSI repository as given to me.

Turns out it was on a NT4 Server (member server) in an AD Domain (mixed mode)

What OS is the server that is hosting the packages share?
NT will not provide Kerberos Authentication to the workstation thereby making application installation of an assigned nature impossible.

Hope that helps!


Mike
Posted by: tan 20 years ago
Senior Yellow Belt
0
Hi again,

Thanks heaps for your suggestions, they're much appreciated :)
The package is located on a Windows 2000 file server, so it's not the NT problem. I don't think it would be a cluster - I'm sorry for being so clueless! But how do I tell if it is and if I need to activate the cluster Kerberos?

Kind regards,

Tania
[:)]
Posted by: tan 20 years ago
Senior Yellow Belt
0
Hello all!! It's working!!! :D

Well for the most part anyway. ;) I turned off XP logon optimisation via group policy, and that seems to have done the trick, because now when you logon there's no trouble applying the software update. Click on a pdf and it installs 6.0.1.
I've even created an administrative template to change any settings via gpo. (As you can tell i'm pretty happy with myself to finally get this working!!! )

The only thing is I still have 6.0.0 installed on most of the machines, so it's wasting space to not uninstall it... any way I can uninstall it with the GPO at the same time as setting 6.0.1??

Thanks heaps again,

Tania :)
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ