Xp Home User/Profile priviledges: Administrator ==> Limited ==> Administrator ... Problem

From: J Kester (funwear@wt.net)
Date: 02/18/03 

From: funwear@wt.net (J Kester)
Date: 17 Feb 2003 21:53:17 -0800

Hi All ... request your help again ... Once again my enthusiasm
exeeded my expertise ...

For security reasons, I added a new administor TYPE account ( i.e
USER2) on my "XP Home" machine. I changed properties of my
default/daily user account (i.e USER1) to "limited".

I found out QuickBooks ( 2001 basic) will not work with "limited" XP
profile, so I changed USER1 profile/account back to full ADMINISTRATOR
priviledges. Well, QB01 does not recognize USER1 as having full ADMIN
priviledges, even though WinXp Home says it does. QB01 says the USER1
account has limited priviledges and to contact "my" network
administrator ... ( that be me, and I don't know what to tell me ...
lol).

I do have to admit I tried a hack posted in a news group about setting
USER1 profile/account as a "poweruser account" which did NOT work as
expected

>==== Type in Start Run control userpasswords2 ====<

After this hack, the USER1 account did not even show up as XP user
account; even though the CPU rebooted to that profile and all programs
worked nominally except for QB01. Fast user switching/UserAccounts
only listed USER2 & Guest accounts.

I had to use another hack found in NewsGroups to get USER1 to even
show up again ..

>==== net localgroup users USER1 /add =====<

Once got USER1 to be listed again, switched to USER2 (ADMIN
priviledges) and changed USER1 account to "ADMIN" PRIVILEDGES. Even
after reboot, Win Xp Home shows USER1 as ADMIN priviledges but QB01
says does not.

Your distinguished assistance would be appreciated ....

Jeff K.
###############################################################

Relevant Pages

  • Re: Group Policy per user
    ... Copy the Registry.pol file that is located in the %Systemroot%\System32\GroupPolicy\User folder to a backup location. ... You can see that the changes that you made in step 3 are not implemented because you have logged on to the computer as an administrator. ... Log in to the computer with the built in Administrator account. ... Copy the NTUSER.DAT files for User1 and User2 to a different folder. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Environ("username")
    ... The same behaviour you can observe if you create an account as a XP ... account to User2 (via standart tools of XP windows administrator). ... Environalways returns User1 not User2. ...
    (microsoft.public.excel.programming)
  • Re: User Profile migration / relocation
    ... Then login user1 again, I found there will be some ... ntusers.ini and ntuser.dat cannot be copied to the new profile etc. ... You need first create an account in Domain B. ... > Use USMT - the user state migration tool. ...
    (microsoft.public.windows.server.migration)
  • Re: Administrator as Only User ?
    ... Data folder for user1 and there are folders there. ... The standard security practice is to rename the account, set a strong password on it, and use it only to create another account for regular use, reserving the Administrator account as a "back door" in case something corrupts your regular account. ... While using a computer with limited privileges isn't the cure-all, silver bullet that some claim it to be, any experienced IT professional will verify that doing so definitely reduces that amount of damage and depth of penetration by the malware. ...
    (microsoft.public.windowsxp.help_and_support)
  • Getting Rid of Multiple Administrators
    ... After cleaning all the ... User1 was the administrator. ... Administrator account that were causing the OS anomalies in the ...
    (microsoft.public.windowsxp.security_admin)
Loading