Eu tenho dois domínios que estou tentando compartilhar informações de disponibilidade de calendário entre a federação. SiteA é uma implantação no local do Exchange 2010 SP2. O SiteB é uma implantação do Office 365 Enterprise.
Ambas as organizações são federadas por meio do gateway MSFT.
O compartilhamento funciona do SiteA para o SiteB, o que significa que um usuário no SiteB pode solicitar acesso a um usuário no SiteA e visualizar o calendário.
O compartilhamento não funciona do SiteB para o SiteA.
A execução de Test-OrganizationRelationship mostra o seguinte:
[PS] C:\Windows\system32>Test-OrganizationRelationship -UserIdentity [email protected] -Identity siteB -verbose
VERBOSE: [20:24:06.006 GMT] Test-OrganizationRelationship : Active Directory session settings for
'Test-OrganizationRelationship' are: View Entire Forest: 'False', Default Scope: 'mydomain', Configuration
Domain Controller: 'mydc', Preferred Global Catalog: 'mygc', Preferred
Domain Controllers: '{ mydc1, mydc2 }'
VERBOSE: [20:24:06.006 GMT] Test-OrganizationRelationship : Runspace context: Executing user:
[email protected], Executing user organization: , Current organization: , RBAC-enabled: Enabled.
VERBOSE: [20:24:06.006 GMT] Test-OrganizationRelationship : Beginning processing &
VERBOSE: [20:24:06.006 GMT] Test-OrganizationRelationship : Instantiating handler with index 0 for cmdlet extension
agent "Admin Audit Log Agent".
VERBOSE: [20:24:06.037 GMT] Test-OrganizationRelationship : Current ScopeSet is: { Recipient Read Scope: {{, }},
Recipient Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive
Recipient Scope(s): {}, Exclusive Configuration Scope(s): {} }
VERBOSE: [20:24:06.037 GMT] Test-OrganizationRelationship : Searching objects "me" of type "ADUser" under the root
"$null".
VERBOSE: [20:24:06.037 GMT] Test-OrganizationRelationship : Previous operation run on global catalog server
'mygc'.
VERBOSE: [20:24:06.037 GMT] Test-OrganizationRelationship : Searching objects "siteB" of type "OrganizationRelationship"
under the root "$null".
VERBOSE: [20:24:06.037 GMT] Test-OrganizationRelationship : Previous operation run on domain controller
'mydc'.
VERBOSE: Test that organization relationships are properly configured.
VERBOSE: [20:24:06.053 GMT] Test-OrganizationRelationship : Resolved current organization: .
VERBOSE: [20:24:06.053 GMT] Test-OrganizationRelationship : Calling the Microsoft Exchange Autodiscover service for the
remote federation information.
VERBOSE: [20:24:09.084 GMT] Test-OrganizationRelationship : The Autodiscover call succeeded for the following URL:
https://pod51041.outlook.com/autodiscover/autodiscover.svc.
VERBOSE: [20:24:09.084 GMT] Test-OrganizationRelationship : The Autodiscover call succeeded for the following URL:
https://pod51041.outlook.com/autodiscover/autodiscover.svc.
VERBOSE: [20:24:09.084 GMT] Test-OrganizationRelationship : The Autodiscover call succeeded for the following URL:
https://pod51041.outlook.com/autodiscover/autodiscover.svc.
VERBOSE: [20:24:09.084 GMT] Test-OrganizationRelationship : The Autodiscover call succeeded for the following URL:
https://pod51041.outlook.com/autodiscover/autodiscover.svc.
VERBOSE: [20:24:09.084 GMT] Test-OrganizationRelationship : Generating delegation token for user me@siteA for
application http://outlook.com/.
VERBOSE: [20:24:09.366 GMT] Test-OrganizationRelationship : The delegation token was successfully generated.
VERBOSE: [20:24:09.366 GMT] Test-OrganizationRelationship : The Microsoft Exchange Autodiscover service is being called
to determine the remote organization relationship settings.
VERBOSE: [20:24:09.366 GMT] Test-OrganizationRelationship : The Client will call the Microsoft Exchange Autodiscover
service using the following URL: https://pod51041.outlook.com/autodiscover/autodiscover.svc/WSSecurity.
VERBOSE: [20:24:10.553 GMT] Test-OrganizationRelationship : The Microsoft Exchange Autodiscover service failed to be
called at 'https://pod51041.outlook.com/autodiscover/autodiscover.svc/WSSecurity' because the following error occurred:
WebException.Response = <cannot read response stream>
Exception:
System.Net.WebException: The request failed with HTTP status 404: Not Found.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse
Não consigo encontrar nenhum motivo para que ele falhe. Está falhando na chamada de descoberta automática para segurança. Todos os posts online dizem para habilitar o wssecurity para o diretório virtual, mas isso não é uma opção para uma implantação on-line completa do Office 365. Francamente, o compartilhamento federado do O365 deve "Just Work"
A próxima parte são os dados do relacionamento da organização que vão do SiteB (O365) ao SiteA (EX 2010)
PS C:\Users\me> Get-OrganizationRelationship | fl
Creating a new session for implicit remoting of "Get-OrganizationRelationship" command...
RunspaceId : b56a8f0b-7e7e-4e8c-bf5c-c33209e59b13
DomainNames : {SiteA}
FreeBusyAccessEnabled : True
FreeBusyAccessLevel : LimitedDetails
FreeBusyAccessScope :
MailboxMoveEnabled : False
DeliveryReportEnabled : False
MailTipsAccessEnabled : False
MailTipsAccessLevel : None
MailTipsAccessScope :
PhotosEnabled : False
TargetApplicationUri : FYDIBOHF25SPDLT.SiteA.us
TargetSharingEpr :
TargetOwaURL :
TargetAutodiscoverEpr : https://autodiscover.SiteA.us/autodiscover/autodiscover.svc/WSSecurity
OrganizationContact :
Enabled : True
ArchiveAccessEnabled : False
UseOAuth : False
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
Name : SiteA
DistinguishedName : CN=SiteA,CN=Federation,CN=Configuration,CN=appriver3651001356.onmicrosoft.com,CN=ConfigurationUni
ts,DC=NAMPR04A001,DC=prod,DC=outlook,DC=com
Identity : SiteA
Guid : d01ce3d5-6b47-41c6-b597-9f5ed5aca4a8
ObjectCategory : NAMPR04A001.prod.outlook.com/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
ObjectClass : {top, msExchFedSharingRelationship}
WhenChanged : 7/19/2013 3:36:22 AM
WhenCreated : 7/19/2013 3:36:13 AM
WhenChangedUTC : 7/19/2013 10:36:22 AM
WhenCreatedUTC : 7/19/2013 10:36:13 AM
OrganizationId : NAMPR04A001.prod.outlook.com/Microsoft Exchange Hosted
Organizations/appriver3651001356.onmicrosoft.com - NAMPR04A001.prod.outlook.com/ConfigurationUn
its/appriver3651001356.onmicrosoft.com/Configuration
OriginatingServer : BL2PR04A001DC06.NAMPR04A001.prod.outlook.com
IsValid : True
ObjectState : Unchanged
E isso é de SiteA (EX 2010) para SiteB (O365)
[PS] C:\Windows\system32>Get-OrganizationRelationship | fl
RunspaceId : a9029d90-cdf0-494a-85ea-a960bc04f023
DomainNames : {SiteB domains, 4 total}
FreeBusyAccessEnabled : True
FreeBusyAccessLevel : LimitedDetails
FreeBusyAccessScope :
MailboxMoveEnabled : False
DeliveryReportEnabled : False
MailTipsAccessEnabled : False
MailTipsAccessLevel : None
MailTipsAccessScope :
TargetApplicationUri : http://outlook.com/
TargetSharingEpr :
TargetOwaURL :
TargetAutodiscoverEpr : https://pod51041.outlook.com/autodiscover/autodiscover.svc/WSSecurity
OrganizationContact :
Enabled : True
ArchiveAccessEnabled : False
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
Name : SiteB
DistinguishedName : CN=SiteB,CN=Federation,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=my,DC=site
Identity : SiteB
Guid : 458f9921-f2f8-4286-92e2-a3f0b8c444f1
ObjectCategory : Mysite/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
ObjectClass : {top, msExchFedSharingRelationship}
WhenChanged : 7/19/2013 10:37:58 PM
WhenCreated : 7/19/2013 3:16:18 PM
WhenChangedUTC : 7/20/2013 5:37:58 AM
WhenCreatedUTC : 7/19/2013 10:16:18 PM
OrganizationId :
OriginatingServer : MyDC
IsValid : True
Deve-se observar que, quando eu digito o TargetAutodiscoverEPR ( link ), solicito credenciais, significando que o erro 404 que recebo é beliche.
A outra coisa estranha que notei é quando configuro o relacionamento da organização do SiteA para o SiteB. A execução de Get-FederationInformation produz o seguinte para o SiteB
PS C:\Users\me> Get-FederationInformation -DomainName SiteB
Creating a new session for implicit remoting of "Get-FederationInformation" command...
RunspaceId : d6086380-948f-43db-9d0c-4ba7325b5a20
TargetApplicationUri : outlook.com
DomainNames : {SiteB domains, 4 total}
TargetAutodiscoverEpr : https://pod51041.outlook.com/autodiscover/autodiscover.svc/WSSecurity
TokenIssuerUris : {urn:federation:MicrosoftOnline}
IsValid : True
ObjectState : Unchanged
O TargetApplicationUri indica "outlook.com", e foi assim que foi inserido quando configurei o relacionamento da organização no EMC do siteA. No entanto, o compartilhamento não funcionou e os testes me deram o seguinte
PS C:\Users\me> Test-OrganizationRelationship -UserIdentity me@SiteB -Identity SiteA
RunspaceId : d6086380-948f-43db-9d0c-4ba7325b5a20
Identity :
Id : ApplicationUrisDiffer
Status : Error
Description : The TargetApplicationUri of the remote organization doesn't match the local ApplicationUri of the
Federation Trust object. The remote URI value is http://outlook.com/. The local URI value is
outlook.com/.
IsValid : True
ObjectState : New
RunspaceId : d6086380-948f-43db-9d0c-4ba7325b5a20
Identity :
Id : VerificationOfRemoteOrganizationRelationshipFailed
Status : Error
Description : There were errors while verifying the remote organization relationship SiteB.
IsValid : True
ObjectState : New
Eu tive que ir manualmente para o objeto Org Relationship (SiteA trust do SiteB) e mudar o URI de "outlook.com" para " link "por compartilhar para trabalhar nessa direção. Esta é outra peculiaridade de definir tudo isso que está me fazendo pensar que este é um problema MSFT no lado do O365 ...