Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. I'm not sure. I think Office365 requires the use of TLS/SSL so uncomment that line ($SMTPClient.EnableSsl = $true ) But there's a reason why in don't use O365. It has started to require modern authentification on it's protocols. Therefor even if you get this to work now it will not work in the future. The right way to do it on office365 require an token with the right permissions setup.
  3. Hi @Wupsje, could you help me troubleshoot why nothing is happening. here is what i have at the bottom of line 17 $CredUser = "name@email.com (Outlook Email)" $CredPassword = "password (Outlook Password)" # Create message $message = New-Object System.Net.Mail.MailMessage # Sender Address $message.From = "My@email.com" # To Address $message.To.Add("@EmailAddress@") # Email info $message.Subject = "Treesize - $((Get-Date).Tostring('dd-MM-yyyy HH:mm')) - $machine" $message.Body = $($sb.ToString() | Out-String) $message.IsBodyHtml = $True # Server Info $SMTPServer = "smtp.office365.com" $SMTPPort = "587" $SMTPClient = New-Object Net.Mail.SmtpClient($SmtpServer, $SMTPPort) #$SMTPClient.EnableSsl = $true $SMTPClient.Credentials = New-Object System.Net.NetworkCredential($CredUser, $CredPassword); $attachment = New-Object System.Net.Mail.Attachment($outputFileName, 'text/plain') $message.Attachments.Add($attachment) $SMTPClient.Send($Message) Start-Sleep -Seconds 10 $attachment.Dispose() $message.Dispose() $SMTPClient.Dispose() Remove-Item $outputFileName -Force } Should this work? the smtp port is the outgoing email port
  4. Yesterday
  5. Thanks for the information guys. Front Page has been updated with the latest past as well as a Pre and Post patch guide to ensure that your agents will check in after upgrading. As always please post any issues you're experiences so that we can all stay informed. Thanks!
  6. I went ahead and did it also, and I had the same issue. I had a lot more than 10% drop out (maybe more like 30%) and had to restart the agents manually. It was definitely not as seemless as most recent patches have been, so be prepared.
  7. hmm...Bitdefender is blocking the powershell script that creates the Automate.bat file....not sure how to work around that without putting environments at risk. It obviously doesn't like system calling powershell (we've had that problem using a batch file with BD to deploy automate). Kinda makes sense...system running a powershell command to download something from internet. its exactly what we do not want to be happening..until we do
  8. Hi Tevin, I use a free account from sparkpost to send emails (since it's next to impossible to always have a secure way to email from the client). You need to adjust the $CredUser, $CredPassword and $Message.From to reflect the settings in your own account. @EmailAddress@ is a labtech variable in the script that gets set to the email adres of the labtech engineer that executes the script. If you have a different SMTP server that accepts email, you could adjust the code to email through there.
  9. I jumped in, to get it out of the way. They didn’t specifically say but I changed our template to upgrade the agent immediately, since they implied that would happen and said no commands would process if it didn’t. Good news is the patch went in fine. Bad news, about 10% of our agents dropped offline. I found on all of them stopping and starting ltservice service via CW control's remote command line got it to upgrade. Some logged connection errors in lterrors.txt which could be our upload being swamped. However they didn’t reconnect in a half hour. And, more than one logged a stream of errors like this: LTService v200.201 - 7/2/2020 11:47:45 PM - Proc Cmds7 ToInteger2 - Conversion from string "randomletters" to type 'Integer' is not valid.::: …many times per second. All that is before changing the system password. For anyone not aware, Dashboard/Management/Outdated is a great way to see old agent versions. Our one XP computer (ugh) needed the service restart but is connecting.
  10. Not sure how to do it in a monitor at the client's office (since that would require specific routing to the gateway), however, pfSense will send notifications of this and various other alerts such as reboot, update install, alias errors, etc. System/Advanced/Notifications. https://docs.netgate.com/pfsense/en/latest/book/config/advanced-notifications.html Note you shouldn't monitor the ISP router in the gateway settings because that router may be up but the connection down. I pick on Google and use 8.8.8.8 on one and 8.8.4.4 on the other since they have to be different.
  11. Hi, i've been testing out a script to make sure it works on not just one PC and I've been running into this error. The code is to copy " \\10.0.0.2\Share\Windows10.iso" to a certain folder. However in running the script on this PC I get ERR an error occurred: Access to the path"\\10.0.0.2\Share\Windows10.iso" is denied. I am able to access this folder on the PC in question and have even tested copying the file over manually. It all works, but the command list on the PC shoots me the above error. This script has worked for another PC so I am unsure where to go from here.
  12. I guess, except this time they fixed a bug which prevent agents from picking up the password change, so you're supposed to rotate passwords after rolling out the new agent.
  13. There is one now... https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/260/050 "product team recommends the system password reset cycle is performed any time agent installers are suspected to have been attained by unintended parties" Well that explains why they broke the direct agent download URL. https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Supportability_Statements/Automate_Security_Release_July#On-Premi Patch 7 is out. Note the part about "The 2020.7 and the 2019.12 patches address issues that prevent agents from receiving the new system password after a reset was performed." So hopefully no one ran into that problem last month...
  14. Last week
  15. Hi. I’m looking for the most efficient way to monitor around 200 public ip addresses. I’ve started creating them manually using remote monitor ping checks but it’s a repetitive process using the monitor wizard Surely there’s a better way ? thanks Gary
  16. Patch 7 is out. https://university.connectwise.com/university/pageview.aspx?short_name=patch-release-notes It says they are delaying security disclosure a week (July 9) to give everyone time to patch. Also that they won't patch 2020.1 to .6. The notes say "Complete the system password reset steps after you applied the patch and after your agents have been successfully updated." However the linked doc says nothing about having to update all existing agents first... Edit: I had stopped to read the release notes. The end of the email says "Both the 2020.7 and 2019.12 patches address issues that prevented agents from receiving the new system password after a reset was performed. Completing the password reset step after the patch is applied & agents have updated ensures agents receive the new information in case they are currently out of sync." So that probably affects anyone who changed their system password before now, especially in the last week or two.
  17. This is a good idea. We've gone for a slightly different approach. Our script is pretty much identical to yours, except for the SQL query at the start. We have a pre-patch script set on the reboot policy which is only applied to Hypver-V Hosts. Then our SQL queriy gets a list of all VMs in the database with a "vmhost" entry of %computername%.%domain% (which is going to be the server that's about to patch). Saves setting the entire location into Maintenance Mode - if you're like us you may have other unrelated devices there too that you don't want to silence. SELECT computerid FROM inv_bios WHERE VMHost = '%computername%.%domain%';
  18. Actually, Yes I have! Made a script that sets the entire location where that hyperv agent resides into maint - used pre-reboot.
  19. Sorry to bump this old thread, but anyone made any progress with this? We have multiple clients that may have multiple standalone hyper-v servers not in a cluster. When the Host server reboots and is potentially offline for a longer period of time due to a long patch install, all of the guest machines will alert because they are off for more than the monitoring period. What I'd like to do is put the guests on the hyper-v into maintenance mode as part of the "run script before patch" process. However I can't work out how to get the list of machines with automate. I can shell out and do a get-vm to return the list of computers on the host. However, putting a machine into maintenance mode requires the ID of the computer and not the computer name. Any one solved this issue or knows how to return the id for a computer against a computer name?
  20. Hi @Wupsje Is all that needs to be changed the $CredUser, $CredPassword, and $Message.From email? Or am I changing @EmailAddress@?
  21. That seems so hard. I found it was easier to just exclude servers with an SSD raid from the monitor completely
  22. You could monitor it from the outside, from your systems or from the systems of a client. Just create a ping monitor for each of the public IPs. or, you could use snmp from a probe on the clients installations which queried the pfsense, but I don't know if pfsense support snmp info to indicate if an interface is considered up or down. or, if the pfsense doesn't support that sort of thing, you could define routes on the pfsense to route a particular IP out over just one of the links. If each of the IPs was for a router in the ISPs network, then pinging IP1 would indicate that DSL1 was working and pining IP2 would indicate that DSL2 was working. I am assuming you can do this in the routing tables of the pfsense. This way a ping monitor on a probe could be used. or, if the pfsense can generate syslogs which correspond to interface down or route down (they're different obviously) then you can point those syslogs at the probe and use those to generate alerts. Never tried that, but in the end, they just go into a table in mysql.
    Took a small bit of tweaking but it works. A few tips: As we have a cloud hosted server, we could not keep our Win10 iso in our LTshare folder. Our workaround was to use one of our on prem share servers. Added a Variable Set with parameter="\\10.0.0.2\Share" Variable Name="ShareDrive" . Instead of using File Download I used File Copy. Source Path="@ShareDrive@\@WindowsISOFilename@" This worked great. With 7zip I was a small bit confused. I downloaded the .7z version of 7zip as I assumed we needed the console version. After installing the 32 bit version of 7 zip I transferred the 7z.exe and 7z.dll from there and it worked after that. If you are like me and are testing it on a very slow laptop, close anything you can thats running in the background of the PC. I was up to the point where everything was extracted but I couldn't get it to update. Removed a bunch of things from startup and got my ram usage down about 1gb. Finally got the update after doing this. Anyway, thanks for the great script, Tevin Ignacio
  23. Thanks Chuck, unfortunately, I'm meeting with an error that the Automate Server or token parameters was not entered or was inaccessible
  1. Load more activity
×
×
  • Create New...