I keep hearing these complaints about things being cut from the GUI, and left 
in the command line only, but as someone who administrates many Exchange 2007 
servers, a lot of what I have to do day to day is done from the GUI, although I 
tend to use the command line because it is quicker. I suspect a lot of it comes 
from people who have simply evaluated Exchange 2007, as the command line is 
used a lot in the setup and configuration, but in the day to day operation, the 
GUI should fulfil most tasks.

However there are at least three active Exchange MVPs on this list, who can 
provide feedback to Microsoft. Therefore lets throw it open…

What do you think is missing from the GUI? You need to be very specific. That 
applies to both Exchange 2007 and 2010 for those who have already looked at it.
Its obviously too late to do anything about the released product, but Microsoft 
do listen – the change in policy over Windows 2008 R2 an Exchange 2007 is a 
clear example, but without being told, how do they know?

Over to you people now.

Simon.



--
Simon Butler
MVP: Exchange, MCSE
Sembee Ltd.

e: si...@sembee.co.uk
w: http://www.sembee.co.uk/
w: http://www.amset.info/
w: http://blog.sembee.co.uk/

Need cheap certificates for Exchange, compatible with Windows Mobile 5.0?
http://CertificatesForExchange.com/<http://certificatesforexchange.com/> for 
certificates from just $23.99.
Need a domain for your certificate? 
http://DomainsForExchange.net/<http://domainsforexchange.net/>



From: John Cook [mailto:john.c...@pfsf.org]
Sent: 10 November 2009 15:39
To: MS-Exchange Admin Issues
Subject: Re: Exchange 2010 RTM?


From a business standpoint you have to understand they came to a point where 
they had to cut off development to make a deadline for RTM. From an admin 
standpoint I think it sucks when you lose that kind of functionality, I'll wait 
till SP1, maybe they'll get to it by then.
John W. Cook
Systems Administrator
Partnership For Strong Families
Sent to you from my Blackberry in the Cloud

________________________________
From: John Bowles
To: MS-Exchange Admin Issues
Sent: Tue Nov 10 10:27:22 2009
Subject: RE: Exchange 2010 RTM?
The argument is that when you add more complexity to an application you're 
going to have more complexity in the configuration.  Honestly, they could of 
kept majority of that functionality in the GUI.  I think it was a vast attempt 
to appease the CL weenies of the world.  And it back fired IMO.  I like E2K7, 
but I think they alienated majority of the population that buys their product.  
The GUI configuratbility from an Admin/Engineer standpoint is one of the big 
reason's Exchange stood out from the pack from the rest of the messaging 
platforms.


John Bowles

________________________________
From: John Hornbuckle [john.hornbuc...@taylor.k12.fl.us]
Sent: Tuesday, November 10, 2009 10:22 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2010 RTM?
I have no clue what MS was thinking when they made that choice.

Adding functionality to the CLI is great. But who, exactly, thought it would be 
a good idea to REMOVE functionality from the GUI?




John Hornbuckle
MIS Department
Taylor County School District
318 North Clark Street
Perry, FL 32347

www.taylor.k12.fl.us<https://outlook.com/owa/UrlBlockedError.aspx>



From: John Bowles [mailto:john.bow...@wlkmmas.org]
Sent: Tuesday, November 10, 2009 10:13 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2010 RTM?

+1


John Bowles

________________________________
From: McCready, Rob [rob.mccrea...@dplinc.com]
Sent: Tuesday, November 10, 2009 8:34 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2010 RTM?
Has anybody played with Exchange 2010 yet?

I’m curious to know if they incorporated any more functions into the GUI.

This PowerShell stuff of typing in 240 characters for one simple requests is 
for the birds.  Holy step backwards.


From: Andrew Levicki [mailto:and...@levicki.me.uk]
Sent: Monday, November 09, 2009 4:10 PM
To: MS-Exchange Admin Issues
Subject: Re: Exchange 2010 RTM?

Hi Troy,

It was in the news.
http://msexchangeteam.com/archive/2009/11/09/453096.aspx

And it comes shortly after they announced it was Code complete:
http://msexchangeteam.com/archive/2009/10/08/452775.aspx

Enjoy!

Andrew

2009/11/9 Ben Scott <mailvor...@gmail.com<mailto:mailvor...@gmail.com>>
On Mon, Nov 9, 2009 at 3:58 PM,  
<tbarnh...@rcrh.org<mailto:tbarnh...@rcrh.org>> wrote:
> I thought we were still months out on these.  Is this correct that this is
> the RTM?
http://www.lmgtfy.com/?q=exchange+2010+rtm

-- Ben


NOTICE: Florida has a broad public records law. Most written communications to 
or from this entity are public records that will be disclosed to the public and 
the media upon request. E-mail communications may be subject to public 
disclosure.

________________________________
CONFIDENTIALITY STATEMENT: The information transmitted, or contained or 
attached to or with this Notice is intended only for the person or entity to 
which it is addressed and may contain Protected Health Information (PHI), 
confidential and/or privileged material. Any review, transmission, 
dissemination, or other use of, and taking any action in reliance upon this 
information by persons or entities other than the intended recipient without 
the express written consent of the sender are prohibited. This information may 
be protected by the Health Insurance Portability and Accountability Act of 1996 
(HIPAA), and other Federal and Florida laws. Improper or unauthorized use or 
disclosure of this information could result in civil and/or criminal penalties.
Consider the environment. Please don't print this e-mail unless you really need 
to.


This email and any attached files are confidential and intended solely for the 
intended recipient(s). If you are not the named recipient you should not read, 
distribute, copy or alter this email. Any views or opinions expressed in this 
email are those of the author and do not represent those of the company. 
Warning: Although precautions have been taken to make sure no viruses are 
present in this email, the company cannot accept responsibility for any loss or 
damage that arise from the use of this email or attachments.

Reply via email to