search for: executionpolicy

Displaying 8 results from an estimated 8 matches for "executionpolicy".

Did you mean: execution_policy
2019 Apr 16
0
[PATCH v2v v2 1/2] v2v: windows: Add a helper function for installing Powershell firstboot scripts.
...check this exists? XXX *) + let ps_exe = + i_windows_systemroot ^ + "\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" in + + (* Windows path to the Powershell script. *) + let ps_path = i_windows_systemroot ^ "\\Temp\\" ^ filename in + + let fb = sprintf "%s -ExecutionPolicy ByPass -file %s" ps_exe ps_path in + Firstboot.add_firstboot_script g i_root filename fb diff --git a/v2v/windows.mli b/v2v/windows.mli index 016ef2a78..6db7874b0 100644 --- a/v2v/windows.mli +++ b/v2v/windows.mli @@ -21,3 +21,9 @@ val detect_antivirus : Types.inspect -> bool (** Return...
2020 Oct 02
0
Unable to compile with R CMD INSTALL on windows when sourcing from Rprofile
...workspace\checkout-base-dir\" [1] "Using environment default" powershell.exe : * installing *source* package 'assertthat' ... At D:\tomcat-jenkins\workspace\checkout-base-dir at tmp\durable-37e772e4\powershellWrapper.ps1:3 char:1 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (* installing *s...assertthat' ... :String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError ** package 'assertthat' successfully...
2013 Jul 22
11
chocolatey, windows, powershell and fault bucket
Hi, I configured puppet open source with the chocolatey module and one windows client. When the puppet agent run as a service (not the interactive version) I can see in the windows event log some errors like Fault bucket 1734820220, type 5 Event name: PowerShell Fault bucket , type 0 Event name: PowerShell I tried to google it but I did not find anything relevant apart from some
2019 Apr 15
2
[PATCH v2v 1/2] v2v: windows: Add a helper function for installing Powershell firstboot scripts.
...check this exists? XXX *) + let ps_exe = + i_windows_systemroot ^ + "\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" in + + (* Windows path to the Powershell script. *) + let ps_path = i_windows_systemroot ^ "\\Temp\\" ^ filename in + + let fb = sprintf "%s -ExecutionPolicy ByPass -file %s" ps_exe ps_path in + Firstboot.add_firstboot_script g i_root filename fb diff --git a/v2v/windows.mli b/v2v/windows.mli index 016ef2a78..6db7874b0 100644 --- a/v2v/windows.mli +++ b/v2v/windows.mli @@ -21,3 +21,9 @@ val detect_antivirus : Types.inspect -> bool (** Return...
2019 Jul 11
2
[PATCH v3 0/2] v2v: Copy static IP address information over for Windows guests
Patch v2 was here: https://www.redhat.com/archives/libguestfs/2019-April/thread.html#00114 There's no change here except that I've rebased it against the latest master branch and retested. There was a comment by Pino (https://www.redhat.com/archives/libguestfs/2019-April/msg00117.html) which isn't incorporated into this patch. Rich.
2018 Dec 04
2
[PATCH FOR DISCUSSION ONLY 0/2] v2v: Copy static IP address information over for Windows guests (RHBZ#1626503).
This patch is just for discussion. There are still a couple of issues that I'm trying to fix. One is that all of the test guests I have, even ones with static IPs, have multiple interfaces, some using DHCP, so the conditions for adding the Powershell script don't kick in. This makes testing very awkward. However a bigger issue is that I think the premise is wrong. In some registries
2018 Dec 11
2
[PATCH v2 2/2] v2v: Copy static IP address information over for Windows guests (RHBZ#1626503).
v1 was here with much discussion: https://www.redhat.com/archives/libguestfs/2018-December/msg00048.html v2: - Fix the case where there are multiple interfaces. Note this does not preserve order correctly (see patch for comment on why that is a hard problem). - Preserve name servers. This patch is still for discussion only. I'd like to see what might be done to get this upstream
2019 Apr 16
6
[PATCH v2v v2 2/2] v2v: Copy static IP address information.
Essentially identical to v1 except that it now uses (overloads?) the --mac option to supply this data. Rich.