Transcript
to Halloween in a couple of days. So today we've got Ajinkya, Amit and Jason and we're going to be talking about RMM. And before we do that I'm just going to do a little bit of introduction and housekeeping for you all. So if you haven't been to one of these before, product office hours is the idea to have an office hours like you might have with a professor back in university where basically you can drop in and in a more informal setting find out you know what's going on, give your feedback, ask us questions and what we hope you get out of it is kind of ideas of what's coming up or tips for how to use ConnexWise products to the best way they can and to help you and your business. And for us it's great because it kind of shortcuts the process of getting your feedback and questions and we learn a lot about what's important to you, what's unclear, you know what you're interested in and we can use that to improve what we're doing. So we do this usually every Wednesday, we will look at the upcoming schedule in a just a couple of slides and there's typically one or two demos of one of our products. So just a quick bit of housekeeping then, we are recording this already, everyone here who's signed up you will be automatically sent an email with a link to the recording in 24 to 48 hours. We also upload all of these to the ConnexWise YouTube channel where we have a whole playlist for these product office hours and we have our other webinars, we have explainers, we have content about IT Nation Connect and our other in-person events. Of course, IT Nation Connect is coming up very soon in Tampa, Florida, in Orlando, Florida, sorry. We'll take a look at the calendar here on the slides, but you can also find the calendar anytime in the ConnexWise University and other webinars are also on there. Technical and Q&A, so any technical issues, don't worry, I've got some troubleshooting tips which we will look at in a second. And for asking your questions, you'll see here in GoToWebinar, we have a chat and we have a Q&A feature. Please use the Q&A feature, that's what we will be monitoring, it's the one that's best laid out for us to keep your questions organized and answer them most effectively. So remember that Q&A, the one with the question mark on it. Yeah, if you're having any trouble with this, we find using the GoToWebinar app works best or if you're doing it in browser, Chrome and Edge are the best ones to use. Any more problems, it's, you know, the classic web troubleshooting steps, reload, clear cache, restart. And for our presenters, we've already checked and we all seem to be connected, so that's great. So as I mentioned, we do have a ConnexWise YouTube channel where we put up these recordings. So there you go, QR code is on the screen right now. If you want to get a direct link to that, you could of course go on to ConnexWise.com and we have links to all of our social media there or go straight to YouTube and just look up ConnexWise. And then as for what is coming up, we don't have a session the first week of November. People are going to be very busy and I hope you all are busy as well with IT Nation Connect. But beyond that, we have CPQ, new capabilities and quoting and a registration link for that is already live. We'll have another QR code for that shortly. It's in the ConnexWise University calendar I mentioned. And then coming up, we've got two sessions about PSA. The following two weeks, we'll be looking at the end user portal and some great new options in there for building your service catalog, which means that your users can better kind of describe and, you know, choose options about what they need help with to expedite your ticket process. And then we'll be looking at a very exciting topic, one of the great benefits of our evolution into ASIO, the RMM and PSA unified ticketing experience. And we'll have registration links for those shortly. So I am going to hand over to Jinkya. So if you want to take over the screen share from now and present your demo. Thanks, Evan. I'm going to now share my screen. Okay, Evan, can you please let me know once the screen is up? Yeah, I can see it. Okay. Hi, everyone. So today, I'd like to talk about a couple of demos, starting off with the updates to the devices page that we've done. So we are essentially working on a new devices page. And as part of the updates of the modernized UI that we are building for the new devices page, I want to focus this demo towards the automation pieces, which is the run button, which allows you to run automations. Along with that, the recent panel tab, which allows you to view results for the automations that you've run and also the automation tab under device details that we have today. So that's going to be one part of the demo, which is going to ensure that you have a consistent and modern UI experience. And because you have the same UI components along all the pages in ASIO, the design is also going to be optimal. And we've ensured that a user can intuitively navigate the pages as well as optimally have optimal clicks overall on the pages. Apart from that, the second demo is going to be having a create suspension functionality inside of script editor. Partners have been asking about this feature where they want to reduce the noise that gets created if a monitor or an alert is already present and a script basically triggers that monitor or alert. So that's another function that we will be shortly releasing. And I'd like to share a demo on that as well. So having said that, I'm actually going to move to the first demo here. And that's related to the modernized UI for the run recent panel and the automation tab on device details. So as you can see, this is actually the new devices page. I am going to focus my attention on the actions button, which essentially contains the run menu and management menu. So I'm just going to go there. Once I navigate to actions, this gives me two options. The first one is run and the second one is managed. As you're familiar, both of these options are available today on the existing devices page. But now they've been combined into a single actions menu. And that's keeping in mind that all actions need to sit together. So what you're essentially seeing is I have now navigated to actions under the run menu and you're going to see the same list of actions that are available. You also saw that the filtering is super fast. When I start typing immediately, the filters get applied or the search is applied. What you will also shortly see is we have a filter component available right now. There's only. Yeah. As you can see, you can use any of these columns in order to filter what you are looking for in the run component. Now, what I'm going to do next is I've clicked on the PowerShell script here. I'm going to write a PowerShell script. Before that, I'd like to talk about the new resource selector or the updated resource selector that we have here. As you can see, you get the four options for company site device groups and device groups and devices. But along with that, you also see an additional column which says device status. So you will be able to look at device status as well when you are essentially planning to schedule a particular task or a script. So once you do that, it's basically the menu which allows you to select devices for scheduling. I'm going to select a couple of devices based on which were online so I can see when 11, 1 and 11, 2 are online. So I did that. And then I'm going to just have a mock PowerShell, which says a core test. As you can also see, I have the buttons below. I'm sorry, though, slightly. Oh, very well. Yeah. You have all the buttons there. And what I did was went to next. One of the things that I would like to call out here is our initial run menu that was available. And what was available under the tasks menu when you navigate to automation and tasks, there were slight differences that were present between the options that were available. These differences will go away as well. You will see a consistent experience where all of these options are now available under the run menu as well. To give you an example, under run menu, when I selected recurring and I go to the monthly option today, you were not able to select every third Monday of that particular month. From this menu, you could do it inside of the tasks menu from the automation page. So just to mention that we now have that consistency as well present under the run menu. So now what I'm going to do is actually run this for next agent checking, which is our recommended schedule. And then it also gives you a review and finalized screen where you get a summary of everything that you're executing, the body and the expected time in seconds. So and then what you're seeing is a success message, which says the task has been successfully submitted. There will also be an upgrade to this where you will get a button, which will allow you to directly open the task results for the task that you've submitted. So that's still a work in progress, as I said. But what it essentially means is if you click on that, it's immediately going to open the task results. If you would like to view the task results and not really close this menu, open up recent tasks and then find the task and then open it up. And I'm actually going to do exactly that right now. But with a single click of a button, you will be able to do that in case you would like to view that. If you do not wish to view that, you can essentially close and continue with your work. OK, so I'm going to close that. Once we close that, I do want to show the location of the recent panels, as you can see right next to actions. We have the. We have a click button present there, which lets you see the recent panel, which will be called as View Tasks. So once I click on View Tasks, as you can see, the PowerShell script that I had executed has come up over there with two devices. When I click on the PowerShell script, it's going to show me both the outputs. So this is essentially the page that's going to open up when when you click the button on View Task Results after scheduling the script. So you don't have to keep navigating out of there and coming back to recent tasks. Now, one of the things that I do want to call out here is you can actually sort this by device or by the status. As you can see, one of them completed successfully and the other one was actually running when I recorded this demo. So it's a good example where you can actually sort on status. You can do a lot more. You can also have an export functionality or you can basically have the same features that you already had on the recent panel. And then I'm going to shortly show a demo of export. So you could export it to a CSV or an Excel file. Once you export it. Just kind of quickly open it. And it should give you a tabular representation of all the information that is available on this particular page. So the demo, the Excel will shortly come up. Yeah, there you go. So it showed the status as one for running and one for success because one was still running. By the time I had exported this information. Now, one other. So one other thing that I do want to call out is another way of scheduling or running tasks, and that is pre-selecting devices that you want to run a particular task for. This was also again available initially, and we made sure that we have the same use case present where I'm going to now select that particular machine. Because I want to I know the machine that I want to run the automation on. So I select both the machines. It shows me two items selected. I go to run tasks and I go to actions. And as you can say, it's already showing me your selection includes two devices. So once I do that, if this time I want to execute the script on it, I'm just going to select the script that I want. Once I select the script and I say next, it's going to show those two devices as pre-selected in the resource selector. So you can see that these two devices are pre-selected and then I can actually go ahead and add more devices if required. So I'm not going through the entire demo again because I think we reviewed the next steps of what they meant. But as you can see, you can still select one more and then you see that three devices got selected. So that was run menu and reset panel. I want to talk about the automation tab as well. So I'm going to now navigate to the device on which I had run the automation win 11-1. And once I go there, you can see the modernized UI for the automation tab as well. So once we come here, as you can see, you basically have the ability to see two things in two broad categories. One is going to be the history, which means all executions that have been executed, that have been completed, success or fail. And the other, which is going to be scheduled, which says, OK, these are the tasks that are upcoming for that particular end point. Under actions, you'll have the same capability where you will be able to enable, disable, postpone or cancel based on the eligibility of that particular task. And then once you go to history, as you can see, you will get all the information about the tasks that have been executed with their corresponding status. Now, this is just a sample showing the task output that I had run for this particular task. And you can see that the output report is present here as well. Now, post that, I do want to show that you have quick filters available here as well, where you can filter it quickly. And I actually have a filter that is already applied here. So as you can see, I've applied a filter which says status as success and type as task. And based on that filter, it quickly filtered down the list for me. And I can actually use the filter very quickly to see the intended results that I need. OK, with that, those are the three items that I wanted to demo on the run recent panel and the automation tab. I'm now going to move to the next demo, which is the create suspension. OK, before I actually demo the create suspension, I do want everyone to understand what we are doing as part of this demo. What we are going to do is I'll demo a monitor that I've created that generates a ticket when Adobe Acrobat Reader is uninstalled from a device. So this is my trigger criteria to create a ticket. The monitor will be triggered and a ticket. I'm sorry. So we'll trigger the monitor by running a script that uninstalls Adobe Acrobat Reader. Then we will verify that the ticket got generated. Then we'll add the suspension logic inside of the script editor to see before the uninstallation step. What that means is the suspension will become active at the time of uninstallation. Then we will rerun the script on a different endpoint because on an endpoint that will have Adobe and we can uninstall it from. And then we'll verify that the suspension entry is seen on the suspensions page. And at the same time, we'll confirm that no ticket was created during this time because we had put a valid suspension. OK, so as you can see, I have the I'm sorry, I have the monitors page open here. I've created a monitor for these three endpoints, which is the QA, KR, Windows Server 2022 and Min 11 QA. Now, with that, I'll just show that the monitor has been created. So as you can see, the monitor is says that if Adobe Acrobat Reader DC is not installed, I would like to create a ticket. And if it gets installed, essentially resolve the ticket. So this is just to show that the monitor gets triggered when the script. OK, so I'm going to go to the script editor. What I've already done is written a create suspension function. It doesn't run when we have our initial run. And I have the application uninstalled here where I've entered the details for Adobe Acrobat Reader and the right version that is present on that particular endpoint. So we'll go ahead and. As you can see, we're going to now schedule it on one of the endpoints, which is QA, KR. We say yes, we save selection and then we run. OK, so as you can see, we've now run it. I'm going to now navigate to the tickets tickets menu where I will show you that the ticket was generated because the application was uninstalled. So as you can see on this screen here for that particular endpoint, I'm looking for the application. The application is no longer found, which means the application has been successfully uninstalled. And now I'm actually going to go to the tickets page to verify that a ticket was generated. All right. So there you see a ticket has indeed been generated based on the fact that a monitor was present for that particular scenario. And if you can see the ticket ID is one one three. So the ticket has been successfully generated. I'm not getting into the details here because this is an existing workflow. We've already triggered that and ensure that a ticket has been generated. Now, the next part that I would like to demo is we are going to go and update our script. And as we update it, we are going to get the create suspension function into place or we are going to enable that function. So the suspension comes back. OK, there you go. So I'm going to enable this function now. I'm going to say enable for create suspension. So create suspension will now be back into picture. After that, what I'm going to do is I'm actually going to schedule this. So I don't want to talk about the create suspension function here. So when you look at the create suspension function, you'll get to name that particular suspension. You will get to have a description for it. This here is the key for suspension where you say apply the suspension for 15 minutes duration. What this will mean is when the when that particular script is executed on that end point, starting from that point, the suspension will get applied for the next 15 minutes. So that is key here where you will get to control for how much duration you would want the suspension to be active from the point when the script actually starts executing. Now, here you will also get to select the type of suspension you want to apply. So you're you're actually going to see monitors and alerts with both present. So your Adobe Acrobat reader is uninstalled is the monitor that we had created. But if you go here, you will under alert type, you will actually get to see both the options. Just going back to see if I had. So under under the selection, you'll actually get an alert option as well, where you will be able to select alerts so you can select monitors or alerts or both. And the view will change based on the selection that. So now we are going to go ahead and we are going to actually show you this. So here I am, and I've actually chosen to divide the other two devices where Adobe Acrobat reader is still installed and I've run it on those particular two devices. Now, I'm going to show that uninstall was success on one of those devices. OK, so as you can see, at 1950, we will be able to verify under applications for one of the devices that Adobe Acrobat reader is no longer present, which means it got uninstalled. So the next step is validated that it got uninstalled. Now, we want to validate that suspensions were actually created against this. So we are going to now look at that. So as you can see, there are two suspensions that have been created. The other three were actually the ones that we've created before, which have already been expired as part of testing. But the two ones have been created for the individual endpoints that were created or that were selected as part of the schedule that we did. You can see that there have been two suspensions that are created. When you click on that suspension, you will be able to see more details with respect to the end point and the time at which it got applied. Right now, you're only seeing the ESD, seeing it as ESD time zone, but we'll get it corrected to the device's time zone. So essentially what you can see is the suspension has been successfully created. Once the time on it expires based on the time selection that you made under create function, it's basically going to expire. That suspension is going to expire. And the last part is to show that there is no ticket that got created as part of the suspension. So I'm actually going to go back to the tickets page and we are back here. And as you remember, the initial ticket that was created was one one three. That ticket is still here and there's no ticket that has been created against the new one installation for our robot reader that we did. All right. So that's as part of the demo that we had. I'll quickly run through the next slide. I did give you a glimpse of the new devices page for automation, run menu and recent panel. But in this, essentially the entire page is actually available for early access. So if you're if you're interested in reviewing how that looks like and if you'd like to use it, please use the following QR code to sign up for the new ASIO devices page and we'll make sure that we can enable it for you. I think it's helpful mutually because we'd like to hear a lot of feedback from you as well in terms of how you go about the user. After that. Oh, I'm so sorry. Here is the QR code for the next session. That's going to happen on November 12th at 10am EST. So please make sure you can make a note of that as well. All right. With that, I'm actually going to take a pause and get the session open for Q&A. Hi, Ajinkya. There are a few questions on the chat here. Let me just quickly check a few of those and ask you those. If you could clarify and answer those. Can you use suspension for windows, patching windows and monitors? This would apply to Windows Server in particular. Oh, I'm sorry. Can you come again? Can you use suspensions for Windows servers? Is that what's the question? Can you use suspension for windows, patching windows and monitors? This would apply to Windows Server in particular. I think I'll try and answer. I'll try and answer. So whenever the today, whenever the patching is performed on the endpoint, based on the patch policies that are being applied, we only apply suspension for about 20 minutes when the machine is getting rebooted. But if you're looking for a similar capability before the patches are getting deployed, please, please elaborate that. But for reboots, we do have a default suspension that gets applied there. All right. Next one. If I use the script function to suspend alerts for a longer period, like 600 minutes, but after 60 minutes I have completed my task, can I unsuspend the alerts manually in the suspension list where I can see them? Can I unsuspend them? Yes, I think you'll be able to go and make changes to the suspension that you've created, because the suspension will be available on the suspension page. So all options that suspensions provide will be available there. You'll basically be able to go and edit the suspension as you wish. But again, you'll have to go through the suspensions page. I also see a question which says, can I unsuspend the alerts via script? So we don't have an option right now which says remove suspension. But I think you'll have to navigate to the suspensions page to make an update. All right, that's good. Jinkai, if you don't mind, can you show the create suspension function once again so that everybody can see that details? Yes. So when you hit add row, you get an option to create suspension. Oh, I'm sorry, not in this environment at the moment. So I'm actually going to go back to my demo. Yeah, there it is. Is there a specific question here? They wanted to go through the features available. So if you can just quickly run this through once again, what are the options within the function? I'll call it out. So under select alert type, you will have monitors and alerts. So right now I've selected monitors. So when you say select, you will see custom monitors and custom monitor types. So I'd like to call out that it's very similar to what we have under the suspension space when you are creating a suspension for a monitor or an alert. So it's the same menu here. But what you can essentially do is you can select monitors or alerts or both. And it will respect all of them. So as you can see, once I save selection, you get the Adobe Acrobat reader is uninstalled, the monitor that I had created here. And then if you had selected an alert as well, you would get like you would get a split over there and you would see the monitor as well as the other. All right. So there's a great question here. It says, can you pass endpoint or company name into this suspension rule title? Yes. So we are actually had a discussion today. We are actually going to pass the name friendly name of the endpoint so that on the suspensions page you are easily able to distinguish that is. That is an announcement that we discussed. All right. Great. Would that be for any variables that we can utilize like company site or just endpoint? So right now, I think the idea is to make sure that you can identify the endpoint on which that suspension is applied and you'll get the entry at an endpoint level. So right now we are thinking friendly name because that makes the most sense. But we are open to feedback. But if you feel you'd like to see a combination of like endpoint or, you know, endpoint and company name together. We'll take one more question. Is it in any of connect twice plans to add an option to run a scheduled task with also the option of next agent check in? Yes. Yes. I can take it. So we are actually working on an initiative, which is running next agent tasks or recurrent tasks on next agent checking that is currently in development. Thanks for calling that out. I actually want to I can call out the releases that are coming up. And that was one of the items which was running tasks on next agent checking, which is the scheduled tasks on next agent checking and a couple of more improvements. Thank you. Okay, thanks. Thanks for the great presentation. Thank you. And also answering those questions. So everyone, as I said at the beginning, you'll be sent a recording of this in a day or two, and it will go up on our YouTube channel. And please do check out the Connectwise University anytime we have a calendar in there where we put all of the events, including our other webinars, and we don't have one of these next week will be at IT Nation Connect. So see you all in two weeks time. Thanks, everyone. All right. Thank you.
