w3.bethelministries.org

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Configure Auto-Login ======

In case of Windows 10 computer on an Active Directory domain, you need to edit the Registry to setup auto login. A domain administrator can manually add these registry keys or if you need to repeat this procedure on a lot of computers you can also create a Group Policy Object to automatically add the registry keys.
To add the registry keys for auto login. Type regedit in the search box and select the registry editor.
Navigate to  ''HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon''
Add/Modify the following key if they doesn't already exit
^Name  ^Type  ^Data  ^
|AutoAdminLogon  |REG_SZ (string)  |1  |
|DefaultDomainName  |REG_SZ (string)  |bethelministries.org  |
|DefaultUserName  |REG_SZ (string)  |checkin@bethelministries.org  |
|DefaultPassword  |REG_SZ (string)  |//[[protected:supersecretpassword|supersecretpassword]]//  |


Restart the computer for the changes to take effect.

====== Change the Shell ======


In Windows, the registry for each user account and administrator account can be set up to start a user-specific shell. There are three keys that must be set up. The first two are generic for all users. This article refers to the keys as "Key1," "Key2," and "Key3" for simplicity.

**Key1** is a string value. When Windows starts, Key1 is called and the default Windows shell is started. However, if the default value is changed to ''USR:Software\Microsoft\Windows NT\CurrentVersion\Winlogon'', Windows looks in the ''HKEY_Current_User'' key to start a specific shell for the user logging on. If the specific user shell is not found, Key2 is called and a default shell is started.
    Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\IniFileMapping\system.ini\boot\Shell
    Type: REG_SZ
    Value: SYS:Microsoft\Windows NT\CurrentVersion\Winlogon

**Key2** provides a default shell if the user shell application cannot be found. When you select a shell component for a Microsoft Windows Embedded configuration, Key 2 is set up to the shell application as the default shell.
    Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell
    Type: REG_SZ
    Value: Explorer.exe (or this can be a different default application)

**Key3** sets up a shell for the current user or logged-on user. Thus, the only way to change a particular user's shell is to log on to the user account and create this registry entry.
    Key: HKEY_Current_User\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell
    Type: REG_SZ
    Value: c:\windows\system32\account shell.exe, where account shell.exe is the name of the application

===== How It Works =====

When the user logs on, Windows uses **Key1** to determine which key holds the shell information. Normally, Windows uses **Key2** next. However, if the value of **Key1** is changed to ''USR:Software\Microsoft\Windows NT\CurrentVersion\Winlogon'', Windows will use **Key3** for the user logging on to start the user's specific shell.

Changing the registry key values in a system with a registry already set up is fairly straightforward. The challenge is how to do this in Windows Embedded, where the registry is set up during the First Boot Agent (FBA) process.

HKLM keys can be set up in Target Designer because they are computer specific. Setting up the HKCU keys, however, is impossible in Target Designer because the accounts will not be created until after FBA runs. The user account and administrator account components create only the accounts, user names, and passwords. These components cannot be used to set up a specific shell. The only solution is to set up the specific shells after the Windows Embedded image has completed the FBA process.
w3.bethelministries.org

User Tools

Site Tools

Page Tools
