Userprofile problem

[Andy Allred [MS]]

How are you cloning the images? Are you using Ghost?

 

[Andy Preston]

I have an XPe disk image that we have been using successfully for the
last several months and have manufactured about 50 units from this
image. We have recently build ten units that all have the same problem.
The hardware is all the same as far as we can tell.

The problem is that the userprofile is modified. On all the previous
units that worked OK, the userprofile was

c:\Documents and Settings\Administrator

on the units that do not work the userprofile is

c:\Documents and Settings\Administrator.NAI-TXXXXXXXXXXXX

NAI-tXXXXXXXXXXXXX is the Computername

Has anyone else encountered this and know why the Computername is
appended to the userprofile. The username is still administrator, but
any application settings are lost since they are looking in the wrong
directory.

thanks,

Andy Preston

 

[Andy Preston]

How are you cloning the images? Are you using Ghost?

They have EWF enabled on the C:, I resealed the master, and then we just
use a disk duplicator to make the clones. This is a homebuilt unit that
does a direct sector copy from the master to the clone. It's a system
that has successfully made over a 100 units, this particular master has
made around 50 units successfully.

thanks,

Andy

 

[Alexander Suhovey]

Has anyone else encountered this and know why the Computername is

appended to the userprofile.

Basically it happens when user logs on first time while folder with name
same as this user's name already exist in %systemroot%\Documents and
Settings\ . Though, I do not know how it applies in your case.
Read this for more details:
http://support.microsoft.com/default.aspx?scid=kb;en-us;228445

The username is still administrator, but
any application settings are lost since they are looking in the wrong
directory.

I suppose hardcoded paths can not be considered as programming best
practice...



Al.

 

[Andy Preston]

Basically it happens when user logs on first time while folder with name
same as this user's name already exist in %systemroot%\Documents and
Settings\ . Though, I do not know how it applies in your case.
Read this for more details:
http://support.microsoft.com/default.aspx?scid=kb;en-us;228445

OK, assuming that the domain name/user name problem is causing this
mechanism to kick in I don't know how this would ever have worked. We've
built over 50 units from this master with no problems. The
UserName/UserDomain are generated by FBA and are NAI-XXXXXXXXXXXX. These
will be unique and will never be the same, and certainly not the same as
the machine I made the master on. So if this were the case then I would
have always had this problem.

Does anyone know how this Username/UserDomain is created ?

I suppose hardcoded paths can not be considered as programming best
practice...

It's not my application this is causing a problem for

thanks,

Andy