WAN Admin

Raymond Norton

<div>
When you setup LDS did you use local admin as the administrator of the AD LDS instance if so then you will need to change the permissions on the .dit file. as it grants explicit permissions when you do the install.&nbsp;
</div>


<div>
It was indeed necessary to elevate the cmd prompt to get adamsync to run. However, I also needed to add the /creds flag to adamsync to get it to work successfully.
</div>


<div>
<div class="content wysiwyg-content fr-view">
<div><div class="content wysiwyg-content fr-view"><p>I am attempting to give another domain admin permission to run adamsync . The user has been added to the domain admin group and I have given permissions via the adam folder. However, adamsync will not run under that account but does run correctly under the administrator account. I am not seeing any warnings in the security or application logs.</p></div></div>
</div>
</div>



I am attempting to give another domain admin permission to run adamsync . The user has been added to the domain admin group and I have given permissions via the adam folder. However, adamsync will not run under that account but does run correctly under the administrator account. I am not seeing any warnings in the security or application logs.

Need to provide permissions to domain admin to run adamsync

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.