blog.wansend.com

April 18, 2007

Web Folders and OWA

Filed under: Exchange 2003 — wansend @ 4:39 am

Microsoft Outlook WebAccess and XP have an almost ready for prime time integration solution — Web Folders. To create a web folder, go into windows explorer (not IE) –>My_Network_Places –>Add_Network_Place –>Next –>Next –>paste in one of the links below –>next –>login as yourself –>next –>finish.

Next you can drag the “web folder” into your C-Drive or desktop for quick access. This can be nice for spreadsheets, word documents, and all.

Cons:

  1. You can’t map a drive to the Web Folder
  2. If you copy it to your desktop, it is just a shortcut
  3. Creating them is awkward
  4. You can’t easily create files in them by right-clicking, only from the spreadsheet
  5. The login box keeps popping up
  6. It may be slower than a mapped drive
  7. You can get to these files from the Internet – a pro and a con here
  8. If a second user opens the same file, he won’t be notified that it is already open
Advertisements

April 16, 2007

Exchange 2003 Mail Limits

Filed under: Exchange 2003 — wansend @ 7:21 pm

Exchange 2003 has many nooks and crannys that have to be known when you want to limit email size. Here are the four locations that I know of:

  1. Exchange SMTP
  2. Exchange Global Settings
  3. User Settings
  4. Windows 2003 Server IIS SMTP

1. Exchange SMTP. MMC–>Console_Root\Domain_(Exchange)\Administrative_Groups \MailDomain \Servers \ServerName \Protococols \SMTP \Default SMTP Virtual Server –> properties –> Messages tab. This one affects incoming message size from the Internet.

SMTP properties

2. Exchange Global Settings. MMC–>Console_Root\Domain_(Exchange)\Global_Settings\Message_Delivery –> properties –> Defaults tab. This one is applied secondly to incoming messages from the Internet. It is also the primary setting for internal mail limits. It can be overridden per user.

Global Settings

3. User Settings. MMC –>Console_Root \Active_Directory_Users_and_Computers[ad.domain.com] \domain.com \Users \Administrator –>Properties –>Exchange_General_Tab –>Delivery_Restrictions. This can be used to override the global settings for power users.

Per User Settings

4. Windows 2003 Server IIS SMTP. MMC –>Console_Root \Internet_Information_Services_(IIS6)_Manager \Windows2003Server \Default_SMTP_Virtual_Server –>properties –>Messages_tab. This was only used by me temporarily because our pop clients needed the old Mail 55 style of login that isn’t compatible with Mail2003. Our pop users used this for their outgoing mail to the corporate headquarters and out to the Internet. This is similar to the first location, but is managed in an entirely different place.

Windows 2003 Server SMTP

April 12, 2007

OWA 2003 web link redirect fix

Filed under: Exchange 2003 — wansend @ 8:30 pm

In Microsoft Outlook Web Access 2003, sometimes an email link to http://www.something.com doesn’t work. It brings up something like:

https://mail.domain.com/exchweb/bin/redir.asp?URL=http://www.something.com

Additionally, it either gives an error saying that the web page cannot be found, or a password prompt pops up.  When you try to close OWA by clicking Logoff, it also annoyingly asks for a password.

The “exchweb/bin/redir.asp” is a clue that you are now being transferred to a different part of the mail web server that has a problem with authentication.

The fix: bring up your MMC –> Internet Information Services (IIS6) Manager\mailserver\Web Sites\Default Web Site\ExchWeb –> right-click ExchWeb and select Properties –> Directory Security tab –> Authentication and access control “Edit” button –> Check the box that says “Basic Authentication” –> Fill in the default domain –> ok –> ok –> if it asks for sub-directories, Check all –> ok.

Microsoft info: http://support.microsoft.com/kb/817312

Screenshot of change:

Screen Shot

March 29, 2007

Exchange 2003 & 5.5 DST Patches

Filed under: Exchange 2003 — wansend @ 8:38 pm

All mail servers have been patched with the latest DST changes.  Workstations, however, are having a problem with calendar appointments being off by an hour for the rest of March. This Outlook 2000/2003 problem has a patch.

Description of problem: http://technet.microsoft.com/en-us/library/bb267339.aspx
Patch: tzmove.exe
Warning 1: Must already have XP/2000 DST patch for this to work (current updates)
Warning 2: Must be logged-in as an Administrator

I’ve fixed the Exchange 5.5 server on Windows 2000 Daylight Savings issue by updating it’s registry as described in http://support.microsoft.com/kb/914387

Step 1: Unzip tzupdate.zip onto a Windows 2000 PC. You must be an Administrator.
Step 2: Import global registry changes by right-clicking on Tzupdate.reg –> merge
Step 3: Run refreshTZinfo.vbs to apply the registry change locally. The script does not run verbosely.
Step 4: Verify with Regedit \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
DaylightStart REG_BINARY 00 00 04 00 01 00… should now be 00 00 03 00 02 00…
StandardStart REG_BINARY 00 00 0a 00 05 00… should now be 00 00 0b 00 01 00…
Check that the new numbers are on the PC.  These numbers are specific to Pacific Standard Time.

I tried running the Mail third DST patch, but it is already installed with Exchange SP2.  Here’s a guide that outlines all the patches: http://exchangepedia.com/blog/2007/02/dst-2007-understanding-what-needs-to-be.html

Apparently there is a calendar bug with calendar events created a long time ago.  Each old recurring calendar event needs to be reset to a more current date for the new daylight savings time to work properly.

Exchange 2003 changing postmaster @domain1.com to @domain2.com

Filed under: Exchange 2003 — wansend @ 7:44 pm

When your active directory domain doesn’t match your email address, you have problems. One of them is that your NDR and delayed mail warnings come from postmaster@domain1.com when it should be from @domain2.com. The fix can be found in your MMC:

JerrysMMC – Console Root\DOMAIN1 (Exchange)\Recipients\Recipient Policies\Default Policy –> Properties –> E-Mail Addresses (Policy) tab –> SMTP @domain1.com Change to SMTP @domain2.com. When you click ok, it will ask you if you want to update all users. I answer No. Answering yes will change all users affected by the policy to the new domain, which can be very bad.

Even if you have other Recipient Policies, the Default Policy determines the source of NDRs.

A Google search for this topic gives unintelligible answers about event sinks or solicits third party software.

NDR = Non DeliveRable email

Lastly, if the postmaster@domain2.com email resolves as a secondary address for a user’s account, Exchange will change the email to the primary address for the user – after about a day. This can be a plus if you want to change the NDR from-address to an address other than postmaster. In my case, I had to move the postmaster@domain2.com name over to another user so it could be the primary email address.

Blog at WordPress.com.