Exchange 2010 SP1 prepareAD Failed
Hello, We have Active Directory on Windows Server 2003 and when we are going to install Exchange Server 2010 SP1 for it give me error:(Exchange server is never installed before in the network) setup.com /prepareschema successful setup.com /prepareAD Failed asking for organization name
January 13th, 2011 4:59pm

So if this is the first time you have ever installed Exchange in your AD, then you will have to run the /prepareAD switch with the /organizationname:NAME switch. Like: setup.com /prepareAD /OrganizationName:NAME This article will explain the whole process: http://technet.microsoft.com/en-us/library/bb125224.aspxTim Harrington | MVP: Exchange | MCITP: EMA 2007/2010, MCITP: Server 2008, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington
Free Windows Admin Tool Kit Click here and download it now
January 13th, 2011 6:11pm

Agree with Tim. As its a first time you are installing exchange hence you will have to specify ORG name (Not like in exchange 2003 it use to ask for ExchangeORG name in GUI) Follow the Tim's instructions and you will be able to install the server successfully. Cheers,Gulab | Skype: gulab.mallah
January 14th, 2011 12:00pm

Else, Just start setup.com and let exchange setup to complete /PrepareAD swicth itself, It will ask for ORG name there. Above are good link to proceed.Anil
Free Windows Admin Tool Kit Click here and download it now
January 14th, 2011 12:20pm

Hi, What name is expected? For example, my domain is called mydomain.com, should I use the same string "mydomain.com" as organization name?
October 28th, 2011 1:50pm

No, it should be anything ABC, XYZ... it shouldn't be domain.com. Its just example.Gulab | MCITP: Exchange 2010-2007 | Lync Server 2010 | Windows Server 2008 | Skype: Exchange.Ranger | Blog: www.ExchangeRanger.Blogspot.com
Free Windows Admin Tool Kit Click here and download it now
October 28th, 2011 1:53pm

It shouldn't be (my)domain.com? Oh! In other words, it doesn't matter and could be "mydomain" or even "whatever", right? PS: Then why the setup can't automatically (and smartly) create some string like domain's NetBIOS name? Strange!
October 28th, 2011 2:01pm

Yeah it could be anything, normally people keep it as per there company.Gulab | MCITP: Exchange 2010-2007 | Lync Server 2010 | Windows Server 2008 | Skype: Exchange.Ranger | Blog: www.ExchangeRanger.Blogspot.com
Free Windows Admin Tool Kit Click here and download it now
October 28th, 2011 2:10pm

Example: setup.com /prepareAD /OrganizationName:DEMO123 dont use .com etc. just plane alpha numeric name. and then in setup also choose same name, i.e DEMO123 as organization name. its better to use first part of the domain such as for UmbrellaCorporation.com use setup.com /prepareAD /OrganizationName:UmbrellaCorporation Thank you
February 26th, 2012 1:47am

I would suggest something even shorter and simpler: EX! As I understood it, it's just a name to make up an LDAP distinguished name, so why bother?
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2012 6:05am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics