Community town hall – November ’24

Since I joined in May, that’s when we’re kind of going to start looking at things. When I joined, some of you saw in the post that I came from more of the gaming industry, which has a very close connection with IT. I always had a fondness for the IT people that I worked with, so it was nice to join and learn how that works from this side of things. Just to cover some of the events: obviously, Co-Pilot was launched. Those of you who have been here for a while know there was a lot of talk about it and very positive discussion. Some people here shared with me a lot of their feedback, which was truly helpful for us as we updated. We are also seeing great results from our different partners as they discuss with us how it can help in their day-to-day work. Another thing we did, in correspondence to what you were sharing, is that we now have the Atera roadmap. By the way, this was recently updated for what’s going on this quarter, so it’s well worth checking in to see what’s coming next in the development cycles. We had this SentinelOne incident. If you remember this quote, “SentinelOne just destroyed Atera,” this was the biggest post of the year. Yes, some things are great, sometimes things aren’t as great, and dealing with them transparently and openly is important. We try to help as quickly as possible in the community and in other tools. 

By you telling us, “Hey, I need help, I need assistance,” and working with our support and SentinelOne support, we were able to help most of the customers. We always tell people if there are problems, instead of being frustrated, it’s better to communicate with us so we can see how we can assist, whether it’s through the CSX, the CSMs, the support, and of course, our PMs are always here to help too. 

We had some fun events like the IT Olympic Champions. Here you can see Egor rocking the design shirt that we created and sent to 50 of the IT Olympic Champions. That was a fun one. Just to run some numbers, and again, this is from May: we have 50 countries represented, as you can see in the chat as well. There are 200 plus posts, and I’m glad to say that I contributed only 20% of them, so the vast majority is still community-driven. The things that I’m contributing more on are the feature update side and updating you, of course, about worthwhile content such as the webinars. You’re very welcome to always comment and tell me if you want to see different kinds of content; I’m here for that. We had nice growth, and I see that you guys are engaged, commenting, and of course, the swag boxes. We sent them again; things are back in action. We also have some new badges. I wanted to actually focus on a few of them. There is the Keyboard Hero badge; we really like seeing when people are talking positively about Atera outside of the Atera forums. If that’s something that was done, share a screenshot with me and you’ll be awarded for it. It’s just nice for us; I always share these kinds of feedback with the team. A conversation starter to get things going; we know it’s sometimes awkward and weird to start a new topic, but you should feel free and we want to encourage you with this. 

And a Town Hall participant badge for everybody that’s here today; we’re going to show you a badge of honor that you can show everybody else. We also had some new swag, some of them in the swag boxes, whether it’s new shirts or new speakers (not boom boxes, sorry, that’s my translation). You can check out the Atera merch store and see what else was updated. 

So for the main event of tonight, the product updates, I’d really like you to meet the team. I keep telling you guys when you have feedback, “Hey, I’m going to relay it to the team, I’m going to tell the PM, I’m going to share it with the AI Co-Pilot team, the product manager.” These are the actual people that are listening to all of your feedback and taking notes. I’m really, really proud to present them. So let’s do one by one, and if you don’t mind saying a couple of words about yourself. 

Yarden Revivo: Hi, thank you Gil. Hi everyone, I’m Yarden. I’m the product manager of Atera AI Co-Pilot. I’ve been at Atera for three years now and have spent the past year fully focused on the Co-Pilot. I can’t wait to show you how the new Co-Pilot features will help you get more value from the Atera system. 

Gil: Awesome, yeah, and I like working with you a lot. 

Ohad Savir: Hi guys, pleasure to meet you. My name is Ohad. I recently joined Atera a few months ago to lead the ITSM products at Atera. Super excited to meet you all and learn from you and provide you with capabilities and features that will help you do your work better. 

Gil: Thanks Ohad. We also go to CrossFit together, functional training actually, FYI. Yasmin, please.

Yasmin Simmons: Hi, thank you everyone for joining. It’s great to be here. I’ve been at Atera for almost five years. For those of you on the line that I may have spoken to in the past, hey! And for those of you who haven’t, it’s great to meet you and I’d love to hear your thoughts in the chat or the Q&A through the session. I’m focused on the RMM side, and it’s great and interesting and also exciting to show you some of the things we’ve developed and things that are coming up. 

Gil: Awesome Yasmin. Yasmin is a great source of knowledge for me and super helpful. A lot of questions go to her and her team, and they always respond with delight. So we’ll start off with the AI Co-Pilot. Can you lead us the way, Yarden? 

Yarden: Yes, all right. Hello again. I’m excited to share some really amazing new features we’ve been working on for our Co-Pilot users, so let’s jump right into the first feature. You can slide, thank you. 

The first feature is the improved script editor, which has been one of the most requested features by our customers, by you guys. Many of you have been asking for a way to continue talking about the script and edit it more easily. So we’ve made some improvements to make the experience smoother and more powerful.

So what’s new? First, when you write a script, you can now add a comment to the script using the hash symbol. The AI will then help you by completing the rest of the script for you based on the comment itself. This means that you can just continue talking about the script without needing to rewrite large parts of it or get bogged down with repetitive edits. Another great addition is the live script test support. Once you’ve edited the script, you can select a device from the system and run the script directly on the agent to test it and see the response immediately. This real-time testing makes it much easier to fine-tune the script before deployment. Lastly, we’ve made the AI aware of the Atera syntax, meaning that the AI understands and uses the specific parameters to make your script more tailored to your environment. Let me show you a quick demo of this. 

Thanks, Gil. So let’s see. Nice. Okay, so you can go to the script editor and just start typing the desired script by typing the comment with the hash. In this case, I was looking for the five largest files on this computer, and the Co-Pilot generated the script. 

Then I can just continue writing another comment, for example, “now in Drive D,” and again the Co-Pilot generated the script for me. 

Once it’s done, you choose the desired machine you want to test it on, click on “play,” and you can see the results of the script in the bottom right of the screen. Super easy. We hope this improvement will make your life easier when working with scripts in Atera. 

Next up, we’ve been working hard on the new device search feature. It allows you to quickly and very easily search for any devices using simple natural language without the need for manual filter setup. You can now simply search with phrases like “find PCs with new security patches,” and the Co-Pilot will automatically pull up the relevant devices with the right filters. It makes it much easier and faster for you to locate the devices that need any kind of attention and perform bulk actions on them in just a few clicks. We actually reviewed some of your suggestions in the Atera community. We gathered some examples of queries that you asked for and can now be answered by the Co-Pilot. Questions like “list all machines not used in the last 90 days” or “which machines do not have BitLocker encryption on them” can now be entered within the Co-Pilot. Let me show you how it works; it’s pretty easy. Here I am on the devices page. I’m clicking on the “Ask Co-Pilot” button and just start typing in natural language, for example, “give me all Macs with less than 16 gigabytes and last reboots over two weeks,” and voila, here are the relevant devices. Pretty easy. You no longer have to spend time manually setting up filters; just type what you need, and it’s pretty easy. The Co-Pilot does the rest for you. 

Insights on Tickets, Alerts, and Devices And now for something a bit different: a sneak peek into a work in progress. It’s not released yet, but it’s insights on tickets, alerts, and devices. This is actually a huge addition to the Co-Pilot’s capabilities. 

We’ve gathered a lot of insights about some of your use cases from the Atera community and through direct calls with customers just like you. Based on your feedback, we’ve been working on a way for the Co-Pilot to help you answer some key questions about your environment. Soon, you’ll be able to query your tickets, alerts, and devices from your Atera account. Just imagine being able to ask the Co-Pilot things like “how many users are waiting for a password reset?” or “what is the most common alert and its average duration?” or “which devices are experiencing frequent system downtime?” These insights will help you make faster and smarter decisions, giving you the data you need in real time. 

We’re releasing this feature in phases, but the ultimate goal is to allow you to ask anything you want about your Atera environment, whether it’s asset-related data, ticket resolution time, or alert frequency. You’ll be able to get instant answers right from the Co-Pilot. I’d like to take this opportunity to ask you to share your suggestions in the comments for any kind of insights you’d like the Co-Pilot to help you achieve, and we will definitely take these into consideration.

So that will be amazing for us. That’s all for the Co-Pilot today. Thank you, guys. 

Gil: Yeah, actually, that’s amazing. I think one of the things that you guys do really well in the community is sharing best practices and finding these new hacks in this new world of AI. What are the right prompts that will make my work more efficient, quicker, better? That’s something that can totally be shared inside the community, so I encourage that. 

We’d love to hear what you have for ITSM. 

Ohad: Great, thank you. Thanks, Yarden, great stuff. Hi guys, as I said before, we’re focused on the ITSM tools and workflows for Atera. We are focused specifically on the asset management capability at the moment. I’m going to show what we’re working on right now. All of the items that I’m going to talk about will be available during Q1 2025. First, let’s start with the problems that we want to help you, our clients, handle better and more easily. 

Gil: Do you mind? 

Ohad: Yeah. Before I talk about the problems, asset management—the entire life cycle—is already supported from Atera, which includes request, fulfill, deploy, monitor, service, and retire. Everything can be done already, though a bit manually, and this is one of the things that we want to help achieve and solve for you guys. 

As I said before, the two main issues that we want to help you with are: 1. A lot of manual work—this is the first thing we want to solve, really reducing as much manual work as possible, making more of the actions related to assets automatic. 2. Data reliability—this is also connected to manual work because a lot of things change during the asset life cycle. We want to make sure that as many changes as possible will always be updated and presented to our users. 

Let’s focus on the first capability that we’re going to provide: asset matching and mapping. Let’s talk about matching first. Whenever a device, which is basically a monitored asset that has the Atera agent on it, wakes up, an asset will automatically be registered with all of the agent’s data from it. The moment it’s being released, by your decision—you can also decide not to—but by default, all the assets that you have in your inventory are going to be automatically appeared and described with all their information, including the user assigned to it, the type, the OS, and all the device information you have on it. 

Also, automatic mapping—you will be able to customize your inventory the way you need it. For example, all Mac and PC Windows laptops will be set as workstation asset types, while all Linux and Windows Server devices will be classified as servers. But you can choose whatever you want; you can create as many different types and segment them as much as you want. 

Moving on to the next one, regarding data reliability and freshness. We are integrating with the biggest vendors in the market that will be able to provide you with warranty and purchase information directly from their APIs. This means that you will not only see the internal data from Atera on your assets, but you will also be able to see the warranty types and, in some cases, the ship dates. For now, we are working with Dell; we already have Dell onboarded, and all the data is already there. We are working over the next couple of months to bring on Lenovo, Apple, HP, and more. 

For the last part, we are going to provide API endpoints, meaning you will be able to get your asset data integrated into your in-house platforms or even third-party platforms for billing, contracts, or whatever else you need. This will ensure that your assets are always updated with everything you need to integrate them with. 

I’m going to share a few screenshots of how it will look. This is the new inventory page. It will appear as a full-blown list of all your assets where you’ll be able to sort them out. You’ll be able to change their status, whether they are in use, retired, or in stock. By the way, as I said before, each time an agent wakes up, it will register as an asset, but this is not the beginning of the asset life cycle. First, you’re going to have them ordered, shipped, and on their way, but you will be able to manage all these stages.

Either manually or by uploading a CSV with their serial numbers, they will wait here with a status of “in stock” or “underway.” Once the device wakes up and the Atera agent is installed, they will be automatically linked, and their status will change to “in use.” Let’s take a deeper look at how the asset page looks. Can you skip to the next slide, please? Thank you. This is how an asset page looks. As I said before, there are three ways to create an asset: manually, by CSV upload, or automatically when the agent wakes up. As you can see, we have the ship date here and the warranty expiration date. You’ll be able to add additional custom fields with different information that you need, for example, color, and more. Everything is editable based on your needs. 

Next, let’s talk about device mapping. Adding granularity to your assets, you can see how you can set the device type based on their OS. Windows and Mac devices will become workstations, while Linux and Windows servers will become servers. It’s very simple to do, very simple to change, and migrate from. You can add additional asset types and migrate some of the assets you already work with to them. Everything will be available and customizable for you. 

Another big pillar we’re working on besides asset management is change management. We are investing in learning and collecting the needs for this big and very important pillar in ITSM. If you’re interested in joining the beta program in return for answering a few questions and talking to us about your needs, you would be more than welcome. Gil will talk about this at the end of this session. Thank you very much, guys. 

Gil: Yes, I’ll provide a few more details later on. I just want to remind you that if you have any questions, please put them in the Q&A. Let us know if there are problems hearing us or any other issues. I forgot to mention regarding Yarden’s input, it’s been a while since AI was released and the Co-Pilot is in the market. Some of you have experienced it, others perhaps didn’t get the chance. If you’d like to have another round of a trial, this is something that we can enable for you. Feel free to reach out and contact me, and I’ll help and assist you in doing that. It’s worth seeing because there are new features on that front, just as the platform is evolving. 

It’s very exciting to move to Yasmin, who has some very neat features to share with you. 

Yasmin: Yes, just making sure—sorry, I was on mute. Thank you, Gil. So thanks, Ohad. That was great content, and hopefully, I still have everyone’s attention. We’re going to share some things that we recently released and some things that are coming up. Someone also mentioned in the chat about the patch management dashboard, so I’m going to talk a little bit about that, and another recent development regarding local time zone support for automation profiles and integration that we are working on. So let’s get started. 

For the patch management dashboard, hopefully, you’ve all seen it. It’s released and has been out there for a while. We were trying to create a workspace to help you effectively manage all of your patching workflows and data in a focused and easy manner. The idea was to increase visibility and your efficiency so you can see where you are, what’s your current patching status, and take action from within that workspace along with viewing live reports. This allows you to focus and prioritize your patching tasks based on patch criticality or device types that you’re managing.

So what did we do? We have our brand new patch management workspace. You can see it on the main menu on the left side, labeled “Patch Management” with a nice new badge next to it. Everything should be available there. We have live reporting, so all of the patch information for online devices is updated once an hour at maximum. You can also see that information on the devices list, either under the patch management tab or the main devices list. There’s a new optional column you can add there so you can see when your devices were last scanned and how up-to-date the information is. We also added a new capability for bulk patch installation. If you go into the available patches, you can bulk install a missing patch on many devices that it’s available on and also queue patches for installation on offline devices. This is something that we had via the IT automation profiles, but now you can also do it for ad hoc patching. For example, if there’s a zero-day vulnerability and a new patch is released, you could easily see which devices this patch is already installed on and which devices this patch is missing on. If it’s something critical that you want to push out immediately, you can do that within the patching dashboard without waiting for automations or having to do it manually on each device. You would search for the patch, view all of the devices, select them, and install them in one go. 

I will say that this is still an initial version of the patch management dashboard. There was a lot of work and effort behind the scenes, but we’re also really looking forward to hearing your feedback and improving it and adding additional capabilities. If you haven’t seen it, there’s a little “Give Feedback” button at the top of the page. I’m personally looking at all of your responses, collecting your feedback and ideas, so that’s great. Please keep doing that and adding your feedback, and we’ll hopefully add additional capabilities down the line from the feedback that you’ve mentioned. If we click, we can see a short video of the dashboard. Just to explain some things here, the idea was to show you an overall status of your compliance, how many devices are up-to-date out of all the devices, and you can see it based on device type. There are a lot of filters that you can use to focus on what matters to you. Here, I’m going to filter online devices.

Because that’s the updated information, I can take action on these devices. Say you’re interested in making sure that you’re covered for all critical patches or different classifications and categories of patches. You can go to the list of devices and focus on specific devices and update them. We’ve also added sorting on the available patches count, which is something that came from our customers—great feedback. You can also view specific patches, either installed or missing patches, and here we can bulk deploy them with the queuing for offline devices capability.

Things that we’re planning on adding include the “update all” functionality, which came up from user feedback, and also reporting on third-party software patching. So there’s a lot more still to come. I think this is a great start, and we’re seeing some great reactions and adoption. Just let us know if anything else comes up, and if you haven’t yet, please explore this page.

Let’s move on to the next item, also related to patching and maintenance. We’re very focused on patching as we understand that it’s a big part of your work and something that requires sometimes a lot of manual work. We want to help you make the most out of the automations. For teams that are managing global sites or global users, it was quite cumbersome to manage different automation schedules for different locations. So we’ve added the option to schedule automation profiles to run based on the device’s local time, not only the account time like it exists now. For example, if you have maintenance or patching windows that run once a week during the night and you manage global teams or global sites, you no longer need to create different profiles to manage different schedules for each location. One profile can be applied for all of the different sites. If, for example, we set it to run at 1:00 a.m., it will run at 1:00 a.m. based on the device’s time. This will simplify the automation management and minimize end-user disruption in case there are any mistakes or errors, making sure that something doesn’t happen when you didn’t plan. Darren, I see you’re excited about that—great, I am as well. 

This is currently in beta, so if you want to move to our beta environment, you can reach out to support and they’ll be happy to transfer you. Maybe a few words about that: it’s an environment where we release all the new features first before they are released to production. If you want to join, we’re happy to put you on that environment, but it will be available for everyone very soon. 

Gil, if you click, we can show what that looks like. Under the automation profiles on the left side, we have the execution settings. Now you can select to schedule the automation profile to run based on the device time. We’ve actually added a new field on the agent console that will show you the agent time zone, so you could check that out and see it there. It shows you the device time zone, and also on the reports for the automation execution, there will be an indication for each execution on which time zone it ran and the devices that were under that time zone. If you’re in beta or want to be in beta, you can try that out. If not, it should be available for everyone in the next few weeks, and hopefully, it will make your operations a bit smoother. 

For the next item, which is also patching related—lots of focus on patch management—we are working to integrate with Winget for software deployment and patching. In addition to what we offer today with Chocolatey for Windows, we also have Homebrew for Mac and the private repository for custom software deployment. We’re going to add an additional source for Windows package management with Winget, which is the Microsoft repository, to ensure consistent and secure software installation and patching. Winget has gained a lot of popularity in the past few years, and packages are Microsoft-approved. It’s a very easy and useful tool to manage software across organizations, and we want to provide another solution alongside Chocolatey. You’ll be able to use both. This will include all the software management capabilities that we have today, so you’ll be able to deploy packages to Windows devices with Winget, either through software bundles and automations or on specific devices ad hoc. The software bundles will be unified, so you’ll be able to add Winget, Chocolatey, and private repository software to a single bundle and make sure that all of the devices have all the software that you want. It will also be available through our customer portal with self-service actions that are available for our Co-Pilot users, and it will include third-party software patching using Winget. The idea is to make sure that we have the largest coverage possible for packages through a repository and for updates, so in case you run any vulnerability scanning, we’ll provide more coverage for more software and ensure your networks are secure. 

Sorry, I see there’s a bit of an issue with the presentation. It’s not yet in beta; it’s in development, but we will gradually release the capabilities to beta within the next month. This is also super exciting. I think we have a sneak peek of what this would look like. 

Gil, if you could click, thank you. One of the capabilities I’m showing here is for software deployment. We can see that I’m searching for a Zoom package and I’ve got different options. 

I can decide where I want to deploy Zoom from: the Chocolatey repository, my private repository where I uploaded a package, or Winget. This gives you many options and it’s also down to your preference. I know some users prefer Winget over Chocolatey or the other way around, so that will be available. 

If we do another click, please. Through the automation profiles, there will be a new section for Winget updates, so you can update all packages through Winget to make sure all of your packages are patched and up-to-date. If you want to maintain certain packages on certain versions, you can exclude them as you can with Chocolatey and Homebrew. 

I think that’s all for me for now. There’s a lot more coming; we didn’t cover everything. I urge everyone to stay up to date with our release notes, and I think Gil’s doing a great job with posting everything on the community. So again, there’ll be more things, and we’re excited to hear your ideas and feedback. Thank you. 

Gil: Yes, I’m going to stop sharing the screen, and we are really happy to see your questions. Just having a look at those, I’ll start from the beginning ones.
Can a photo be attached to the assets page? Ohad, that’s in your area. Ohad: This is a great question. The answer is yes, but not in the first phase. We are going to add support for this based on other users’ feedback as well. This is something planned for 2025 to be added. 

Amazing. Nice to see that we’re going with images as well. Will there be an ability to send an agreement to the user with that asset? 

Ohad: This is great feedback. We haven’t scoped this yet, so this is exactly why this town hall is important—learning from you guys. I’m going to take this, look into it deeply, and update once we have more information. 

Gil: Some of the questions that we got… Sorry, I’m just going through them. From Vasili… No, sorry, we just went through that. John asked about the patch dashboard and scheduling relative to Patch Tuesdays. For example, running on the second Tuesday of each month plus six days—is this something that… 

Yasmin: Yes, this has come up. We understand the need and we do plan on adding this. I can’t commit to a time frame at the moment because we have a lot of patching improvements, and we’re prioritizing them now towards next year. But there will be a lot of patching improvements next year, so this is on my radar for sure. 

Gil: Right. Also in the area of patching, and Deep, nice to see you again. You wrote about enhancements in reporting. I think it would be helpful if you can give us an example or two, and then I’d be happy to get back to the question. 

Yasmin: Sure. We’ve added all of the software information to our advanced reports, and we’ve also created a preset. If you go under the advanced reports section, there’s a software inventory preset that shows all of the software packages, versions, and if there are any updates for installed software. That’s a preset that’s available for Growth tier and higher. For Power and higher, you can also customize and build your own reports. We’ve added software installation feedback and failure feedback to our recent processes and to the agent activity log on the new agent page, which I hope you’ve all seen. We’re also enhancing the IT automation feedback report, so we’re trying to provide as much visibility as possible. But I’m happy to understand what you need specifically. 

Gil: I also want to clarify that even if we don’t have the time to answer everything here, since some of the questions require a deeper look, we’ll be aggregating all of them. That way, we can release more concise answers for everything in some takeaway that I’ll do in the community later on. 

Tom and Brian, yes, we’ll be sharing takeaways from this webinar and we’ll cover all the different parts. Another question about the API: Ohad, will the API be read-only for the assets? 

Ohad: Great question. By the end of 2025, we’ll have the full CRUD API. For Q1, we will have the read-only API, meaning you can get assets. 

Gil: Amazing. I know, by the way, that API is a huge topic in the community. There are lots of threads about it, so it’s something that we value and want to promote as we move on.

Let’s see. Are we able to install custom packages using scripts and have that as a software bundle? Also from Vasili. 

Yasmin: So, at the moment, we have our private repository. You can integrate with external repositories to host packages and deploy them through Atera using the software bundles. That’s one option. Another option is to attach executables as scripts through the automation profiles. So those are two options to deploy custom software.

Gil: Thank you. Some of the questions or remarks were more in the areas of feature requests. I’d like to read them out loud so everyone is aware of them, but I’m not sure this is exactly when we can address them. I do want to give them the spotlight. Patch dashboard is brilliant, Yasmin, but we really need to schedule relative to Patch Tuesday. Oh, sorry, I mentioned that earlier on. There was also a low-priority feature from Gabe: coordinating patch installation with user schedules, as in they can choose a time slot, create a calendar item for them, and automate patching based on that time. This is for more executives who come and go at unusual hours. 

Yasmin: I also want to remind everyone that we have our features board that everyone can access, and we take it very seriously—all of us on the product side. You can go in, vote for existing feature requests, and also suggest additional features like the ones you just mentioned. It’s great if we have everything there because we can review it. We also communicate and update when things are released, and you get automatic emails. That helps you stay up to date and you can also see what other people requested. I’m sure there are some things that you could find that could be really nice and helpful for your day-to-day work. It’s a great chance to bring up things that you want and see if others connect, and it helps us prioritize things too.

Gil: Great. We still have a few more minutes and I want to maximize our time. Ohad and all of the PMs discussed a bit about beta testing. If you don’t know this program and you’re not aware of it, it really is an opportunity to test things as we release them for select customers. We usually ask them for feedback to know how they work with it, what their usage is, and if there are different bugs or things that don’t meet their expectations. I’m going to share a survey that will allow you to indicate both regarding this webinar what you thought of it, what you would like to see for our next community town hall, and also the opportunity to let us know which of these areas are relevant for your beta testing needs. I do want to indicate that this is for qualified users, meaning that we have to check and make sure that your usage is relevant and the metrics are applicable to participate. But we’re looking for you, we want your feedback, and all of the PMs said they’re thirsty for it—they’re looking for what you have to say.

The survey should be launched in your email when we finish up and send it out. Just one last thing that I want to share: as we mentioned the beta testing program, we have a little something for Black Friday, or Pink Friday as we like to call it. There’s also a code available for you if you like some of the stuff on our store. You’re welcome to have a look, and even better yet, send this to your HR and ask them if they have something nice that they want to plan for you. That’s how we do things here.

Really, thank you so much for joining us today. It’s the first town hall, and you guys being here gives us a lot of support that this is something we should do again. It was really nice, and a huge round of thanks to the PMs for giving their time. They really care about what you have to say and think. We’re in constant contact over the things that you’re sharing with me. Thank you so much for taking the time, participating, and preparing all the materials for us. It was really fun. Thank you, guys, and I’ll see you at the forums. Have a great night and I’ll see you soon. 

Participants: Thank you!