Windows 2000 Policies - Tilted Forum Project Discussion Community

Drugbug · 05-26-2004, 10:21 PM

Windows 2000 is the server and all the client PC's are Windows XP machines. Now, when a user logs in, he has practically no rights at all. Nothing, zero. What I want to do, is give the users the right to change the Regional Settings in the Control Panel, but obviously I don't want to give them acces to anything else.

Opening Word, as soon as wanting to print preview or change a font, the PC hangs for a while, sending data accross the network like crazy. But another user, belinging to a different domain, doesn't get this problem.

I have like sooo little understanding of networks.

Thanks in advance.

hrdwareguy · 05-27-2004, 06:02 AM

Quote:

Originally posted by Drugbug
Windows 2000 is the server and all the client PC's are Windows XP machines. Now, when a user logs in, he has practically no rights at all. Nothing, zero. What I want to do, is give the users the right to change the Regional Settings in the Control Panel, but obviously I don't want to give them acces to anything else.

At the server, go into Active Directory Users and Computers. Right click the Organizational Unit the users are part of and select Properties. Click on the Group Policy tab. If there is not a group policy already listed, you will need to create a new one. Once created, edit the group policy. Go to User Configuration/Administration Templates/Control Panel. Use the "Show only specified Control Panel applets". Enable this and add the regional settings to it.

Quote:

Originally posted by Drugbug
Opening Word, as soon as wanting to print preview or change a font, the PC hangs for a while, sending data accross the network like crazy. But another user, belinging to a different domain, doesn't get this problem.

Do you have office installed on a network drive or is it installed via a policy?

Drugbug · 05-27-2004, 07:38 AM

Office is installed locally on each PC. The pc's with the office problem, are all NT4 pc's.

There are a crapload of users though. But I will try what you suggested though. Thank you

Let me elaborate on the office problem.

There are 2 types of users. One of these types get this error when trying to print preview or change a font "System log is full" or something along those lines. This happens on every PC, but the other group of users have no problem on that same PC.

hrdwareguy · 05-27-2004, 08:25 AM

Quote:

Originally posted by Drugbug
There are 2 types of users. One of these types get this error when trying to print preview or change a font "System log is full" or something along those lines. This happens on every PC, but the other group of users have no problem on that same PC.

Your first type of user has events going to the Event Log, the other does not. Of the top of my head, I can't tell you where this setting is. Go into the event viewer for each user in the first group and empty it out. That will temporarily fix the problem.

05-26-2004, 10:21 PM	#1 (permalink)
Drugbug Upright	Networking error Windows 2000 is the server and all the client PC's are Windows XP machines. Now, when a user logs in, he has practically no rights at all. Nothing, zero. What I want to do, is give the users the right to change the Regional Settings in the Control Panel, but obviously I don't want to give them acces to anything else. Opening Word, as soon as wanting to print preview or change a font, the PC hangs for a while, sending data accross the network like crazy. But another user, belinging to a different domain, doesn't get this problem. I have like sooo little understanding of networks. Thanks in advance. Last edited by Drugbug; 05-27-2004 at 12:10 AM..

05-27-2004, 07:38 AM	#3 (permalink)
Drugbug Upright	Office is installed locally on each PC. The pc's with the office problem, are all NT4 pc's. There are a crapload of users though. But I will try what you suggested though. Thank you Let me elaborate on the office problem. There are 2 types of users. One of these types get this error when trying to print preview or change a font "System log is full" or something along those lines. This happens on every PC, but the other group of users have no problem on that same PC.