Repository navigation
MSI installer run RegisterManifest.ps1 and Enable-PSRemoting #5979
Description
Activity
Do those 2 scripts need to be run as admin?
Steve Lee (@SteveL-MSFT) I'll tackle this if you don't mind. I already have a dummy prototype working that executes a psscript as an admin but I will be busier for the rest of this week, so I guess you can expect a PR in February if that's OK?
Have a think about the UI aspect please in the meantime (I think we need more details in parenthesis to briefly explain what the options mean) and the preferred name for the MSI properties. I suggest putting it together with the existing custom dialog:
Christoph Bergmeister (@bergmeister) consider it yours! Thanks!
No rush as 6.1.0 previews will come out on a regular cadence. If it doesn't make Preview1, no problem!
I think putting it in the
Optional Featuresin your mockup seems fine. Suggest some wording changes:- Register Windows Event Logging Manifest
- Enable PowerShell Core remoting
cc Joey Aiello (@joeyaiello) for wording suggestions
From an Enterprise Management and Security point of view , I would like to see that the owerShell ETW manifest is registered by default. Is there a reason to not do so?
Alex Verboon (@alexverboon) I believe the current design is that the ETW manifest is registered by default (option is checked).
Reacted by Alex Verboon
Users may not be aware that they need to run RegisterManifest.ps1 to get logging and Enable-PSRemoting to have a PSCore6 remoting endpoint. The MSI installer should have two checkboxes: register eventing manifest (checked by default), register powershell remoting (unchecked by default) along with appropriate MSI options for quiet installs.