Ramblings from The Montopolis Group

Building better businesses… with Technology

Archive for June, 2008

Fun with Exchange SP1’s EWS

I also could not get a clean Test-OutlookWebServices in Exchange 2007 SP1 as Joel Stidley mentions on his post here

But prior to that I was getting “403: Permission Denied” errors.  Nothing I tried worked. 

So I ended up removing just the Exchange Web Services or EWS with Remove-WebServicesVirtualDirectory and recreating it with New-WebServicesVirtualDirectory.  This restored EWS to its defaults.  That fixed my 403 problem quickly.

Then I started getting the “401: Unauthorized” as Joel mentions on his post.  I opted for Method 2 (no reboot). 

After that, my EWS came up without any issues…

I tested inside and outside hosts with Outlook and Communicator, all passed.

Test-OutlookWebServices ran clean. 

Outlook connection status (ctrl-right click on running icon) and Test Autoconfiguration all were clean and reconnected quickly. 

Event logs were all clean to boot!!!!!

To make things even better, I was then able to switch Outlook RPC/HTTP authentication to NTLM and it worked flawlessly!  For some reason previously it only worked in Basic mode, and under some circumstances would annoy outside users with unnecessary credential checks. 

We in IT are responsible to enforce the fewest credential checks necessary, while not compromising anyone’s security.   Credential checks should also use the most secure and resilient form of communication available at the time of that check.

So if your Outlook RPC/HTTP and/or Communicator are complaining about communicating with Exchange, my first step would be to rebuild EWS. 

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Google
  • E-mail this story to a friend!
  • LinkedIn
  • Live
  • Print this article!
  • Technorati
  • 0 Comments
  • Filed under: Exchange
  • If you have a:

    •EPSON GT-6700

    •EPSON GT-S60

    •EPSON GT-S600

    •Canon CanoScan FB1210U

    •Canon PIXMA MX 300

    •Canon CanoScan LiDE 90

    •Canon CanoScan LiDE 500F

    •HP Officejet 7210 All-in-One

    REF: http://support.microsoft.com/kb/943087/en-us

    The Microsoft Office Document Scanning tool may crash after installing SP1 of Office 2007. Microsoft is aware of the issue, but currently has no fix for it.

    Follow these steps to disable OCR, which crashes the scanning wizard…

    1. Select your Preset for scanning then expand the Preset Options drop down and select Edit.
    image-thumb Microsoft Document Scanning OCR Fatal Error w/ Office 2007 SP1

    2. Go to the Processing Tab and deselect Use OCR
    image-thumb1 Microsoft Document Scanning OCR Fatal Error w/ Office 2007 SP1

    3. Because Scanning Uses OCR to name the file, disable automatic naming by going to the output tab and changing the File Name to Date and Time.

    image-thumb2 Microsoft Document Scanning OCR Fatal Error w/ Office 2007 SP1

    4. Hit Ok and try and scan something now!

    Share and Enjoy:
    • Digg
    • Sphinn
    • del.icio.us
    • Facebook
    • Google
    • E-mail this story to a friend!
    • LinkedIn
    • Live
    • Print this article!
    • Technorati
  • 0 Comments
  • Filed under: Tips