Using Elevate Policy for access to Environment Variables?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Using Elevate Policy for access to Environment Variables?

L3 Networker

This is an interesting case don't know if it has been answered before. We have a couple of users who need access to modify their environment variables.

 

I can properly give access to SystemPropertiesAdvanced.exe in Windows/System32. But I was wondering if there was any way to not let the user do other functions in System Properties like:

  • Change computer name
  • Alter Start and Recovery settings
  • etc.

 

Anything is appreciated!

1 accepted solution

Accepted Solutions

L5 Sessionator

we personally have a policy for Environmental variables - Allowing users the ability to edit the user and system variables currently can be done from cmd or windows + R using the following command rundll32 sysdm.cpl,EditEnvironmentVariables  and we actually block SystemPropertiesAdvanced.exe as you say it gives access to many other things that we don't want our dev/users to have access too. Therefore we actually have a block policy for systempropertiesadvanced.exe and have an allow policy for the above which I believe doesn't require admin rights and can access the user/system ENV buttons. Hope that helps? We then say on the block GUI prompt to use the other method suggested

View solution in original post

3 REPLIES 3

L5 Sessionator

we personally have a policy for Environmental variables - Allowing users the ability to edit the user and system variables currently can be done from cmd or windows + R using the following command rundll32 sysdm.cpl,EditEnvironmentVariables  and we actually block SystemPropertiesAdvanced.exe as you say it gives access to many other things that we don't want our dev/users to have access too. Therefore we actually have a block policy for systempropertiesadvanced.exe and have an allow policy for the above which I believe doesn't require admin rights and can access the user/system ENV buttons. Hope that helps? We then say on the block GUI prompt to use the other method suggested

L4 Transporter

we personally have a policy for Environmental variables - Allowing users the ability to edit the user and system variables currently can be done from cmd or windows + R using the following command rundll32 sysdm.cpl,EditEnvironmentVariables  and we actually block SystemPropertiesAdvanced.exe as you say it gives access to many other things that we don't want our dev/users to have access too. Therefore we actually have a block policy for systempropertiesadvanced.exe and have an allow policy for the above which I believe doesn't require admin rights and can access the user/system ENV buttons. Hope that helps? We then say on the block GUI prompt to use the other method suggested

L3 Networker

@Touseef-ur rehman​ - Thanks this worked great, appreciate the quick help!

=

  • 1 accepted solution
  • 161 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!