Windows Default Built-In Administrator

-

Windows Default Administrator account

We have following 4 types of accounts in windows pc.

  1. Standard user
  2. Administrator User
  3. Guest User
  4. Build-In Administrator


First three accounts we know and see it regular. Guest account is the one with very limited privileges for a guest session, usually we disable it.

Default Administrator account is the built-in administrator account with very elevated privileges (i.e. Super User).  Usually and by default this is account is disabled and hidden.
 

Difference between Built in Administrator and Administrator User


Administrator user – Is an un-elevated administrator account. This is controlled by UAC (User account control) by default. Though this account has complete access, any changes that require elevated admin rights will be prompted by UAC to do so.


Built-in Administrator – This is an elevated administrator account, will not be monitored by UAC. This is hidden by default. This account has a well-known SID.


To enable default administrator account


  1. Go to start menu
  2. Select Command Prompt
  3. Right click and run as ‘Administrator’
  4. Now command prompt will be opened
  5. Type the following command
          Net user administrator /active:yes



Security Warning

It’s not advisable to enable the built-in Administrator account and use it for daily use. Since this account has a well know SID (Security Identifier) intrusion programs can make harm to the computer by using this account.  In case you have reasons to use this account use it with a very strong password.

Command to see the SID of users 

wmic useraccount get name,sid 

You will see the list of users in the system with SID of each of the users.


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\windows\system32>wmic useraccount get name,sid
Name            SID
Administrator   S-1-5-21-1180699209-877415012-3182924384-500
Guest           S-1-5-21-1180699209-877415012-3182924384-501
HomeGroupUser$  S-1-5-21-1180699209-877415012-3182924384-1002
 


Comments

Post a Comment

Popular posts from this blog

Java NIO2 - Watching a directory for changes. FileWatcherService.

-
Image
File Watch Service The NIO2 WatchService API provides the ability for java code to watch for file modifications in a directory in the filesystem. A WatchService object watches the folder it is registered with and signals the changes detected through event notifications.  Steps to create a WatchService Create a WatchService object (FileSystem.newWatchService()) Register the directories to be watched with the WatchService (WatchService.register()) Watch for file change events (poll()/take() methods) Retrieve the event keys and process them Rest the key and got to step 3 to watch again. Example code Below is a simple working code. import java.io.IOException; import java.nio.file.Path; import java.nio.file.Paths; import java.nio.file.StandardWatchEventKinds; import java.nio.file.WatchEvent; import java.nio.file.WatchKey; import java.nio.file.WatchService; import java.util.List; import java.util.concurrent.TimeUnit; public class FileWatcherTest { private static
More posts »

Log4j multiple WAR files in single EAR configuration

-
Log4j multiple WAR files in single EAR configuration Problem: When you have multiple WAR files under the same EAR with multiple log4j config files in each of the war files, the logging API will pickup the first available config file and ignores the list. i.e, only a single log4j config file applies to entire EAR. Consider the below app app.ear |__admin.war    |__WEB-INF/classes/log4.xml |__web.war    |__WEB-INF/classes/log4j.xml When you deploy this app to the server all logs of two war files admin.war and web.war will go to admin.war' log. The log4j.xml in web.war has no effect here. There are some complex solutions for this like adding a logback, specifying package level log files in log4j configuration etc. Solution The easiest way is configuring the context param in web.xml In your web.xml add the following context param will send the log4j config locations specific to the contexts and fixes this issue. web.war/WEB-INF/classes/log4j.xml <conte
More posts »

SVN File Creation Date

-
SVN Find File creation date. @echo off  REM Thi batch files iterates over svn to print first verison of files REM that is exactly when a file is added into svn set file=%1 if [%file%] == [] (   echo Usage: "%0 <file>"   exit /b ) rem first revision as full text for /F "tokens=1" %%R in ('" svn ls -R %file%"') do ( IF NOT EXIST %%R\NUL (                 @echo %%R                 svn log -r 1:HEAD -l 1 %%R  -q                 ) )
More posts »