Jump to content

toril

Members
  • Content Count

    49
  • Joined

  • Last visited

  • Days Won

    1

toril last won the day on May 20

toril had the most liked content!

Community Reputation

2 Neutral

My Information

  • Agent Count
    2000 - 3000 Agents

Converted

Recent Profile Visitors

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

  1. Won't these options do just what you are asking?
  2. Are you sure that the domain admin account had never logged in? I ask because I think I remember hearing of issues with admin accounts not having logged in because there was no local user profile folder. Could your install maybe be failing because of a lack of the \Users\username\AppData folder?
  3. And apparently that was only really needed if you used the network probes to do agent deployment.
  4. Yes, probes = network probes, same thing.
  5. @MGreen just shared this, which helps expain:
  6. From what I understand from those in the know, like @MGreen and @DarrenWhite99, I'd say to make sure the agent is reporting in all it's important info, such as BIOS info, services, storage, etc. If not, then reinstall the agent and verify the new install reports in as it should. The idea behind 2a, as I understood it, was that the oldsystempassword could still be used for new agent installs without exposing the current system password.
  7. The following information was taken from the MSPGeek Slack discussion on 6/22/2020 in the #cw-automate channel: 1. Remove your "non-functional" agents from the system2. Change system password from the Control Center (not directly in the DB) and document for later use as oldsystempassword2a. Embed oldsystempassword into future uses of LTPosh as server password (server password will now be required when using LTPoSh)3. Change system password again, this will be the production system password4. If you have probes you'll have to be reinstall it on the applicable agentsStep 4 expanded is:4a. uninstall the probe from the site4b. reinstall the agent with the new password4c. deploy probeAnd keep those system passwords, old and new, super secure.
  8. Afraid I've not done that exact switch, but we did go from Vipre to Bitdefender GravityZone a few years ago. In our case we had the Vipre solution that included Vipre uninstall scripts, then I developed install scripts using this old post as a guide: That's not exactly an easy or quick setup though, and it really helps to have a handle on Automate scripting. At the time we weren't happy with the BD plugin for Automate, so this was best for us. You don't mention if you have the Bitdefender Solution for Automate installed, but if not, you might want to take a look at it. I know it's been updated since the days we decided against it, so it may be a lot better now. In theory, you could use your Ncentral console to issue uninstall commands (presuming that is an option), then use the BD plugin to do the install. Here's the BD documentation on that Automate plugin: https://download.bitdefender.com/business/Labtech/Bitdefender_GravityZone_ConnectWiseAutomateIntegrationGuide_enUS.pdf
  9. I think the monitor @WesleyNZ referenced is for when your network probe detects a new PC on the network. https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/165/050/080#Automate
  10. Does the code below help? It uses the DATE_SUB() function to subtract 2 weeks from NOW(). I use something a bit similar in a script that runs on our Automate server every Monday to collect info like what is listed below. SELECT c.ComputerID, c.Name AS ComputerName, c.ClientID, cl.Name AS ClientName, c.LocationID, l.Name AS LocationName, c.DateAdded, c.Domain, c.OS, c.BiosMFG, c.BiosName, c.BiosFlash, c.BiosVer, c.LastContact, c.LocalAddress, c.MAC from (computers c JOIN clients cl ON c.ClientID = cl.ClientID) JOIN locations l ON c.LocationID = l.LocationID WHERE DateAdded > DATE_SUB(NOW(), interval 2 week)
  11. We put the workgrouped agents into their own separate location that uses our local admin creds for that client.
  12. Yes, that's what I was told. We were also having issues of some configurations not syncing, but the problems were VERY inconsistent. Some clients would sync up fine, others were just failing to update quantities under additions, and still a few others were syncing quantities but not creating configurations. The prorate checkbox was the first fix I was given, and while it fixed the issue for some of the sync problems, it didn't fix them all. (BTW, the effected clients were not all using the same agreement type, so the problem wasn't restricted to just one agreement type.) From my support chat on 10/9/2019: While that suggestion helped it didn't fix all my problems so I had them keep the ticket open. During a later phone call with a different support tech I mentioned the prorate again, and again was told that information was correct. If your agreement has an open invoice, then the prorate checkbox doesn't matter, but if there is no open invoice and you want additions to update, you must prorate. I guess the bottom line is if the configuration and quantities sync isn't working, there is no open invoice, and you've confirmed the Billing Information section of the agreement is populated, then try prorating the agreement and syncing again.
  13. I was also told that in addition to the Billing information section, if you want your additions to be updated whether or not the agreement has an open invoice, then the agreement must have the Prorate box checked.
  14. Hope this helps some... To me this kind of depends on what you want to consider oob. If you mean a clean Automate install with only Ignite, then the most useful scripts are probably the ones you are already familiar with, like the scripts for daily agent maintenance and offline server diagnostics/ticketing. (Although imho even those need customized for your company's preferences.) However, I think that if you take oob to include the plugins that you should get from the Solution Center for whatever products your company uses, then you'll probably get a lot more scripts/monitors/etc that will be more useful. Example, the StorageCraft Backup plugin includes the scripts needed to install/uninstall ShadowProtect and ImageManager, as well as monitors to alert to issues with those products. Again, to me this depends on what plugins you use. Backup/DR products can be so varied in how they work, I don't think there could be one way to check them all. The network probe has been completely rewritten, so you may have more success with it now than before. (Full disclosure, I haven't used it yet, but have heard some good things.) GPOs still work, of course, but if you already have a way to run a powershell command on your PCs, then you may find the Install-LTService function of LTPosh helpful. I sure do. The Control Center has a completely different look/feel then it used to, and, like most UI overhauls, it has good points and drawbacks. Some other new stuff that we use all the time: the new Patch Manager gives you more control over patching, including the ability to release patches is stages the new Report Manager is a little easier to design custom reports the Web Control Center has most of the agent info available in a web browser, which is pretty handy for techs (they're also adding more into that interface with every patch) speaking of patches, they release new patches about once a month or so now There's always something they are working on, such as adding the script editor the Web Control Center
  15. If I were doing this, I'd probably create an EDF checkbox and have both groups populate based on whether that EDF was checked or not.
×
×
  • Create New...