Idea ID 2698114
We are currently discovering windows servers with PowerCMD, but want to discover with the PowerShell discovery, but there are some things we noticed.
1. The PowerShell discovery needs .Net3.5 and the Powershell2.0 engine installed in order to run
Our company security does not allow us to use these old and deprecated versions.
2. You need to be local administrator in order to do the discovery right.
Our company does not allow the discovery user to be local admin
3. The PowerShell discovery uses a powershellconnector.exe on the probe
this connector is limited in it's use and does not support all the powershell commands
Our Windows administrators asked us if it is possible to edit the powershell discovery so we can connect to another powershell configuration that supports JEA (Just Enough Admin) which allows the discovery user to be a virtual local admin during the discovery and deletes it's privileges after the discovery is finished. This way it's more secure. We've tested it with the PowerCMD discovery and it works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.