Adobe CS6 - Super Mandatory Profiles

[Zoom7000]

I've just installed Adobe Design & Web Premium CS6 on to our Windows XP PCs. We are running a Windows Server 2003 AD with Super Mandatory Profiles. Every time I launch Photoshop, Bridge, InDesign or Illustrator I get a fatal application error and the program terminates and every time I run Flash Professional, I get the message "FlashPro encountered a fatal exception. FlashPro will now terminate."

 

I've followed advice in this thread and I've disabled ScriptingSupport.8li to get Photoshop working. However, I can't seem to get any of the applications working. The only application that seems to work is Acrobat. I've tried giving users Modify access to the following areas:

 

C:\Program Files\Adobe

C:\Documents and Settings\All Users\Application Data\Adobe

C:\Program Files\Common Files\Adobe

 

But this hasn't resolved any of the issues.

 

Any ideas what I can do?

[Willott]

Procmon and see what's being denied?

[OhDear]

Does it work if you make them local admins/power users? We had to do this for a piece of software

[Zoom7000]

Does it work if you make them local admins/power users? We had to do this for a piece of software

 

I've logged on with my admin user domain account that has also has a redirected application data and I get the same error.

 

Procmon and see what's being denied?

 

Procmon? How do I go about doing this?

[VeryPC_Tom_M]

Procmon? How do I go about doing this?

 

Procmon is part of the SysInternals Toolkit

 

You can either download it from here: Process Monitor

or run it live from: live.sysinternals.com - /

[2097]

When you created the profile , did you open each program before making it a mandatory profile ?

[Zoom7000]

When you created the profile , did you open each program before making it a mandatory profile ?

 

No, the Super Mandatory profile was created years ago long before we ever installed CS6.

 

How would I use Process Monitor to check what is being blocked?

[AngryTechnician]

I've logged on with my admin user domain account that has also has a redirected application data and I get the same error.

I would wager that the redirected AppData is the problem. Adobe products have had problems with it intermittently for years: one version will work, the next version won't.

 

Basically, they don't ever test their products in a redirected AppData environment. We were officially told by an Adobe support rep in 2009 that Adobe don't support the use of redirected AppData at all (may have changed now, but that was the case at the time).

 

If you have any way of testing without redirection, try it.

Edited September 25, 2012 by AngryTechnician

[Willott]

Apologies for my lack of reply. Proc mon is a download from Microsoft iirc, if you load it up, then load whichever program you have the issue with, let the issue happen, then stop capture in proc mon. You can then filter by process name (for flash I think that's flash.exe) then do a find for "denied" and see if anything comes up.

[Zoom7000]

I would wager that the redirected AppData is the problem. Adobe products have had problems with it for years. We were officially told by Adobe in 2009 that Adobe don't support the use of redirected AppData at all (may have changed now, but that was the case at the time).

 

If you have any way of testing without redirection, try it.

 

Yes, I though this was the case. I've tested it using the builtin Administrator account, which has it's profile in C:\Documents and Settings (i.e. Not redirected) and the program works just fine. Is there any chance of getting the suite working with super mandatory profiles or is there no hope whatsoever? As I can't see us being given the chance to change the current setup.

[Zoom7000]

When you created the profile , did you open each program before making it a mandatory profile ?

 

I've just tried this. I changed the profile from Super Mandatory to Roaming. Opened all the applications (with no errors), saved settings and then made the profile Super Mandatory again. Gave the same errors

[7UD9]

I've just tried this. I changed the profile from Super Mandatory to Roaming. Opened all the applications (with no errors), saved settings and then made the profile Super Mandatory again. Gave the same errors

 

Have you made any progress with this? We're having the same issue at the moment and struggling for a solution.

 

Thanks

[Finch7]

Same problem,

 

Fixed it just now by

 

1) copying my mandatory profile

2) Assign the copy to a test student account

3) give that student full control

4) rename ntuser.man to ntuser.dat

5) assign your test pc to a test OU (within the existing strucure) and edit the GPO to allow changes to propagate to server (it's a computer policy, system>userprofiles)

6) reboot test pc so gpo change applies

7) log on as test student

8) log off as test student

9) check that the time stamp on the ntuser.dat has changed to the log out time. (if not check steps above)

10) log back on

11) open CS6 Indesign

12) wait till it opens fully then close it (our issue was that it crashed on launch for mandatory profile)

13) log off

14) rename ntuser.dat to ntuser.man

15) remove test account permission and edit gpo to prevent changes to propagate (belt and braces)

16) log back on and open CS6 indesign (for us this still worked)

17) So far this bloated our mandatory profile by 2Mb so for us the following elliminates most of this and still works.

18) make a copy of the new profile

16) delete appdata\roaming\adobe folder

17) test again.

 

We're currently going to thoroughly test the new profile tomorrow before making it live (by renaming the copy to the live version)

 

I'll post any updates or glitches this may have caused should any crop up.

[7UD9]

Same problem,

 

Fixed it just now by

 

1) copying my mandatory profile

2) Assign the copy to a test student account

3) give that student full control

4) rename ntuser.man to ntuser.dat

5) assign your test pc to a test OU (within the existing strucure) and edit the GPO to allow changes to propagate to server (it's a computer policy, system>userprofiles)

6) reboot test pc so gpo change applies

7) log on as test student

8) log off as test student

9) check that the time stamp on the ntuser.dat has changed to the log out time. (if not check steps above)

10) log back on

11) open CS6 Indesign

12) wait till it opens fully then close it (our issue was that it crashed on launch for mandatory profile)

13) log off

14) rename ntuser.dat to ntuser.man

15) remove test account permission and edit gpo to prevent changes to propagate (belt and braces)

16) log back on and open CS6 indesign (for us this still worked)

17) So far this bloated our mandatory profile by 2Mb so for us the following elliminates most of this and still works.

18) make a copy of the new profile

16) delete appdata\roaming\adobe folder

17) test again.

 

We're currently going to thoroughly test the new profile tomorrow before making it live (by renaming the copy to the live version)

 

I'll post any updates or glitches this may have caused should any crop up.

 

I've done the exact same today and have already rolled it out after some testing. I forgot to post it up so thanks for posting these steps, hopefully it will help others out facing the same issue.

[Zoom7000]

Same problem,

 

Fixed it just now by

 

1) copying my mandatory profile

2) Assign the copy to a test student account

3) give that student full control

4) rename ntuser.man to ntuser.dat

5) assign your test pc to a test OU (within the existing strucure) and edit the GPO to allow changes to propagate to server (it's a computer policy, system>userprofiles)

6) reboot test pc so gpo change applies

7) log on as test student

8) log off as test student

9) check that the time stamp on the ntuser.dat has changed to the log out time. (if not check steps above)

10) log back on

11) open CS6 Indesign

12) wait till it opens fully then close it (our issue was that it crashed on launch for mandatory profile)

13) log off

14) rename ntuser.dat to ntuser.man

15) remove test account permission and edit gpo to prevent changes to propagate (belt and braces)

16) log back on and open CS6 indesign (for us this still worked)

17) So far this bloated our mandatory profile by 2Mb so for us the following elliminates most of this and still works.

18) make a copy of the new profile

16) delete appdata\roaming\adobe folder

17) test again.

 

We're currently going to thoroughly test the new profile tomorrow before making it live (by renaming the copy to the live version)

 

I'll post any updates or glitches this may have caused should any crop up.

 

I've just tried this and it hasn't worked for me. I've followed everything until step 11, but I get the error when launching InDesign and can't get the applications to launch. I've tried launching Dreamweaver - which won't start at all and I've tried Flash, which takes forever to start and gives the error:

 

FlashPro encounter a fatal exception. FlashPro will now terminate.

 

So, no luck for me I'm afraid