Windows 8, 7, Vista, XP, troubleshoot, fix, stop error, Internet Explorer, live, downloads. Windows power users have many ways to launch a Command Prompt or Windows command processor (Cmd.exe) with administrator privileges, rights or credentials. Only the first and hidden win-8 administrator account on Windows 8 (seven, 8.1)brings a full access, by default it is not activated. How to Reset a Windows XP or Vista Password. If you've forgotten your user password for Windows XP or Vista, you can use the hidden Administrator account to reset. Microsoft Windows updates were loaded and now I get the following when I log on to my PC. C:Windows\system32\Config\systemprofile\Desktop is not accessible. Enable the (Hidden) Administrator Account on Windows 7, 8, or 1. Many people familiar with prior versions of Windows are curious what happened to the built- in Administrator account that was always created by default. Does this account still exist, and how can you access it? The account is created in Windows 1. Vista, but since it’s not enabled you can’t use it. If you are troubleshooting something that needs to run as administrator, you can enable it with a simple command. Warning: The built- in Administrator account has a lot more privileges than a regular administrator account—privileges that can easily get you into trouble if you use it regularly. We recommend only enabling the built- in Administrator account if you are certain you need it to troubleshoot a specific problem and then disabling it when you are done. If you’re unsure whether you need it, you probably shouldn’t use it at all. First you’ll need to open a command prompt in administrator mode by right- clicking and choosing “Run as administrator” (or use the Ctrl+Shift+Enter shortcut from the search box). Note that this works the same in all versions of Windows. Just search for cmd and then right- click on the command prompt icon in the Start menu or Start screen. If you are in Windows 8. Start button and choose to open a command prompt that way. Now type the following command: net user administrator /active: yes. You should see a message that the command completed successfully. Log out, and you’ll now see the Administrator account as a choice. Type the following command: net user administrator /active: no. The administrator account will now be disabled, and shouldn’t show up on the login screen anymore. Troubleshoot Slow GPO Processing and Login Speed Impact. Quite often, domain users complain about slow computer startup and login time caused by long processing of Group Policies (GPO). From the user’s point of view, the computer boots for a long time and it seems it hangs up for several minutes on the stage of “Applying computer/user settings“. In this article I will try to collect useful diagnostic tools and methods that allow an administrator to determine the reasons of slow GPO applying on the domain computers. Actually, there are a number of reasons why Group Policies take a long time to be applied: these can be DNS issues, DC availability and the speed of connection to it, wrong configuration of AD sites or replication problems, misconfigured group policies, incorrect scripts, etc. It’s hard to describe an all- in- one algorithm to diagnose all these issues. In this article, we will focus only on the diagnostics of the problems with the GPO and GPClient mechanisms. How to Block Group Policy Inheritance. To make sure that the issue is related to the domain GPO, create a separate OU in the domain and move the problem computer to it. Then using Group Policy Management Console (GPMC. Block Inheritance). Thus, all domain policies will stop to be applied to this container (policies with the Enforced mode enabled are the exception). Today's article is a quick tip on how to troubleshoot problems in Windows 8.1, which you will most definitely run into using Microsoft's shiny new OS. Restart the computer and check if the problem with slow GPO applyingpersists. If it persists, it is likely that the problem is in the computer itself or the local group policies (try to reset them to default ones). How to Display Detailed Information on the Boot Screen. In Windows, you can enable the display of detailed status information that allows users and the administrator to visually understand at what stage of computer loading the greatest delay is observed.
If you enable this policy, the information about GPO components being applied is also displayed. You can enable this policy in the following GPO section: in Windows 7 / Vista : Computer Configuration - > Policies - > System - > Verbose vs normal status messages = Enabledin Windows 8/1. Computer Configuration - > Policies - > System - > Display highly detailed status messages = Enabled. The same parameter can be activated via the registry. To do it, create a DWORD parameter with the name verbosestatus and the value 1 in the registry key HKEY. In the System log, only the events related to the operation of the Group Policy Client (gpsvc) itself are left. To analyze the policy application time, the following Event. IDs will be useful: The events with the IDs 4. GPO application extensions starts and ends. The latter also indicates the total time of the extension processing. For example, on the screenshot below the filtering of Group Policy - > Operational by the Event. ID 4. 01. 6 and 5. In the message of Event. ID 5. 01. 6 you can see the time of this GPO component processing. Completed Group Policy Registry Extension Processing in 1. Event. ID 5. 31. 2 contains the list of the applied policies, and the Event. ID 5. 31. 7 shows the list of the filtered GPOs. Event. ID 8. 00. 0 and 8. And Event. ID 8. 00. Completed computer boot policy processing for CORP\pc. When analyzing the log, pay attention to the time between two neighboring events. It can help to find the problem component. GPSVC Debug Log. In some cases it is useful to enable GPO processing debug log — gpsvc. Using timestamps in gpsvc. GPO components that have been processed for a long time. Group Policy Preferences Debug Logs. Group Policy Preferences extensions can also log the booting of each CSE (Client- Side Extensions) component. CSE debug logs can be enabled in the following GPO section: Computer Configuration - > Policies - > Administrative Templates- > System- > Group Policy - > Logging and tracing. As you can see, the individual settings are available for each CSE. In the policy settings, you can specify the logged event type (Informational, Errors, Warnings or all of them), maximum log size and log location path: User policy trace file %SYSTEMDRIVE%\Program. Data\Group. Policy\Preference\Trace\User. Computer policy trace file %SYSTEMDRIVE%\Program. Data\Group. Policy\Preference\Trace\Computer. Tip. If you don’t have Logging and Tracing subsection in the Group Policy section of your gpedit. GPMC console, download and install Group Policy Preferences ADMX templates and copy Group. Policy. Preferences. PROGRAMFILES%\Microsoft Group Policy to the local folder Policy. Definitions or to the central directory Policy. Definitions in SYSVOL. After collecting the logs, you need to analyze them for errors, and also try to find nearby events, the time between which is different for a few minutes. So in this article, we have considered the main ways to diagnose the slow Group Policy processing on the domain computers. I hope the article will be useful.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |