Can’t run PP5.5 without domain admin credentials

[Todd Kopriva]

What’s the question, exactly?

Yes, you should run Premiere Pro as administrator.

———————————————————————————————————
Todd Kopriva, Adobe Systems Incorporated
Technical Support for professional video software
After Effects Help & Support
Premiere Pro Help & Support
———————————————————————————————————

[Michael Stephens]

The question is that since I’m already an admin on my computer how do I run PP5.5 without having to run it as a domain administrator. It doesn’t fully load even though I’m an admin and even if I tell it “Run as Administrator” it freezes right before the option to start or load a project.

[Alex Gerulaitis]

Michael,

Have you tried creating a local admin account (non-domain) and try to run Pr there? (Not saying this is a solution – I understand if you need to run the system on a domain – just as a test.)

All I can think of is that (a) local folders may be redirected for domain accounts, (b) Pr attempts to access some of those on launch, and (c) domain group policies may restrict access to some of them unless it’s a domain admin account; that would explain Pr not launching properly. The fix would to modify domain GPOs accordingly, possibly with the help of Todd who I am sure knows intimately which folders need which permissions in Pr. Or, run Pr as a local admin.

Alex (DV411)

[Alex Gerulaitis]

[Todd Kopriva] “Yes, you should run Premiere Pro as administrator.”

Todd,

I am just curious: is Pr CS5.5 operation unsupported on a non-admin accounts? If indeed so, are there plans to support running Pr without admin privileges in future versions?

Thanks.

Alex (DV411)

[Todd Kopriva]

> I am just curious: is Pr CS5.5 operation unsupported on a non-admin accounts? If indeed so, are there plans to support running Pr without admin privileges in future versions?

Premiere Pro needs to write to a lot of files and locations, and doing that requires a certain level of permissions on the system. Running as administrator is the easiest way to ensure that such writes don’t fail.

If you want this to change, let us know with a feature request.

———————————————————————————————————
Todd Kopriva, Adobe Systems Incorporated
Technical Support for professional video software
After Effects Help & Support
Premiere Pro Help & Support
———————————————————————————————————

[Michael Stephens]

That does work, but I can’t switch back and forth between a domain and a non-domain account to do my work as I won’t have access to our e-mail if I’m not on the domain anymore.

[Michael Stephens]

I’ve found a workaround solution to the problem. If I load the Task Manager and create a task that launches PP5.5 with “highest privileges” and create a shortcut to the task, then PP5.5 loads without any problems. This bypasses needing to launch it as another user and entering the domain admin credentials when I’m logged into the computer using my account.

I’m a little curious as what was changed in version 5.5 as I didn’t have this problems with PP CS5.

[Alex Gerulaitis]

[Todd Kopriva] “If you want this to change, let us know with a feature request.”

Done, thanks. 🙂

Alex (DV411)

[Rosanne Grigoletti]

We have had a similar issue here at our school. Installed Adobe CS6 on our Windows 7 workstations. Allowed the software to run for students via group policies.
Ran fine for faculty and admins. For students, all of CS6 ran with the exception of Premiere Pro. That application would launch and then bomb out with no error message.
After 16 man hours and 4 phone calls to Adobe support, we finally found the solution.

In Group Policies, gave our students unrestricted access to C:\Program Files (x86)\Common Files\Adobe. (We had already given the unrestricted access to the C:\Program Files (x86)\Adobe folder.)
Within this folder, there are many subfolders with executables that apparently run in the background. In all there are 60 executables there.

The way we found it was through and administrative event viewer that referred to updatestarterutilty.exe, switchboard.exe and dynamiclinkmanger.exe being blocked by group policies.

By the way, Adobe support told us that users had to be local admins of the machines. In a high school setting, this is simply not an option. By posting this, I hope to save other school admins the time and frustration that we experienced.