zsere86

Okay, I think we're misunderstanding each other. I've already added the workstations to the Nakivo console. I used an account with domain-level administrator privileges for this. Now I need to limit this account to communication between the Nakivo server and the workstations. Thanks for the tip that the account must have "Log on as a batch job" permissions. My question was more about best practices for configuring such an account for communication between the Nakivo server and a workstation running the "transporter" backup agent. Is there any way to prevent Nakivo from treating workstation unavailability as a problem? The point is that workstations are only available during office hours on workdays. And the console shows hundreds of host unavailability issues after the weekend. While this is generally correct, it's a bit irritating and blurs the picture of the network situation?

I'm currently implementing NAKIVO Backup & Replication for Physical Workstations on Windows. I'm looking for a user configuration solution for installing and managing the NAKIVO agent on a Windows workstation. I've implemented a solution that involves creating a "nakivo" account in the Active Directory domain with minimal privileges and a 25-character password based on a generator consisting of lowercase and uppercase letters, numbers, and special characters. Cyclic password changes have been disabled in accordance with the policy for this account. Using Group Policy, I've granted local administrator privileges on workstations for this account and disabled the ability to log in via Terminal Services and locally. Is there another configuration option based on a more secure solution, such as a gMSA account?