Microsoft is considering supplying a possible fix for this oddity with the release of Service Pack 3 for Windows 2000.įorcing a refresh of the Group Policy by using the Secedit command won’t help fix the problem. However, for some odd reason, Terminal Services will go ahead and apply the rest of the Group Policy.
Terminal Services will assume the SID is valid, assume the group membership list is current, and won’t apply Folder Redirection. However, Terminal Server will then check the registry and notice that the user has a profile with a SID already associated with it. If you’re using Folder Redirection and delete the profiles with Windows Explorer, the next time a user logs on, Terminal Server will re-create the directory structure stored for the user. This presents a problem if you plan to use Folder Redirection in Group Policy. By just deleting the profile directory, you don’t delete the associated entries and Security IDs (SIDs) in the registry. But profile information also exists in the server’s registry in several locations. When you use Windows Explorer to delete locally cached user profiles on Terminal Services servers, you only delete the physical directory structure where the profiles are located. But first, let’s go over the problems that can occur when you use Explorer for the cleaning task, instead of DELPROF. In this Daily Feature, I’ll show you what DELPROF is and how it works. In this case, the DELPROF utility is your best bet for quickly and effectively cleaning up the mess caused by locally cached profiles. Using Explorer for this cleanup job can actually create a host of new problems. However, the easiest way isn’t always the best. The easiest way to delete these files is by using Explorer. You must remove these profiles often in order to prevent them from filling up your server’s hard drive. If you administer Terminal Services or Citrix MetaFrame, you know that locally cached user profiles can cause a mess on your server’s hard drive by chewing up valuable space.
0 kommentar(er)
