Greetings all,

I've got a new Exchange 2013 setup and external internet users have been reporting that attachments they receive from internal users are showing only as winmail.dat (why does this problem still exist?!?)

In Exchange 2010 I had a transport rule that sent *everything* to the internet as plain-text to stop this happening, but I can't seem to find any info on how to do this in Exchange 2013. There's no obvious options in the ECP, so I'm guessing it's a powershell command?

Hello Friends.

I am migrating from Exchange Server 2010 to 2013, with coexistence. This is my first migration and I am having doubts about autodiscover settings. Here we go...

The scenario is as follows:
Two forests/Two Exchange:
contoso.local - Exchange 2010
adatum.com - Exchange 2013

What step am I in?
As my client ran ADMT first, instead of running the prepare move reques, I enabled all users of adatum.com as mailusers, then run the prepare with the attributes -OverwriteLocalObject -UseLocalObject, so far so good.

I was able to execute the move successfully.

My doubt is: After the process of performing the move, at the end, the account takes about 5 minutes to identify the changes, I do not think that normal, I think it's missing some configuration on autodiscover.

Remembering that the workstations are in the domain contoso.local trying to access a mailbox on domain adatum.com

What would be the step-by-step autodiscover configuration between environments 2010 and 2013? With workstations applied on these two domains?

Hi all,

We've moved our entire mailbox workload into O365. Our setup looks like this:

Old Exch 2010 standalone server

Exch 2013 DAG (2 members split over 2 data centres)

2 Exch 2013 CAS (2 members split over 2 data centres)

2013 uses a hybrid connector.

Due to old hardware, we need to come off one of the Exchange 2013 MBX and CAS servers so my plan is to decommission 1/2 of the 2013 estate by using this guide as a reference: http://practical365.com/exchange-server/exchange-2013-how-to-remove-dag-member/

Our mail flow in and out goes directly via our anti-spam provider so none of the internal CAS are used anymore so I'm thinking that all I have to do to uninstall is remove the database copies from the MBX server I want to remove from the DAG and then uninstall via add/remove programs. Uninstall the CAS using add/remove programs too and then remove the computer objects from AD.

The servers I'm looking to uninstall have been off for almost a week now without any fall out reported. Essentially what I will be left with is a 1 member DAG, which sounds pointless but this will be purely used for management tasks.

I trust its safe to uninstall the CAS and MBX servers, are there any gotchas I might want to look out for?

I'm attempting to upgrade Exchange 2013 and am seeing the following error message. I've been unable to get past it and haven't found any helpful information in my research on what to do. Thoughts?

Welcome to Microsoft Exchange Server 2013 Unattended Setup
Languages
Mailbox role: Transport service
Client Access role: Front End Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Management tools
Client Access role: Client Access Front End service

Performing Microsoft Exchange Server Prerequisite Check

    Configuring Prerequisites                                                                         FAILED
     The following error was generated when "$error.Clear();
          if (Get-Service WinMgmt* | ?{$_.Name -eq 'WinMgmt'})
          {
            Set-Service WinMgmt -StartupType Automatic
            Start-SetupService -ServiceName WinMgmt
          }
        " was run: "Service 'Windows Management Instrumentation (WinMgmt)' cannot be configured due to the following err
or: Access is denied".

    Prerequisite Analysis                                                                             COMPLETED

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

Hello All............I have following questions with respect to Accepted Domain and External URL.

1.  Is it possible to have different Accepted Domain (abc.com) and External URL Domain (https://webmail.xyz.com/owa)?

2.  If so, what steps would be necessary?

3.  If we want to do that afterwards that is separating Accepted Domain and External URL Domain, what steps would be necessary?

3A.  Would generating CSR, Importing and Assigning Certificate; and changing the External URL do that trick? Would there be anything else needed?

Thanks in advance. 

Hi

I want to install exchange server 2013 on a VM Server 2012r2 with Hyper-V, because a previous installation on the physical machine was damaged. The physical machine  is also the domain controller and the file server of the company, and before the exchange damage every client after connecting with the domain was using the Outlook 2010. Its an intranet with no internet connection. I haven't got another machine to migrate. I want the users as before to have same credentials on Outlook with the domain and to migrate the old mailboxes to the new VM.

thanks.

Regards, Kesavan K M. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello All.........I have few questions with respect to Licensing:

1.  What are the bare minimum licenses needed for Microsoft Exchange Server 2013/2016?

1A.  Do we need any one from Server Standard OR Server Enterprise?

1B.  Do we need any one from Standard OR Enterprise CALs?

1C.  Do we need Windows Server Client CALs as well?

1D.  In what scenarios, we need client CALs for Windows Server?

tHANKS IN ADVANCE.

Hello all,

We are looking to upgrade our Exchange 2013 environment. We have 3 CAS servers that are behind a Load Balancer and 3 Mailbox servers in a DAG. If we were to upgrade our current Exchange setup, is it safe to upgrade from Exchange 2013 SP1 to CU15? Has anyone done it already? What issues will I face? Should we do an incremental upgrade to  CU6 and then to CU15?

My other option would be to stand up 3 new Exchange 2016 servers and then migrate everything to the new servers. Currently Exchange CU4 is out. Are there any major issues I should be mindful of if we go this route?

Would be interested to hear from someone that has already gone through the two options above from the version of Exchange we are on. 

TIA,

TD

Looking to install Exchange 2013 on a new physical server.

The old ways said put the Operating System on the C: and Exchange databases and such on the D:

I'm now see conflicting views - seems now with the larger drives and faster systems that for a small business; putting everything on a large C: drive is the way to go. Keep it simple is what I have seen for this.

Our company will never be more then 125 users and pretty light email senders.

Does it make sense now to just setup the new server with a large RAID 6 C: drive and install everything there.

Thanks for any responses,

Hi All,

Good Day!!!,

Scenario Explanation:

We have 2 Data Centers in 2 different geographical locations

We have single AD forest 

Data Center-1 we are installed Exchange 2013 CU10 with IP less DAG and enabled mailbox for all the users in the organization

Currently our organization has planned to setup Exchange server at Data Center-2 and move some mailbox users who are belongs to Data Center-2 site.

My Query is :

If we setup Exchange server in Data Center-2 with IP Less DAG and Configure Database then how can we move the mailbox from Data Center-1 to Data Center-2 site , is that the same migration batch we can use?

What about the Email Flow, The respective send/receive Connectors will be updated and new server name added into that

What about GAL / Address book for Data center-2 site?

What are the best practice & pre-requisites for this setup?

Since then worked with single site DAG exchange environment this is something new for me, so that looking for some guides from the experts.

any Technet article , document shared  it will help me lot.

thanks in advance.

Regards,

Regards, Kesavan K M. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi,

I had completed the hybrid mode on my Exchange server 2013, which is working on all.

After I changed my public IP addresses (1 x public IP address is one to one mapping to Exchange server; 1 x public address is Firewall outside interface (NAT PAT)). Now, I cannot migrate back the online user to Exchange on-perm. as the below error.

I really don't know why just change the public IP addresses, then cannot work on the hybrid communication?

I got this error while installing second Exchange 2013 on same DC.

Please help me, how to get rid of this error.

Appreciated your reply..

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'.".

Regards, Kesavan K M. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I am performing a migration from Exchange 2007 to Exchange 2013. The  legacy Exchange 2007 environment has 2 CAS & 2 MBX servers, there is no load balancing solution in place. The users currently connect to a single CAS through autodiscover. 

Legacy Exchange 2007 

exch1.company.com - MBX
exch2.company.com - MBX
exch3.company.com - CAS/Hub
exch4.company.com - CAS/Hub

Exchange 2013

The Exchange 2013 solution is 2 x multi-role Exchange servers and DNS is to be used for load balancing. 

exch5.company.com - Multi-role
exch6.company.com - Multi-role

mail.company.com - new load balanced unified namepspace. 

https://blogs.technet.microsoft.com/exchange/2014/02/28/namespace-planning-in-exchange-2013/

All of the reading I have done with regards to namespace planning, is that I need to reconfigure the legacy Exchange 2007 servers with a legacy namespace:   e.g. legacy.company.com

In this case, I am planning to implement a new namespace, therefore there is no conflict between legacy and new environment. Therefore on the new SSL certificates for Exchange 2013 and legacy Exchange 2007, I am planning to include the following SANs. I don't see any requirement to replace legacy URLs given there is no conflict? 

mail.company.com                         (Load balanced Exchange 2013) 
autodiscover.company.com             (autodiscover for Exchange 2013)
exch1.company.com                       (Legacy FQDN for Co-existence)
exch2.company.com                       (Legacy FQDN for Co-existence)

Is my thinking correct or is there another reason why I would need to reconfigure legacy URLs ? 

Thanks,

Brian

Regards, Kesavan K M. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Good Morning,

We are deploying Exchange 2013 CU 14 as a hybrid server to replace the existing Exchange 2010 hybrid that is in place at the moment. As part of the Exchange 2013 installation, I need to prepare and update the AD schema for the additional attributes required by Exchange 2013.

I have a process detailed on how this will play out but have questions around using snapshot in VMware as a recovery method.

The forest contains three domain controllers and the DC upon which the changes will be made is the least utilised and will have replication inbound and outbound disabled prior to running the PrepareSchema and PrepareAD switches on the Exchange setup.exe.

My question is whether the snapshot would be a supported method of rolling back the DC in the event of the schema update causing corruption? The forest contains services such as System Centre which are sequence sensitive and my concern is that by rolling back the snapshot, we may introduce problems with USN's and sequence sensitive processes. There will also be BMR, System State and Service Database backup's taken immediately before but I'm ultimately trying to avoid having to invoke forest recovery by hopefully using the snapshot.

I am attempting to setup Exchange in a lab.

Right now I have a Server 2008 and Server 2003.

I installed Exchange 2013 on the Server 2008 box and I am getting a Global catalog error. I can not authenticate to active directory.

Server 2008 has a domain and was replicated to the 2003 box.

I think during this replication process my DNS broke.

I am not so familiar with DNS and not sure how to ensure my records are correct.

nltest /dsgetdc: /site:<site name>

returns

Getting DC name failed : Status = 133 0x64b ERROR_NO_SUCH_DOMAIN

Hi all,

Due to the POODLE vulnerability and TLS 1.0 showing as enabled on one of our external scans, we were informed that we would need to disable SSL 3.0 and TLS 1.0 on our Exchange server.

Apparently, this wouldn't even be possible until Update Rollup 9 was released on 3/16/15:

Rollup resolves:

KB 3029667 SMTP is not transported over TLS 1.1 or TLS 1.2 protocol in an Exchange Server 2010 environment

After installing this update, SSL 3.0 and TLS 1.0 were disabled and the servers rebooted (cross site, same domain, two Exchange servers).  After resolving some issues with certificates that apparently broke as a result of the changes, we found that EWS was not working - the log full of these errors: