|
Product Support Article
Article ID: PSA200309
A quick setup guide to the steps required in
installing and verifying that Directory Assistant is working
properly.
Applies To:
Directory Assistant 5.0 for Exchange 2000, 2003
and 2007.
Installation
Guide:
The main setup for the software should be
installed on a workstation that has Microsoft Outlook installed.
Once the console opens, it should prompt
you to select a mail profile that you want to use. You
should have a profile configured in Outlook that accesses your
mailbox.
After this the
console should tell you that you need to install the Directory
Assistant service before you can use the software.
Right-click on the service and select the menu option to Install
the service.
Installation of the
service requires you to select the server where you want to put
the service, the name of your IIS server and also the Active
Directory container where you want to create the user account
for Directory Assistant. The server where you choose to install
the service must have either Microsoft Outlook or the Microsoft
Exchange System Manager installed. A share is also
created on the server named “MADSDA”. This is where
settings and service files and logs are kept.
Notes:
If you decide to install the service on an
Exchange 2007 server please refer to the Support Article
PSA200308
The service installation attempts to give
certain permissions in your directory to the user account that
is created. Depending on your environment this may not
succeed if the account is not yet ready. If this occurs
you will get warnings but you will be allowed to continue the
service installation.
Verify that the new
user account created for Directory Assistant has the following
permissions or add them if the service installation was not able
to do so:
-
On the server
where it was installed: the local privileged for “log on as
a service” should be given to the account
-
On the server
where it was installed: it should be added to the local
Administrators group
-
It should be
added to the Domain Admins security group in your Active
Directory
Start the service if
it is not running after checking the above permissions.
After a few minutes, go to the “MADSDA” share on the server and
check the log file named “MADSDA Events”. This log file
should not list any errors. If it lists any errors and the
service has stopped then those errors will need to be resolved.
Open your Internet
Services Manager console for your IIS server. A new folder
with the name “DA” is created and the web pages for Directory
Assistant are placed in this folder. You will need to view
the properties of the “DA” web folder and in the Directory
Security section, turn off the “anonymous access” and select the
option for Windows authentication (this option may be named
differently depending on the version of IIS you are using).
In the policies
section of the Directory Assistant console, create a new policy.
The policy wizard will show you the attributes that are on your
Exchange template and allow you to select which ones you want
users to be able to modify. There are several options
available that you will see when selecting attributes to control
how they are modified.
Once you have
finished creating and saving your policy, go into the Users
section of the console and locate your user account.
Right-click on your account and choose the option to assign a
policy to your account. Select the policy you created.
Once a policy has
been assigned to a user they should now be able to use the web
pages. The page to connect to on your server is
“\DA\DAMain.asp”. If you receive any standard browser
errors such as “page not found” or “not authorized” those errors
are caused by IIS and will need to be resolved. Once you
can reach the DAMain.asp page you should see the blue background
for the page and a progress will tell you that it is working.
Once the DAMain.asp
page tells you it is working it is then contacting the Directory
Assistant service to handle the request. Once it has
processed the request the web page should then update to show
you changes that you can make to your information.
If you do not get a
page displaying your information and instead the “working” page
times out, then it means that the web pages and service are not
able to communicate.
If you get an error
that says you do not have a directory assistant policy, it means
there has been an issuing in matching the user account name or
domain name our console found versus the account or domain name
that the web pages are getting.
These issues can be
checked by looking at the “Directory Assistant.log” file kept in
the “MADSDA” folder. It will list errors and also will
show the domain and account names it is getting when users
access the pages.
When you assign a
policy to a user account, a data file is written in the
“MADSDA\Users” file folder. This will show you the domain
and user account name that our console is getting.
You can compare this with what the web pages are getting in the
“Directory Assistant.log” file to determine what is different or
missing that is causing a problem.
Once you have
successfully completed the above test and used the web pages to
make changes to your information the software should be fully
functional and you should be able to continue testing the
various features in the software.
|
