1. Verify the service exists.
   
2. Bail if it doesn't.
   
3. Verify the service is running.
   
4. Log that you are stopping the service.
   
5. Set the wait duration.
   
6. Stop the service as a job.
   
7. Cycle a while loop every second to check if it's still running.
   
8. Bail and Log if the job fails.
   
9. After the wait duration elapses, check if the service is running.
   
10. If it is, log and bail.
    
11. If it's good and stopped, log and continue.
    

• Our logging writes to ~4 separate log files of varying verbosity, by default, with some scripts adding more. this is in addition to any CM logs generated.
  
• These 4 log files are written for different audiences and obscured away at different levels based on technical competency of the target audience.
  
• One of the log files, the most public-facing, and the one we recommend end users and low-tier techs check, is written at script exit with an extension based on script function and status, replacing all previous logs of that type, regardless of extension.
  
• The typical extensions are .S (successful install), .F (Any failure), .U (successful uninstall), .I (script incomplete, probably pending reboot).
  
• Buuuuuttttt, there's no standard for what these logs contain. Some of the are 0-byte empty files, some include return codes, some include timestamps, some have human-readable summaries, it entirely varies not only by who wrote it, but how they were feeling that day.
  

adaz fucked around with this message at 16:03 on Jun 24, 2021

PierreTheMime fucked around with this message at 23:14 on Jul 12, 2021

 
$Subscriptions = @('Sub1','Sub2','Sub3')

ForEach ($Sub in $Subscriptions){
   Set-AzContext $Sub
   $RGs += Get-AzResourceGroup

            ForEach ($RG in $RGs){
                $AAs = Get-AzAutomationAccount
            }
}

Luna fucked around with this message at 20:27 on Jul 16, 2021

I haven't used that module, but two things jump out at me:


• Why $RGs += Get-AzResourceGroup rather than $RGs = Get-AzResourceGroup?
  
• Don't you need to specify the resource group name for Get-AzAutomationAccount?
  

$AAs = foreach ($Sub in $Subscriptions)
{
    Set-AzContext $Sub
    Get-AzResourceGroup | ForEach-Object
    {
        Get-AzAutomationAccount -ResourceGroupName $_.ResourceGroupName
    }
}

• Uninstall it
  
• Delete all local GPO's
  
• Update GPO's.
  

$Credential = Get-Credential
$PCName = Get-Content "C:\path\to\file\remotecomputers.txt"

foreach ($name in $PCName) {
    $prog = Get-WmiObject Win32_product -ComputerName $name -Credential $Credential | Where-Object Name -eq "ProgramX"
    if ($prog) {
        Write-Host "Found ProgramX install on $name"
        Invoke-Command -ComputerName $name -Credential $Credential -ScriptBlock {Start-Process cmd.exe -ArgumentList {"/c C:\windows\ProgramX\programx.exe /uninstall" };
            Start-Process -wait cmd.exe -ArgumentList {"/c RD /S /Q `"%WinDir%\System32\GroupPolicyUsers`""};
            Start-Process -wait cmd.exe -ArgumentList {"/c RD /S /Q `"%WinDir%\System32\GroupPolicy`""};
            Start-Process -wait cmd.exe -ArgumentList {"/c gpupdate /force"}
        }
        Write-Host "Finished process on $name"
    }
}

Start-Process "C:\windows\ProgramX\programx.exe" -ArgumentList "/uninstall"

Toast Museum fucked around with this message at 01:17 on Oct 8, 2021