?
Solved

Need help with installing ms exchange 2013 on windows server 2012

Posted on 2014-12-26
12
Medium Priority
?
198 Views
Last Modified: 2015-01-12
Need help, when installing ms exchange 2013 on windows server 2012, Exchange cant find the federated mailbox  (xxxxxxxxxxxxxxxxxxxxxxx), and I have to recreate it from exchange management console but the command cant run because the exchange install is not complete.

Need help with resolving this....
0
Comment
Question by:Kasonde Neddy
  • 5
  • 3
  • 2
  • +2
12 Comments
 
LVL 19

Expert Comment

by:R--R
ID: 40518398
Is this your first exchange server in org?
0
 

Author Comment

by:Kasonde Neddy
ID: 40518459
Attached the error message....
IMG-20141226-WA0000.jpg
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
LVL 36

Expert Comment

by:Seth Simmons
ID: 40518547
try this on your 2010 server:

New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@default_accepted_domain

replace default_accepted_domain at the end with your domain
0
 

Author Comment

by:Kasonde Neddy
ID: 40518566
R--R yes it is the first....trying out solutions, thanks for responses, will be in touch shortly...
0
 

Author Comment

by:Kasonde Neddy
ID: 40518582
Seth Simmons..the command is bringing up a syntax error...
0
 
LVL 36

Expert Comment

by:Seth Simmons
ID: 40518622
this is your first exchange server?
there was no 2010 existing before?
everything i have seen thus far points to an issue related to a 2010 install
0
 

Author Comment

by:Kasonde Neddy
ID: 40518670
no its not the first... 2010 was existing before... i think it oculd be related to previous install..any advice on what to do to resolve?
0
 
LVL 36

Expert Comment

by:Seth Simmons
ID: 40518681
ok...going back to R-R second link (kickthatcomputer) did you try the suggestions there?
0
 
LVL 19

Assisted Solution

by:Adam Farage
Adam Farage earned 1000 total points
ID: 40519313
Is Exchange 2010 gone, or does it still exist? If its still there what service pack and update rollup is it at? What version of Exchange 2013 are you attempting to install?

What is the full error message you are getting during installation?

I would look at this article here but mainly at these steps *only if* Exchange 2010 is still installed...

First...

Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEDIT tool. To do this, follow these steps:

    Click Start, click Run, type adsiedit.msc, and then click OK.
    Locate the Default Naming Context node, and then locate to the CN=Users container.
    Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click Delete.

Then...

New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>

Mainly fill in the "default accepted domain" with what yours is, and make sure that you run this in the Exchange Management Shell for Exchange 2010.

If you get a Syntax error then please post it here. I am also curious if this is a single domain design or do you have multiple domains under a single forest? Mainly because when you run schema and ad prep you should have the schema master local to the domain you are preparing or I have seen similar results..
0
 
LVL 5

Accepted Solution

by:
Hello World earned 1000 total points
ID: 40521437
0
 

Author Closing Comment

by:Kasonde Neddy
ID: 40544161
Thanks guys!
0

Featured Post

[Webinar] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Among the most obnoxious of Exchange errors is error 1216 – Attached Database Mismatch error of the Jet Database Engine. When faced with this error, users may have to suffer from mailbox inaccessibility and in worst situations, permanent data loss.
Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses

621 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question