Jump to content

LocalService account (S-1-5-19) is NOT created


Recommended Posts

Posted

Hi all,

I tried to create an slim-stripped version of unicode WinXP SP3 (Greek).

But, the LocalAccount is not created during install. Add this mean that Services that depend on this account never start.

I am guessing that some additional unicode(?) .dll or .exe is missing and cannot create the S-1-5-19 account.

Does anyone have any idea, which files are needed for creating new users (with unicode support) ?

Any hint to solve this issue would be appreciated.

Thanks in advance.


Posted (edited)

Any hint to solve this issue would be appreciated.

Please read the big red message up your screen.

Edited by Ponch
Posted

vasili0s, Ponch means RED message and attach your Last Session. Have you seen this type of site? I really don't know what you mean by LocalAcccount - please tell us and tell us what your symptoms are indicating a problem. The user accounts that you specify in the Unattended task of nLite are created by the nLite.inf file during install. It can be found in your nLited folder, compressed into NLITE.IN_. You can extract it and see the accounts being created there. Search on the account name. Please tell us more about unicode XP and LocalAccounts. Enjoy, John.

Posted

Guys thanks for the reply, but the nlite does not really mess with the S-1-5-19 account at all. I have seen all .inf/.in_ files and there is no reference to the S-1-5-19 account.

After I found this information from ms: http://support.microsoft.com/kb/307419 , I am guessing that is created from within an .exe or .dll file by default during the installation.

This is really weird problem, but maybe someone have came across this, or knows the low-level setup process.

Posted

Guys thanks for the reply, but the nlite does not really mess with the S-1-5-19 account at all. I have seen all .inf/.in_ files and there is no reference to the S-1-5-19 account.

After I found this information from ms: http://support.microsoft.com/kb/307419 , I am guessing that is created from within an .exe or .dll file by default during the installation.

This is really weird problem, but maybe someone have came across this, or knows the low-level setup process.

vasili0s, please attach your Last Session. Enjoy, John.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...