The IT Crownd

Since migrating our users to Exchange 2010 from Exchange 2003 we've had a few issues dotted around the organization where users are unable to edit or even view delegate information on their mailbox. A quick check in powershell shows that there are indeed delegates but these are delegates whose AD account is no longer around...simple fix really. To show all mailbox delegates try this... Get-Mailbox | Where {$_.GrantSendOnBehalfTo -ne $null} | select Name, @{Name='GrantSendOnBehalfTo';Expression={[string]::join(";", ($_.GrantSendOnBehalfTo))}} | Export-CSV C:\SendOnBehalfTo.csv The above will dump its output into a file on C: called SendOnBehalfTo.csv If you are dealing with just one customer you can simplify this to... Get-Mailbox <mailbox-alias>| Where {$_.GrantSendOnBehalfTo -ne $null} | select Name, @{Name='GrantSendOnBehalfTo';Expression={[string]::join(";", ($_.GrantSendOnBehalfTo))}} | ft -wrap In any case to remove a gho...

So we've been running SMSPS for a while now, well, easily for two months with no incident.  Until last week. We got some nasty looking notifications, with " Clone Backup DB Error " in the Statistical Result section of the notification. As we have SME too it was already known that there have been issues when a cloned LUN is dismounted after backup validation.  We wondered if this was happening in SMSPS. Opening up SQL Management Studio on the server runnning the DBCC installantly showed the databases mounted included clones used in the DBCC process. Looking in Snap Drive there was the cloned LUN mounted in the folder default location. After detaching the DBs from within SQL and then removing the LUNs from SnapDrive things looked good. Well looked until the backup ran that night :) This time we got " Error During Backup Raw DB " which sounded even more scary. Turns out there was one last DB still mounted in SQL. Cleaning that out sorted things ...

We had a brand new iPad arrive destined for one of our established users. Nothing out of the ordinary there.  However when the Service Desk team attempted to connect the device to our Exchange Active Sync site the device failed to communicate with Exchange. This was not a case of being unable to sync but a steadfast refusal at the first! No logs and no events generated at all  Great! User was enabled for EAS (as is the default) in Exchange so it wasn't that...hmmmm. We noticed that the Active Directory account wasn't inheriting permissions from the parent.  I couldn't be that.  Could it? Ba-Zinga! - Sorry Sheldon!? Some needed permissions were missing (i've no idea what) and ticking the inhert sorted these out. Why this tick wasn't there in the first place? Go figure.

I've now un-hindered the comments process.  Everyone can comment un moderated.  I will of course prune those comments deemed unsavoury :)

*phew* Finally got everything working with our SnapManager for SharePoint install.  Here's a few gotchas for those brave souls about to embark on a similar voyage of the damned :) Whilst the install is relatively straight forward, almost next, next finish infact the configuration is the opposite. There are quite a number of requests for credentials during the install.  I think we used just two accounts in the end, one for accessing the DFM and one to access SharePoint DBs.  Be aware that there is a "hidden" service running as a user account.  We found that the password was not transferred correctly from the installation wizard to the registry for this account.  Luckily there is a commandline tool to change the password. sdcli dfm_config set -host <hostname> -user <username> -pwd <password> As with all NetApp documentation.  Read it.  Read it and read it again.  Then ignore the majority of it and look elsewhere....

I've been looking for a way to make our NetScalers load balance the SMTP traffic to our Exchange 2010 environment. Here's a blog posting which shows you how to do it. http://citrix.stefanriek.de/citrix/howto-load-balance-while-preserving-a-clients-source-ip-but-not-using-the-netscaler-as-your-gateway/ Basically you need to make a new service group with ANY as the protocol on which you have enabled USIP. Then in the Virtual Server (again protocol ANY) you select the service group and enable MAC redirection. Here is the kicker. You now need to edit your Exchange server!  Well you need to add a loopback adapter with the IP of the Virtual Server in NetScaler.  Then enable weakhost receive and send on the loopback adapter and enable weakhost receive on the live adapter. netsh interface ipv4 set interface "Your production network adaptor name" weakhostreceive=enabled netsh interface ipv4 set interface "Your loopback network adaptor name" weakhostrecei...

I recently found out why our MOSS 2007 FEW which was hosted on a Windows 2008 R2 server was unable to provide MOSS sites. Whilst this was not a service impacting issue, we have plenty of other SharePoint 2007 FEWs so one less didn't matter plus this one was really just doing the Report Service bit in any case. However after a couple of weeks of getting annoyed at this I decided to look for a solution.  A quick trawl of Google later and I found this site which explains things nicely. http://sharepointspot.blogspot.co.uk/2008/12/sharepoint-kerberos-on-windows-2008.html Basically this is due to Windows 2008 R2 doing kerberos in the kernal and as such it ignore any SPN you may have in place and uses the computer object.  In principle this is a great thing, no more SPNs needed!  However poor old MOSS needs SPNs as all the website applicaiton pool MUST run using identities if you are using kerberos. Quick change to the C:\Windows\System32\inetsrv\config\applicationHos...