How To Change Active Directory Computers OU Display Name
I am running Active Directory using AWS Directory Service, specifically SimpleAD.
The challenge I'm having is that the Active Directory OU for Computers is displaying an old computer name.
In the screenshot I've taken, I've first highlighted the OU Name, in this case "DB-PRIVATE". Yes, this computer was renamed that, but it's not the current name.
The "real" name of this computer is ESROM, as demonstrated on the "General" -> "DNS Name:" section of the screenshot. I've noted this in green.
However, what is displaying is the Canonical Name of the Object, as demonstrated in the "Objects" -> "Canonical name" section of the screenshot. This is noted in red.
I've unsuccessfully attempted this change with Netdom.
Any suggestions how I can get Active Directory to display the correct name of the computer?
Thanks!
The challenge I'm having is that the Active Directory OU for Computers is displaying an old computer name.
In the screenshot I've taken, I've first highlighted the OU Name, in this case "DB-PRIVATE". Yes, this computer was renamed that, but it's not the current name.
The "real" name of this computer is ESROM, as demonstrated on the "General" -> "DNS Name:" section of the screenshot. I've noted this in green.
However, what is displaying is the Canonical Name of the Object, as demonstrated in the "Objects" -> "Canonical name" section of the screenshot. This is noted in red.
I've unsuccessfully attempted this change with Netdom.
Any suggestions how I can get Active Directory to display the correct name of the computer?
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What version of powershell are you using. Install windows management framework 5 on your server.
ref link:
https://www.microsoft.com/en-us/download/details.aspx?id=50395
ref link:
https://www.microsoft.com/en-us/download/details.aspx?id=50395
ASKER
Thank you, I am running Powershell 4 and it appears that Windows Management Framework is already installed on the Server. I did download the file from that page but when I ran the MSI file it stated that this update didn't apply for this system (Win 2k12r2 Standard).
Maybe I'm getting the parameter wrong. Do you have any Microsoft documentation for "-CaonicolName", or even "-CanonicalName"? I cannot seem to find that anywhere.
Thanks for all your help. This has been great.
Maybe I'm getting the parameter wrong. Do you have any Microsoft documentation for "-CaonicolName", or even "-CanonicalName"? I cannot seem to find that anywhere.
Thanks for all your help. This has been great.
send me a screenshot of the exact command you ran
also... for the computer in question run this command on your server and let me know if CanonicalName comes up in its properties
Get-ADcomputer computername -proprerties *
also... for the computer in question run this command on your server and let me know if CanonicalName comes up in its properties
Get-ADcomputer computername -proprerties *
Did you run this install?
W2K12-KB3134759-x64.msu
W2K12-KB3134759-x64.msu
ASKER
Thank you, Foxluv. I was able to install WMF 5.0 RTM on the machine in question. After the required restart and attempting to invoke "Import-Module ActiveDirectory" I get the following error:
WARNING: Error initializing default drive: 'Unable to find a default server with Active Directory Web Services running.'.
This might have something to do with SimpleAD and the way AWS runs the Domain Controllers. I have since escalated via their forum with the following question:
https://forums.aws.amazon.com/thread.jspa?threadID=236283
I will be monitoring that as well to make sure that AD is setup correctly. All other functionality is working (e.g. Active Directory Users and Computers, logging in and out of servers with AD credentials), so now I'm a little more stumped.
Thank you again for your help.
WARNING: Error initializing default drive: 'Unable to find a default server with Active Directory Web Services running.'.
This might have something to do with SimpleAD and the way AWS runs the Domain Controllers. I have since escalated via their forum with the following question:
https://forums.aws.amazon.com/thread.jspa?threadID=236283
I will be monitoring that as well to make sure that AD is setup correctly. All other functionality is working (e.g. Active Directory Users and Computers, logging in and out of servers with AD credentials), so now I'm a little more stumped.
Thank you again for your help.
did you install the windows managment framework on a domain controller or a workstation? Did you right click powershell (run as administrator) before you attempted to do any commands?
In the AD administrative Center right-click local>change domain controller and see if it has a list with your domain controller , then connect to it
ASKER
Thanks Foxluv - I installed the Windows Management Framework on a DC (or, rather, the EC2 instance I have connected to SimpleAD). I did run Powershell as an Administrator before attempting all commands.
In the AD Administrative Center, I went to change the Domain Controller and it did NOT propagate a list. In fact, it actually gave an error "Cannot find an available server in the Domain". This is leading me to believe that it's perhaps a higher-level problem. (This is what I referenced in the AWS Developer Forum post that I gave the link to before). I have attached a screenshot for a visual.
Thanks!
In the AD Administrative Center, I went to change the Domain Controller and it did NOT propagate a list. In fact, it actually gave an error "Cannot find an available server in the Domain". This is leading me to believe that it's perhaps a higher-level problem. (This is what I referenced in the AWS Developer Forum post that I gave the link to before). I have attached a screenshot for a visual.
Thanks!
What was your final fix on this issue?
ASKER
Hey Foxluv - There was no final fix on this issue. I was able to determine that this is a constraint due to using the AWS SimpleAD Directory Service. I had no idea that this service lacked "Active Directory Web Services" and that it would cause such suppression. I used your described method flawlessly in a co-located AD environment and it worked great. Thanks for your help.
Ok great.
ASKER
This is a point in the right direction, thank you for that. :-)