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

Community Reputation

0 Neutral

My Information

  • Location
    USA
  • Agent Count
    750 - 1000 Agents

Recent Profile Visitors

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

  1. Sorry to necromance this thread but was wondering will this work on labtech hosted environments? If so how hard is it to make the connection to the hosted environment to accomplish this?
  2. There are several ways to skin the cat. 1: Remote monitor using event log (this will watch on the device for the event to take place monitored at the agent level) 2: Internal Monitor (Monitor that watches the automate db the settings for how often this will check is defined on Automation -> Schedules -> select the type of computer it is (server/workstation/etc) -> Event Log, Syslog and Windows Update log scan) (the value of this dictates how often the internal monitors are grabbed) 3: Powershell you can create a powershell remote monitor to watch for the events this would fall under a remote monitor. the tl;dr version is remote monitor using powershell is your best option otherwise I'd suggest an internal monitor because quite honestly you won't need to watch for that particular event terribly often.
  3. i'm east coast while my msp is west coast and our server itself is west coast as well... simple solution i changed my computer time to west coast and haven't had any problems since.
  4. Not sure what you're trying to accomplish specifically but why not make use of the L drive rather than involve added moving parts?
  5. You could leverage powershell then search the output for what you seek if what you're looking for comes up then you could have the script make a ticket that is personally how I would do it rather than depend on the AD Plugin. Import-Module ActiveDirectory once you load the AD module in powershell here are some commands you can use to query AD itself. Update: You can get the accounts if you pass a string value, passing an integer initializes the timespan to 7 ticks! Search-ADAccount -AccountExpiring -TimeSpan "7" other valid options: Search-ADAccount -AccountExpiring -TimeSpan (New-TimeSpan -Days 7) Search-ADAccount -AccountExpiring -TimeSpan ([TimeSpan]::FromDays(7)) Could be a bug, it doesn't work for me as well. Here's a workaround: $NeverExpires = 9223372036854775807 $ExpringIn = (Get-Date).AddDays(7) Get-ADUser -Filter * -Properties accountExpires | Where-Object {$_.accountExpires -ne $NeverExpires -and [datetime]::FromFileTime([int64]::Parse($_.accountExpires)) -lt $ExpringIn } Referenced this thread: https://stackoverflow.com/questions/10247334/powershell-find-users-expiring-in-7-days
  6. @LoneWolf Kinda curious we just had a couple tickets in our queue this morning of the following. SERVERREDACTED at REDACTED, location REDACTED has drives in its RAID array that are of a type that are known to fail early. This ticket has been opened to address the issue with Dell. The Physical Disk Report and the controller logs have been uploaded to the LabTech Server. Physical Disk Info: C:\LTShare\Uploads\REDACTED\REDACTED\storagelog.txt on the LabTech Server Controller Logs: C:\LTShare\Uploads\REDACTED\REDACTED\RAIDLogs.txt on the LabTech Server Can you shed some light on this? I'm assuming this is likely from one of your scripts. I'm assuming this is the script doing it "Copy of Dell - Identify Problematic Server Drives - This script identifies Seagate drives of a very, very problematic Cheetah mode series, specifically what my organization knows as "The Dreaded ES66 firmware drive". Dell firmware updates to ES68 make them run a bit better, but these drives are extremely failure prone compared to other drives we have seen. If drives are found meeting the script's criteria, a ticket is opened." What action does your org normally take on these? I'm assuming based on your notes updating firmware to ES68. Can this be done remotely or should we onsite for it?
  7. Haven't tried it myself but found this tutorial: http://www.matthiaseinig.de/2009/12/06/qnap-activate-root-account-on-nas/
×
×
  • Create New...