NT/2000 account resources
Active Directory, Cabling, DataCenter, Desktop management applications, Desktops, DHCP, DNS, Hardware, Hubs, Management, Microsoft Windows, Network management software, Network monitoring, Networking, Networking services, OS, Routers, Security, Servers, SQL Server, Switches, Tech support
Hi. I have an NT server but Win2K workstations. I have a couple of individuals who cannot log onto their roaming profile on certain workstations. The particular workstations will log them on with a local profile to use the shared resources on the network. On other 2K workstations, they can access everything they need. Other people have no problem logging on, no matter where they log on to. Could this be an account problem, or could the particular workstations not have something they should have? BTW, the hard drive on one of the workstations crashed and I had to reload. I reloaded the OS and all of the drives and network resources that I know of. Any ideas? Thanks in advance.
neo
Software/Hardware used:
Software/Hardware used:
ASKED:
August 24, 2005 11:29 AM
UPDATED:
September 13, 2005 7:37 PM
Answer Wiki:
I've seen general weirdness with roaming profiles in the past but there was no clear answer what was causing it. Usually what fixed it was deleting the local copy of the roaming profile from the offending workstation thus forcing the logon to initiate a full download of that users profile. Failing that you can completely redo the users profile by deleting both the local and server copies but that can be a pain in the butt especially from the users perspective.
HTH
To see all answers submitted to the Answer Wiki: View Answer History.
Check to make sure there is enough room on the workstation to load the roaming profile. The max registry size is configurable, if I remember correctly, and you may need to increase it on those systems, or create a new profile for the user.
One thing to check is that the user has the rights to write to the local workstation, or at least the location where the profile will be kept, otherwise they wont be able to download thier profile.
The only other thing that I can think off is those users who cant log on may have some issues with the user_hive of the registry on those affected PC’s
find a tool that will give you the SID for the useraccount in question and then delete the corresponding SID registry key from the workstation’s registry, it would also be a good idea to clean up the users profiles from the local PC then get the user to log on again.
Come to think of it, if you remove the user profile thought the User Profiles Tab of the system properties, I am pretty sure it will do all this for you, as this is a much more efficient way of removing users from a PC than just deleting the profile.
You might want to try resetting the security on those workstations useing the compatws.inf template, with the local security mmc. this sets the security settings the on the box to be compatible with NT4 workstations.
the defult win2k workstation security settings often lock out users from certain folders and registry settings that they had full control over under nt4.
another but less desirable fix would be to ad those users to the local administrators group on the workstation.
Everytime that I have personally seen this happen is when there is not enough free space on the drive to create the temporary profile.