Hi There

I'm troubleshooting an issue during a exchange 2010 to exchange 2013 migration where the OOF is not working for users homed on the exchange 2010 mailbox servers. This applies to users using outlook 2010 and outlook 2013 .OWA works perfectly and you can also enable OOF via exchange powershell.

Users homed on the exchange 2013 servers does not have any issues.

The exchange 2010 servers is on SP3 rollup 4 and the 2013 servers on SP1 only without any rollups installed.

So my question will be - have anyone experienced this issue during migration and will patching the exchange 2010 servers to rollup 5 or 6 and the exchange 2013 to sp1 rollup 5 fix the OOF issue then? If requested the client to patch to these levels, but in the meantime I'm checking if anyone else had similar issues.

Any pointers will be welcome.

Hi guys,

I've been tasked with reviewing an Exchange environment, which is as follows:

4 x Exchange 2013 SP1 VM's with CAS and MBX roles. 12 DB's in a DAG
1 x Exchange 2010 SP3 VM with CAS, HT and MBX roles. 2 small DB's

The 2013 environment is a state, with 1 server totally offline / destroyed, another "Paused" at Hypervisor layer for last 2 months and no backups for over a month! Plus all traffic is going over a single interface rather than replication over a dedicated one...

Never having dealt with mixed environments before, I'm curious about how to decommission the 2010 server?

I'm assuming that mail flow for a user on a 2013 DAG MBX will use the 2013 send and receive connectors defined on the server rather than what's in the 2010 EMC for the legacy 2010 server. (Users are homed on the 2013 DAG) There is no external URL set on the 2010 server at all, just internal.

Really, I'm trying to work out what to do with the 2010 server. Other than move the DB's off it are there any tips or tricks, gotcha's or general advice on doing so?

Thanks - Steve

Hi ,

I have a 32bit machine windows 7. So far I was installing EwsManagedAPI.msi without any problems in my machine. My latest version was the 2.1

I have downloaded 2.2 and I tried to install it and I got the below

That means that the msi is ONLY for 64bit machines ?????? 

We don't have a 32bit msi ??? 

Can someone help me on this ?

thank you

This one is driving me absolutely crazy,  hours and hours spent on this with no luck.  This is 2007/2013 env.  The issue is, if I move a mailbox to 2007 then 2013 OWA is fine, then if I move the mailbox back to 2007 I can't access the mailbox via OWA when going through a 2013 CAS server.  yes I've read the posts about permissions inheritance etc.. yes I've cranked up AD and OWA logging nothing.. yes I've imported the IIS logs into log parser and I'm seeing various errors mostly 302.  Yes, I've ruled out 2007 servers, it's 2013.  If I recreate the mailbox it works then when move back and forth from 2007 to 2013 problem re-appears.  Yes, I have dumped AD attributes and compared them with working and non working mailbox can't find anything.  Yes, I've rebooted servers.  Yes this happens with multiple mailboxes.

In fact I have this example right now makes no sense.  I have two 2013 servers, if I go through the 2013 servers CAS servers to access the mailbox using OWA that resides on the 2007 server, it works through one server and the other it doesn't with the above errors.  I'd love to hear suggestions.. I'm at the end of my rope

I'm on a 2003 AD functional level on Server 2003 Std domain controllers.  I am in process of migrating from Exchange 2007 to Exchange 2013.  After reading the Exchange 2013 support matrix I need to make certain I understand my migration path correctly.  I am adding Server 2012 R2 DCs into my AD environment in preperation for this project. However, I had mistakenly thought that Exchange 2013 was not supported on a 2003 functional level domain, but after reading the support matrix that appears incorrect.  

My questions are these:

Is Exchange 2007 supported on a 2012 domain so that I can raise the functional level now rather than later.

Or, should I stay on a 2003 functional level until after the migration to 2013 is complete?

I'm getting a headache trying to get my mind wrapped around this.  Maybe I'm getting too old.  

Tony

I need to redirect the E:\Exchange\V14\Logging folder to L:\Logging.  Will the mklink be able to redirect the folder?

mklink /j E:\Exchange\V14\Logging folder  L:\Logging

Is there a better option?

I have a 2010/2013 environment.

I'm trying to create a DAG in 2013 but when i try to specify the fileshare witness directory(or leave it blank) i see this error in the 2013 mailbox server.

i currently only have 1 2013 cas server and 1 2013 mbx server.

i tried to point the witness directory to be the 2013 cas server.

Below is the event

Also should I be able to ping the DAG ip address?

thanks in advance

Ive install Server 2012R2 with Exchange 2013, DC in other server, before install Exchange 2013, ive install below pack:

1) UcmaRuntimeSetup.exe

2) FilterPack64bit.exe

3) filterpack2010sp1-kb2460041-x64-fullfile-en-us.exe

Then install Exchange 2013, after complete, open the IE to https://127.0.0.1/ecp, after successful login in with administrator (or other username) in show below error:

---------------------------------------------------------------------------------------------------------------------------

Server Error in '/ecp' Application.

NegotiateSecurityContext failed with TimeSkew
             Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.            

Exception Details: System.Web.HttpException: NegotiateSecurityContext failed with TimeSkew

Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.                   

Stack Trace:
[HttpException (0x80004005): NegotiateSecurityContext failed with TimeSkew]
   Microsoft.Exchange.HttpProxy.ProxyRequestHandler.EndProcessRequest(IAsyncResult result) +578
   System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +282

                   
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34009

---------------------------------------------------------------------------------------------------------------------------

Ive check IIS on "Default Web Site" Bindings "Type; port; ip address is
 http; 80; 127.0.0.1
 https; 443; 127.0.0.1

Beside, I also login to OWA also has same error. Please help.

Regards

Chris

Chris Pang Chris@networkstar.com.hk

Trying to download Hotfix KB2619234 which is pre-req for exchnage 2013 installation on Win 2008 R2.

After providing the e-mail address and request hotfix....received error...The system is currently unavialable, Please try back later r contact support if you want immediate assitance.Seems like the HF is not available for download now, Any other option to get this HF?

Thanks,

Praveen

I am running two, two node DAG's with Exchange 2013.

One DAG pair is running 5 databases with Server 2012 Standard and the second DAG pair is running Server 2008 R2 SP1 Standard with a single shared database.

No matter what I try, ALL 6 databases show "ContentIndexState: Failed" with "ContentIndexErrorMessage: An internal error occurred for the database or its index.".

I have tried rebuilding the indexes manually, automatically and manually copying the database files between servers.  I also receive errors when trying to failover the databases because the content index state is failed.

In my test environment I have a very similar setup working fine with no issues.

Please let me know what I can try to get this resolved.

The error I receive when running the following set of commands is:

suspend-MailboxDatabaseCopy dag2db1\mbox1

update-MailboxDatabaseCopy dag2db1\mbox1 -deleteexistingfiles

[PS] C:\Windows\system32>update-mailboxdatabasecopy dag2db1\mbox1 -deleteexistingfiles

Confirm
Are you sure you want to perform this action?
Updating database copy DAG2DB1\MBOX1 on server MBOX1
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): a
WARNING: Seeding of content index catalog for database 'DAG2DB1' failed. Please verify that the Microsoft Search (Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: Therevwas no endpoint listening at net.tcp://localhost:17063/Management/SeedingAgent-0A2745DF-4522-42AB-9115-5DDE9EDEF1C612/Single that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details..
[PS] C:\Windows\system32>

Dears,

i setup single Exchange 2013 (CAS/Mailbox) server,, and i used Outlook 2013 in Joined Domain machines, the profile configured automatically but once access the outlook every time i got password prompt then i type and could access

this is Exchange 2013 CU5 , INTENRALClient authentication is set to NTLM ,  no external Outlook anywhere configured,  IIS authentication is set to basic, ntlm, negotiate..

i tested in test lab and worked charm,, but i don't know what is the issue in Production server

your help is appreciated

Hi,

Is there any special things that I should think before migrating users? The current situation is that we have Exchange 2010 in AD.old domain. All the users have been migrated wito AD.new domain with SID history, and the mailboxes have been converted to linked mailboxes. There is trust between these domains, and they are different forests.

We want to abandon our Exchange 2010, and I’m thinking  to set up a new Exchange 2013 in the AD.new domain, and move mailboxes to that.

Will the mailboxes be connected directly the users in AD.new domain, or will they linked mailboxes? Anything else to think of with this upgrade/migration project, or is this similar process than upgrading 2010 to 2013 in the same domain?

Thanks,

Jouko

Hello All,

Recently we've upgrade our Exchange 2013 SP1 servers to CU5 but we are having very slow response while opening ECP & Powershell. MS support team says its known issue and only CU6 can support on this

Is there anyone here also facing the same issue post CU5 upgrade? If yes, is there any workaround or permanent solution available to overcome this situation

Vinoth Kumar. M

Hi,

I have a quick question for you regarding upgrading Exchange 2007 to 2013. I know there is no actual upgrade path from 2007 to 2013 so I am looking at this from a slightly different way.

My current Exchange server is sat on a Windows 2008 x64 Enterprise Server which has 2 quad core Xeon 2ghz processors and 20Gb of RAM, the only problem it has is a shortage of space on the C Drive.

Having given several options to my boss he has agreed that a new Windows Server with Exchange 2013 is the way ahead for us but because we only have around 30 users and because I do not think the server is that bad a spec I had a different idea.

I thought that if I could migrate everything from the exchange server to another format I could then bang some bigger drives in the old server and reinstall it as 2012 and then install the new version of Exchange on this new platform.

So my question is this. Is this feasible/sensible? If so how do I go about exporting all the exchange data I need ready to import into the new version of Exchange?

I know I could go to Office 365 but at this time we do not want to do this.

Thanks for your help,

alamb200

I am getting the following error when I'm setting up the mailbox server as I'm currently doing a test virtual machine throughHyper-V, it seems to happen during the transport service phase of the installation which is 7/12

Do i know need a D:\ drive for the mailbox server to work? as in my test i only have a c:\ drive but no d:\ drive

Error:
The following error was generated when "$error.Clear();
            if ($RoleProductPlatform -eq "amd64")
            {
                $useAttachMode = $false;
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                $dataFolderPath = $fastDefaultDataFolderPath;

                if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                {
                    $useAttachMode = $true;
                }
                else
                {
                    if ($RoleIsDatacenter -eq $true)
                    {
                        $preferredDataFolderPathRoot = "D:\";
                        if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                        {
                            $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                            {
                                $useAttachMode = $true;
                            }
                        }
                    }
                }

                if ($useAttachMode -eq $true)
                {
                    &$command -action a -dataFolder $dataFolderPath -silent;
                }
                else
                {
                    try
                    {   
                        &$command -action i -dataFolder $dataFolderPath -silent;
                    }
                    catch
                    {
                        $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $errorMsg;
                        &$command -action u -silent;
                        try
                        {
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                            {
                                [System.IO.Directory]::Delete($dataFolderPath, $true);
                            }
                        }
                        catch
                        {
                            $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath+ " - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $deleteErrorMsg;
                        }
                    }
                }
            }
        " was run: "Couldnít attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnít contain old nodes belonging to the system 'Fsis'.".

Warning:
An unexpected error has occurred and a Watson dump is being generated: The following error was generated when "$error.Clear();
            if ($RoleProductPlatform -eq "amd64")
            {
                $useAttachMode = $false;
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                $dataFolderPath = $fastDefaultDataFolderPath;

                if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                {
                    $useAttachMode = $true;
                }
                else
                {
                    if ($RoleIsDatacenter -eq $true)
                    {
                        $preferredDataFolderPathRoot = "D:\";
                        if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                        {
                            $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                            {
                                $useAttachMode = $true;
                            }
                        }
                    }
                }

                if ($useAttachMode -eq $true)
                {
                    &$command -action a -dataFolder $dataFolderPath -silent;
                }
                else
                {
                    try
                    {   
                        &$command -action i -dataFolder $dataFolderPath -silent;
                    }
                    catch
                    {
                        $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $errorMsg;
                        &$command -action u -silent;
                        try
                        {
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                            {
                                [System.IO.Directory]::Delete($dataFolderPath, $true);
                            }
                        }
                        catch
                        {
                            $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath+ " - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $deleteErrorMsg;
                        }
                    }
                }
            }
        " was run: "Couldnít attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnít contain old nodes belonging to the system 'Fsis'.".

Hi,

I have Exchange 2010 with Sp3 Currently running in environment, Now we have plan to Migrate it to Exchange 2013.... Total number of mailbox is around 26000.

Before Migration we want below things to keep in mind...

1. We want to Use existing exchange 2010 OWA url ( mail.abc.com ), How to accompolish this as it will take couple of months to migrate all mailbox ?

2. Can i use my Existing Exchange certificate to get the above goal done ?

3. What will be the steps and pre-requsite to achieve the Goal ?

An Early reply would be appreciated !! 

Amit

Hi,

What is command & Steps to configure CAS Array in Exchange 2013 ?

Regards, 

Amit

Exchange 2013 CU6

When i first setup my 2013 servers, it looks like exchange went to my internal CA for each exchange server and got a cert for its self.

On the mailbox servers the cert has its self set for IMAP,POP,IIS,SMTP and it doesn't really appear to be editable.

On the cas servers this cert seems to have IMAP,POP,SMTP and it doesn't look like i can unselect those services.

These certs are going to expire soon and im not sure how to go about renewing/replacing them... since it looks a little different then doing the cert for OWA/ActiveSync.

Any help would be great.

Thanks

Systems Administrator