Powershell to export list of all services not running as SYSTEM account on all domain computers
I need to see if there are any services running as service accounts and wanted to query all our domain computers to get the service name, what state is it in (Running/Disabled/Stopped), the server it is running on and what account is running the service. I am not sure the best way to proceed so I pieced together some Powershell code from the web but it's not working when I try to use the $Servers variable to search the OU (line 2) & store that info so the code can run on all the machines. I'm not great with PowerShell & don't know if it needs a FOR EACH or not? It DOES work when I comment line 2 out & uncomment the line that specifies individual computers (line 3), but there are 2000+ machines I need to query. How can I have the script search my entire domain & get the ServiceName, ServiceDisplayName, StartName, State & servername it is running on, then export that to a CSV? I've tried Googling, but unfortuantely nothing I have tried works, any help is greatly appreciated, thank you in advance! # Get a list of all computers in the domain (you may need to customize this query) $Servers = Get-ADComputer -Filter * -SearchBase "OU=Citrix,OU=HCAA,DC=PACs,DC=local" # $Servers = ("cxap01", "msql01", "hwbr01") $ServiceName = @{ Name = 'ServiceName'; Expression = {$_.Name}} $ServiceDisplayname = @{ Name = 'Service DisplayName'; Expression = {$_.Caption}} Invoke-Command $Servers.servername -ScriptBlock { Get-CimInstance -Class Win32_Service -filter "StartName != 'LocalSystem' AND NOT StartName LIKE 'NT Authority%' " } | Select-Object SystemName, $ServiceName, $ServiceDisplayname, StartMode, StartName, State | format-table -autosize
How to find out who created a Azure Service Bus queue
Is there any way to determine who created a Service Bus queue and forwarded the messages from an existing Service Bus Queue to it? We tried the steps in the blog http://blog.itaysk.com/2017/06/25/determine-who-created-resources-in-azure, but that does not work if the Service Bus Queue is created using Service Bus Explorer (we've tested that). We had an incident where a new Service Bus Queue was created with the name of an existing one, with temp added to the end, which caused some issues, so we are trying to determine what or who caused it.
