The reason for the error is that in ADFS
2012 the cmdlets are surfaced by a module instead of a snapin, and the MSOnline
cmdlets are hardcoded to load the old snapin which was available in ADFS 2.0.
You can work around this issue by creating your own reference in
the registry to the ADFS module as a snapin.
To do so, copy and paste the items below into notepad and save them as a .reg file and then execute.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Adfs.PowerShell]
"ApplicationBase"="C:\\Windows\\ADFS"
"Version"="6.2.9200.0"
"AssemblyName"="Microsoft.IdentityServer.PowerShell, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
"Description"="This powershell snap-in contains cmdlets used to manage Microsoft Identity Server resources."
"PowerShellVersion"="1.0"
"ModuleName"="C:\\Windows\\ADFS\\Microsoft.IdentityServer.PowerShell.dll"
"Vendor"="Microsoft"
You can now use Windows Server 2012 for Single Sign on to Office365 :)
Please note : This solution is not supported by Microsoft. It is my understanding that a new Microsoft online services powershell module will be available for download when the new Office365 is generally available in Q1 of next year.
Please note : This solution is not supported by Microsoft. It is my understanding that a new Microsoft online services powershell module will be available for download when the new Office365 is generally available in Q1 of next year.
January 11th 2013,
ReplyDeleteStill no fix for this issue. Thanks a lot!
Your welcome :)
ReplyDeleteHi Sean
ReplyDeleteJust a general question about ADFS on Windows Server 2012.
Can ADFS on Windows 2012 co-exist as a member server in a Windows 2003 SP1 domain