46: IGEL Weekly: How to Use and Optimize IGEL Jobs (Scheduled Tasks)

Apr 19, 2022

Watch this IGEL Tech-Tips Tuesday video to learn how to use and optimize IGEL’s Job (scheduled tasks) feature. 

IGEL’s Sebastian Perusat teaches you to create and optimize IGEL scheduled tasks, known as Jobs. You will learn how to create jobs, the commands required for Jobs, schedule an update, and check the Job’s results. 

Presented by Sebastian Perusat, IGEL Community FELLOW.

In this video, Sebastien will teach you how to:

  • 00:00 Introduction
  • 02:50 Creating a Job
  • 03:25 Commands explained
  • 10:00 Schedule an Update
  • 14:55 Check Jobs results

Host: Patrick Toner
Co-host: Chris Feeney
Co-host: Sebastian Perusat


00:00:02.850 –> 00:00:19.590
Patrick Toner: Alright Hello everybody, welcome to the agile weekly podcast episode number 46 my name is Patrick toner i’m filling in for Andy whiteside today, and I am joined by the podcast regular co hosts Sebastian pair SWAT and Chris Fini, you guys wanna say hello.

00:00:20.880 –> 00:00:21.480
Sebastien Perusat: what’s your first.

00:00:22.950 –> 00:00:32.130
Chris Feeney: And greetings everybody looking forward to another episode with thought Patrick concepts, so we got a good good topic today looking forward to going through it.

00:00:34.800 –> 00:00:42.660
Sebastien Perusat: And how would just add pepe to have critics here for moderating and helping us to make this podcast hopefully as successful at the others.

00:00:43.530 –> 00:00:53.220
Sebastien Perusat: And just wanted to say that, just in case you missed it we launched the US 610 and 1107 firmware a few days ago, so if you didn’t up they don’t know.

00:00:53.640 –> 00:01:09.960
Sebastien Perusat: might be worse have tried to look at it, since we integrate a lot of new features, like the structure tech replacement for the customer attributes and so on, so just wanted to say, he said, the security topics, it would be definitely as a good thing to look at the update from our side.

00:01:11.310 –> 00:01:18.660
Patrick Toner: yeah you know great great update their seven you know great point right there sitting, especially with all the security vulnerabilities going on, you know always want to be keeping up to date.

00:01:20.370 –> 00:01:35.730
Patrick Toner: More than ever, but um so yeah so we’re gonna we’re gonna get into a nice topic today a topic that’s really useful for a lot of agile and admins that you may not be using and you know, as always, we want to provide as much value to you as we can.

00:01:36.810 –> 00:01:45.960
Patrick Toner: You know, so if you have any feedback, you have any topics, you know how do we get you know request for topics in Sam or is that something we can do to the agile community.

00:01:46.560 –> 00:01:52.740
Sebastien Perusat: Oh yes, definitely So if you didn’t try them to now, just in case so agile community.com would be the URL to join us on slack.

00:01:53.220 –> 00:01:58.320
Sebastien Perusat: And chatting with the word what your actual customers partners and distributors.

00:01:58.710 –> 00:02:05.310
Sebastien Perusat: And just trying to what Patrick asked for, yes, so basically what we’re doing is as soon as the topics coming up and the agile community and.

00:02:05.760 –> 00:02:09.330
Sebastien Perusat: We are seeing a kind of records questions coming in, quite often.

00:02:09.750 –> 00:02:17.970
Sebastien Perusat: We are trying to cover that in detective juicy video that’s obviously what we’re trying to cover them and the eccentric our podcast on the agile Community podcast so.

00:02:18.360 –> 00:02:25.020
Sebastien Perusat: For the moment, the committee’s asking for topic, and we are trying to cover it so just do you think the next one might be the device encryption keys.

00:02:25.530 –> 00:02:35.580
Sebastien Perusat: Where you’re able to make a pre boot on vacation on your item endpoint or new ud pocket so that’s might be the next one we’re caught me speakable that into it.

00:02:36.870 –> 00:02:42.030
Patrick Toner: Very good, very good, you know me, and this is the thing right, this is the the nice thing about the agile communities, you know.

00:02:42.450 –> 00:02:50.640
Patrick Toner: it’s it’s very it’s designed to be organic and you know, to talk to other people your peers in the industry and ask people like like Sebastian who.

00:02:50.910 –> 00:02:58.200
Patrick Toner: You know, is an expert in Nigel who can you know you can send a question in he does these nice videos and and I guess, we talked about them and.

00:02:59.070 –> 00:03:06.450
Patrick Toner: You know kind of talk through them, so you know with that the one we’re going to be focusing on today, this was an article written back in February.

00:03:07.440 –> 00:03:21.330
Patrick Toner: But believe written by that you said yep written written by seven and it’s going to be Scott, you know, covering a topic that like again I don’t think a lot of people are using and that is scheduled tasks in the in the agile us it’s called jobs.

00:03:22.830 –> 00:03:31.560
Patrick Toner: And you know so we’re going to talk kind of through that, and you know, one of the said, make a nice VID he made a nice video here just kind of walking through it.

00:03:32.100 –> 00:03:38.940
Patrick Toner: seeing him do in the US it’s all kinds of different options so let’s let’s just kick it off i’ll go ahead and share out this web page.

00:03:39.120 –> 00:03:43.680
Patrick Toner: For our kind of play the video with kind of talk through it, as it goes lovely.

00:03:45.060 –> 00:03:52.440
Sebastien Perusat: So there was one thing I just want to stay at the introduction, because it’s something which is a little bit misleading and the actual ecosystem.

00:03:53.100 –> 00:04:01.650
Sebastien Perusat: When we speak about scheduled jobs on the topic of today we’re speaking about specific tasks that you want to execute in the direction of men point.

00:04:02.880 –> 00:04:10.140
Sebastien Perusat: But we have also a second part, which is called administrative tasks which we already covered, if I remember right another podcast.

00:04:10.650 –> 00:04:20.100
Sebastien Perusat: So there are two absolute different parts of the US, the one the jobs were talking today is related to endpoints directly and can be executed without being an administrator.

00:04:21.450 –> 00:04:33.450
Sebastien Perusat: And then we have a second part, which is everything which is related to let’s say backups assigning profiles for review exporting specific Informations in a specific format sending out.

00:04:34.110 –> 00:04:45.090
Sebastien Perusat: scheduled tasks emails etc, etc, and that’s something which is related to US Administration administrative tasks so we’re not covering that one today, but really just the standard jobs.

00:04:45.900 –> 00:04:57.570
Sebastien Perusat: What you might already have seen on your side, or one with big about the wake on LAN feature or the update itself because that’s where the all the power of that features coming up.

00:04:59.250 –> 00:05:00.840
Patrick Toner: Greg can you guys see my screen okay here.

00:05:02.010 –> 00:05:05.340
Sebastien Perusat: What i’m yes in there perfect.

00:05:05.700 –> 00:05:09.360
Patrick Toner: Great so i’m going to go ahead and play this can mute button.

00:05:10.530 –> 00:05:19.530
Patrick Toner: But let’s you know let’s kind of talk through this right, so what are some of the things I mean you mentioned a few of them what are some of the things if an agile administrators listening to this.

00:05:21.150 –> 00:05:29.280
Patrick Toner: What are some of the things that they want to do what they’d want to leverage jobs for now what are some of the main most popular reasons you want to do that.

00:05:30.360 –> 00:05:37.980
Sebastien Perusat: I would say, when we come back to the beginning of the podcast we discussed already our test the main proposal to job tasks.

00:05:39.060 –> 00:05:53.550
Sebastien Perusat: updates so let’s imagine that you have a 1000 2000 10,000 seats your mess obviously you could send out an update immediately or you could also say send an update on shut down that something that you can do.

00:05:54.060 –> 00:05:58.500
Sebastien Perusat: As a context menu and saying right click and send that comment on no question.

00:05:59.250 –> 00:06:10.410
Sebastien Perusat: But then, if you want to repeat that, if you want to do that to devices which are maybe not online when you send out that comment in all the different automation that you would like to use on an update task.

00:06:11.280 –> 00:06:27.870
Sebastien Perusat: is not possible, by just sending out a common that where the jobs are taking place, so if you want to think about top that should happen on a record on our scheduled time frame, or, if you want to leverage the boot time specific.

00:06:29.160 –> 00:06:34.860
Sebastien Perusat: specific conditions for your endpoints because the customer, or the end users complaining don’t get me wrong.

00:06:35.310 –> 00:06:46.110
Sebastien Perusat: That the endpoint is taking too long to boot, my it’s less than a minute, in most cases, so I don’t feel it pretty slow, but some cases it might already be something which caused some some frustration.

00:06:46.980 –> 00:06:56.490
Sebastien Perusat: So that’s something also where you could say hey, why not waking up all my devices to specific time sets during the day so let’s measure you’re working for.

00:06:57.450 –> 00:07:18.000
Sebastien Perusat: For bank, where every employee has coming in at I don’t know seven 738 in the morning and the device should already be started contact the login mouse that’s something they can do easily by humans and their jobs, so coming back to your question, Patrick jobs are really powerful.

00:07:19.530 –> 00:07:31.620
Sebastien Perusat: painkiller for all the administrators, where you can send out without having the need to watch them every minute updates and command to the end customer to the end user.

00:07:32.940 –> 00:07:35.070
Patrick Toner: Alright, and shout out to the Quebec listeners there.

00:07:36.270 –> 00:07:41.700
Patrick Toner: You know, assuming they they’re listening in English, we wanted to Michael Berman on the next one, I think he’s bilingual but.

00:07:42.780 –> 00:07:54.360
Patrick Toner: You know so yeah so that’s a good point right, you might have you might have users in different regions, you know a lot of lot of ideal customers are global right they they might have help desk in a different country different time zone.

00:07:55.680 –> 00:07:56.400
Patrick Toner: You know so.

00:07:56.730 –> 00:08:05.190
Patrick Toner: yeah How would so you know you can obviously create different jobs and then, how would you assign them to have you would assign them it let’s say you had things separated by directory.

00:08:06.060 –> 00:08:11.610
Patrick Toner: So, are you saying that’s how you would recommend doing that you would apply the job with the different directory based on location.

00:08:12.600 –> 00:08:21.840
Sebastien Perusat: that’s a really, really good question I would always respond that it depends from your architectural from the wishes of your of your administrators.

00:08:22.950 –> 00:08:35.340
Sebastien Perusat: You could definitely just say, I have a comment, and I want to send it out or devices inside of director, that the easiest way because you don’t have to think about any kind of supplementary restrictions or filters.

00:08:35.970 –> 00:08:45.990
Sebastien Perusat: So that’s something short answer is yes that’s definitely one way and maybe already the most used way, but at the same time, if you think on an.

00:08:47.100 –> 00:09:01.860
Sebastien Perusat: update process, you might have some devices inside of that folder which might be I know it’s a little bit exaggerated, but from your cto or CMO, and you don’t want to put out the update because you know that he is having a extremely important.

00:09:02.880 –> 00:09:07.080
Sebastien Perusat: meeting that day and do it on to get an update push just before he’s leaving his office.

00:09:07.860 –> 00:09:13.770
Sebastien Perusat: that’s the reason why we have some additional filter through the comments were sending out so depending on what you want to do.

00:09:14.340 –> 00:09:22.560
Sebastien Perusat: Like update shutdown reboot update whatever you like you can and that’s something I will cover in the video just a little bit later on.

00:09:23.130 –> 00:09:38.190
Sebastien Perusat: it’s assigning the jobs to a view and that’s where all the magic can happen because of view is a dynamic filter that’s my definition for for you and the view is, if you didn’t have the chance to create one is us.

00:09:39.060 –> 00:09:46.440
Sebastien Perusat: Just views right click and create a new view, then you can say show me all devices which are not having the expected firmware.

00:09:46.890 –> 00:09:53.760
Sebastien Perusat: And beneath a specific folder and maybe having I know doesn’t make sense, but having two monitors attached.

00:09:54.540 –> 00:10:02.820
Sebastien Perusat: Or maybe having a specific flash drive installed, because we know that the APP that you want to push out is quite big and that’s what we are dealing with everyone on the database.

00:10:03.270 –> 00:10:12.450
Sebastien Perusat: You don’t want to push that on two gigabyte flash runs but only on forgive items that’s where the directory logic is reaching out as limits.

00:10:13.290 –> 00:10:23.550
Sebastien Perusat: On views you can say create as many filters, as you like and combine them and then say hey I just want to use the job conduct base because let’s imagine that.

00:10:24.030 –> 00:10:35.370
Sebastien Perusat: We stay on the firmware update, we have a we have devices on 1104 and want to go to level six want to go a direct path to the not latest but more his latest firmware.

00:10:36.840 –> 00:10:48.480
Sebastien Perusat: And if you want to do that, we could say, send out the comment every morning, just in case I mean doesn’t mean a lot of network load but send the US is sending out the comment, the endpoints.

00:10:49.080 –> 00:10:59.280
Sebastien Perusat: It might be worth a try to say creative human saying send it out only two devices which are not on additional six which made network even less important.

00:11:00.090 –> 00:11:09.030
Sebastien Perusat: And that’s where I must say the views in combination with the with the jobs are extremely powerful if using the right in the right way.

00:11:10.290 –> 00:11:13.140
Patrick Toner: yeah absolutely all comes down to automation right.

00:11:13.890 –> 00:11:28.890
Patrick Toner: You know automating away to the mundane day to day tasks which you know, are not as common when you’re using agile, as if you were, for example, managing SEM or some other windows management you’re going to be a little more involved, I just not quite as involved.

00:11:30.120 –> 00:11:38.400
Patrick Toner: You know not not even close really but you know what like one of the ones is we’re looking through the list here, you know you have a few options, you have update on boot different times you can push the update.

00:11:38.790 –> 00:11:47.760
Patrick Toner: Then you have some other ones like reboot schedule, you know I don’t know about you guys, you know we both been I guess all three of us have been around I gel for a little while.

00:11:48.930 –> 00:11:54.900
Patrick Toner: i’ve seen customers with who you know devices that haven’t rebooted in months, you know still working fine.

00:11:55.590 –> 00:12:02.070
Patrick Toner: And you know so it’s good to have that reboot scheduled you don’t need to reboot as often as you would windows being you know the nature of the operating system.

00:12:02.610 –> 00:12:07.230
Patrick Toner: But no, what about you guys, have you seen that in your experience so customers leveraging that.

00:12:07.950 –> 00:12:16.920
Patrick Toner: For reboots and what do you guys what’s your recommendation will you know if someone’s listen to this what’s your take on how often people should be doing, you know automated reboots in their environment.

00:12:18.480 –> 00:12:21.600
Sebastien Perusat: Chris will you have to jump in or, should I should I take over, as you wish.

00:12:24.150 –> 00:12:33.180
Sebastien Perusat: And the reboots job is for my personal opinion, something which is important but not over the job itself.

00:12:34.290 –> 00:12:41.730
Sebastien Perusat: I will tell you what i’m trying to explain to customers that I had to cover the last year’s when it came to 24 seven.

00:12:43.290 –> 00:12:44.850
Sebastien Perusat: production lines or whatever.

00:12:45.900 –> 00:12:55.260
Sebastien Perusat: sending out a reboot to specific time when it’s just normal standard Office what place is great, no question you do that at 11 o’clock in the evening or good.

00:12:56.010 –> 00:13:02.610
Sebastien Perusat: To tour in the morning, but if you think about I want to reboot the device when it becomes idle.

00:13:03.270 –> 00:13:11.190
Sebastien Perusat: that’s where I would say the job execution method is coming to an end and that’s where the conditional command.

00:13:12.000 –> 00:13:19.380
Sebastien Perusat: Based on the screensaver is reaching the next level of doing your automated reboot but coming back to your question.

00:13:19.950 –> 00:13:25.860
Sebastien Perusat: i’m definitely seeing the customers who are working in such kind of of environments.

00:13:26.220 –> 00:13:41.580
Sebastien Perusat: should at least have a post session command which reboot the device or shut down the device after the session is closed so i’m not using the job itself such often for reboots but more it’s a other workarounds like the conditional command and the position comment that.

00:13:41.610 –> 00:13:47.490
Patrick Toner: You know and that’s a great point sad, you know because, and this is one that you know, Chris you’ve obviously worked in healthcare.

00:13:48.180 –> 00:14:00.300
Patrick Toner: Formerly, with him, actually work together we mentioned on the last podcast you know you have certain industries healthcare said you mentioned you knew about have a facility that’s running 24 hours a shift workers.

00:14:01.410 –> 00:14:10.560
Patrick Toner: Were this may not be a fit right, you were you don’t want to do a scheduled reboot based on time I think it’s probably worth maybe for another episode.

00:14:10.890 –> 00:14:17.370
Patrick Toner: going through that other scenario where you’re talking about the conditional reboot you know leveraging something like the ideal screensaver.

00:14:18.240 –> 00:14:27.930
Patrick Toner: But let’s just in layman’s terms if you’re if you’re if you need that device on 24 seven it’s critical, this may not be the right method is that is that an accurate statement.

00:14:28.500 –> 00:14:33.840
Sebastien Perusat: Absolutely to one person again so sorry go ahead.

00:14:34.410 –> 00:14:36.840
Patrick Toner: Chris I don’t know if you had something there, so I come off mute.

00:14:38.670 –> 00:14:45.300
Chris Feeney: No, I just was just listening to the conversation here, I do think you know the industry in the situation does.

00:14:46.620 –> 00:14:47.820
Chris Feeney: require some thought.

00:14:49.050 –> 00:14:59.580
Chris Feeney: I was on a call with a partner, last week, they have a manufacturing facility and they literally have a setup so they can only absorb certain down times.

00:15:01.320 –> 00:15:09.780
Chris Feeney: During during the year, and that gives them very little wiggle room for when they can do updates or reboots or whatever, because they’ve got a production line running.

00:15:10.470 –> 00:15:20.250
Chris Feeney: I mean the nice thing is I just keeps running like the energizer bunny for them, but when they do need to do an update that definitely needs to be a very much scheduled situation.

00:15:21.810 –> 00:15:27.300
Chris Feeney: I don’t know if they’re doing it manually or scheduled job but but it’s one of these things where.

00:15:28.260 –> 00:15:41.730
Chris Feeney: They just can’t random the reboot whenever they want to, so they have to have to have to get it figured out and certainly if they can schedule it and plan it out it’s certainly doable to just automate the whole process.

00:15:42.990 –> 00:15:44.610
Chris Feeney: Hopefully, a sleep well at night.

00:15:46.200 –> 00:16:00.150
Patrick Toner: or yeah you know so so really guys if you’re listening that’s what we’re saying here it’s listen this this schedule job is a great feature, but if you’re on one of those categories, you know where you have health care 24 seven facility, this is probably not what you want to do.

00:16:01.170 –> 00:16:04.440
Patrick Toner: However, if that’s not you you’re in an office scenario.

00:16:05.550 –> 00:16:14.400
Patrick Toner: You know where people leave for the day those devices are just sitting there you can automate things like forcing the shutdown doing an update when they shut down.

00:16:15.060 –> 00:16:21.990
Patrick Toner: forcing them to reboot so that’s that word that’s where this would be a fit and I think guys for the next maybe the next one.

00:16:22.350 –> 00:16:29.850
Patrick Toner: You know, maybe we walk through the other scenario, but that’s a totally different can of worms because it’s very useful, you know, especially if you’re in that other camp.

00:16:30.900 –> 00:16:45.510
Patrick Toner: So so let’s talk through so we’re kind of watching it go through here, so now let’s say we’ve selected what we want to do, whether we want to update on boot whether we want to send a reboot a shutdown request let’s talk through some of the other ways that we can optimize this.

00:16:46.530 –> 00:16:48.300
Sebastien Perusat: So yeah totally confident.

00:16:48.660 –> 00:16:52.620
Patrick Toner: Now go ahead, I was gonna say, let me, let me rewind the video a little bit back to this menu.

00:16:54.180 –> 00:16:57.300
Patrick Toner: They have some other things you have execution time you have the start date.

00:16:59.010 –> 00:17:01.860
Patrick Toner: How many threads let’s talk through these these options, a little bit.

00:17:03.540 –> 00:17:15.330
Sebastien Perusat: So, first of all, if you think of a scheduled top because that’s something that came out on our enterprise German customer who just tell you just a short story.

00:17:16.020 –> 00:17:28.350
Sebastien Perusat: Who replicated the he is installation in from the prod to test environment, so what he did is basically he made a backup of his database and all the settings important that on and others are not so good.

00:17:29.100 –> 00:17:40.380
Sebastien Perusat: What he didn’t do his he didn’t separated the network, so the new you your mask could contact the endpoints obviously the other way around, was impossible because another IP address etc, etc.

00:17:41.550 –> 00:17:44.100
Sebastien Perusat: Even the certificate was another one.

00:17:45.600 –> 00:18:04.830
Sebastien Perusat: But what he did, is he tested some jobs and just one thing I want to mention sending out job is always sending out a comment from cms to the endpoint and if the MAC addresses stood there like an example, so the network communication is still available, then you might hit.

00:18:05.850 –> 00:18:13.980
Sebastien Perusat: quite interesting situation where the endpoint will get the comment, even if it’s not related to the to the test information.

00:18:14.460 –> 00:18:23.970
Sebastien Perusat: So, just in case be aware that a job is always sent out and it’s not sent out in a way, where the device will get it as soon as it reboots if it wasn’t.

00:18:24.660 –> 00:18:37.200
Sebastien Perusat: wasn’t moment it’s just a live statement so that’s the reason why coming back to the queue execution time and start date obviously you say it will happen one time on Sunday morning at four o’clock that’s right.

00:18:38.280 –> 00:18:47.490
Sebastien Perusat: But some devices may not be reachable to that moment and that’s the reason why you can say hey, why not repeating that in the regular amount of time and that’s something we’re covering a bit later.

00:18:48.240 –> 00:19:07.290
Sebastien Perusat: So coming to the thread itself if you send out a specific comment, like a shutdown to your home your mess endpoints you might send out that comment to 10,000 5000 devices that’s something which might also hit a specific imitation inside of for your mass communication.

00:19:08.430 –> 00:19:08.910
Sebastien Perusat: method.

00:19:09.930 –> 00:19:18.900
Sebastien Perusat: that’s the reason why we can say don’t do that for 10,000 devices, at one time, because you might get unresponsive or less responsive than before.

00:19:19.410 –> 00:19:27.660
Sebastien Perusat: So that’s reason why we are limiting the amount of threats related with a specific job that’s something which is already quite helpful.

00:19:28.110 –> 00:19:44.640
Sebastien Perusat: Because, if you do not know how to you that that that feature I wouldn’t care about a threat amount, but that’s what what we already teaching you obviously you can increase that amount, there is no big deal, but when that just be aware that you will need more.

00:19:45.780 –> 00:19:57.840
Sebastien Perusat: More requirements on your server regarding cpu and Ram memory so just be aware that if you want to move that threat to a higher amount that you might need more resources.

00:19:58.560 –> 00:20:06.030
Patrick Toner: So it’s it’s really coming down to concurrent devices doing the same things things like boot storming trying to avoid that we’ve rebooted.

00:20:06.390 –> 00:20:16.920
Patrick Toner: 10,000 devices in your environment and they’re all trying to hit the US, at the same time that could be a problem obviously So if you said it to 100 it’s only going to be 100 at a time yeah that I understand that stuff.

00:20:16.950 –> 00:20:18.750
Sebastien Perusat: yeah yeah very good exactly.

00:20:20.520 –> 00:20:25.230
Sebastien Perusat: So that’s the only recommendation read that I haven’t that specific moment.

00:20:26.370 –> 00:20:34.620
Sebastien Perusat: So even if you think of the different the different comment that we are sending out so we already spoke about update we spoke about reboot.

00:20:35.190 –> 00:20:41.970
Sebastien Perusat: But, before going to the next step just let me mention one last thing we have situations where we assign.

00:20:42.810 –> 00:20:52.800
Sebastien Perusat: configurations on your settings not now because we don’t want to interrupt the user, which might get a graphical user interface restart or session restart.

00:20:53.370 –> 00:21:03.240
Sebastien Perusat: We do the next reboot and they’re coming back to your example Patrick where the device or would step for one month, the US will never get this new setting so one of us to do a reboot.

00:21:03.930 –> 00:21:11.430
Sebastien Perusat: But there was also another one, so there was just another setting that you can send out, which is called setting us to device.

00:21:11.820 –> 00:21:22.230
Sebastien Perusat: So you’re pushing really the last known configuration from the database to the endpoint and that’s something that you could do on a Sunday morning at four o’clock in the morning, like an example.

00:21:22.650 –> 00:21:39.030
Sebastien Perusat: without having to reboot the device just one thing that came to my mind, but that’s something that you could do coming to the next part of the job window on a specific repeating method so saying that it will happen every Sunday.

00:21:40.650 –> 00:21:51.600
Sebastien Perusat: Well that’s something that we occurring in the tutorial just explain that the job is isn’t meant to happen on a one time, but can also be a repeated quite quite often.

00:21:52.740 –> 00:22:03.330
Sebastien Perusat: And my opinion is, if you have such kind of jobs watch them by using the luck function coming a little bit later on, but also set a maximum duration, because.

00:22:03.810 –> 00:22:13.950
Sebastien Perusat: That, if you have a job which takes 30 minutes, it cannot be It cannot be right, in my opinion, I mean there was a specific use case of what might be right, but it may have been there’s something wrong.

00:22:14.400 –> 00:22:29.460
Sebastien Perusat: that’s the reason why i’m always setting that always but in most cases, setting out a canceled canceled job execution of a Max duration time of 20 minutes if it’s not a really huge amount of devices that i’m looking at.

00:22:30.870 –> 00:22:36.210
Patrick Toner: Except you know with those lab results where where does the admin view them if you them in the US Council.

00:22:37.320 –> 00:22:38.850
Sebastien Perusat: You mean the job execution locks.

00:22:39.180 –> 00:22:47.670
Sebastien Perusat: Yes, yes, very good point so if you didn’t deactivate the lock results checkbox which is activated by default.

00:22:48.300 –> 00:22:58.740
Sebastien Perusat: Every execution of the job, and the response of the device is getting locked in the database of the humans, so you have as soon as you’re.

00:22:59.640 –> 00:23:05.880
Sebastien Perusat: saved your job that the job run for the first time let’s say until the morning you come back to the office on Monday morning.

00:23:06.420 –> 00:23:14.220
Sebastien Perusat: And then you have your mess your job and beside that you have the execution results and execution results are holding.

00:23:14.730 –> 00:23:32.280
Sebastien Perusat: A history of every job run and for every job run the results of the device you, you would see if the device wasn’t reachable like an example and then you can try to work around by creating a view or the to create a new schedule for that specific kind of devices.

00:23:33.570 –> 00:23:39.900
Patrick Toner: Great not the neck That in itself could be a whole nother topic for a different podcast right, you know all the rules, this logging features.

00:23:40.710 –> 00:23:55.680
Patrick Toner: You know there’s some powerful stuff you can do in there from hey seeing who made changes at what time what’s what’s you what’s user account new Ms did it it’s it’s really powerful stuff but okay you don’t want to derail there so so let’s say you have your you know you have your.

00:23:57.000 –> 00:24:08.460
Patrick Toner: have your your job created you want to do an update you want to do something like you mentioned us to settings probably the most used option in the US, as an admin right you’re always right clicking and doing that, when you’re troubleshooting.

00:24:09.990 –> 00:24:14.610
Patrick Toner: yeah you set your execution time, I think we got a little head on the video here, let me rewind a bits.

00:24:15.900 –> 00:24:18.960
Patrick Toner: Then, once you hit next on that first screen, you have a few other options here.

00:24:20.700 –> 00:24:22.320
Patrick Toner: And it’s going to be around scheduling.

00:24:23.340 –> 00:24:28.770
Patrick Toner: So you can select your you know time you want to do it, you mentioned said, you know doing it.

00:24:29.610 –> 00:24:41.340
Patrick Toner: You know how often you want to do it, do you want to do it once do you want to do it, you know, every week on the same day, but kind of walk us through that a little bit and just some some important high level things people might want to consider here.

00:24:42.090 –> 00:24:54.750
Sebastien Perusat: Right, so we already covered the the engine job execution itself so just in case, I just wanted to reimagine it if your job is taking too long, you want to cancel it and that’s something that you can do on that button part of the page.

00:24:55.800 –> 00:25:08.640
Sebastien Perusat: What we are doing on the job execution repeating so happening on a regular recommend task ID that let’s imagine that you want to wake up all your devices on your network.

00:25:09.270 –> 00:25:16.170
Sebastien Perusat: And that does it do not want to do it just one time, because you want met one every morning so every one day during weekdays.

00:25:16.920 –> 00:25:29.010
Sebastien Perusat: does something with a repeat of features pretty helpful because that imagine that the wake up job didn’t went to the unit your network, so the magic packet didn’t reach the network interface from your endpoints.

00:25:29.670 –> 00:25:38.700
Sebastien Perusat: Which is that is from the European point of view happening every 90% of all cases, because the network department wasn’t really.

00:25:39.450 –> 00:25:48.030
Sebastien Perusat: kind to open that box of warm So what we are using there’s the wagon and proxy another topic another tutorial but just saying.

00:25:48.510 –> 00:26:01.560
Sebastien Perusat: That, if you want to send up a wake up job to the endpoints just maybe we’ll do not that non do that just maybe one time do that every day and that’s where the repeating function of the job is taken all the places.

00:26:03.810 –> 00:26:16.380
Patrick Toner: Right, and you know, then so once you have that setup so here we’re seeing you know it’s being applied to now you mentioned applying it to a view there’s other options, you can apply to a directory, you can apply directly to a device probably is that’s probably a good first step for testing.

00:26:17.490 –> 00:26:19.560
Patrick Toner: You know just applying directly to a device.

00:26:21.090 –> 00:26:26.040
Patrick Toner: You know other any other options those Those are the three main options there once you have the job graded.

00:26:26.520 –> 00:26:37.260
Sebastien Perusat: yeah that’s right, besides the views and the directories, there is no other let’s say graphical user interface way to to send out a regular coming to the end point.

00:26:38.550 –> 00:26:51.030
Sebastien Perusat: What we’re not covering and there is the endpoint side, since sending out a job from cms is like I said just sending out the command prompt us to the end point but you could also do something like.

00:26:51.450 –> 00:27:08.640
Sebastien Perusat: send me something from the end punch to the your mess, so that would be a local scheduled task by using chrome system define us nother topic mothers tutorial again just saying well really focusing on the on the on so that’s right we have us and we have the director is devices.

00:27:10.950 –> 00:27:16.950
Patrick Toner: Very good, and then, once it’s once it’s a you know absolutely set up here, we were seeing it’s getting a firmware update.

00:27:17.850 –> 00:27:21.870
Patrick Toner: You know and we’ve actually like you always want to test with these right, I mean that’s obviously best practice.

00:27:22.350 –> 00:27:36.000
Patrick Toner: But once you create that job skipping over schedule it for one device make sure it works correctly and then from there, you can then take that to the next level applied to the you know the larger directory or the view it’s giving you a specific amount of devices.

00:27:37.980 –> 00:27:39.510
Patrick Toner: Now here I think we’re seeing.

00:27:40.560 –> 00:27:48.630
Patrick Toner: You know, in the US, you can check if you click on the job itself, you can see, which is a really great feature hey which devices have gotten it, what are the results.

00:27:50.250 –> 00:28:04.590
Patrick Toner: You know just just a really nice feature, I can tell you, you know back when I used to manage SEC, so this was a lot more mean yes, it has a nice interface there to where you can kind of look through and say Okay, which devices didn’t get this which ones failed.

00:28:06.000 –> 00:28:09.330
Patrick Toner: you’re probably not going to get quite as many failures generally with agile with this.

00:28:10.530 –> 00:28:12.870
Patrick Toner: But it’s just nice to be able to view it and have that peace of mind.

00:28:14.310 –> 00:28:24.000
Sebastien Perusat: Absolutely, just in case I want to mention for for our listeners, since I said, all the locks are based and stored in the your message in the database.

00:28:25.260 –> 00:28:33.930
Sebastien Perusat: And if you have a job which is reaching out to 10,000 devices every morning, you might a little bit mess up your database that’s what i’m calling the next step and just explaining.

00:28:34.500 –> 00:28:40.980
Sebastien Perusat: hey might be a good idea to have an administrative task which delete all the toxic lock execution results.

00:28:41.490 –> 00:28:49.890
Sebastien Perusat: older than the know, three weeks like an example because yeah you don’t want to look, three weeks ago, if you do device gotta wake up second.

00:28:50.310 –> 00:29:01.710
Sebastien Perusat: So, just in case I would just wanted to mention it, they got the job execution in the database and if you are scared to mess it up just do the administrative tasks to delete them after specific amount of time.

00:29:03.930 –> 00:29:04.440
Patrick Toner: Very good.

00:29:06.330 –> 00:29:09.630
Patrick Toner: Then what’s your what’s your take on, you know let’s say you have a schedule job.

00:29:09.840 –> 00:29:11.100
Patrick Toner: Just kind of throw one out there.

00:29:12.270 –> 00:29:22.200
Patrick Toner: You know you generally, would you recommend creating new as you go or editing as you go like let’s say it’s an update schedule right and you need to change it.

00:29:22.980 –> 00:29:35.070
Patrick Toner: Is that all you know is is the admin fine just right clicking editing that job and changing the feature changing the attributes there for a different time or would you recommend creating a new job and get rid of the old one.

00:29:36.420 –> 00:29:54.750
Sebastien Perusat: If a think about the historical approach of the your mess I would definitely say that deleting and creating a new one might be my best bet just for one reason, most of our listeners and our human Samina stretches out like I do lazy people you create a job to leave it running.

00:29:55.770 –> 00:30:05.010
Sebastien Perusat: And it works that’s the way that’s the reason why i’m happy to work visor that’s why it is working, you click on it, you create the job and it’s executed.

00:30:06.000 –> 00:30:11.340
Sebastien Perusat: But at the same time, you will maybe have forgotten to create the object is the.

00:30:11.580 –> 00:30:22.230
Sebastien Perusat: cleanup talent for the database, you will have some devices or maybe some jobs which are just there for testing and there was stayed there for ever, maybe just the activated but still there.

00:30:22.980 –> 00:30:30.510
Sebastien Perusat: create a new one is the old one, and it will just give you a little bit better feeling about what you are doing, because sometimes even if the job.

00:30:31.740 –> 00:30:43.890
Sebastien Perusat: tool itself is not such complicated, you might have some views which are not updated anymore, because they were old all data or you might use.

00:30:44.400 –> 00:30:59.670
Sebastien Perusat: or directories and if you just edit and change it every time you might miss something new, something new territories that something which will not happen if you create the job itself from from from the beginning on their your focus on religious endings and use.

00:31:01.770 –> 00:31:09.810
Patrick Toner: Think, if I understood that correctly, I think the US management might be making us a little lazier based on you know you’re making me think introspective right now.

00:31:10.980 –> 00:31:18.450
Patrick Toner: being one of the lazy people you mentioned but yeah that’s a great point right it’s it’s all about you know maintenance, you know, making sure.

00:31:19.770 –> 00:31:23.970
Patrick Toner: You know the interviews are great, but if you don’t touch it for two years, it might not be giving you.

00:31:24.720 –> 00:31:31.260
Patrick Toner: The accurate information and sometimes you know kind of the blessing, and the curse of us it because it’s so easy to work so well.

00:31:31.830 –> 00:31:37.650
Patrick Toner: it’s a lot of times it’s set it and forget it, and then next thing you know you’re like wow I haven’t I don’t even know what’s in that view but i’ve been relying on it.

00:31:38.850 –> 00:31:48.810
Patrick Toner: um so very good so that so that, in a nutshell, is jobs right, you know just to recap it’s it’s it’s really designed for devices that you know.

00:31:49.110 –> 00:31:54.990
Patrick Toner: Have downtime number one that’s got to be definitely a prerequisite devices that are you know they’re going to be.

00:31:55.800 –> 00:32:05.280
Patrick Toner: there’s going to be a period of time where there’s no one at that device offices closed or whatever, and then from there, you can push these scheduled automated tasks that just make your life easier.

00:32:06.990 –> 00:32:11.700
Patrick Toner: All right, any any closing thoughts on that any anything we missed Chris said.

00:32:14.640 –> 00:32:15.420
Sebastien Perusat: With you first.

00:32:16.410 –> 00:32:28.260
Chris Feeney: No i’m sorry i’ve been very quiet here i’ve had traveling and made without knocking and so i’m just trying to be polite and not bring in some ambient noise but.

00:32:29.460 –> 00:32:30.810
Chris Feeney: No, I mean honestly.

00:32:31.920 –> 00:32:33.930
Chris Feeney: This is sort of the advanced stuff that.

00:32:35.250 –> 00:32:40.620
Chris Feeney: You know you really kind of want to roll your your hands up and kind of get get into it and I haven’t had a chance to.

00:32:41.280 –> 00:32:53.400
Chris Feeney: Just in my role to be able to do that my son just listening i’m really have any thing to add at this point, other than Thank you said, for taking the time to put the video tutorial together and I appreciate that.

00:32:55.320 –> 00:32:56.010
Sebastien Perusat: My pleasure.

00:32:57.000 –> 00:33:09.660
Patrick Toner: Absolutely well guys, you know it’s been a pleasure, you know for everybody listening, you know again anything you want to hear on this podcast any any topics or anything like that, please reach out I joke community is a great place to do it.

00:33:10.860 –> 00:33:14.700
Patrick Toner: All three of us are on the agile Community Sebastian is extremely active on the agile community.

00:33:15.210 –> 00:33:21.150
Patrick Toner: And we want to hear from you guys you want to hear what are the topics or you’re thinking like hey you know I, how do I do this, how.

00:33:21.420 –> 00:33:29.430
Patrick Toner: How, you know there’s there’s a workflow that I know other customers are doing let’s walk through it, so we can all see it we’ve talked about a few of them today, doing the automated.

00:33:30.480 –> 00:33:38.970
Patrick Toner: reboots for devices in those high use areas healthcare 24 seven facilities so that’s one that will kind of table and talk about and.

00:33:39.420 –> 00:33:48.420
Patrick Toner: Hopefully, presented the next one or down the road, but we definitely want to hear your thoughts and get your feedback, so we can you know give you topics that are useful to you.

00:33:49.770 –> 00:34:01.470
Patrick Toner: And with that said guys it’s been a pleasure, you know I think we can kind of close here and thank you, everybody for listening have a great week and we will talk to you on the next one.

00:34:02.160 –> 00:34:05.490
Sebastien Perusat: And thank you, Patrick for in the session was federal.

00:34:06.150 –> 00:34:07.230
Patrick Toner: You got it you gotta.

00:34:07.320 –> 00:34:07.710
Chris Feeney: Take care.

00:34:09.240 –> 00:34:09.750
bye bye.