Transcript
You might recognize some new faces on the couch today. Not totally new. You guys have been here before. But we are missing Josh and Tara. I believe that they're out... I think they're trying to get their name on the Hollywood Walk of Fame. I couldn't get a confirmation on that, but this whole PDQ Live webcasting has kind of gotten to them. So they're out trying their best to get their star out there. But anyways, they're missing out because we've got a great show today. We are talking about a lot of stuff. I think everybody gets excited when we have Mark on, because you know that we're going to be kind of looking behind the curtain a little bit with PDQ Connect. So we've got Mark Littlefield, VP of Product. We've also got Leilani and Michael joining us today, both product managers, correct, on the Connect team? We're just Mark's underlings. On the product team, though. Yeah, on the product team. So we've got the experts with us to kind of like take us on a tour of PDQ Connect. And I know we've got a ton to get into, so I don't want to kind of draw this out. I just want to like jump right into it. So I'm going to pass it over to Mark to kind of lead us through a little bit of the roadmap, because I think even this morning, the roadmap had actually shifted. Yeah, that's right. We are excited to talk to you about the roadmap today and dive into some of the changes that we're making, which are pretty big. Like the car sound gets me every time. You know, it's funny because there's actual, like there's sound and stuff inside of that stinger, but yet Kelly still drops the, we couldn't have just put baked the car sound in. No, no, of course not. It has to be different every time. Well, we have been really, really busy working on PDQ Connect. If you have not checked out the roadmap, you absolutely should. If you just Google PDQ Connect roadmap, you can find it. We have it up on the screen. There is a lot that's in progress. We have worked on and delivered a lot of items over the last handful of months. If you're feeling a little stressed about the rate of development, I have bad news for you because we're not slowing down. We have a lot that we're working on. In fact, when Allison messaged today, she said, we're updating the roadmap every two weeks now. That's how fast like we're moving. Yeah. I mean, it's really, really quick. Before we jump into the actual items, I just want to acknowledge that the roadmap is not possible without everyone on this call and all of our customers telling us what it is that they want us to build. We analyze every piece of feedback, every sales phone call, every customer email, every ticket that goes to our support and solutions department. We actually look at all of them and analyze what are the areas that we need to invest and add more capabilities to address the needs of our customers. So thank you before we jump into this for everyone who contributes great ideas and helps us build the right things because it makes a huge difference in what we build. We are going to go over some of the features that we have not yet released and give you a little bit more information. We're going to do some live demos today, actually show you these features actually working. So really excited about that. We're going to start with Michael, who's going to walk us through, I think some really, really cool improvements to how automation works inside of PDQ Connect. All right, cool. Automation we are going to introduce our new policies feature. Really quickly, just echo what Mark said. A lot of the customers have been very instrumental in helping us shape this feature. So absolutely love the engagement that you guys have all given us. So I'm going to come over here and come to our new policies tab and let's dive right in just to show you what it's like to create a new policy. And then as we do this, I'll talk a little bit about not only, you know, the purpose of creating a policy, but how it maybe differs from automations you've been creating Connect to this point when it might make sense to use one over another. So inside a policy, there's a couple things to pay attention to. You have your rules. This is essentially what is the policy trying to accomplish. You have guardrails. This is like the boundaries within a policy, within which the policy is allowed to work to accomplish its mission. And then the devices, obviously, that you want to point this policy at. So just as a simple example, I think I already have a rule in here for, you know, keeping Google Chrome installed on devices and up to date. If there's, you know, we can keep this thing going with browsers, go to Mozilla, for example, and say that I want this policy also to manage Mozilla Firefox. Don't necessarily care that it's installed on every machine, but where it is installed, I want to make sure that it's updated to the latest version. So we'll add that rule in here as well. You know, could go however far we want with this. What I want to illustrate is with the previous, or up until now, the way that we would use Connect to accomplish what we're trying to accomplish with the policy here is a lot of different things. So in order to get this Google Chrome and up to date, you'd need to be over on the devices tab. And you need to first make sure that you have your groups targeting Google Chrome being old. Then you need to come over here to your automations and create an automation. Need to find the Google Chrome old group. And then you need to find the right package for it. And I've been talking about this for a while now. I'm already tired of all the work that goes to create one automation to manage one piece of software. Right. A lot of steps that it's like, hey, I got to do this first, I got to do this next. And then it's not just that, but then it's like, I've got to maintain those things, make sure that my group memberships are working right, I've got to make sure my automations are working right, and that everything's firing. That way at the end, I'm achieving the result I want. Exactly. So where this sort of just cuts down on that is, I'm done. Google Chrome is ready to go. I just pulled that in. And rather than doing that for each and every software, I've got a bunch of rules in here that somebody in testing has already created. You can just drag them all in. Here, there's a cool one I'll show you guys here on the webcast. We do support shift-click. So you can pull a bunch of them in at once, just if you have them ordered as such. Same with control-click. Now are these all user-created rules, or are there any rules that are created by PDQ, like the package library, things like that, where we create it and build it for you? These are all user-created, and the reason for that is the software list that we have available is something that we're curating. To start with, this is software that we have a PDQ package available to deploy, and it's one that we've configured properly so that we can reliably track that it's on the latest version or what version it's on. So this list will grow over time and just be available for people to come in here and find the software that they need. Ultimately, we're planning to allow users to come in here and bring their own package to manage software that maybe we don't have in our library yet as well. I think going along with that question, it is so much easier to create a rule. As you can see here, you're not creating filters and trying to figure out what is the right filter structure and logic. You're selecting the application, and then you're just saying whether or not it should be installed or just updated or not installed or removed, and then that's it. So you add that rule to this policy, and a policy can have many different rules. So you can imagine that maybe you have your servers, for example, and on your servers, you have a certain number of certain rules for what you want installed on your servers. You put all of those rules in a single policy, and then apply that policy to all of your servers. And then it will automatically enforce the installation and compliance of that policy. Yeah, exactly. So just continuing through steps of creating a policy here, in Guardrails, what we're going to be launching with for the early access coming soon is a maintenance window. So the two options that we have here are that it can deploy anytime. This is similar to if you had an automation set to the automatic trigger, this is essentially the same thing. Anytime that the policy sees a device is not following the rule, it's going to try and run a deployment on that. If you want to restrict when deployments are allowed to happen, you can come in here and set a maintenance window for when those devices are eligible for deployment. And then, yeah, it's just assigning devices. Like Mark was saying, if you had some list of software that you want only for servers, some list of software you want for workstations, or any other breakdown that you want to have, as long as you have a group for those devices, you can target it here directly. So like I said, this could be targeting new device servers. I'm actually curious if there are any devices in this group. Looks like there aren't. Let me see if I can find a good group in here. We'll just apply there. Okay. We've got a few devices. Once I save this, what it's going to show is it's going to do this calculation. And, hold on, I'm going to have to refresh real quick. Okay, so you can see what it's doing right now is it's trying to calculate the compliance and show how well these devices are following this rule. If I go out to policies, you can sort of see this generally. I've got all these policies here, the number of rules that are on them, devices that are targeting, and it's showing the compliance. So are those metrics going to show up in the dashboard and stuff? Yeah, they're going to show up in the dashboard. And that's one of the things we'll be continuing to build out throughout the early access phase is we want to get this in people's hands as early as possible so that they can start testing it, playing around with it, seeing if it works well in their environment. And then as customers are using this, we'll be servicing it not only in the dashboard, but also here in devices, you'll be able to check compliance that a device has for the potentially multiple policies that are targeting it. And we're also planning to add it here to software. From a software perspective, you could have some number of rules targeting some number of devices. So what is the breakdown of how well those rules are being followed for this specific software? So we are going to have an early access because we're already getting asked about it in the chat. Is there an early access test group for this? If so, yes, please. Yeah. Yeah. We do have we are collecting, you know, names of people that want to be added to early access. So just keep that rolling in. We'll go through the chat here if there's anybody that hasn't been added yet. Make sure we get a link posted so that you can sign up for it. We think it's going to be a great improvement. Again, like if you're used to the way today where you create like Michael showing custom groups and you have packages and you have automations. That's not going away. That is still an option if you want to manage it that way. For me, I find it really easy to use policies. You can just easily scan the page you see on the screen. You just scan it really quick and you can see where am I compliant, where am I not compliant. Whereas today with automations and groups, you have to look through each one one at a time and just see is the count what you would expect it to be. This is a great simplification. It's a workflow improvement. Yeah. Yeah, it really is. The other thing that I think is exciting about this is it's getting our, this is our first step to more of a policy driven approach to managing devices. First phase of this, we're just covering software. But one of the other things we've been cooking up and we're really excited to get started on is policies to manage Windows updates as well. And in addition to some of what you've seen here, that's going to come with things like deployment rings, the ability for users to defer reboots that you need to get the update installed all the way. And like scheduling when the install happens versus or downloading the update versus installing versus reboot. So you have a lot of granular control to just make sure that the updates are working well in your environment. Yeah. No, that sounds amazing. Because again, a lot of people are coming from maybe a different solution, maybe like an Intune or WSUS or something, and they're just, they're used to a different workflow of managing their devices and those updates and the software policies and stuff. So adding that in there, like you said, Mark, is like, you know, all the features that are currently in there, the device groups, the automations, it's all staying. You're just getting more ways to do it. Yeah. Yeah, exactly. Right. Yeah. Still plenty of use cases for automations. We don't plan on taking those away or sunsetting them. Like with automations, you still have a lot of power to schedule deployments for the future or set up recurring deployments that don't necessarily have a policy rule compliance component to them. So we plan to continue supporting all those features as well. Let's see, there's a question in the chat. New rules allow for sending messages to user that browser must be restarted update. Not during the early access phase. That is something that we are looking at through a couple of different perspectives. We can speak a little bit more to that maybe another time. But one of the common requests that we have is for like on a package, a custom package to have message steps and the ability to like pop something up to the users that lets them interact with the package mid deployment. So it is something that's on our mind and we'll make sure that as we design that out, it works well with the policies feature. Great. Okay, should we shift gears over to self-serve? Yeah, let's do it. Yeah, this one, I know a lot of people are really excited for this. This is one that we've been asked about, not just since Connect. I think we've been asked about this for probably seven, eight years. I know when DNI was our flagship product, it was still being asked about back then. Yeah, yeah, this is an exciting one and has been really fun to design and build this one just because it's sort of like Mark was saying, in some ways, this is a new product. There's new aspects of it that we get to add. And so for the engineering team in particular, it's been exciting for them to dive in. So yeah, self-serve. The goal of this is we want to reduce the amount of tickets that you have to manage saying, can you please install this on my machine? Can you please help me do this with my machine? By consolidating some of that into this self-serve hub. So the way that this works is I'm going to make some software available to users in my environment, come here, pick a piece of software. Again, to start off, this is a list of software that we're curating. As we get this a little bit more developed, you'll be able to bring your own packages into this list of software. So if we pick something like DBeaver for my engineers, then the next step for me once I pick that software is I get to assign it to. is I get to assign it to the right people. So I don't know if I have a group in here for engineers specifically, so I'll just say all devices. And so all devices will have this software in their self-serve hub on their device. They can go in, click the button, and it will deploy the package for them. So what does that workflow look like for the users? Are they going to a web address that's specific to your org? So it's going to be an application that lives on their machine. Like you can think of it similar to, like a managed software center. Yeah, like a managed software center. There will be some flexibility around exactly how users interact with it, whether it's coming from system tray or something they can open from a start menu or other like desktop shortcut, and then the equivalents that we have on the Mac side as well. Let's show the setup screen. I think that everyone's really curious about how that will. Yeah, what is it going to look like? So here's the easiest way for me to demo that right now with what we have in this environment. We're missing Josh today, so we had to have him represented somehow. This sort of gives you two things. It first gives you a little bit of a preview of what the self-serve hub will look like on your end users' devices. As far as, you know, on the left, you've got options for your software, your actions. You have this bar across the top, and this is where, you know, you can put in your customization rather than Josh's face or IT team's face, probably a company logo or something like that. No, I definitely recommend sticking with Josh's face. We'll make this image the default for everybody. But yeah, something, oh, it's not typing. There we go. Something like company name here, and then we've gone and, you know, we can thank some of our design team for this, curated a few nice-looking color schemes that you can pick from. You can preview these both in light mode and dark mode. It should just go based on whatever the system preferences your user has. And if you don't like any of those, you can pick, you know, your own colors for the header or the button. The engineer who demoed this previously picked some really fun colors, and I've just left them in there because I get so much joy out of this pink and brown combination. Anyway, this is what it's gonna look like for end users. You've got software and actions. So question about actions, what is that? How does it differ from software? This is where you can actually come in and pick any custom package that you have prepared. So it could be a custom package that installs software, if that's what you want it to do. Some of the customers that we've talked to have mentioned, like, it'd be nice to have a package to install a printer or do some sort of disk cleanup. I was about to say, some, you know, yeah, disk management. Yeah. Cleaning up temp files, things like that. Exactly. So it's sort of the world is at your fingertips. You can put whatever you want in there. If it's something that you can deploy from Connect, you can make it available to your end users to deploy as well. There was a question about how, you know, how do you limit who gets what software in their self-serve portal? So that is fully configurable. That is done by groups. And so for a specific piece of software, you can say this software, in our example a moment ago, 1Password is available to computers in these groups, but maybe not in these other ones. So if you have, like in Michael's example, some software that's really only for engineering, you don't need the rest of the company to see that in self-serve. You absolutely can restrict it in that way. Yeah. And that targeting of software or, you know, packages to individual groups is done per software. So you don't need to create, like, self-serve hub and then pick which one of that, like, group of software goes to some group of computers. It's just, each one of these will target, you know, dynamically whichever devices end up in the groups that you put here. Okay, great question about can the groups be tied to AD groups? The answer is yes. And I think that there's probably a little bit more that we can do there. First thing is, I don't know if we have a good demo for it here, but we do have an integration with Active Directory where you can pull in some groups to connect and use that data to target AD groups. What a lot of people are interested in, though, is that the groups be user-based. Today, the groups that we pull through the integration are computer-based. We don't yet have user-based groups in that. And that has been some pretty common feedback we've received from customers as we've demonstrated this feature. And so we're talking with the engineering team right now about expanding that integration so we can pull in user groups as well, and then ultimately make this feature more targeted at the people that you wanna get software access to. I saw a question about multi-tenancy. So the way this works is each tenant has its own self-serve area. So you can configure the self-serve by tenant, but there isn't a primary where you manage it just purely from the top level. Yeah. Super cool. I think people are gonna love this feature. I think, like I said, this is one of those that people have been asking for for a long time, right? They wanna avoid the phone calls, they wanna avoid the tickets. Like, great, just go install it yourself. Well, we've had customers do it, but it's required, like, we're using the API or on-deploying inventory, even getting more creative with how you do it. Yeah, I saw someone on Reddit where someone was like, oh yeah, I'm gonna do this with the API. I'm gonna build out this self-service hub. And I was like, you might wanna wait just a little bit. Yeah, yeah. Maybe save yourself some time. What's nice about this is you don't have to worry about user authentication like this because it's accessed on the device. So you access it through the system tray or through another means there. So there's not like a separate username and password to log into the self-serve portal. It's right there on everyone's computer. Really easy to click. And as an IT person, you don't have to do a lot of custom coding to make this thing work. You just configure it just like we did. There's really no coding needed at all. Right, yep. I'm seeing some questions about when. Just a couple of comments about that with regard to both policies and self-serve hub. These are both like the primary focuses for their respective engineering teams right now. And we're getting pretty close to ready for early access for both of these. Not sure on the exact dates, but we're talking about a matter of weeks in both cases. Awesome, that's soon. Yeah. Yeah, I love it when we're showing stuff off because unlike movie trailers, where you're like watching, they're like, hey, coming 2028. And you're like, what? Why are you even showing me a trailer? It's like, no, we show you something and it's coming out in like a few weeks. Yeah, this is all real code. None of this was like fake or screenshots. This is all like legit product. Cool, all right, what else we got? All right, Leilani, I think you're up. Awesome, so the features that I'm gonna be talking about are ones that stemmed off of a request that we had for backstage mode. If you're not familiar with backstage mode, it's pretty much being able to do remote actions on a device without having the user know that you're there. So the way that you would solve this right now inside of Connect, we have the remote desktop option, which obviously that doesn't really solve your problem if you're wanting the user to not see that you're there. Or you can go in and do a command. But the way that you do commands right now is you have to know exactly where you're going to create a command. So it's not live, it doesn't know exactly what you've done previously. So you have to know exactly where it needs to go, which can kind of be frustrating when you're running a command on a device. So I'm excited to share that we're going to have Live Shell as the first live feature that we're going to be introducing, which is pretty much like you're on the terminal on the device. So you'd be able to, oh, I'm in caps, let's see. You can see the actual files on the device here and then go into one of those. So I'll go into the library here. I'm loving chat's response already. Like within seconds, they're like, yes, I've been waiting for this forever, this is awesome. Yeah, so now as you can see, it's a lot more live. You can see what you've done in the past and then just go through it that way. And then there's also going to be the up arrow that I know lots of people have been asking for. Oh, it's reconnecting here, but yeah, all of those actions or key actions that you've had with a terminal, it'll be available in the terminal. So it's pretty much like you have it here. You'd be able to adjust which type of command you'd want to run. So ZSH, Bash, or yeah, PowerShell 7. And then for Windows, same. We'd have PowerShell 5 or PowerShell 7. We'll offer whatever is the most used on that device or whatever is available as like the one that we'll start with. And then you can open it up to into a new tab and then that'll open it up here if you want it to still do things on Connect at the same time. You can't really see the difference here, but let's see, how do I get out of that? There we go. So yeah, as you can see, it'll open a whole new tab for you if you want it to like mess around with something else inside of Connect at the same time. So yeah, that one is LiveShell. So if you got those users that are very needy, very hand-holy, you just have that LiveShell window up for their computer, just like 24-7. Just like, okay, Barbara, hold on. I guess if that's the way you want to do it. And then the next live feature that we have is File Explorer. I love this one. So this one is where you'll be able to see all of the files on the user's device. This one's still, like Mark mentioned, this is real code. So we're still working on adding things to this, but pretty much what you'd be able to see is a look at all of the files, all of the folders on the device. You can delete those. So there'll be like a delete option here. Copy the file path name or file name or file path. You can also, if you know where you want to go, you can enter the file path directly in here. We're going to have that drag and drop option. So you can just be directly on your device and drag and drop the folder that you want onto that user's device. You can rename those files or folders. So pretty much anything you'd want to do with those files and folders when you're on here. I mean, I'm thinking, you know, I got to get some log off of somebody's computer, right? And to just be able to open up a Remote File Explorer and never talk to the user and just pull it off is just the dream. And you don't have to interrupt them with remote desktop or anything like that. Like you just get straight to the file. Yeah, so cool. Awesome, yeah, that's everything I had. So I think it's your turn, Mark. Great, all right, I'm up. There was a question about LiveShell as whether or not that is Mac and Windows or one or the other. It's both, so everything, LiveShell and File Explorer will be Mac and Windows when we release. And that should, it's planned to come out hopefully at the end of September. We're going to be getting some early access groups for that as well? No, we're just going to actually release. Just going live with it, gotcha, just like LiveShell? Yeah. Launching it, we're doing it live. All right, well, we are humming along here. The next thing we're going to do is I'm going to spend a little bit of time talking to you about some of the things we've released recently and announce a couple things that have not been announced yet. So first, I'm not going to show this one. We'll just talk about it. Actually, no, no, I will. I'm going to show it. We have made a lot of improvements to the PDQ Connect API. If you've been watching, or if you haven't been watching, you should. We have invested a lot in the API, adding new endpoints. We've also added in scoping on API keys. So you can now control what, when you make an API key, what it can access in the product. So you can give it read access only, you can give it read-write access to certain objects. So a lot of flexibility there. And then we also have made the API available on all of the Connect subscriptions. So it used to be premium only. We heard a lot of pushback and feedback from our customers around, hey, we really want this API in all of the different offerings of PDQ, and we've delivered on that. So anyone can now go and do it. Yeah, yeah, I mean, we think it was the right decision for everybody. Excited about that. There is a lot of other things we've been working on too. And so I'm gonna spend just a minute here and introduce you to two features. One of these features we just barely released. So we're gonna publish the release notes right after the webcast here. And that is AI deployment log summaries. So maybe to kind of frame it a little bit here, we've all done a deployment that has failed for whatever reason. And it can be a lot of work to figure out why did the deployment go bad? Yeah, there's one that I did not too long ago, actually, where it failed. And I looked at the deployment logs and I could not figure out why it failed. You're like trying to decipher it and- Yeah, yeah, we've made the deployment logs way better. I mean, there's been a lot of improvements around the deployment logs to make it a little easier. It's great now. Yeah, it's significant improvements, but it can still be hard to figure out why did something fail? Because we only return what the logs tell us. Yeah. In this particular example, my deployment failed because the device was out of hard drive space. But the logs never told me that and they never explained that to me. And so what we have done is we have added a new summary for your deployment. So in this case, I have a deployment here. It's for Discord. And I'm gonna go ahead and jump into the failure here. We can see our failed deployment. We're gonna go ahead and look at that output log. There is a lot of information in this output log. We got lots of different steps. This is actually a pretty small one. Oftentimes it'll be thousands and thousands of rows. What we have done is we've added a summary for that output log. So leveraging PDQ.AI, you can now invoke or request that our AI system take a look at and analyze your deployment to help you figure out what went wrong. And it will look at things like, did the computer run out of hard drive space? Was the computer online when you tried to make the deployment? What were the failure codes? And what do the failure codes actually mean? All of that we're bringing into the product. So you don't have to go out to your favorite LLM and go do the research yourself. Plus it has contextual awareness about your environment inside of PDQ Connect, which is something you don't get when you go out to like a. when you go out to like your LLM. And awareness of PDQ itself. Yeah, yeah, exactly. Yeah, so we just barely released this. It's a brand new feature. You'll now find it at the top of your output log. There'll be a little button that says summarize output log. Now we know that some customers don't wanna use AI, and that is totally fine. You can manage what AI features are available inside the product by going to settings and going to AI tools, where you can turn on and off various parts of the product. So in this case, deployment log summary. Maybe you don't want that. That's totally fine. Turn it off. All of our AI features are in early access, which means there's no cost to use them. So we want you to go try them out. And we want you to give us feedback as you're using the output log. We'd love for you to use the thumbs up and thumbs down. Tell us what's working, what's not working, because we are wanting to make it good. We wanna make it better. All right, ready for the next one? Oh, dude, I'm so excited. Okay, I've got two more for us today. All right, we are gonna jump over to a device now. So I have five devices in my test environment here. It's looking pretty good, a whole bunch of devices here. We've all been in the place where a user creates a ticket and they say, my computer is slow. Oh yeah. Something is wrong. My computer got a blue screen. Yeah, it's all day, right? Like we get it all day long. Especially if you're working help desk, I mean, it's just constant. It can be challenging and really time-consuming to go and troubleshoot one of those things. Where do you start? You look at the event logs, you go pull crash logs, you're gonna go look at memory usage, you're gonna go look at processes. It can be a lot of work and it really adds up a lot of these tickets over time. So we are adding in, this has not been released yet, we are adding in the ability to summarize or engage with a device using PDQ.AI. So what you can now do is you can go to Ask.AI. This is not released by the way. We'll do a new conversation so we can give it from the beginning. And we're gonna say, run a health check on this computer. User is complaining, if I can spell, about slowness. Now what that's gonna do, again, this is not released yet and so you're gonna see a couple little weird things here that what it's gonna do is it's gonna go and decide what commands to run to analyze this. So it's gonna run these commands live on this computer. In this case, we're gonna look at top processes by memory. You can see the PowerShell command that we're gonna run so you can decide if that's okay or not. It's gonna look at stopped automatic start services and a handful of others. And we're gonna go ahead and run that script or run these scripts. It's gonna collect all this information and then it's gonna give me an output and tell me what is going on in this particular. So it's doing the troubleshooting for you at this point because again, someone reporting, hey, my device is slow, is super vague. Yeah, it's not helpful at all. There's a million places you could start, right? What was running at the time? What's the hardware spec on that computer like? And so this is like, hey, let me find all of the things that are the most likely culprits and just check them for you. Yeah, that's exactly right. And so it has all of the collective knowledge of PDQ's IT knowledge, right? We've programmed this agent to know when someone says something is slow, where should we look? So it's not just doing this like vague, like, well, let's go analyze this in this way and this way. It's very like focused analysis based on IT and how IT troubleshoots issues with computers. So in this case, it did find a handful of things. It says that the device is generally healthy. It's looking okay. It does need a reboot. And it does have some memory problems. And it's gonna highlight a couple services that are currently stopped that maybe we want to reconsider and maybe go look at. Point is that it's going to analyze a lot about it. In this case- And in reboot, yeah, it could definitely be the issue. It absolutely could be. And so we could reboot the computer very easily. In this case, it's a VM. It's also identifying that there's not a lot of RAM on this computer, eight gigs of RAM. Not super good. Not for Windows 11, no. No, and so it's going to help pull that out and a little bit of insight. So it's not just looking at one little piece. It's looking at lots of different data to tell you and help you be more informed as an admin. Right. That's incredible. I mean, again, it's like how many times, like, hey, my computer crashed during this. I'm like, great, where do I start? It's like, what logs do I have to pull up for this? And instead you could just ask this. It's like, hey, so-and-so complained that this happened when they did this, you know? And it could probably go identify those logs and pull them back for me. Yeah, so I've asked it things like, hey, can you, this user's got a really, they said they have a blue screen. How do we address the blue screen? It'll go and look at the event logs and it'll go pull and say, this is the blue screen that they got. Here's what we think went wrong. And then it can give you suggestions on how to remediate that. That's huge. Absolutely huge. Just saving you a little bit more time, you know, helping you out, just a little bit more, making your time where you could spend your time a little bit differently. Yeah, for sure. Ooh, all right. Yeah, let's take a question or two. We do have a few questions queued up. And the first one, can you speak briefly about some of the recent incidents and how you're balancing new features with stability of the core and current features? Sincerely, Alexander. All right, that is a great question. So obviously we want the product to be available all the time. I don't think we've publicly shared a lot about this. What we're finding is that with the emergence of AI, the number of vulnerabilities that exists in software that we help update has exploded. Oh, yeah. And we've seen this with like the Microsoft, you know, Patch Tuesdays. They're bigger than they have ever been. That does put real stress on our systems. Yeah. Because we're creating the packages for all those things. Especially when you have a vulnerability scanner. All of a sudden your log just blows up. It's like, hey, there's been 700 new vulnerabilities released this month. Great. Yeah, so it's like, I'm not gonna downplay it. Like it's a legitimate challenge for us. We are prioritizing that on our roadmap. So we have a handful of teams that they're exclusively looking and working on addressing some of those scalability items that have emerged due to the insanity that AI has introduced for IT teams around the world. Yeah. We fill it at scale. And so that is a top priority for us. There are certain teams where we have pulled them off of building features altogether to focus exclusively on how do we continue to scale in the new world that we're now in where there's vulnerabilities everywhere in the software that we update for customers. All right, let's take a look at this one. What's on the roadmap for DNI or is it just left in the corner to die quietly? Just drop. Thank you for the emotional element on that one, Saab. Yeah, so there absolutely is a roadmap. You can find that roadmap. There's a public roadmap for that as well. If you go, I forget the exact URL, but it's if you look pdq.com, Deployment Inventory Roadmap, you'll find it just like there is one for Connect. There's not as much on that roadmap. To be completely candid, we are investing more of our time and you can see that in Connect, but we absolutely have a roadmap. We recently released feature permissions inside of Deployment Inventory. So if you've missed that update, you should go take a look at that. Yeah, and we have the team on here as well that can answer questions, but there's a lot we're working on. Okay, few more in the queue. Will policies have a best practice documentation with examples? Thank you in advance, Marcel. Good question. We haven't yet settled exactly how we want to tackle this. One of the ideas we've had so far is we may seed the feature with like a sample policy that you can click around and get it just for the feature before creating of your own policies and maybe even enabling what we put in there. It's gonna be during this early access phase that we hopefully learn from our customers what some of those best practices are, and then we'll take it back to the team to figure out how can we enable everybody to take advantage of some of that community knowledge. Yeah, it's a great approach. Next question, can rules work across tenants or do we have to do them for each one? Thank you, www, www. Again, that's another one. Starting out, this is gonna be sort of geared around single tenant use, and you won't have the ability to share rules from tenant to tenant, similar to how today we don't have that ability with automations, and that's just sort of a known limitation we're gonna have to work around for a while. Okay, next up, we have a question from AdamL5707. Will policies work for macOS as well or start with Windows devices only to start? Yep, great question. It will work for macOS. Right now, that's actually one of the things that is on the top of the list for, before we get early access, we're building support for Macs. The difference between them will be for Windows, we will have just a longer list of software that is available to manage via policy, and on the Macs, it'll just be a little bit more restricted as we start out, sort of similar to how our PDQ package library is today. Yeah. All right, just a few more. I'm not sure what you were discussing when this question was submitted. Hopefully, you'll be able to decipher this. Is this limited to checking for software compliance? Can it be customized to check other compliance via PowerShell scanner? Yeah, so definitely limited to software compliance to start out. It's compliance specifically relative to the rules you've created. So, and this is a term we wanna be really clear about because the word compliance carries a lot of meaning like outside of our product, like there's compliance to security frameworks and so forth. When we're using the term compliance, we're talking about the other side of a rule that you've created. Yeah, that specific rule, how are they following that rule? Exactly. So, as policies grows, the more things you can make rules about, the more things you can have measuring compliance. And you talk about like actions and stuff that people feel like deploy themselves. You think that that kind of computer management level stuff will be maybe on the roadmap at some point? Computer level management, you mean like password length and things like that? No, I mean, kind of like those other, for instance, like they're talking about PowerShell scanners that they can customize that type of stuff. Do you think that would ever come into that compliance and making sure that like people are like those rules that you set maybe via PowerShell scripts that you'll have that same kind of level of control? Yeah, to be honest, I haven't thought of that, but it is a really fascinating idea. And I think the nice thing about how we've set this up is I think we're well set up to expand in a lot of different directions. And so definitely something I think we can look into. Yeah. All right, two more in the queue. Will policies support relative timetables, i.e. second weekend after Patch Tuesday? Yeah, great question. Less relevant to software policies now, but we are building that into the Windows Update policies that we're designing. What you'll be able to do is set a delay for after the updates are released on Patch Tuesday, how long until that policy starts to take effect. And our final question, can you give more detail on what AI you use and how our data is kept private? Thanks, JustRob. That's a great question and probably one that we can't fully answer just with the time that we have left. We do keep customer data separate. We don't use like a central model that we're training that uses your data with other customers' data. At no point is your data shared with anyone else. That's true just in general, but also with AI. We are working on some additional AI documentation that we can provide around the security of the AI. That's my quick answer. Kelly, I have two more things. If we can just wrap up with those, that's all right. That works for me. Let's do it. All right, so we have two other items that we didn't have time to go over today. So we'll just briefly touch on it. One, if we can switch to the screen, I actually wanna show a change that's coming. We are implementing a new top bar across PDQ Connect. This is gonna come in the next couple of weeks. We wanted to share this because we know that a change to the front end can be a little jarring, especially if you're used to it. So we are implementing this top bar. That's where you'll find the org moving forward. So it'll be over here on the left. Why we're doing this, one, we wanna make the org more discoverable so you always know what org you're in. Right now, if you scroll down on the page, you might lose, depending on your resolution, what org you're in. Yeah, and we're also looking to build some additional functionality like live notifications. And so this is a precursor to some additional functionality where you can see things that are going on in your environment up in like a notification feed up here in the top corner. Oh, gotcha. Yeah, so excited about that. Some big changes coming there. And then the last item I'll mention, we just barely put this on the roadmap. So if you go to the roadmap, you'll see it. We are now working on imaging inside of Connect. So it's very early still. I saw a demo of it yesterday. It's looking really good. Wow. But we will have the ability to image inside of Connect. Towards the end of this year, we'll start talking about early access for that functionality. Wow, I bet there's gonna be a lot of people that are interested in signing up for that. Yeah, it's gonna be really cool. It's looking amazing. Very, very cool. Well, man, we went over, but I don't think anyone is complaining because we just like, you guys revealed so much. It's always so fun having you guys on because again, you guys pull back that curtain and show all the stuff that like, honestly, those last few things you talked about, like, I had no idea, you know? So it's really cool to see that. Thank you guys for joining us. Thanks everyone for watching. Again, we take feedback super seriously. You can always reach out to us, find pretty much any one of our employees, reach out to Mark, reach out to us on Discord. Like, we'd be happy to hear from you and hear about these features, sign up for the early access and stuff like that. Again, we love building what people want. So it gets us super excited to see you guys liking it. So anyways, for PDQ, I'm Brock. Thanks for watching, everyone. Thank you so much for joining us today. We love how excited you are and how excited we are about building the things that you want us to build. Do us a couple of favors, like and subscribe to us on YouTube, leave us your comments, and please join us right now on Discord. We've got some trivia and some other games. other games happening there with I do believe Andrew and maybe Brock might even join. So there you go. Have a great week. We'll see you back here next time.
