Exchange Server 2013 task that must be done through powershell ?


Since I'm familiar with Exchange Server 2007/2010 Management Console, I wonder what are the list of things that must be done through Powershell console only ?

From what I can see and read through there are some task that must/can only be done through Powershell instead of Exchange Admin Console in Exchange Server 2013 SP1 or Office 365 ?

LVL 11
Senior IT System EngineerSenior Systems EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Amit KumarCommented:
Exchange PowerShell is backbone of Exchange infrastructure from onwards Exchange 2007, every task you do in EMC in backend it performs powershell cmdlet.

So from user creation to add/modify/delete any configuration for Exchange can be done by EMS.



Creation of RDB and restoring mailbox data can only be don by EMS, Anti-Spam feature configuration can be done by EMS. There are lot of this you can do.

Message tracking in  E2k13 or Message Trace in Office 365 can be performed in Powershell. Office 365 has a remote powershell module which we can connect through internet.
Senior IT System EngineerSenior Systems EngineerAuthor Commented:
ok, what about something that is more specific like setting the Atachment limit size and Address book filtering ?

I need to classify and know which one needs Powershell and which one can be done using EAC.
Vasil Michev (MVP)Commented:
A full list will be hard to come by, especially in EO where things are changing frequently. Pretty much everything you can run from the EAC is a PowerShell cmdlet.

Examples I can think of:

- creating/editing RBAC scopes, creating new Roles, etc
- creating/editing Address Lists and Address Book Policies
- forcing the Managed Folder assistant to process a mailbox
- Configuring folder permissions
- Configuring Organizational relationships
- Configuring IRM
- Pretty much every setting configurable by Set-OrganizationConfig
- Some cmdlets that perform tests and/or allow you to obtain logs

Others can certainly add to the list.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Amit KumarCommented:
which attachment limit size you are talking about?

if mailbox then can be set by EAC and EMS both.

Address books can only configured in EMS

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
Hardik DesaiIT Architect and TrainerCommented:
Anything that can be changed/set in Exchange 2013 can be done via powershell. Not sure the significance of this question.
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Guess the question is: Which operations cannot be done in Exchange 2013 / O365 GUIs but in Exchange 2007 or 2010? And hence require to use PowerShell now?
Hardik DesaiIT Architect and TrainerCommented:
Ok, so the 1 line answer: any kind of script automation or bulk modification cannot be done via GUI and requires Powershell. This includes all the commands available in powershell.
Senior IT System EngineerSenior Systems EngineerAuthor Commented:
Yes QLemo is correct :-)

Is there any List or website which shows the Powershell command that otherwise EAC cannot perform ?
AmitIT ArchitectCommented:
Try this;

Also note, whatever you do it from GUI also, back-end PowerShell commands are used. Any advance level changes, you might need to use powershell, like making bulk changes on user mailbox. Testing server/services health, you can do it with PS much easier, compare to GUI.

Rest, it depend on your requirement. If you are good in using commands, then PS is the best way to manage exchange.  I suggest to start using it for basic task also, that will help you to learn and later you can use it for complex task.
Senior IT System EngineerSenior Systems EngineerAuthor Commented:
Thanks !
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

From novice to tech pro — start learning today.