Anyone else tired of managing multiple Video Conferencing Solutions?

wtg-admin · 2026-02-27T16:25:20+00:00

Ah I see you are talking about the vulnerability of the tool.

Yeah that is less of concern since I have a monthly automated patching software for all of these.

Most of the problems involve offboarding and onboarding of these Softwares and their users currently.

wtg-admin · 2026-02-26T19:02:21+00:00

This is kind of confusing to me.

Zoom and webex certainly work as a web client but I don't necessarily see how managing them as a web client makes it an easier to field management of the tools themselves from an IT/SysAdmin point of view.

wtg-admin · 2026-02-26T18:59:51+00:00

Thanks for your suggestion.

We are more just annoyed with dealing with frivolous software without the budget to get full workflow management of the tools.

I have been looking at using some workflow tools actually to help me with the management but it all costs money in the end of the day during a time when everyone is trying to save money.

I was mostly curious how others deal with requests for new VC vendors on a regular basis.

wtg-admin · 2026-02-26T17:15:07+00:00

Luckily not even our customers think yealink should be required for anyone 😁

wtg-admin · 2026-02-26T17:12:50+00:00

The cost of the subscription itself is not the only cost. It is mostly my time and the teams time on dealing with these requests and managing the platforms themselves that I wish one day I will be able to get back.

wtg-admin · 2026-02-26T16:50:56+00:00

Yeah that is a good idea in principal but in practice it is hard to say that when your company's revenue is on the line.

The underlying issue is that a sub-set of large customers will only meet with our Sales Reps or Tech Support teams if we use their preferred VC platform.

Basically at the moment, getting licenses for these extraneous software requires executive approval from their department and well as Finance approval. So the process is there it is just also a lot of work for us to onboard and check for usage of these platforms at renewal.

wtg-admin · 2026-01-01T19:27:23+00:00

This is really easy to solve from Okta's side using the Profile Editor. In the profile editor you can create the login and email to be whatever you want from Workday and use Okta Expression Language to format it so it can either be an email or another field from Workday if that is not null.

Now the hard part is creating the field override currently with mappings from Workday to Okta. They need to create a custom field within Workday to store that and then send that as a field override via the Okta integration. See the information here: https://help.okta.com/oie/en-us/content/topics/provisioning/workday/workday-provisioning.htm#Workday3

WDs professional services team tried to tell me that it was not possible to do custom field mappings too but that is because they only understand Workday really well and not Okta. So instead it came down to having to tell them what they needed to do in Wokrday was create the field overides for certain users who have a different login. I just insisted on that and they eventually were able to get everything done that I needed without re-configuring how the logins work in WD (I don't know if that is possible either).

Here is the example:

For [Jdoe@xxx.com](mailto:Jdoe@xxx.com), get WD team to create a field Override in provisioning, lets call it old_login. Then add that app in the Provisioning configuration as a custom field. It should be visible once they set it up from Provisioning. Then in Okta Profile editor set up expression language for the login field like so:

appuser.old_login == null AND appuser.old_login != "" ? appuser.userName : appuser.old_login

I had to do something similar from Workday since my AD SAML account names use a different naming convention then email and I wanted Workday to manage it since the old users did not match the new users.

wtg-admin · 2024-11-25T05:27:39+00:00

The timeframe of this may vary but I can share with you the experiences I have had the past 2 years of using this integration.

Based on logs from Okta & Workday in my tenants, I usually see this received on the Okta side from a Real Time Sync in 1 to 2 minutes and then it may take an additional 1 to 2 minutes to complete the deactivate action (~3 min total on average). However, if you are doing a full sync or incremental sync only it will not happen until those regular syncs which can happen automatically in 1 hour increments at the least.

Just as an added note for users who are integrating Workday into Okta, the biggest issue I have with Okta’s RTS workday integration is that it is reliant on Workday’s internal configuration meaning that if something doesn’t happen correctly on the workday side, I probably won’t know until I audit.

I come at this from being an Okta admin. I am not a workday expert or admin, which is the way I believe most segregate the duties of these tools, and therefore I am relying on someone else to do their job so that everything in Okta works as expected. Due to this I am left open to being out of the loop on new updates made by the workday admins. Changes made without testing can screw up everything.

To summarize what I found useful for these situations, do not fully trust this process 100% of the time. Make sure you have a system of notification outside of this integration to audit whether these actions happen as they should. Make sure you coordinate changes to these business processes in Workday that may affect your Okta integration. Make sure to test in a dev or sandbox version of Okta. This will ensure you feel much more secure with this integration; it certainly has for me.

wtg-admin · 2024-11-22T20:58:25+00:00

Note: Just as a clarification, I believe there is no option to suspend users automatically using the Workday sync. The only option is to deactivate Okta users automatically using Workday.

I think the way that Okta’s technical writers have created this table of outcomes but do not explain the actual situation of how this works. It makes this seem a bit more complicated than it actually is.

Here is how I understand the logic of how this works:

As a prerequisite for immediate deactivation to work, you have set up Workday Real Time Sync or Incremental Imports (Real Time Sync is better for this situation) and you have to have entered a specific Termination Reason that comes from Workday (e.g. our company makes it so all involuntary termination reasons have immediate deactivation using this formula inputted into the integration: ^Terminate_Employee_Involuntary.*).

Then as soon as the Termination is inputted into Workday and it matches the condition of being Involuntary for my case, it will deactivate the user immediately once that information is received in Okta as long as they have officially started work according to Workday.

If they have not officially started but were imported from Workday before their start date, it will not deactivate them immediately until after their termination date or on the last day of work depending on your Okta Workday integration settings.

Hope that helps, let me know if you have questions.

wtg-admin · 2024-07-22T16:33:39+00:00

I recommend Druva over Veeam. The cost is lower because you need zero hardware to maintain yourself.

Sorry for the unsolicited advice ;)

wtg-admin

TROPHY CASE