Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

Everything posted by KKerezman

  1. Our main use of Manage's Configurations is for billing purposes and as a waypoint along the way to becoming an IT Glue Configuration. All a Manage Configuration is, is just a way to document assets in that environment. Before ITG came along it was where we had techs create most of the non-RMM-provided assets (printers, routers, switches, NAS/SAN units, etc). If you want to sync more than just the built-in Managed Server and Managed Workstation types, you'll want to do some reading & planning on what other kinds of devices you want to sync, etc. (We have Types for various devices that we sync to IT Glue, tagged with "-ITG" in the name for easy spotting. YMMV, etc.) In order to control which clients' agents & devices become Configurations, you want to be in the Agreement Mapping section of the Manage Plugin in Automate. Build an Asset Template (button on the bottom of that display) for the agreement type of that client, decide what Automate asset type becomes which kind of Manage configuration type (and what product in Manage), and select that template in the drop-down next to that client in the list. Without an assigned template, the plugin doesn't have any way to know what to do with the assets so it just won't. So only the clients you've selected a template for will get sync'd. There's one big honking-huge configuring-the-Manage-plugin doc here: https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/080/040/020/040 I just went through the process of getting devices out of the Network Probes into Manage/ITG so I might be able to answer certain types of questions, but I'm far from an expert at this point!
  2. You can't edit Agent Monitor Creation - Disk* but you can copy it, then just edit the step in the Agent Monitor Creation* script that runs Agent Monitor Creation - Disk* to run your copy instead.
  3. Well of course I was coming at this the long way 'round. Adding the Client Name column to your instructions got me what I needed. (I didn't mention the Client Name requirement in the original post because I hadn't even gotten as far as the Computer Name, and figured if I could solve that then the client info would be solvable through a similar method.) May Washu-sama bless you and keep you, good sir.
  4. Hello, neighbors. I'm still only a few months into this Automate experience. I spent the morning going over https://www.gavsto.com/labtech-report-center/ (missing images and all) as well as what I can grok of the DevExpress docs online. All this so I can make a single-table report to show which machines have what CrashPlan versions installed. (Can this be done in a Search? KIND OF, but as soon as you do Application Match you lose the ability to get anything under that match group into the Excel results, grr, argh. Can it be done in SQL? Maybe but I'm not a SQL guy and we're Hosted so our access to SQL is very limited. Can it be done in a Dataview? Boy wouldn't a non-wonky Dataview editor be nice!) Anyway: Instead of adding new forehead-shaped dents to my wall, I'm here to see if anyone can nudge me in the right direction. All I really want, at the moment, is to make it so I can get the computer name to match up to a computer ID in my little software installed-version table. I have two Queries in my Data Source Editor: CrashPlan Software - Source: 'software', Where SQL: Name like '%CrashPlan%', Included columns: ComputerID, Name, Version, DateInstalled. Basically this does work! And if I didn't mind looking up agent ID numbers I wouldn't need to tie into the other table, but I do mind so I do need the other table. Client Computers - Source: 'computers', Included columns: ComputerID, Name, ClientID. I have a parent/child relationship tied to the ComputerID field. Great, but no matter what I do, regardless of which I make the Parent and which the Child, when I try to bring in computers.Name and/or computers.ClientID I get either the first result repeated or blank results. Is this just brokenness in the Report Designer or am I fundamentally misunderstanding how this is supposed to work?
  5. Darren, Sorry about the delay, I apparently didn't set myself to get notified on replies. Good questions! The users in question are assigned to All Clients. The Location's "Deployment and Defaults" has been left Not Selected. (Our migration consultant stressed making sure there's a Login for Admin Access selected and that the Default template is chosen, but nothing about the Default Group For New Agents option. If we're missing a best-practice there, I'm all ears.) Since we're hosted I can't really check the server to see if it's having issues building the searches/groups. But our techs are definitely set to All Clients, which one would think would give them what they need. I might try enabling Show All under Computers in the User Class Manager, though I feel like that might bite me in the backside if we need to carve out a client out from their visibility later on. Thanks for the info!
  6. For what little it's worth: We've tried the Reload Cache thing, and it only works sometimes. We also have the techs close out and re-launch Control Center, which also only works sometimes. We've pestered our migration consultant, who hasn't yet come back with anything useful. It's... rather annoying, especially coming from the "the installer always Just Works and the agent is useful right away" land of Kaseya. Sigh.
  7. You're most welcome! After a few weeks with this in production (a modified copy of it is run every few hours against online CrashPlan-installed agents and emails Backup Radar in their "generic" format), I should note that if CP is installed "per user" into the AppData hierarchy this script basically won't work. (It will do the thing in the first # point above, bailing when it doesn't find the log file.) You're free to add in some "find where it's installed" logic if you want, but we just decided to reinstall those endpoints "properly" instead. We're fussbudgets that way.
  8. I'm probably going to end up building a script around the idea of checking NLA's status and kicking the service, and scheduling that script to run a few times per day/night. My bit of PowerShell that'll determine if the service needs kicking: Get-WmiObject MSFT_NetConnectionProfile -Namespace root/StandardCimv2 | Select -ExpandProperty NetworkCategory If the result is '2' then it's in "domain" mode and the service can be left alone. Hope that helps a bit.
  9. The Computer Types search "Computers - Windows Laptop" could be used to build a Group, which could then only run your agent install script against members of that group. That'd probably be the easiest way.
  10. Dude, you just saved me an ongoing headache of "save %shellresult% to file, upload file, attach file to email" to get around the problem of badly-formatted console command output, THANK YOU.
  11. I needed a way to pull the list of "failed" files from the gigantic CrashPlan client logs, and to do so without downloading several gigs of logs locally and eyeballing it myself. So, coupled with the "opportunity" to learn more about how to wrangle things in PowerShell, I have created the attached TESTING script. In a nutshell, it performs the following steps: Checks if the backup_files.log.0 exists in the CP log directory under ProgramData and emails the tech who ran the script a DIR of the directory if it's missing (then bails). Makes a "today's date" variable in a format matching what's in the log. Parses log looking for lines with today's date, twice. Once to pull the timestamp of the latest job run, once to pull the number of failed files in that job. Generates a "working" (just the desired date/time lines) copy of the log file in %tempdir% and parses that for the lines with the actual failed files. (Upon later runs, the working file is checked for and deleted first.) Emails the resulting info to the tech who ran the script. Note that if you do play with this, you should obviously season it to taste. I merely figured somebody somewhere might get some value out of the day I have just spent chasing down syntax errors... CrashPlan Job Log Reporter (TESTING).xml
  12. Bill, Some Googling has led me to a lot of not-terribly-useful information but also one thing that MIGHT be worth a look...: http://kolbi.cz/blog/2017/11/10/setdefaultbrowser-set-the-default-browser-per-user-on-windows-10-and-server-2016-build-1607/ I recommend experimentation. I believe that you'll need to run whatever command/utility in the user's context since browser preference is a per-user thing. Good luck!
  13. Dattos have saved our clients' bacon over and over (and thus our agreements with said clients). StorageCraft has been a decent solution for clients who don't want to invest in the full Datto experience, BUT note that their new version 6.8 of the SPX product is basically broken right now. Our Acronis experience is mainly through what's left of our Kaseya environment and... meh.
  14. We're using a mix of products, though we're looking to whittle that down. My preferred option is the Datto product-formerly-known-as-Backupify solution.
  15. Jason, I'm asking the obvious questions because I'm still new at the Automate way of things: Are your examples a pair of one-liner scripts you'd run as part of Groups populated by an Auto-Join Search looking for agents offline more than 60/90 days? Thanks!
  16. Yeah, whatever genius at Microsoft decided that servers should create those per-user services at login needs to be horsewhipped. Anyway! We ended up making a copy of the "SVC - Auto Services Stopped" internal monitor with this tacked onto the end of the Configuration directive: AND Services.name not like '%OneSyncSvc%' We disabled the stock one and enabled our copy in our Servers 24x7 service plan group, and voila. Seems to be working. (We don't have auto-services monitoring enabled at all for workstations, because ain't nobody got that kind of free time.)
  17. Yeah, an EDF ("Group B Member" or whatever) sounds like an infinitely easier way to make this work. "IsServer = true, GroupBMember = false" is all the search you need for Group A at that point, especially since you say you're manually adding machines to Group B anyway. If you don't want to open up a bunch of servers in the Computer Management view one at a time to set the EDF, make a quick one-liner offline script to flip that toggle, then you can multi-select servers and run that.
  18. We do, in fact, have the desktop CC client running on our RDS for non-administrative users. It's not fun, but for our Mac guys who have been left in the lurch by the migration to Automate... it's what we've gotta do. Once we get the software running (a lot of "run as Administrator" during initial setup, and every time there's a patch update to the client) it seems to behave okay. It's mostly a case of run-as-Administrator until you don't need to use run-as-Administrator to get in anymore as a local admin account, at which point non-admin users seem to be able to run it again. Yeah, that's a bit confusingly worded, sorry.
  19. We're only using CloudBerry for one specific client with gigantic data storage/retention needs. Luckily that client's situation is outside of my scope of responsibilities... at least for now.
  20. Not an expert, but coming off of one RMM and into another RMM, my general impression is that basically you're either relying on a Microsoft system (WUA) to get your patch info & installation done, or you're relying on a Microsoft system (WSUS) to get your patch info and... you get the idea. Kaseya tried to do the "we're going to maintain our own DB and shut out WUA" trick, which was unwieldy as heck AND basically became untenable once MS switched a lot of patches to "Internet install only." Eventually they punted to more-or-less what Automate's doing (albeit not nearly as well), which is just querying and triggering actions via WUA. It's Microsoft's world, we just try to get by in it.
  21. We've been a Sophos AV shop for years and years now. I love the product, kind of hate the company. When we get protection working on a machine it tends to stay clean. It's keeping things updated and under control that's been a problem. We started with the Enterprise Console in an MSP mode (which almost nobody at Sophos Support understood, so yes I had to educate them on their own product every time we opened a ticket), and now we're migrating clients to Central w/ the HitmanPro/InterceptX feature. The thing about Central is, if you use the multi-tenant model client-by-client, there is no way to push one policy to all clients AND if you goof and use the wrong installer token at the wrong client, you get to fully uninstall and reinstall to get it into the proper tenant. On the upside, the Sophos Central "solution" in Automate does a rather good job of handling Central deployment so as long as you onboard the machine into the right Client\Location you should be fine. And that's my two farthings' worth.
  22. Just ran into this with one of our client agent installs. First machine out of over 1600 to exhibit this behavior. Uninstalling the agent, downloading the cert and using the command line above to import it, then reinstalling the agent package worked perfectly. Thanks to everyone in this thread for your work!
×
×
  • Create New...