Work station on Domain, HQ & DVM on no domain.

[shork]

Hello all,
Do the call manager function when the HQ and DVM servers are not in the same Domain as the user's Workstations.

Thanks,

[Palitto Consulting]

I believe ShoreTel recommends against joining DVM/HQ servers to domains. Group policies can sometimes have unexpected effects on these servers. As such, many installs do not have them joined to any domain.

[grdne1]

The documentation reports that you should install the ShoreTel server software first then join the Windows server to the domain. I am not sure on what version those recomendations changed, but this is in the v9.1 manual.

We have our ShoreTel servers on the domain and started using AD Auth for Call Manager and Director authentication immediately after upgrading to v9.1. That feature is very nice and will not work without a domain joined ShoreTel server.

[Palitto Consulting]

Thank you, you are correct. This feature is new with 9.1 so I had not considered the implications yet.

[shork]

DVM/HQ=No domain User desktops=domain

I believe ShoreTel recommends against joining DVM/HQ servers to domains. Group policies can sometimes have unexpected effects on these servers. As such, many installs do not have them joined to any domain.

Hello,

I intend to have the DVM/HQ server in no domains because the effect of joining the current domains is not known. Is there any effect on the call managers functionality if the users desktops are in a domain while the HQ/DVM server is out of the domain.


Any info

[grdne1]

I believe it will work fine as long as you plan to keep ShoreTel client passwords seperate from Active Directory passwords. Single Sign On is the only feature I am aware of that you would not be able to use.

The SSO feature got my boss excited and others in my dept as well due to password resets for Call Manager. Nobody ever rememberd what there client password was when they had to move to another machine or after a re-image.

[aclements]

I've done just about every combination of joined/not joined on the ShoreTel server and workstations. In general ShoreTel PCM always works regardless on any domain membership.

I've had ShoreTel server not joined to domain with PCs joined - works great (this is the norm)

ShoreTel server joined to domain and PC not joined - also works.

ShoreTel server joined to domain and PC joined to another domain - also works, no problems.

I've also tested AD integration (much less extensively) and all the above scenarios continued to work, except single sign on was obviously not available to everyone; regular ShoreTel password auth continues to work fine though.


If there are going to be any issues with having the ShoreTel server joined to a domain, in my experience it isn't going to be with getting call manager working. It'll be something like DCOM errors, or permissions getting applied that prevent some process from running right on the server.

[shork]

I've done just about every combination of joined/not joined on the ShoreTel server and workstations. In general ShoreTel PCM always works regardless on any domain membership.

I've had ShoreTel server not joined to domain with PCs joined - works great (this is the norm)

ShoreTel server joined to domain and PC not joined - also works.

ShoreTel server joined to domain and PC joined to another domain - also works, no problems.

I've also tested AD integration (much less extensively) and all the above scenarios continued to work, except single sign on was obviously not available to everyone; regular ShoreTel password auth continues to work fine though.


If there are going to be any issues with having the ShoreTel server joined to a domain, in my experience it isn't going to be with getting call manager working. It'll be something like DCOM errors, or permissions getting applied that prevent some process from running right on the server.

Thanks you for the information.