phildyer Posted May 27, 2016 Posted May 27, 2016 Hi all Does anyone have a link to the quest AD cmdlets? I've looked everywhere but I can't find anything, any help would be much appreciated. Many thanks Phil
HPlum78 Posted May 27, 2016 Posted May 27, 2016 Anyhow the reason I asked is because Dell took them over and changed it to this Active Directory User Management | Dell Software
phildyer Posted May 27, 2016 Author Posted May 27, 2016 I've been following a really good tutorial on how to audit AD with machine serial numbers & populate the MDT database from it: https://deployhappiness.com/importing-computers-into-the-mdt-database-with-powershell/ The powershell script they've supplied uses QAD however I'm pretty poor with powershell so wouldn't really know what to do to make it work.
phildyer Posted May 27, 2016 Author Posted May 27, 2016 If anyone is curious I've just found a zip here: Windows: Quest AD PowerShell cmdlets | Mohammed Wasay
jinnantonnixx Posted May 27, 2016 Posted May 27, 2016 (edited) This is timely. I've got a boatload of custom attributes in AD which I read and set using a custom class I modified in .Net. I need to do some ad-hoc tasks in Powershell rather than compiled code, so I thought that the Get-ADUser cmdlet from Microsoft would work, but I was totally wrong. It can't see custom attributes. End of story. It's really bad that you have to hunt around random download sites to find tools that Microsoft should have written correctly in the first place. However, the link for the free Quest tools is dead. Edited May 27, 2016 by jinnantonnixx
jinnantonnixx Posted May 27, 2016 Posted May 27, 2016 (edited) I've found that it's possible to set the value of a custom attribute in Powershell. To change a user's favourite curry (assuming you have added a custom attribute to store such a critical item), you can do this: Set-ADUser john.smith –replace @{favouriteCurry=”Dhansak"} You call also use the -remove operator to remove a value, and the -add operator to set a value. I still can't figure out a way of reading the damned values in Powershell, but it's better than nothing I suppose. Edited May 27, 2016 by jinnantonnixx
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now