Set-ADDomainMode - ResourceUnavailable

context: i'm making effort learn how perform various operations powershell.

this test network.

two domain controllers:

dc2 - windows 2008 r2

dc5 - windows 2012

++++++++++++++

problem: when attempt increase domain functional level using believe correct ps cmdlet, obtain following error (note: cmdlets run on windows 2012 server):

ps c:\> get-addomain | set-addomainmode -domainmode windows2008domain

confirm [snip] y

set-addomainmode : referral returned server
@ line:1 char:16
+ get-addomain | set-addomainmode -domainmode windows2008domain
+                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + categoryinfo          : resourceunavailable: (dc=mynet,dc=lan:addomain) [set-addomainmode], adreferralexception
    + fullyqualifiederrorid : activedirectoryserver:8235,microsoft.activedirectory.management.commands.setaddomainmode

++++++++++++++++++++++++++++++++++

yet get-addomain cmdlet return name of domain (tried various methods here):

ps c:\> (get-addomain).name
mynet
ps c:\>

*

ps c:\> get-addomain | fl name,domainmode

name       : mynet
domainmode : windows2003domain

++++++++++++

i'm logged in default domain administrator.

d2 (the w2k8r2 dc) holds fsmo roles.

i opened ps run administrator.

after startup (since there transient "waking up" errors), forced replication between domain controllers , stopped , started netlogon service on dc5.

repadmin /showrepl shows successful replication 5 partitions.

dns servers on dc5 are:

10.0.0.12 (dc2)

10.0.0.15 (dc5)

++++++++++++

i can raise dfl using gui without problem (on windows 2012 server):

indeed, dfl raised windows 2008.

i attempted raise dfl windows 2008 r2 using same cmdlet (just in case transient problem solved in meantime - allowed me succeed gui). same result: resourceunavailable.

i tried once before well, left aside couple weeks, thought maybe missing something. had exact same results. raising dfl , ffl gui (either aduc, addt, adac) successful.

i still cannot raise dfl powershell.

can see wrong?

---

please mark helpful if find contribution useful or answer if answer question. encourage me - , others - take time out you.

i able duplicate error purposely targeting dc other pdc.  when targeted pdc, command worked.

next time, try this:

$pdc = (get-addomain).pdcemulator set-addomainmode <domain> -domainmode <newmode> -server $pdc

---

chris ream

- if have found post helpful, or answer, please mark appropriately.  thank you.

Windows Server  >  Directory Services