Restore Exchange Server 2013

Hi
My Exchange server 2013 is running in Windows server 2012 evaluation version and because of evaluation version I cant activate domain controller .I have only one HP Server so kindly advise how to backup exchange server in to temporary server and restore
to HP Server.
Thank You,
Arafath

Hi Arafath,
I suggest using Windows Backup method to back up the Exchange server.
More details in the following articles:
How to back up and restore an Exchange computer by using the Windows Backup program
https://support.microsoft.com/kb/258243/en-us
Overview of Exchange Server Backup Methods
http://technet.microsoft.com/en-us/library/aa996125(v=exchg.65).aspx
Using Windows Server Backup to Back Up and Restore Exchange Data
http://technet.microsoft.com/en-us/library/dd876851(v=exchg.150).aspx
However, I still suggest we restore our Exchange 2013 Server into Windows Server.
Windows Server 2012 Standard or Datacenter
Windows Server 2008 R2 Standard with SP1
Windows Server 2008 R2 Enterprise with SP1
Windows Server 2008 R2 Datacenter RTM or later
More details in the following article:
Exchange 2013 System Requirements
http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
Please notice the "Operating System" session.
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

Exchange Server 2013: no send/receive after failed CU1- CU2 and machine restore

Hi!
For several reasons, I decided to fully restore my Exchange Server 2013 machine today.
The machine is virtualized on Hyper-V.
I rebooted the server and recovered from backup and Exchange seems to be working fine. However, I cannot receive or send mail. If I try to send a message it goes to the "drafts" folder. OWA and EMC is working. I can not send mail between interna mailboxes
either. Outlook says disconnected.
When running the Exhchange Connectivity Analyzer, I get the following:
- Receive: Connection was successful but no banner was received.
- Send: Successfull. However when trying to send mail to external mailbox it does not reach that mailbox.
Mailflow was working perfectly at the time of the backup.
Help is much appreciated!
UPDATE 1: When telnet on local server i get SMTP banner. But not on other computers in same subnet.

OK. After fiddeling around in ADSIedit and trying to rebuild my Exchange environment I ended ut breaking it completely.
I then restored both my DC (Exchange schema CU2) and my EX (Exchange schema CU1). Scema Versions where the inconsistent as stated.
Then I uninstalled the KB2874216 successfully. After that i tried to Upgrade Exchange to CU2. The Upgrade failed at Mailbox Role: Mailbox Service With error Message:
The following error was generated when "$error.Clear();
          if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
            if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
              $sysMbx = $null;
              $name = "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}";
              $dispname = "Microsoft Exchange";
              $mbxs = @( get-mailbox -arbitration -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
              if ( $mbxs.length -eq 0)
                $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                if ($dbs.Length -ne 0)
                  $arbUsers = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                  if ($arbUsers.Length -ne 0)
                    $sysMbx = enable-mailbox -Arbitration -identity $arbUsers[0] -DisplayName $dispname -database $dbs[0].Identity;
              else
                if ($mbxs[0].DisplayName -ne $dispname )
                   set-mailbox -Arbitration -identity $mbxs[0] -DisplayName $dispname -Force;
                $sysMbx = $mbxs[0];
              # Set the Organization Capabilities needed for this mailbox
              if ($sysMbx -ne $null)
                  Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
                  set-mailbox -Arbitration -identity $sysMbx -UMDataStorage:$true -Force;
                  # No RetentionPolicy assigned to E-Discovery arbitration mailbox currently, we need to set it here.
                  # This can be remove after BUG(O15#2555914) is fixed.
                  if ($sysMbx.RetentionPolicy -eq $null )
                     $arbitrationRetentionPolicy = @(Get-RetentionPolicy -DomainController $RoleDomainController | where {$_.Name -eq 'ArbitrationMailbox'});
                     set-mailbox -Arbitration -identity $sysMbx -RetentionPolicy $arbitrationRetentionPolicy[0].Identity -Force;
              else
                Write-ExchangeSetupLog -Info ("Cannot find E-discovery arbitration mailbox with name=$name.");
            else
              write-exchangesetuplog -info "Skipping creating Discovery Arbitration Mailbox because of insufficient permission."
        " was run: "Database is mandatory on UserMailbox. Property Name: Database".
Seems the problem was corrupted arbitrary system mailboxes from previous Exchange 2010 to Exchange 2013 migration.
The solution for me was to restore the corrupted arbitrary mailboxes using this
LINK. It is for 2010 but Works on 2013.
I am now currently on Exchange CU2 on both my EX server and on my DC. Now I have to check mail flow and will report back.

Exchange Server 2013 Update from to CU3 to CU8 stuck, Exchange completely down

Hello,
We tried to update a Exchange 2013 server to CU8 because we needed support from Microsoft (certificate revoked, so OWA not working anymore) and they could only help us after updating to CU8 first. The problem is that the update got stuck and now Exchange
is not working at all anymore. Since it is a production enviroment and there is mail in all outboxes we do not want to turn back to a snapshot but solve the problem and continue the update. Any help is welcome because all mail is down now :-(
The error we received at the Exchange Server is:
C:\Users\administrator.DOMAINNAME\Downloads\Exchange-cu8>setup.exe /m:upgrade /In
stallWindowsComponents /IAcceptExchangeServerLicenseTerms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 8 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
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 COMPLETED
Prerequisite Analysis COMPLETED
Configuring Microsoft Exchange Server
Preparing Setup
COMPLETED
Stopping Services COMPLETED
Language Files COMPLETED
Removing Exchange Files COMPLETED
Preparing Files
COMPLETED
Copying Exchange Files COMPLETED
Language Files COMPLETED
Restoring Services COMPLETED
Language Configuration COMPLETED
Mailbox role: Transport service FAILED
The following error was generated when "$error.Clear();
$connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g
t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 }
" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei
veConnectorRoleConflictException: The values that you specified for the Bindings
and RemoteIPRanges parameters conflict with the settings on Receive connector "
SERVER-EXCHANGE\Externe POP3 mailboxen". Receive connectors assigned to differen
t Transport roles on a single server must listen on unique local IP address & po
rt bindings.
bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio
n, ErrorCategory errorCategory, Object target, String helpUrl)
bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio
n, ErrorCategory category, Object target)
bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto
r.InternalValidate()
bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu
ncName, Action func, Boolean terminatePipelineIfFailed)".
The following error was generated when "$error.Clear();
$connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g
t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 }
" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei
veConnectorRoleConflictException: The values that you specified for the Bindings
and RemoteIPRanges parameters conflict with the settings on Receive connector "
SERVER-EXCHANGE\Default Frontend SERVER-EXCHANGE". Receive connectors assigned t
o different Transport roles on a single server must listen on unique local IP ad
dress & port bindings.
bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio
n, ErrorCategory errorCategory, Object target, String helpUrl)
bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio
n, ErrorCategory category, Object target)
bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto
r.InternalValidate()
bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu
ncName, Action func, Boolean terminatePipelineIfFailed)".
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Hello Gadget,
Please find the solution as follows
This error is concern about WMSVC certificate which was deleted, we could refer to the following steps:
1- Go to IIS Manager and select server certificate,
2- Select “Create Self-Signed Certificate”,
3- For Server 2012 in the Friendly Name Field type: WMSVC and select the personal (certificate Store),
4- Now go to ” Management Service”,
5- From SSL Certificate choose the newly create “WMSVC” Self-Signed Certificate,
6- Apply,
7- Now start service of “Web Management service”.
https://social.technet.microsoft.com/Forums/office/en-US/eac00dc2-6e43-45ae-939c-aad82a144908/cu8-install-fails?forum=exchangesvrgeneral
Exchange Queries

Exchange Server 2013: Installation fails

Migrating SBS 2008 to Windows Server 2012 R2 (no virtualization) and Exchange Server 2013 SP1
(1) ADprep on SBS 2008 went fine
(2) Installed necessary feature for Exchange (website “Part 1: Step-by-Step Exchange 2007 to 2013 Migration”)
A) the first time I installed Exchange 2013, the setup succeeded, however there were several ecp/WinRM errors.
B) restored Windows Server 2012 R2 to the state (2). Removed from AD (ADSI Edit)
… CN=Services; CN=Exchange; CN=First Organization; CN=Exchange Administrator Group; CN=Servers
delete new Win 2012 server
Run Exchange setup again:
The following error was generated when "$error.Clear();
if ($RoleStartTransportService)
start-SetupService -ServiceName MSExchangeTransport -MaxWaitTimeForRunningState 0:0:40
" was run: "Service 'MSExchangeTransport' failed to reach status 'Running' on this server.".
Checked:
- IPv6 is enabled, but was setup correctly after installing ADDS role)
- Administrators (Group) is a member of the Exch. Trusted Subsystem
Probably there is an AD problem, after the restoration (B) (bare metal) of the Win 2012 server.
Please help!
Fulco

Hi
the error states that the MSExchangeTransport service failed to start. Can you manually try starting the service and then run the setup again?
Hope this helps. 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.

Mails struck in Drafts folder after Transport Agent installed in Exchange Server 2013

Hi all,
I created Transport Agent and installed successfully in exchange server 2013.
After that mails are struck in drafts folder.
I thought because of My Custom transport Agent , then i Uninstall Transport agent.
but still no use.
I restart Microsoft Exchange Transport Service and restart my server also.
Here is the code i used
public sealed class MyAgentFactory : RoutingAgentFactory
public override RoutingAgent CreateAgent(SmtpServer server)
return new MyAgent();
public class MyAgent : RoutingAgent
public MyAgent()
this.OnSubmittedMessage += new SubmittedMessageEventHandler(this.MySubmittedMessageHandler);
public void MySubmittedMessageHandler(SubmittedMessageEventSource source, QueuedMessageEventArgs e)
e.MailItem.Message.Subject = "This message passed through my agent: " + e.MailItem.Message.Subject;
I search in google about mails struck in drafts folder, all replies are
restore Default Receive Connectors. How can i restore it.
here is the link i see
http://community.spiceworks.com/topic/309145-exchange-2013-messages-stuck-in-drafts

Hi Martina
Miskovic,
Here I am facing some weird situation.
Mails again stuck in Drafts folder.
i didn't installed anything. just checking again after some
time gap .
I tried again by restarting all services
, but no use.

Recover mailbox from Exchange server 2010 information store to exchange server 2013

I have a big issue. I have a correct exchange server 2010 where the active directory is corrupt but the information store is good.
I would like to recover a couple of mailboxes to an exchange server 2013.
Can anyone give me a detailed walk through of how I can accomplish this?
Thank in advance

Well if your AD is messed up that leaves you in a jam for sure because;
1. Database portability ONLY works within the same organization, so you cannot just install a new 2010 server in a completely different forest and then move the DB in hopes that DB portability will work.
2. As Ed said you should build a new Exchange 2010 server and use portability but it has to be in the same organization.
3. Here is a good article on how to accomplish
http://exchangeserverpro.com/exchange-2010-database-portability-disaster-recovery/
4. Now if you by chance have an AD backup before it went south you could build a separate network with same names etc just keep it isolated from the production server and then restore AD to that environment and you could then use DB portability.
That said if you don't have any other machines to work with then you are in a bit of a pickle and will have to use a 3rd party product to get to that data within the 2010 DB. We make a product that can do this (DigiScope), however if you don't
have any budget to handle its a non-issue.
The only other thing you could consider is to restore your AD from a previous point in time, however BE VERY CAREFUL if you consider this since it could cause more issues then you have now.
BTW if you AD is messed up, where are you putting this new 2013 server?
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Backing up Exchange Server 2013 CU3 with Windows Server Backup Program

Looking at configuring Windows Server Backup Program to backup Exchange Server 2013 CU3 which is a member a DAG Group using a specific Backup Domain Account.
From my understanding from the following technet Article" Using Windows Server Backup to Backup and Restore Exchange Data" at http://technet.microsoft.com/en-us/library/dd876851(v=exchg.150).aspx I cannot use wbadmin.exe has it uses an older
unsupported version of Powershell.
My question is what are the minimum AD rights required for an AD account needed to be able to backup/restore Exchange Datastore using Windows Server Backup Program in Windows Server 2012?
Thanks,
NIck

Hi Sathish,
After looking at your response, it all make sense except when I look at what exchange right assigned via RBAC. I understand that the backup service account will require access to the exchange databases
to be able to backing and restoring them. After looking at the different roles
I'm wondering if I require to assign both the Databases roles for Backing up the databases and the Disaster Recovery Role as well to be able to restore the databases has well as having a mailbox on the exchange
server for the backup service account?
Below is explanation of the roles via the ECP
Database Role
This role enables administrators to create, manage, mount and dismount mailbox and public folder databases on individual servers.
Disaster Recovery
This role enables administrators to restore mailboxes and database availability groups in an organization.
Thanks,
Nick

Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

Hi Team,
Need urgent help in resolution of following error:
Environment Details: VMware ESXi 5.5 (vMotion)
Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
Prerequisites: Installed
Error: Installation gives Error at Step 10 during installation of Mailbox Service
Error Details Below:
Error:
The following error was generated when "$error.Clear();
if ([Environment]::OSVersion.Version.Major -ge 6)
$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
$reg= join-path (join-path $env:SystemRoot system32) reg.exe;
$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
if ((get-service wsbexchange).Status -eq "Running")
Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
Exchange /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
" was run: "Process execution failed with exit code 1.".

Resolved ! :)
Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
Thanks to all.

Exchange Server 2013 Client Mail are Return.Error is [0x80040305-0x0004de-0x00054a]

Hi,
We are using Exchange Server 2013.we have Outlook 2007 SP3 and 2010 SP2 client .Some clients inform mails are return.
Return massage
"This message could not be sent. Try sending the message again later, or contact your network administrator. Your server administrator has limited the number of items you can open simultaneously.
Try closing messages you have opened or removing attachments and images from unsent messages you are composing. Error is [0x80040305-0x0004de-0x00054a]"
Thanks,
Gayan

1) Disable TCPChimney and RSS on CAS and Mailbox Servers by running below commands
netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled
2) Disable unwanted Add-Ins in outlook that may open many sessions
3) If above steps doesnt resolve, you can delete existing outlook profile and create new Outlook online profile

How can I clone a completed Exchange Server 2013 in a Lab Enviroment?

I was having great time with my Exchange Server 2013 until I tried to clone it to avoid fresh installation of another Exchange 2013 server. Steps taken
(1)Clone the Exchange1 and turn it off
(2) Brought the Clone Exchange2, renamed it, change the IP configurations,
(3) Re-ran the ADprep/Doamin prep
(4) Checked the ASDIedit to verify the Schema/configuration in AD
(5) Restarted I and was able to logon to the Exchange2
(6) Brought up the Exchange1, but unable to logon because the name was no longer in AD database
What I did to fix this:
(7) Rejoin the Exchange1 to the domain - and was able to logon
(8) Unable to access ECP or OWA of any of the two servers.
(9) Errors received - Fix the configuration file of the application
My Question - How to I fix the configuration file as suggested (via powershell or GUI or ASDIedit.msc)?

Unless you are cloning an entire environment, and then bringing it up in a seperate isolated environment, it is not supported to simply clone an Exchange Server, and then bring it online in an existing environment and rename it to save on setup and configuration
time.
You can script the setup and configuration of Exchange through Powershell, either with scripts or with another product controlling it - something like
System Center Orchastrator.
From the script side of things there are many available on peoples blogs. Check
here.
Edit: and to be clear, there is no need to re-run any prep tasks against Active Directory when installing a new Exchange Server, unless you are installing into a new domain as part of your Forest.
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Exchange Server 2013 and Remote Access VPN on a single server running Windows Server 2012?

Just by way of background, I have been installing and administering network servers, e-mail systems, VPN servers, and the like for many years. However, my involvement with Exchange and Windows Server has been mostly on the forensics and data recovery
level, or as a (sophisticated) user. I have never tried to deploy either from scratch before. My deployment experiences have been mostly with Linux in recent years, and with small private or personal "servers" running such cutting edge
software as Windows XP back when it was new. And even NetWare once.
When a client asked me if I could set up a server for his business, running Exchange Server (since they really want Outlook with all of its bells and whistles to work, particularly calendars) and providing VPN access for a shared file store, I figured it
could not be too difficult given that its a small business, with only a few users, and nothing sophisticated in the way of requirements. For reasons that don't bear explaining here, he was not willing to use a vendor hosting Exchange services or cloud
storage. There is no internal network behind the server; it is intended to be a stand-alone server, hanging off a static IP address on the Internet, providing the entirely mobile work-force of about 10 people with Exchange-hosted e-mail for their computers
and phones, a secure file store, and not much else. If Exchange didn't need it, I would not need to install Active Directory, for example. We have no direct need for its services.
So I did the research and it appears, more by implication than outright assertion, that I should be able to run Windows Server 2012 with Exchange Server 2013 on a server that also hosts Remote Access (VPN only) and does nothing else. And it appears
I ought to be able to do it without virtualizing any of it. However, I have spent the last three or four days fighting one mysterious issue after another. I had Remote Access VPN working and fairly stable very quickly (although it takes a very
long time to become available after the server boots), and it has mostly remained reliable throughout although at times while installing Exchange it seems to have dropped out on me. But I've always been able to get it back after scrounging through the
logs to find out what is bothering it. I have occasionally, for a few minutes at a time, had Exchange Server willing to do everything it should do (although not always everything at the same time). At one point I even received a number of e-mails
on my BlackBerry that had been sent to my test account on the Exchange Server, and was able to send an e-mail from my BlackBerry to an outside account.
But then Exchange Server just stopped. There are messages stuck in the queues, among other issues, but the Exchange Administration Center refuses now to display anything (after I enter my Administrator password, I just get a blank screen, whether on
the server or remotely).
So, I am trying to avoid bothering all of you any more than I have to, but let me just begin with the basic question posed in the title: Can I run Exchange Server (and therefore Active Directory and all of its components) and Remote Access (VPN only) on
a single Windows Server 2012 server? And if so, do I have to run virtual machines (which will require adding more memory to the server, since I did not plan for it when I purchased it)? If it can be done, can anyone provide any pointers on what
the pitfalls are that may be causing my problems? I am happy to provide whatever additional information anyone might like to help figure it out.
Thanks!

An old thread but I ran into this issue and thought I share my solution since I ran into the same issue. Configuring VPN removes the HTTPS 443 binding on the Default Site in IIS for some strange reason; just go and editing the bindings, add HTTPS and things
should be back to normal.

Error when try to install exchange Server 2013 in windows server 2008 R2 Sp1

Hi
I'm getting these errors while trying to install Microsoft Exchange Server 2013 on my Windows Server 2008 R2 SP1 the user i'm using is the Administrator and it is already a member of "Enterprise
Admins" and "Schema Admins"
in my organization there is 6 Exchange server 2013 in 3 site windows server 2012 in this case
I have to install exchange 2013 in windows Server 2008 r2 sp1
the functional level 2008 R2 I getting these errors please help.
Errors:
This computer doesn't belong to a valid Active Directory site. Check the site and subnet definitions.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.InvalidADSite.aspx
Error:
A reboot from a previous installation is pending. Please restart the system and then rerun Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RebootPending.aspx
Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency. See the Exchange setup log for more
information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
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

I think it's from subnet in site and services
have 3 site A,B,C and new site is "D"I have problem in "D" site
A subnet is 10.33.50.0/24 AD 2012 ,exchange 2013
B subnet is 10.35.50.0/24 AD 2012 ,exchange 2013
C subnet is 10.36.50.0/24 AD 2012 ,exchange 2013
D subnet is 10.100.100.0/25 AD 2008 ,exchange 2013 error when install it
find event error
The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair
the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
test-SetupPrerequisites
{Roles={LanguagePacks, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport, Cafe}, LanguagesAvailableToInstall=True, DomainController=, CustomerFeedbackEnabled=True, ExchangeVersion=15.0.847.32, LanguagePackDir=D:\Exchange
Server Software, SufficientLanguagePackDiskSpace=True, ADInitError=Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites
or by rep, ScanType=PrecheckInstall, LanguagePackVersioning=True, HostingDeploymentEnabled=False, TargetDir=C:\Program Files\Microsoft\Exchange Server\V15, SetupRoles={LanguagePacks, AdminTools, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport,
Cafe}}

Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

What am I trying to do?
I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
error logs at the bottom of the page but the basics are in order it will throw which loop around are:
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
What am I running?
2 X DC on domain and forest functional level 2008R2 both writable
1 X fresh install of Windows 2012 R2 which is domain joined
What have I tried?
Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
Rebooted every server
Run setup as Administrator
My account is part of the domain Enterprise Admin group
Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
Computer Configuration Windows Settings
Security Settings + Local Policies
User Rights Assignment Mange auditing and security log
Turned off firewall on DC and Exchange Server even stopped the service
Turned off all AV on the DC and Exchange Server
Checked I could telnet to global catalog servers on port 3268 which I can
Checked the global catalog records existed in DNS which they all do
Done the obvious ping tests all round which confirms connectivity
Schema has been prepared using appropriate commands before running the setup exe
setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
Making sure the following path has full permissions:
EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Restarted Microsoft Exchange Active Directory Topology service
DcDiag all looks good
What have I noticed that is suspicious?
Microsoft Exchange Transport service will not start even though both of its dependences services have started:
Microsoft Filtering Management Service
Microsoft Exchange Active Directory Topology Service
It will eventually error with
“Windows could not start the Microsoft Exchange Transport Service on local computer
Error 1053: This Service did not respond to the start of control request in a timely fashion”
This error is from the GUI wizard itself:
Error:
The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
" was run: "System.Exception: Unable to set shared config DC.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Exchange logs which have been written:
**The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
[01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
'{ mydomain.com}'
[01/20/2015 17:13:20.0084] [2] User specified parameters:
-DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
[01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
[01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
Windows Event Viewer:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
in either the local site 'Default-First-Site' or the following sites:

Hi apl228,
1. Please make sure the IPv6 is enabled.
2. Please make sure the account that install Exchange server has Administrator permission.
3. Please make sure DNS has been configured correctly.
Thanks
Mavis Huang
TechNet Community Support

How can i get newly added contacts for a Mailbox User in Exchange Server 2013

Hi all,
I need to synchronize contacts in Exchange Server and Sugar CRM Application, for that
i need to get newly added contacts for a User in Exchange Server 2013 by using EWS Managed API.
I know how get the list of all contacts for a particular user , but in the list how i can find
new contacts ?

Hi Dora,
that's the fun thing:
You add your own property (and it'll be invisible to outlook users, not to worry).
Extended Properties allow you to define custom property on Exchange Items. And it has a
method for setting those too.
Here's a short post doing a very simple intro on using Extended Properties.
Glen's Exchange Blog is a generally useful resource when working with EWS, I'm confident you'll be able to find lots of tips there as well.
Cheers,
Fred
There's no place like 127.0.0.1

Best practice on mailbox database size & we need how many server for deployment exchange server 2013

Dear all,
We have an server that runs Microsoft exchange server 2007 with the following specification:
4 servers: Hub&CAS1 & Hub&CAS2 & Mailbox1 & Mailbox2
Operating System : Microsoft Windows Server 2003 R2 Enterprise x64
6 mailbox databases
1500 Mailboxes
We need to upgrade our exchange server from 2007 to 2013 to fulfill the following requirment:
I want to upgrade the exchange server 2007 to exchange server 2013 and implement the following details:
1500 mailboxes
10GB or 15GB mailbox quota for each user
How many
servers and databases are
required for this migration<ins cite="mailto:Mohammad%20Ashouri" datetime="2014-05-18T22:41"></ins>?
Number of the servers:
Number of the databases:
Size of each database:
Many thanks.

You will also need to check server role requirement in exchange 2013. Please go through this link to calculate the server role requirement : http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
2TB is recommended maximum database size for Exchange 2013 databases.
Here is the complete checklist to upgrade from exchange 2007 to 2013 : http://technet.microsoft.com/en-us/library/ff805032%28v=exchg.150%29.aspx
Meanwhile, to reduce the risks and time consumed during the completion of migration process, you can have a look at this proficient application(http://www.exchangemigrationtool.com/) that would also be
a good approach for 1500 users. It will help you to ensure the data security during the migration between exchange 2007 and 2013.

Restore Exchange Server 2013

Similar Messages

Maybe you are looking for