Anonymous
PowerShell AD Module for Windows Server 2008?
1
PEOPLE
Don, I just read your TechNet Magazine article about AD scripting with PowerShell v.2.0 and the ActiveDirectory module. You state that in order to use this module (and the included AD cmdlets), your client has to run Windows 7 or Windows Server 2008 R2.
Unfortunately, my admin workstation runs Windows Server 2008, and I did not want to rebuild it just to be able to use the new AD cmdlets. I copied the module from one of our W2K8 R2 DCs to my admin machine and tried to use "Import-Module", but this failed. After that, I tried to manually register the required assemblies into the GAC (like Microsoft.ActiveDirectory.Management), and that worked except that my PowerShell did not find any Domain Controller with the AD Web Services running. To solve that, I had to install hotfix 967574, and after that (and a reboot), the ActiveDirectory module runs just fine on my Windows Server 2008 machine - nice!
So - one of my colleagues pointed out that this procedure might violate Microsoft's End User Licence Agreement. Do you have any insight on that?
Related Content
In This Community...
From The Experts Community...
Replies
I don't think MS would really mind, but it's a lot of work and, if you're willing to enable remoting, there's an easier way.
So I'm assuming you're running v2 on your Win2008 machine. It doesn't need anything done to it, but you do need to enable remoting on one of your 2008R2 DCs (Set-WSManQuickConfig or use GPO). Then read this.
The idea is that, as time goes on, there will be more and more modules not installed on your workstation - and they don't need to be. You can run them "locally" by importing them - via remoting - from a machine that does have them. And you can easily set things up so that it happens every time you open the shell on your machine, if that's what you want.
In MS' mind, with this "implicit remoting" trick, you don't need any "server" modules installed on your local computer.
