Month: April 2009

Security warning pops up when using Outlook2007 and Exchange 2007

After a recent migration of mail to Exchange2007, we’ve just started getting users logging tickets where a security window pops up saying “The name of the security certificate is invalid or does not match the name of the site”. This can happen even when the client is not at their desk. It took a few seconds to work out what was causing it – the clue was that the window had an icon in the taskbar for outlook. Searching in Google found Microsoft’s KB article 940726 with the resolution to the fix which involves changing various internal url attributes.
The instructions are fairly straightforward but I wanted to see what the values were set to before making the change. As I’m not very familiar with powershell it took me a while to work out what I needed.
For the command

Set-ClientAccessServer -Identity Servername -AutodiscoverServiceInternalUri https://name.contoso.com/autodiscover/autodiscover.xml

you want to run the command

Get-ClientAccessServer -Identity Servername | fl
The pipe fl provides all the values in a list – if you don’t include this part of the code you will end up with one line containing the name of the server – a value that you hopefully know already!
I really need to get cracking on my powershell skills – I still prefer good old fashioned dos batch programming but now that we’ve started to roll out powershell across all machines, powershell skills will be in demand more and more.

4 Years in the States.

Monday was our fourth anniversary of being in the States. As it is now Wednesday you can tell I forgot! I did actually realize it yesterday but I ended up working until 8.30pm last night on a very weird networking issue so didn’t have time to celebrate or anything.
I was back in the UK for 5 days over Easter to attend the funeral of my Uncle which was a sad occasion, but it was nice to meet up with other family members and some relatives I’d only met a couple of times.
People often ask me if England is much different to Ohio and normally I would have said no, but having been back I would have to say it is fairly different. When Kristen’s parents came over to the uk when we were living there, they would often remark how narrow the roads are, how green everything is, people’s accents are so amazing and does it always rain this much? My observation whilst I was back was how narrow the roads are, how green everything is, people’s accents are so strong and I wish it would stop raining! Actually that last bit was not strictly true as the weather wasn’t too bad – it rained heavily on the day we drove back from Croydon to Chesterfield – a 180 mile journey that took 6 hours – NOT fun – but the rest of the week was pretty good with just a few scattered showers.
I was pretty amazed at the strong accents I heard whilst I was there – although I was in Chesterfield there were a lot of people around with strong yorkshire accents but it was so different to hear all these different accents that I would have normally not paid any attention too. I still get comments about my accent over here in the States and still get asked to record people’s voicemail messages and to “just say something” to people when I’m introduced to them.

Exchange 2003 NDR’s are sent a long time after email was sent.

The past two reboots (where the server has been offline for a while) has resulted in non delivery reports being sent back to some of the mailboxes for mail that was sent several weeks ago and that had not been reported as failed when the mail was initially sent.
The first time this happened I thought it was just one of those things, especially as I had not seen mail in the queue before rebooting the server. After the second occurrence I knew it was time to investigate.
SBSisyphus has a great posting including a link to the exchange2003 (sp2) patch that should fix the “kb950757 Email senders do not receive an indication that some messages have been held by Exchange Server 2003 until the SMTP service, The Microsoft Exchange Information Store service, or the Exchange server is restarted”. I applied it to my machine and I’ll have to see what happens.
For what it’s worth you do not need to reboot the server (unless wmiprvse.exe is running – but you get an option to kill this process if it is running before proceeding) but it will stop and start your mail and web services so don’t apply it during the day and it goes without saying that you should have a backup first.