[cisco-voip] Webex Directory Connector Welcome Emails

Jonathan Charles jonvoip at gmail.com
Fri Nov 15 12:00:08 EST 2019


The alternative was sending thousands of emails to users who would never,
ever, use Webex... (lots of drivers and warehouse people...)


Jonathan

On Fri, Nov 15, 2019 at 10:42 AM Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

> If you’re going to add to the group manually, then you’re good to go!
>
>
>
>
>
> ---
>
> *Lelio Fulgenzi, B.A.* | Senior Analyst
>
> Computing and Communications Services | University of Guelph
>
> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON |
> N1G 2W1
>
> 519-824-4120 Ext. 56354 | lelio at uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
>
>
> *From:* Jonathan Charles <jonvoip at gmail.com>
> *Sent:* Friday, November 15, 2019 10:56 AM
> *To:* Lelio Fulgenzi <lelio at uoguelph.ca>
> *Cc:* Matthew Loraditch <MLoraditch at heliontechnologies.com>;
> cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Webex Directory Connector Welcome Emails
>
>
>
> We are going to go ahead and create a Webex group and throw the users in
> there... that way we can control who gets added.
>
>
>
> Thanks!
>
>
>
>
>
>
>
> Jonathan
>
>
>
> On Tue, Nov 12, 2019 at 4:41 PM Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
> When you build your filter, you might want to add a couple of things. This
> is based on feedback and experience…
>
>
>
> The first, is an AND with (mail=*), this way, if they don’t have an email
> address, they don’t get created.
>
> Also, AND with (!(memberOf=cn=<bypassgroupname>)), this way, for whatever
> reason, you can add someone to the bypass list and avoid errors.
>
>
>
> My groups are created by machines. I can’t modify them. So, if someone out
> there has an issue, I add them to the bypass list and resolve later and cut
> down on email alerts.
>
>
>
> Example, for some reason, people have used our corporate email address to
> get a webex account from another organization who has also enabled AD
> integration. Go figure.
>
>
>
> ¯\_(ツ)_/¯
>
>
>
> ---
>
> *Lelio Fulgenzi, B.A.* | Senior Analyst
>
> Computing and Communications Services | University of Guelph
>
> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON |
> N1G 2W1
>
> 519-824-4120 Ext. 56354 | lelio at uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
>
>
> *From:* Jonathan Charles <jonvoip at gmail.com>
> *Sent:* Tuesday, November 12, 2019 4:59 PM
> *To:* Lelio Fulgenzi <lelio at uoguelph.ca>
> *Cc:* Matthew Loraditch <MLoraditch at heliontechnologies.com>;
> cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Webex Directory Connector Welcome Emails
>
>
>
> Thanks, I think we are going to assign the users to an AD group...
>
>
>
>
>
> Jonathan
>
>
>
> On Mon, Nov 11, 2019 at 12:57 PM Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
> 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 feedback as well as observation, you’re looking at about 1hr
> per 10,000 records.*
>
>
>
> ---
>
> *Lelio Fulgenzi, B.A.* | Senior Analyst
>
> Computing and Communications Services | University of Guelph
>
> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON |
> N1G 2W1
>
> 519-824-4120 Ext. 56354 | lelio at uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
>
>
> *From:* cisco-voip <cisco-voip-bounces at puck.nether.net> *On Behalf Of *Matthew
> Loraditch
> *Sent:* Monday, November 11, 2019 1:37 PM
> *To:* Jonathan Charles <jonvoip at gmail.com>; cisco-voip at puck.nether.net
> *Subject:* 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 <https://aka.ms/o0ukef>
>
>
>
> *Matthew Loraditch**​*
>
> *Sr. Network Engineer*
>
> p: *443.541.1518* <443.541.1518>
>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>
>  |
>
> e: *MLoraditch at heliontechnologies.com* <MLoraditch at heliontechnologies.com>
>
> [image: Helion Technologies] <http://www.heliontechnologies.com/>
>
> [image: Facebook] <https://facebook.com/heliontech>
>
> [image: Twitter] <https://twitter.com/heliontech>
>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
> ------------------------------
>
> *From:* cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of
> Jonathan Charles <jonvoip at gmail.com>
> *Sent:* Monday, November 11, 2019 1:34:18 PM
> *To:* cisco-voip at puck.nether.net <cisco-voip at puck.nether.net>
> *Subject:* 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 <jonvoip at gmail.com>
> 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 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?
>
>
>
>
>
> Jonathan
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191115/0bb9afbd/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1297 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191115/0bb9afbd/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 6884 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191115/0bb9afbd/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 431 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191115/0bb9afbd/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 561 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191115/0bb9afbd/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 444 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191115/0bb9afbd/attachment-0004.png>


More information about the cisco-voip mailing list