July 28th, 2014
You want to query AD, Exchange, SharePoint, etc. to quickly retrieve some basic, but really useful information about something really common. Examples: users, sites, etc. And of course you want to export these values to a CSV so you can sort, filter, aggregate, count, etc. in Excel or some similar tool. One or more of the values that you’ll retrieve – usually the most important ones, in our experience – is not a single value, but instead, a set of values (e.g., a user belongs to multiple groups, or multiple distribution lists.) Easy, right? Not so much.
PowerShell queries on fields/objects that naturally yield multiple results don’t return the values when you use the Export-Csv cmdlet, even when the values are displayed in the PowerShell console itself.
October 26th, 2012
Out of the box a My Site is limited to a maximum of 100 MBs, and generates a size warning at 80 MBs. Those last 20 MBs can .go quickly, and SharePoint will not allow users to create or upload new documents once they’ve hit that limit… Worse yet, that limit may present as other types of errors, making it difficult to pinpoint – for example, auto-syncing OneNote 2010 Notebooks will simply generate errors during sync, and the errors you get are not clear and obvious. (This, in fact, is the use case that inspired this post).