Jump to content

timbo83251

Members
  • Content Count

    102
  • Joined

  • Last visited

  • Days Won

    2

timbo83251 last won the day on December 20 2018

timbo83251 had the most liked content!

Community Reputation

5 Neutral

My Information

  • Agent Count
    1500+

Recent Profile Visitors

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

  1. @SteveYatesThanks. Automate patching and reporting needs another overhaul especially with WIn10 in mind.
  2. What is the best way to exclude operating systems that are no longer receiving updates due to end-of-support (e.g. Windows 7, Server 2008)? There's no point in alerting on these... I'm thinking just adding additional WHERE to the monitor condition like "AND computers.os NOT LIKE '%server 2008% and computers.os NOT LIKE '%windows 7%'". Unless there is some other table out there that classifies OS versions as supported or not... or would using the version # be better?
  3. I had been denying them, but found that the feature update to 1909 from 1903 works ok when deployed from automate. Still requires the user to reboot I think (to initiate it?), but I was able to, over the course of a few months, get almost all my 1903 to 1909 from Automate. I hope it continues in this fashion.
  4. So I was able to utilize BITS different way (avoiding the LT function) and just using "Execute Script>Powershell (bypass)" instead. This way, it waits for that powershell command to complete before moving on to the next script step and you don't have to do all that file checking crap (although an MD5 check against the source is still a good idea) start-bitstransfer -source http://server.com/Windows.iso -Destination @pathToISO@/@isoName@.iso
  5. Have to be careful with SAVE auto stop action. VM's with a ton of RAM can take way longer to save than to just shut down. We have customers with VM's in the 100's of GB of ram. Save action also creates a blank file of equal size on the host to accommodate that (similar to hiberfile.sys). Make sure you have the disk space before you go setting all VM's to save I like @maxgruv idea of setting location into maintenance mode via script in the reboot policy, I'll work on that. That way we don't have to go by group level maintenance windows which may apply unnecessarily as can only do weekly.
  6. I'll share what I have for powershell -- not working 100% for the auto downloading of psexec to sysvol and stuff, but I tweak as needed. You can prob see where I as going. I'm sure someone can make it way better... Write-Host "This script will use PSEXEC to run a powershell command on every remote PC on the a specific network to Replace and/or Install our Labtech Agent" Write-Host "It will attempt to download PSEXEC.exe to the NETLOGON folder of the domain. If this script fails, you may need to place it there manually." Write-Host "You should be running this script from a domain controller AS ADMINISTRATOR" Write-Host "Networks will be broken down into /24" $SUBNET = Read-Host -Prompt 'Input the Network ID (e.g. 192.168.1.0)' $SUBNET = $SUBNET.Substring(0,$SUBNET.Length-2) $LocationID = Read-Host -Prompt 'Input the Labtech Location ID' $Domain = $env:userdnsdomain $PSEXECPATH = \\$Domain\NETLOGON\psexec.exe #If (-Not(Test-Path -Path "C:\Windows\SYSVOL\domain\scripts\psexec.exe" -PathType leaf)) #{ #Invoke-WebRequest -Uri "https://ltserverfqdn.com/Labtech/Transfer/Tools/psexec.exe" -OutFile "C:\Windows\SYSVOL\domain\scripts\psexec.exe" #} Write-Host "Labtech will now be pushed out to '$SUBNET.0' and will go into Location '$LocationID'. The location of PSEXEC is '$PSEXECPATH'" $x=1 DO { $IP = "$SUBNET.$x" Write-Host "$IP" $ARGUMENTLIST = "-n 9 \\$IP C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe (new-object Net.WebClient).DownloadString('http://bit.ly/LTPoSh') | iex; Reinstall-LTService -server https://ltserverfqdn.com -LocationID $locationID" Start-Process -filepath "$PSEXECPATH" -ArgumentList $ARGUMENTLIST $x++ "Now `$x is $x" } While ($x -le 254)
  7. Copy-Item C:\inetpub\wwwroot\automate\index.html -Destination C:\inetpub\wwwroot\automate\index-backup.html;((get-content -path C:\inetpub\wwwroot\automate\index.html) -replace 'var isChrome = !!window.chrome && !!window.chrome.webstore;','var isChrome = !!window.chrome;') | Set-Content -Path C:\inetpub\wwwroot\automate\index.html;
  8. Depending on how many units you are managing, look into GMS. We tried the SNMP route years ago, it was a ton of effort for nothing.
  9. I've noticed they finally released the fix for the Known Issue you originally referenced @Gavsto. (8396574). AD report still broken so I assume that wasn't the only cause.
  10. When I hit logon after entering my creds, it just does nothing. In come cases I actually see the "Logout" link appear (while still showing the same logon prompt fields) but right now I do not. Login just has no change. If there's any logs you want me to gather let me know. I also recently installed the new CW manage plugin from solution center but I doubt that's related. thanks. EDIT: THIS WAS MY STUPIDITY - IGNORE
  11. This break for anyone else after latest version of screenconnect 6.7?
  12. awesome thanks! FYI in the ProPlus script (all apps), your download location and unzip location are named incorrectly to Business-Retail which might add confusion.
  13. Assuming the correct permission for the user is there (I think it's location access or something, you can try this: a. Close the Control Center, if open. b. Open RegEdit. c. Browse to HKEY_CURRENT_USER\Software\LabTech\Client\ d. Delete the lists folder.
  14. The update prompts seen recently are due to 2 KB patches: -KB4091461 (End of servicing notification for Windows 10 Versions 1507, 1511, and 1607. ) -KB4023814 (Some versions of Windows 10 display a notification to install the latest version) I have disabled these updates and set them to remove which will be during next patch cycle. I'm not sure if this will stop it where it's already installed, however. I wish patch manager just took care of installing 1709!
×
×
  • Create New...