The Three UC Amigos : How can I analyze my public folder usage?
Stranger things have happened...
Dad, iPhone/Apple fanboy, beginning guitarist, runner, Enterprise 2.0, collaboration/communication.Working as a Windows sysadm, with primary responsibilities towards Exchange, OCS, Sharepoint.
I think all the friggin' time, and I get way too many ideas I want to execute in real life, but either don't have the time or competency for. So I try to pick the ones I can execute, or find exciting enough that I may gain the competency to execute.
Enterprise 2.0/Social Media is definitely something I want to get more into. Not because it's hot now. But because it's useful, and has enormous potential to change how businesses do business.
I hope you find my blog, and the links I share, useful or funny. Maybe even inspiring. Who knows ?
In any case: Welcome :)
Filed under
Exchange
Exchangepedia Blog: iPhone OS 3.1 Security Changes and Exchange ActiveSync Policy
With the latest iPhone OS 3.1 update, iPhones start identifying themselves correctly, and if the ActiveSync policy configured by the administrator requires device encryption (see Figure 1 below), data on the device is encrypted. That's great news— unless you happen to have an older iPhone. If you're using the (Original/Classic/2G/1G?) iPhone , or the iPhone 3G, and device encryption is required, you will be unable to log on to your mailbox.
Important to remember these days, when execs start sporting iPhones.
Comments [0]
Exchange/AD: Finding users whose mail is forwarded
I was asked earlier by one of my colleagues, if there was a way to find out which users have their mail forwarded to other users. I answered no, cause I don't know of a way to do that. So, just now my colleague Thomas presented me with the answer:
get-qaduser -SizeLimit 0 -IncludedProperties altrecipient -ldapfilter '(&(mail=*)(altRecipient=*))' | Select-Object -property "name","description","altrecipient" | where {$_.altrecipient -like "*Put a name here*"}
Pretty cool :) Updated at 17:14, the powershell code was a bit too long ;)
Comments [0]
Comments [0]