Discussion Locked

group policy implementation

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

my question is that i followed all the steps in for creation of a group policy in Win2k Advanced Server viz..

1. Create a pdc. (althoug in system properties\network identification it shows domain controller) name of teh domain punetelecom.local. name of server admin.punetelecom.local.

2. created OUs, created a Non-Management Users group.

3. placed users in this group and created group policy of these users in this OU in AD users and computers.

4. result : - group policy doesnt apply, i know the order of implementation of group policy with the default domain policy being applied first..but i have tried disabling the default domain policy too

nothing worked.

question WHERE I AM GOING WRONG ?

second question

is it possible to change the my documents path of EACH user to a location in the server shared directory like a user with account JOHN shud have his My documents directory routed to \\admin\documents\JOHN

this needs to be done for 25 users.. ? what to do..

trial: - have tried this logon script

net use z: \\admin\documents\JOHN.
but one problem again all the user's my documents path needs to be changed..

how to do the tasks mentioned above...

kindly excuse my descriptive question, but iwanted to clearly specify my problem bfore pasting a question..

any workable reply is eagerly awaited

Bhargav

7 replies

by dwdino

Assuming this is an all W2K setup:

1) Verify that the apply permission is set to the appropriate user group, by default this will be authenticated users.

2) Remember that clients must be a member of the domain and rebooted for the changes to take effect. (you can also run gpupdate, see url)

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsnetserver/proddocs/entserver/RefrGP.asp

3) Verify that pc's are listed in the "Computers" container in "AD users and computers"

4) Choose an obvious change for testing purposes. Something like disabling Windows Update is an easy test. (User Config -> Admin Templates -> Start Menu)

On changing the home directory:

If you wish to use "net use" it needs to be constructed as follows:

net use z: \\admin\documents\%username%

When this command is run, Windows will replace "%username%" with the users login name.

It is cleaner and easier to use a Policy for this purpose. (User Config -> Windows Settings -> Folder Redirection) Right click on My Documents and choose properties. Choose basic config. Put the path in the supplied box ("\\admin\documents\%uusername%"), and you will be good to go.

by beermonster

Hi,

1) In win2k there is no such thing as a 'pdc' (although there is a component that acts like a pdc, specifically to service pre win2k clients, known as the pdc emulator). win2k uses the 'multi master model' whereby all win2k dc's are equal. This removes the single point of failure in a purely win2k domain.

2)okay...

3 and 4)I take it that you added users to the group, then placed that group into an OU. This is a confusing area, and one that I only understood myself when I tested it.GPO's DO NOT APPLY TO GROUPS - only to specific user or computer accounts. Groups exist for two reasons, firstly so that you assign security using them (eg to files and folders), and so you can use 'GPO filtering'. That means that if the user account is at the bottom of a nested OU structure, and it is not possible because of your OU design to use block inheritance \ no override, then the GPO security settings can be modified (where appropriate) to stop one or more GPO's in the chain from beingapplied to your users. Let's say that I have OU1 and below that OU2. All of my users reside in OU2, and receive the GPO settings from both OU's. However, there is a subset of 10 users for whom I don't want the OU1 settings to be applied. I can add them to a security group, and deny that group the read and apply grouppolicy rights on the OU1 GPO. Essentially GPO filtering just gives you more scope in the way you design your OU structure.

As to the my documents issue, the previous respondentis bang on the money and my advice would just be a repetition of his.

Hope this helps....

by desktop jinx

To the above, I can only add the obvious -- that policies listed under the Computer Configuration branch do not apply to users.

This discussion is closed to new replies.