Skip to content
This repository has been archived by the owner on Mar 21, 2021. It is now read-only.

Execution Policy Unrestricted | Winrm / Admin Rights #19

Open
chwilfing opened this issue Aug 29, 2018 · 2 comments
Open

Execution Policy Unrestricted | Winrm / Admin Rights #19

chwilfing opened this issue Aug 29, 2018 · 2 comments
Labels
Question Question asked To Investigate... Investigate

Comments

@chwilfing
Copy link

Hi @veronicageek,

out of curiosity - which part of the tool needs Execution policy - Unrestricted? I've just run without and as far as I see there are no impacts running with policy 'RemoteSigned'.

Also the Admin Rights as far as I are not required. My SFB Online Powershell does work without WinRM service running and the only error I receive running the retriever is the Access Denied starting the WinRM service, everything else seem to work?

BG Christoph

@veronicageek veronicageek added the Question Question asked label Aug 30, 2018
@veronicageek
Copy link
Owner

@chwilfing: It seems the execution policy can be set to RemoteSigned indeed as the script will be run locally, and after testing, it works fine too on my machine. Something I'll change on the next release then...

With regards to the WinRM service, this is what I got with the service "Stopped":

start_winrm

It's halting the script, and needs manual intervention. However, when I choose "No", it seems to work fine still... Something I need to investigate with a Skype person I assume. I'll check that one.

Thanks for pointing that out 👍

@veronicageek veronicageek added the To Investigate... Investigate label Aug 31, 2018
@Toasterlabs
Copy link

On the admin rights: The whole script hangs on my Win 10 machine if it isn't running in an administrative context on the starting WinRM step

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Question Question asked To Investigate... Investigate
Projects
None yet
Development

No branches or pull requests

3 participants