Windows Legacy OS forum

General discussion

installed tweak ui and now i can't log on to windows

by stevemo / June 25, 2004 1:05 AM PDT

except as "guest". the only thing i changed in the logon category, using tweak ui, was check the box to "parse autoexec.bat at logon". now, the only option i have when the logon window comesup is guest. no administrator logon or my own. so i don't have administrator rights to correct the problem. i'm a single user on a stand alone system running windowsxp. i used to boot directly into windows without any logon required.

Post a reply
Discussion is locked
You are posting a reply to: installed tweak ui and now i can't log on to windows
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: installed tweak ui and now i can't log on to windows
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Collapse -
Re: installed tweak ui and now i can't log on to windows
by Albertv / June 25, 2004 1:31 AM PDT

Login as the administrator and uninstall tweak ui. or go back to a earlier time in system restore.

Collapse -
Re: installed tweak ui and now i can't log on to windows
by webdeveloper99 / June 25, 2004 1:58 AM PDT

we can't log on to windows anymore either,but we did not install tweakui. I just thought you may know this one too:in winxp 2002, i started getting the ntoskernel error message that this file needed to be replaced. So, i changed keyboards and mouse and the error message did not return. Only one prob,tho, now my passwords do not work. The unit was set up to allow 3 different passwords to log on to the same machine. And when we were getting the ntoskernel err-mess,we could not reach the screen where we type in our passwords. Any help would be appreciated. TIA

Collapse -
Re: installed tweak ui and now i can't log on to windows
by Cetin Denislam / June 25, 2004 2:12 AM PDT

You have an absolutely different problem that does not relate with this thread's context. Post again using New Discussion and be more clear about the description. Also, what's your XP version Home or Pro ?

Good Luck,

Cetin


Trying to unweave, unwind, unravel
And piece together the past and the future,


T. S. Eliot

Collapse -
Re: installed tweak ui and now i can't log on to windows
by Cetin Denislam / June 25, 2004 2:02 AM PDT

Probable you unchecked by mistake the next box in that screen.

Press Ctrl Alt Del. Does a Logon screen come up ? If so, type Administrator and pray that the password is blank.


Good Luck,

Cetin


Trying to unweave, unwind, unravel
And piece together the past and the future,


T. S. Eliot

Collapse -
Re: installed tweak ui and now i can't log on to windows
by webdeveloper99 / June 25, 2004 2:20 AM PDT

yes,we tried that procedure,but we discovered that the administrator screen does require a passw,but the person that used that screen is on vacation.E.G.,we don't know the password for administrator. Is ther any other way to get the password screen to recognize our passwords,because when i typed my password in it did not log on to winxp2002. The others using it don't remember their passw.

Collapse -
(NT) (NT) Reread my post again (missing info) and post in new th
by Cetin Denislam / June 25, 2004 2:27 AM PDT
Collapse -
Some ''learning'' if interested:
by Cursorcowboy / June 25, 2004 2:38 AM PDT
PART I

1. Ordinarily, the Administrator account is hidden from view and only appears on the Welcome screen in the following situations:

a. No other administrative user accounts exist.

b. The computer is started in Safe Mode (pressing F8 during startup).

c. The Administrator account is logged on and Fast User Switching is used.

d. Pro users can log on as the Administrator, but HE users only in Safe Mode because it is prevented by account restrictions. If the Welcome screen is enable, a Pro user presses the key combinations Ctrl+Alt+Delete one time and then by entering the password created when the account was setup.

Note: By default, the Administrator password in the Home Edition is blank and cannot be used for logging on locally or through a network connection. Because this account exist on almost every computer running XP, hackers might attempt to break into the computer using it -- they already know the name and only need a password.

2. It will happen to the best of us -- someday when logging on, you draw a blank. Windows offers two tools for this dilemma:

a. Password hint - available by click the question mark icon which appears after clicking a name on the Welcome screen. However this is not available if the Welcome screen is not used.

b. "Password Reset Disk" - allows anyone without a password to use it to change a user password. Users probably should have and keep one in a secure location. However, this disk is not useful if a computer is joined to a domain. Nor will it or the hints be very useful if one is not created first.

3. A user is better off using a Limited or a Power User account for everyday processes and use the Administrator account only when needed to perform administrative tasks in XP Pro, which cannot be setup in HE -- well it could but even if it appeared on the Welcome screen, it would be unusable:

a. At the command prompt, type lusrmgr.msc, and then press Enter to access Local Users And Groups.

b. In the console tree, click Groups. Double-click the Administrators group and remove all accounts except Administrator.

c. Open the User or Power User groups and then click Add, to add each of the accounts just removed.

4. Don't like the name Administrator in XP Pro -- change it:

a. At the command prompt type secpol.msc to open Local Security Settings or double-click the Local Security Policy shortcut in the Control Panel's Administrative Tools folder.

b. Open Local Polices\Security Options and then in the details pane, double-click Accounts: Rename Administrator Account, and type a new name.

Note: Because HE users cannot use this snap-in, change the user name by launching the Windows 2000-style User Accounts. At the command prompt, type control userpasswords2, and then press Enter. Select Administrator, click Properties and change only the user name, not the full name.

5. XP includes several features to ensure that a computer and the applications and devices installed work correctly. These features help solve problems resulting from adding, deleting, or replacing files that an operating system, applications, and devices require in order to function. Most of these features are available on all three versions. The recovery feature or features used depends on the type of problem or failure encountered. Please read the Microsoft Developer Network (MSDN) article, subject "Description of the Windows XP Recovery Console (Q314058)."

a. Backup [Q302894] - used when needing to restore data file previously saved. It is available on all versions of XP but, is not installed by default on the Home Edition.

b. Device Driver Roll Back [Q306546] - used when a device driver has been recently updated and cause system unstability (other than a printer driver). It restores all system and application settings back to those that were in effect at a point in time being specified by the user. Affects no other files or settings. Printer drivers cannot be restored using it (See: Steps to Manually Remove and Reinstall a Printer Driver (Q135406)).

c. Disable the Device [Q244601] - used when installing and the specific hardware devices causes problems. (Control Panel, Device Manage, "the device" and check the Disable Device in Properties).

d. Last Known Good [Q307852] - used when suspecting that a change made before restarting the computer is causing it to fail. It restores the registry settings and drivers that were in effect the last time the computer started successfully.

e. Safe Mode and System Restore [Q315222] - used when the system still works. It uses only basic files and drivers (mouse, except serial mice; monitor; keyboard; mass storage; base video; default system services; and no network connections). Then use System Restore to restore all system and application settings back to those that were in effect at a time when the system was working optimally.

f. System Restore ]Q304449] - used when device drivers have recently been updated using Device Driver Roll Back did not restore stability. It restores all system and application settings back to those that were in effect at a point in time being specified by the user. Affects no other files or settings.

g. Recovery Console [Q307654] - used when restarting the computer with the installation CD and when prompted during the text-mode setup, the Recovery Console is started by pressing R. It starts, using only basic files and drivers (mouse, except serial mice; monitor; keyboard; mass storage; base video; default system services; and no network connections). The following changes can be made to start the computer:

(1) Enable or disable device drivers or services.

(2) Copy files from the installation CD for the operating system, or copy files from other removable media. For example, copy an essential file that had been deleted.

(3) Create a new boot sector and new master boot record (MBR), which might be needed if there is problems starting from the existing boot sector.

WARNING: A password must be set for the Administrator if the Recovery Console is run. However, thanks to information at "TheElderGeek" site, steps are provided to edit the system registry that negates the password requirement for accessing the Recovery Console.

h. Automated (not Automatic) System Recovery (ASR) [Q818903] - used after all other attempts at recovery fail, or a damaged hard drive has been replaced. Previously used Backups sets must have been created using Automated System Recovery. It restores all disk signatures, volumes, and partitions on the disks required to start the computer. ASR then installs a simplified installation of Windows and automatically starts a restoration using the backup sets previously created. Not available on the XP Home Edition.

Note: Be advised, if a full backup has been performed after SP1 is installed, SP1 is then uninstalled, a restore is then performed, expect big troubles, [Q328035].

i. Windows Installation ("Setup" compact disc) [Q310760] & [Q307848] - used when the computer cannot be started in Safe Mode, neither Last Known Good nor Recovery Console was successful, and there are no backup sets to use with Automated System Recovery.

j. Please be advised of the following:

Microsoft recently announced the availability of Windows XP Service Pack 1 (SP1). Initially, owners of HP Pavilion home PCs and Compaq Presario 6300 series desktop PCs installed with Windows XP were recommended to delay installation of SP1. The reason for this recommendation is that SP1 was discovered to be incompatible with the PC system recovery tool.

To resolve this incompatibility, HP developed a new patch named
"SP1RcvryFix.exe". This patch can be installed before or after installing XP SP1 to correct the incompatibility with the PC system recovery tool.

6. Supplemental reading:

a. "Using System.alt to Recover the System Hive (Q151247)."

b. "HOW TO: Re-Create a Missing Automated System Recovery Floppy Disk (Q299526)."

c. "An Error Message Is Displayed When You Attempt to Use the Automated System Recovery Wizard (Q302700)."

d. "Icons, Favorites, E-Mail Messages, and Customization Is Missing After Upgrade to Windows XP Professional (Q307229)."
Note: This occurs if you created a new user account during Setup and you are logged on as the new user. If the Recovery Console is installed, installing/download the updates.

e. "HOW TO: Configure Recovery Techniques in Windows XP (Q307973)."

f. "How to Disable a Service or Device that Prevents Windows from Starting (Q310602)."

PART II

1. During Setup, the Administrator account is created automatically as a member of the Administrators group on the workstation or member server and when the screen "Who will use this computer?" was displayed and a name entered, they retain full administrative privileges without password by default. The Administrator account can never be deleted, disabled, or removed from the Administrators local group, ensuring that you never lock yourself out of the computer by deleting or disabling all the administrative accounts.

Note: Since User accounts created during Setup are initially created with Computer administrator access and password, which means they have complete control over a computer and can gain access to and modify all user accounts on a computer, launch User Accounts from the Control Panel and individually select each account and supply a password, change the picture, and optionally change the account type -- such as Computer administrator and Limited account types limiting what other family members/users are authorized to do. Click Start, Help and Support, type safe mode in the Search box and read how to create/change an Administrator account password.

2. Every user has an account (a record that consists of all the information that defines a user and includes the user name and password required for the user to log on, the groups in which the user account has membership, and the rights and permissions the user has for using the computer and network and accessing their resources) that allow the user to access resources on a local computer or domain. If the account is specific to a local computer, the user will not be able to access network based resources unless the resources have been configured to allow Anonymous access. If the account is domain based, the user will be able to access network resources from the local computer. However, his or her permissions as a user of network resources might be quite different than his or her rights on the local computer. Two user accounts, Administrator and Guest are created automatically when Windows is installed.

Administrator can install software, configure printers, join the computer to a domain, and after the computer has been configured. Log on only as the Administrator to perform administrative tasks.

Guest accounts can be used to allow different users to log on and access local resources without having to create an account for each user. It can also be enabled to simplify file and printer sharing with other Windows-based computers configured in a workgroup environment. Otherwise, it is recommended that Guest accounts be turned off, Q300489).

Note: Guest account users normally do not have access to the Internet unless they are allowed on a computer which is already connected by dial-up or the computer is connected to the Internet using cable, DSL, or the system is on a network.

a. Except for the Administrator and Guest accounts, Local User accounts are not created automatically when Windows is installed. Instead, an account must be created by a member of the Administrators group after the installation is complete. Only a domain-level Administrators and Account Operators can create domain accounts. User accounts, which include information such as the user's name, alias, password, and unique security identifier (SID), enable users to log on to the network or local computer and to access local and network resources. Domain or local user can manage permissions on resources on the local computer -- as long as the user has change permission rights on the resource.

b. To create, delete, and manage user accounts, Administrators use the User Accounts in Control Panel -- the Local Users and Groups snap-in to the Microsoft Management Console (if the user account is local to a particular computer) or the Active Directory Users and Computers snap-in (if the account is to participate in a domain) (Q279783). For more information about creating, deleting, and managing user accounts, see "Local Users and Groups" in the Windows Help and Support Center.

3. User's group and account type depend on whether a member is part of a network domain or is a part of a workgroup (stand-alone computer). Steps to perform tasks differ:

Warning: Must be logged on as an administrator or a member of the Administrators group in order to complete this procedure. In addition, if a computer is connected to a network, network policy settings may prevent this procedure from being completed "Use the Group Policy Editor to Manage Local Computer Policy (Q307882)."

a. When a computer is part of a network domain, users are assigned to user groups and are granted the rights and permissions granted to the group.

b. When a computer is part of a workgroup or is a stand-alone computer, users are assigned types of user accounts and are granted the rights and permissions associated with that account.

4. There are three fundamental levels of security granted and are granted to end users through membership in:

Note: By default, the predefined and used security templates are stored in systemroot\Security\Templates. Setup security.inf is a computer-specific template that represents the default security settings that are applied during installation of the operating system, including the file permissions for the root of the system drive.

a. ADMINISTRATORS - is the most secure option, because the default permissions allotted to this group do not allow members to modify operating system settings or other user's data. However, user level permissions often do not allow the user to successfully run legacy applications. The members of the Users group are only guaranteed to be able to run programs that have been certified for Windows. As a result, only trusted personnel should be members of this group. Ideally, administrative access should only be used to:

(1) Install the operating system and components (such as hardware drivers, system services, and so on).

(2) Install Service Packs and Windows Packs.

(3) Upgrade the operating system.

(4) Repair the operating system.

(5) Configure critical operating system parameters (such as password policy, access control, audit policy, kernel mode driver configuration, and so on).

(6) Take ownership of files that have become inaccessible.

(7) Manage the security and auditing logs.

(8) Back up and restore the system.

b. POWER USERS - are provided primarily backwards compatibility for running non-certified applications but have more permissions than members of the Users group and fewer than members of the Administrators group. Power Users can perform any operating system task except tasks reserved for the Administrators group. The default permissions that are allotted to this group allow this group's members to modify computerwide settings. Power User can:

Note: If non-certified applications must be supported, then end users will need to be part of the Power Users group.

(1) Run legacy applications, in addition to Windows certified applications.

(2) Install programs that do not modify operating system files or install system services.

(3) Customize systemwide resources including printers, date, time, power options, and other Control Panel resources.

(4) Create and manage local user accounts and groups.

(5) Stop and start system Services, (click to see an example screenshot) which are not started by default.

Note: Power Users do not have permission to add themselves to the Administrators group. Power Users do not have access to the data of other users on an NTFS volume, unless those users grant them permission.

Warning: Running legacy programs often require modification to access certain system settings. The same default permissions that allow Power Users to run legacy programs also make it possible for a Power User to gain additional privileges on the system, even complete administrative control. Therefore, it is important to deploy certified programs in order to achieve maximum security without sacrificing program functionality. Programs that are certified can run successfully under the Secure configuration provided by the Users group. Since Power Users can install or modify programs, running as a Power User when connected to the Internet could make the system vulnerable to Trojan horse programs and other security risks.

c. USERS - is the most secure because the default permissions allotted to this group do not allow members to modify operating system settings or other users' data and provides the most secure environment in which to run programs. On a volume formatted with NTFS, the default security settings on a newly installed system (but not on an upgraded system) are designed to prevent members of this group from compromising the integrity of the operating system and installed programs:

(1) Users cannot modify systemwide registry settings, operating system files, or program files.

(2) Users can shut down workstations, but not servers. Users can create local groups, but can manage only the local groups that they created.

(3) They can run certified Windows programs that have been installed or deployed by administrators.

(4) Users have Full Control over all of their own data files (%userprofile%) and their own portion of the registry (HKEY_CURRENT_USER).

Note: User-level permissions often do not allow the user to successfully run legacy applications. Only the members of the Users group are guaranteed to be able to run Certified for Windows applications. Users will not be able to run most programs written for prior versions of Windows, because they did not support file system and registry security (Windows 95 and Windows 98) or shipped with lax default security settings (Windows NT). If problems are encountered in running legacy applications on newly-installed NTFS systems:

a. Install new versions of the applications that are certified for Windows.

b. Move end users from the Users group into the Power Users group.

c. Decrease the default security permissions for the Users group which can be accomplished by using the Compatible security template.

5. Compatible (Compatws.inf) - default permissions for workstations and servers are primarily granted to three local groups: Administrators, Power Users, and Users. Administrators have the most privileges while Users have the least. Because of this, you can significantly improve the security, reliability, and total cost of system ownership by:

a. Making sure that end-users are members of the Users group.

b. Deploying applications that can be run successfully by members of the Users group, who can successfully run applications that take part in the Certified for Windows program. However, applications probably cannot be run that are not certified in a User context. If non-certified applications must be supported, there are two options:

(1) Allow members of the Users group to be members of the Power Users group.

(2) Relax the default permissions that are granted to the Users group.

c. Since Power Users have inherent capabilities, such as creating users, groups, printers and shares, this can be relaxed in order that the default User permissions allow end-users to be members of the Power Users group and this is precisely what the Compatible template is for. The Compatible template changes the default file and registry permissions that are granted to Users in a manner that is consistent with the requirements of most non-certified applications. Additionally, since it is assumed that the administrator who is applying the Compatible template does not want end users to be Power Users, the Compatible template also removes all members of the Power Users group.

Warning: The Compatible template should not be applied to domain controllers. For example, do not import the Compatible template to the Default Domain policy or Default Domain Controller policy.

Note: Security template (located in %windir%\Security\Templates) settings can be viewed text files.

6. Secure (Secure*.inf) - defines enhanced security settings that are least likely to impact application compatibility. For example, the Secure templates define stronger password, lockout, and audit settings.

7. Highly Secure (hisec*.inf) - templates which are supersets of the secure templates that impose further restrictions on the levels of encryption and signing that are required for authentication and for the data that flows over secure channels and between SMB clients and servers. For example, while the Secure templates cause servers to refuse LAN Manager responses, the Highly Secure templates cause servers to refuse both LAN Manager and NTLM responses.

8. System root security (Rootsec.inf) - specifies the new root permissions introduced with Windows. This template can be used to reapply the root directory permissions if they are inadvertently changed, or the template can be modified to apply the same root permissions to other volumes. As specified, the template does not overwrite explicit permissions that are defined on child objects; it propagates only the permissions that are inherited by child objects.

9. No Terminal Server user SID (Notssid.inf) - the default file system and registry access control lists that are on servers grant permissions to a Terminal Server SID. The Terminal Server SID is used only when Terminal Server is running in application compatibility mode. If Terminal Server is not being used, this template can be applied to remove the unnecessary Terminal Server SIDs from the file system and registry locations. However, removing the access control entry for the Terminal Server SID from these default file system and registry locations does not increase the security of the system. Instead of removing the Terminal Server SID, simply run Terminal Server in Full Security mode. When running in Full Security mode, the Terminal Server SID is not used.

10. Special Groups - When a prior version of Windows is upgraded resources with permission entries for the Everyone group (and not explicitly to the Anonymous Logon group Win2000) will no longer be available to Anonymous users after the upgrade, which is an appropriate restriction. If access must be permitted in order to support pre-existing applications, the Anonymous Logon security group and its permissions must be explicitly added. However, in some situations where it might be difficult to determine and modify the permission entries on resources hosted, the Network access: Let Everyone permissions apply to anonymous users security setting, could be changed.

a. Interactive - contains the user who is currently logged on to the computer. During an upgrade to XP, members of the Interactive group will also be added to the Power Users group so that legacy applications will continue to function as they did before.

b. Network - contains all users who are currently accessing the system over the network.

c. Terminal Server User - when Terminal Servers are installed in application serving mode, this group contains any users who are currently logged on to the system using Terminal Server, with default permissions already assigned and are able to run most legacy programs.

Note: The same default permissions that allow a Terminal Server User to run legacy programs also make it possible for a Terminal Server User to gain additional privileges on the system, even complete administrative control. Applications that are certified for Windows can run successfully under the secure configuration provided by the Users group. Local accounts created on the local computer are created without passwords and are added to the Administrators group by default. If this is a concern, use Security Configuration Manager to allows membership of the Administrators (or any other group) with Restricted Groups policy.

11. Domain - "Configuring" (Q305553) and "Change a Computer Name or Join" (Q295017).

Warning: The most fundamental difference between the Professional edition and Home Edition is that only Professional can join a network domain. A computer running Home Edition can be a member of a workgroup (a home network), but not a domain. This distinction may sound trivial, but it?s important if you need the features available to computers that can join a domain. Expert Zone, by Sharon Crawford.

a. Open User Accounts in Control Panel.

b. On the Users tab, under Users for this computer, click the user account name, and then click Properties.

c. On the Group Membership tab, click the group wanted, and then click OK.

d. Notes:

(1) New users should not be added to the Administrators group unless they will perform these tasks only.

(2) To include a user in more than one group, open Local Users and Groups in the User Accounts dialog box, and on the Advanced tab click the Advanced button. Double-click Groups and then add the user to the group(s) wanted.

e. Should an error be rendered that an account already exists, even though it is not reflected in either the User Accounts tool in Control Panel or on the Welcome screen, it may have existed but is now disabled (Q297221).

12. Workgroup (a stand-alone computer)

a. Open User Accounts in Control Panel.

b. Click the user's account name and click Change the account type.

c. Click the type of account wanted, and then click Change Account Type.

Warning: If there is only one user on a computer with a computer administrator account, the account type cannot be changed because there must be at least one person with a computer administrator account at all times.

13. Password - Computer security includes the use of strong passwords (up to 127 characters long) for network logon and the Administrator account and can be the weakest link in a computer security scheme. Strong passwords are important because password cracking (which uses one of three approaches: intelligent guessing, dictionary attacks, and automation that tries every possible combination of characters) tools continue to improve and the computers used to crack passwords are more powerful than ever. For a password to be strong, it should be at least seven characters long, because of the way passwords are encrypted, the most secure passwords are seven or 14 characters.

a. A password should contain characters from each of the following three groups:

(1) Letters (uppercase and lowercase) A, B, C... (and a, b, c...)

(2) Numerals 0, 1, 2, 3, 4, 5, 6, 7, 8, 9

(3) Symbols (all characters not defined as letters or numerals) ` ~ ! @ # $ % ^ & * ( ) _ + - = { } | [ ] \ : " ; ' < > ? , . /

b. Have at least one symbol character in the second through sixth positions.

c. Be significantly different from prior passwords.

d. Not contain your name or user name.

e. Not be a common word or name.

f. To ensure security, passwords must be used carefully. These recommendations will help protect a password(s):

(1) Never write down the password.

(2) Never share a password with anyone.

(3) Never use a network logon password for another purpose.

(4) Use different passwords for network logon and the Administrator account.

(5) Change a network password every 60 to 90 days or as often as required in specific environments.

(6) Change a password immediately if you think it has been compromised.

(7) Be careful about where a password is saved. Some dialog boxes, such as those for remote access and other telephone connections, present an option to save or remember a password and this option should not ever be selected.

(8) Create and Use a Password Reset Disk for a Computer That Is Not a Domain Member (Q305478).

14. Running Windows XP as an Administrator makes the entire system totally vulnerable to Trojan horses and other security risks and the simple act of visiting an Internet site can be extremely damaging to it since an unfamiliar Internet site may have Trojan horse code that can be downloaded and executed. When logged on with administrator privileges, a Trojan horse could do anything, like reformat the hard drive, delete files, create new user accounts with administrative access, and a host of other things. When logged on as a member of the Users group, routine tasks can be performed including running programs and visiting Web sites without exposing a system to unnecessary risk. As a member of the Power Users group, routine tasks can be performed, programs can be installed, printers added, and allows use of most Control Panel items. When needing to perform Administrative tasks, such as upgrading the operating system or configuring system parameters, log off and log back on as an Administrator. When needing to log on as an administrator the runas command may be used:

Note: The article [Q294676] states you can run programs as a different user than the currently-logged on user provided the RunAs service (installed by Windows and started by default automatically, and accept only password authentication) as well as the Secondary Logon service is running -- the same services with different names. This step-by-step article describes how to enable and use the Run As command.

a. In Windows Explorer, click the executable program file wanted.

b. Press and hold the SHIFT key, right-click the program icon, and then click Run as.

c. To log on using an Administrator account, click The following user.

d. In User name and Password, type the Administrator account name and password.

e. Else, create a shortcut for easier access to use the runas command (password required):

(1) Right-click the Desktop, point to New, and then click Shortcut.

(a) For a command prompt with administrator credentials, type runas /user:ComputerName\administrator cmd

(b) For a Computer Management with administrator credentials, type runas /user:ComputerName\administrator "mmc %windir%\system32\compmgmt.msc"

(2) Click Next, type a name for the shortcut, and then click Finish.

15. Please review the information:

a. "Account Configuration for XP Pro".

b. "You Cannot View HTML Help Files When Special Characters Appear in Your Username (Q307823)."
Collapse -
Some "learning" if interested
by kbxtra / March 7, 2005 8:56 AM PST

Cursorcowboy this just what I have been looking for. It gives me all the steps to take concerning Admin.Acct. and more. Got anymore good sites to recommend for XP Pro. Way to go!!!!!

Popular Forums
icon
Computer Help 47,885 discussions
icon
Computer Newbies 10,322 discussions
icon
iPhones, iPods, & iPads 3,188 discussions
icon
Security 30,333 discussions
icon
TVs & Home Theaters 20,177 discussions
icon
HDTV Picture Setting 1,932 discussions
icon
Phones 15,713 discussions
icon
Windows 7 6,210 discussions
icon
Networking & Wireless 14,510 discussions

Big stars on small screens

Smosh tells CNET what it took to make it big online

Internet sensations Ian Hecox and Anthony Padilla discuss how YouTube has changed and why among all their goals, "real TV" isn't an ambition.