There was a serious problem deploying the controller to SERVERNAME: Insufficient Privilege

This article discusses information regarding the following error message that may appear when performing any live conversion. This error occurs on step 6.1 “Installing Controller on Source Server”

 ERROR: There was a serious problem deploying the controller to <SERVERNAME> : Insufficient Privilege

ERROR: There was a serious problem deploying the controller to <SERVERNAME> : Insufficient Privilege

When performing any live conversion the above error appears at step 6.1 on the PlateSpin Server. In addition there will be an EventID 577 in the security event log on the source server where the live conversion controller is being installed.

Source: Security
Type: Failure
Category: Privilege Use
Event ID: 577
Description:
Privileged Service Called:

Server: Security
Service: -
Primary User Name: PrimaryUserName
Primary Domain: PrimaryDomain
Primary Logon ID: PrimaryLogonID
Client User Name: ClientUserName
Client Domain: ClientDomain
Client Logon ID: ClientLogonID
Privileges: SeIncreaseBasePriorityPrivilege

Solution:1  Modify the Bypass Traverse Checking Local Security Policy

Step 1: Click Start, Programs, Administrative Tools, Local Security Policy.

Step 2: Expand Security Settings, Local Policies, User Rights Assignment.

Step 3: Double-click on Bypass Traverse Checking in the right-window pane

Step 4: Click Add to insert the appropriate accounts (in this case we added Authenticated Users).

Step 4: Refresh the policy immediately using GPUPDATE /FORCE (for Windows 2003/XP) or secedit /refreshpolicy machine_policy /enforce  (for Windows 2000)

Solution:2  Modify the Replace A Process Level Token Local Security Policy

Step 1: Click Start, Programs, Administrative Tools, Local Security Policy.

Step 2: Expand Security Settings, Local Policies, User Rights Assignment.

Step 3: Double-click on Replace A Process Level Token in the right-window pane

Step 4: Add the NETWORK SERVICE and LOCAL SERVICE accounts

Step 5: Refresh the policy immediately using GPUPDATE /FORCE (for Windows 2003/XP) or secedit /refreshpolicy machine_policy /enforce  (for Windows 2000)

These 2 policy modifications will resolve the issue as this policy allows the Network Service to perform the correct WMI call to remotely install the PlateSpin Controller Package.  This can be an issue when a domain environment is highly locked down and secured.