MSCONFIG is a Windows system configuration utility used to manage the startup applications. While this utility does its job of listing all applications (both enabled and disabled), it doesn’t have an option to delete disabled applications even they no long exist as they may already have been uninstalled from the system.

Now, these disabled applications could stay there forever without having any effects on the system but the list could grow very long. If you don’t want this list to continue to grow, you could remove the unwanted items from the list by editing the Windows registry. There are also a number of third party utilities to help take care of these unwanted items on the list. I prefer to directly edit the registry as some of these tools might prove to be harmful.

Locations of the entries in MSConfig:

The enabled/checked items are populated from the following locations:

HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Windows \ CurrentVersion \ Run

HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Run


HKEY_CURRENT_USER \ Software \ Microsoft \ Windows NT \ CurrentVersion \ Windows

Values named Run & Load

The disabled entries are present in these locations:

HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shared Tools \ MSConfig \ startupreg

HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shared Tools \ MSConfig \ startupfolder

To remove these entries, you first have to start the registry editor (regedit.exe), backup the folder MSConfig before deleting the unwanted items’ folders.

After doing this, all the deleted entries should disappear from the MSConfig startup.

Be careful NOT to break your system. Once again remember to backup before deletion.

Mapping network shares from a network is a pretty easy thing to do. The standard command for this in windows is:

net use x: \\{host}\{share} {password} /u:{unsername} /p:{no|yes}


x = drive letter (a-z)

p = persistent (yes means re-map after system restart and no means the opposite)

Assuming you want to automate such action mapping more shares from different networks, you will want to use the FOR loop in a batch script. These steps will show my aproach:


1.) The first thing to do is create and place all your share information (host, share, password, username and drive letters in a file and name the file anything you want. To suite my purpose, I’ll jsut name the file “dat2″ without any file extention. The content should look like this:






2.) Create a batch script to disconnect all existing network drives. Let’s name this file “delmap.bat”


REM ======================= Begin Of Script =============================

@echo off

REM Check and disconnect all existing network drives


if exist t: net use /del t: /y

if exist u: net use /del u: /y

if exist v: net use /del v: /y

if exist w: net use /del w: /y


goto :EOF

REM ======================= End Of Script =============================


3.) Now, we can create the main script “NetShare.bat” with the following contents:


REM ======================= Begin Of Script =============================


@echo off

REM To avoid error messages, check and disconnect all existing network drives

REM by calling another batch file named delmap.bat.


call “%~dp0\delmap.bat”

REM To avoid unexpected errors, the system needs to wait 3 seconds after

REM disconnecting all existing drives before re-mapping the network resources.

REM All pre-defined parameters in the file (dat2) will be fetched line by line using

REM the (for) loop. There are 6 columns in the file (dat2) separated by commas (delims).

REM The first is the line numbers (not needed). That is the reason why the tokens is

REM defined from 2-6. The pre-defined variables (hostN, userN, paswd, drive and share) are

REM passed one by one from the ‘sub routine’ (:var) to process the mapping of the drives.


ping -n 3>nul

for /F “tokens=2-6 delims=,” %%g IN (%~dp0dat2) do call :var %%g %%h %%i %%j %%k

goto end


set hostN=%1

set userN=%2

set paswd=%3

set drive=%4

set share=%5

net use %drive%: \\%hostN%\%share% %paswd% /U:%userN% /P:no

goto :EOF



REM ======================= End Of Script =============================




Both files NetShare.bat and delmap.bat are included in the dowload below:


You need to create  your share information (dat2) by following the first step above.

This tutorial will show you how to reset and change local administrator password on remote windows systems. This was tested on Windows XP and Windows 2003 server but should work on Vista/7/2008 operating systems.


1.) Download the official PsTools from microsoft directly or click here

2.) Extract the downloaded file to a folder called PsTools

3.) Just copy pspasswd.exe to your executable path “C:\Windows\System32″

4.) Open the prompt command line (star -> Run (type “cmd” + OK) and type in the following:

pspasswd \\{IP-Address} -u administrator -p {OldPasswd} administrator {NewPasswd}


{OldPasswd} = Old Password

{NewPasswd} = New Password

{IP-Address} = System IP Address

Reset and Change Local Administrator Password On Remote Windows System

Typing “pspasswd” displays its usage syntax.

Usage: pspasswd [\\[computer[,computer,[,...]|Domain]|@file] [-u Username [-p Pa

ssword]]] Username [NewPassword]

     computer    Direct PsPasswd to perform the command on the remote

                 computer or computers specified. If you omit the computer

                 name PsPasswd runs the command on the local system,

                 and if you specify a wildcard (\\*), PsPasswd runs the

                 command on all computers in the current domain.

     @file       PsPasswd will change the password on the computers listed

                 in the file.

     -u          Specifies optional user name for login to remote


     -p          Specifies optional password for user name. If you omit this

                 you will be prompted to enter a hidden password.

     Username    Specifies name of account for password change.

     NewPassword New password. If ommitted a NULL password is applied.

Have fun ;-)

Written on February 23rd, 2012 , Recent Posts, Vista, Windows, Windows 7, Windows Logon, Windows Vista, Windows XP

As in many situations the network administrator has task of connecting to remote systems to perform his duties. Ocassionally, the remote tasks become more difficult and frustrating when there are no remote tools available on the system and the remote desktop application is deactivated. Forturnately, Microsoft has provided a means for resolving such problems and therefore restoring back the hope of the administrator.

PsExec is one of the many PsTools Microsoft has provided for network administrors for the sole purpose of system administration. The following steps will show you how to activate RDP remotely from your local computer with the use of PsExec.

1.) Download the official PsTools either from microsoft directly or here

2.) Extract the downloaded file

3.) Just copy PsExec.exe from the extracted location into your executable path ”C:\Windows\System32″.

4.) Open the prompt command line (start -> Run and type “cmd” + OK) and enter the following:

psexec -u {username} -p {password} \\{iP-Address} reg add “hklm\system\currentcontrolset\control\terminal server” /f /v fDenyTSConnections /t REG_DWORD /d 0


{username} = Administrator (must be administrator)

{password} = Administrator’s password

{IP-Address} = System IP Address

psexec remote desktop activation

If not already enabled, use the following commands to enable RDP traffic through the windows firewall:

psexec \\ {iP-Address} netsh firewall set service remoteadmin enable

psexec \\ {iP-Address} netsh firewall set service remotedesktop enable


To deactivate RDP, just change “0″ to “1″.

Typing “psexec” displays its usage syntax.

Usage: psexec [\\computer[,computer2[,...] | @file][-u user [-p psswd]][-n s][-l][-s|-e][-x][-i [session]][-c [-f|-v]][-w directory][-d][-<priority>][-a n,n,... ] cmd [arguments]

computer Direct PsExec to run the application on the computer or computers specified. If you omit the computer name PsExec runs the application on the local system and if you enter a computer name of “\\*” PsExec runs the applications on all computers in the current domain.

@file Directs PsExec to run the command on each computer listed in the text file specified.

-a Separate processors on which the application can run with commas where 1 is the lowest numbered CPU. For example, to run the application on CPU 2 and CPU 4, enter: “-a 2,4″

-c Copy the specified program to the remote system for execution. If you omit this option then the application must be in the system’s path on the remote system.

-d Don’t wait for application to terminate. Only use this option for non-interactive applications.

-e Does not load the specified account’s profile.

-f Copy the specified program to the remote system even if the file already exists on the remote system.

-i Run the program so that it interacts with the desktop of the specified session on the remote system. If no session is specified the process runs in the console session.

-l Run process as limited user (strips the Administrators group and allows only privileges assigned to the Users group). On Windows Vista the process runs with Low Integrity.

-n Specifies timeout in seconds connecting to remote computers.

-p Specifies optional password for user name. If you omit this you will be prompted to enter a hidden password.

-s Run remote process in the System account.

-u Specifies optional user name for login to remote computer.

-v Copy the specified file only if it has a higher version number or is newer on than the one on the remote system.

-w Set the working directory of the process (relative to the remote computer).

-x Display the UI on the Winlogon desktop (local system only).

-priority Specifies -low, -belownormal, -abovenormal, -high or -realtime to run the process at a different priority. Use -background to run at low memory and I/O priority on Vista.


In XP, we used to have the ability to Ctrl-Alt-Del twice at the welcome screen to get to the standard login screen (where you get to type in your username & password). This is gone in Windows 7… Well not really ;-).

For the average user, it could be sometimes frustrating to have user accounts all over the logon screen. First, this reveals the user name making the system a little unsecure. Second, it just doesn’t look nice when you have over 30 or more user accounts all over the logon screen in a domain environment.

The good news is, there’s a way to come back to old Windows classic logon screen. Just follow these steps:

1.) Run>type: netplwiz > Advanced > check “Require users to press Ctrl+Alt+Delete”

2.) Run > gpedit.msc > Computer Config\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Do not display last user name > Enabled

Without being so strict, you could make it a little less painful for users by omitting the first step above. The result will still be nice and secure.

It’s slightly different in XP.

That’s it… enjoy!

Related forum:

Written on December 21st, 2010 , Logon Screen, Windows, Windows 7, Windows Logon

OMOTECH Tips & Tricks is proudly powered by WordPress and the Theme Adventure by Eric Schwarz
Entries (RSS) and Comments (RSS).

OMOTECH Tips & Tricks

this blog offers tutorials based on various it-subjects