Windows Server

eva · Guest

Hello all,

I'm tying to migrating user accounts between two Windows 2000 forests using
ADMT v2. The users have roaming user profiles on a Samba server shared as
\\servername\sharename$\folder1\username\.profil\username etc.

In the log file it says:

ERR3:7438 No NTUser.DAT file for user account was found in
\\servername\C$%H\.profil\\username. The roaming profile can not be
translated.

I'm in no luck trying to find more information on ERR codes for ADMT, nor
makes it sense that the profile path looks like it does in the log file.

- Ideas anyone?

Vincent Xu [MSFT] · Guest

Hi,

The migration process is slightly different for local and for roaming
profiles. You need to select the profile migration option during the user
account migration process.

From the error message we may learn that ADMT try to connect C$%H on the
profile server. Please check that if the share folder is shared as C$%H.
Since this issue happens to the profile server which is SAMBA, I think you
post your issue on it org site may be a good choice.

Hope the information helps.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

--------------------

eva · Guest

Hi,
Thank you for your answer. Yes I choose to migrating roaming profiles
running ADMT, and yes maybe the answer is to find at the SAMBA site, but I'm
also hungry for more information on ADMT and how it really works - and, why
not how to read the log file - that is what does the error codes mean. In
troubleshooting there is a big difference to me if I look at an "access
denied" or a "network path could not be found".

I've been testing. I got different information on profile path in the log
depending on whether I connect to the user home directory share before
running ADMT or not.

In the case I connect to the share the path is as described earlier. In the
case I don't connect the path is \\servername\profile\%usernamne% which is
the path user accounts is normally configured for, although this has been
changed and is not the present configuration. There is no share named C$H%.

A question: how is ADMT connecting to the profile of a user account during
translation? As far as I understand the administrative account running ADMT
must be able to access the user account profile share.

The SAMBA server is configured so the user connecting to the server only
will get his own home folder. The profile directory for each user is located
in the user home directory and shared in the same manner, each user account
uses the same profile path: \\servername\profile\%username%

In order to make the administrative account able to access the user profile
we've changed the profile path and sharing the main home directory for
administrative access.

Mvh

Eva

"Vincent Xu [MSFT]" <v-xuwen@online.microsoft.com> wrote in message
news:mdcLD$MuFHA.780@TK2MSFTNGXA01.phx.gbl...

Vincent Xu [MSFT] · Guest

Hi Eva,

Maybe I didn't explain clearly. When ADMT tried to miagrate profile, he
needs to read NTUser.DAT. From the error message, we can learn that the
user profile path is invalid, because "." can be used in the folder name.
However, we cannot use it as the first letter of the folder name. Also, "\"
is also a reserved letter for file/folder names.
from your description, I know you didn't shared the folder as such name on
the Samba server, that's why I recommed you post your issue at Samba side.
At Windows side, I suggest you check the user profile path in the Admin
tools called AD users and computers. Right click a user and select
"Properties". Click "Profile" and check the settings of "ProfilePath"

You also may run a command such as "LDIFDE -d "DC=YourDomain,DC=com" -f
C:\AD.ldf" and attache the ad.ldf file. I'll check the profilepath for you.

Hope the information helps.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

--------------------

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1