Exchange 2007 Power Shell

Author
Discussion

BliarOut

Original Poster:

72,857 posts

240 months

Tuesday 3rd August 2010
quotequote all
Is ste...

That is all punch

If you're going to develop an operating system document the fker properly and don't release it till you've finished writing the GUI.

tts, I'm off to play with Vi.

:wq

buggalugs

9,243 posts

238 months

Tuesday 3rd August 2010
quotequote all
Yeah, all seems a bit arbitrary and un-intuitive. Feels like a list of random commands you have to copy & paste for various scenarios. Just put more buttons in the console FFS yes

Prak

722 posts

219 months

Wednesday 4th August 2010
quotequote all
powershell is incredibly, er, powerful. It comes into its own when you need to quickly script a load of changes to multiple objects, or pipe the results of one command into another

I have to manage a very large scale Exchange system and I doubt i could do it without powershell.

I agree there are places where the gui is somewhat lagging behind what you can do with the shell, but I think it's fundamentally the right way round to build a consistent command line interface first then gui tools on top of that rather than vice versa.

itsnotarace

4,685 posts

210 months

Wednesday 4th August 2010
quotequote all
I like it as well, for the same reasons Prak posted. Does take a bit of getting used to though.

What is it you're having problems with OP?

BliarOut

Original Poster:

72,857 posts

240 months

Wednesday 4th August 2010
quotequote all
Nothing in particular at the moment, I just hate poor software. If you *need* a shell to perform a command in 2010 is it really fully developed?

Take the vanilla product, you had to set the maximum message size from the command line. WTF???? And you had to do it differently for individual send and receive connectors... and then you have to pipe it to see what size is actually allowed punch

Still, MS tells us this is the future and it's much better than those crappy old windows... They're so last century, what you need is a poorly documented and inconsistent command line interface. I did Vi, it was st then and it still is. I could pipe, grep and cat till the cows come home but why should I? Still, let's look at the documentation...


Set SendConnector subcommand

And that's bloody it. No examples, no references to what the subcommand is and no links to it punch

Now I know there are a few (probably untanned wink) people out there who like it but if it is the future why did they vastly increase the GUI capabilities in SP1 & SP2.

I'll leave you with this, how do you set up a new user who has an e-mail address in Active Directory users and computers? I could achieve that task back in 2003..... wink

sjg

7,454 posts

266 months

Wednesday 4th August 2010
quotequote all
BliarOut said:
Still, let's look at the documentation...


Set SendConnector subcommand

And that's bloody it. No examples, no references to what the subcommand is and no links to it punch
You mean this documentation for 2010?

http://technet.microsoft.com/en-us/library/aa99829...

Or this documentation for 2007?

http://technet.microsoft.com/en-us/library/aa99829...

Or are you just going to sit and cry because your 2003 skills are obsolete now?

BliarOut

Original Poster:

72,857 posts

240 months

Wednesday 4th August 2010
quotequote all
sjg said:
BliarOut said:
Still, let's look at the documentation...


Set SendConnector subcommand

And that's bloody it. No examples, no references to what the subcommand is and no links to it punch
You mean this documentation for 2010?

http://technet.microsoft.com/en-us/library/aa99829...

Or this documentation for 2007?

http://technet.microsoft.com/en-us/library/aa99829...

Or are you just going to sit and cry because your 2003 skills are obsolete now?
Yes that 'documentation' rofl

My example was typed from memory, but there are swathes of it that are incomplete.

So, how do you add a user with a mailbox in Active Directory?

sjg

7,454 posts

266 months

Wednesday 4th August 2010
quotequote all
EMC if you want to point and click. "New Mailbox.." will give the option to mail-enable an existing AD account or create a new one.

Else the New-Mailbox cmdlet: http://technet.microsoft.com/en-us/library/aa99766...

BliarOut

Original Poster:

72,857 posts

240 months

Wednesday 4th August 2010
quotequote all
sjg said:
EMC if you want to point and click. "New Mailbox.." will give the option to mail-enable an existing AD account or create a new one.

Else the New-Mailbox cmdlet: http://technet.microsoft.com/en-us/library/aa99766...
So you can't? wink Blimey, that's progress....

So what's the business benefit of investing in training for this new command line language? What's the actual training cost and how long will this language be in mainstream use?

If it's so great why have MS added to the GUI at each successive SP release?

Sure, expose the command line if you can't be bothered to write a responsive and informative GUI but don't release a product before it's ready for market.

itsnotarace

4,685 posts

210 months

Wednesday 4th August 2010
quotequote all
BliarOut said:
So, how do you add a user with a mailbox in Active Directory?
I don't follow. That is not consistent with what you wrote above. Does the user have an existing mailbox or just an email address already set in AD?

If just an email address you can add a new mailbox as per normal using the EMC GUI, you can also add it from the shell - whichever takes your fancy. You don't need any extra service packs installed to do that.




itsnotarace

4,685 posts

210 months

Wednesday 4th August 2010
quotequote all
Ahh I just re-read twice. You want to be able to create a mailbox directly when creating a new user in AD. Well no, you can't.

You use Exchange to create a new user now and create a mailbox at the same time. Things have moved on, it's just a different way of doing things so get used to it!


BliarOut

Original Poster:

72,857 posts

240 months

Wednesday 4th August 2010
quotequote all
itsnotarace said:
BliarOut said:
So, how do you add a user with a mailbox in Active Directory?
I don't follow. That is not consistent with what you wrote above. Does the user have an existing mailbox or just an email address already set in AD?

If just an email address you can add a new mailbox as per normal using the EMC GUI, you can also add it from the shell - whichever takes your fancy. You don't need any extra service packs installed to do that.
Sorry, typing in a rush. How do you add a user with a mailbox in ADUC? If 2K7 is progress the task will be quicker, surely?

itsnotarace

4,685 posts

210 months

BliarOut

Original Poster:

72,857 posts

240 months

Wednesday 4th August 2010
quotequote all
itsnotarace said:
So you can't... Which we both bloody well knew anyway wink

Sure, I like progress when it's actual progress but when a task takes longer to achieve the word you should be using is 'retrograde'.

sjg

7,454 posts

266 months

Wednesday 4th August 2010
quotequote all
Er, you fire up a piece of software and do account creation including mailbox in one hit.

On Ex2003, that's ADUC.

On Ex2007/2010, that's EMC. (and you have the option of a very flexible, easily automated command line method too).

How is one GUI method "quicker" than the other? Things move on. You can't use User Manager for Domains to create users any more either.

BliarOut

Original Poster:

72,857 posts

240 months

Wednesday 4th August 2010
quotequote all
sjg said:
Er, you fire up a piece of software and do account creation including mailbox in one hit.

On Ex2003, that's ADUC.

On Ex2007/2010, that's EMC. (and you have the option of a very flexible, easily automated command line method too).

How is one GUI method "quicker" than the other? Things move on. You can't use User Manager for Domains to create users any more either.
I want to set a couple of additional AD properties when I create the user. Is that task quicker or slower with 2007?

It's not that I can't accomplish the tasks, but the documentation varies between poor and non-existent.

I haven't received an answer to the business benefits questions yet ears

BliarOut

Original Poster:

72,857 posts

240 months

Wednesday 4th August 2010
quotequote all
Add-AdPermission -Identity "Default Receive Connector" -User "NT AUTHORITY\Authenticated Users" -ExtendedRights ms-Exch-SMTP-Accept-Any-Sender


Lovely, look how intuitive that is, my morning is complete...

sjg

7,454 posts

266 months

Wednesday 4th August 2010
quotequote all
Business benefits? Any sysadmin worth their salt can easily automate all the tedious day-to-day stuff without writing long and complex vbscripts. Need a list of the top 50 mailboxes by size, emailed to someone weekly? Straightforward to do. Need to mailbox-enable every plain AD user in an OU? Very easy. Need to mount an Exchange DB in your test environment and want to create an AD user for each mailbox in the DB? Easy.

Less time clicking, more time for doing other things.

The powershell model (GUI management driving powershell cmdlets) is becoming the default for Microsoft's server platforms. Windows Server, Hyper-V, IIS, SQL 2008 all do the same. Get used to it, it's not going anywhere.

Not sure how you're having a problem with docs. I fire up EMS on my test Exchange 2007 box, and there in yellow text it reminds you that "help <cmdlet>" or "<cmdlet> -?" will show help. If what's there isn't enough, it tells you how to get the detailed/full versions at the end (which are very, very extensive). And it's all online at technet anyway.

BliarOut

Original Poster:

72,857 posts

240 months

Wednesday 4th August 2010
quotequote all
If we're going cmdlet, let's look at the business benefits of going *nix then.

And you used to just right click the mailbox store to find your top fifty users wink