Mailbox Archiving Task - Enable Mailbox stucks
Hi!
After the fix of my problems in the threads
https://www-secure.symantec.com/connect/forums/queues-a1-a7-missing-after-creation-mailbox-archiving-task
and
https://www-secure.symantec.com/connect/forums/exchange-archiving-task-gets-stuck-configuremsgservice
i have now a new problem. The Mailbox Archiving Tasks are complete created incl. all MSMQ-queues. That worked with registry key "DS server". Now, i deleted the Registry Key after some Synchronizations and some "Enable Mailboxes".
After i deleted the Registry Key, the following stucks:
- Enable Mailbox (=> No answer at enabling mailboxes for more than 15 min., no errors, no events)
- Synchronization in Mailbox Archiving Task (=> Queue a7 grows up)
- Disable Mailbox (=> No answer at enabling mailboxes for more than 15 min., no errors, no events)
I deleted the Key to reactivate the other Mailbox Archiving Tasks of the other domains/forrests, which would run inot error if the Key
Data type: REG_SZ (string)
Value data: FQDN of the global catalog server
Gerrit
for that other domain you may have to create a new EVAdmin for the site unfortunately.
So you may have the followingEVAdmin is a user in DomainA
DOMAINA -> All Exchange Server tasks work
DOMAINB -> All Exchange Server tasks work
DOMAINC -> All Exchange Server tasks do not work
If you use DS Server pointing to a GC in DOMAINC, the Exchange Server Tasks in DOMAINC work but DOMAINA\DOMAINB both fail....
So what you would do is the following
1, Create a new EVAdmin in DOMAINC
2. Give it the same permissions as DOMAINA\EVAdmin had on all the exchange servers (Send As etc)
3. Make the DOMAINC\EVAdmin a local admin on the EV Servers
4. Log on to the EVServer as DOMAINC\EVAdmin
5. Create an outlook profile to the DOMAINC Exchange Servers system mailbox for EV
6. Create the DS Server registry key pointing to the DOMAINC Global Catalog
7. Change the DOMAINC exchange server tasks to Run as the DOMAINC\EVAdmin identity
The reason this would work is that the DS Server is an HKEY_CURRENT_USER registry key which is tied to the user , where as HKEY_LOCAL_MACHINE is a machine wide setting that would affect everyone.
The Tasks do allow for different users to run them, so in this case you would leave all the tasks for DomainA and DomainB alone, and DomainC would run as an EVAdmin within that domain, then when the task runs, it runs as DomainC\EVAdmin, within that user profile it will read the DS Server registry key and connect to the specific Global Catalog.....the other domains will run as a different EVAdmin and not connect to that specific GC