So, how many of your Exchange 2003 users are using cached mode? This script can pull that information through WMI for current logged on users.
So, how many of your Exchange 2003 users are using cached mode? This script can pull that information through WMI for current logged on users.
We have been exporting some mailbox information manually and I was sort of tired of doing it that way. I thought I'd try to make it work with PowerShell to automate it and add some consistency. It took some experimentation and here it is.
It saves to a file, ServerName-Date.csv in the directory it's run from. It has Display Name, Storage Group Name, Store Name, Mailbox size (in kb like ESM) and Date Discovered Absent in DS (which is short for when the Active Directory account the mailbox was associated was deleted).
I learned this neat trick with PFDAVAdmin last year. We had a performance issue with our Exchange servers and one thing I learned was that people not in cached mode with high item counts in their folders affected everyone on the servers performance. If you only had one or two, then not so bad, if you had a lot then not so good. You can identify potential people with the ExMon tool and Performance Troubleshooting Analyzer. This is a server side part of an earlier Outlook tips post where you can find the folder item count recommended numbers.
Recently we had an perceived performance issue with our Messaging environment. Ultimately it came down to high DiskIO and a large number of people with high Item Count in top level folders.
This is a collection of tips that can help improve/mitigate MS Outlook’s performance with an Exchange server. Complete Outlook/Exchange performance relies on a lot more.
Here is the start of a script to pull user information into a tab seperated file from Exchange users.
Thought I'd see what this Technorati stuff does.