Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all 7129 articles
Browse latest View live

Coexisting exchange 2007 with exchange 2013 Error

$
0
0

Dear All

I am currently starting the installation Exchange server 2013 in exchange 2007 SP3 Environment. but when I kick the installation I get the following error 

Error:
The following error was generated when "$error.Clear(); 
          $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
          $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
          $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
          if( $dismbx -ne $null)
          {
          $srvname = $dismbx.ServerName;
          if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
          {
          Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -eq $null )
          {
          Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
          mount-database $dismbx.Database;
          }

          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -ne $null )
          {
          $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
          $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
          if( $dmRoleGroup -ne $null )
          {
            trap [Exception]
            {
              Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              continue;
            }

            Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
          }
          }
          }
          }
        " was run: "Couldn't resolve the user or group "mydomain.local/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust.".

*****************************************************

SOME FORUMS ARE ADVISING TO DELETE THE (DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}) WHICH IS DISABLED IN ACTIVE DIRECTORY. 

KINDLY ADVISE THE BEST WAY TO RESOLVE THIS 

YOUR USUAL SUPPORT IS GREATLY APPRECIATED IN ADVANCE

REGARDS

MICHAEL

            

Autodiscover internal

$
0
0

having some issue after we have decomission exchange2010 in site one and migrated everything to exchange 2013.

SITE 1

EXCHANGE 2013

SITE 2

EXCHANGE 2010

Site 2, Outlook clients which are hosted on exchange2010 on site2 gets popup redirections internally.

If we try with test E-mail Autoconfiguration internally on OUTLOOK 2013 (SITE2 - exchange2010) we get.

POP UP: https://owa.domain2.com/autodiscover/autodiscover.xml
And errors: httpStatus=500; FAILED (0x800C820F)

On exchange2010 on SITE2 results:

Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

Identity    : EXCHANGE2010\EWS (Default Web Site)
InternalUrl : https://owa.domain2.com/EWS/Exchange.asmx
ExternalUrl : https://autodiscover.domain2.com/EWS/Exchange.asmx

Get-ClientAccessServer -Identity exchange2010.subdomain.domain.local | fl

AutoDiscoverServiceInternalUri       : https://autodiscover.domain2.com/autodiscover/autodiscover.xml
AutoDiscoverSiteScope                : {SITE2}

Please help?


bostjanc


OWA Redirect loop after mailbox move to 2013 - external only

$
0
0

After moving mailboxes to Exchange 2013, I get this loop of where when I log in through the OWA in 2013, it redirects me tohttps://legacy.myorg.com/owa which then presents a message that the mailbox needs to be accessed in a different version of OWA, and it gives the link to it. So I click the link and I go right back to the OWA 2013 login page.

Now here is where it gets unusual... if I'm outside my network accessing OWA externally, it continues this cycle over and over.  If my users are internal and they try it, it puts them on OWA correctly.  It never attempts to redirect them to the legacy site (or it may try once, but then after that they are fine).  Exchange knows that the mailbox has moved and sticks the user to the correct OWA server.  But all that's internal.  Externally, it just goes back and forth which is aggravating because I do have a few users that use OWA externally majority of the time.

Any ideas?


JB

export Mailbox To Pst File

$
0
0

Hi Everyone,

i am trying to export some mailbox in my exchange2010 Sp3 to Pst , but when excute the below command i got the Error:

New-mailboxExportRequest -Mailbox "admin" -filepath \\ server\Pst\admin.pst

i got the following Error:

The call to 'net.tcp://server name/Microsoft.Exchange.MailboxReplicationService server name' timed out. Error details: This request operation sent to net.tcp:// server name//Microsoft.Exchange.MailboxReplicationService did not receive a reply within the configured timeout (00:01:00).

i tried to increase TimeOut on Client Access folder in Web.config file  i make (DataImportTimeout=00:20:00)but not successfully.

 

Note: (Pst) folder has been shared and give Group (exchange trust subsytem) full permission.

thank in advance 

On Premises Exchange 2010, Installed 2013, want to move mailboxes to cloud with hybrid, existing Office365 setup.

$
0
0

I think I have a weird scenario.

We have 2 AD domains that don't talk to each other at all. I'll try to explain in detail...

We have contoso.com and alumni.contoso.com...but remember they were named like that but they are not related, not even in the same network subnet.

In contoso.com we have exchange 2010 working with outlook web app and certificates without problems. We installed a new exchange 2013 Mailbox and CAS server, no certificates.

Alumni.contoso.com is setup in Office365, so our DNS is configured to forward mail for alumni.contoso.com to microsoft.

Contoso.com receives our email in our exchange 2010.

I'm working on getting the certificates for exchange 2013 and moving the users from 2010 to 2013...I did this with exchange 2007...

What I'm trying to figure out is how to move the on premises contoso.com exchange if I already have alumni.contoso.com in Office365. Since alumni.contoso.com "acts" as a child domain from contoso.com I think I might run into trouble?

Thanks for your time and suggestions.

Exchange 2007 to 2013 coexistence - 2013 ECP does not list 2007 database

$
0
0

I have Exchange 2007 currently coexisting with Exchange 2013. I have one server 2008 r2 server with Exchange installed all roles on one server. I also have 2x 2012 r2 servers one with CAS role and one with Mailbox role. So far the install has gone without issue but before i can move on i need to be able to see the 2007 database in the 2013 ECP but currently only the 2013 database is listed and I do not feel good about moving further until i can get 2013 to recognize the 2007 Database. 

Can someone help??

new-moverequest this request operation sent to net.tcp://target.2013.fqdn/microsoft.exchange.mailboxreplicationservice did not receive a reply within the configured timeout

$
0
0

Hi ,

I am currently testing a cross forest migration from exchange 2007 to exchange 2013. i do not have trust between my forest but i did set up conditional forwarding in both the source and target environment.

The Mailbox replication service does not behave as expected when i submit a new move request.

the move request : New-MoveRequest -Identity "f2867850-5e88-4f97-9efb-0b867a1fdb4b" -BadItemLimit "10" -TargetDeliveryDomain "TargetDomain" -TargetDatabase "{cbc90e5e-6124-458c-8105-464bc27d26c1}" -RemoteCredential (Get-Credential "sourcecredential") -RemoteGlobalCatalog "FQDN of source GC" -RemoteLegacy:$true

the error : "The call to 'net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService SERVERNAME (15.0.775.35 caps:3F)' timed out. Error details: This request operation sent to net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client."

I can ping both global catalog in the source environment and in the target from both side. nslookup and autodiscover is working as well.

MRS Proxy is enable on the exchange 2013 side and i have enable remote Powershell on both side.

i do not have any load balancer configure.

If anyone can point me in the right direction where to look it would be greatly appreciated.

thanks you



Frédéric Bédard

Exchange Server 2016 - service MSExchangeFrontedTransport can not start after setup

$
0
0

Hi every one, i need some help. Setup process of Exchange 2016 finishing with Error on step 14:

Ошибка:
При выполнении "$error.Clear(); 
start-SetupService -ServiceName MSExchangeFrontendTransport

" произошла следующая ошибка: "Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Службе 'MSExchangeFrontendTransport' не удалось достичь состояния 'Running' на этом сервере.
   в Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   в Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   в Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
   в Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   в Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   в Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
   в Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   в Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Service MSExchangeFrontedTransport can not start. It begin starting and stoped, so many times. In System monitor there is id mistake 7031. I could not stop it manually - it starts and then stops automatically. If u have any ideas i will really appreciate it! Thanks!




Errors in updating to CU9

$
0
0

Hi,

I'm currently having problem in enabling a hybrid setup for exchange 2013, the error is "HYBRID SYNCHRONIZING FAILED"

So upon reading blogs and forums, I was given an idea to upgrade my exchange to CU9. But I'm having issues on doing this task. 

Can you please help me? below are the errors encountered when upgrading to CU9

Error:
The following error was generated when "$error.Clear(); 
            #
            # O15# 2844081 - Create PartnerApplication "Exchange Online" in DC and On-Premise
            #
            $exch = [Microsoft.Exchange.Data.Directory.SystemConfiguration.WellknownPartnerApplicationIdentifiers]::Exchange;
            $exchApp = Get-PartnerApplication $exch -ErrorAction SilentlyContinue -DomainController $RoleDomainController | Where { $_.UseAuthServer };
            if ($exchApp -eq $null)
            {
                $exchAppName = "Exchange Online";
                $exchApp = New-PartnerApplication -Name $exchAppName -ApplicationIdentifier $exch -Enabled $RoleIsDatacenter -AcceptSecurityIdentifierInformation $false -DomainController $RoleDomainController;
            }

            # Create application account for Exchange
            $appAccountName = $exchApp.Name + "-ApplicationAccount";
            $appAccount = Get-LinkedUser -Identity $appAccountName -ErrorAction SilentlyContinue -DomainController $RoleDomainController;
            if ($appAccount -eq $null)
            {
                $appAccountUpn = $appAccountName.Replace(" ", "_")+ "@" + $RoleFullyQualifiedDomainName;
                $appAccount = New-LinkedUser -Name $appAccountName -UserPrincipalName $appAccountUpn -DomainController $RoleDomainController;
                Set-PartnerApplication -Identity $exchApp.Identity -LinkedAccount $appAccount.Identity -DomainController $RoleDomainController;
            }

            foreach ($roleName in ("UserApplication", "ArchiveApplication","LegalHoldApplication", "Mailbox Search", "TeamMailboxLifecycleApplication", "MailboxSearchApplication"))
            {
                $roleIdentity = Get-ManagementRole $roleName -DomainController $RoleDomainController;
                $roleAssignment = Get-ManagementRoleAssignment -Role $roleIdentity.Identity -RoleAssignee $appAccount.Identity -DomainController $RoleDomainController;
                if ($roleAssignment -eq $null)
                {
                    New-ManagementRoleAssignment -Role $roleName -User $appAccount.Identity -DomainController $RoleDomainController;
                }
            }
        " was run: "Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException: Active Directory operation failed on TFSSERV23.tfsph.local. The object 'CN=Exchange Online-ApplicationAccount,CN=Users,DC=tfsph,DC=local' already exists. ---> System.DirectoryServices.Protocols.DirectoryOperationException: The object exists.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.NewTaskBase`1.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.NewADTaskBase`1.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Checking if the Online Archiving Policies are working

$
0
0
Is there anyway to check to see if the Online Archiving Policies are working? I know it use to work for us a few weeks ago before we had to change our server to FQDN for new SSL cert but we have submitted changes on people mailboxes and I don't see the mail moving from the main mailbox to archive mailbox. I can't fine any commands for the shell to see if it working or not. We have it set to process them every day and know it takes in to account the server load but we made changes to peoples mailboxes days ago..

AllowIncrementalSyncs not syncing every 24 hours like I expected?

$
0
0

I successfully ran the following powershell cmdlet kicking off an initial sync of mailboxes in preparation to migrate from Exchange 2007 SP3 Update rollup 16 to Exchange 2013 CU9, all from one local server to another local server:

New-MigrationBatch -Local -Name Users1 -CSVData ([System.IO.File]::ReadAllBytes("C:\!IT\Migration\Users1.csv")) -AutoRetryCount 5 -AllowIncrementalSyncs $true -BadItemLimit 1000

The way I understand it, the AllowIncrementalSyncs parameter allows for incremental synchronization between the source and target mailboxes every 24 hours.  Any new messages sent to the source mailbox are supposed to be copied to the target mailbox.  

I waited 40+ hours after the initial MigrationBatch was kicked off and completed and ran the following cmdlet:

Get-MigrationBatch -Identity Users1 | FL

I expected to see theLastSyncedDateTime to show that it synced again since it's been over 40 hours but it shows the date/time of when I initially kicked it off, not 24 hours later like I expected, it's been over 40 hours since the initial sync completed.  What am I missing here?  

My intention is to migrate all 500 of our users this way and the night of the final cut over I can complete the migration batch.  How do I confirm these mailboxes are syncing every 24 hours?  I'm concerned that it could take too long to complete if they don't sync every 24 hours.  I appreciate any assistance you can provide.

Exchange 2013 Hybrid Configuration Error

$
0
0

Hi Guys,

I'm currently having a problem on my hybrid configuration,

One of the prerequisites for the Hybrid was to install CU6 or lates on Exchange 2013 as there was an error on the wizard.

So we upgrade it to CU9

After upgrading when I try to re-run the wizard I received below error.

The wizard did not complete successfully. Please see the list below for error details. Federation certificate with the thumbprint "A27A5D1D0F7BCAB4B5DDD75BD7CFFF36594C14E3" cannot be found.

Any help on this will be much appreciated

Migration to Exchange 2016

$
0
0
Hi guys,

Quick question. I have a fairly complex migration to plan and I was wondering if anyone could tell me if this is possible.

Due to a merger I have 2 seperate AD Environments both running seperate Exch 2007 that are working using internal relays & cross site federation. A new AD environment is currently being created and I am hoping to install Exch 2016 in this so what I need to know is it possible to move an Exchange 2007 mailbox into this new Exch 2016 environment or will I need to upgrade both sites to Exch 2013 first and then migrate to 2016?

Thanks
John

All Exchange 2007 servers in the organization must have Exchange 2007 SP3 or later installed. The following servers don't meet this requirement

$
0
0

Hi Everyone,

I am trying to install exchange 2013 and I'm running in to an issue. I am not an exchange expert, however I can understand the error message. 

I see that exchange 2007 must be have SP3 but the funny thing is that all the exchange servers in the organization were decommissioned.

This is the error message,

Error:

All Exchange 2007 servers in the organization must have Exchange 2007 SP3 or later installed. The following servers don't meet this requirement: xxexx,exchxx,exchxzx

For more information, visit: 

http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.E15E12CoexistenceMinVersionRequirement.aspx


If there is anything I can do to check why this error message pops up.

(or)

If there is any entry that remains even after exchange is decommissioned causes this error message to pop up?

Appreciate your input and time.

Thanks,

Sathish_Phoenix



ecp login on branch site redirects to main site / owa login on branch site redirects to main site on owa backend site port 444

$
0
0

hi,

I have a strange problem on exchange 2013 cu10 on the branch site.

When I want to logon to the ecp at branch site, after logon I get redirected to a exchange server in the main site and if I want to logon at owa on the branch site I get also redirected to the main site and the owa backend site of exchange on port 444.

This Issue is since I had a problem with the canaray data, I cleared this to not set in AD and updated all exchange server from sp1(cu4) to cu10.

The exchange server in the main site work correctly. I also deinstalled the two exchange server and take it off the domain in the branch site with the problem, then installed new but the redirect still exist.

Have anybody an idea why I get redirected to the main site?? Of course on the virtual directories there are no redirects set!

Beste regards,
marcus




Error with installing CU9

$
0
0

Hi,

I have a server with only the Exchange 2013 client tools installed. My upgrade to CU9 failed. I try to re-run the installation, which tries to complete the setup, but I am running into the following error:

Log Name:      MSExchange Management
Source:        MSExchange CmdletLogs
Date:          16.10.2015 0:52:56
Event ID:      6
Task Category: General
Level:         Error
Keywords:      Classic

Description:
Cmdlet failed. Cmdlet New-PushNotificationsVirtualDirectory, parameters -Role "Mailbox" -OAuthAuthentication "False" -DomainController "DCname".

System.InvalidOperationException: The Active Directory object for virtual directory 'IIS://DCname/W3SVC/25/ROOT/PushNotifications' on 'Servername' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it. ---&gt; Microsoft.Exchange.Configuration.Tasks.TaskException: Couldn't find the parent object for  on domain controllerDCName. Check that HTTP exists and that the domain controller belongs to domainDomainname.

Any insights on how to solve this error or work around it?

Thanks,

I. Kinal

extending schema on server 2008 r2 for exchange 2013 sp1 setup

$
0
0

Team,

i had transfer schema mastewr role on server 2008 r2. post transfering the role when i trying to extend the schema on server 2008 r2 server. I am getting error message. Please help me to fix up the issue

Trying to Uninstall: An incomplete installation was detected. Run setup to complete Exchange installation.

$
0
0

Hello All...

Trying to uninstall Exchange 2013 CUv2 v2. I've moved all the Mailboxes, Arbitration, Discovery, Public Folder, etc to another working server. Everything was moved over fine. Uninstall via the control panel proceeded as normal, then just failed. No choice but to exit. Now when trying to recover, and uninstall again....I cannot. I get the vague error of "An incomplete installation was detected.  Run setup to complete Exchange installation." 

Not that I want to, but tried to reinstall, but can't do that either.

I know it's a last resort and not supported, but can I just use ASDIEdit ,and manually remove the server references? If so, what is a good guide on the procedure....? I don't want spend hours pouring over setup logs and the registry if I don't have to- just want this removed from AD.

I've searched the net quite a bit on manual removal, but can't find a concise how-to...

Any help is appreciated ...Thanks

Exchange 2007 Problem

$
0
0

I work as an instructor for apprentices at a school in Norway.

I have set up a virtual server 2003, and installed Exchange 2007. After setup is complete, I try to create a mailbox, both new user and existing user. The wizard failes, giving this error:

An Exchange 2007 server on which an adddress list service is active cannot be found.

I've googled around for a while, and the only answer I found was that the Microsoft Exchange System Attendant service needs to be started from services.

However, that service is missing from my list.

I have tried reinstalling Exchange server, but had no luck..

[E2007] > [E2013] CU10, SRV 2008 ENT CA / CBA>User Based Cert Authentication not working as it should on [E2013]CU10

$
0
0

Good day,

We have:

* Existing E2007 Sp3 latest Rollup on SRV2008 (With user certs for ActiveSync(External + Internal)

* Fresh Installed Exchange 2013 CU10 on Server 20012 R2 (Only Test user on other side)

* Enterprise CA on Server 2008

* User Cetrificate Authentication for Iphone and Android (No user cert auth W7 client side needed)

Problem:

A 2013 test user is able to do ActiveSync test with EAD Mobilitydojo.net tool (No cert)

Same test user is unable to authenticate with a user cert file and >User based Certificate Authentication on E2014< for Acticesync

* Exchange 2013 clean and fully de-installed (No ADSI Entrys left in any  form for that server). Could clean deinstall. All Arbitary and Health/Search moved.

* Exchange 2013 clean and fully re-installed

* Did rebuild of Acticesync Virtual Directory

WORSE I GOT it running IN LAB: Same Setup in VM Lab BUT with NONE 2007 in Place and fresh installed CA seems to work.

MAY BE SOURCE BUT UNABLE TO SOLVE. If we Import the user Cert PFX from the user in the Computer/personal store of the Exchange 2013 and run the test tool direct there IT works.

> It seems like the E2013 does NOT trust the CA

IF i take out the Personal Cert from STORE and Clean with (certutil -urlcache crl delete,certutil -urlcache ocsp delete ) and test again it does not work. So in that case hes not able to autheticate to the CA. But if he has it local it works.

And the Exchange Activesync MD test Tool from Mobilitydojo.net we have the cert correct with Filename and Password. H:\migration\exchange_2007_2013\eas\2007_personal.pfx

--------------------------------------------- ERROR we see there if it does not work -----

testing HTTP GET:
Response: The remote server returned an error: (403) Forbidden.
Explanation:
The server requires SSL and will not let you connect over HTTP.
(
For instance trying to connect over HTTP while IIS requires SSL.)
Status: Further action required

--------------------------------------------- ERROR we see there if it does not work -----

All root / intermediate to my knowledge (only weakness PKI sometimes ;-)) ok BUT the if we import Manual and then it works worries me. For me that means something between the Exchange 2013/2012R2 and the SRV 2008 CA is not ok.

We use a SAN-With 4 names but TWO Domains. webmail.test01.com autodiscover.test01.com and webmail.test02.com (Old). Have made a self signed for Debug but was the source.

* IIS settings are complete identical and we verified them (REAL Server and LAB we build 2 times)

* Cert Authentication IIS feature installed

* The Meta ENABLE for Authentication Certs is on TRUE

* All Cash cleaned from IIS

Please help if you can. ;-)


Viewing all 7129 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>