Okay I still suck and PowerShell…but my problem isn’t PowerShell…. it’s that I turned off IIS logging because on SBS 2008 the dang thing’s WSUS IIS logs hog room on the drive.
Parses log files from the default log directory “C:\WINDOWS\system32\LogFiles\W3SVC1″ to “C:\output.csv”
I don’t have that folder…. but there’s more ways to find out exactly what devices are hanging off the server in a small firm.
1. Ask them. Walk around, make sure you understand the network topology, the people you’ll be interacting with and while you are there ask them what applications they need to work and what mobile devices they use.
2. Check the DHCP/IP address table in either the SBS box on the network or in the router table.
3. Look in the Exchange ActiveSync section of the mailbox and …okay okay we can script this:
But you can do it this way too:
And while you are there you can delete out old partnerships…
Like I haven’t had an android touchdown since 2011.
IMAP and POP3 Logfile analysis
By default IMAP and POP3 logging are not enabled within Exchange 2007. If you have enabled IMAP or POP3 and want to discover those clients, you’ll need to enable Protocol Logging in advance.
I really don’t see why someone would need imap or pop3 if you have a phone client that has a solid activesync protocol. So I’m going to assume you are like me and don’t use imap or pop3. If you use popconnector in SBS 2003…. it’s really and truly time to cut the cord on that or move to Office 365.
Blackberry Enterprise Server
We need to collect two key pieces of information about the Blackberry Enterprise Server – firstly the number of enabled users to feed into the sizing. Secondly we need to check the version of BES that is currently in use so we can ascertain if it requires an upgrade.
Got Blackberries? I hope not as you’ll probably need a separate server to run a BES deployment on it.
For our edge firewall we’ll rely on what we have and then a combination of URLrewrite as well as ARR application request routing in order to handle multiple web sites on the same server.
Finally we will collect information about our MailEssentials gateway. The product we’re using interfaces with SMTP using the IIS SMTP Service, therefore we can use the IIS Management Console to examine accepted domains and relay settings. The location of the settings for the product you use may vary, however the information that must be collected is approximately the same.
In my case I use www.Exchangedefender.com which will be able to hold the mail during the migration. (and if my blogging has entirely freaked you out, contact Exchangedefender.com to also do a migration to their hosted email platform, bug I digress…)
I don’t have a IIS smtp gateway but I do have a mail relay/smtp connector setting I need to make sure I document:
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