A user asked how to add a computer in a different AD forest using the ControlUp Monitor. The EUC-Sync script, which can add machines is available, but the DNS records must be recognized. Additionally, the AD Connection needs to be configured in ControlUp Monitor settings in the Domain Identities section, which is not tied to the user logged in to the console.
Read the entire ‘Adding Computers from Different AD Forests with ControlUp Monitor’ thread below:
Hi,
I’m running a scheduled task as system on my monitor to automatically add computers to my org.
The VM the monitor is installed on is in a different AD forest than the VM i want to add. I have added VM’s from another forest with the task running as system, but not able to add from these particular new forests. It’s throwing "The relevant AD Connection must be configured in the ControlUp Monitor". Is this connection user specific? How do I enable the AD Connection for the system account?
In Monitor Settings you can co figure AD Connections. And if you‘re able to reach the machines in the other AD forest via DNS you should be good to go.
Have you seen the EUC-Sync script which will add machines for you?
There is also a sync script for Hypervisor-Connection available…
indeed most probably the dns records are not being recognized
I can use the Get-ADComputer cmdlet to read the computer info of the VM i want to add from the monitor.
with the ad sync script you can select a different domain https://support.controlup.com/docs/active-directory-organizational-unit-sync-with-controlup-console-tree#input-parameters
I can add computers from forest1.local, but not forest2.local. In my current powershell context, I can both Get-ADComputer on both computer objects, and I can ping them using DNS.
Make sure there’s an ad object for both int he monitor config like @member said
There is – but are AD Connections somehow tied to the user logged in to the console? So if I set up a connection with one user, another doesn’t automatically have the same?
Not in this context. The add-cucomputer cmdlet is looking for the ad connection configured under monitor settings > domain identities.
Do note that the console also has its own private ad connections. That’s not what we are referring to. It has to be under monitor settings > domain identities and then the top half.
ahhhh
Thank you, that was the issue.
Continue reading and comment on the thread ‘Adding Computers from Different AD Forests with ControlUp Monitor’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers