The term 'setup' is not recognized as the name of a cmdlet...

Hello,

I am performing the pre-steps prior to installing Exchange 2013 on Windows 2012.  I am using the following document: http://exchangeserverpro.com/install-exchange-2013-pre-requisites-windows-server-2012/

In attempting to prep AD, I'm running the following command in PowerShell as Administrator.
setup /PrepareAD /OrganizationName: "MyOrganizationName" /IAcceptExchangeServerLicenseTerms

setup : The term 'setup' 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
+ setup /PrepareAD /OrganizationName:CalVivahealth
+~~~~
+ CategoryInfo  : Object NotFound: (setup:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Any input would be greatly appreciated.

Regards,
RealTimer
realtimerAsked:
Who is Participating?
 
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
Unless you are in a domain where you have the schema master in a separate site, or have multiple domains in the forest, you don't have to run prep manually. You can just run setup.exe and it will get on with it, including preparing the domain.

On Exchange 2013 there is only setup.exe and you need to be in an elevated command prompt which is in the directory where you extracted the setup files for Exchange 2013 SP1 to. If you haven't extracted them, or you aren't using SP1 media, go and download it.

Simon.
0
 
MutogiIT ManagerCommented:
after typing 'setup' hit the "TAB" key to see if the command is complete, it will change to caps if the command can run.

If not try i believe 'run'

sorry im not much help.
1
 
Justin YeungSenior Systems EngineerCommented:
it is setup.com
0
 
Brad BouchardInformation Systems Security OfficerCommented:
it is setup.com

It might be this...

or you may need to be in a certain directory to run the setup command... make sure you don't need to be in C:\Windows\WHATEVER (whatever referring to the specific directory) for this command to work.
0
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.

All Courses

From novice to tech pro — start learning today.