There appears to be a problem with the new  ADSMConnect Agent for
Microsoft Exchange.  While running my initial evaluation on our test
Exchange site, it appeared to be a solid product.  After putting it on a
test server in our production site my feelings changed.
        The backups seem to work just fine.  Filespaces are created on the
ADSM server so I can assume this half is of the process is working.
Restores are a different animal.  When trying to browse the filespace to get
a list of backup versions I receive the message:

        ACN125E - The specified database objects are not available on the
selected ADSM server (dsm).

        The filespace name on the ADSM server is made up of
"ORGANIZATION.SITE.SERVER.DIR" or ".IS".  I am guessing the problem could be
caused by how our Exchange Organization is named.  Our name has a "." at the
end of the name, so the filespace is created as "Company,
Inc..CTIX.EXCH01.DIR".  I am thinking the two periods in a row could be
causing the problem.
        Has anyone else experienced this problem during testing?  Is the a
fix available?  A case has been opened with IBM but have not heard back from
them on this being a problem.

        Jim