Hi,
I'm running a Windows Server 2003 network with approx. 700 clients. For the last two years or so I've been using the Restricted Groups group policy to allow about 14 users in the 1200-user organization to be local administrators on the clients, mostly for the purpose of installing software. This has worked great up until about a month ago when suddenly these users were not allowed to install software. When I go to a client and check the local users and groups, all of these users are still in the Administrators group, however they are still prevented from installing programs, and I have to log in as administrator in order to do the installation.
My first thought was that a windows update on the clients might have caused this, but I have to admit that 90% of our clients haven't received an update in almost a year. Our servers however do receive regular updates.
Any thoughts?
Thanks!
-dan
I forgot to add that all of the clients are running Windows XP Pro, SP2, with a handful running SP3. The problem exists on both sp2 and sp3 machines.
I'm running a Windows Server 2003 network with approx. 700 clients. For the last two years or so I've been using the Restricted Groups group policy to allow about 14 users in the 1200-user organization to be local administrators on the clients, mostly for the purpose of installing software. This has worked great up until about a month ago when suddenly these users were not allowed to install software. When I go to a client and check the local users and groups, all of these users are still in the Administrators group, however they are still prevented from installing programs, and I have to log in as administrator in order to do the installation.
My first thought was that a windows update on the clients might have caused this, but I have to admit that 90% of our clients haven't received an update in almost a year. Our servers however do receive regular updates.
Any thoughts?
Thanks!
-dan
I forgot to add that all of the clients are running Windows XP Pro, SP2, with a handful running SP3. The problem exists on both sp2 and sp3 machines.