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.]]

KKerezman last won the day on May 4

KKerezman had the most liked content!

Community Reputation

3 Neutral

My Information

  • Location
    Hillsboro OR USA
  • Agent Count
    1500 - 2000 Agents

Converted

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You're welcome! Our EDF is populated by a script which runs this Powershell command: (Get-ItemProperty -Path ‘HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion’).CurrentBuild Then passes the results through a series of IF checks along the lines of "If @powershellresult@ NOT = 10240 THEN Jump To :Not1507, otherwise set EDF to 1507 and exit" and so forth. We just tack a new IF check on twice per year. The script gets run weekly against online Win10 endpoints to keep the EDF updated. This lets us do groupings and reports and so on.
  2. (...and then find a way to hack the UI to turn the online/offline flag indicator a different color, say blue for instance, *coughKaseyacough*) 😑
  3. Your mileage may almost certainly vary but for the sake of hopefully pointing you in a useful direction, I'll describe our current system. We imported and updated our old kludgey way of doing it from Kaseya (we migrated after the end of last calendar year). The script goes a bit like this: Check for and deploy 7-Zip if needed. (The standalone executable can't do ISOs.) Download the ISO. (We're storing it at... ugh... SharePoint at the moment. Hey, it works.) Create working folder and extract ISO into folder. Make sure the setup.exe is actually present and bail with a detailed email to the tech if it isn't, since clearly something went horribly awry with the preceding steps. Pop up a "please don't turn off your system, you asked for this" message. Run 'path\to\setup.exe /auto upgrade /ShowOOBE none /quiet' And yes, there's a cleanup script to be run afterward. If the tech has a ticket to be doing this at all, they should be tidying up as part of that ticket. As to how we deal with feature updates to Win10 logistically, it's a matter of looking through the search we built looking for likely candidates, then coordinating time with the clients for access to the relevant machines. (The search is centered on an EDF which we populate with the build number.) It may not be fully automated but so far it's been working moderately well.
  4. We migrated ~2500 endpoints from Kaseya to Automate over the start of the year going into mid-springtime. I have a few thoughts, which may or may not match up with anyone else's, so... grain of salt, I guess. Make the heck sure that you have consultation hours banked with ConnectWise. You will have questions, you want a consultant available who can get you answers. We did this and it's 95% of the reason why we have a functional system now. (I mean, I'm good but adjusting to that-which-was-LabTech was a thing and a half.) Be prepared to disable all kinds of built-in monitoring systems. Most of them are so, so noisy. Also be prepared to dig through the archives of this here forum in search of how to edit the built-in searches and monitors and scripts to deal with things like, oh, Automate building semi-bespoke disk space monitors for attached USB drives. Ahem. Learn the EDF (custom fields)/search/group triumverate. It is where the bulk of your successful automation efforts will take place, and it's ridiculously powerful and good. When asked, I reply that it's my favorite thing about having done the migration. (Second-favorite? Control, formerly-known-as-ScreenConnect.) Sean, above, makes a case for having some SQL knowledge. Which is good, but if you're cloud-hosted by CW themselves you'll have... limited access to the actual SQL server. We have generally made do without getting into the SQL weeds. Could we be doing better if we were SQL gurus? I don't doubt it. But don't feel like you're going to be hamstrung without it. User permissions are super duper weird. In order to grant an account the ability to change an endpoint's location we had to give their class access to... I think it was one of the Reporting tickyboxes? Whatever, it was super counter-intuitive. Other than the rickety agent-deployment process itself, permissions are the most frustrating thing in Automate. Think through every possible outcome when building your scripts, and leave breadcrumbs (log entries with shell command results, mostly) for "well this shouldn't have happened" situations. Later!You will thank Today!You when troubleshooting why your script didn't do what you thought it would do. Scripts have permissions. Make sure that user classes that don't need access to the more dangerous scripts (like ones that perform queries against the live Automate database) aren't available to your rank-and-file techs, let alone any high-end clients you may decide to allow any kind of Automate access. That'll do for now, I suppose.
  5. Yeah, un-retiring has been a joke here. I ended up in a two-hour support chat session and the baffled tech basically punted to "rip out everything on the PC and start over." (We could run scripts and send commands but NOTHING to do with the ScreenConnect piece would work. Un-and-re-installing had no useful effect. Support had us play around in the relevant parts of the registry and everything.)
  6. 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!
  7. 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.
  8. 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.
  9. 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?
  10. 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!
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. 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.
×
×
  • Create New...