Jump to content

SOrlando

Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

1 Neutral

My Information

  • Agent Count
    3000+

Recent Profile Visitors

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

  1. SOrlando

    Remote Monitor Triggered when User Logs In

    That is' what I wound up doing. A simple logoff script that runs a ROBOCOPY/Delete command to clean those folders up. I just need to create an additional Flexible Asset in IT Glue to make sure we document all of the GPOs and additional custom automation going on per client so there is information somewhere that these items exist.
  2. SOrlando

    Remote Monitor Triggered when User Logs In

    Brainstorming: Can I get a File/Directory Monitor to check as the user? Scenario: User logs in. Monitor now sees the AppData folder in the users profile now that their Profile Disk is active (C:\Users\%userprofile%\AppData) and triggers a script that runs as user to clean up cache files in AppData folder.
  3. Has anyone had success creating a Remote Monitor that triggers when a user logs in? I have a client with an RD Environment using Profile Disks, so a script to clean up cache files does not work unless the user is logged in. Rather than fire off a script to grab users currently logged in and run it several times a day; if I can get a working Remote Monitor that detects when a user logs in and then responds by firing off the script to clean up their profile, that would be perfect.
  4. SOrlando

    Ticket Update Function Not Working

    Worked like a charm. You, sir; get a cookie. A big rancor one. Made out of Gammoreans.
  5. Need help to make sure I am using the Update Ticket script function correctly. I have a powershell script fed into an Automate script which I have confirmed is working as intended. If successful, it returns a True result. This is then used to trigger a Create Ticket and Update Ticket function. This is also working, until it gets to the Update Ticket task. Pic1 = Automate Script Pic2 = Ticket Create function (Works - Automate Ticket gets created when powershell script returns True) Pic3 = Ticket Update function set to change Category ID to 124 which is Performance - Server OS Pic4 = Automate Ticket with Category unchanged from default Monitor Alerts category
  6. Nevermind. Found out that the Location they are in was not configured properly for Ignite Patching. That's what I get for giving other techs rights to create Locations. We can never have good things!
  7. I am having a rash of workstations in the patch manager that are not updating at the Next Microsoft Window date is set in the past. Workstations show with no available jobs, but are members of the proper default workstation patching group.
  8. Still gold! Needed to create a new MS SQL 2016 Servers role group.
  9. SOrlando

    Finding Disk Monitors

    So I have been tasked to clean up noise being produced by Automate tickets. One of which is Disk Space tickets for Workstations. We have decided we do not care about these enough to fill our ticket queues with them, but wish to continue to work any tickets for Server Disk Space issues. I have dug around the monitors and found at the Global level, the DRV monitors are set to Do Nothing; however when I look at a Workstation's Effective Policy there is a Remote Monitor called Disk that is creating tickets, but is not associated with a group. Where do I control those monitors?
  10. SOrlando

    Script to Notify Customers of Patching

    Instead, I setup ticket templates under each client that corresponds with their monthly scheduled maintenance in Automate. The ticket is generated 7 days before the maintenance date and sends out the first notice that maintenance is coming up. Then workflow rules watch for the age of the ticket and the night before maintenance another notice gets sent out to the client and my tech team so they are aware of the maintenance that evening. At the same time it sets the ticket to QA status and puts me as the Resource so it is in my queue the next morning.
  11. That seemed to work; although I guessed the wrong KB. Now I can setup a schedule to run tonight against our workstations and servers and tomorrow see if there is any fallout before dealing with client's.
  12. True. I use a lot of EDFs to group my Veeam proxies so I can organize them to patch during the day when backups aren't running.
  13. When you run the script against the All Agents Group as a Run Once, you can click on the Advanced Settings link and uncheck the 'Skip Offline Agents' box so it will queue for any devices that are offline. So the next time they report in, the script will be queued to run.
  14. I ran my script against the Location, so it hit all devices under that location for our machines. I suppose when I am ready to send it to all our client's devices, I can run it against the All Agents group.
  15. Here's what I'm thinking (and testing against a few my own machine): Create a new Approval Policy with Automatic Approval for the KBs by Title (KB4056615, KB40567559, KB4056888, KB4056890, KB4056891, KB4056892, KB4056893, KB4056897, KB4056898, KB4056899, KB4056941, KB4056942, KB4056944). Call it Speculative Execution Mitigation Policy. Create a Test Group to apply the Policy to. In my case, I am testing it against my workstation, so my workstation is the only device populated in the group (whether it is an autojoin or a drag and drop [while we still can until v12 hits]). My workstation qualifies for one of the patches (KB4056892). Set a Microsoft Update Policy with a maintenance window within the next hour. Under Groups, assign the Speculative Execution Mitigation policy to your Test Group and assign the Microsoft Update Policy schedule that starts during the time you set. Not going to Suppress Reboots and allow it to reboot during my maintenance window to see if it does. We'll see how it goes.
×