by Michael B. Smith, MCSE/Exchange MVP
Patching technologies have come a long way since Windows NT 3.5. (Yes, I've been
around that long. No, I don't want to talk about it!) Way back then, practically
every change to a server required you to reinstall the current service pack plus
any additional patches you might have been using. Similarly, Exchange 5.x often
required you to reinstall the Exchange service pack after making changes to the
Exchange application. And, of course, you ALWAYS rebooted after applying any
patch. And do you remember 'DLL hell' when differing applications required
different versions of the same DLL making it impossible to run certain
applications at the same time?
These issues are pretty much long gone (and good riddance!).
Continue reading...
You can restrict OWA to offering only OWA Light for a specific Virtual Directory
or for a specific user.
To set the restriction on the Virtual Directory for all users, you need to enter
the following PowerShell:
Set-owavirtualdirectory -id:<virtual directory ID> -PremiumClientEnabled:$false
To set it for a particular user, use:
Set-CasMailbox -id:<mailbox ID -OWAPremiumClientEnabled:$false
The user will see both the "Premium" and "Light" logon option but they will
always get the Light version, regardless of which option is chosen. This happens
because Exchange renders before it knows who the user is or which logon page
they are supposed to get.
Do you need to configure an Exchange server Public folder so that everyone can
send messages to the folder but only a few select users can read the messages?
After mail-enabling the folder, give Contributor permissions to Anonymous to
allow everyone internally and externally to send to the folder's address. If you
only want to allow internal users to send mail to the folder, set Default to
Contributor and Anonymous to None.
Then set the permissions for the other users or groups to a permission level
that includes Folder visible and with read and Delete all permissions. The
predefined permission levels of Editor and above will work or use custom
settings.
When you try to delete non-Task items that are flagged completed from the To-do
folder this warning dialog pops up:
Deleting this item will also delete the contact.
Do you want to continue?
This warns you that clicking Yes (to continue) will delete the item from its
folder as well as remove it from the To-Do list. This happens because the To-do
list folder is just a search folder for your tasks, flagged messages and
contacts and deleting the item for this folder deletes it from Outlook. If you
want to keep the item but remove it from the To-do folder, right click on the
completed check and choose Clear Flag instead. If it needs to remain marked
completed, create a custom view that hides completed items. You won't get this
warning for completed tasks since users know (or should know) that they are
deleting the actual task.
If you accidently click Yes, the items can be recovered from the Deleted items
folder. To easily find the item, add the modified folder to the view in Deleted
items then sort by it. The last deleted items will be on top.
If you attempt to use spell check and receive an error message
that says "The spelling operation could not be completed. The
word is too long for the dictionary", you either have a entry in
the custom dictionary that is too long or your custom.dic file
is corrupt.
Don't waste your time reinstalling or repairing Office. Locate
the custom.dic and either rename it or open it in Notepad and
look for the corrupt entry. It should be easy to spot as
normally the entries are one word per line and a corrupt entry
may be several words run together (forming a really long word)
or contain HTML code or other strange text.
The custom dictionary is located at %USERPROFILE%\Application
Data\Microsoft\Proof\Custom.dic in Windows XP and by default its
at %USERPROFILE%\AppData\Roaming\Microsoft\Uproof\Custom.dic in
Vista.
RSS
