Your network contains several servers that run Windows Server 2012 R2 and client
computers that run Windows 8.1.
You download several signed Windows PowerShell scripts from the Internet.
You need to run the PowerShell scripts on all of the servers and all of the client computers.
What should you modify first?
A.
The environment variables on all of the servers
B.
The execution policy on all of the servers
C.
The execution policy on all of the client computers
D.
The environment variables on all client computers
Restricted
– Default execution policy in Windows 8,
Windows Server 2012, and Windows 8.1.
RemoteSigned
– Scripts can run. This is the default execution
policy in Windows Server 2012 R2.
https://technet.microsoft.com/en-us/library/hh847748.aspx
0
0
So according to that the answer C is correct, as marked by the site.
0
0
Windows PowerShell execution policies let you determine the
conditions under which Windows PowerShell loads configuration files
and runs scripts.
You can set an execution policy for the local computer, for the current
user, or for a particular session. You can also use a Group Policy
setting to set execution policy for computers and users.
Execution policies for the local computer and current user are stored
in the registry. You do not need to set execution policies in your
Windows PowerShell profile. The execution policy for a particular session
is stored only in memory and is lost when the session is closed.
The execution policy is not a security system that restricts user actions.
For example, users can easily circumvent a policy by typing the script
contents at the command line when they cannot run a script. Instead, the
execution policy helps users to set basic rules and prevents them from
violating them unintentionally.
0
0
can some one please tell the answer?
0
0
C – set execution policy on client computers
Server 2012R2’s default execution policy is remotesigned which allows signed scripts. Workstations are set with “restricted” by default.
http://windowsitpro.com/powershell/use-execution-policies-control-what-powershell-scripts-can-be-run
https://blog.netspi.com/15-ways-to-bypass-the-powershell-execution-policy/
0
0