Hi there.  I know this is an old topic, but I would greatly appreciated if anyone can give me some inputs on this. This is what I need to achieve:

1. Currently having 1 AD Domain (Windows 2008 R2) - Need to setup a new Domain (Windows 2012 R2) in a new forest and migrate all the AD users to the new AD environment

2. Currently having Exchange 2013 in old forest - Need to setup Exchange 2013 in new forest and migrate all the mailbox(s) to the new Exchange 2013 forest.  The new Exchange 2013 forest would need to use (share) the same SMTP Name Space as the current (old) Exchange 2013.  Co-existence is required while the migration work is in progress.  Once all data from old AD and Exchange migrated to the new AD and Exchange forest, we will decommission the old AD and Exchange servers. 

From this URL below, this is the similar steps I assume would meet my goal. 

https://social.technet.microsoft.com/Forums/office/en-US/6159a52c-d154-461c-b7ab-c84592e60f32/exchange-and-ad-migration-to-new-forest?forum=exchangesvrdeploy

1. Install Exchange 2013 in the target forest
2. Configure DNS for a forest trust
3. Set up a forest trust
4. Set up GAL sync which you will need to use to sync the GALs between the forests: https://technet.microsoft.com/en-us/library/bb124734(v=exchg.150).aspx
   
5. Configure cross site availability service for free/busy information transfer between forests: https://technet.microsoft.com/en-us/library/bb125182(v=exchg.150).aspx
6. Configure cross forest mail flow using internal relay accepted domains for the source forest domains on the target forest: http://markgossa.blogspot.co.uk/2015/09/exchange-2013-cross-forest-mail-flow.html
7. Migrate AD groups using ADMT
8. Stage AD users using ADMT
9. Migrate AD users using ADMT, prepare for a cross forest move request (Prepare-MoveRequest.ps1) and move the mailboxes: https://technet.microsoft.com/en-us/library/ee633491(v=exchg.150).aspx, http://blogs.technet.com/b/meamcs/archive/2011/10/25/exchange-2010-cross-forest-migration-step-by-step-guide-part-i.aspx
10. Prepare for decommissioning the servers in the source forest
11. Decommission servers in the source forest

This looks pretty straight forward.  My question were as the following: 

a) How should I configure Autodiscover for external clients?  My understanding is Autodiscover only works on 1 forest, which means on the new AD forest, there would be no Autodiscover service for external clients. 

b) To share Free / Busy info between the two Exchange forest, I can utilize the "Add-AvailabilityAddressSpace" Exchange Powershell command?

c) To share Global Address List (GALSync) between the two Exchange 2013 forest, do I must use either FIM or ILM?  Is there are any built-in tools that can achieve the same result? 

d) How do I migrate Exchange resource mailbox (eg: room) to the new Exchange forest?  Is that the same process as the user mailbox migration? 

Thank you.

Hi All,

 Microsoft Recommendation for Public DNS records are: 

      

but my client setup for public dns are:

     contoso.com  -  MX  - owa.contoso.com
     owa.contoso.com -  A  - 1.1.1.1                                                                  
     autodiscover.contoso.com -  A  - 1.1.1.1

is it ok to have this kind of configuration on publick dns? because all external users that was set for virtual directories in exchange 2013 are using "owa.contoso.com". That's what they dont configure CNAME Record in Public DNS. and now they are having an issue on configuring exchange in phone using autodiscover activesync.

Thanks in advance

Hi i have created new user in AD and tried to open exchange 2013 OWA. i am getting below error. can anyone help to find the issue.

X-OWA-Error: Microsoft.Exchange.Data.Storage.ObjectNotFoundException
X-OWA-Version: 15.0.995.28
X-FEServer: ABGSR
X-BEServer: ABGSR
Date: 4/25/2016 11:43:02 AM

Hi,

I'm setting up exchange 2013 within a exchange 2010 environment, its all going ok but Ive hit a bit of a problem. The only way I can get the outlook 2010 clients to connect is to manually configure them using outlook anywhere and manually adding the server settings - this is with a migrated account. Ive checked the auto discovery which appears to be working I setup the external connection name to mirror that of the exchange 2010 box and also the internal (which didn't effect anything) so I'm at a bit of a lose end - could anyone suggest anything please?

Thanks 

Hi,

We are in progress of Migrating of our existing Exchange server from 2007 to 2013. Right now first part of migration is completed. we are migrating the mailboxes from 2007 to 2013 server, hence we do have both server on production(exchange 2007 & exchange 2013). The user mailboxes which is on exchange 2013 server, On outlook client, users has a App tab on each emails like "Action Items, Bing Maps, Suggested Meetings and Everyone".

I can able to disable the App from the outlook client manually from Manage Addin option under file tab, where as when i trying to turn Off Globally for all user account from the Exchange Admin Console(EAC). I don't see anything by default setting like "Action Items, Bing Maps, Suggested Meetings and Everyone" App Which comes under organization under Apps tab in EAC(it shows as blank under App tab). When i press the refresh button on EAC, i used to get attached error message.

It will be helpful if i get answers for the following :

* I would like to remove or disable or hide the App tab on all user account mailboxes mails globally.

* I am not sure about error message which i am receiving whenI Click on App Tab, would need to be fix this issue in order to get the default settings under App tab.

error

Cannot open mailbox /o=XXXXXXXXXXXXX/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EX2013MBX/cn=Microsoft System Attendant.

Please let know the best to fix the issue and block the app tab in emails.

Thanks

Hello Exchangers,

Would you please confirm if I can upgrade our Exchange 2013 from CU1 to CU12 directly?

As far as I red all CU is a new version of Exchange and include all the security updates and fixes.

The only thing I have to do is prepare the AD?

Thanks in advance!

Albey

Got a few users who just won;t migrate.

Create migration batch, it runs for a while and then says 0 mailboxes. It seems there must be some sort of flag on the mailbox.

There are no outstanding move requests - cleared all of these.

I guess there is something in a log file somwehere that can help with this?

Hi,

I'm having problems sending mail internally from my ex2013 account to an ex2010 account. The setup on the 2010 exchange server is:

ex2010 client receive connector -
x Transport Layer Security (TLS)

Enable domain security (mutual Auth TLS)
x Basic authentication
  x Offer basic authentication only after starting TLS
x Integrated Windows authentication
Exchange Server authentication
Externally secured (for example, with IPsec)

Permission groups:
Specify who is allowed to connect to this receive connector.

Exchange servers

Legacy Exchange servers

Partners

x Exchange users
Anonymous Users

ex2010 default receive connector -
x Transport Layer Security (TLS)

Enable domain security (mutual Auth TLS)
x Basic authentication
  x Offer basic authentication only after starting TLS
x Integrated Windows authentication
x Exchange Server authentication
Externally secured (for example, with IPsec)

Permission groups:
Specify who is allowed to connect to this receive connector.

x Exchange servers
x Legacy Exchange servers
Partners
x Exchange users
Anonymous Users

Custom Created Receive Connector -
x Transport Layer Security (TLS)

Enable domain security (mutual Auth TLS)
Basic authentication
Offer basic authentication only after starting TLS
Integrated Windows authentication
Exchange Server authentication
Externally secured (for example, with IPsec)

Permission groups:
Specify who is allowed to connect to this receive connector.

Exchange servers

Legacy Exchange servers
Partners
Exchange users
x Anonymous Users

The 2 default receive connectors have the standard network adapter bindings where as the custom additional third has some ips in it including the ex2010 server. This was an inherited server which I'm sure doesn't require the 3rd connector and just requires anonymous adding to the Default connector. Any thoughts? Thanks

Hello,

I would like to clarify the guidance detailed in the Exchange Server Deployment assistant.  If selecting the scenario "I currently have an Exchange 2010 deployment but would like to implement Exchange 2013 Hybrid" the resulting configuration details namespaces to apply to the Exchange 2013 servers.  The example namespace is hybrid.contoso.com.

I have customers referring to this documentation and believe that there is a requirement for a "hybrid namespace".  My understanding is that while you could deploy with a hybrid namespace this is not best practice and should not be implemented. 

Is anyone aware of documentation which states that you should implement Exchange 2013 and move your Exchange 2010 internet facing namespace to the 2013 servers, and not create an additional namespace for hybrid purposes?

This is an extract from the deployment assistant, it mentions hybrid.contoso.com.  Surely this should be mail.contoso.com? or the internet facing namespace of the 2010 servers?

(On the Configure external access domain page, enter the externally accessible FQDN of your Exchange 2013 Client Access servers in theEnter the domain name you will use with your external Client Access servers text box. For example, hybrid.contoso.com.)

In the prepare for deployment section of the deployment assistant the following namespaces are displayed:

Can anyone explain why the deployment assistant is advising these namespaces should be implemented.  All of the technet documentation states autodiscover, EWS, OWA etc should be pointing at the most recent version, which in this scenario is 2013.

Many Thanks

J

When creating a new public folder mailbox and public folder it seems to accept the parameter "DomainController". However if I script this and create a public folder mailbox and new public folder in that PF mailbox it generates an error saying the mailbox doesn't exist.

I've narrowed this down to a sync delay if you have multiple domain controllers since i'm executing the powershell commands back to back.... but since i'm providing the -DomainController option it shouldn't make a difference!

What is the recommend way to complete this task with powershell? Why doesn't the -DomainController option work for this?

While I make migration Exchange Server 2010 to Exchange Server 2013 Exchange installation has been stop and I see error message how can I solve this problem ?

     A Setup failure previously occurred while installing the Mailbox role. Either run Setup again for just this role, o
r remove the role using Control Panel.

Hi,

I'm currently running Exchange 2007 SP3 on Windows 2003 so I'm starting the process of migrating to Exchange 2013. Our current Exchange 2007 configuration is very small with 31 users and an Exchange mailbox size of around 100 GB right now.  Our current Exchange 2007 box has a Xeon CPU with hyper-threading so I've got two CPUs and it has 6 GB of memory. I've got two Raided drives for the C and D with the Exchange 2007 software and mailbox on the D drive. The performance of this server is adequate though it's beginning to get a little slow.  We also have an SCR replica server that is virtualized.

So I'm trying to figure out what would be an appropriate new server size should be and I've looked at all the server sizing information and looked at the Microsoft provided sizing calculator workbook but even the smallest example is for a server with 1000 users which is clearly way more than what I have.

Given what I've read, I was going to go with the following hardware:

- New very fast Xeon CPU with at least 8 cores

- 16 GB of memory, possibly 24 GB

- Raided drives for the C, and D, and possibly an E drive to separate the database and log files. Probably 250 GB for the OS and 1 TB each for the data drives.

Any thoughts on this?  Also if anyone has any links for sizing that are a little more specific to smaller deployments that would be very helpful.

Thanks

Nick

We have an Exchange 2013 Environment running on Server 2012 R1.

We currently have two MBX Servers in a DAG, and only one CAS.

I want to add a second CAS for redundancy.  The current CAS is on Cumulative Update 5.

Questions:

1.  Can I install CAS2 with CU7 and add to Exchange, or do I need to update CAS1 to CU7 first?

2.  When I upgrade CAS1 to CU7 - how much downtime will there be?

Hi,

We've got a piece of in-house software that we use to mail out notifications to users which is sitting on a SQL server being 192.168.0.4, the old 2010 exchange server is 192.168.0.3 and the new 2013 exchange server is on 192.168.0.7.

After the migration, if I turn off the old exchange 2010 server and setup an additional IP on the new server as 192.168.0.3, I then use in-house software to send a mail out notification, it comes up with error 5.7.1 Client was not authenticated. I've had a look at a few threads and made sure that the Default Frontend receive connector is set to anonymous which it is but it still doesn't work. I've also thought of the possibility that the message might be coming from the users pc rather than the server but it shouldn't matter because all IPv4 and IPv6 ip addresses are accepted in the Default Frontend receive connector. Right now, its working because its still routing mail through the old server which was turned back on and not fully decommissioned.

The in-house software points to the IP address and not a DNS record. If I remove the IP address 192.168.0.3 from the new server and leave 192.168.0.7, the in-house software reports back and says it cannot contact the server so I know its hitting the right server. The software is also using a username and password to authenticate which is correct and I can use it to log into its own OWA.

Suggestions anyone?

Name             : Default Frontend XXXEXH01
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : AnonymousUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 36 MB (37,748,736 bytes)

Hi,

I have coexistence of Exchange 2013 & 2010, I am testing 2013 mailbox (with host file entries pointed to Exchange 2013 ). Everything is working fine except when i see in Room Finder , I can see meeting rooms but it show as "5 Unknown, No Room available".

http://prntscr.com/azbqt6

If i configure a mailbox which exist on 2010 but host entries on client machine pointed to Ex2010 CAS , it configured properly but in room finder it shows , "Free/busy Data could not be retrieved"

It seems proxy for meeting rooms from exchange 2013 to 2010 is not working properly. any help

Regards
Usman Ghani

Usman Ghani - MCITP Exchange 2010

The problem I am having is I cannot get my Public Folders to accept mail as well as I cannot manage them in the EMC either. 

I will start by saying this problem started when I was migrating from 2003 to 2010 and attempted to remove the last 2003 server and was unable to get it to uninstall. Prior to using ADSIedit to remove the "First Storage Group" where my 2003 server existed I moved all replcas and followed the documentation exactly on removing the last server the only thing that didn't go as planned was the uninstalling of Exchange off the last server so I had to manually remove it. I had taken my 2003 Exchange offline for over 4 weeks prior to taking this step and had no issues up until then. 

Current status is -

I can see the public folders from Outlook and I believe I can even modify the calendars but any mail enabled public folders can see old mail but do not get any new messages since I deleted the "First Storage Group" from AD. Inside of EMC I originally had a DB called "Public Folder Database" which was mounted and seemed to be working until I deleted that entry then it disappeared after closing and reopening EMC. Since then I made a backup of that DB (edb file) and attempted to create a new Public Folders Database. When I try create a new one using the same name it tells that the name has to be unique yet it is not in my list of DB in EMC. So I went ahead and created a new one, unmounted it, renamed the DB, and copied old one in it's place. Of coarse it wouldn't mount so I ran a repair on it and it said it fixed the corruption. I was able to mount it and tried changing the client settings of the mail stores to use this newly named Public Folder DB in hopes it would fix my issue. Still the same thing unable to send to mail-enabled PF. When I try to create a public folder using the shell it tells that the server does not have a  PF DB which it clearly does. So I also used the shell and browsed into the original DB location and tried to repair it but get this error

Error: Access to source database '.\Public Folder Database 0576360222.edb' failed with Jet error -1032.

Operation terminated with error -1032 (JET_errFileAccessDenied, Cannot access file, the file is locked or in use) after 20.31 seconds.

When I run this get-publicfolder -identity "\"

All I get is this

Name                                                                               Parent Path
----                                                                               -----------
IPM_SUBTREE

When I run this get-publicfolder -getchildren -identity "\NON_IPM_SUBTREE"

I get this

Name                                                                               Parent Path
----                                                                               -----------
EFORMS REGISTRY                                                                     \NON_IPM_SUBTREE
The database 'Public Folders Database' to be accessed on server 'a001exchng5.mylocal.domain.com' is not mounted or is not available.
    + CategoryInfo          : NotSpecified: (0:Int32) [Get-PublicFolder], DatabaseUnavailableException
    + FullyQualifiedErrorId : 8846CE95,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder



[PS] X:\Microsoft\Exchange Server\V14\Mailbox\Public Folder Database 0576360222>mount-database '.\Public Folder Database 0576360222.edb'
Cannot process argument transformation on parameter 'Identity'. Cannot convert value ".\Public Folder Database 0576360222.edb" to type "Microsoft.Exchange.Configurat
n.Tasks.DatabaseIdParameter". Error: "'.\Public Folder Database 0576360222.edb' is not a valid value for the identity.
Parameter name: Identity"
    + CategoryInfo          : InvalidData: (:) [Mount-Database], ParameterBindin...mationException
    + FullyQualifiedErrorId : ParameterArgumentTransformationError,Mount-Database

I am at a loss here and been all over google researching this which seemed like a common problem after migrating but unfortunately my issues seems a little different than most I have ran across. Any help or guidance would be appreciated.

Thanks

Jeremy

Jeremy Clark

Currently running Exchange 2010 on premise in a hybrid mode.  We have have Azure AD Sync running as well.  Almost all mailboxes have been migrated to the cloud, but we needed to keep a server on premise for management and internal relay.  Recently an admin uninstalled the on premise Exchange server "accidentally" and is now having a difficult time installing it back into our environment.  We are unable to manage DLs and mailboxes without this on-premise server.  

Would it be possible to remove all links to the on-premise server and O365 and then try to install a new Exchange 2013 server, then re-establish the hybrid mode?

Any suggestions on how to get it installed back into our environment?

Hello,

My exchange server has 2 IPs.

One as the primary IP4 address and the second IP attached to Relay connection in the Receive Connectors in Hub Transport. The issue is that the relay IP creates an record in the DNS. Occasionaly, client workstations will try to use the relay IP to connect to Exchange and it causes all sorts of issues.

My question is: how do i not allow the clients to connect to exchange's relay IP? I have two IPs connected to one NIC