System Variables Identify the Environment
Many system variables are available within Windows 7, and you'll see these often when using the command prompt and Windows PowerShell. They are useful in identifying specific information about the environment, without actually knowing the current environment. As a simple example, every computer has a computer name, but the computer names are different. However, the system variable %computername% holds the value of the local computer's computer name.
System variables are easy to identify. They always start and end with a percent symbol (%). An easy way to view the value of any variable is by using the echo command in the following format:
Echo %variableName%
Table below shows many of the commonly used system variables and their value.
Some commonly used system variables
Variable | Value |
%windir% %systemroot% | Both %windir% and %systemroot% identify the folder where Windows was installed, typically C:\Windows. |
%systemdrive% | The folder where the system boot files are located, typically C:\. |
%computername% | The name of the local computer |
%username% | The name of the user logged on to this session |
%date% | Holds the value of the current date in the format ddd mm/dd/yyyy The first three letters are an abbreviation of the day such as Mon, Tue, Wed, and so on The remaining format is all numbers with mm for the month, dd for the day, and yyyy for the year |
%time% | Holds the value of the current time in a 24-hour format as hh.mm.ss.ms |
%errorlevel% | Indicates whether the previous command resulted in an error If it didn't have an error, the value is 0. |
%ProgramFiles% | Points to the location of the Program Files folder, which is normally C:\Program Files. |
%Public% | The location of the Public folder, typically C:\Users\Public. |
In this tutorial:
- Working with the Command Prompt
- Starting and Ending a Command Prompt Session
- Easy ways to invoke administrator Command Prompt sessions
- Starting Command Prompt at a Particular Folder
- Strings with Spaces Need Quotes
- Cmd.exe vs. Command.com
- Commands Are Not Case Sensitive
- Starting Command Prompt and Running a Command
- Cmd.exe and Other Command Prompts
- Using AutoRun to Execute Commands When Command Prompt Starts
- Using Cmds Command-Line Syntax
- Using Commands
- Type /? for help
- Starting Programs
- Open Windows Explorer at the current Command Prompt folder
- Using File-Name and Folder-Name Completion
- Use a different completion character
- Using Wildcards
- Editing the Command Line
- Using Command Symbols
- The Redirection Symbols
- The Pipe Symbol
- The Command Combination Symbols
- Pausing or Canceling Commands
- Simplifying Command Entry with Doskey Macros
- DOSKEY Saves Typing
- System Variables Identify the Environment
- Viewing Environment Variables
- Modifying Environment Variables
- Predefined Environment Variables
- Customizing Command Prompt Windows
- Setting the Window Size and Position
- Setting the Window Size and Position Visually
- Selecting a Font
- Setting Colors
- Setting Other Options
- Copy and paste in the command prompt window
- Navigating from the command prompt
- Printing a list of filenames
- Commands Use Paths
- Identifying Executables
- Modifying the Path to Executables
- Modifying the Path with the GUI
- Changing the Current Path with CD
- Changing the Current Path with Windows Explorer
- Capturing the Output
- A Sampling of Commands
- Dir
- Copy
- XCopy
- SET
- NET USE
- SystemInfo
- DriverQuery
- Echo
- Advanced Shell Commands
- Creating a Batch File
- Scheduling a Batch File
- Creating Scheduled Tasks with a Script
- Using Windows PowerShell and the PowerShell ISE
- Windows PowerShell ISE
- PowerShell Commands
- Verbs and Nouns
- Sending Output to a Text File
- PowerShell Syntax
- Variables Created with a $ Symbol
- Comparison Operators
- Parentheses, Brackets, and Braces
- Running PowerShell Scripts
- PowerShell Execution Policy
- Changing the Execution Policy
- Looping
- Collections
- Creating a PowerShell Script
- Documenting Scripts
- Using PowerShell Commands
- Getting Help on PowerShell
- Using WMI_Cmdlets
- Getting Details on an Object
- Querying Information on Specific Objects
- Terminate Applications with Win32_process
- Formatting Output with the -f Format Operator
- Filtering the Output with the Where-Object Command
- Using the IF statement
- Using the Switch Statement
- Script Reusability