TMS as a part of the domain

[rfrome]

Does TMS need to belong to the domain in order to intigrate with AD or use the TMSXE connectors? If so, are there specific group policies in the domain that are know to have conflict with the TMS application?

Any best practices that exist around this would be helpful.

thx,

robert

[cfiestas]

Robert,

We recommend that tms must be part of the domain before deploying TMSXE in your environment

Cesar Fiestas

[teotodor]

You do not need tms to be part of a domain. It may even be in a domain different from the doman which exchange belong to. This is valid if you use version 3.0

[Kjetil Ree]

I would generally recommend adding TMS to a domain, but this is not a requirement. The main disadvantage of not adding it to a domain is that conference ownership will be wrong when booking from Outlook — if I book from Outlook as kjetil@example.org, a TMS not in the exmple.org domain thinks that a local account 'kjetil' owns the booking.

Sent from Cisco Technical Support iPhone App

[teotodor]

What can be the bigest problem in this scenario? Can it cause conferences not being booked? What can go wrong?