markulous wrote: » Build your own Exchange server. I'm not sure if you're in school but I know WGU gives out a copy of Exchange (2010 I believe) for free. Since you'll need licenses for Outlook/Office, you'll probably want to use OWA mainly on the client side. I have experience with O365/Exchange so it was pretty straight forward to set it up, create a couple distros, SGs, etc. Even without that experience, it's not too difficult. It's fairly user-friendly IMO.
cyberguypr wrote: » Many moons ago I read about Exchange and wasn't quite getting it. Once I started looking at the implementation we had in the office lab a lot of stuff made sense. Later on I deployed 2003 in my home lab, made it fully functional with one of my domains, then installed 2007 side-by-side and performed a migration. It was a beautiful thing. Exchange 2010 is still out there on Microsoft's site. If you run Hyper-V you can find an Exchange trial VHD. There's also 60 day office trials so if you run all this stuff on VMs you could easily go around the need for licenses. Finally, don't forget there are some Exchange labs at https://technet.microsoft.com/en-us/virtuallabs. I say definitely watch the videos but supplement them with lots of online content and perhaps a book or two. That in addition to the lab, is a recipe for a win.
NetworkNewb wrote: » There is a MCTS Exchange Server certification if you wanted to go that route. https://www.microsoft.com/learning/en-us/mcts-certification.aspx
N2IT wrote: » Aren't most organization going to the cloud based exchange, using 3rd party vendors? Rackspace etc. I would think having an understanding of vendor management and working with their support team would be number 1. Unless you are going to/trying to work for one of an MSP who offers exchange in it's portfolio.
N2IT wrote: » SQL is a niche thing, you just don't learn SQL at a competent DBA level. I wouldn't beat yourself up over that, Exchange is very similar, it's fairly niche. It sounds like to me they are asking to much of their candidates. I wouldn't stress it to much, obviously you want to make yourself marketable so that comes into play, but don't go wild trying to meet all the demands on these companies, you'll only stress yourself out.
kurosaki00 wrote: » If you just want to put the word exchange in your resume, just deploy it on a VM and play with it. Basic stuff in exchange are very easy and straightforward. Something neat to do is play with it with powershell.
JubeiYagaru wrote: » Sounds like a good idea. I'm polishing my powershell skills now, so this would give me a few more things to try with it.
kurosaki00 wrote: » Btw I just say to put it on your resume. Please dont go saying Super Over 9000 Exchange Admin-Engineer-person. I just meant like adding it as a skill or just saying Know how to admin accounts on exchange, something like that.
Chinook wrote: » The bulk of the work in Exchange is creating accounts, mail stores, permissions & general administration. The basic admin is not difficult, it's the architecting stuff that's complex.
N2IT wrote: » Chinook this is already taken place. The company I work for which is top fortune 20 and ALL of our subsidiary have all gone to Exchange / Office 365. It seems to make more sense. My friend works for a large credit company as well, fortune 500 and they are migrating to this as well.