Capture 1 v4 in a Windows Server 2003 domain

smartyn

• 2007年12月28日 01:17

Does anyone know how to use Capture 1 v4 in a Windows 2003 Server Domain, as a regular user? C1 version v3.7.x was no problem, v 4b2 was no problem, but C1 v4 fails for any logon except as either a domain admin or a local admin. I have granted full access control to all Phaseone folders that I can find, but it still fails for a normal user. Every other piece of software we use works perfectly for normal users (Adobe CS3 suites, CS2, Lightroom - all enterprise licenses).
Because of network security issues and best security practices recommended by Microsoft, admin rights are not acceptable for normal users.
I opened a support case, and the reply was: this is the way the Program was designed.
Could this be related to the licensing engine Phase One uses?
Any thought would be useful.

0

• 

  Photographicon

  • 2007年12月28日 02:16

  Can you be more preceise about the way in which it fails...? What error messages, etc.
  
  Windows admin accounts generally differ from standard users accounts through the Permissions (to access file system objects) and Rights (to perform certain tasks) granted to them. You say you have given standard users the correct Permissions for the Phaseone folders (have you tested these?)... perhaps you also need to grant a specific Right (via the Domain Admin tool)? You can experiment by creating a new user group to which you can assign the same Rights as the Administrators group... if CO works for users in this group, then progressively remove Rights until you find the preceise one(s) required.

  0
• 

  Paul Steunebrink

  • 2007年12月28日 05:22

  Initial and limited testing I did revealed that the user logged onto the workstation (whether in a domain or a workgroup) at least needs Power User rights on XP Pro for CO4 to run. For me this was the same as with CO since v1.x.
  When starting CO4 with only User rights level access, the applications does not start but the Capture One Crash Reporter dialog shows up with an empty report(!).
  
  I have to dive deeper into it, but I suspect it is due to CO's type of access to its program files folder and/or registry keys in Local Machine (or outside the Current User part).
  
  Phase One has not implemented the Win32 application specifications properly at all in the past, in that it separates the computer part (read permission required) from the user part (change permissions allowed). Moving the work and preview files from the program folder to the user's folder in CO4 was a move in the right direction. However, there is still some work to be done for which PO does not show great enthusiasm to my regret.
  
  It is obvious that working with high privileges granted to a user today introduces high risks due to a potential user failure and threats by malicious code. Stating that Admin level access is required is not acceptable both for private and corporate environments. The fact that this forum is not flooded with complaints in this respect confirms my fear that also from the side of computer users the awareness regarding the risks is very low (in plain English: most users still work on their computer and access the internet with Administrator level privileges; they don't have a separate low privilege level user account on their computer to do their daily work with).
  
  Have a nice day.

  0

投稿コメントは受け付けていません。