Hi.

We moved our Exchange 2013 Virtual machine( which has server 2012 Datacenter OS) to new Hyper-V Host server(Server 2012 R2 Datacenter) We tried to upgrade integration services from 6.2.9200.16384 to 6.3.9600.16384 on our Exchange server so that Veeam can do backup. but after upgrading Integration services, server cant boot fully.

I am not sure what is causing the issue. because all other VM's which also got moved to new Hyper-V host are working after Integration services upgrade.

Deepthi Nune

Hello! First, thank you for reading and taking the time. My company would like to use Exchange Control Panel (EAC) for HR to adjust title, phone number, address, location, etc for recipients.

I found a document online and ran the the following commands to create the role:

New-ManagementRole -name "Manage User Contact Information" -Parent "Mail Recipients"

Get-ManagementRoleEntry "Manage User Contact Information*" | where { $_.Name -ne "Set-User"} | Remove-ManagementRoleEntry

Set-ManagementRoleEntry "Manage User Contact Information\Set-User" -Parameters City,Company,CountryOrRegion,Department,Fax,HomePhone,Manager,MobilePhone,Notes,Office,OtherFax,OtehrHomePhone,OtherTelephone,Pager,Phone,PostalCode,PostOfficeBox,StateOrProvince,StreetAddress,Title,WebPage

Get-ManagementRoleEntry "Mail Recipients\Get-*" | Add-ManagementRoleEntry -Role "Manage User Contact Information"

New-ManagementScope -Name "ContactManageScope" -RecipientRestrictionFilter { RecipientType -eq 'UserMailbox' }

I then logged into EAC as an admin, went to permissions, admin roles, found my Contact Management role and added Manage User Contact Information role and change the write scope to ContactManageScope. I added my test account named "testacct" to members. Hit save.

I logged into EAC as the testacct user and I am able to see the recipients but cannot edit any of the parameters I set for that role. What am I missing here?

The very first thing the Best Practices Analyzer says wrong is that Application pool 'MSExchangeOWAAppPool' on server 'EMAIL' is configured to run under the wrong identity.  'MSExchangeOWAAppPool' should run under the 'Local System' identity.

I would like to know where this tool is getting this information?  I went into IIS and verified MSExchangeOWAAppPool is running under the LocalSystem identity.

What else do I need to do?  The OWA virtual directory is attached to this app pool.  Things look correct so why is the BPA saying that I have an error in the configuration?

IMAP crashed and not working after applying the CU10 on top of Exchange 2013 CU10. I read the KB that "This issue occurs because Internet Mail Access Protocol (IMAP) does not support the generic security services application programming interface (GSSAPI) as an authentication mechanism in a Microsoft Exchange Server 2013 environment "

and I tried to enable Set-IMAPSettings –EnableGSSAPIAndNTLMAuth:$FALSE

and no luck, still IMAP asking for a credentials again and again. POP is working fine.
I can see the IMAP protocol log, there are msgs

"IN:9933:SSL;ErrMsg=ProxyNotAuthenticated;LiveIdAR=OK""

"authenticate,NTLM,"R=""l7z2 NO AUTHENTICATE failed."";"

the IMAP settings are

[PS] C:\Windows\system32>Get-ImapSettings | format-list


RunspaceId                        : 32a6432b-de4f-4730-adf3-6595ccb25ce8
ProtocolName                      : IMAP4
Name                              : 1
MaxCommandSize                    : 10240
ShowHiddenFoldersEnabled          : False
UnencryptedOrTLSBindings          : {[::]:143, 0.0.0.0:143}
SSLBindings                       : {[::]:993, 0.0.0.0:993}
InternalConnectionSettings        : {essrv011.****.IN:993:SSL, essrv011.***.IN:143:TLS}
ExternalConnectionSettings        : {}
X509CertificateName               : email.***.ac.in
Banner                            : The Microsoft Exchange IMAP4 service is ready.
LoginType                         : SecureLogin
AuthenticatedConnectionTimeout    : 00:30:00
PreAuthenticatedConnectionTimeout : 00:01:00
MaxConnections                    : 2147483647
MaxConnectionFromSingleIP         : 2147483647
MaxConnectionsPerUser             : 16
MessageRetrievalMimeFormat        : BestBodyFormat
ProxyTargetPort                   : 9933
CalendarItemRetrievalOption       : iCalendar
OwaServerUrl                      :
EnableExactRFC822Size             : False
LiveIdBasicAuthReplacement        : False
SuppressReadReceipt               : False
ProtocolLogEnabled                : True
EnforceCertificateErrors          : False
LogFileLocation                   : C:\Program Files\Microsoft\Exchange Server\V15\Logging\Imap4
LogFileRollOverSettings           : Daily
LogPerFileSizeQuota               : 0 B (0 bytes)
ExtendedProtectionPolicy          : None
EnableGSSAPIAndNTLMAuth           : False
Server                            : ESSRV011
AdminDisplayName                  :
ExchangeVersion                   : 0.10 (14.0.100.0)
DistinguishedName                 : CN=1,CN=IMAP4,CN=Protocols,CN=ESSRV011,CN=Servers,CN=Exchange Administrative Group
                                    (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=****,CN=Microsoft
                                    Exchange,CN=Services,CN=Configuration,DC=***,DC=AC,DC=IN
Identity                          : ESSRV011\1
Guid                              : 4ed7aaa3-90b7-4c3b-b373-bccccf85fcf3
ObjectCategory                    : ****.IN/Configuration/Schema/ms-Exch-Protocol-Cfg-IMAP-Server
ObjectClass                       : {top, protocolCfg, protocolCfgIMAP, protocolCfgIMAPServer}
WhenChanged                       : 22-09-2015 20:02:07
WhenCreated                       : 22-07-2015 18:54:19
WhenChangedUTC                    : 22-09-2015 14:32:07
WhenCreatedUTC                    : 22-07-2015 13:24:19
OrganizationId                    :
Id                                : ESSRV011\1
OriginatingServer                 : ***.IN
IsValid                           : True
ObjectState                       : Unchanged

3 node CAS and 3 node Mailbox DAG is my environment.

Pl. help put

I am getting ready to migrate Exchange 2010 to 2013. I need you advise on namespace planning.

Current Exchange Deployment information.

1 Exchange 2010 SP3

AD DNS information

MX = EXCH.domain.com
autodiscover CNAME EXCH.domain.com
mail CNAME EXCH.domain.com
EXCH.domain.com A 192.168.1.26

Client Access URLs - Outlook Web App, ECP, ActiveSync,EWS,oAB

All InternalURls https://EXCH.domain.com/
All ExternalURls https://mail.domain.com/

AutodiscouverInternalURI https://EXCH.domain.com/autodiscover/autodiscover.xml

Important:
Currently server FQDN EXCH.domain.com is identical to All InternalURls which is https://EXCH.domain.com/

New Exchange Deployment information:

1x Exchange 2013
EXCH2013.domain.com A 192.168.1.25

In new Exchange 2013 installation if I use the namespace "mail.domain.com" for both InternalURLs and ExternalURLs:
how will it impact the clients, Certificates etc. Does the virtual directories setup in Exchange 2013 need to use the same names like in exchange 2010?

Thanks,

a colleague had tried and failed to install Exchange 2016 on a new server (Exchange 2010 environment), and then tried to install Exchange 2013 instead and wasn't able to migrate mailboxes.   I am just looking into the issues now and it seems like the schema is at fault, when trying to /preparead I get the following message.  I think the important one is bolded below, if I am not mistaken the schema for AD is upgraded for 2016 so the upgrade for 2013 is failing because it lower then the current version.

I am not sure why 2016 didn't work, but I just looked at the system requirements for 2016 and it requires CU11 on the 2010 SP3 server.  At this point I am not sure if I should attempt 2016 myself or try to fix this 2013 install issue.

Any thoughts?

Setup encountered a problem while validating the state of Active Directory: The Active Directory organization confi
guration version (16210) is higher than Setup's version(15844). Therefore, PrepareAD can't be executed.  See the Exchang
e setup log for more information on this error.

Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup

Performing Microsoft Exchange Server Prerequisite Check

    Prerequisite Analysis                                                                             FAILED
 Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have b
een detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
 For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.
aspx

 Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
 For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.
aspx

     Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins'
 group.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateReq
uired.aspx

     The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Managemen
t' role group, or 'Enterprise Admins' group to continue.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LocalDomainPrep
.aspx

     Setup encountered a problem while validating the state of Active Directory: The Active Directory organization confi
guration version (16210) is higher than Setup's version(15844). Therefore, PrepareAD can't be executed.  See the Exchang
e setup log for more information on this error.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule
.aspx

     The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To i
nstall Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotW
in2003Native.aspx

     Either Active Directory doesn't exist, or it can't be contacted.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.
aspx

The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.

Hey everybody

I have a strange one for you all. I am working on a greenfield setup and after fixing up 2 DC's, DNS etc Exchange will not install.

The whole environment is 2012 R2, Exchange 2013 CU9.

IPv6 enabled on adaptors but disabled in registry as my cloud provider has IPv6 disabled. I am using the disabled components key. I have tried 3 and 8 F's.

I get Event 2142 telling me no suitable DC or GC is available, but here is the kicker. It lists the sites, but it doesn't list the DC's, at all and it says the secondary AD site has no DC's either. 

DNS and sites/services have the subnets mapped to the correct site PRIDC

I don't even see the typical list of DCs and features that are enabled disabled. I get a blank list of no DCs!

I ran

nltest /dsgetsite

and get the correct site, PRIDC

I ran a test to check the GC's are registered in the site

nltest /dnsgetdc:<domain> /gc /site:PRIDC

I get both domain controllers. I did DCDIAG /test:DNS and everything passes

I re-ran /preparead /prepareschema  and in desperation /preparealldomains.

then I read about some bug in CU 2 and ran /PS, PD and PAD to be sure.

there is nothing obvious in the ad setup logs and no events in AD that relate to failures.

I turned the AD topology logging up to 7 but all it tells me is that it is connecting to the DC's on LDAP 389 and 3268. I can see the login in AD event logs with no failures in the security log.

I have checked ,Domain>\Exchange Servers is assigned Manage Auditing and Security log in the default domain RSOP and policy.

No AV software and tried with firewalls disabled

Only thing other than the default server setup is EMET has been installed by the security team but I have tried disabling that.

I am all out of ideas!

Hi,

I am in the process of migrating a lot of mailboxes from an 2010-installation to a 2013-installation. I migrate the mailboxes by using the Migrate-wizard in ECP from the 2013-installatin. I have migrated hundreds of mailboxes without any problem, but for one spesific mailbox the migration fails and I cannot solve the problem. It seems that the migration runs as normal until  it is almost ready, but then the log shows errors as shown below. Any tips on how I can troubleshoot this?

As said, I have migrated hundreds af mailbox without problems so I think the problem is related this this spesific mailbox.

From the log:

02/12/2015 14:37:27 [ha-exch-01] Connected to source mailbox '520c4e66-721e-4267-86c2-d013de53be7f (Primary)', database 'exdb03_database3', Mailbox server 'EXDB05.hrp.no' Version 14.1 (Build 438.0), proxy server 'postit.hrp.no' 14.1.438.0 caps:01FFFF.
02/12/2015 14:37:27 [ha-exch-01] Transient error CommunicationErrorTransientException has occurred. The system will retry (1/60).
02/12/2015 14:38:52 [ha-exch-01] The Microsoft Exchange Mailbox Replication service 'ha-exch-01.ad.ife.no' (15.0.1076.6 caps:1FFF) is examining the request.
02/12/2015 14:38:52 [ha-exch-01] Connected to target mailbox '520c4e66-721e-4267-86c2-d013de53be7f (Primary)', database 'ha-exch-01_database2', Mailbox server 'ha-exch-01.ad.ife.no' Version 15.0 (Build 1076.0).
02/12/2015 14:38:52 [ha-exch-01] Connected to source mailbox '520c4e66-721e-4267-86c2-d013de53be7f (Primary)', database 'exdb03_database3', Mailbox server 'EXDB05.hrp.no' Version 14.1 (Build 438.0), proxy server 'postit.hrp.no' 14.1.438.0 caps:01FFFF.
02/12/2015 14:38:53 [ha-exch-01] Relinquishing job because the mailbox is locked. The job will attempt to continue again after 02/12/2015 14:43:53.
02/12/2015 14:43:53 [ha-exch-01] The Microsoft Exchange Mailbox Replication service 'ha-exch-01.ad.ife.no' (15.0.1076.6 caps:1FFF) is examining the request.
02/12/2015 14:43:53 [ha-exch-01] Connected to target mailbox '520c4e66-721e-4267-86c2-d013de53be7f (Primary)', database 'ha-exch-01_database2', Mailbox server 'ha-exch-01.ad.ife.no' Version 15.0 (Build 1076.0).
02/12/2015 14:43:53 [ha-exch-01] Connected to source mailbox '520c4e66-721e-4267-86c2-d013de53be7f (Primary)', database 'exdb03_database3', Mailbox server 'EXDB05.hrp.no' Version 14.1 (Build 438.0), proxy server 'postit.hrp.no' 14.1.438.0 caps:01FFFF.
02/12/2015 14:43:53 [ha-exch-01] Relinquishing job because the mailbox is locked. The job will attempt to continue again after 02/12/2015 14:48:53.
02/12/2015 14:48:59 [ha-exch-01] The Microsoft Exchange Mailbox Replication service 'ha-exch-01.ad.ife.no' (15.0.1076.6 caps:1FFF) is examining the request.
02/12/2015 14:48:59 [ha-exch-01] Connected to target mailbox '520c4e66-721e-4267-86c2-d013de53be7f (Primary)', database 'ha-exch-01_database2', Mailbox server 'ha-exch-01.ad.ife.no' Version 15.0 (Build 1076.0).
02/12/2015 14:48:59 [ha-exch-01] Connected to source mailbox '520c4e66-721e-4267-86c2-d013de53be7f (Primary)', database 'exdb03_database3', Mailbox server 'EXDB05.hrp.no' Version 14.1 (Build 438.0), proxy server 'postit.hrp.no' 14.1.438.0 caps:01FFFF.
02/12/2015 14:48:59 [ha-exch-01] Transient error CommunicationErrorTransientException has occurred. The system will retry (1/60).

Thor-Egil

When migrating or adding a new user to Exchange 2013, I get the following error when going into the Mailbox Delegation section in the Exchange Admin Center.

The object <Object CN> has been corrupted, and it's in an inconsistent state. The following validation errors happened:

The access control entry defines the ObjectType 'Object GUID' that can't be resolved.

I have done the following to try and resolve the GUID

Searched via LDP, ADSI, ADUC, Repadmin, with nothing found. I've converted the GUID from string to hex and searched with still no luck.

I get the identical error when running a Get-ADPermissions on the object as well.

There are no inheritance blocks on the object or OUs.

I've opened a Premier case, but wanted to ask the community if they have seen this or had any suggestions. As of right now, Exchange 2013 is the only app that can see this orphaned object.

Hello, 

i have office 365 and i will tried to install  a new exchange server 2013 with the same domain. 

in the past i had exchange 2010 that migrate mailbox to office 365.

now, when i try to install new installation of exchange the installation fail on mailbox roles - the message is mandatory mailbox   

 ****log**** ” was run: “Database is mandatory on User Mailbox. Property Name: Database”.

it is possible to install new exchange 2013 that is separated with office 365 with the same domain?

Thanks,

aedmo

Hi there,

I'm trying to automate powershell commands which will add different GAL's to my Exchange.

But i'm having the following issue:

Import-CSV AddGAL.csv | foreach {New-GlobalAddressList -Name "$_.GAL – GAL" -ConditionalCustomAttribute1 $_.GAL -IncludedRecipients MailboxUsers -RecipientContainer "domain.local/Email/$_.GAL"}

It does not accept the $_.GAL between qoutes ("")

Any idea how i can fix this?

We are in the middle of a large migration from 2010 to 2013.

To narrow down the situation ill only tell whats relevant.

###Exchange 2010:

Exchange 2010 Casarray: casarray.contoso.com

Internal and external namespaces are webmail.contoso.com

Outlook Anywhere enabled on 2010, external hostname: webmail.contoso.com, auth: internal NTLM, IIS, basic&NTLM

SCP is the FQDN of the 2010 CAS servers

Its a hybrid setup with Office 365,

External autodiscover and namespaces are pointing to the 2010 CAS array.

### Exchange 2013

multi rol servers

namespaces internal and external webmail.contoso.com

Outlook Anywhere configured with NTLM, internal clients do not require SSL, external yes.

outlookprovider: EXPR is MSSTD:webmail.contoso.com

The servers are in the build fase and we started testing the servers before putting in production by moving the namespaces. To avoid problems during the configuration, we changed the SCP of the 2013 servers to the FQDN of the 2010 servers. The SCP records are only filled with 2010CAS servers.

I am trying to test the Exchange 2013 servers:

OWA: works correct, proxy to 2010 mailbox gives no problems.

Autodisover/autodiscoverpage gives an Error code 600, thats ok.

We have created a mailbox on the 2013 server and added a hostfile on a client so that the CAS2010 servers (SCP) are resolved to the CAS2013 server. Because the cas2010 fqdn's are added to the certificate, no SSL warning is displayed.

For testing purposes in other migrations we never had problems with changing the hostfile to test the autodiscover process. But now, if we use Outlook 2013 and want to connect to the 2013 server, Outlook is configured by autodiscover to use the CAS-Array as entry point. Sure that's not going to work.

Manually configure the outlook client doesn't work either.

What is going wrong.......

Marcel

So I've decided to start testing SSL offloading with Exchange 2013 SP1 now that it is supported. I have followed this guide: http://technet.microsoft.com/library/dn635115(EXCHG.150).aspx. It is fairly straightforward, remove the "Require SSL" option on the VDIRS and IISRESET.

To test, I load up http://CAS/OWA and it immediately redirects to HTTPS://CAS/OWA. I do not see why it is doing this or how to configure it otherwise. So while my server is accepting connections on port 80, it's just bouncing them over to 443. How do we disable this?

I checked the HTTP Redirect option on the VDIRs, which is not present. Also, I am going straight to the server, so there is not a device in front that is redirecting my requests. Any thoughts?

Thanks,

Brandon

The time in mailbox migration statistics shows with not my preferred time zone, any idea?

I have a client using Exchange 2007 with 2 mailbox two Hub/CAS and two Edge transport server.

The organization is using comanyA.com as internal AD Domain.

companyB.com is an accepted domain using same active directory.

now I have created new exchange 2013 forest with companyB.com and hosted exchange 2013 organization.

Now customer requirement is to route email via existing exchange 2007 edge transport server. (this will be for temporary duration as soon as mailbox migration between two domain has been completed). a new edge server will be added and mail flow will be shifted to it. Right now client has no edge servers and he has sent PO for it , will take some time. Once the migration has been completed will remove old organization.

If anybody could help me out it will highly appreciated.

SYED WASIL UDDIN Infrastructure Consultant/System Engineer Premier Systems (Pvt.) Ltd.

My client have exchange 2007 deployed using third party certificate. with

subject: mail.CompanyA.com

SAN:

autodiscover.companyA.com

HUBCAS01.CompanyA.com (HUB/CAS Server)

HUBCAS02.CompanyA.com (HUB/CAS Server)

Legacy.CompanyB.com (Not using this)

Autodiscover.CompanyB.com (Not using this)

mail.CompanyB.com (Pointed to Public IP NATed to TMG Publishing Server)

I have deployed new exchange 2013 domain and exchange organization and want to use the same certificate for temporary duration of coexistence will migrate every mailbox and close the old system.

now both organization have same smtp domain companyB.com and CompanyA is basically used by other organization having different Site and certificate.

This third party certificate will be expired in 2017.

I want to either publish exchange using same proxy and don't want to add new certificate.

or if I can set exchange 2007 to recognize exchange 2013 or if the requested recipient doesn't recognized relay it to exchange 2013 organization.

SYED WASIL UDDIN Infrastructure Consultant/System Engineer Premier Systems (Pvt.) Ltd.

I have a client who has 2 separate forest domains with two separate exchange servers serving two separate email domains (DomainA.com & DomainB.com).  The forest domains have a trust relationship established between themselves.

They would like to have both Exchange servers send/receive email primarily from DomainA.com but still have DomainB.com active on the DomainB exchange server for transitional purposes.

I believe I can accomplish this by adding DomainA.com as an Accepted Domain on the DomainB exchange server, creating email aliases for each mailbox, and then creating connectors between the two servers and setting up the DomainA server as the "Head End".

However, the client would like a common GAL between the two servers and from what I have read this cannot be accomplished when the Exchange servers are on separate domains.

My question is, how would I design their Exchange environment to fulfill their request? 

Would I have to collapse/merge into one domain?

Could I migrate DomainB's Exchange server into the DomainA domain?  If so what does that process look like/encompass?

Also, if there is a better way to accomplish this than what I have mentioned I am open to options.

Thank you,

Kyle

Hi:

I have a Exchange 2010 test migration to 2013 enviroment , On the 2013 for some issues I´ve delete-remove the Powershell VirtualDirectory with the Remove-PowerShellVirtualDirectory , then I´ve closed the Shell and I´ve tried to reopent and of course it conect to other Exchange 2010 server VirtualDirectory.

I´ve tried to recreate the Virtual Directory but it said VirtualDirectory is created because it tries to create it on the other Exchange 2010 server that has its own virtualdirectory

How can I create the virtual directory on my new 2013, I´ve tried with the -server option but Exchange 2010 doesn´t accept this option:

Even I´ve tried to create handly the VirtualDirectory on IIS but no way.

Pls, some help.

Thanks a lot.

Hi guys,

Im strugling with the following scenario:

We try to setup Exchange federation between Exchange 2010 sp2 and Exchange 2013. Everything is setup as described on Technet.

The problem I'm having is the following:

WHen i run test-organizationrelationship i get this.

RunspaceId  : 09496e7f-2a7c-4e3a-b15d-0c8d6a1a867b
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 ishttp://fydibohf25spdlt.aldum.co.za/. The local URI
              value is FYDIBOHF25SPDLT.aldum.co.za.
IsValid     : True
ObjectState : New

RunspaceId  : 09496e7f-2a7c-4e3a-b15d-0c8d6a1a867b
Identity    :
Id          : VerificationOfRemoteOrganizationRelationshipFailed
Status      : Error
Description : There were errors while verifying the remote organization relationship Aldum.
IsValid     : True
ObjectState : New

For the life of me the application uri on Exchange 2010 is FYDIBOHF25SPDLT.aldum.co.za

Here is the proof:

RunspaceId            : e58ad1c2-2910-42c7-a624-748dd0ffbb57
DomainNames           : {aldum.co.za}
FreeBusyAccessEnabled : True
FreeBusyAccessLevel   : LimitedDetails
FreeBusyAccessScope   :
MailboxMoveEnabled    : False
DeliveryReportEnabled : False
MailTipsAccessEnabled : False
MailTipsAccessLevel   : None
MailTipsAccessScope   :
TargetApplicationUri  : FYDIBOHF25SPDLT.aldum.co.za
TargetSharingEpr      :
TargetOwaURL          :
TargetAutodiscoverEpr : https://autodiscover.aldum.co.za/autodiscover/autodiscover.svc/WSSecurity
OrganizationContact   :
Enabled               : True
ArchiveAccessEnabled  : False
AdminDisplayName      :
ExchangeVersion       : 0.10 (14.0.100.0)
Name                  : Aldum
DistinguishedName     : CN=Aldum,CN=Federation,CN=Onesys,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onesys,D
                        C=local
Identity              : Aldum
Guid                  : 7e806cf3-69d3-40ca-bd29-4ebbecb6e2f9
ObjectCategory        : onesys.local/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
ObjectClass           : {top, msExchFedSharingRelationship}
WhenChanged           : 2013/05/16 12:45:12 PM
WhenCreated           : 2013/05/16 12:44:57 PM
WhenChangedUTC        : 2013/05/16 10:45:12 AM
WhenCreatedUTC        : 2013/05/16 10:44:57 AM
OrganizationId        :
OriginatingServer     : isdc01.onesys.local
IsValid               : True

I allready deleted the federation trust and organization relationship and recreated it but the problem persists.

Your help will be appreciated.

Regards