General discussion

Locked

profiles nt 4.0

By craig2599 ·
I setup roaming profiles and assigned users to groups, I then assigned security policies to the groups, When a user logs into one workstaion he can access things like the A: drive and cdrom, explorer, If that same person logs into another computer and tries to access these same things it sends an error message back saying that sys admin has restricted this machine and cannot perform that operation. I made sure that the group was put into the admin group on the local workstation and still get the same result. Also if a make a change to the policy it doesn't seem to update till I erase their local profile and then they log back in.
any help would be great.

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

profiles nt 4.0

by elmagoal In reply to profiles nt 4.0

You need to use user manager for domain and not for the local station. IN there you should put a profile path and when the user logon it will map it. You can copy the user manager for domain fron the domain to the work station and do it that way or just do it from the domain controller.

Collapse -

profiles nt 4.0

by craig2599 In reply to profiles nt 4.0

The question was auto-closed by TechRepublic

Collapse -

profiles nt 4.0

by myon In reply to profiles nt 4.0

Profiles are only update when the user logs in. That is the reason it will not refresh until the user logs off and logs back in.

By setting up roaming profiles, I am assuming you mean you set them up in user manager under the user's account. If you only setup roaming profiles and did not setup a mandatory profile to go with it, then the profile is not your problem. When you setup policies, did you setup one for each user and machine? If so, the machine policy is is the problem. Try to find the differences between the workstation that is correct and the one that isn't. If you only set policies for a few machines and not all of them and the one with the problem you did not set up a policy, it is using the default machine policy.
Another way to troubleshoot it is have a person from the same group try both machines. If the problem exists, look at the group policy. I do not believe this is the problem. If a policy is assigned to a group, it should happen on all machines auser from that group logs into.

Also, it is not good practice to make the group a member of the Admins group. It is ok to do it to test the problem, but make sure you remove it when the problem is fixed.

Collapse -

profiles nt 4.0

by craig2599 In reply to profiles nt 4.0

The question was auto-closed by TechRepublic

Collapse -

profiles nt 4.0

by craig2599 In reply to profiles nt 4.0

This question was auto closed due to inactivity

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums