Elevated Command Promt

levated Command Prompt How to Open a Elevated Command Prompt in Windows 7 Published by Brink 12-04-2008

Elevated Command Prompt How to Open a Elevated Command Prompt in Windows 7    Information This will show you how to open a elevated command prompt with administrator rights (Run as administrator) instead of the default command prompt without administrator rights in Windows 7. EXAMPLE: Elevated Command Prompt NOTE: Notice how the elevated command prompt opens to C:\Windows\System32 and not C:\Users\(user name) as the default command prompt without administrator rights. Here's How: 1. Use a Elevated Command Prompt shortcut. OR 2. Open the Start Menu. 3. Click on All Programs and Accessories, then right click on Command Prompt and click onRun as administrator. (See screenshot below) OR 4. Open the Start Menu. 5. In the Start Menu search box area, type cmd and press CTRL+SHIFT+ENTER. OR 6. Open the Start Menu. 7. In the Start Menu search box area type cmd, then right click on cmd (at top), and click onRun as administrator. (See screenshot below)    Tip If you are in a administrator account and get a log in prompt after doing any of the above steps, then click on the Cancel button and repeat the above step again. This will only do this for the very first time you try to open a elevated command prompt in Windows 7. If you are in a standard account, then you will need to type in the administrator's password to elevate the command prompt. That's it, Shawn

Elevated Command Promt

levated Command Prompt How to Open a Elevated Command Prompt in Windows 7 Published by Brink 12-04-2008

Elevated Command Prompt How to Open a Elevated Command Prompt in Windows 7    Information This will show you how to open a elevated command prompt with administrator rights (Run as administrator) instead of the default command prompt without administrator rights in Windows 7. EXAMPLE: Elevated Command Prompt NOTE: Notice how the elevated command prompt opens to C:\Windows\System32 and not C:\Users\(user name) as the default command prompt without administrator rights. Here's How: 1. Use a Elevated Command Prompt shortcut. OR 2. Open the Start Menu. 3. Click on All Programs and Accessories, then right click on Command Prompt and click onRun as administrator. (See screenshot below) OR 4. Open the Start Menu. 5. In the Start Menu search box area, type cmd and press CTRL+SHIFT+ENTER. OR 6. Open the Start Menu. 7. In the Start Menu search box area type cmd, then right click on cmd (at top), and click onRun as administrator. (See screenshot below)    Tip If you are in a administrator account and get a log in prompt after doing any of the above steps, then click on the Cancel button and repeat the above step again. This will only do this for the very first time you try to open a elevated command prompt in Windows 7. If you are in a standard account, then you will need to type in the administrator's password to elevate the command prompt. That's it, Shawn

Change the User Account password

User Account Password - Change from WinRE How to Change the User Account Password if Unable to Login to Windows Published by Dinesh 01-20-2010

User Account Password - Change from WinRE How to Change the User Account Password if Unable to Login to Windows    Information This tutorial will help you remove the existing user account password and set up a new password incase you have forgotten the user password using WinRE (Windows Recovery Environment) Here's how: 1. Boot to WinRE (Windows Recovery Environment). 2. Click on the Command Prompt option. 3. Type the following commands and press enter after each one: C: CD Windows\system32 ren cmd.exe cmd.old ren magnify.exe cmd.exe ren cmd.old magnify.exe 4. Restart computer.  5. Click on Easy of Access centre left side bottom à Choose Magnify option. 6. A Command prompt opens up 7. Type: net user administrator /active:yes and press enter. 8. Restart the computer. 9. Logon on administrator account and then using User Accounts page in the Control Panel, remove password for the other account. 10. Type Magnify.exe in Start Menu search box and press enter and open it. 11. Command prompt opens up 12. Type: net user administrator /active:no and press enter. 13. Restart the computer NOTE: This will disable the administrator account. 14. Now, Boot to winRE again, and click on the Command Prompt option. 15. Type the following commands and press enter after each one: C: CD Windows\system32 ren magnify.exe cmd.old ren cmd.exe magnify.exe ren cmd.old cmd.exe exit 16. Restart the computer – system logs on to the User account without asking for password provided there is only one user account.

Change the User Account password

User Account Password - Change from WinRE How to Change the User Account Password if Unable to Login to Windows Published by Dinesh 01-20-2010

User Account Password - Change from WinRE How to Change the User Account Password if Unable to Login to Windows    Information This tutorial will help you remove the existing user account password and set up a new password incase you have forgotten the user password using WinRE (Windows Recovery Environment) Here's how: 1. Boot to WinRE (Windows Recovery Environment). 2. Click on the Command Prompt option. 3. Type the following commands and press enter after each one: C: CD Windows\system32 ren cmd.exe cmd.old ren magnify.exe cmd.exe ren cmd.old magnify.exe 4. Restart computer.  5. Click on Easy of Access centre left side bottom à Choose Magnify option. 6. A Command prompt opens up 7. Type: net user administrator /active:yes and press enter. 8. Restart the computer. 9. Logon on administrator account and then using User Accounts page in the Control Panel, remove password for the other account. 10. Type Magnify.exe in Start Menu search box and press enter and open it. 11. Command prompt opens up 12. Type: net user administrator /active:no and press enter. 13. Restart the computer NOTE: This will disable the administrator account. 14. Now, Boot to winRE again, and click on the Command Prompt option. 15. Type the following commands and press enter after each one: C: CD Windows\system32 ren magnify.exe cmd.old ren cmd.exe magnify.exe ren cmd.old cmd.exe exit 16. Restart the computer – system logs on to the User account without asking for password provided there is only one user account.

How can I run two Skype accounts on the same computer?

How can I run two Skype accounts on the same computer?
For Skype 4.0 and later
For Skype 3.8 and earlier
For Skype 4.0 and later
In order to use more than one Skype account on the same computer at the same time you need to start a new instance of Skype:

From the Windows taskbar, click Start > Run (or press the Windows and R keys on your keyboard at the same time)
In the Run window, enter the following command (include the quotes) and press OK:
"C:\Program Files\Skype\Phone\Skype.exe" /secondary

If you get any error messages, please copy and paste the exact command from this email and try again.

Please keep in mind that if you have changed the installation path for Skype then you need to enter the correct path for the Skype.exe file.

If this solution fails, you can try another option:

Find the Skype executable file (Skype.exe) in: C:\Program Files\Skype\Phone\
Right click on it and choose: Send to > Desktop (create shortcut)
Locate the shortcut on the desktop, then right-click on it and choose Properties
In the Target field, add: /secondary. The Target field should now be: "C:\Program Files\Skype\Phone\Skype.exe" /secondary
Click OK. You can now start a new instance of Skype every time you double-click on the new shortcut.
For Skype 3.8 and earlier
Requirements: Windows XP, Two Skype User accounts

First, create a new Windows user by going to the Control Panel and clicking on User Accounts. Choose Create a new account and follow the steps to set permissions. We also suggest setting a password for the new user by clicking on the newly created user and choosing the Set Password option. The new user will also require admin rights on your PC.

Next, create a shortcut to Skype or make a copy of the shortcut that is already in the Start menu. Right-click this new shortcut and choose Properties. On the bottom of the first page there is a button labelled Advanced... . Click this button and select Run with different credentials. Select OK, and then select OK again to close the Properties dialog.

You're all set. Whenever you use this new shortcut it will ask for a Windows username and password. Enter the Skype Name and password of the user you created earlier by choosing The following user: option. Click OK and you'll have a second instance of Skype. It will require that you sign in with your Skype Name and password the first time.

To help automate the Run as trick you can create a second desktop icon for Skype and modify its properties. Click the Advanced button and check the box Run with different credentials. After clicking on the modified icon it will ask you to sign in as another user. Changing the icon graphic also helps ensure you click on the correct icon.

If you have multiple USB headsets or USB Phones you should be able to set up both instances of Skype to use a different sound device.

How can I run two Skype accounts on the same computer?

How can I run two Skype accounts on the same computer?
For Skype 4.0 and later
For Skype 3.8 and earlier
For Skype 4.0 and later
In order to use more than one Skype account on the same computer at the same time you need to start a new instance of Skype:

From the Windows taskbar, click Start > Run (or press the Windows and R keys on your keyboard at the same time)
In the Run window, enter the following command (include the quotes) and press OK:
"C:\Program Files\Skype\Phone\Skype.exe" /secondary

If you get any error messages, please copy and paste the exact command from this email and try again.

Please keep in mind that if you have changed the installation path for Skype then you need to enter the correct path for the Skype.exe file.

If this solution fails, you can try another option:

Find the Skype executable file (Skype.exe) in: C:\Program Files\Skype\Phone\
Right click on it and choose: Send to > Desktop (create shortcut)
Locate the shortcut on the desktop, then right-click on it and choose Properties
In the Target field, add: /secondary. The Target field should now be: "C:\Program Files\Skype\Phone\Skype.exe" /secondary
Click OK. You can now start a new instance of Skype every time you double-click on the new shortcut.
For Skype 3.8 and earlier
Requirements: Windows XP, Two Skype User accounts

First, create a new Windows user by going to the Control Panel and clicking on User Accounts. Choose Create a new account and follow the steps to set permissions. We also suggest setting a password for the new user by clicking on the newly created user and choosing the Set Password option. The new user will also require admin rights on your PC.

Next, create a shortcut to Skype or make a copy of the shortcut that is already in the Start menu. Right-click this new shortcut and choose Properties. On the bottom of the first page there is a button labelled Advanced... . Click this button and select Run with different credentials. Select OK, and then select OK again to close the Properties dialog.

You're all set. Whenever you use this new shortcut it will ask for a Windows username and password. Enter the Skype Name and password of the user you created earlier by choosing The following user: option. Click OK and you'll have a second instance of Skype. It will require that you sign in with your Skype Name and password the first time.

To help automate the Run as trick you can create a second desktop icon for Skype and modify its properties. Click the Advanced button and check the box Run with different credentials. After clicking on the modified icon it will ask you to sign in as another user. Changing the icon graphic also helps ensure you click on the correct icon.

If you have multiple USB headsets or USB Phones you should be able to set up both instances of Skype to use a different sound device.

Introduction


With Windows Server 2008, there are a number of changes to networking and Routing and Remote Access. In fact, I wrote about some of these changes in my WindowsNetworking.com article: Which Windows Server 2008 Networking Services were removed and which should you use instead? In that article, I covered how OSPF is no longer part of Windows Server 2008. I find that unfortunate because I think that OSPF is likely the best dynamic routing protocol ever created. Still, I can also partially understand Microsoft’s decision to remove it as I would venture to guess that 99.9% of Windows Server Admins never used it. So what are we left with?



With the removal of OSPF, we are left with either 1) static routing or 2) dynamic routing with RIPV2. Let’s find out how each of these work.



Should you use static or dynamic routing?

The question of whether you should use static or dynamic routing is really a question of administrative overhead. In the end, the result of your network traffic being routed to the correct network should be the same, no matter what method you choose.



With static routing, you must make an entry on your Windows Server for every network that will be routed by that server. Thus, for a simple network with a single windows server, routing traffic between two networks, static routing is a “no brainer”. You could configure it with two simple route add commands.



On the other hand, on a network where you want the Windows Server 2008 system to route for 25 networks or to exchange routes with a Cisco network that uses RIP, you will want to choose dynamic routing. Obviously, you do not want to have to key in those 25 networks manually nor can you provide the true dynamic features that RIP provides.



Speaking of that, what does dynamic routing provide you? Let’s list out some features.



Ability to automatically add networks by learning them from other RIP routers

Ability to automatically remove routes from the routing table when other RIP neighbors delete them

Ability to select the best route based on routing metrics

Reduce configuration of Windows Server routing systems that have more than a few static routes that need to be added

So how do you configure static and dynamic routing in Windows Server 2008?



Static Routing in Windows Server 2008

Static routing in Windows Server is nothing new. We have been using the route command for years. You can configure static routing in Windows 2008 Server using either the route command or using the GUI. However, if you use the Windows GUI interface, those routes will not be listed in the CLI interface, when you type route print. Thus, I highly recommend that if you are going to use static routing in Windows 2008, you just use the route command at the windows command prompt.



So let’s look at some examples of how you configure static routing using the route command:



Show the static routing table



Showing the static routing table is easy, just use the route print command, as you see in Figure 1 below.





Figure 1: Showing the IP Routing table in Windows Server 2008



In the route print output, the first important thing that you see is the interface list. Windows Server IP interfaces are labeled with an interface number. The interface numbers in Figure 1 are 16, 14, 1, 15, 20, and 12. These interface numbers are used whenever you add or delete routes to the routing table.



The second important thing in the route print output is the IPv4 Routing Table. This shows us the network destination, network mask, the default gateway, interface, and metric. This table tells the Windows Server where to route the traffic.



Below that is the IPv6 routing table. For more information on IPv6, I recommend Brien Posey’s articles Crash Course in IPv6 (Part One) & Crash Course in IPv6 (Part Two) and Mitch Tulloch’s article IPv6 Support in Microsoft Windows.



Add a static route



So how do you add a static route at the command line? The answer is easy- use the route add command, like this:



route add 1.1.1.0 mask 255.255.255.0 10.0.1.1 if 1



As you see in Figure 2, the results of our route add was an affirmative “OK!”





Figure 2: Using the route add command in Windows 2008



What was important in the route add command was the network we want to add, its subnet, the destination/gateway, and the interface for that route.



Delete a static route



Deleting a route is even easier than adding a route. All you have to do is to tell route delete the network that you want to remove, as you see in Figure 3.





Figure 3: Using the route delete command in Windows 2008



So those are the basics of configuring static routes at the command line. Now let’s learn about configuring dynamic routing.



Dynamic Routing in Windows Server 2008 using RIPV2

Earlier in the article, I talked about the benefits of configuring dynamic routing. So, now let me provide you the steps to configuring RIPv2 in Windows 2008:



1.The first step is to install the Routing and Remote Access (RRAS) role in Windows 2008 Server. If you go into the Add Roles Wizard, the RRAS role can be difficult to find because what you really need to add is the Network Policy and Access Services role then the Routing and Remote Access Services Role (as you see in Figure 4 and Figure 5).



Figure 4: Adding the RRAS Role through he Network Policy and Access Services





Figure 5: The Win 2008 Role Services are part of the Network Policy and Access Services Role



Once installed you can configure RRAS from the Server Manager application but I prefer the Routing and Remove Access application.



2.The second part of this is to Configure Routing and Remote Access by opening the RRAS MMC, right-clicking on the server name, and clicking Configure and Enable Routing and Remote Access, like this:



Figure 6: Configuring and Enabling RRAS



Make sure that you do a Custom Configuration concerning what RRAS protocol to install. Then, choose to install LAN ROUTING then choose to start the service.



From there, you can see the Network Interfaces controlled by RRAS and specific configurations for IPV4 and IPV6.



At this point, you can expand IPV4, go to General, then to New Routing Protocol.





Figure 7: Adding a new Routing Protocol



Next, choose to install RIPV2 as your routing protocol.





Figure 8: Adding RIP V2



3.Now that you have RIPv2 installed, you can configure it. Configuring it is really as easy as adding the interfaces that you want to use to exchange RIP routes with. To do this, go to the RIP section, right click, click on New Interface, select the interface you want to add under RIP as you see in Figure 9.



Figure 9: Adding a new RIP interface



4.After selecting the interface, you have the option to configure a wide variety of RIP connection properties (as you see in Figure 10). There is more to configuring RIP than I can go into in this article as RIP configuration can either be very simple or it can become very complex.



Figure 10: Configuring the new RIP interface



5.Once you have your RIP interfaces added, you can check to see if you are sending and receiving responses on your RIP interfaces (you should be). You can also check to see if you have any RIP neighbors by right-clicking on the RIP protocol, then clicking Show Neighbors.

Before I conclude this section about RIP in Windows, I want to point you to a couple of excellent resources I used while preparing for this article:



1.Recently I was watching Ed Liberman’s Train Signal Windows 2008 Network Infrastructure video. In that video, besides explaining routing and the differences between static and dynamic routing, Ed shows, step by step, how to configure RIPv2 in Windows 2008. I found the video very helpful and recommend it to you whether you just want to learn about Win 2008 and routing or if you are looking to pass Microsoft’s Windows 2008 Network Infrastructure exam (70-642). Here is a screenshot of Ed configuring RIPV2:



Figure 11 Train Signal’s Windows 2008 Video on how to install and configure RIPV2



2.Over at the Petri IT Knowledgebase, I wrote an article on how to configure it in Windows 2003, then another article on how to exchange routes between a Cisco router and a Window Server. While not pertaining to Win 2008, the process of configuring RIP on Win 2003 is similar and the configuration to exchange routes with a Cisco router is very relevant: