Discussion Locked

NT4 / W2K Roaming Profiles

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

I have a network with a PDC, BDC/Print Server, 20 NT Workstations (all NT4) and a Windows 2000 Workstation. The computers are set up in a kiosk environment where a single user could walk up to any machine (except the servers) and logon.

My problem is this; on all of the NT boxes, the roaming profiles work great, on the 2000 box, everything on the profile seems to work with the exception of the printer connections. When a user logs on, the printers on the print server do not show up. You need to go to the Add Printer wizard to reinstall the printers manually ? for each user.

I logged on to both the local box (and on the domain) with a temp user account, made all the changes to the work environment as needed, mapped the printers, mapped the drive where the Home Directories are located and set up the default applications and shortcuts. I then logged off and logged back on as the administrator. I then copied the temp user profile to the All User profile and gave Everyone permission to use it. When I log back on with the temp account, the printers are there, along with the other changes, when any other user logs on, the printers are not there, but all of the other changes are? When I log on to one of the NT Workstations, make changes, (like change the color of the desktop), those changes propagate to the 2000 machine fine - just not the printers.

What am I missing?

5 replies

by mm212

Instead of copying to the "All Users" profile, copy your temp profile to the "Default User" profile.

by larry23

I initially tried this, and tried it again... If I log on to any NT4 machine and make changes to a user profile and then log off, when I log on to the W2K machine, all the chages appear, except there are no networked printers as there were on the NT4 box.

by larry23

This didn't help. It would also cause a security problem in my particular environment.

by larry23

As suggested in a reply, coping the temp profile to the default (both local and domain wide) user profile made no changes to the problem.

This discussion is closed to new replies.