• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 385
  • Last Modified:

Exchange

Hi

WHY, the modern Microsoft Exchange has become so painful to troubleshoot?

I remember Exchange 2003 and prior, installation and troubleshooting is a breeze. If you are unhappy with the installation, simply go into Control Panel>Add and Remove programs then uninstall.

Today, I was onsite installing SMB 2011 and the bloody thing took ages to complete the installation. Then, after the install, the Exchange mailbox role wasn't installed. Tried installing the mailbox role manually through Exchange 2010 SP1, the bloody things says that PowerShell>Virtual blah blah blah was already installed in the Defaul Website. Then, what a painful trying to uninstall the silly thing.

If you google Exchange 2007 and 2010, there are some many issues you come across with varying difficulty of issues.

These days, uninstall Exchange 2007 and 2010 become sacred event...you cannot just delete parts of its from the IIS, or make some changes on the default policy email etc etc. or if you HUB transport fucked up, you going to have tough time trying to figure out your out from the issue.

Further, the modern Exchange becomes tangled well with the AD, it is like deep entrenched with the AD scheman,  so you cannot just untangled the stupid thing and it is pain in the neck to try to bloody troubleshoot the silly thing. I'm well versed with the old Exchange but it doesn't help with the new ones since they are binded with the domain and AD schema etc r and removing Exchange maybe required a rocket science degree???????

Not sure WHY f*cking Microsoft made it very tough for Exchange admin and administrators to administers a once simply and easy to manage server/client application???

Apologies if I"m portraying Exchange as cumbersome application but it appears very much that way.

What's the best practice to install the modern exchange without LESS hasshle and troubled free if you want to uninstall it????

Appreciate your feedback
0
mcse2007
Asked:
mcse2007
  • 3
2 Solutions
 
Rob WilliamsCommented:
I am assuming you are familiar with Exchange but not SBS. SBS is not server standard and you must accept defaults and use wizards. Exchnge is integrated with SBS and cannot be uninstalled. I recomend some reading on SBS before proceding. Exchange is and always has been very tightly integrated with AD and DNS. It will not and never would work with out either. The following has some great SBS pointers
http://social.technet.microsoft.com/wiki/contents/articles/small-business-server-2011-standard-build-document.aspx
0
 
GusGallowsCommented:
My best advice is don't install it under Small Business Server and do not install it on a Domain Controller. All of my Exchange servers (exchange 2007) are on stand alone Windows 2003 x64 servers with no other roles installed. For Exchange 2010, it is still a good idea to put it on it's own Windows 2008 R2 x64 servers. It is still going to be tied heavily into AD (nature of the beast) but that actually is a good thing when it comes to doing a disaster recovery of an exchange server. Back in the day when Exchange had it's own directory (Exchange 5.5), it was a bit of a bear to recover.

Small business server incorporates a lot of additional overhead and seems to be widely problematic.
0
 
Rob WilliamsCommented:
>>"What's the best practice to install the modern exchange without LESS hasshle and troubled free if you want to uninstall it????"
To further explain. With SBS 2011, follow the build document provided above and install SBS. Then run the "connect to the Internet wizard" and then the "set up your Internet address wizard". The latter will completly configure IIS, DNS, and Exchange. You cannot uninstall Exchange.
0
 
Rob WilliamsCommented:
SBS is really only problematic for those that are not familiar with it. SBS is it's own "keetle of fish". Very qualified technicians have numerous problems with it because they try to configure components manualy. It cannot be done with SBS. There are far too many integrated services to manualy configure any serveice as you would with server std versions.
0
 
mcse2007Author Commented:
I've connected the server to the internet ran HP Smartstart disk including the SBS O/S disk and configured the rest...finally!
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now