Adam's AD Admin

AADSites - Update 2 This is my second update / bug fix for my module AADSites.  The latest release can be downloaded  here . For more info on the module see here . This is, in real terms, quite a big update!  Not for those who are using MSAD management pack, for those who use quest tools!  This update adds quest support - just open up your quest powershell console and load the AADSites module and it will find the quest snappin. Thanks goes to Shay for taking the time to give me feedback on this module! As always please post any feedback to this page! In version 0.92, the following has been changed : Fixed Issue in set-AADSitelink where a null value caused an error Added Quest tools are now supported! Updated As quest tools are now supported, either MSAD or the quest tools need to be loaded before this module is loaded. If you have both loaded, the MSAD module will be used.

UPDATED: now supports Quest tools see v0.92 update for details It's been a while since I have put anything on here, as noted by a few of my colleagues. I have been busy developing various ideas in PowerShell, and generally pulling together all the scripts, functions, features, techniques etc that I have learnt over the past few years.  This, and raising an ever growning young family! It has been a very exciting journey which is far from over, but I suppose I have come to a point where I feel I have something useful to give back. In my quest to automate AD management (one of the ideas I have been working on), I found that there isn't much in the way of Site / Subnet / Site link management in PowerShell. True, these are just objects in AD and can be referenced by get-ADobject or by the [ADSI] shortcut, or even the quest AD management tools, but formatting the configuration naming context with sub OU's is a pain - if you actually know that this is where sites and servic...

It has been a while since I have posted anything, mainly due to changing jobs and the time spent with my ever growing family.  This is not to say that I have not been keeping up with scripting development...far from it! I had an interesting one today where a request came in for the following : “I need the bitlocker recovery password for a deleted computer object” As my current environment does not support the AD cmdlets, I looked to the quest tool set and was pleasantly surprised. Here is what I came up with, commented in line... #for easy editing, define the computername that has been deleted $compname = "ABC12345" #search AD including Deleted objects (-tombstone) for recovery information objects and filter where the last known parent contains the computer name. Then just return the password $recoverykey = Get-QADObject -Tombstone -Type "msFVE-RecoveryInformation" -SizeLimit 0 -Includedproperties msFVE-RecoveryPassword -SearchRoot "CN=Deleted Objects...