Tag Archives: Exchange

Getting a stubborn Exchange Rollup Patch to Install

Over the course of a couple of days I’ve struggled to get an Exchange Server to install an update.  What I stumbled upon was an idea I’ll share now.  After repeated failures pointing to insufficient privilege, I discovered that while I couldn’t run the .msp package “As Administrator”, instead I could run an elevated command prompt that way and launch the .msp from that context.  Well guess what?  It worked!

While this was for Exchange 2007, I believe the concept is universal with any stubborn updates for any Microsoft products.  This means you have to manually download the patch locally too of course.

image

Advertisements

Direct File Downloading via OWA and Mobile Phones Now in SBS 2008

http://sbs.seandaniel.com/2008/07/allowing-owa-and-mobile-devices-to.html

Tested and verified.  This works, is simple to setup, and is cool!

Historical Post Series – ADSIEdit & ExMerge prep

The Historical Post Series are writings I produced in my former blog on Live Spaces and due their value are being reposted here.  Hope you enjoy these.

ADSIEdit.msc – to install and use for ExMerge Admin Mailbox Permissions

originally posted August 2006

Exchange 2003’s enhanced security permissions leave no default account or group with Read As and Send As permissions to Exchange Mailboxes (Enterprise Administrators, Domain Administrators, & the Administrator).  It is possible to alter the security permissions for a mailstore on its properties sheet by negating inheritance and then overriding the settings.  The only thing is it isn’t as easy to put the Genie  back in the bottle once you’re done with whatever task required this security breach.  With ADSIEdit it is possible to make the needed changes and revert back in a much cleaner way.

ADSIEdit is part of the Windows 2003 server resource tools.  In SBS these are found on disc 2 under the SUPPORTTOOLS directory.  Click support.msi, agree to the EULA, and they install.  Now you are able to type ADSIEdit.msc into the command window provided in the newly added Windows Support Tools program group.  This will invoke the tool.

A word of CAUTION.  Accidental keystrokes or mouse clicks could be extraordinarily calamitous and dangerous when using this tool – proceed with due caution.  You have been warned!

You will have to logoff and logon for the security token to be reissued with the changes.

Create DNS Service Location (SRV) records for the Exchange Autodiscover service

In earlier blog posts I’ve discussed other DNS records such as the TXT SPF record.  This is a new but very important record that you will want in place for your domain.

Here’s a list of great resources that describe this in detail and include guidance to manually create and publish the record to whomever is hosting your DNS records for the domain.

  • Sean Daniels very good explanation with examples

    Both of those will fail in the default SBS case as the info is actually at https://remote.contoso.com/autodiscover. With Outlook 2007 SP1 and above, outlook adds a third check. It checks a SRV record, or service. When you run the Internet Address Management wizard with a partner, this SRV record is automatically set. It looks like:

    _autodiscover._tcp IN SRV 0 0 443 remote.contoso.com

  • This blog post goes into what the syntax means piece by piece …a tech deep dive meant to tie in their chat client software to Google Apps.  They do have a tester there too.  Realize that in the GoDaddy record wizard that for SBS you enter @ for the Name field which represents your domain name.
  • Susan Bradley post on the same including a Go Daddy creation guide
  • Microsoft KB 940881- A new feature is available that enables Outlook 2007 to use DNS Service Location (SRV) records to locate the Exchange Autodiscover service
  • Test your record here – https://www.testexchangeconnectivity.com/
  • double-check to ensure that it was correctly published by those hosting your domain’s DNS records – my fav http://www.intodns.com (but I don’t see SRV record reported) – tech sent me to http://network-tools.com but none of the tests there seemed to fit