How to logoff remote desktop sessions via command line tools?

Query the Remote Server for Current Terminal Sessions

To query and list the sessions on the remote session, you could use QUser.exe or QWinsta

1. QUser

QUser command comes with all the latest Windows clients and servers. This will list the sessions of the remote server (or local machine).
NOTE: if you are using Windows XP, you need to add this location into your System path: C:WindowsSystem32DLLCache. To do this, in command prompt, type the following.
SET PATH = %PATH%;C:WindowsSystem32DLLCache;
QUser help shows,

C:Anand>QUser /?
Display information about users logged on to the system.
QUERY USER [username | sessionname | sessionid] [/SERVER:servername]
  username            Identifies the username.
  sessionname         Identifies the session named sessionname.
  sessionid           Identifies the session with ID sessionid.
  /SERVER:servername  The server to be queried (default is current).

E.g.,

C:>quser /server:MyCitrixSVR
USERNAME              SESSIONNAME        ID  STATE   IDLE TIME  LOGON TIME
johndoe               ica-tcp#966        10  Active          7  7/31/2008 3:04 PM
averagejoe            ica-tcp#969         1  Active          9  7/31/2008 3:30 PM
familyman             ica-tcp#984         5  Active       1:06  7/31/2008 4:33 PM
normaldude            ica-tcp#987         2  Active          4  7/31/2008 6:20 PM
 

2. QWinsta

QWinsta is little different and better. It has more features and options. It comes with all flavors of Windows.  QWinsta command line help displays as,

C:>qwinsta /?
Display information about Terminal Sessions.
QUERY SESSION [sessionname | username | sessionid]
              [/SERVER:servername] [/MODE] [/FLOW] [/CONNECT] [/COUNTER]
  sessionname         Identifies the session named sessionname.
  username            Identifies the session with user username.
  sessionid           Identifies the session with ID sessionid.
  /SERVER:servername  The server to be queried (default is current).
  /MODE               Display current line settings.
  /FLOW               Display current flow control settings.
  /CONNECT            Display current connect settings.
  /COUNTER            Display current Terminal Services counters information.

E.g.,

C:>qwinsta /server:citrixserver
SESSIONNAME       USERNAME                 ID  STATE   TYPE        DEVICE
                                             0  Disc    rdpwd
ica-tcp                                 65536  Listen  wdica
rdp-tcp                                 65537  Listen  rdpwd
console                                    16  Conn    wdcon
ica-tcp#966       johndoe                  10  Active  wdica
ica-tcp#969       apple                     1  Active  wdica
ica-tcp#984       averagejoe                5  Active  wdica
ica-tcp#987       familyman                 2  Active  wdica
ica-tcp#989       whoisme                   3  Active  wdica

You are welcome to try the other options QWinsta provides.

Logoff the Remote Sessions

To Log off the terminal session of the remote server, you can use any one of two command line tools. One of LOGOFF and another one is RWINSTA. Before you log off the remote session, you should know the "Session ID" which you get it from "QUSER" OR "QWINSTA" commands as above stated.

1. Logoff

Logoff command kicks off (logging off) the specified remote session. Log off help shows,

C:>logoff /?
Terminates a session.
LOGOFF [sessionname | sessionid] [/SERVER:servername] [/V]
  sessionname         The name of the session.
  sessionid           The ID of the session.
  /SERVER:servername  Specifies the Terminal server containing the user
                      session to log off (default is current).
  /V                  Displays information about the actions performed.

E.g.,

C:>logoff /server:infra-apps 1 /v
Logging off session ID 1

2. RWinsta

RWinsta has same parameters and does same thing as log off command. It simply means Reset WINdows STAtion. The help goes as,

C:>RWinsta /?
Reset the session subsytem hardware and software to known initial values.
RESET SESSION {sessionname | sessionid} [/SERVER:servername] [/V]
  sessionname         Identifies the session with name sessionname.
  sessionid           Identifies the session with ID sessionid.
  /SERVER:servername  The server containing the session (default is current).
  /V                  Display additional information.

E.g.,

C:>RWinsta /Server:MyWinServer 1

Note: RWinsta command does not return anything.
Happy Re-setting the remote sessions (Hey, stop cursing your co-workers who didn’t log off their sessions).
Keywords: Reset remote session, Remote Desktop Session

Microsoft Word: “This modification is not allowed because the selection is locked.”

If you’re getting a message at the bottom of Word 2007, Word 2010, or other products in the Office suite whenever you try to change the document saying “This modifications is not allowed because the selection is locked.”, this article should answer your question ‘why’ and tell you how to make your document editable again.

There are four possible causes to this problem:

1. The document is marked as final.
2. The document is protected.
3. You are using a trial of Office 2007.
4. Office 2007 has not yet been activated.

Document is Marked as Final

You will also be unable to paste into the document. If you hover over the Paste button under the Home tab, you’ll get this error message: “This command is currently disabled. This command is not available because the document is marked as final.”

The rest of that error message also points us in the right direction.
Click on the Office button (the circle with the office logo on it in the top-left corner) and go down to the Prepare sub-menu. In this sub-menu, you’ll see an icon next to ‘Mark as Final’ highlighted in orange. This means that it is enabled and the document is “finalized.” It won’t allow any changes to the document. It would be best practice to mark your document as final before you send it off to others for professional evaluation. This also makes the red (spelling) and green (grammar) squiggles under words go away as well as any marked changes throughout the document.

Besides the ‘Mark as Final’ icon being highlighted in the Prepare sub-menu you will also notice a small version of the same icon at the bottom of Word 2007 in the status bar.

In order to make changes, the document just needs to be “un-finalized.” Go back to the Office button -> Prepare menu and click “Mark as Final” to toggle it off. After that, the icon will now appear unhighlighted and the icon will be gone from the status bar.

Document is Protected

If you are still not able to edit the document, it may be protected. Switch to the Review tab and then hit the Protect Document button to bring up a small menu.

From that menu, choose Restrict Formatting and Editing.

Next to the document, a little window should pop up. If at the bottom, you have a Stop Protection button, click that. If you don’t see that button but instead see a ‘Start protection‘ button, you can close this little window. This setting is not the one locking your document. You may have to enter a password in order to modify the document. You’ll need to know the password in order to stop this protection.

Your trial of Office 2007 has expired.

If you’re using Office 2007 that came with your computer, likely it was only a trial and has expired. Try opening your document in the free Open Office or purchase a full version of Microsoft Office 2007. “If you have the Office Home and Student 2007 Trial preloaded on your computer, you can purchase the disc version and use the product-key to unlock and activate the preloaded trial.”

Installing the File Server Resource Manager Tools in Windows Server 2008

The File Server Resource Manager (FSRM) can be installed separately or it can be installed during the installation of the File Services role. If FSRM needs to be installed on a system that is not a file server or just installed separately, follow the below steps:

1. Log on to the Windows Server 2008 system with an account with administrator privileges.

2. Click on Start > All Programs > Administrative Tools > Server Manager.

3. Click on the Features > Tree pane and Add Features > tasks pane.

4. The Add Features Wizard opens. On the Select Feature page, click the plus symbol next to Remote Server Administration Tools.

5. Click the Role Administration Tools > File Services tools > File Server Resource Manager Tools > Next 

6. On the Confirm Installation Selections page,  click Install to continue.

7. On the Installation Results page, review the result summary, and click Close to complete the installation.

On a system with the FSRM tools installed but not the File Server and File Server Resource Manager roles, FSRM will only be available from the Administrative Tools menu to manage remote servers. On systems with the File Server and File Server Resource Manager roles installed, FSRM will be available in the Server Manager console in the File Services group under Roles.

NOTE: If the File Services role is installed but the File Server Resource Manager Tool cannot connect to the system, chances are that during the File Services role installation, File Server Resource Manager was not selected. To add this functionality, the File Service Resource Manager service will need to be added using the Add Role Services from the tasks pane in the Server Manager Role node.

How to Use Jetpack.exe to Compact a WINS or DHCP Database

Microsoft Windows NT Server includes a utility, Jetpack.exe, that can be used to compact a Windows Internet Name Service (WINS) or Dynamic Host Configuration Protocol (DHCP) database. Microsoft recommends that you compact the WINS database whenever it approaches 30 MB.

The correct syntax for Jetpack.exe is:

JETPACK.EXE

Example commands to compact the WINS database:

CD %SYSTEMROOT%\SYSTEM32\WINS
NET STOP WINS
JETPACK WINS.MDB TMP.MDB
NET START WINS

Example commands to compact the DHCP database:

CD %SYSTEMROOT%\SYSTEM32\DHCP
NET STOP DHCPSERVER
JETPACK DHCP.MDB TMP.MDB
NET START DHCPSERVER

In the examples above, Tmp.mdb is a temporary database that is used by Jetpack.exe. Wins.mdb is the WINS database. Dhcp.mdb is the DHCP database.

Jetpack.exe compacts the WINS or DHCP database by doing the following:

1. Copies database information to a temporary database file called Tmp.mdb.
2. Deletes the original database file, Wins.mdb or Dhcp.mdb.
3. Renames the temporary database files to the original filename.

NOTE: During the compact process, Jetpack.exe creates a temporary file with the name that is specified by the temp database name parameter. The temporary file is removed when the compact process is complete. Make sure you do not have a file already existing in WINS or DHCP folder with the same name as the one specified in the temp database name parameter.

Configuring a Server Core installation: Command line

Server Core installation does not include the Windows user interface so you need to install by using command line interface.

Administrative credentials

If you are going to join a server running a Server Core installation to an existing Windows domain, you need a user name and password for an account that has the administrative credentials to join a computer to the domain.

Known issues for configuring a Server Core installation

• If you close all command prompts, you will have no way to manage the Server Core installation. To recover, you can press CTRL+ALT+DELETE, click Start Task Manager, click File, click Run, and type cmd.exe. Alternatively, you can log off and log back on again.
• Because there is no Web browser, you cannot activate a Server Core installation or access the Internet through a firewall that requires users to log on.

Steps for configuring a Server Core installation

The following procedures explain how to configure a computer running a Server Core installation. You’ll need to:

• Set the administrative password.
• Set a static IP address.

Note: A DHCP address is provided by default. You should perform this procedure only if you need to set a static IP address.

• Join a domain.
• Activate the server and entering a product key, if required.
• Configure the firewall.
• Configure several aspects with one tool (Windows Server 2008 R2 only).

To set the administrative password in Windows Server 2008

1. When your computer starts for the first time after the installation completes, press CTRL+ALT+DELETE. Type Administrator for the user name and leave the password blank.
2. The system will inform you that the password has expired and will prompt you to enter a new password.
3. Type an appropriate password.

To set the administrative password in Windows Server 2008 R2

1. When your computer starts for the first time after the installation completes, the system will inform you that the user’s password must be changed before logging on for the first time. Click OK.
2. The system will prompt you to enter a password.
3. Type an appropriate password.

To set a static IP address

1. At a command prompt, type the following:
   netsh interface ipv4 show interfaces
2. Make a note of the number shown in the Idx column of the output for your network adapter. If your computer has more than one network adapter, make a note of the number corresponding to the network adapter for which you wish to set a static IP address.
3. At the command prompt, type:
   netsh interface ipv4 set address name="" source=static address= mask= gateway=
   Where:
   ID is the number from step 2 above.
   StaticIP is the static IP address that you are setting.
   SubnetMask is the subnet mask for the IP address.
   DefaultGateway is the default gateway.
4. At the command prompt, type:
   netsh interface ipv4 add dnsserver name=">" address=index=1
   Where:
   ID is the number from step 2 above.
   DNSIP is the IP address of your DNS server.
5. Repeat step 4 for each DNS server that you want to set, incrementing the index= number each time.

Note:

If you set the static IP address on the wrong network adapter, you can change back to using the DHCP address

supplied by using the following command:

netsh interface ipv4 set address name="" source=dhcp

where ID is the number of the network adapter from Step 2.

To join a domain

1. At a command prompt, type:
   netdom join > /domain: /userd: /passwordd:*
   Where:
   ComputerName is the name of the server that is running the Server Core installation.
   DomainName is the name of the domain to join.
   UserName is a domain user account with permission to join the domain.
2. When prompted to enter the password, type the password for the domain user account specified by UserName.
3. If you need to add a domain user account to the local Administrators group, type the following command:
   net localgroup administrators /add \
4. Restart the computer. You can do this by typing the following at a command prompt:
   shutdown /r /t 0

To rename the server

1. Determine the current name of the server with the hostname or ipconfig command.
2. At a command prompt, type:
   netdom renamecomputer  /NewName:
3. Restart the computer.

To activate the server

• For Windows Server 2008 R2, enter a product key by typing the following at a command prompt:
  slmgr.vbs –ipk
  Then, for both Windows Server 2008 R2 and Windows Server 2008, activate the server by typing the following at a command prompt:
  slmgr.vbs -ato

If activation is successful, no message will return in the command prompt.

Note:

You can also activate by phone, using a Key Management Service (KMS) server, or remotely by typing the following command at a command prompt of a computer that is running Windows Vista or Windows Server 2008:

cscript windows\system32\slmgr.vbs  :-ato

To configure the firewall

• Use the netsh advfirewall command. For example, to enable remote management from any MMC snap-in, type the following:
  netsh advfirewall firewall set rule group="Remote Administration" new enable=yes

Note:

You can also use the Windows Firewall snap-in from a computer running Windows Vista or Windows Server 2008

to remotely manage the firewall on a server running a Server Core installation. To do this, you must first enable

remote management of the firewall by running the following command on the computer running a Server Core

installation:

netsh advfirewall set currentprofile settings remotemanagement enable

How to set Static/DHCP IP Address from command line

In Windows Server 2008 Core installation, the only way to setup IP Address eithe Static or DHCP is from the command line. The following procedure helps setting the IP Address from the command Line using “netsh”. This procedure works in Windows Server 2008 (No core installation as well), Windows Server 2003, Windows XP, Windows Vista.

To setup Static IP Address:

From the command prompt:

1. Type 

C:\Users\Administrator> netsh interface ipv4 show interfaces
Idx  Met   MTU   State        Name
—  —  —–  ———–  ——————-
  1   50 4294967295  connected    Loopback Pseudo-Interface 1
 10   20   1500  connected    Local Area Connection

This should show the Network Connections. We are looking for the name here. On mine, I have one LAN interface and is named as “Local Area Connection”

2. To set a static IP Address type the following command

C:\Users\Administrator>netsh interface ipv4 set address name=”Local Area Connect
ion” source=static address=192.168.0.5 mask=255.255.255.0 gateway=192.168.0.1

The syntax is

netsh interface ipv4 set address name=”” source=static address= mask= gateway=

Where:
ID is the name of the LAN Connection
StaticIP is the static IP address that you are setting
SubnetMask is the subnet mask for the IP address
DefaultGateway is the default gateway

3. Now set the DNS Servers one at a time with the followind command. For each DNS server, increase the index number.

C:\Users\Administrator>netsh interface ipv4 add dnsserver name=”Local Area Conne
ction” address=192.168.0.1 index=1

C:\Users\Administrator>netsh interface ipv4 add dnsserver name=”Local Area Conne
ction” address=192.168.0.10 index=2

The syntax is

netsh interface ipv4 add dnsserver name=”” address=index=1

Where:
ID is the name of the Network Connection
DNSIP is the IP address of your DNS server

This should do. To confirm, do an “ipconfig”

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controller
   Physical Address. . . . . . . . . : 00-1D-09-D4-2C-8F
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.5(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.0.1
                                       192.168.0.10
                                       127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Set IP through DHCP Server

To set the DHCP Server, from the command line

C:\Users\Administrator> netsh interface ipv4 set address name=”Local Area Connection” source=dhcp

Syntax is

netsh interface ipv4 set address name=”ID” source=dhcp

where ID is the name of the Network Connection

Get MAC Address Remotely by Computer Name or IP Address

Obtain the MAC address of a network card by IP address or Computer Name by using the GETMAC command.
To use this command, do the following:
1. Open a command prompt with administrator privileges.
2. You can use one of the following commands


Help:
GETMAC /?
GETMAC /S system /U user
GETMAC /S system /U domain\user /P  password


GETMAC /s computername - Get MAC by Computer Name
GETMAC /s 192.168.1.1 – Get MAC by IP Address

Description of the 64-bit operating systems that are supported together with Microsoft Dynamics GP

To run Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 9.0 on a 64-bit computer or on a 64-bit server, you must satisfy the following prerequisites:

Note Microsoft Dynamics GP only work with a 32-bit ODBC. When Microsoft Dynamics GP is installed on a 64-bit computer, the ODBC is automatically defaulted for 64-bit and the server list will be empty. In this case, a new 32-bit ODBC have to be created.

• You must use a 32-bit Open Database Connectivity (ODBC) Data Source Name (DSN) when you try to log in to Microsoft Dynamics GP. If you use a 64-bit ODBC DSN, the server list will be empty.
  
  Note To configure a 32-bit ODBC DSN, follow these steps:
  1. Right-click Start, and then click Explore.
  2. Locate the following folder:
     C:\Windows\SysWOW64
  3. Right-click the Odbcad32.exe file, and then click Create Shortcut.
  4. Right-click the shortcut file, and then click Rename.
  5. To rename the shortcut file, type Data Sources (ODBC) 32-bit.
  6. Right-click the shortcut file, and then click Copy.
  7. Expand My Computer, expand Control Panel, and then click Administrative Tools.
  8. Paste the shortcut file in the Administrative Tools folder.
  9. Close Windows Explorer.
  10. Click Start, click Control Panel, double-click Administrative Tools, and then double-click Data Sources (ODBC) 32-bit.
  11. In the ODBC Data Source Administrator dialog box, create an ODBC data source.
      
      Note Rename the ODBC data source by using a name that clearly identifies this ODBC data source as the 32-bit version. For example, use the name "Dynamics32bit."
  12. Start Microsoft Dynamics GP.
  13. Select the ODBC data source that you created in step 11.
  14. Double-click the new shortcut to open it.
  15. Reference Microsoft Knowledge Base article 870416 to create an ODBC connection for Microsoft Dynamics GP. For more information about this article, click the following article number to view the article in the Microsoft Knowledge Base:
      870416  How to set up an ODBC Data Source on SQL Server for Microsoft Dynamics GP
  Note To clearly identify the names of the shortcut files of the ODBC data sources, rename the shortcut file of the 64-bit version as "Data Sources (ODBC) 64-bit."
• During installation, remove any information that is in parentheses from the default installation path. For example, the 64-bit ODBC DSN uses the following default path:
  C:\Program Files (x86)\Microsoft Dynamics\GP\
  In this case, you must change the installation path of the following path:
  C:\Program Files\Microsoft Dynamics\GP\
  Note The Field Service notification is incompatible with any x64-based server.

-----------------------------------------------------------------------------

To run Web Services on an x64-based operating system, you must use the following workarounds.

Web Services Runtime workaround

Windows Server 2003 x64 and Microsoft Dynamics GP 10.0 only

1. In Windows Explorer, locate the system drive, and then open the following folder:
   %SystemRoot%\Windows\Microsoft.NET\AuthMon\1.2 folder
2. Drag the Microsoft.Interop.Security.AzRoles.dll file into the %SystemRoot%\Windows\assembly folder.
3. In Windows Explorer, verify that you can see the Microsoft.Interop.Security.AzRoles.dll file in the %SystemRoot%\Windows\assembly folder.
4. Install the x64 Dexterity Common Components on the IIS server. To download the x64 Dexterity Common Components, visit the following Microsoft Web site:
   https://mbs.microsoft.com/fileexchange/?fileID=2a6324c4-ce09-440b-b93d-3541dc7074e9
5. Install Microsoft Dynamics GP 10.0 Service Pack 3 or a later version. To do this, visit the following Microsoft Web site:
   https://mbs.microsoft.com/customersource/downloads/servicepacks/mdgp10_patchreleases.htm?printpage=false
6. Download Web Services Service Pack 3 or a later version. To do this, visit the following Microsoft Web site:
   https://mbs.microsoft.com/customersource/downloads/servicepacks/webservicesformicrosoft+dynamicsgp10.htm?printpage=false
7. Browse the Web Services installation folder, and then double-click the DynamicsGPWebServices.msi file.
8. After Web Services is installed successfully, see the "Web Services Management Tools workaround" section.

Windows Server 2008 x64 or x86 and Microsoft Dynamics GP 10.0 only

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756  How to back up and restore the registry in Windows

1. Refer to page 24 in the WebServicesInstallation.pdf file for the Windows Server 2008 roles and role services that must be enabled. To download the WebServicesInstallation.pdf, visit the following Microsoft Web site:
   https://mbs.microsoft.com/downloads/customer/WSInstallAdminGuide.pdf
2. Click Start, click Run, and then type REGEDIT.
3. Locate the following registry subkey, and then follow these steps:
   HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion
   1. Right-click the registry subkey, point to New, click Key, and then name the new key ADAM_Shared.
   2. Open the ADAM_Shared folder.
   3. Right-click the ADAM_Shared folder, point to New, and then click String Value.
   4. Name the new string value InstalledVersion, and then type 1.1.3790.2075 as the value data.
4. Install the x64 Dexterity Common Components on the IIS server. To download the x64 Dexterity Common Components, visit the following Microsoft Web site:
   https://mbs.microsoft.com/fileexchange/?fileID=2a6324c4-ce09-440b-b93d-3541dc7074e9
5. Install Microsoft Dynamics GP 10.0 Service Pack 3 or a later version. To do this, visit the following Microsoft Web site:
   https://mbs.microsoft.com/customersource/downloads/servicepacks/mdgp10_patchreleases.htm?printpage=false
6. Download Web Services Service Pack 3 or a later version. To do this, visit the following Microsoft Web site:
   https://mbs.microsoft.com/customersource/downloads/servicepacks/webservicesformicrosoft+dynamicsgp10.htm?printpage=false
7. Browse the Web Services installation folder, and then double-click the DynamicsGPWebServices.msi file.
8. After Web Services is installed successfully, see the "Web Services Management Tools workaround" section.

---------------------------------------------------------------------------

Web Services Management Tools workaround

This workaround is necessary for Microsoft Management Console (MMC) to work for Web Services:

1. The Microsoft Visual C++ 2005 SP1 redistributable package (x86) must be installed on the x64-based computer for the Management Tools to work correctly. To download and install the redistributable package, visit the following Microsoft Web site:
   http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
2. The Web Services Management Tool installation must be started from the "Web Services" folder on CD2 or the Feature Pack DVD. Locate the Microsoft Dynamics GP 10.0 CD2 or the Feature Pack DVD, and then open the AdProd\WebServices folder. Double-click the DynamicsGPWebServicesManagementTools.msi file.

How to compact Active Directory in Windows 2008?

Active Directory Maintenance

1.    1.  Use ntdsutil command

2.     2.Stop Active Directory Domain Services.

3.     3. Type Help to know sub commands

4.   Type compact to c:\ 

4

4.  5.     Quit à quit

6.     Copy the ntds.dit and overwrite the old one. Delete the log file.

7.      Check the integrity

7.     

8.     8.Type semantic  checker after the colon :. Then type verbose on . Then type go fixup

9. .Quit àquit

10. Restart Active Directory Domain Services

How to Determine Your Device's Ethernet or Wireless Hardware Address

All manufacturers of Ethernet and Wireless interfaces cooperate to ensure that every hardware interface has a unique address.
If your computer has both an Ethernet interface and a Wireless interface, each will have its own unique hardware address.
An Ethernet or Wireless hardware address is a 6-byte hexadecimal number; for example: 0x080007A9B2FC. (Each byte is written as two hexadecimal digits, so there are twelve hexadecimal digits; each hex digit is a number from 0-9 or a letter from A-F. A leading '0x' may be written to make explicit that the following digits should interpreted as hexadecimal.)
Ethernet and Wireless hardware addresses are often written in other forms, to make them easier to understand. It is common to leave off the leading '0x', and also to separate the six pairs of digits with colons or dashes, like: 08:00:07:A9:B2:FC or 00-00-94-ba-0e-cc. When using colons or dashes to separate the address into six pairs, sometimes any leading zero in each pair of digits is dropped; e.g. 8:0:7:A9:B2:FC or 0:0:94:ba:e:cc. (Note that when dropping leadings zeroes, '00' becomes '0' -- you never completely eliminate any of the six pairs of digits.)

Windows 95, 98, ME

The process of obtaining your ethernet address is fairly simple in Windows 95, Windows 98, and Windows ME. You need to have, at least, installed the Microsoft TCPIP protocol to use this method. If you have installed the MS TCPIP protocol do the following:

1. Click on Start.
2. Click on Run.
3. In the command line box which appears, enter the following and press the Enter key:

   winipcfg
   

4. A box will appear with a variety of information. Check the pull-down menu near the top to verify that your Ethernet interface is selected; if it is not, then select it in this menu.
5. Look for the line labelled Adapter Address. This is your Ethernet interface's hardware address. It will be written out completely as 6 pairs of 2 digits separted by hyphens. Write it down.
6. If your machine has a wireless card, select Wireless interface from the drop down menu. Look for the Adapter Address under this section and write it down.

Windows NT 4.0

You can find your ethernet address using Microsoft's ipconfig utility:

1. Click the Start button.
2. Select Programs and then select Command Prompt.
3. At the C:\> prompt, enter the following then press the Enter key:

   ipconfig /all
   

4. Your machine's ethernet address is listed as the Physical Address.
5. If your machine has both an Ethernet and a Wireless connection, two Physical Adresses will be shown in different sections. The Ethernet hardware address is listed under Ethernet Adapter Local Area Connection and the Wireless hardware address will be listed under Ethernet Adapter Wireless Network Connection.
6. To close the Command Prompt window, enter the following at the C:\> prompt then press the Enter key:

   exit
   

---

Windows 2000, XP

You can find your machine's Ethernet or Wireless hardware addresses using Microsoft's ipconfig utility:

1. Click the Start button.
2. Select Programs and then select Accessories/Command Prompt.
3. At the C:\> prompt, enter the following then press the Enter key:

   ipconfig /all
   

4. Your machine's Ethernet or Wireless hardware address is listed as the Physical Address.
5. If your machine has both an Ethernet and a Wireless connection, two Physical Adresses will be shown in different sections. The Ethernet hardware address is listed under Ethernet Adapter Local Area Connection and the Wireless hardware address will be listed under Ethernet Adapter Wireless Network Connection.
6. To close the Command Prompt window, enter the following at the C:\> prompt then press the Enter key:

   exit
   

---

Windows Vista, Windows 7

You can find your machine's Ethernet or Wireless hardware addresses using Microsoft's getmac utility:

1. If your device is a Dell laptop, ensure it is plugged into an electrical outlet; if it is not plugged in, the device's Ethernet address will not be displayed.
2. Click the Start button.
3. In the Search box, enter the following then press the Enter key:

   cmd
   

4. At the DOS prompt, enter the following then press the Enter key:

   getmac /v
   

5. Your machine's Ethernet or Wireless hardware addresses are listed as the Physical Addresses.
6. If your machine has both an Ethernet and a Wireless connection, two Physical Adresses will be shown in different sections. The Ethernet hardware address is listed under Ethernet Adapter Local Area Connection and the Wireless hardware address will be listed under Ethernet Adapter Wireless Network Connection.
7. To close the Command Prompt window, enter the following at the C:\> prompt then press the Enter key:

   exit
   

---

Mac OS X 10.4, 10.5, 10.6, 10.7

To display your Mac OS X device's Ethernet or Wireless hardware addresses:

1. Make sure that the network interface you're interested in is part of the current location, and is turned "on":
   
   1. Open the System Preferences application in the Apple menu.The System Preferences application is also sometimes available in the Dock. It's also available in the Utilities folder (in versions 10.4 - 10.5) or the Applications folder (in versions 10.6 - 10.7).
      
   2. Click the Network icon in the System Preferences application.
   3. The Network pane of the System Preferences application displays a Location pop-up menu near the top of its window.In this Location pop-up menu, select a location that includes the network interface of interest.
      For Mac OS X 10.4: You can verify that a network interface (port) is a member of a location by selecting that location, then in the Show pop-up menu, selecting Network Port Configurations. Verify that network interface of interest appears in the port list, and is turned "on" (its checkbox is checked).
      For Mac OX X 10.5 - 10.7: You can verify that a network interface (port) is a member of a location by selecting that location, then verifying that the network interface of interest appears in the network ports list on the left side of the window. Verify that the interface's status (which appears in grey just below the name of the interface) is anything other than "Inactive."
      
   4. If you made any changes in this window, click the Apply button in the lower right corner of the window.
   5. If you made any changes in the Network pane in System Preferences that you won't want to retain, make a note of them now, so you can undo them later.
   6. Once you've verified that the network interface you're interested in is part of the current location and is turned "on" (in 10.4), or is anything except "inactive (in 10.5 - 10.7), you can selectQuit System Preferences from the File menu.
2. In Mac OS X 10.4 - 10.6, launch the System Profiler application. In Mac OS X 10.7, launch the System Information application.This program is normally located in the Utilities folder, which in turn is located in the Applications folder.
   
3. In the Contents pane on the left, select Network.
4. Displayed in the upper-right pane is a list of each of the Mac's network interfaces that are part of the current network location and are turned "on" (in 10.4), or anything except "inactive" (in 10.5 - 10.7). (In 10.6 - 10.7, these are entitled "Active Services".)In this upper-right pane, select the item for the Ethernet or Wireless (a.k.a "AirPort") interface in which you are interested.
   
5. Displayed in the lower-right pane is information about the selected network interface.Each interface's hardware address is the value labelled Ethernet address, MAC address, or Hardware (MAC) address This is true even if the device is actually a wireless interface. (It is not the item labelledRouterHardwareAddress.) Make a note of the value; this is the information you were seeking.
   
6. Quit the System Profiler (in 10.4 - 10.6) application or the System Information (in 10.7) application.
7. If earlier you changed any settings in the Network pane of System Preferences (e.g. to make a particular network interface active) and you wish to change it back, do so now.

---

Apple iPhone OS 3.1 - 3.2; iOS 4.0 - 5.0

To display your Apple iOS (or iPhone OS) device's Wireless hardware address:

1. Open the Settings application.
2. From the list of setting categories, select General.
3. From the list of general settings, select About.
4. The Wireless hardware address is the value labelled Wi-Fi Address.
5. Leave the Settings application.

---

Android 2.2, 2.3

To display your Android device's Wireless hardware address:

1. Open the Settings application.
2. From the list of setting categories, select About phone. (This category might be named something else, for example, About tablet.)
3. From the list of choices, select Hardware information. On some versions of Android, you may instead need to choose Status.
4. The Wireless hardware address is the value labeled Wi-Fi MAC Address.
5. Leave the Settings application.

---

Sun

When executed as root, the following command will show the hardware address for each Ethernet interface that is plumbed on the system:

# /usr/sbin/ifconfig -a

   lo0: flags=1000849 mtu 8232 index 1
           inet 127.0.0.1 netmask ff000000 
   hme0: flags=1000843 mtu 1500 index 2
           inet 192.168.1.2 netmask fffffc00 broadcast 192.168.1.0
           ether 8:0:20:4:5:6