pakenney38 Posted March 17, 2005 Share Posted March 17, 2005 Yesterday at work I was fooling around in our test network try to get a path rule to work in a software restriction group policy. My goal was to restrict the execution of a .cpl file in %SystemRoot%. This for some reason did not pass down to my test user account. What I have been following is a document from Microsoft known as the Windows Server 2003 Deployment Guide. This document, like all other Microsoft documents, seems to have some issue with the concept of ordered lists.So anyway, then I tried something basic. I attempted to restrict Internet Explorer, which has been in the same place in Windows since at least version 5. I used the direct path to IEXPLORE.EXE. Even this didn't work.So now I am at a loss. Is there something more I should be doing, or what? Link to comment Share on other sites More sharing options...
un4given1 Posted March 17, 2005 Share Posted March 17, 2005 Make sure you are setting the policy under USER and not COMPUTER Link to comment Share on other sites More sharing options...
pakenney38 Posted March 17, 2005 Author Share Posted March 17, 2005 I started off with user. It's basically what I was trying to test to begin with.Love the avatar. Link to comment Share on other sites More sharing options...
pakenney38 Posted March 17, 2005 Author Share Posted March 17, 2005 I just thought of something. Could it be that the user is not receiving the policy because he is on a Windows 2000 Workstation? I read somewhere that the software restriction policies only work in Windows XP. Link to comment Share on other sites More sharing options...
wullieb1 Posted March 17, 2005 Share Posted March 17, 2005 Are you setting it via a GPO on a 2000/3 based network?? Link to comment Share on other sites More sharing options...
pakenney38 Posted March 17, 2005 Author Share Posted March 17, 2005 I answered my own question earlier. The policy I'm trying to set only works in XP/2003. I was trying to apply the policy to a Windows 2000 workstation. I can't believe Microsoft would actually expect companies to upgrade their entire lot to XP to get this to work. Link to comment Share on other sites More sharing options...
valter Posted March 18, 2005 Share Posted March 18, 2005 I answered my own question earlier. The policy I'm trying to set only works in XP/2003. I was trying to apply the policy to a Windows 2000 workstation. I can't believe Microsoft would actually expect companies to upgrade their entire lot to XP to get this to work. <{POST_SNAPBACK}>welcome to the club ... what do you think, how Gates became rich Link to comment Share on other sites More sharing options...
un4given1 Posted March 18, 2005 Share Posted March 18, 2005 No, you can restrict the usage of files in Windows 2000. You need to do it under COMPUTER and not USER Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now