Installing Exchange server 2013

I have done some reading about the Install of Exchange 2013, most of articles they talk about preparing Active Directory using:
Setup.exe /PrepareSchema
Setup.exe /AD

etc...

Actually, I have installed Exchange 2013 on Windows 2012 server without going through any preparation of Active Directory, and I worked..

I wonder why going through all that extra work.
Any idea ?

Thanks
jskfanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AmitIT ArchitectCommented:
In case your ID doesn't have domain admin, schema and Enterprise admin rights and you have separate AD team, to manage the environment, In those cases, you might need to follow those steps. It seems the ID you used had all required rights, that's why it didn't asked you anything to do in advance.
0
NetoMeter ScreencastsCommented:
The Exchange 2013 Setup wizard performs automatically a series of prerequisite checks. One of these checks is the Active Directory schema version.

If Active Directory hasn't been prepared, as it is in your case, Exchange 2013 setup automatically connects and prepares AD. There is nothing wrong in what you've done - you were performing a greenfield install and the account that was used had the required privileges - schema and enterprise admin.

Normally, when you are installing Exchange 2013 in a production environment, you start with Active Directory health check (replication, DNS zones, old Exchange server not decommissioned properly etc). Preparing the Schema and AD in advance for Exchange 2013 provides an extra step for detecting early hidden problems instead having a failed Exchange setup due to some missed AD misconfiguration,replication issue etc.

In your case, everything was kosher and you should be able to proceed with the Exchange 2013 initial configuration.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jskfanAuthor Commented:
Thank you Guys!!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.