AD Config - Soverance/Exodus GitHub Wiki

Create and apply an Exodus AD Security Group to the Domain

For many features to of the Exodus Data Service to function, the computer accounts interacting with Exodus require Full Control permission to access the designated network shares that Exodus will write data to. To ensure all machines which interact with the Exodus service will have the appropriate permission level, you will need to create and apply a new security group to manage these permissions.

Create a new Active Directory Security Group

You can create this group in any OU you wish to best organize for your domain. Add to the group every computer account which will interact with the Exodus service - this includes the Exodus server itself, the Hyper-V host you plan to export, all virtual machines you plan to export, and any destination file servers that will be written to.

Grant permissions to the security group

Any network shares that will be written to by the Exodus service must have their permissions modified to grant Full Control access to the newly created security group. Ensure that this permission change is applied to both the File Share, as well as the NTFS folder-level security permissions.

Update the Group Policy on each computer in the group

Active Directory will generally take care of this automatically over time, but you can force the issue in a new PowerShell window using the "gpupdate /force" commands and/or a machine reboot. View the status of a machine's currently applied group policies using the "gpresult /r /scope computer" command.