M
MartinF
Hello,
When a user tries to log on to the Terminal server he gets one of two
responses:
1. The log on window goes away and the only visible thing is the blue
Win 2000 background - not "blue screen o death". Nothing else happens.
2. The user gets a message saying that the user profile could not be
read and a standard profile was loaded instead.
The problem can be solved temporarely by upgrading the user to
administrator and resetting his session in the Terminal
services-manager.
Other symptoms are that users cannot move or delete files in their own
folders and that they often get applications that shut down due to
memory problems.
I have seen to it so that the registry memory and and the pagefile has
enough allocated memory.
The users has correct rights to the \WINNT, WINNT\SYSTEM32 and user
profiles directories.
I'm going nuts.
Best regards
/Martin
When a user tries to log on to the Terminal server he gets one of two
responses:
1. The log on window goes away and the only visible thing is the blue
Win 2000 background - not "blue screen o death". Nothing else happens.
2. The user gets a message saying that the user profile could not be
read and a standard profile was loaded instead.
The problem can be solved temporarely by upgrading the user to
administrator and resetting his session in the Terminal
services-manager.
Other symptoms are that users cannot move or delete files in their own
folders and that they often get applications that shut down due to
memory problems.
I have seen to it so that the registry memory and and the pagefile has
enough allocated memory.
The users has correct rights to the \WINNT, WINNT\SYSTEM32 and user
profiles directories.
I'm going nuts.
Best regards
/Martin