Tips Exchange 2003

Gente aca va info de Exchange 2003, espero que sirva.

Saludos.

TSI: Setup


The following is a list of the top support issues and FAQ for Exchange 2003
Setup. All of these are BY DESIGN or known issues.


-
-

PROBLEM #1 - Running the Exchange 2003 ForestPrep appears to reset manually
indexed attributes to non-indexed.

CAUSE - This occurs if you have previously run Exchange 2000 ForestPrep and
then manually set indexing on certain Exchange attributes (such as a custom
attribute). The Exchange 2003 ForestPrep not only extends the schema for new
features and functionality in Exchange 2003, but it also re-applies the
original Exchange 2000 extensions.

SOLUTION - Use the AD schema manager to enable indexing of the desired
attributes



-
-


PROBLEM #2 - After running Exchange 2003 ForestPrep, bespoke and third-party
applications are logging error events due to a permissions error accessing
mailboxes.

CAUSE - These applications rely on gaining access to mailboxes through
membership of the Exchange Domain Servers group. However, on each Exchange
2003 ForestPrep and server install, a DENY ACE is placed on this group on
the 'Servers' container.

SOLUTION - As a temporary workaround, you can remove the DENY ACE through
Active Directory Sites and Services. You will need to add the registry
parameter as defined in Microsoft Knowledge Base article 225921 to complete
this procedure. For a more permanent solution, you should create a service
account/group and grant this "Send As" and "Receive As" permissions on the
appropriate Exchange configuration container (such as the Organization
object).



-
-


PROBLEM #3 - During upgrade/re-install of Exchange 2003, setup fails with
"Error code 0xC00706FD: The trust relationship between this workstation and
the primary domain failed".

CAUSE - One possible reason is that anti-virus software running on the
Exchange server is interfering with the setup process. This particular issue
has been seen when the "Symantec Antivirus/Filtering Service for Microsoft
Exchange 2000" was running (EXPS:225642).

SOLUTION - Temporarily stop the anti-virus service and attempt setup again.


-
-

PROBLEM #4 - When attempting to upgrade from Exchange 2000 to Exchange 2003,
a pre-req fails specifying that NNTP is not installed or disabled.

CAUSE - The administrator has disabled the NNTP service

SOLUTION - Temporarily enable the NNTP service, and re-attempt the upgrade



-
-


PROBLEM #5 - When attempting to install the Exchange System Management tools
(ESM-only), Setup prompts that is cannot continue because SMTP has not been
installed. However, the administrator is only attempting to install the
management components, not the full Exchange server.

CAUSE - The Exchange System Manager snap-in relies on the SMTP snap-ins to
manage the SMTP virtual server.

SOLUTION - Review the ESM-only pre-requisite list and install the necessary
components.


-
-


PROBLEM #6 - When looking through the Exchange Setup log, I notice an error
code of 0x000645 being returned when Setup attempts to uninstall the ASP.NET
Device Update component.

CAUSE - This error code translates to "Package not found"

SOLUTION - No action required. Setup was attempting to uninstall a component
that wasn't installed, so it just ignored the error.


-
-

PROBLEM #7 - After upgrading my Exchange 2000 front-end server to Exchange
2003, I've noticed that some of the new settings and virtual directories
were not installed. For example, I do not see the new OMA virtual directory
under IIS.

CAUSE - The System Attendant service is disabled on your front-end server.
The Exchange 2003 upgrade process modifies the Active Directory and relies
on the DS2MB process to replicate these new settings into the IIS metabase.
The DS2MB process runs as part of the System Attendant.

SOLUTION - Do not disable the System Attendant (MAD.EXE) service on
front-end servers.