Re: User and profile problems

This is very weird,

I've elevated the user to administrator under the DLU and it has logged in
without a problem..

What I don't understand is before I rebuilt the image, the DLU was able to
change the user rights without the problem!

Is there a GPO or something somewhere? or is the installation broken?

"Neil" wrote:

Thanks.. what I thought! Will take a look at that.

"R. McCarty" wrote:

Sounds like a Permissions/SID (Security IDentifier) issue. Changing
access from Administrator down to User may restrict access to the
Documents and Settings\Profile or the NTUser.Dat. In either case XP
would then create a Domain ( or MachineName ) extension to a new
replacement profile. Believe it takes the machinename first, then if that
profile is inaccessible it moves on to a numbering scheme 00x, 002.

"Neil" <Neil@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:594AE6F3-38B3-4D44-A5CF-61292E7D8821@xxxxxxxxxxxxxxxx
Hi,

Firstly, I appreciate that this could be a Novell problem, but equally is
could be an XP one so I need some ideas from an XP point of view to help
solve this problem..

We use Novell Client to enable our users to login.. part of this uses
something called Dynamic Local User Policy (DLU) which enables us to
dynamically create accounts on the local machine as required..

In our case, we use 2 setup accounts which create a 'Localuser' username
and
'Localuser' profile folder in Docs and Settings. This user is created
initiallty with administrator rights which can be controlled from the DLU.
We
logon once with the first setup account, do bits and pieces, reboot and
log
on with the second account and finish off. Once complete, the users are
then
free to use the machines.

When a user logs on, the DLU changes the user access level to User from
Administrator. Now, up until now this has worked ok - the User logs on
dynamically to the local machine and attaches to 'Localuser' profile in
XP.
Recently I've rebuilt our image and since then this has not worked.
Instead
it creates a second profile folder called Localuser.Machinename
(machinename
varies), ignoring the 'Localuser' profile which was initially setup but
still
uses the 'Localuser' username.

File rights are a condiseration, but within the DLU you can assign file
rights per user which enables me to control how much access the user can
have. Using this, I've given fill rights to the c:\documents and
settings\localuser folder.

In general, what causes Windows to ignore an already created profile
folder
connected to a username; Instead creating a second replacement one. Are
there
any Group Policy (GPO) considerations?

Another thing I've noticed is before the rebuild you would login with the
first setup account, it would create the profile, account and perform the
initial first log in setup. You would then login with the second setup
account and it would go straight in without doing the setup. After the
rebuild, the first log in setup appears after each login - though the
profile
problem, where a new folder is created, doesn't occur here but only when
the
student logs in and the rights are changed by the DLU.

Now again, I appreciate that this could be a Novell problem, but equally
it
could be an XP setting that I need to change.

Any help would be very much appreciated.

Neil



.

Relevant Pages

  • Re: User and profile problems
    ... would then create a Domain (or MachineName) extension to a new ... profile is inaccessible it moves on to a numbering scheme 00x, ... we use 2 setup accounts which create a 'Localuser' username ... on with the second account and finish off. ...
    (microsoft.public.windowsxp.general)
  • Re: User and profile problems
    ... would then create a Domain (or MachineName) extension to a new ... profile is inaccessible it moves on to a numbering scheme 00x, ... we use 2 setup accounts which create a 'Localuser' username ... on with the second account and finish off. ...
    (microsoft.public.windowsxp.general)
  • Problems creating a new profile using PST folders
    ... We are trying to configure outlook and setup a profile using a predefined ... pst file and also to not have an email account defined i.e. it will be setup ... ;-- The URL of Exchange Web Services Form Directory page used to create Web ...
    (microsoft.public.outlook.installation)
  • Syncing Outlook data across 2 Windows OSes
    ... I imagine you'll have no trouble understanding the setup below, ... the profile files on a common 'files only' partition, ... Connector add-in from the default set of folders. ... if you ever choose to change the default account associated with the ...
    (microsoft.public.outlook.installation)
Loading