?
Solved

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

Posted on 2014-03-12
4
Medium Priority
?
3,950 Views
Last Modified: 2014-03-17
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
0
Comment
Question by:realtimer
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 
LVL 3

Expert Comment

by:Mutogi
ID: 39925214
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
 
LVL 14

Expert Comment

by:Justin Yeung
ID: 39925356
it is setup.com
0
 
LVL 17

Expert Comment

by:Brad Bouchard
ID: 39927423
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
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 2000 total points
ID: 39927720
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

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

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

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Suggested Courses

762 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