Moveuser.exe is incompatible with Windows Vista and is replaced by the new Win32_UserProfile WMI functionality

Moveuser.exe is incompatible with Windows Vista and is replaced by the new Win32_UserProfile WMI functionality

Article ID : 930955
Last Review : August 24, 2007
Revision : 4.4
On This Page

SUMMARY

The Windows Resource Kit tool Moveuser.exe is incompatible with Windows Vista. In earlier versions of Windows, Moveuser.exe is used to map an existing local user account profile to a new domain profile when a computer in a workgroup is joined to a domain. Alternatively the tool can also used to map an existing domain account profile to another new domain account profile. However, you cannot use the Moveuser.exe tool to perform these tasks on a Windows Vista-based computer.

Back to the top

RESOLUTION

After you install the update that is described in this article, the User Profile Windows Management Instrumentation (WMI) provider (Win32_UserProfile) is added in Windows Vista. This User Profile WMI provider replaces Moveuser.exe in Windows Vista. The new User Profile WMI provider can be used to map an existing local account profile to a new domain based account. It can also be used to map an existing domain-based account profile to a new domain-based account profile.

Back to the top

Update information

The following files are available for download from the MicrosoftDownload Center:

Windows Vista, 32-bit versions
DownloadDownload the Windows6.0-KB930955-x86.msu package now. (http://www.microsoft.com/downloads/details.aspx?familyid=9106B9D4-BAA8-4C29-A605-A4D09C04A5F3)

Windows Vista, 64-bit versions
DownloadDownload the Windows6.0-KB930955-x64.msu package now. (http://www.microsoft.com/downloads/details.aspx?familyid=D812B06B-0601-4755-98D3-878093CAD40C)For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 (/Feedback.aspx?kbNumber=119591/) How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

To apply this update, you must have Windows Vista installed.

Restart requirement

You must restart the computer after you apply this update.

Update replacement information

This update does not replace any other updates.

File information

The English version of this update 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 item in Control Panel.

Windows Vista, 32-bit versions
File name File version File size Date Time Platform
Profprov.dll 6.0.6000.20515 32,768 16-Jan-2007 03:35 x86
Profsvc.dll 6.0.6000.20515 163,840 16-Jan-2007 03:35 x86
Userprofilewmiprovider.mof Not Applicable 10,702 16-Jan-2007 00:02 Not Applicable
X86_microsoft-windows-profsvc.d_31bf3856ad364e35_6.0.6000.20515_none_24c745098e822984.manifest Not Applicable 691 16-Jan-2007 17:13 Not Applicable
X86_microsoft-windows-profsvc_31bf3856ad364e35_6.0.6000.20515_none_fa4ee34c4ea7bad8.manifest Not Applicable 49,152 16-Jan-2007 17:14 Not Applicable
Windows Vista, 64-bit versions
File name File version File size Date Time Platform
Amd64_microsoft-windows-profsvc.d_31bf3856ad364e35_6.0.6000.20515_none_80e5e08d46df9aba.manifest Not Applicable 695 16-Jan-2007 17:13 Not Applicable
Amd64_microsoft-windows-profsvc_31bf3856ad364e35_6.0.6000.20515_none_566d7ed007052c0e.manifest Not Applicable 49,152 16-Jan-2007 17:19 Not Applicable
Profprov.dll 6.0.6000.20515 49,152 16-Jan-2007 04:42 x64
Profsvc.dll 6.0.6000.20515 180,224 16-Jan-2007 04:42 x64
Userprofilewmiprovider.mof Not Applicable 10,702 16-Jan-2007 00:02 Not Applicable

Back to the top

MORE INFORMATION

Information about how to use the User Profile WMI provider

• The source user profile cannot be private.
• Any folder redirection to a local volume or to a server must be disabled.
• Access to the following settings is not preserved:

• Encrypted files
• Certificates
• The user account picture
• Disable encryption for any files before you map any profile to another new user account profile.
• User saved passwords will not be mapped from the local profile to the domain profile. Therefore, the user will be prompted to reenter these passwords the first time that they access the associated program. For example, the user will be prompted to reenter the password for Windows Live Messenger the first time that they start the program after the profile is moved.
• The User Profile WMI provider is implemented like other WMI interfaces by using WMI tools, scripts, or applications that use the WMI COM interface. For more information about how to use WMI, see theAbout WMI topic at the following MSDN Web site:

http://msdn2.microsoft.com/en-us/library/aa384642.aspx (http://msdn2.microsoft.com/en-us/library/aa384642.aspx)
• To learn specifically about the management functions that the User Profile WMI provider supports, use a repository browsing tool to explore the class in the root CIMV2 namespace.

Visual Basic script examples

• The following Microsoft Visual Basic script example retrieves a user profile object through the user name and the domain and then deletes the user profile object.

strComputer =. Set objAccount = GetObject(winmgmts:{impersonationLevel=impersonate}!   _                            & strComputer & root cimv2:Win32_UserAccount. _                            &Domain='contoso',Name='fabrikam')     Set objUserProfile = GetObject(winmgmts:{impersonationlevel=impersonate}!   _                               & strComputer & root cimv2:Win32_UserProfile. _                               &SID=' & objAccount.SID &') objUserProfile.Delete_

• RoamingPreferenceis the only property that can be set by a user who has administrative credentials. The following Visual Basic script example retrieves and displays information about all the profiles on the local computer.

• To run the Visual Basic script against a remote computer, set the value of the strComputer variable to the name or the IP address of the remote computer. The placeholder RemoteComputerName is used to set the variable in the following example:

strComputer = “RemoteComputerName”.

• When you run this script by using Wscript.exe, one series of message boxes is displayed for each profile. You receive one message box for each profile. You have to click OKto close each message.
• To avoid these message boxes, run the script by using Cscript.exe instead of Wscript.exe. When you use Cscript.exe, the information is displayed at the command prompt instead of as message boxes. To run the following script by using Cscript.exe, type cscript.exe script_nameat the command prompt, and then press ENTER.

strComputer =.Set objWMIService = GetObject(winmgmts:   & strComputer & root cimv2)Set colProfiles = objWMIService.ExecQuery(Select * from Win32_UserProfile)For Each objProfile in colProfiles    Set objSID = objWMIService.Get(Win32_SID.SID=' & objProfile.SID &')    Wscript.Echo======================================================& VBNewLine _        &Sid: & objProfile.Sid & VBNewLine _        &User Name: & objSID.AccountName & VBNewLine _        &User Domain: & objSID.ReferencedDomainName & VBNewLine _        &LocalPath: & objProfile.LocalPath & VBNewLine _        &Loaded: & objProfile.Loaded & VBNewLine _        &RefCount: & objProfile.RefCount & VBNewLine _        &RoamingConfigured: & objProfile.RoamingConfigured & VBNewLine _        &RoamingPath: & objProfile.RoamingPath & VBNewLine  _        &RoamingPreference: & objProfile.RoamingPreference & VBNewLine _        &Status: & objProfile.Status & VBNewLine _        &LastUseTime: & objProfile.LastUseTime & VBNewLine  _        &LastDownloadTime: & objProfile.LastDownloadTime & VBNewLine  _        &LastUploadTime: & objProfile.LastUploadTime & VBNewLine  Next

Back to the top

For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 (/Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates

Back to the top


APPLIES TO
• Windows Vista Enterprise 64-bit Edition
• Windows Vista Ultimate 64-bit Edition
• Windows Vista Business
• Windows Vista Business 64-bit Edition
• Windows Vista Enterprise
• Windows Vista Ultimate

Back to the top

Keywords: 
kbbug kbfix kbqfe kbpubtypekc atdownload kbhotfixserver KB930955

Back to the top

 

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks


You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

AddThis Social Bookmark Button

Leave a Reply

*
To prove that you're not a bot, enter this code
Anti-Spam Image