Permabanned
- Joined
- 28 Dec 2009
- Posts
- 13,052
- Location
- london
Does anyone else hate exchange 2010 as much as me?
I thought new versions of software was meant to be an improvement? I am yet to see one improvement with the software. It seems to me like they just added 5 steps to ever simple function and then took most of the functionality out of the gui and put it in to the command shell, which is beyond atrocious.
For a simple function like how to see the size of mailboxes you have to use a command like this
(Get-MailboxDatabase) | Select-Object Name,@{Name="Number of users";Expression={(Get-Mailbox -Database $_.name).Count}}
Who thought of this ? Before it would just display in a column in the gui.
Do you think they did this to add extra learning curve to it, so that it makes the training and usage of the software more difficult, in order to make the administration of it more scarce and ultimately sell more over priced training courses. Or was it just the usual lazy programming from microsoft, instead of making a solid software they ware more focussed on creating a fullscreen windows 2012, which also looks atrocious.
Don't get me wrong, i have no problem with CLI, ive been using linux for 15 years. But when there is software that has functionality in a gui, i don't expect the next version to move all the functions in to the CLI just for the fun of it. Don't come with that, its more powerful that its now in the CLI, non sense. It takes up more of time, it requires me to learn things that i didn't need to know. waste of time =! more powerful.
I would hate to see how bad 2013 is and wonder if its soon will be all CLI based because some lazy programmers at m$ can't be bothered putting the functions in to the gui. So while im playing with my fullscreen blocks i can load the exchange gui and type a programming code to just see basic functions.
I laughed when something that was a basic feature in 2003 required me to write a script and then add it to a windows scheduler because M$ coulnd't be bothered creating an ACL For the exchange databases. Now they have changed it for no good reason and you have to use asdi edit or windows scheduler to change top level exchange permissions.
I thought new versions of software was meant to be an improvement? I am yet to see one improvement with the software. It seems to me like they just added 5 steps to ever simple function and then took most of the functionality out of the gui and put it in to the command shell, which is beyond atrocious.
For a simple function like how to see the size of mailboxes you have to use a command like this
(Get-MailboxDatabase) | Select-Object Name,@{Name="Number of users";Expression={(Get-Mailbox -Database $_.name).Count}}
Who thought of this ? Before it would just display in a column in the gui.
Do you think they did this to add extra learning curve to it, so that it makes the training and usage of the software more difficult, in order to make the administration of it more scarce and ultimately sell more over priced training courses. Or was it just the usual lazy programming from microsoft, instead of making a solid software they ware more focussed on creating a fullscreen windows 2012, which also looks atrocious.
Don't get me wrong, i have no problem with CLI, ive been using linux for 15 years. But when there is software that has functionality in a gui, i don't expect the next version to move all the functions in to the CLI just for the fun of it. Don't come with that, its more powerful that its now in the CLI, non sense. It takes up more of time, it requires me to learn things that i didn't need to know. waste of time =! more powerful.
I would hate to see how bad 2013 is and wonder if its soon will be all CLI based because some lazy programmers at m$ can't be bothered putting the functions in to the gui. So while im playing with my fullscreen blocks i can load the exchange gui and type a programming code to just see basic functions.
I laughed when something that was a basic feature in 2003 required me to write a script and then add it to a windows scheduler because M$ coulnd't be bothered creating an ACL For the exchange databases. Now they have changed it for no good reason and you have to use asdi edit or windows scheduler to change top level exchange permissions.
