Exchange 2016 install - permission error

Question

_{Thursday, March 10, 2016 4:21 PM}

Hello all,

I won't go through the entire background to this but start from the point that I have a "clean" domain that has no Exchange loaded. Installing Exchange 2016 from the GUI setup, and get:

Error:
The following error was generated when "$error.Clear();
*    Set-LocalPermissions*

" was run: "System.Security.AccessControl.PrivilegeNotHeldException: The process does not possess the 'SeSecurityPrivilege' privilege which is required for this operation.
*   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)*
*   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)*
*   at Microsoft.Exchange.Management.Deployment.SetLocalPermissions.InternalProcessRecord()*
*   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()*
*   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".*

I did see a similar issue on googling it, and oddly I did actually have a default domain policy setting in place - the "Manage auditing and security log" was set to some specific machines, but now it's back to the default not defined setting. The DC has been gpupdate/force and rebooted.

I am installing this as myself, and I am every level of admin that I can be - schema, enterprise and domain etc. The actual domain "Administrator" account is never used and is disabled.

Any pointers as to what to look for would be much appreciated.

All replies (3)

_{Friday, March 11, 2016 9:41 AM ✅Answered | 1 vote}

Thanks for both replies. It turns out that I had indeed fixed the problem by removing the settings in Manage security settings, but hadn't rebooted the server. I rebooted both the AD main server and also the Exchange server, and it installed OK. I will close this now

_{Thursday, March 10, 2016 5:17 PM}

Hello,

Post here an Exchange setup log located in <system drive>\ExchangeSetupLogs\ExchangeSetup.log as a plain text. It should contain an additional information about the issue.

My LinkedIn profile

_{Friday, March 11, 2016 7:39 AM | 1 vote}

Hi Robatwork，

Base on my search, I found another reason may cause this issue also, you can refer to the following option and check if any helps:

Found that the exchange servers group was not added to the default policy.
Manage auditing and security logs.
Also the exchange server was not a member of the exchange servers group.
Added the same.
Checked ad replication and then it was working.

Hope this helps!

Best regards,

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Niko Cheng
TechNet Community Support