Terminal Server users are reportedly getting new profile

[Harin$Akshi]

Recently I have been noticing that new users are getting some issues with the network login and it is said that each time they login back they are getting a slower network login times. The reason behind the slower login times is said that it is caused by the terminal server, so why is that such issue happening why is it that it is reportedly giving problems when a new user logs in the network so why is that so do you all have any idea why is that such thing happening? I mean you all have a good knowledge on it so please do answer it for me.

[Wguy2008]

It happens usually when the user somehow ends up in the Guests group so for that reason windows completely locks the portions of the registry and also it does ot allow the user to log off so that is one situation where such thing can happen hence it is better to create our own user account in it and try logging in the system I think we must create some certain permission parameters such that such type of things are completely avoided here. So that’s a small response from my side I hope you all liked it and hence that’s what I want to say here.

[Carley]

Yes agreed with you but one thing that I would like to add here is that the permission standards that you were talking about can also result into such kind of issue. in case if the permissions get screwed up and If the user loses Full Control over their profile folder which is there in the documents and Settings folder, then the system will have to create a new profile with each logon. So that’s also a reason why the new user profile is being generated by the system. so hope you have got the necessary suggestions from my side read it carefully and implement it accordingly.

[addie]

I think so there would be some problem with the registry key HLM\Software\Microsoft\Windows\CurrentVersion\NetCache\PurgeAtNextLogoff
I am specifying that because one of my friends was also having the same problem and how he encountered the problem was by removing the offending SID's because his previous registry was full with all the SID's that were giving a new profile with for each user during the login and hence he tried removing the offending SID's that did the trick for him so I ask you also to try the same problem hope it helps you to some extent.

[Harin$Akshi]

Hey thanks for giving me that suggestion that really helped me a lot, so thanks for all the efforts that you have given and let me tell you that your suggestion did gave me the actual solution that I was looking for so all the cresit goes to you for giving me the exact solution so appreciate your efforts for giving meso9em valuable tips on the problem, so that’s what I want to say here. Thanks a lot again.