Deploying Adobe Reader 6.0.2 German

[Soeren Kuklau]

Hi,

Adobe Reader 6.0.2 provides an important security fix over 6.0.1, so
I'd rather deploy it as fast as possible. However, for some reason,
Adobe does not provide a German full install package, and only an
update package for 6.0.1 users. This means that I cannot replace my
6.0.1 MSI (which works fine) with a 6.0.2 one, but will instead have
to add a 6.0.2 Update MSI.

Unfortunately, one machines that don't have 6.0.1 installed yet,
Windows will decide to try and install 6.0.2, which fails, as it's the
incorrect order.

How can I force the 6.0.1 to be installed before the 6.0.2 Update
package gets considered?

 

[Cary Shultz [A.D. MVP]]

Soeren,

Schoenen Guten Morgen aus den USA!

I will speak only to the order for this 6.0.2 to be installed.

I am going to make a couple of assumptions here:

1) that you are deploying 6.0.1 via GPO ( should be safe on that one )
2) that you are deploying 6.0.1 to the computer configuration side of things
( could go either way - I like to publish to the user side )...

What I would do is to make sure that all of the computer account objects (
see assumption #2 ) are in the OU to which you are going to link the GPO (
or, possibly better said - that all of the computer account objects that you
would like to fall under the influence of this GPO are in OUs to which the
GPO is linked ) and then make sure that at the bottom of the list is the GPO
that deploys 6.01 and above this is the GPO that deploys 6.0.2!

Remember that the pecking order of GPOs is local, Site, Domain and OU and
that within the same level the one at the bottom of the list is deployed
first and the one at the top of the list is deployed last.

Now, having said all that I am not sure - from experience - that you can
deploy an 'update'. And I am not talking about creating a GPO that deploys
Service Pack 4 to update the GPO that deploys Service Pack 3. This I have
done many times. In this example both deployments were of the full version
( of the Windows Service Pack )!

I will play with this and let you know what I find out if you do the same!

HTH and mfg,

Cary

 

[Soeren Kuklau]

Soeren,

Schoenen Guten Morgen aus den USA!

Bin gerade erst wieder zurueck von dort!

I will speak only to the order for this 6.0.2 to be installed.

I am going to make a couple of assumptions here:

1) that you are deploying 6.0.1 via GPO ( should be safe on that one )
2) that you are deploying 6.0.1 to the computer configuration side of things
( could go either way - I like to publish to the user side )...

I should have mentioned this. Both assumptions are correct: I am using
GPOs, and I am deploying on the computer-side, not the user-side.

What I would do is to make sure that all of the computer account objects (
see assumption #2 ) are in the OU to which you are going to link the GPO (
or, possibly better said - that all of the computer account objects that you
would like to fall under the influence of this GPO are in OUs to which the
GPO is linked )

That is the case.

and then make sure that at the bottom of the list is the GPO
that deploys 6.01 and above this is the GPO that deploys 6.0.2!

Remember that the pecking order of GPOs is local, Site, Domain and OU and
that within the same level the one at the bottom of the list is deployed
first and the one at the top of the list is deployed last.

Ah, I wasn't aware of this bottom-to-top rule. I should give that a
try.

Now, having said all that I am not sure - from experience - that you can
deploy an 'update'.

If not, I'm puzzled how others have solved this problem, as Adobe
Reader 6.0.2 solves a security issue and is this an important update.

I will play with this and let you know what I find out if you do the same!

Thanks a lot for your help

Regards,

Soeren 'Chucker' Kuklau

 

[Cary Shultz [A.D. MVP]]

Soeren,

Have not had time to check this out yet. Will, however, in the near future.

Cary

"Cary Shultz [A.D. MVP]" <[email protected]> wrote in message

Soeren,

Schoenen Guten Morgen aus den USA!

Bin gerade erst wieder zurueck von dort!

I will speak only to the order for this 6.0.2 to be installed.

I am going to make a couple of assumptions here:

1) that you are deploying 6.0.1 via GPO ( should be safe on that one )
2) that you are deploying 6.0.1 to the computer configuration side of things
( could go either way - I like to publish to the user side )...

I should have mentioned this. Both assumptions are correct: I am using
GPOs, and I am deploying on the computer-side, not the user-side.

What I would do is to make sure that all of the computer account objects (
see assumption #2 ) are in the OU to which you are going to link the GPO (
or, possibly better said - that all of the computer account objects that you
would like to fall under the influence of this GPO are in OUs to which the
GPO is linked )

That is the case.

and then make sure that at the bottom of the list is the GPO
that deploys 6.01 and above this is the GPO that deploys 6.0.2!

Remember that the pecking order of GPOs is local, Site, Domain and OU and
that within the same level the one at the bottom of the list is deployed
first and the one at the top of the list is deployed last.

Ah, I wasn't aware of this bottom-to-top rule. I should give that a
try.

Now, having said all that I am not sure - from experience - that you can
deploy an 'update'.

If not, I'm puzzled how others have solved this problem, as Adobe
Reader 6.0.2 solves a security issue and is this an important update.

I will play with this and let you know what I find out if you do the

same!

Thanks a lot for your help

Regards,

Soeren 'Chucker' Kuklau