Popular Posts

Wednesday, June 8, 2011

Microsoft Exchange Server 2003-2007 - Troubleshooting Eseutil

Dears... I got more reviews regarding  Eseutil. But its Very help full as an exchange Administrator....Please check and  verify.. Tell Ur opinion....



Introduction to Exchange Server 2003 - Troubleshooting Eseutil
Eseutil reminds me of a knife.  How do you feel about a knife in the hand of a lunatic - uneasy?  How about a knife in you hand at the supper table - happier?   My message is this, please be aware that eseutil is a dangerous tool and that you ought to practice on a test Exchange machine before taking a stab at eseutil /r on your production server.  Now that I have warned you of the dangers, there will be situations where eseutil is a life saver. (Or at least a mail saver.)
Topics for Exchange Server 2003  - Troubleshooting Eseutil
 ♠

By spelling it ESEutil, two thoughts spring to my mind; firstly, I am reminded that here is a tool that manipulates Exchange's Extensible Storage Engine.  Secondly, ESEutil is a relative of NTDSutil which I use to manipulate Windows Active Directory from the command line.  Whether you spell it ESEutil, Eseutil or plain eseutil, this executable is really three tools in one. 
A different switch controls each aspect of eseutil.  The first and harmless aspect, is shown by the eseutil /k, /mh and /cc switches.  These gentle commands give you the ability to re-run procedures that occur naturally in Exchange, for example, when you remount a store, or replay the logs after a backup.
The second side of eseutil is to defrag Exchange 2003's databases with eseutil /d switch.  This /d switch shrinks the .edb files and recovers disk space.  Eseutil /d performs a specialist database compaction which is not the same as Windows 2003's built-in disk defragmenter.
The third and most dangerous side of eseutil is the repair function with /r or /p.  Regard eseutil /r or /p as a last resort to repair your damaged mailstore.  If the repair fails then it can leave the store in an unusable state, so always backup your Exchange server before you unleash the /r or /p switches.Eseutil path exchsrvr\bin  Exchange 2003
My advice is to begin by practicing with the harmless switches, for example eseutil /mh or /k.  To get started go to the command prompt and then navigate to the Exchsrvr\Bin folder.  Because this \bin folder is not in the file 'Path', beware of the notorious: 'not recognised as an internal or external command ' error.  This does not necessarily mean there is no eseutil on the Exchange server, just that you are not executing the command from the Exchsrvr\Bin folder.
eseutil /k tip.  Start in the \exchsrvr\bin folderNavigate to the \exchsrvr\bin folder before typing any eseutil commands.  An old trick is to copy the Address as seen in Explorer and then go to the command prompt, right click and paste that path.  (See diagram opposite.)
Alternatively, if you are going do a lot of command line troubleshooting, then it's worth editing the Path in the System Icon, Environmental Variables.

TrainSignal - Guy's recommended training videos for Exchange 2003Exchange Server 2007 is a complex topic, do you need practical hands on training?  As an MCT trainer, I can thoroughly recommend TrainSignal.  In particular, I like the way that TrainSignal cover all learning methods, instructor lead, video and of course text material.  You can either take one module, for example Exchange 2007 or go for a combination of modules.  Learn more about Microsoft Exchange Server 2007 here


Here is a simple switch to verify the state of an Exchange database.  All that eseutil /mh does is to determine whether the last shutdown was clean or dirty.  Eseutil /mh is ideal to practice getting to the right path and executing eseutil without doing any harm to the mailstore databases.
To start with, familiarise your self with the names and location of the Exchange 2003 databases, for example priv1.edb is usually in the \exchsrvr\mdbdata folder.  My suggestion is to type this command from the exchsrvr\bin folder:
eseutil /mh "d:\program files\exchsrvr\mdbdata\priv1.edb"  (Assuming Exchange 2003 is installed on the d:\.)
Examine the output for this line, 'State: Clean Shutdown' (or Dirty Shutdown).  In passing, you can also see when the last backup occurred.  Notice how the first line of the output changes when you substitute priv1.STM for priv1.edb.  Note the phrase: 'Streaming File'.
Another use of eseutil /mh is in disaster recovery where you want to see if eseutil /p has already been run.  If 'Repair Count' is greater than zero, then you can see how many times eseutil /p has been tried already.  In general, the greater the Repair Count, the less chance of a successful repair.
Eseutil /ml
Similar to the /mh, except this switch performs an integrity check on log files, for example, E00.log.
Eseutil /mm
Dumps metadata from the database file (not the logs).  Specialist use only, I find the output fascinating but not very useful.
Eseutil /mk
Provides information about the checkpoint file.  Handy for troubleshooting backup / restore problems.  Where /mh used priv1.edb, remember to substitute the name of the checkpoint file E00.chk with /mk.
This switch, eseutil /k is new in Exchange 2003.  The keyword is: check.  Just as checksum verifies a file's size, so eseutil /k checks the integrity of Exchange 2003's information stores.  One application of eseutil /k is to troubleshoot an Exchange 2003 database after an unscheduled shutdown of the Windows 2003 server.  The only downside with eseutil /k is that it does not recover the database.  (For recovery try /r or /p - but be careful.)
If you create additional mailbox stores, then check their corresponding .edb filenames.    Example: to check the default mailbox store = priv1.edb go to the command prompt and type:
eseutil /k "c: \program files\exchsrvr\mdbdata\priv1.edb" 
(This time I assumed that Exchange 2003 has been installed on the c:\).
Do not worry about uninititialized pages, it's normal to have several hundred in this category.  However, what you don't want is bad checksums or wrong page numbers.
Another scenario is that you wish to check the transaction logs, in which case here is the command:
eseutil /k c:\exchsrvr\mdbdata\e00.log
As there are no spaces in the above file or folder names, you do not need to enclose the command with speech marks.  However, to save disappointment, pay special attention to the path where the databases are stored.
Key terms: Hard and Soft recovery.  Checkpoint file, Transaction Logs
A common scenario for this /cc switch is that you have just restored an Exchange mailstore from last night's backup and you want to replay today's logs.  Eseutil /cc would achieve your goal provided you issue the command from the folder that contains the Restore.env file.  This special file (Restore.env) carries information about the restore in general and the log sequence numbers in particular.
Command: eseutil /cc path to restore.env
There is a sister command just to check the contents of restore.env : eseutil /cm path to restore.env
Likely contents of restore.env would include paths to source files.  Names of databases .edb and .stm files.  See more on restore.env here.
Terminology check
Cases where you force a replay of the transaction logs are referred to as a hard recovery.  Eseutil /cc gets the restored database up-to-date through such a hard recovery process.  Hard recovery replays the transaction logs after a backup, either select the 'Last Backup Set' checkbox, or use eseutil /cc.  Remember that eseutil /cc looks for instructions in the Restore.env file.  Perhaps you can see what I mean when I say that some aspects of Eseutil are just command line methods of controlling Exchange 2003.
In cases where you are short of disk space, call for the temp switch.  Eseutil /cc "name of temp folder" /t.  Naturally you would need to substitute "name of temp folder" for a real folder.
Eseutil /cc tip wait for event id 205To be sure that the recovery is complete, wait until you see an ESE event ID 205 in the Event Viewer, Application Log.
Soft recovery replays the logs - but only after the last checkpoint.  The normal routine at startup is for uncommitted transactions to be written to the database.  Just remounting the store triggers a built-in soft recovery routine.
With a soft recovery, Exchange processes a few recent transactions after the last checkpoint.  Soft recovery reads pointers in E00.chk, from this information it knows which transactions to commit or roll-back in order to get the database into a consistent state.  One such soft recovery scenario could be a sudden 'dirty' store shutdown, which resulted in transactions being interrupted.
If you delve more deeply, you find that eseutil /c has a whole family of commands e.g. cc /ch
Eseutil /cm - Read Restore.env
.

Eseutil / d is probably the commonest and the safest of eseutil's switches.  This switch works in the same way that Disk Keeper defrags a physical disk.  Take the problem where Exchange's mailstore is huge and does not shrink even after you have deleted several mailboxes.  You would like to recover the space occupied by the deleted mailboxes.  So this is a job eseutil /d.
To prepare for eseutil /d, first dismount the store.  There is no need to stop the Information Store service, just dismount the individual stores in the Exchange System Manager.  Next, make sure that you have plenty of free disk space, at least as much as the priv.edb or store.edb that you wish to defrag.  Navigate in the cmd window to the \exchsrver\bin folder and issue a command such as this:
Example: eseutil /d  e:\exchsrvr\mdbdata\priv1.edb (Or other path to your store)
If you really do not have enough free space try the Eseutil /d /t "f:\temp.edb".  Where the f drive has enough free space.  Always remember to remount the store once the defrag has finished.
Tip Exchange 2003 eseutil /d Take a reading before and after running the command  Take a reading of the store size before and and after running eseutil /d.

Exchange Monitor from SolarWindsGuy Recommends: The SolarWinds Exchange Monitor

Here is a free tool to monitor your Exchange Server.  Download and install the utility, then inspect your mail queues, monitor the Exchange server's memory, confirm there is enough disk space and check the CPU utilization. This is the real deal - there is no catch.  SolarWinds provides this fully-functioning product for free, as part of their commitment to supporting the network management community.
Free Download of SolarWinds Exchange Monitor

Typical Scenario: you have restored an Exchange 2003 database but you cannot mount the store.  When you examine the event log, you see errors: ESE ID 494 - Recovery failed with error -1216.  Further down in the Application Log you may see ESE BACKUP ID 904 and ID 905.
Do not run /r just for fun or  merely to see what happens, eseutil /r is strictly an emergency measure when all else fails to get the restored server working.
What can you do?  Really, you should backup the Exchange database as it is NOW.  Then Try eseutil /r e00 /i .  Note the sequence /r e00 /i is correct.  This assumes that your first, or base log is e00 not some other number.  If you have a storage group with multiple stores, I am afraid that you have to dismount all stores before running the /r switch.  Perhaps this reminds you that all members of a storage group share the same transaction log.
Scenario.  You try to recover a store.edb database.  However it fails, possibly because the corresponding transaction logs are missing.  For example, you may get an error: 'The database files in this storage are inconsistent'.  To gather more information try eseutil /mh.  You determine that the state is inconsistent, after backing up the current database, you try eseutil /p.  Follow up with isinteg -fix.
Eseutil troubleshootingAnother nasty problem is that you cannot backup the store.  The worst cases are errors caused by hardware malfunction.  As a last ditch, do or die measure, you could try eseutil /p.  I was going to say backup before you try, but of course in this particular case, backup is the problem.  How about a little lateral thinking and try to copy the store before you run eseutil /p.

Kiwi Syslog Server - Free Utility to Analyze Your Network Messages

Syslog messages are full of information for troubleshooting network problems.  When something goes wrong then surely there will be an error message in the syslog datagram - if only we can find that record and interpret the event.  What will help to capture and analyze such network messages is the Kiwi Syslog Server.
Free Download of Kiwi Syslog Server

Eseutil is a powerful utility.  It has at least three separate jobs, defragging stores, checking the .edb database files, repairing corrupted priv1.edb files.  My advice is to practice with the /cc switch before you have to use the /r (repair) switch on a live network.
Full list of Eseutil switches for Windows Exchange
Eseutil /cc Performs a hard recovery after a database restore.
Eseutil /d Performs an offline compaction of a database.
Eseutil /g Verifies the integrity of a database.
Eseutil /k  Verifies the checksums of a database.
Eseutil /m Generates formatted output of various database file types. e.g. /mh
Eseutil /p Repairs a corrupted or damaged database.
Eseutil /r Performs soft recovery to bring a single database into a consistent or clean shutdown state.
Eseutil /y Copies a database, streaming file, or log file.


Thanking You,
Mohammed Sameer

Saturday, June 4, 2011

Virtual Machene Technology


Virtual Machine Technology

View all answers
A.  
Virtual machine technology applies to both server and client hardware. Virtual machine technology enables multiple operating systems to run concurrently on a single machine. In particular, Hyper-V, a key feature of Windows Server 2008 R2, enables one or more operating systems to run simultaneously on the same physical system. Today, many operating systems are supported by Virtual PC 2007, Virtual Server 2005, and Hyper-V.
A.  
Virtual machine technology serves a variety of purposes. It enables hardware consolidation, because multiple operating systems can run on one computer. Key applications for virtual machine technology include cross-platform integration as well as the following:
  • Server consolidation. If several servers run applications that consume only a fraction of the available resources, virtual machine technology can be used to enable them to run side by side on a single server, even if they require different versions of the operating system or middleware.
  • Consolidation for development and testing environments. Each virtual machine acts as a separate environment, which reduces risk and enables developers to quickly recreate different operating system configurations or compare versions of applications designed for different operating systems. In addition, a developer can test early development versions of an application in a virtual machine without fear of destabilizing the system for other users.
  • Legacy application re-hosting. Legacy operating systems and applications can run on new hardware along with more recent operating systems and applications.
  • Simplify disaster and recovery. Virtual machine technology can be used as part of a disaster and recovery plan that requires application portability and flexibility across hardware platforms.
  • Moving to a dynamic datacenter. Hyper-V, along with systems management solutions, helps you to now create a dynamic IT environment that not only enables you to react to problems more efficiently but also to create a proactive and self-managing IT management solution.
A.  
Our goal is to help customers make their IT systems more self-managing and dynamic so that they can gain more control of their IT systems, and enable their businesses to respond faster and stay ahead of the competition. We're doing this by:
  • Providing a complete set of virtualization products that span from the desktop to the datacenter
  • Helping manage all IT assets—both physical and virtual—from a single platform
We are making broad investments—in the areas of the platform, management, applications, interoperability, and licensing, and working to enable customers to take advantage of their existing platform investments, utilize their existing support skills and infrastructure, and to reduce costs associated with implementing virtualized environments.

Configuration of Hyper V for windows 2008 server

Hyper-V Installation Prerequisites
Hyper-V requires specific hardware. You can identify systems that support the x64 architecture and Hyper-V by searching the Windows Server® catalog for Hyper-V as an additional qualification. The Windows Server catalog is available on the Microsoft Web site .
To install and use Hyper-V, you need the following:
  • An x64-based processor.
  • Hardware-assisted virtualization. This is available in processors that include a virtualization option; specifically, Intel VT or AMD Virtualization (AMD-V).
  • Hardware Data Execution Protection (DEP) must be available and be enabled. Specifically, you must enable the Intel XD bit (execute disable bit) or the AMD NX bit (no execute bit).

 

Additional considerations

  • The settings for hardware-assisted virtualization and hardware data execution protection are available in the BIOS. However, the names of the settings may differ from the names identified previously.
    For more information about whether a specific processor model supports Hyper-V, check with the manufacturer of the computer.
  • If you modify the settings for hardware-assisted virtualization or hardware data execution protection, you may need to turn off the power to the computer and then turn it back on. Restarting the computer may not apply the changes to the settings.



Setting the Administrator Password

During the first logon after the installation of Hyper-V Server, you will be prompted to enter a user name and create a password.  The following instructions outline this process.
Note: This process will only occur during the first logon after the installation of Hyper-V Server.
1.       Click on Other User.
2.       In the user name field type Administrator and then press ENTER.
3.       A message stating that “The user’s password must be changed before logging on the first time” appears. Click OK.
4.       Type a new password in the New password field.
5.       Type the same password again in the Confirm password field, and then press ENTER.
6.       You will see a confirmation that your password has been changed. Click OK.

Hyper-V Configuration Tool

The Hyper-V configuration tool is intended to support the administrator with a menu driven User Interface (UI) to configure Hyper-V Server. The Hyper-V configuration tool starts automatically at login of the system administrator or it can be started manually.
To manually start the Hyper-V configuration tool
1.       Change to the system drive.
2.       Type hvconfig.cmd and then press ENTER.
Figure 1: Hyper-V Server Configuration Tool

Domain/Workgroup

The current Domain/Workgroup settings are displayed in the default Hyper-V Configuration screen.


To join a domain
1.       Type 1 and press ENTER.
2.       Type D and press ENTER.
3.       Type the domain name and press ENTER.
Example: domain.corp.company.com
4.       Type an authorized domain\user
Example: domain\user1
5.       When prompted, type a password for the user and press ENTER. 
6.       You will be prompted with “You must restart your computer to apply these changes.  Restart now?”
7.       Click Yes to reboot.
NOTE: By default, running virtual machines will automatically be saved prior to restarting the Hyper-V Server.
NOTE: If a domain user has not been added to the local administrators group, you will not be able to make system changes, such as changing the computer name, using the domain user.  To add a domain user to the local administrators group, allow the computer to reboot.  Next, log onto the computer as the local administrator and follow the steps listed below in the section Add Local Administrator.
To join a workgroup
1.       Type 1 and press ENTER.
2.       Type W and press ENTER.
3.       Do one of the following:
If currently joined to a workgroup
1.       Type the name of the workgroup to join and press ENTER.
2.       You will be prompted with “Welcome to the workgroup: workgroup name
3.       Click OK.
If currently joined to a domain
1.       Type the name of the workgroup to join and press ENTER.
2.       You will be prompted with “Machine currently joined to domain.  Do you want to remove this computer from the current domain now?” Click Yes.
3.       Type an authorized domain\user
Example: domain\user1
4.       When prompted, type a password for the user and press ENTER. 
5.       You will be prompted with “You must restart your computer to apply these changes.  Restart now?” Click No.
6.       Type 1 and press ENTER to configure the Hyper-V Server Workgroup name.
7.       Type W and press ENTER.
8.       Type the name of the workgroup to join and press ENTER.
9.       You will be prompted with “Welcome to the workgroup: workgroup name
10.   Click OK.

4.       Type 11 and press ENTER to restart the Hyper-V Server.
5.       You will be prompted with “Are you sure you want to restart?”
6.       Click Yes.
NOTE: By default, running virtual machines will automatically be saved prior to restarting the Hyper-V Server.



Computer Name

The current computer name is displayed in the default Hyper-V Configuration screen.
If joined to a workgroup
1.       Type 2 and press ENTER to change the computer name.
2.       Type the new computer name and press ENTER.
3.       You will be prompted with “The computer needs to be restarted in order to complete the operation.  The command completed successfully.” Click OK.
4.       You will be prompted with “You must restart your computer to apply these changes.  Restart now?” Click Yes to reboot.
NOTE: By default, running virtual machines will automatically be saved prior to restarting the Hyper-V Server.
If joined to a domain
1.       Type 2 and press ENTER to change the computer name.
2.       Type the new computer name and press ENTER.
3.       When prompted type the domain and the name of an authorized user and press ENTER.
4.       Next, type a password for the user and press ENTER.
5.       You will be prompted with “You must restart your computer to apply these changes.  Restart now?” Click Yes to restart.
NOTE: By default, running virtual machines will automatically be saved prior to restarting the Hyper-V Server.

Network Settings

Hyper-V Server network settings can be assigned by a DHCP Server or an IP Address can be assigned manually.
1.       Type 3 and press ENTER to configure the Hyper-V Server network settings.
2.       You will be presented with a list of available network adapters attached to your Hyper-V Server.
3.       Type the Index# of the adapter you want to configure and press ENTER.
4.       You will be presented with the current configuration for the network adapter you selected.
5.       Type 1 and press ENTER to configure the IP address for the selected network adapter
To receive an IP from a DHCP Server
1.       Type D and press ENTER
To assign a static IP to the network adapter
1.       Type S and press ENTER to manually assign a static IP to the network adapter.
2.       Type the desired static IP address and press ENTER.
3.       Type the desired subnet mask and press ENTER.
4.       Type the desired default gateway and press ENTER.

To configure DNS Server settings for the selected network adapter
1.       Type 2 and press ENTER.
2.       Type the IP address of the desired preferred DNS server and press ENTER.
3.       You will be prompted with “Preferred DNS server set.”
4.       Click OK.
5.       Type the IP address of the desired alternate DNS server and press ENTER.
6.       You will be prompted with “Alternate DNS server set.”
7.       Click OK.
To clear the current DNS Server settings
1.       Type 3 and press ENTER.
2.       You will be prompted with “DNS servers removed.  DNS servers will be automatically obtained from network.”
3.       Click OK.

6.       Type 4 and press ENTER to return to the default configuration page.

Add Local Administrator

Additional users can be added to the local administrators group on a Hyper-V Server computer.
To add a domain user to the local administrator group
1.       Type 4 and press ENTER.
2.       Type the domain name + username and press ENTER.
Example: domain\domain user
3.       You will be prompted with “User added to local Administrators group.  domain\domain user”
4.       Click OK.
NOTE: To add a domain user to the local administrator group, you must be currently joined to a domain (See Domain/Workgroup above).
To add a workgroup user to the local administrator group
1.       Type 4 and press ENTER.
2.       Type the username and press ENTER.
Example: user1
3.       When prompted, type a password for the user and press ENTER. 
4.       When prompted, type the password a second time and press ENTER.
5.       You will be prompted with “User added to local Administrators group. Username.”
6.       Click OK.

Windows Update Settings

The current Update settings are displayed in the default Hyper-V Configuration screen.

To set updates to automatic
1.       Type 5 and press ENTER.
2.       Type A and press ENTER to set updates to automatic.
3.       You will be prompted with “Windows Update set to Automatic.  System will check for and install updates every day at 3:00AM.”
4.       Click OK.
5.       You will be returned to the Hyper-V Server Configuration Tool and you will see “Automatic” next to “Windows Update Settings”.
To set updates to manual
1.       Type 5 and press ENTER.
2.       Type M and press ENTER to set updates to manual.
3.       You will be prompted with “Windows Update set to Manual.  System will never check for updates.”
4.       Click OK.
5.       You will be returned to the Hyper-V Server Configuration Tool and will see “Manual” next to “Windows Update Settings”.

Download and Install Updates

The current Update Status is displayed in the default Hyper-V Configuration screen.

NOTE: You must be connected to the internet to receive Hyper-V Server updates.

1.       Type 6 and press ENTER to search for updates.  You will be presented with a list of applicable updates.
2.       Type Y and press ENTER to download and install all updates.
3.       The download and installation of updates will begin.
Note: This may take some time.
Note: You may be prompted with “A restart is required to complete Windows Updates.  Restart now?” Click Yes to initiate a restart. By default, running virtual machines will automatically be saved prior to restarting the Hyper-V Server.
4.       You will be returned to the Hyper-V Server Configuration Tool and will see the current Hyper-V Update status next to “Download and Install Updates“.

Remote Desktop

The current Remote Desktop status is displayed in the default Hyper-V Configuration screen.
To enable Remote Desktop for clients running Remote Desktop with network Level Authentication
1.       Type 7 and press ENTER.
2.       Type E and press ENTER to enable Remote Desktop.
3.       Type 1 and press ENTER to allow only clients running Remote Desktop with Network Level Authentication (more secure).
4.       You will be prompted with “Remote Desktop enabled for clients only running Remote Desktop with Network Level Authentication (more secure).”
5.       Click OK.
6.       You will be returned to the Hyper-V Server Configuration Tool and will see “Enabled (more secure clients only)” next to “Remote Desktop”.
To enable Remote Desktop for clients running any version of Remote Desktop
1.       Type 7 and press ENTER.
2.       Type 2 and press ENTER to allow clients running any version of Remote Desktop (less secure).
3.       You will be prompted with “Remote Desktop enabled for clients running any version of Remote Desktop (less secure).”
4.       Click OK.
6.       You will be returned to the Hyper-V Server Configuration Tool and will see “Enabled (all clients)” next to “Remote Desktop”.
To disable Remote Desktop
6.       Type 7 and press ENTER.
5.       Type D and press ENTER to disable Remote Desktop.
6.       You will be prompted with “Remote Desktop disabled.”
7.       Click OK.
8.       You will be returned to the Hyper-V Server Configuration Tool and will see “Disabled” next to “Remote Desktop”.

Regional and Language Options

1.       Type 8 and press ENTER to configure or modify the Hyper-V Server Regional and Language options.
2.       You will be presented with the Hyper-V Server Regional and Language options dialog box.
3.       When you are finished configuring Regional and Language Options, click OK or Apply to commit the changes or Cancel to discard them.
Figure 2: Hyper-V Regional and Language Options



Date and Time

1.       Type 9 and press ENTER to configure or modify the Hyper-V Server Date and Time options.
2.       You will be presented with the Hyper-V Server Date and Time options dialog box.
3.       When you are finished configuring Date and Time options, click OK to commit the changes or Cancel to discard them.

Figure 3: Hyper-V Server Date and Time Settings

Log Off User

1.       Type 10 and press ENTER to log off the current user.
2.       You will be prompted with “Are you sure you want to log off?”
2.       Click Yes.

Restart Server

1.       Type 11 and press ENTER to restart the Hyper-V Server.
2.       You will be prompted with “Are you sure you want to restart?”
3.       Click Yes.
NOTE: By default, running virtual machines will automatically be saved prior to restarting the Hyper-V Server.

Shut Down Server

1.       Type 12 and press ENTER to shut down the Hyper-V Server. 
2.       You will be prompted with “Are you sure you want to shut down?”
3.       Click Yes.
NOTE: By default, running virtual machines will automatically be saved prior to shutting down the Hyper-V Server.

Exit to Command Line

1.       Type 13 and press ENTER to exit to the Command Line. 
NOTE: To return to the Hyper-V Server Configuration Tool, type hvconfig and press ENTER.

Open a new Command Line window

1.       Press CTRL+Shift+ESC to open Task Manager
2.       In Task Manager click File -> New Task (Run) -> CMD.

Hyper-V Server Remote Management

There are a few ways to remotely manage Microsoft Hyper-V Server:
·         Microsoft® Windows Server 2008 (a full installation) with the Hyper-V Manager
·         Microsoft® Windows® Vista SP1 with the Hyper-V Manager
·         Microsoft® System Center Virtual Machine Manager 2008
Choose which option is right for you and follow the corresponding steps below.

Hyper-V Server Remote Management with Microsoft® Windows Server 2008

To enable the Microsoft® Windows Server 2008 Hyper-V Manager MMC:
NOTE: The Hyper-V Manager MMC is automatically installed when the Hyper-V role is enabled on full installations of Windows Server 2008.
1.       Launch Server Manager from the Start menu.
2.       Click Add Features.
3.       Under Remote Server Administration ToolsàRole Administration Toolsà
a.       Enable Hyper-V Tools and click Next.
4.       Click Install.
5.       After the reboot, go to Administrative Tools in the Start menu and click on the Hyper-V Manager.
6.       On the left side of the MMC window, click on Hyper-V Manager.
7.       From the Actions menu, click Connect to Server, select Another Computer and enter the name or IP address of the server you want to connect to.

 


Hyper-V Server Remote Management with Microsoft® Windows Vista SP1

To enable the Microsoft® Windows Vista SP1 Hyper-V Manager MMC,
1.    
2.       After the reboot, go to Administrative Tools in the Start Menu and click on the Hyper-V Manager.
3.       On the left side of the MMC window, click on Hyper-V Manager.
4.       From the Actions menu, click Connect to Server, select Another Computer and enter the name or IP address of the server you want to connect to.

Hyper-V Server Remote Management with Microsoft® System Center Virtual Machine Manager

Please see the Microsoft® System Center Virtual Machine Manager documentation.

Setup Hyper-V Server virtual networks

Configure one or more virtual networks for virtual machines to access network resources.

Creating Hyper-V Server Virtual Networks

From a system running Microsoft® Windows Server 2008 or Microsoft® Windows Vista SP1 with the Hyper-V Manager management pack loaded, launch the Hyper-V Manager. 
1.       On the left side of the MMC window, click on Hyper-V Manager.
2.       From the Actions menu, click Connect to Server, select Another Computer and enter the name or IP address of the server you want to connect to.
3.       In the Actions menu click Virtual Network Manager…
4.       Under Create virtual network, select External and click Add.
5.       Type a name for the new virtual network, such as Corpnet and click OK.

NOTE: When you create a virtual network remotely, Hyper-V Server creates the new virtual switch and binds it to the physical network TCP/IP stack. If the Hyper-V Server system is configured with only one physical network adapter, this may result in a dropped network connection. This is normal while the virtual network is being created.