After changing my computer description within windows and restarting the machine, the description field in active directory for that particular machine will not populate? Any tip/idea of what the problem may be?
Windows – Syncing Computer Description With Active Directory Description Field
active-directorywindows
Related Solutions
Likewise-Open makes integrating Linux clients and member servers into an existing Active Directory fairly simple. We use it on a couple of Ubuntu servers for NAS -- just upgraded to Jaunty and it works great, though we stuck with the likewise-open (4.x) rather than likewise-open5 package, as there are some changes in the newest version which we haven't figured out completely. In particular, Likewise takes some of the overhead and configuration out of the krb5/pam/winbind/samba setup. Supposedly its authentication mechanism is more efficient too, but this isn't something that we've really noticed.
Also, the long-awaited Samba 4 is supposed to be coming in the not-too-distant future, and promises a number of interoperability improvements such as Group Policy support, might be worth staying tuned.
Related Topic
- Active Directory Naming – Best Practices for Windows Active Directory Naming
- Windows – See network computer description in Explorer
- Active Directory Domain Services – What It Is and How It Works
- Locating services running as an Active Directory user account
- Windows – Can a user see the Active Directory computer description in the Windows network browser
Best Answer
It's by design. The description box that you find in
Control Panel > Systemis for use by the local computer only. It is not meant to sync automatically with AD.You could synchronize them with some sort of script if you wanted to.
If you're actually on the computer you want to get the local computer's description for, omit the
-ComputerNameparameter fromGet-WMIObject. That's for remote systems.)To make this work, you'd need AD Web Services running on your domain controller (2008 R2 and above,) you'd need the AD Powershell cmdlets on your client, (the Remote Server Administration Tools come with these) and of course write permission to actually write to the description LDAP attribute of the desired computer object in AD.