AD Cmdlets RTM

AD cmdlets are finally gold!

We kind of kept sticking to the fashion of perpetual betas for quite some time now (since the first 1.0 beta released late March through the RC 1.0.5 this fall) and we feel that the product is now feature rich and stable enough for us to drop the beta label.

In the coming weeks I’ll blog more about the cmdlets features and the changes compared to the RC build but for now, here’s a quick list:

User account management:

Set-QADUser Unlock-QADUser Disable-QADUser Deprovision-QADUser Enable-QADUser New-QADUser Get-QADUser

Plus a few common ones:

Move-QADObject Rename-QADObject Remove-QADObject

Group management:

Set-QADGroup Get-QADGroup New-QADGroup Get-QADGroupMember Add-QADGroupMember Remove-QADGroupMember

Move, Rename, Remove obviously also apply:
Move-QADObject Rename-QADObject Remove-QADObject

Managing computer accounts:

Get-QADComputer Set-QADObject Move-QADObject Rename-QADObject Remove-QADObject New-QADObject

OUs and other objects:

Set-QADObject Move-QADObject Rename-QADObject Remove-QADObject New-QADObject Get-QADObject

Fine-Grained Password Policies:

New-QADPasswordSettingsObject Get-QADPasswordSettingsObject Add-QADPasswordSettingsObjectAppliesTo Remove-QADPasswordSettingsObjectAppliesTo

Selecting DC/domain/ADAM instance/ARS proxy or supplying alternate credentials:

Connect-QADService Disconnect-QADService

Auxiliary cmdlets to make life easier:

Convert-QADAttributeValue Set-QADPSSnapinSettings Set-QADPSSnapinSettings

It is more or less the same list we had in RC (with one new cmdlet and a few improvements and bugfixes in the others – and finally full PowerShell v2 compatibility ;)), but the EULA change alone (not a beta any more!) is probably worth making the upgrade all by itself!

And did I say that despite the RTM status AD cmdlets still remain free? Any reason for not going to the site right away and getting them? 😉

10 Responses to “AD Cmdlets RTM”

Feed for this Entry Trackback Address

1 BSonPosh December 20, 2007 at 3:20 pm

Download is still ReleaseCandidate.
ManagementShellforActiveDirectoryReleaseCandidate_106.msi

2 dmitrysotnikov December 20, 2007 at 3:27 pm

Oops, looks like the web guys messed up with the filename (changed the version but left the rest of the name from 1.0.5) – I’ll ping them right away so they rename the file. Thanks for reporting the issue!

3 matthew g December 27, 2007 at 8:03 pm

thanks, guys. I continue to use this all the time and it rocks!

4 Andy December 29, 2007 at 12:21 pm

Just stumbled across this after getting powergui (referred from technet magazine). My initial comment is that it seems weird that powergui requires this activeroles to be installed BEFORE powergui is installed if AD is needed.
The end user interface would be nicer if the program detected that ActiveRoles wasn’t installed and then either offered to download and install it or at least give a clickable link to the download page – as it is the dialog box is not clickable so you have to type it in by hand, download the file, cancel the powergui installation, install ActiveRoles then install Powergui – a bit messy.

5 dmitrysotnikov December 29, 2007 at 7:00 pm

Andy,

I agree. All good points. There’s definitely room for improvement here and we’ll try to make the experience more streamlined in subsequent releases.

Also, please consider using PowerGUI.org discussion forums next time you have a change request like that: http://powergui.org/forumindex.jspa?categoryID=55 – this would ensure that the whole dev team sees the request and it gets added to our CR tracking system.

No need to do that for this one. I’ll add it to the system manually – as I mentioned I think it makes total sense, so thanks for reporting!

Dmitry