Eval of Windows 7, MCITP, and e-learning notes

 Posted by at 2:26 pm  Windows, Windows Research  Comments Off on Eval of Windows 7, MCITP, and e-learning notes
Apr 122010

I have a need to maintain my marketability and recent job searching has reminded me that I need to add a few certifications to my resume.� Towards that end I decided to use Microsoft’s e-learning to study for and pass (hopefully) the testes required for MCITP: Enterprise Administrator. MCITP stands for Microsoft Certified IT Professional, and it is the certification track to use for skill building with the latest topics such as Windows Server 2008, SQL Server 2008, or Exchange 2010. Visit the MCITP page at Microsoft for all the details.

I found navigating the Microsoft training website somewhat awkward at first, and it felt as though I was clicking around in circles until I got my bearings.� I purchased e-learning for the first three of five tests required for the MCITP: Enterprise Administrator, for roughly $1,300.00, and plan to practice my labs both online and on an instance leveraging my TechNet subscription and VMWare Fusion: my laptop is a MacBook Pro. I still need to purchase the last two tests, the complete list for MCITP: Enterprise Administrator is 70-640, 70-642, 70-643, 70-680 (my choice), and 70-647. Those I procured are for 70-640, 70-642, and 70-643.

I am taking the e-learning classes from Windows 7, built virtually in VMWare Fusion and will be making notes on that experience as I go.� I tried to initiate the e-learning lessons under Firefox from OS X and found that they would not load, luckily I had a Windows 7 instance already built.� I loaded the free “Microsoft Live” bundle of applications onto Windows 7, which gave me Live Mail among other apps which worked well with my passport account in hotmail.� But I haven’t yet seen if there is an office live linkage for Wordpad; I suspect there is not.

More to come…

Exchange 2003 client protocols

 Posted by at 6:10 pm  Windows, Windows Research  Comments Off on Exchange 2003 client protocols
Apr 042010

So why the generic subject of protocols under Exchange 2003? I had an interview the other day and one of the three consultant questioned the configuration of my Exchange server, stating it was a strange configuration that my clients were not connecting via MAPI and why we still relied on PST files. I replied that the clients connect either by IMAP or POP3, and felt a little caught off guard about his MAPI comment. Some searching on the net revealed what I already knew that there are three essential protocols: POP3, IMAP, and MAPI (known usually at client setup as MS Exchange Server). The later is what caught me, that I think of “MS Exchange Server” rather than its underlying protocol, MAPI.

So what then are the deciding factors whether to use POP, IMAP or MAPI? Some additional research was warranted.� My hypothesis is that the original design decision was performance related, and our hub and spoke WAN topology (data center with two remote branch offices) across T1s was the reason that POP was chosen.� This bears additional research.

On a different note my search also revealed that I need to regress myself from time to time and review the innards of my current configuration, if for no other reason that to stay frosty on those topics. For instance, one article from MSExchange.org by Henrik Walther, circa 2006, (“Explaining the MAPI Access Feature in Exchange 2003 Service Pack 2”) states that Exchange 2003 before Service Pack 2 there was no elegant way to disable MAPI access, and offered an explanation of how to enable or disable MAPI access on a per user basis: ADSIEdit and ADModify are involved. ADSI, by Microsoft, is meant to abstract the capabilities of directory services from different providers and provide a single interface.