Software Deployment

what kind of permission problem are you facing.
cache.db and pcd.db are not the one which used for file permissions. it is more for their own meta data.
can you describe more on the problem you are facing

Thanks for the reply,

Here we go

1. It Installs and works fine as an administrator but as an user it fails to install "Additional File Formats and Effects Installation"

I used reg mon and filemon to find what is happening and found out and what it needed permissions to the these folders
a. Adobe PCD, Caps and backup.

And the weird thing is even though i give full permissions to these folders as I launch the shortcut it reverts back the file permissions to normal.

And then tried disabling the Advertised shortcuts to see if it is actually reparing it but then it still asks for the permissions for Caps folder.
stuck there

So thisz wat happening any help would be appreciated.

Thanks,
Ram.

Different app, I know, but here's the text of an email I sent to my current client's management about Acrobat Professional v8:

The main EXE is altering permissions to a folder (C:\Program Files\Common Files\Adobe\Adobe PDC) such that 'Administrators' have 'Full Control' and 'Everyone' has 'Read/Write' access. The problem is that the EXE requires the 'Write DAC' permission! Without that access, it pops up a dialog telling me that there is a serious error and then exits. What superb error-handling... [/align] I have obviously tried re-assigning permissions after installation but the EXE alters those permissions back as it loads, on the fly. This is 100% reproducible. Following suggestions on the Adobe forum, I tried SP1 but it made no difference. Quite why ANY application thinks it can walk over local permissions escapes me but anyway, as a consequence, I regard this application as unusable. [/align] [/align] If go-ahead is required, the only viable solution is to add the user(s)/group to the local Administrators group, something which will need sign-off from someone other than me. I have logged it as a bug on Adobe's site but, from past experience with this bunch of clowns, I hold no hope of any action anytime soon. Of course, if [client's name removed] has any inside track with Adobe, it might be apposite to exploit it.

As ever, ProcMon was able to show me this access issue.
[/align]

Thankyou VBScab,

I was woundering how come others have no issues about this. Even I spoke to Adobe and gave them a clear description about what is happening.
Still waiting for a response from them.

Thanks,
Ram.

ORIGINAL: Ram
Even I spoke to Adobe and gave them a clear description about what is happening.
Still waiting for a response from them.Don't hold your breath. From a support point of view, they are just about the most useless vendor I've encountered. All I've ever got from them is a "scripted" response, the usual nonsense:

- uninstall all Adobe products, then re-install [crappy Adobe app of your choice]
- turn off a/v, anti-spyware, then re-install [crappy Adobe app of your choice]
- turn off firewall (!), then re-install [crappy Adobe app of your choice]
- re-install Windows, then re-install [crappy Adobe app of your choice]

Thankyou VBScab,
I will try that now.

And see how it goes.

Thanks,
Ram.

ORIGINAL: Ram
Thankyou VBScab,
I will try that now.Er, I wasn't suggesting that you try anything, but telling you that that's the pointless trail that Adobe will send you down. You will need to first tie down if my supposition is correct. If you're sure that the EXE is altering the permissions, then you need to get hold of someone at Adobe and once you've talked them out of their desire to get you to jump through the pointless hoops detailed above, shout, very loudly, about their wanton destructiveness of your carefully-built workstation permissions and ask them if you can have a non-destructive version.

Hello VBScab,

Thankyou onceagain.
They did call me but they said they dont have a solution as of now.
But I did find the solution.
The AdobeAfterEffects once installed and it actually runs one more msi to install the additional formats. I took that msi out I installed(had to turn off few custom actions to make it run successfully) it seperately as soon as I installed AdobeAftereffects.

One can think i could use Active setup but that would not help as It only runs the msi once the shortcut is launched. And also applying Active setup would take 20 min to reinstall the entire thing.

Anyway thanks for you help.

Ram.

You wouldn't be able to use AS to install applications anyway, unless all your users have local admin privileges because it runs in the User context.

ORIGINAL: VBScab

Different app, I know, but here's the text of an email I sent to my current client's management about Acrobat Professional v8:

The main EXE is altering permissions to a folder (C:\Program Files\Common Files\Adobe\Adobe PDC) such that 'Administrators' have 'Full Control' and 'Everyone' has 'Read/Write' access. The problem is that the EXE requires the 'Write DAC' permission! Without that access, it pops up a dialog telling me that there is a serious error and then exits. What superb error-handling... [/align] I have obviously tried re-assigning permissions after installation but the EXE alters those permissions back as it loads, on the fly. This is 100% reproducible. Following suggestions on the Adobe forum, I tried SP1 but it made no difference. Quite why ANY application thinks it can walk over local permissions escapes me but anyway, as a consequence, I regard this application as unusable. [/align] [/align] If go-ahead is required, the only viable solution is to add the user(s)/group to the local Administrators group, something which will need sign-off from someone other than me. I have logged it as a bug on Adobe's site but, from past experience with this bunch of clowns, I hold no hope of any action anytime soon. Of course, if [client's name removed] has any inside track with Adobe, it might be apposite to exploit it.

As ever, ProcMon was able to show me this access issue.
[/align]


This is great information, I'll make a note of it.
Some of you might not believe this, but the last 4 years I have only done projects/contracts where the users of the companies had a minimum of Power Users access/permissions. The last two companies........local admin.....all of the users. So, explains why I didn't have this problem with these Adobe products.
But who knows what the future holds, I just might end up "some day" in a lock down environment and when I run in to this problem.... well,........I'll thank you now, cause it surely saves a lot of work.

Cheers.
Gizsha

Ian,

The problem is that the EXE requires the 'Write DAC' permission! Without that access, it pops up a dialog telling me that there is a serious error and then exits.

Would it be possible to use ACT to fool the EXE regarding the permissions and then if required only set permissions on files it really needs write access to?

ORIGINAL: AngelD
Ian,

The problem is that the EXE requires the 'Write DAC' permission! Without that access, it pops up a dialog telling me that there is a serious error and then exits.

Would it be possible to use ACT to fool the EXE regarding the permissions and then if required only set permissions on files it really needs write access to?Not a clue, Kim, I'm afraid. I try to avoid kludging wherever possible. This sort of nonsense (i.e. wanton permission-changing by apps) has no place in a corporate environment and in this case, the client agreed and I left it to them to shout at the vendor.