Jump to content

RamboBinne

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Location
    Quebec
  • Agent Count
    < 500 Agents
  1. Hi, Windows manage reboot pending with 14 registry key. Some third party app use some of those key and after a deployment its common to see the yellow flag in our start menu. After a reboot Windows manage to erase the related key. Its all in all a good mechanic to manage reboot. My issue arise with some third party that doesnt use the Windows internal reboot flag mechanic, and yes Automate fall in this category. It know however where to look and across those 14 key below it read the two i've prefixed with **** (as per a ticket resolved by CW, those two key would be the one automate consider in the search condition "computer.os.isrebootpending" HKLM:\SOFTWARE\Microsoft\Updates HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager ****HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\Pending HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\PostRebootReporting HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce ****HKLM:\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending HKLM:\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootInProgress HKLM:\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackagesPending HKLM:\SOFTWARE\Microsoft\ServerManager\CurrentRebootAttempts HKLM:\SYSTEM\CurrentControlSet\Services\Netlogon HKLM:\SYSTEM\CurrentControlSet\Services\Netlogon HKLM:\SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName we are using some plugin to manage third party software like AV and Backup solution and sometime they report a required reboot. With some monitor, autofix and script twist we parse the database for third party required reboot message, then create a group, then reboot those within over night. It work well. We would however like to use the same registry key as some third party are able to use, to benefit from having just one rebootpending group. the issue is that while some third party app manage to register their required reboot, i fail to find a way to create a key. even in powershell there seem to be no way of calling something like get-rebootpending and set-rebootpending
  2. how the automate agent is handled during this process ?
  3. just here to follow this too !
  4. I did the same thing as the OP a while back, the use case is to make the process of excluding those ssd fully autonomous after new customer onboard or after an hardware migration, very efficient way to work
  5. Hi, its been driving me crazy since its an issue with a script that lead me to realize that indeed there is 30% of agent are for an unknown reason in a perpetual maintenance mode i've looked at deployment default, nothing there i've cleared it from the web control center as from the desktop app, nothing i've cleared it from the context menu of a location, then from the agent, nothing even got 4 years back in the audit to comprehend when or why but nothing there it just keep coming back each x minutes and the CW chat support have no clue, im waiting for escalation Vic
×
×
  • Create New...