Monica KVH
Not quite a wizard. Systems Support Specialist @ Bedford Industries. PDQ Inventory enthusiast & PDQ Deploy dork. Drinker of bourbons and Scotch whiskies, and petter of corgis. Handler of weird stuff with PowerShell.
Comments
-
Here's a fuller version of what I posted above that uses more of Microsoft's script: $comp = $env:ComputerName$ExecPol = Get-ExecutionPolicySet-ExecutionPolicy RemoteSigned -ForceInstall-Module Spe...
-
To capture the results of Microsoft's script, you can pass the Get-SpeculationControlSettings results to a text file using the pipeline. Something like this should do: $comp = $env:ComputerNameGet-...
-
Try using the full path in your remote command: C:\Windows\system32\bdeHdCfg.exe -target default -size 300
-
Swank! Thanks, Colby! I think I goofed up the comparison filter or the group filter when I tried and failed initially.
-
Are you deploying via .exe or .msi? You'll want to make sure that you have set up the package with the correct silent parameters. For file not found, make sure the package is targeting the installe...
-
As far as I'm aware, no. You might want to check out PowerShell (Get-EventLog / Get-WinEvent) or a tool like Labstats. However, if the application is updated frequently, you can run a report in Inv...
-
Thanks, Colby. I have a little bit of tweaking to do for our particular environment and the file scans I set up but it's getting results. :)
-
Stephen - that would work, but I'm hoping to keep everything in Inventory as much as I can so I can quickly share reports with the other admins. Colby - SQL is ideal so I'm excited to see what you ...
-
I delete them, but that's what works for our environment. Our retired PCs are generally wiped and donated to PCs for People, so keeping the history of them isn't really necessary or useful. We docu...
-
Our password policies for administrators here is to change them every 90 days. Of course, we can change them more often if we like. As far as capture and abuse mitigation go, I could only recommend...