Exchange 2010 why?

[MasterPlan1]

Exchange 2010 is great, powershell is great. If you're moaning about having to know a few powershell commands to look up a few random bits and bobs in Ex2010, you might as well go look for another job now, as powershell is how WS2012+ is going to be moving.

It's also all pretty logical stuff, especially for Get-ing stuff, tab your way to finding what you want, a few selects, sorts, job done. It took me about 2 weeks of dropping from using EMC to EMS to know enough of Ex2010's powershell commands to get by and do everything I needed via EMS.

 

[Django x2]

For a simple function like how to see the size of mailboxes you have to use a command like this

Or, click on the mailbox in the GUI and look at the size of the mailbox in there.....

Seriously. Man up. Further more, you will not be able to show a clear justification for not moving to the cloud that a large cloud provider, like MS, cannot validate with supporting evidence. Some of the largest government agencies are moving to O365 (albeit some in private cloud) and that's taking EU Safe Harbor, EU Model Clauses and the Patriot Act into account. None of which would even appear on the radar of legal firms.

If Exchange goes back to Shell only, it will be a good thing, as it will lower the footprint and allow the server to do what it's meant to do. As it is, it's moved to a web gui which allows almost all of the administrative functions you would want without having to go to the shell.

It's clear in Exchange 2010 that Microsoft want people to use Power Shell more. I too get annoyed at such functions that should be in the GUI. Like exporting a mailbox to PST, why not right-click -> export?

This is a feature of the GUI in 2010, as with 2013, you have to ensure the correct permissions are enabled before the option becomes available.

 

[Yaayuh!]

This is a feature of the GUI in 2010, as with 2013, you have to ensure the correct permissions are enabled before the option becomes available.

Edit:
Nope, doesn't work. It's not available in GUI.

Thanks Microsoft.

 

[MasterPlan1]

It's not like it's a hard, long, complex command, New-M[tab]E[tab] -M[tab] 'Name' -F[tab] \\server\share$

Takes way less time than trawling through GUI.

 

[Django x2]

Edit:
Nope, doesn't work. It's not available in GUI.

Thanks Microsoft.

You assigned the recipient management role, then gave access to the user who needs to run the import / export then refreshed the MMC console?

Then you get this:

 

[Bry]

Edit:
Nope, doesn't work. It's not available in GUI.

Thanks Microsoft.

?
Does work fine and is detailed here
http://howexchangeworks.com/2009/06/export-import-in-exchange-2010.html.

You do need correct permissions. By default Exchange organization administrators do not have the permissions. You need to assign extra permissions for this

 

[NightShadow]

Have to say, I'm actually a big fan of 2010 and PowerShell, scripting and automating stuff that used to take ages really does make my life easier. 2013 is taking a bit of getting used to but I've only really used it a few times so sure it will become natural soon enough.

I think the key thing is the number of users you are supporting, any more than 25 or so and you will see the benefits of scripting and powershell rather than doing each mailbox manually or clicking through endless wizards in the GUI.

 

[Bry]

Have to say, I'm actually a big fan of 2010 and PowerShell, scripting and automating stuff that used to take ages really does make my life easier. 2013 is taking a bit of getting used to but I've only really used it a few times so sure it will become natural soon enough.

I think the key thing is the number of users you are supporting, any more than 25 or so and you will see the benefits of scripting and powershell rather than doing each mailbox manually or clicking through endless wizards in the GUI.

Couldn't agree more. I can do something in 1 minute in Exchange 2010 vs a couple of hours in 2003. It really is fantastic.

If you dont want to get into scripting then I have 3 tips:

1) When doing any action via the GUI you will see in the bottom elft hand corner a small icon (arrow iirc). Clicking this tells you the powershell command of the action your about to take. Its extremly useful for learning powershell. As everything done in the GUI is just a powershell command being run

2) For smaller things google is your friend. As shown in this thread there are lots of one line 'scripts' that will tell you a lot of things

3) Need something more? look at the exchange 2010 gallery of scripts
So many and so very useful!

 

[anything I don't mind]

Thanks for the tips Bry.

I agree and see the logic with the scalability argument. But doesn't help me with 100 user sites that much. But my boss is getting an exchange expert (from our company) to come in and check the DAG configuration and decommission the 2003 environment in a few weeks after moving mailboxes. So i can put off learning 2010 that bit longer

 

[Bry]

Thanks for the tips Bry.

I agree and see the logic with the scalability argument. But doesn't help me with 100 user sites that much. But my boss is getting an exchange expert (from our company) to come in and check the DAG configuration and decommission the 2003 environment in a few weeks after moving mailboxes. So i can put off learning 2010 that bit longer

Forgot to add, if your going to different sites and want a quick overview of the exchange environment and mailboxes then check out this
http://www.stevieg.org/2011/06/exchange-environment-report/

Its so useful we run it daily to keep track of mailbox usage.

I notice you said specifically about dag replication? Then this is your answer
http://gallery.technet.microsoft.com/office/Exchange-DAG-Replication-d8e99705

But generally when in the gui, organization management --> mailbox server. Will show you the status of the dag and your passive databases. As long as your copy queue length is 0 then your fine (note a copy queue length of greater than 0 is fine if your databases are set to be lagged for point in time backup)

 

[anything I don't mind]

Thanks bry, those scripts are very useful and will help to make it appear like i know what i am doing

Seriously though, very useful thanks, The dag report said its working but when i ran the other report its showing 0 mailboxes on the DR site. So definitely not working 100%.

 

[Yaayuh!]

?
Does work fine and is detailed here
http://howexchangeworks.com/2009/06/export-import-in-exchange-2010.html.

You do need correct permissions. By default Exchange organization administrators do not have the permissions. You need to assign extra permissions for this

It was there in Beta, it's not there i in the actual release.

I will check permissions, even though i'm doing this as domain and enterprise admin which should have all the roles to do such things. But i'm fairly sure it's not available in the release version because i did search for ages to find out how the first time round.

 

[Django x2]

Enterpise and domain don't have the required permissions in Exchange 2013 either, they have to be added

 

[Yaayuh!]

Enterpise and domain don't have the required permissions in Exchange 2013 either, they have to be added

My standard account has that role and i don't have access to exporting mailboxes via EMC.
Added the main admin account to that role it as well, to no avail. I get:

Enable Archive
Disable
Remove
Enable UM
Manger Mobile Phone

New Local Move Request
New Remote Move Request

Manage Send As
Manage Full Access

Send Mail

Properties

Help

As i've said, i've researched this a lot, everywhere i have looked it says the function (among a some others) have been removed from EMC to Shell only. There were a few that were in EMC in the BETA form of Exchange.