Re: [cisco-voip] DNS and LDAP Domain name change - current process node is IP

From a server perspective, just make sure the forward A record and reverse PTR record for the new FQDN exist BEFORE using the CLI command to run the sanity check scripts to change the domain. You can change the DNS records shortly before running the CLI command, but not for long as it would even

Re: [cisco-voip] DNS and LDAP Domain name change - current process node is IP

Sorry the ask it so change from the DNS suffix of customername.us.com to customer.com. Also the users from customername.us.com have been moved into a customername.com OU on different LDAP servers with the same usernames. The servers are configured with a DNS domain and DNS servers but they proces

Re: [cisco-voip] DNS and LDAP Domain name change - current process node is IP

what are you trying to do? Do you need to add a domain name to UC servers that currently do not have a domain name? Sent from my iPhone On Nov 11, 2019, at 18:21, Nick Britt wrote:  A customer has had a domain name, this includes the DNS and the active directory integration. I am trying to p

[cisco-voip] DNS and LDAP Domain name change - current process node is IP

A customer has had a domain name, this includes the DNS and the active directory integration. I am trying to pull together the necessary steps for each application. Below is what I have deduced from the documentation so far *Change Domain name CUCM, Pub and Sub* The CUCM processNode name is the

Re: [cisco-voip] UCCX Callback Script

Tanner, That was tongue in cheek my man. I was really looking forward to having more of a conversation with you about the thread locking solution, and balancing the pros and the cons with it. Also, I'm still confused how you are doing your solution, pertaining specifically to keeping script 1 ali

Re: [cisco-voip] Webex Directory Connector Welcome Emails

Confirming this. You can also build your AD/LDAP filter accordingly in your directory connector application. However, this is a one shot deal. The license template on AD group helps you send them to the right license pool. Feel free to reach out if you want a 1:1 chat about this. P.S. From feed

Re: [cisco-voip] Webex Directory Connector Welcome Emails

You must enable sso. You can sync licenses based on ad groups now if that helps your license issue. Get Outlook for iOS Matthew Loraditch Sr. Network Engineer p: 443.541.1518 w: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com

Re: [cisco-voip] Webex Directory Connector Welcome Emails

Also, we have not yet enabled SSO, so unchecking the welcome email is not an option Jonathan On Mon, Nov 11, 2019 at 12:33 PM Jonathan Charles wrote: > Have a customer with 20K+ users, want to enable directory > synchronization, but am concerned it is going to send 20K emails to 15K > users w

[cisco-voip] Webex Directory Connector Welcome Emails

Have a customer with 20K+ users, want to enable directory synchronization, but am concerned it is going to send 20K emails to 15K users who will not be using Webex. How do I avoid this? Also, if all of them are licensed via template, how do we ensure users who never log in will not use a license