ADMGS - How to install on Server 2003 and Server 2008
From someone who has done a lot of AD related scripting in powershell v1, it has taken me a while to get to grips with using the new AD cmdlets in PowerShell v2. Needless to say, I have started 'dipping my toe' into the vast 'sea of cmdlets' now available and am finding them quite useful. So much so, that enabling the ability to use the cmdlets in my older domains has become essential. I no longer want to have to write v1 and v2 scripts, or more specifically, ad cmdlet and non-ad-cmdlet enabled scripts.
Here enters the 'Active Directory Management Gateway Service' .This provides the connectivity for the AD-cmdlets to communicate with a domain controller in your domain.
Pre-requisites
For a small installer, this guy need a fair few prerequisites - each OS version being slightly different.
Windows 2008 (tested on 32bit)
It is best that you have SP2 installed as there is an issue with Windows 7 clients and 2008 DCs. There is a hotfix but you have to request it, but it is included in Windows 2008 SP2
General installs
What ever platform you are using, these are required :
The only 2003 specific patch required is 969429, which is a request by email patch. Don't be put off by this as I got the link emailed to me very quickly.
Once you have completed all these tasks, install the applicable version of the gateway
Using the gateway.
My R2 forest is single domain, so I have not given a second thought to how I access resources in other domains using the AD cmdlets. I also have take for granted that the cmdlets just work. I am, however, fortunate enough to have an R2 utility server to script on as well as R2 DC's.
The biggest thing here is the AD cmdlets only run on Windows 2008 R2 or Windows 7. The gateway will run on the older OS's, but the cmdlets themselves do not.
The second thing is that you need a gateway server in each domain. I ran this in my test forest (from the root domain)
For the future
I can see use for the gateway, as long as I can get the required R2 utility servers in the forests to run the scripts. I would probably (on the said R2 util server) setup the profile to create variables for each domain gateway server. This would not only make the scripting easier and more uniform, if I had to move my gateway server, I would change only the profile rather than all my scripts.
This being my research and testing, I am about to deploy this in my environments (this time 64 bit). I'll report on the experience once I am up and running.
From someone who has done a lot of AD related scripting in powershell v1, it has taken me a while to get to grips with using the new AD cmdlets in PowerShell v2. Needless to say, I have started 'dipping my toe' into the vast 'sea of cmdlets' now available and am finding them quite useful. So much so, that enabling the ability to use the cmdlets in my older domains has become essential. I no longer want to have to write v1 and v2 scripts, or more specifically, ad cmdlet and non-ad-cmdlet enabled scripts.
Here enters the 'Active Directory Management Gateway Service' .This provides the connectivity for the AD-cmdlets to communicate with a domain controller in your domain.
Pre-requisites
For a small installer, this guy need a fair few prerequisites - each OS version being slightly different.
Windows 2008 (tested on 32bit)
It is best that you have SP2 installed as there is an issue with Windows 7 clients and 2008 DCs. There is a hotfix but you have to request it, but it is included in Windows 2008 SP2
General installs
What ever platform you are using, these are required :
- Domain controller - can only run on a DC!
- .net 3.5 SP1
- .net hotfix 969116
The only 2003 specific patch required is 969429, which is a request by email patch. Don't be put off by this as I got the link emailed to me very quickly.
Once you have completed all these tasks, install the applicable version of the gateway
Using the gateway.
My R2 forest is single domain, so I have not given a second thought to how I access resources in other domains using the AD cmdlets. I also have take for granted that the cmdlets just work. I am, however, fortunate enough to have an R2 utility server to script on as well as R2 DC's.
The biggest thing here is the AD cmdlets only run on Windows 2008 R2 or Windows 7. The gateway will run on the older OS's, but the cmdlets themselves do not.
The second thing is that you need a gateway server in each domain. I ran this in my test forest (from the root domain)
get-aduser -SearchBase "dc=child,dc=test2003,dc=com" -filter {name -like "*"}and got this back :
The correct command is :
Get-ADUser : A referral was returned from the server
At line:1 char:11
+ get-aduser <<<< -SearchBase "dc=child,dc=test2003,dc=com" -filter {name -like "*"} + CategoryInfo : ResourceUnavailable: (:) [Get-ADUser], ADReferralException + FullyQualifiedErrorId : A referral was returned from the server,Microsoft.ActiveDirectory.Management.Commands.Ge tADUser
get-aduser -Server dc2.child.test2003.com -filter {name -like "*"}...where server is the gatway server of that domain.
For the future
I can see use for the gateway, as long as I can get the required R2 utility servers in the forests to run the scripts. I would probably (on the said R2 util server) setup the profile to create variables for each domain gateway server. This would not only make the scripting easier and more uniform, if I had to move my gateway server, I would change only the profile rather than all my scripts.
This being my research and testing, I am about to deploy this in my environments (this time 64 bit). I'll report on the experience once I am up and running.
Comments
Post a Comment