Wednesday, 19 January 2011

Adobe Acrobat OS X Active Directory Crash

So after fixing Adobe Acrobat admin password problem acrobat 8 loads up, but crashes after 20 seconds. I remember fixing this exact problem with Marketings' computer, Louise Webster I think.

Doh! I didn't write the solution in the blog!!! Lesson learned over and over again. So here's the brief explination I told Paul Jenkins by email:


Hi Paul,
I went over at 12 today to have a look. It appears to have problems on any active directory accounts which aren’t administrators. Its a permissions issue because acrobat (and lots of other programs) write temp files to the users home drive with the wrong permissions. The NHR program was installed but only redirects caches and fonts folders to the local drive, but still didn’t fix the acrobat problems. I found another folder which needed re-directing - “~/Library/Application Support/Adobe/Acrobat/”
I made a folder in “/Users/Shared/Websterl/” and created an alias in her “/Library/Application Support/Adobe/Acrobat/” so it gets re-directed to the local drive. It only works on this machine for only her at the moment. If any more people have the same problem it would be worth adding an entry in the NHR program for acrobat.
I also noticed the programs and operating system weren’t up-to-date. I’ve set it updating adobe products. Louise said she’d get back in contact if she had any more problems. I didn’t get around to updating the operating system though.
Cheers
Stephen
I had a look at this folder and came up straight away with error! I remember not it was a folder within this folder:  /Library/Application\ Support/Adobe/Acrobat/9.0_x86. So after redirecting this one it works. So to fix this problem for everyone, NHR program will need to do this as well! I'll find out how to do that tomorrow!



Unfortunately, NHR the full program redirects too many folders, i.e. Microsoft User Data, so I'll have to adapt the loginhook, logouthook, clean script files etc. But then I can copy them to all machines and it should be fine.

No comments:

Post a Comment