RE: 'must change password at next logon' gets enabled after ADMT migration for each user



Hello Spin,

Thank you for using newsgroup!

As far as I know, the setting of "User must change password at next logon"
is by design and we do not have a method to change it with ADMT. We can
change this post migration for all users with a script. The attribute that
has to get changed is pwdLastSet. You will need to set this to a negative
1. This link has an example for your reference:
<http://www.microsoft.com/technet/scriptcenter/guide/sas_usr_akke.mspx>

New in Windows Server 2003 are security checks whenever various passwords
related API's are used. ADMT uses such API's to set the users password
during user migration. Windows Server 2003 provides a setting to allow an
administrator to prevent tampering of user passwords, and this causes the
behaviors you are observing when migrating users.

This setting is part of the following registry key:
Key: KEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
Value name: SamRestrictOwfPasswordChange
Data type: REG_DWORD

By defining SamRestrictOwfPasswordChange to a value of '0' on all 2003
domain controllers, the LSASS process will allow the ADMT tool to set user
passwords without requiring a password change at next logon.

Enabling Migration of Passwords
<http://technet2.microsoft.com/WindowsServer/f?en/Library/75c15a86-f52d-46dd
-b894-a933ab2024621033.mspx>

Hope the information helps!

Ken Zhao

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.





--------------------
| From: "Spin" <Spin@xxxxxxxx>
| Newsgroups:
microsoft.public.windows.server.active_directory,microsoft.public.windows.se
rver.migration
| Subject: 'must change password at next logon' gets enabled after ADMT
migration for each user
| Date: Thu, 2 Feb 2006 08:06:28 -0500
| Lines: 14
| Message-ID: <44eeccF1oudvU1@xxxxxxxxxxxxxx>
| X-Trace: individual.net 1TS27c7s/MLy0I+Y1ZNgbQl7QJKeQlFlXOv7h7FSNf+f6XfYym
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| X-RFC2646: Format=Flowed; Original
| Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!newsfe
ed01.sul.t-online.de!t-online.de!fu-berlin.de!uni-berlin.de!individual.net!n
ot-for-mail
| Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.windows.server.migration:22270
microsoft.public.windows.server.active_directory:62448
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Experts,
|
| I am doing a migration in AD to Windows 2003 from Windows 2000 using the
| ADMT. I am saving the passwords during the migration by way of a
password
| export service on the source DC, and everything works great. However,
the
| user is tagged with a "must change password at next logon" attribute in
the
| target domain. Is there a way to prevent this from getting enabled or a
| script I can run to run thorough my target AD and un-check that option
for
| each user?
|
| --
| Spin
|
|
|

.



Relevant Pages

  • Re: default domain display at logon
    ... Microsoft Online Partner Support ... | It does matter when you change the registry. ... |> will be in the admt migration code anyway. ...
    (microsoft.public.windows.server.migration)
  • RE: ADMT Computer migration error
    ... Thank you for posting to the SBS Newsgroup. ... the newsgroups are staffed weekdays by Microsoft Support professionals to ... 2> Make sure the ADMT is not loaded in Test Mode. ... 3> An important thing is when doing Migration, please ask client not to log ...
    (microsoft.public.windows.server.sbs)
  • Re: Migration of user accounts from NT4 to 2003 AD
    ... account and the account that runs ADMT have access to it. ... Microsoft Online Partner Support ... |Subject: Re: Migration of user accounts from NT4 to 2003 AD ...
    (microsoft.public.windows.server.migration)
  • Re: ADMT VS 3rd Party Tools
    ... I have performed several migrations with ADMT and several with third party ... > I'm in the Process of doing my second NT 4.0 to Win2kx migration. ... >> Microsoft is providing this information as a convenience to you. ...
    (microsoft.public.windows.server.migration)
  • Re: [Rant] ADMT
    ... Microsoft Online Partner Support ... |> I'm sorry to hear that ADMT tool gives you so much trouble. ... | and finally became absolutely sure you need to run user migration on a DC ... | server or workstation results in a "Cannot stablish session to PES. ...
    (microsoft.public.windows.server.migration)

Loading