Windows 10: Block script execution for standard user.

How to restrict standard user from executing scripts and to provoke windows admin credential to execute them?

:)

 

UAC & standard users with additional privileges

I am marking this problem as solved. The problem was:

Allow a standard user to enable/disable a network without having to enter a password every time.

My solution for Windows 7 was:

1. Add the standard user to the "Network Configuration Operators" group.
2. Login as the standard user.
3. Create a shortcut to the network adapter.
4. Right-click on the shortcut to see or change the state of the network adapter.

I have received many useful and instructive suggestions on Tenforums. Based on those suggestions,
here's my solution for Windows 10:

1. Add the standard user to the "Network Configuration Operators" group.
2. Login as the standard user.
3. In a cmd window, run this command
netsh interface show interface
to learn the name of the network adapter.
4. Run Task Scheduler using the password of the standard user.
5. Create two shortcuts in accordance with Option 2 in this tutorial:
Elevated Shortcut without UAC - TenForumsTutorials
-- at Step 3, name the shortcuts something like “EnableLAN” and “DisableLAN”
-- at Step 7, in the Program/script field, type netsh
-- at Step 8, into the Add arguments field, type
interface set interface "name of network adapter" admin=enable
(Make the last element “disable” for the second task.)
-- at Step 14, name the shortcuts something like “Turn LAN On” and “Turn LAN Off”
6. Press the Win + R keys to open the Run dialog, type ncpa.cpl into Run, and click OK to open the Network Connections window. Keep this window open on your desktop to see the state of the network adapter. The color of the icon reflects the state of the adapter.
7. Click on one or the other of the two newly-created shortcuts to change the state of the network adapter. A cmd window briefly flashes on the screen. This can be eliminated using the procedure mentioned by Try3 in a previous post, if desired.

The solution for Windows 10 is much more cumbersome than the solution for Windows 7. I have to stop using Windows 7 due to the end of Microsoft support, and this is not the first time that I find Windows 10 to be less user friendly than Windows 7.

Thanks, again, to all who have kindly given me help and advice

 

script to delete users profile

*Sad - Been there, done that.

I would suggest the first thing to do is to check the local PowerShell execution policy:

1. Right-click on Start and select Windows PowerShell (Admin). This will invoke the User Account Control (unless the Domain Administrator has amended the default UAC policy) for you to accept then display an elevated PowerShell console.
2. In the console, enter Get-ExecutionPolicy.
3. If this returns 'Restricted' (the default policy), enter Set-ExecutionPolicy unrestricted.
   
   If this command is accepted without error then you should be able to be able to run that TechNet script without any permission problems.

PS. Don't forget to reset the execution policy back to Set-ExecutionPolicy restricted afterwards.

Hope this helps...

 

Issue faced when PowerShell script executed through SQL Server Agent Job

I have a PowerShell script that searches for an excel file at a particular location, if found copies it as a CSV file to another location.

This CSV is used as a source in ADF - Copy Activity.

This script is not interacting with any database, nor performing any db tasks - just reading an excel and converting it to CSV at particular location.

It is working fine as intended, when executed through PowerShell ISE, but when I scheduled it as a SQL server agent job it is not doing anything. The job successfully as per the message in Job History, but it does not do anything. The message says :

=====================================================================================

Message

The job succeeded. The Job was invoked by User PMCI\VermaRachna. The last step to run was step 1 (Load_Radiotherapy_Machine_Utilization_File_Org_Src).

Message

Executed as user: PMCI\SVC_DASH_SQLDevAGT. The step did not generate any output. Process Exit Code 0. The step succeeded.

=====================================================================================

I have scheduled the Job with type as "Powershell" and the script code is pasted in Command area of the Job Step.

Since I am not getting any error message how do I know what is the issue due to which script is not doing anything when run through SQL Server agent job. Can some one help with this please. I can share the script code if required.