Exchange Server 2013 non-unicode

Hi
i am facing problem with notification (emails) from the ERP system in Arabic language as below, am already configured the exchange to accept traffic from the ERP system
from : admin
to : ÇäÌÒÇÑ, êÇÓÑ
ID: 59
Although Arabic character set is correct into ERP, If i changed the language for non-unicode programs locally on the exchange server shall this change will affect
on the exchange or the users messages
Appreciate your help
BR
Mahmoud

Hi
any one can help plz ?
BR
Mahmoud
Mahmoud

Similar Messages

Exchange Server 2013 SP1 - Readiness Check Failing - Detected Non-existent Exchange 2007 Servers

For development purposes, I needed to install Exchange Server 2013 in our environment. Our current environment includes a couple Domain Controllers, a Sharepoint Server, and a SQL Server. So, it's got a very simple topology. The one thing
our environment does NOT have are current Exchange servers.
During the "Prerequisite Analysis" phase of the install it complained that two servers, that I can find nowhere in our active directory domain, are running Exchange 2007. Obviously, this presents some unique problems. Perhaps as a test
many years ago, someone installed Exchange 2007 to "play" with, but we've never run Exchange for any length of time.
So, this is quite the conundrum, given the above does anyone have any suggestions as to a potential solution? Ideally, I'd like to be able to "lift the covers" and cleanup the references to the non-existent servers somehow, but ANY suggestions
for fixes are MUCH appreciated.
Cheers,
Nate

Here is the thing I would do (Only if I am not going to have any exchange 2007 ever in the environment).
On any of windows server 2008 download
Exchange 2010 SP3
Extract the file and run the below command:
Setup.com /ps
This will make Exchange 2013 install. Also Deleting Exchange Administrator Group wouldn't help as Setup will look for the information about schema into AD.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange Server 2013 does not deliver mail as they arive.

I need Help and guidance on this problem. I have installed Exchange server 2013 with SP1 on Server 2012. Install Went perfect no error. It on a server with 2 TB storage. 16G
memory. Exchange 2013 is the only application running on the box. DNS service is also running on the box. I can see the mail arrive in the mail Box Queue with the Queue Viewer and they would just sit there and then after a 15 to 30 min delay it release the
mail to the mail boxes. The only error or warning I am seeing in the logs are the 6002 warning. Any suggestion would be greatly appreciated.

Please share message header of one of the delayed message. It will help to narrow down the issue.
Do you see any connection failures in connectivity logs.
Do you have multiple 2013 servers in your exchange environment ?
Lets fix it.
Received: from Xchngsvr.A.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
(xxx.xxx.xxx.xxx) with Microsoft SMTP Server (TLS) id 15.0.847.32 via Mailbox
Transport; Fri, 25 Apr 2014 13:31:33 -0400
Received: from Xchngsvr.a.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
(xxx.xxx.xxx.xxx) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 25 Apr
2014 12:30:44 -0400
Received: from xchngsvr.a.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
(xxx.xxx.xxx.xxx) with Microsoft SMTP Server id 15.0.847.32 via Frontend
Transport; Fri, 25 Apr 2014 12:30:37 -0400
Received: from mia0vm-cass03.colo.sonicwall.com ([208.17.117.5])
by
xchngsvr.a.com (SonicWALL 7.4.5.1391)
with ESMTP id 201404251630370000228;
Fri, 25 Apr 2014 12:30:38 -0400
Received: from mail1.fieldsolutions.com ([98.129.95.107])
by
mia0vm-cass03.colo.sonicwall.com (SonicWALL 7.4.4.8439)
with ESMTP id
201404251631070343409; Fri, 25 Apr 2014 09:31:07 -0700
Received: from localhost (localhost [127.0.0.1]) by mail1.fieldsolutions.com
(Postfix) with ESMTP id F32731031781
for <[email protected]>; Fri, 25 Apr 2014
11:31:06 -0500 (CDT)
MIME-Version: 1.0
To: <[email protected]>
From: Field Solutions <[email protected]>
Subject: WIN#: 649890 NEW Signage - Reply-To: <[email protected]>
Content-Type: multipart/alternative;
boundary="=_747eac72d0ea92652b25d7d469d7165b"
Message-ID: <[email protected]>
Date: Fri, 25 Apr 2014 11:31:06 -0500
X-Mlf-KeyWords: preapproved,dollars$$$,pay,toner,expectations,fl,dollars,guarantee,voltage,confi
X-Mlf-Language-Detected: NoLanguageFilter_English
X-Mlf-Connecting-IP: 50.244.134.141
X-Mlf-Country-Code: US
X-Mlf-Rules: rn;7.24
X-Mlf-Rules-Pos-Features: WORD_voltage_2.97;WORD_configuration_2.51;WORD_inputs_2.50;WORD_documentation_2.
X-Mlf-Rules-Neg-Features: WORD_preapproved_-1.85;SUBJ_dollars$$$_-1.74;SUBJ_pay_-1.56;WORD_toner_-1.53;WOR
X-Mlf-Sliderbars: N4,B4,S4,L4,Q4,G4,A4,I4
X-Mlf-Version: 7.4.4.8439
X-Mlf-Threat-History: nothreat
X-Mlf-Threat-Detailed-History: nothreat;none;none;none
X-Mlf-UniqueId-History: i201404251631070343409
X-Mlf-Connecting-IP: 208.17.117.5
X-Mlf-Country-Code: --
X-Mlf-Threat: nothreat
X-Mlf-Threat-Detailed: nothreat;none;none;cloud-nj
X-Mlf-UniqueId: i201404251630370000228
Return-Path: [email protected]
X-MS-Exchange-Organization-Network-Message-Id: 5ea15b9c-561d-4a2a-d03e-08d12ebad75d
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: Xchngsvr.a.com
X-MS-Exchange-Organization-AuthAs: Anonymous
There is only one Exchange server in the Organization

What is the order for upgrading exchange server 2013 SP1 servers to CU7?

Hi All
I am planning to upgrade my exchange server 2013 SP1CU4 to CU7 . As per my understanding , we always proceed with the CAS servers and then the Mailbox Servers during up-gradation.
But I am confused now , since I have seen articles stating , that the Mailbox servers has to be upgraded first and then the CAS servers in exchange 2013.
What will be the correct order . My environment consists of 2 Mailbox servers in DAG and 2 CAS servers (Exchange server 2013 SP1)
Thanks in Advance .
Joyso Senior Messaging Admin

Hi Joyso,
The Microsoft recommendation regarding the order in which the Exchange 2013 server roles should be installed or Upgraded is Mailbox and then CAS.
It makes sense as the CAS Role is a stateless server and all major components are held by the Mailbox Role.
Until a 2013 mailbox server comes online, the CAS server is pretty much useless. Hence, the recommended installation order in 2013 is the reverse of 2010 – Mailbox role first & then CAS
Note: If your DAG have more nodes, you need first upgrade all non-PAM nodes and then upgrade PAM node.
Some References:
The recommendation from the Product Group is to install Exchange 2013 Preview Mailbox Role first, and then the
CAS role.
If you're separating your server roles, we recommend installing the Mailbox server role first.
Upgrade your Exchange 2013 server roles in the required order. First, upgrade Mailbox servers
and then upgrade Client Access servers. -Upgrade DAG Mailbox servers
Exchange 2013 Server Roles Installation Order – Mailbox First:
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Issues trying to recover failed Exchange Server 2013 in a DAG

Having several issues attempting to recover a failed Exchange Server 2013. To start out, the failed server was mounted on a virtual server using hyper-v. The virtual server failed due to some hard drive partition issues and would no longer boot. As there
really was no purpose to having Exchange on a Virtual Server I decided to rename the host to the same name as the virtual server. I reset the name in AD and proceeded to rename the server. Then made sure all the necessary things were installed and proceeded
to do a recovery installation. I neglected to properly delete the old databases belonging to that server. I simply deleted the files off the hard drive instead of doing it properly. I should mention this is a two node plus witness server installation.Now,
it seems I cannot delete the former server in either ECP or command line. I have attempted to clean up the mess with the old databases but there is one that was mounted only on the failed server that I cannot remove. It seems until I can remove that, I cannot
remove the failed server from the DAG and do a recovery install. The steps shown in the tech net articles to remove a failed database have also failed. At this point I am wondering if I should just give up on the server name and do an install on a new server
name or if someone can give me some information on how to clean up the mess, that would be better I am sure. Here is a list of the things I have tried.
https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx and in this article, the item mentioned is not in ADSIedit.
http://exchangeserverpro.com/unable-remove-failed-server-dag-exchange-server-2010/
http://exchangeserverpro.com/exchange-2013-how-to-remove-dag-member/ This
article describes one of the problems I am having but the solution is not there.
Thanks to any and all who can offer advice.
Ronald C. Pope

Thank you for your answer. Running that command results in the following:
[PS] C:\Windows\system32>Remove-MailboxDatabase "Mailbox Database 0939719168"
This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes or
arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database"Mailbox Database 0939719168". To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of
archive mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Archive. To get a list of all
public folder mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -PublicFolder. To get a
list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Arbitration.
To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox
<Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox
<Mailbox ID> -Archive. To disable a public folder mailbox so that you can delete the mailbox database, run the command
Disable-Mailbox <Mailbox ID> -PublicFolder. Arbitration mailboxes should be moved to another server; to do this, run
the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command
Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox.
Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID>
-Database "Mailbox Database 0939719168".
    + CategoryInfo          : InvalidOperation: (Mailbox Database 0939719168:DatabaseIdParameter) [Remove-MailboxDatab
   ase], AssociatedUserMailboxExistException
    + FullyQualifiedErrorId : [Server=EX01,RequestId=69b60793-fc4f-4dac-beb9-8c9afe381a36,TimeStamp=1/26/2015 6:28:34
   PM] 2BA41E0C,Microsoft.Exchange.Management.SystemConfigurationTasks.RemoveMailboxDatabase
    + PSComputerName        : ex01.<domain>com
I was able to disable the one mailbox that was listed for the database. I got the following error when attempting the command Get-Mailbox -Database"Mailbox Database 0939719168"
[PS] C:\Windows\system32>Get-MailboxPlan Database "Mailbox Database 0939719168"
Get-MailboxPlan : The term 'Get-MailboxPlan' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
+ Get-MailboxPlan Database "Mailbox Database 0939719168"
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-MailboxPlan:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
the public folder and archive switch simply return a command prompt leading me to believe that there are no public or archive boxes on that database.
Ron

Exchange server 2013 - Setting up DAG

Hi Guys,
I have an Exchange 2013 server(a single dedicated box with all the roles(MailBox and Client Access) configured in it. Now I want to enable data redundancy and Failover. So, I want to setup a DAG and my idea is given below.
I Want to setup a 2 node DAG. The first node is my current working box and the second node is another box at a different location. I would then Install Exchange on the 2nd node with mailbox role on it. As it is a 2 node DAG, I would require another box as
a witness server.
Please let me know if there is any flaws with the above setup. Also, let me know if I require a different Exchange server license for the second installation.
Thanks and Regards,
Nash Burns

Hi,
From the article blow, we know a license must be assigned for each instance of the server software that is being run. The second Exchange server need a license.
Exchange Server 2013 licensing
http://office.microsoft.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview-FX103746915.aspx
And the type of license is based on the number of mailbox databases.
Standard: designed for the mailbox needs of small to midsize organizations. Also appropriate for non-mailbox roles in a larger Exchange deployment. This edition supports 1 to 5 mailbox databases.
Enterprise: designed for larger organizations that may require a greater number of mailbox databases. This edition supports 1 to 100 mailbox databases.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange Server 2013 Database not showing in ECP after removal of Exchange Server 2010

I recently complete the migration of my Exchange 2010 server to Exchange 2013. I then proceeded to uninstall the 2010 server using setup.com /m:uninstall. At the end of the process I received an error that it did not complete the uninstall.
I checked the server and Exchanged 2010 was removed. When I checked ECP on 2013 it still showed the old 2010 server listed. I used ADSI edit and manually removed the old sever.
Now when I log into 2013 ECP I only see the one serve but when I go into databases, none are listed. I check under the server itself and it shows the database that it is using but it is not listed under the database tab.
If I do a search under the database tab I can find it and adds it to the list. I can then open and view details.
My issue is, after I log out and then back in, I have to run the search to find the database again. In ideas on how to have it show up in the list like it did before I removed the 2010 Exchange server?
Thank you,

Hi,
From your description, I recommend you verify the following things for troubleshooting:
1. Please make sure that AD replication is completely by checking the user object's homeMDB attribute. This value should contain the DN value of the Exchange Server 2013 mailbox database.
2. Wait 30 minutes for the cache on the Exchange Server 2013 Client Access Server to clear or restart the MSExchangeOWAAppPool on the Exchange Server 2013 Client Access Server.
For more information, here is a kb for your reference.
Exchange 2013 Redirects to Exchange 2010 for OWA and ECP
http://support.microsoft.com/kb/2931385
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Exchange Server 2013 failover design

Hello:
I'm designing a failover Exchange Server 2013 solution. I only need mail and calendar services.
I'm planning to put two physical servers with Windows Server 2012 R2 with (or without) Hyper-V to run one virtual machine in
each physical server.
I don’t have external storage device, I like to use database replication
Also, I have a physical third party anti-spam firewall
The questions:
I need one VM for Mailboxes and a separate one for CAS (4 VMs in total) or I can install 2 VMs with MBX+CAS in each VM server?
I need a third server to avoid brain duplication, or isn’t needed?
Exchange Server 2013 supports POP3 connections?
Thanks for your time, and sorry for my bad English!
Un saludo! Juan Segura

The questions:
I need one VM for Mailboxes and a separate one for CAS (4 VMs in total) or I can install 2 VMs with MBX+CAS in each VM server? - Definitely you can go for multi-role servers
to combine MBX+CAS and in fact that's
recommended except couple scenarios.
I need a third server to avoid brain duplication, or isn’t needed? You need a witness server but that can be non-Exchange server too. You need to add Exchange trusted subsystem
in Local Admin group of that server
Exchange Server 2013 supports POP3 connections? - Yes, you can have POP3 connections
Blog |
Get Your Exchange Powershell Tip of the Day from here

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

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

Exchange Server 2013 non-unicode

Similar Messages

Maybe you are looking for