Wednesday, October 28, 2015

Allowing Non Server Admins to Build Pharos Printing Packages

In our environment, our application administrators are not always the same people as our server administrators. This led to a problem with Pharos, a product we use for our pay for print system. To build or rebuild a package of printers in Pharos, the user had to also be an administrator on the server. So I broke out procmon and got down to figuring out what type of access a user would need to be able to build packages. It turned out to be fairly simple. I created an AD group, put the Pharos Administrators in the new group and gave that group:

Modify access to C:\inetpub\wwwroot\Uniprint
Full control on C:\Program Files (x86)\Pharos\Bin

In the server's registry, gave the group:
Full Control on HKLM\Software\Wow6432Node\Pharos
Full Control on HKLM\System\CurrentControlSet\Services\WinSock2\Parameters

No comments:

Post a Comment