Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. Hello @Rafe Spaulding - I am a little new to Labtech/Automate and found your post and scripts extremely useful, so thank you for that. I am having issues getting Shell to open setup.exe with it’s switches? It looks like it actually runs it as a process but doesn’t ever go through or do anything. Is there some kinda tip to run .exe’s in Shell? I have tried multiple ways around this like Execute Script as Batch or opening an existing .bat with no luck!
  3. Last week
  4. I created a PowerShell script that accomplishes what you are looking for. It has to be run from a domain controller or computer with ActiveDirectory module loaded. https://github.com/Braingears/PowerShell/blob/master/Create%20Domain%20User%20with%20Domain%20Admin%20Rights/CreateDomainUserWithDomainAdminRights.ps1
  5. Hey all, I'm re-hashing an older conversation from here: I'm looking for the error and warnings and ID's for the event log source from "Cissesrv", "HP Smart Array", "Smart Array Events", "HP", "NIC", and any of the other HPE specific ones. I'm trying to improve our list of Blacklisted Events to better monitor our clients HPE Servers, so far I've had to add a bunch for "Smart Array Events" and "ServeRAID Manager Agent" and one for Dell's "MR_MONITOR" that isn't included in Automates standard set of Event Blacklist. I'm happy to share all that I have in our Event Blacklist. Thanks, Ryan
  6. It's passed the two week mark and there are no signs of any major bug or flaws, so I'm going to go ahead and greenlight it.
  7. Hey all, I'm more comfy as a redditor, so I made the post to the labtech subreddit, but I wanted to crosspost here to make sure it gets the attention of anyone who might appreciate this. I got a lot of good info out of old posts about dataviews on the mspgeek forums (thanks!). Basically, I made a custom dataview which can be used as a mostly full replacement for 2019 Automate's "Browse" interface. It provides a lot of additional data in a more accessible way. More discussion is here: https://www.reddit.com/r/labtech/comments/d6wgwp/how_to_make_labtech_v2019_more_functional/ And the actual insert statement is here: https://pastebin.com/VR9QWhw7 Enjoy! PS: I also posted this guide on how to successfully upgrade from 10.5 to 2019, and a lot of what made that possible was from comments here and on the labtech reddit, so hopefully that also helps anyone else who needs it in the future, and thanks!
  8. Thanks for the responses guys, as expected 3 different way to accomplish 1 thing! In my view that's another selling point though, more flexibility and always a way to get to end goal, even if sometimes a little more long winded that one might like. Thanks Hoe.
  9. Hi @Aenabs We've still yet to achieve this, I've tried looking at possibly creating a script using the file download function to an internal server address, but with little success. I'm thinking next possibly to create an automate script using robocopy going forward to distribute the ISO but haven't had time to test it yet. Have you had any success?
  10. I am replacing this script with my new Install-Automate Functions that I've placed on GitHub: https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/175 CMD (as Admin) %windir%\system32\WindowsPowerShell\v1.0\powershell.exe -Command "Invoke-Expression(New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/Braingears/PowerShell/master/Automate-Module.ps1'); Install-Automate -Server 'YOURSERVER.DOMAIN.COM' -LocationID 2" PowerShell (as Admin) Invoke-Expression(New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/Braingears/PowerShell/master/Automate-Module.ps1'); Install-Automate -Server 'YOURSERVER.DOMAIN.COM' -LocationID 2 In ScreenConnect / Control #!ps #timeout=900000 #maxlength=9000000 Invoke-Expression(New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/Braingears/PowerShell/master/Automate-Module.ps1'); Install-Automate -Server 'YOURSERVER.DOMAIN.COM' -LocationID 2 Examples: # Install Automate Invoke-Expression(New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/Braingears/PowerShell/master/Automate-Module.ps1'); Install-Automate -Server 'YOURSERVER.DOMAIN.COM' -LocationID 2 -Transcript # Force Rip & Replace of Automate Agent Invoke-Expression(New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/Braingears/PowerShell/master/Automate-Module.ps1'); Install-Automate -Server 'YOURSERVER.DOMAIN.COM' -LocationID 2 -Force -Transcript # Check if Automate is installed and checking in Invoke-Expression(New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/Braingears/PowerShell/master/Automate-Module.ps1'); Confirm-Automate -Show # Show Automate registry key Invoke-Expression(New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/Braingears/PowerShell/master/Automate-Module.ps1'); Confirm-Automate -Raw Functions: Confirm-Automate Uninstall-Automate Install-Automate
  11. Deploying Agents: Use a Scheduled+Immediate task to make rollouts a breeze. Using the scheduled/immediate task means you don't have to wait for reboots to get the agent installed, can automatically reinstall if the agent is removed or cannot run, and has other benefits. Stash the .bat file and the Labtech.psm1 file on a dc under a folder under netlogon, setup group policy preferences to do the following: Use GPO Folder Security to create a base folder, secured from being written to by non-admins. Use GPP Folder preferences to create %systemdrive%\basefolder\AgentDeploy - Make it replace, and remove no longer applied. Use GPP File Preferences to copy \\%userdomain%\netlogon\AgentDeploy\*.* to %systemdrive%\basefolder\AgentDeploy if the AgentDeploy folder exists. Use GPP Scheduled Task preferences to create the immediate task to run the batch as SYSTEM from %systemdrive%\basefolder\AgentDeploy\agent.bat if the %systemdrive%\basefolder\AgentDeploy\agent.bat file exists. Do the same for a repeating task, say, running hourly, targeting only if the bat file exists. Make the item remove if no longer applied. That's a short version of what is in the post above, with some minor updates. The post above has attached files you can use as a base GPO and has the script that you can run. The batch file can specify the target location, so each client can be automatically setup in the right location. Don't use a GPO to deploy the MSI as a published app, that just doesn't work very well.
  12. If you have very little experience perhaps stick to the Exclusions Tab in your screenshot - it should do everything you're asking. its per computer there tho, not per group.
  13. If your "main site" is where your automate server lives (or VPN Tunnels included) then this is working as expected. Traffic doesn't hit the internet IP so it will show the firewall.
  14. Dashboard/Management/Outdated also shows all such agents, and one can right click to Force Update. I just check it every so often, especially a few days after a patch. (and don't have that monitor)
  15. They broke it a while back but fixed it a month later, saying they still don't support XP/2003 and it may stop working in the future. 2019.9/190.250 works on XP. Even if you install an older agent I don't know how you can prevent it from upgrading?
  16. On domains we often use a domain startup script, something like: if exist %windir%\ltsvc\ltsvc.exe goto :SKIPAGENT copy "\\domain\netlogon\path\Agent_Install.exe" %windir%\temp call %windir%\temp\Agent_Install.exe /q /wait :SKIPAGENT Can also be done with ltsilent.exe copied from the probe PC to have the new install drop into that customer/location. Either way it's probably a good idea to update the agent installer from time to time. Does the MSI installer still leave an entry in add/remove programs? That always kinda bothered me. Can also download via PowerShell: powershell -command "& { (New-Object Net.WebClient).DownloadFile('https://%LTServerHostname%/Labtech/Deployment.aspx', '%temp%\agent_install.exe') }" Generally the probe push has worked for us. Definitely not on workgroups as there is a bunch of setup required to run stuff over the network that domain admins/PCs already have. Probably 80-90% of the time on domains?
  17. It looks to me like the screen cap script step is using Shell to run a PowerShell command which isn't going to work. Try the PowerShell Command script function. We used msiexec.exe calling the various GUIDs in our system, e.g.: start /wait MsiExec.exe /X{0309AC01-330F-494C-B27D-58E297E4674F} /qn REBOOT=REALLYSUPRESS A search on that software using "related-software installed" with field "Uninstall" will show you the uninstall command line...ensure you use /x (uninstall) not /i (install). The command will "succeed" even if that program is not installed. I have read warnings previously about using "wmic product"...I emailed this to my staff a while ago about it: "The reason any command starting with "wmic product..." can take a long time is because for some silly reason it has Windows Installer run a "consistency check" a.k.a. "reconfiguration" on every installed product. So that could essentially mean a repair install, is run on any installed product where it thinks it is necessary, even if only one product is queried. It's been known to re-enable services, for example. " Take a look at the application event log when you run a wmic product command and you'll see what it touches.
  18. Interested to see if you got this working? I am trying to learn how to create scripts as needed and found that there is a recent issue where Dell Support Assist is persistently prompting users for UAC to allow Dell Support Assist to complete tasks but it is causing a large influx of calls to the desk. TIA.
  19. 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
  20. Interested in this as we use prtg and automate as well.
  21. Ahhhhh. This makes a lot of sense. I will look into this. Thank you very much!
  22. Hey Guys & Girls, After a long time away from Automate, well looks like I am coming back thank god as my new company have all but decided to move over and get me to set it all up! One thing which keeps coming up those as resistance to it, is the following... What are the most useful \ most used scripts in Automate out of the box, I find this hard to answer as I wrote all our for the old company and we used very little out of the box scripts which now looks a lot more complete than it did last time I set up a new Automate server which was back on version 9 or 10 (I realise everyone's list maybe different but any good examples would be appreciated). At the moment the company is doing a very manual backup check process, this needs to stop, I get there is quite good Shadow Protect integration through the plugin but other programs are a bit more hit and miss, we have all sorts from Asigra to Windows Backups but mostly StorageCraft. I am wondering if there is any wonderful does all plugins or script for checking backups from any application (or at least most)?! I think I know the answer but after some time away would like to know if it's changed... Agent Deployment, the probe is OK and useful in some cases, but we found Group Policy Run Once was the best deployment option for Domain based PC's? We have 300+ Agents on LogMeIn, I know we could deploy it to these machines fairly easily but would be in root group unless we wrote a number of versions (1 per location), has anyone got a clever way to do this better? What have I missed since LT10? I have had a few demo's etc. and I can see that much is improved and added since I last used it, Updates, Layout \ Design etc. but much also looks very much as was it the backend, particularly the script editor which I am pleased to see if as comprehensive as it's always been, is there anything less obvious which has changed improved over the last few years? (Probably many points, I am looking for things I can use as selling points to directors if that helps). Anything else I should raise? Something coming soon? In development? etc.? I realise many of those questions are quite open which I apologies for, I don't expect any real detail in your responses I don't mind doing the leg work in researching the details, one liners will do if you prefer. I also realise I can get much of this information from the sales guys and believe me I have tried, but I get indifferent responses to some questions, for example most useful scripts, they say to don't know, don't have this info which is fair enough in my view but some of our Regional Managers want more, some of the other questions we have got answers from but I think I may get a whole different and more compelling set of responses from you guys who actually use it day to day! So all responses appreciated! Thanks Hoe.
  23. So i look in to Dataviews and found the other location's Router Address is the public IP of the firewall. I'm wondering why my main location is showing the private IP of the firewall and not the public. We are still in the implementation so we still adjusting. UPDATE: I install agents to machines in two of our locations and both of them have the Router Address as the Firewall's public IP. Not sure why our main site have private IP
  24. Try looking at another computer @Michael Diaz.. I suspect you are seeing a NAT loopback, or you are SNATing incoming packets. That should be the agent’s IP as the server sees it (which would normally be the agent’s public IP).
  25. I checked it and it's showing the default gateway which is a firewall, ideally we are looking for the firewall's public IP.
  1. Load more activity
×
×
  • Create New...