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

dustinriley last won the day on January 11 2018

dustinriley had the most liked content!

Community Reputation

6 Neutral

My Information

  • Location
    Louisville, KY
  • Agent Count
    1500+

Converted

Recent Profile Visitors

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

  1. My contacts also said that a different port shouldn't be an issue as long as Automate supports using a different port. So that's not of much help to you, sadly.
  2. There's no plugins that I'm aware of that will accomplish this. However, there's a PowerShell module from Microsoft for Group Policy that can probably be used with Labtech scripting to do what you're wanting. https://docs.microsoft.com/en-us/powershell/module/grouppolicy/
  3. The ITGlue documentation for Automate integration doesn't specifically state they support using a custom port number. I'm going to go out on a limb here and say that's what the problem is. I'm reaching out to some contacts I have to see if I can get an answer for you.
  4. Maybe this is well known, but I haven't seen anything about it, so I figured I would share our findings. The Automate web console has Missile Command hidden in it. You can access it by entering the Konami code (Up, Up, Down, Down, Left, Right, Left, Right, B, A).
  5. How long have you been using CWA12? We've been using it in production for several months now with 1800+ agents. (The Leroy Jenkins approach to Automate) What problems if any were encountered DURING the upgrade. How was it resolved? (Or is it still an issue?) We had no issues with the upgrade, it performed just as a normal monthly patch would. We already had an SSL certificate installed and the new Patch Manager enabled. What problems if any were encountered POST upgrade. How was is resolved? (Or is it still an issue?) We didn't have any issues post upgrade. What is your feedback on the changes? What do you like best/worst? The new UI for the Control Center is a great improvement, especially the Computer List, with column filtering and choosing. The speed keeps getting better just as it had been with 11. With that being said there are still screens that will hang for long periods, but that's nothing new and I'm sure is being tweaked more. What feedback did you get from your other users/techs? The overall feedback has been positive from the entire organization. Only issues have been locating where some things are now, especially with users who use CWA less.
  6. I included checks into the script to check for the existence of each of the three files before attempting to creating. But yea that's a great idea, creating a remote monitor would be pretty spiffy and easy to create to check for the existence of the three files and if any don't exist call the script.
  7. Based on this BleepingComputer article, this Automate script vaccinates machines against Petya (Not Petya) by creating three files in the Windows directory and setting them to read only. https://github.com/dustinriley/cw-automate-scripts/blob/master/Malware/Petya%20(Not%20Petya)%20Vaccine.xml
  8. Beginning Plugin development for Automate can be a daunting task to someone just starting out, as many of us know. I'm currently working on producing example Automate plugin examples written in C# and posting them to GitHub to hopefully help get more people up and going on developing their own plugins. Computer Screen Plugin Example: https://github.com/dustinriley/labtech-plugin-computer Menu Plugin Example: https://github.com/dustinriley/labtech-plugin-menu
  9. Moved to: http://www.labtechgeek.com/forum/viewtopic.php?f=13&p=21616#p21616 Delete thread.
  10. 1. Honestly, I think relying on proven third party Two Factor Authentication methods is a better way for them to go. It's proven and likely more secure. Duo would be the one I'd look into, as the ScreenConnect team is supposedly looking to add it to that product. The missing support would be for ConnectWise, as I'm not sure if they've added it to that roadmap yet. Would I like them to support more options? Yes that would be preferable. 2. Yes this is a huge pain that LT doesn't authenticate against LDAP directly, instead it simply does a sync periodically and authenticates against that sync. 3. Someone can correct me if I am wrong, but I don't believe there is a way to limit the Control Center to your internal network only. 4. I would suggest creating your own User Classes in LT and not giving everyone global admin rights especially if you don't want everyone being able to see passwords. You might also look into PassPortal which has an LT plugin and granular control on password visibility as well as an audit trail. 5. If you're referring to the LT_SYSTEM_PASSWORD in the install shell script, that isn't the root password for the LT database. It's the server password for communication between agents and the server. This password is visible in the Windows Agent EXE installer as well as in the registry of Windows LT agents.
  11. You'll also want to test for SPX 6.5+ as it's changed registry key locations. Here's an alternate way of getting the installed versions of installed StorageCraft products using PowerShell: ImageManager: (Get-Item ((Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Services\StorageCraft ImageManager").ImagePath).Replace('"', '') | Select -ExpandProperty VersionInfo).ProductVersion ShadowProtect 5.x (and possibly older, don't have any to test on): (Get-Item ((Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Services\ShadowProtectSvc").ImagePath).Replace('"', '') | Select -ExpandProperty VersionInfo).ProductVersion ShadowProtect SPX (pre 6.5): (Get-ItemProperty "HKLM:\SOFTWARE\StorageCraft\spx").InstallVersion ShadowProtect SPX (6.5+): (Get-ItemProperty "HKLM:\SOFTWARE\StorageCraft Technology Corporation\spx").InstalledVersion
  12. The following is present if ImageManager 7+ is installed, however it doesn't get you the software version. HKLM\SOFTWARE\StorageCraft Technology Corporation\ImageManager The role definition for ImageManager uses the following PowerShell command to get the version installed: (Get-Item 'C:\Program Files (x86)\StorageCraft\ImageManager\ImageManager.exe' | Select -ExpandProperty VersionInfo).ProductVersion
  13. Starting with ShadowProtect SPX 6.5, StorageCraft changed the registry keys for the software. ShadowProtect SPX (Pre-6.5) HKLM\SOFTWARE\StorageCraft\spx\InstallVersion ShadowProtect SPX (6.5+) HKLM\SOFTWARE\StorageCraft Technology Corporation\spx\InstalledVersion Before the Role Definitions get updated you can potentially do something like this to the role definition for SPX, I haven't tested this yet so it may not be entirely correct but it should point you in the right direction. {%_or|{%-HKLM\SOFTWARE\StorageCraft\spx:InstallVersion-%}|{%-HKLM\SOFTWARE\StorageCraft Technology Corporation\spx:InstalledVersion-%}_%}
×
×
  • Create New...