I have a client that purchased a LoB application and we installed it on their 2nd AD server. The server is not doing much besides being an additional AD server so it seemed like a good home for the software. The software company confirmed that the server being a DC should not be an issue. Now we find out that the users will need to connect and run certain tasks locally on the machine. This means setting up RDP access to that server. From my understanding I have to make the user a member of the group "Administrators" in order for this to work. I tried just adding them to "Remote Desktop Users" and that didn't fix it. Since the server is a DC there is no "local" administrators group for me to add them to. This results in them being added to the domain "Administrators" group. Which is NOT what I want. Is there another way around this? I don't mind the user having admin access to the server (although not ideal) but I don't want them being an administrator for the domain. Thanks in advance for your advice.
Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.
Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space.
Verify that the path to the shared storage is valid and that data can be written to that location:…
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention.
Multiple USB devices need t…