Services & Profiles in XP

  • Thread starter Thread starter Doug Chesner
  • Start date Start date
D

Doug Chesner

I went to that site ( www.blackviper.com ) and I am 99.95% sure I followed
the instructions correctly, yet once I made the extra hardware profiles of
which I had 2 to begin with, and made the changes (in one of the newly
created profiles), to the first service (alerter) when I rebooted the change
was done in all the profiles. So then I began experimenting (sticking with
just the first service listed) and found that no matter what way I went
about it, any change I made was done across the lot (of profiles).

Now I cannot start the service because the password is gone and my admin
password wont work in that service. I noticed that whenever there was a
password (on the login tab of the services properties window) it was quite
long and not one that I had made/set up.

I would like to take advantage of the info on vipers website and experiment
with the settings without messing up my system like I did on my first
attempt.

If I should not be asking for help with this here, please accept my apology
in advance.

Doug
 
oops

ok.....I disabled the service (which I did in just the NEW profile I had
created, but it was then disabled in all of the profiles. And it
specifically said not to alter the main (default) profile, yet it too was
disabled. Then to make matters worse I tried to change the logon from Local
System Account (which had a password, account name etc) to the second one
where you pick the account...and in doing that in an effort to try to
restart the service, I lost the account name and password.


You don't say what you did. Did you read help which has directions.
 
You are aware, and I'm sure you are because you read help (giggle to myself then roll eyes, shake head), that the 1st profile in list doesn't exist. It's there just to be copied. Therefore you copied it twice, didn't you.

Password is ignored for the local service account (although it's only in the developers documentation that snippet of info). It doesn't have one.
 
LocalService Account
The LocalService account is a predefined local account. It has minimum privileges on the local computer and presents anonymous credentials on the network. The name of the account is NT AUTHORITY\LocalService. This account does not have a password. If you specify the LocalService account in a call to the CreateService function, any password information you supply is ignored.

The user SID is created from the SECURITY_LOCAL_SERVICE_RID value.

The LocalService account has its own subkey under the HKEY_USERS registry key. Therefore, the HKEY_CURRENT_USER registry key is associated with the LocalService account.

Generally, the LocalService account has access to resources whose ACLs allow access to this account, Everyone, or Authenticated users. The service cannot share objects (pipes, file mapping, synchronization, and so on) with other applications, unless it creates them using either a DACL that allows a user or group of users access to the object, or a NULL DACL that allows everyone access to the object. Note that specifying a NULL DACL is not the same as specifying NULL. If you specify NULL in the lpSecurityDescriptor member of the SECURITY_ATTRIBUTES structure, access to the object is granted only to processes with the same security context as the process that created the object. For information on specifying a NULL DACL in the security descriptor field, see Allowing Access Using the Low-Level Functions.

The LocalService account has the following privileges:

SE_AUDIT_NAME
SE_CHANGE_NOTIFY_NAME
SE_UNDOCK_NAME
 
Back
Top