I was in the process of attempting to enable the option AD Recycle bin feature via powershell. From what I've read from microsoft, the domain/forest functional level must be 2008 R2, which ours is.
Next, you must import the AD module into powershell while connected to either the Domain Naming Master FSMO role holder, or the Schema Master FSMO role holder which I've done without error using the following command:
[code]import-module activedirectory[/code]
Next I run the command to enable to feature (obviously subbing in my domain name for contoso):
[code]Enable-ADOptionalFeature –Identity "CN=Recycle Bin Feature,CN=Optional Features,CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=contoso,DC=com" –Scope ForestOrConfigurationSet –Target ‘contoso.com’[/code]
So far, so good. I receive the expected confirmation prompt of:
[code]WARNING: Enabling 'Recycle Bin Feature' on 'CN=Partitions,CN=Configuration,DC=contoso,DC=com' is an
irreversible action! You will not be able to disable 'Recycle Bin Feature' on
'CN=Partitions,CN=Configuration,DC=contoso,DC=com' if you proceed.
Confirm
Are you sure you want to perform this action?
Performing operation "Enable" on Target "Recycle Bin Feature".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"):
[/code]
Upon responding 'Y', I get the dreaded error:
[code]Enable-ADOptionalFeature : A referral was returned from the server
At line:1 char:25
+ Enable-ADOptionalFeature <<<< -Identity "CN=Recycle Bin Feature,CN=Optional Features,CN=Directory Service,CN=Windows
NT,CN=Services,CN=Configuration,DC=contoso,DC=com" -Scope ForestOrConfigurationSet -Target `contoso.co
m'
+ CategoryInfo : NotSpecified: (CN=Recycle Bin ...tsbangor,DC=com:ADOptionalFeature) [Enable-ADOptionalFe
ature], ADException
+ FullyQualifiedErrorId : A referral was returned from the server,Microsoft.ActiveDirectory.Management.Commands.En
ableADOptionalFeature[/code]
Now based on research, I should be able to run this command from either my Domain Naming Master FSMO role holder or the Schema Master FSMO role holder successfully, but I receive the same error from both. Please note, we're trying to avoid moving the Schema Master role as this is a production environment. Any workarounds available for this?