I am still learning my way around PowerShell, but getting a bit better everyday, things are looking up. One of the issues that my team and I are facing is Remote Management of domain level machines. A little background, I work in a environment where WinRM and PSRemoting are not enabled through Group Policy. The machines are imaged, added to the domain, and begin their jobs. There are no PowerShell users other than our handful of techs that are trying to learn and use this wonderful tool at our fingertips. So, here is the question, is it possible to build a script that will test the connects/configurations of distant machines and return the results. Then the same script of a different script to run against remote machines to enable the remoting configurations, without using Group Policy? We have machines that were deployed before PowerShell was discovered, so right now we are manually configuring all new machines before they leave our shop, but what can be done about those that are already in the field? Even a list of the ones that are enabled versus not-enabled would be of help at least we could reach out to just those machines. Group Policy is out of the question, if we announce the fact that GP is the answer, we will be locked out of PS completely, any answers or ideas are welcome. Our PowerShell knowledge is just not up to where it needs to be to solve this issue, but we are learning.
↧