Next up … http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part4.html

In the next step of the blog post they have you connect into WSUS and make sure all the clients are communicating.  In our case we already have WSUS installed as we’re coming in from SBS 2008.  But we’ll take the time to ask ourselves how we’re going to handle patching in the future?

You could put WSUS back in the network and can possibly put it on the Essentials server – or you can opt to go with Intune and have all the workstations connect into patching that way (keep in mind that intune still does not support servers.

Alternatively you can let each workstation just go to Microsoft updates for their patches… but… do you really want to not manage patches?  Bottom line use WSUS to review what workstations have what, know that Outlook 2003 clients have to be updated and decide what you will do with WSUS.

Next up is determining who connects to the server via Active sync…..

IIS Logfile Analysis (The easy way)

We’ll move on to other clients next, starting with clients that communicate with Exchange via the Web, including searching for clients including:

  • Outlook – covering off any external, non domain-joined and seldom used clients using Outlook 2007 or above.
  • Outlook 2011 and Entourage 2008 Web Services Edition and Mail Mail.
  • Older WebDAV clients such as Entourage 2004 and non Web Services editions of Entourage 2008.
  • ActiveSync clients from all vendors.

LogParser is one option for collecting this data, but for our organization we’ll use a script I’ve prepared earlier specifically written to collect data for Exchange 2007 upgrades, which can be downloaded from my website.

After extracting the downloaded script onto the Exchange 2007 server hosting the Client Access role – in our case our multi-role server, we’ll execute it specifying the path to the IIS Log Files, choose to analyse 30 days of log files and specify an output CSV file IISAnalysis.csv:

.\ExIISLogParser.ps1 -LogFilePath C:\inetpub\logs\LogFiles\W3SVC1 -Days 30 -OutputCSVFile .\IISAnalysis.csv

Upon executing the script, you’ll see the progress as log files are analysed. This may take some time, so if you like coffee you might want to grab one:

Or in my case I have to go ask someone why this isn’t working because once again either I totally SUCK at PowerShell (which is true), or SBS 2008’s implementation of Exchange is just odd enough to not work with all of these normal Exchange scripts.

As once again a script doesn’t work like it’s supposed to. 

(Don’t you just love reading my blogs and seeing how frustrated I get with PowerShell?  Just when I think I get it, I realize I don’t.)

As an aside I wonder if it’s too late to sign up for this?

PowerShell for Exchange Administrators | Windows IT Pro:
http://windowsitpro.com/powershell-exchange-administrators?promo=EP14203&NL=Promo_WIN_GC_030414PowerShellExchange_4&E_ID=15757939&NLL=3960

Blogging my way (starting over) through a proof of concept migration from SBS 2008 to Essentials 2012 R2 series will be a SMB kitchen project whitepaper.  More about the SMBKitchen project at – http://www.thirdtier.net/enterprise-solutions-for-small-business 

 

Comments are closed.