Force Local Profile Option in Windows 2000

Article translations Article translations
Article ID: 817361 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

SYMPTOMS

Profile upload problems may occur where there is a chance that the roaming profile of a user is being uploaded from more than one computer at the same time. This may also occur for example, when a Terminal Server farm publishes a desktop that itself starts programs published on other server farms, or when a user logs off and several published applications quit at the same time.

Microsoft Windows XP and Microsoft Windows 2003 have a Group Policy option that permits a computer to ignore roaming profiles. The "Only allow local profiles" feature is now available in Windows 2000. Applying this policy at Terminal Servers that publish programs that do not require roaming settings will reduce the chances of profile upload failures arising from simultaneous file access.

CAUSE

This problem may occur if the policy is exposed to the Group Policy Editor through a new System.adm file. This new file will be inherited by new Group Policy objects created on the computer that contains the hotfix. However, the file must be copied to existing Group Policy objects before it can be set in them. The new policy is located here:
Computer Configuration\Administrative Templates\System\Logon\Only allow local user profiles

RESOLUTION

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time     Version        Size        File name
   ------------------------------------------------------------
   30-Mar-2003  11:29   5.0.2195.6688     42,256   Basesrv.dll
   14-Feb-2003  11:49   5.0.2195.6660    222,992   Gdi32.dll
   30-Mar-2003  11:29   5.0.2195.6688    710,928   Kernel32.dll
   04-Feb-2003  11:15   5.0.2195.6661     29,264   Mountmgr.sys
   30-Mar-2003  11:29   5.0.2195.6669    333,072   Msgina.dll
   30-Mar-2003  11:29   5.0.2195.6685    476,944   Ntdll.dll
   28-Mar-2003  10:19   5.0.2195.6696  1,694,912   Ntkrnlmp.exe
   28-Mar-2003  10:19   5.0.2195.6696  1,693,952   Ntkrnlpa.exe
   28-Mar-2003  10:19   5.0.2195.6696  1,714,944   Ntkrpamp.exe
   28-Mar-2003  10:19   5.0.2195.6696  1,672,448   Ntoskrnl.exe
   21-Mar-2003  12:43   5.0.2195.6692     90,232   Rdpwd.sys
   28-Mar-2003  11:50   5.0.2195.6680  3,988,992   Sp3res.dll
   30-Mar-2003  11:27                    753,702   System.adm
   30-Mar-2003  11:29   5.0.2195.6688    380,176   User32.dll
   30-Mar-2003  11:29   5.0.2195.6697    385,808   Userenv.dll
   30-Mar-2003  11:26   5.0.2195.6697  1,628,688   Win32k.sys
   11-Mar-2003  06:15   5.0.2195.6682    181,008   Winlogon.exe
   14-Feb-2003  11:49   5.0.2195.6655    243,472   Winsrv.dll
				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.

MORE INFORMATION

For more information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the following article number to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product

Properties

Article ID: 817361 - Last Review: February 27, 2014 - Revision: 2.6
APPLIES TO
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Advanced Server SP3
  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2
  • Microsoft Windows 2000 Service Pack 3
  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Service Pack 3
Keywords: 
kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbsysadmin kbwin2ksp4fix kbprb kbwin2000presp4fix kbfix kbbug KB817361

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com