Solved

Deleted objects in roaming profiles reappear

Posted on 2001-09-05
4
396 Views
Last Modified: 2013-12-28
I have the problem that deleted desktop and start menu objects (files and directories) in user profiles for roaming profiles reappear in later sessions. I observe this effect with NT 4.0 SP4 to SP6 but not with SP3. The reason: If a user logs in at a workstation different from the previous one, these objects are copied from the user profile on the server to the local user profile without clearing the local profile before! Therefore the resulting profile is the sum of the local profile and that on the server instead a pure copy of that on the server.

This way objects in the desktop and start menu deleted by the user at one workstation can reappear, if the user logs in on another workstation containing these objects in the local user profile due to earlier sessions, and distribute in the whole net again like a virus.

What can I do to obtain the behavior like with SP3? Is there any registry key which controls that behavior or any other trick?
0
Comment
Question by:beyer
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 

Accepted Solution

by:
soderkisen earned 200 total points
ID: 6456507
There is a way to solve this. This tweak will delete all local profiles when users with roaming profiles log off.

Open your registry and find the key below:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\
CurrentVersion\Winlogon

Create a new DWORD value, or modify the existing value, called 'DeleteRoamingCache' and edit the value with a REG_DWORD = "1" for enabled (0=disabled).

Good Luck!

0
 
LVL 10

Expert Comment

by:Longbow
ID: 6456530
0
 
LVL 1

Expert Comment

by:Kitekid
ID: 6462360
You can also do this with a policy.  We use this policy on conference room machine so the HD does not fill up with profiles.  
0
 

Author Comment

by:beyer
ID: 6471508
Adding this registry key seems to be a good solution. But the time for login and logout is increased. Usually the server based profile is downloaded only if NTUSER.DAT on the server is more recent than that on the workstation indicating that the last login occurred on an other workstation. With this registry key set to "1" downloading occurs always, which can take much time in case of several hundred profile files.

Furthermore if the network is down temporarely (which happens about every 3 months in our case) during login, the user obtains the default user profile instead the locally cached profile. If the network reappears during the session, the user profile on the server is overwritten with this default user profile during logoff.

Hallo Kitekid: How can I solve this problem with a policy?
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question