Windows 2003 Server Performance Advisor

08/29/2007




Overview  

Microsoft ® Windows Server ™ 2003 Performance Advisor is the latest version of Server Performance Advisor, which is a simple but robust tool that helps you diagnose the root causes of performance problems in a Microsoft Windows Server 2003 deployment. Server Performance Advisor collects performance data and generates comprehensive diagnostic reports that give you the data to easily analyze problems and develop corrective actions

Microsoft ® Windows Server ™ 2003 Performance Advisor provides several specialized reports, including a System Overview (focusing on CPU usage, Memory usage, busy files, busy TCP clients, top CPU consumers) and reports for server roles such as Active Directory, Internet Information System (IIS), DNS, Terminal Services, SQL, print spooler, and others. 
 

System Requirements 

 

·        Supported Operating Systems: Windows Server 2003  

 

Install procedure step by step 

 

 

 

1.   Download this tool at this Microsoft Site Link  

 

2.   Check requirements below before install tool:  

 

    1. .NET 1.1 Framework

       

    2. SQL 2000 or MSDE (if you use the data trending feature). For more information, see "Trending Data" in the Server Performance Advisor Help

       

    3. Do not install on Windows 2000 or Windows XP as neither are supported.

       

3.  1.  Setup

 

 

 

 

 

 

 

 

 

 

4.  2. Accept agreement

 

 

 

 

 

 

 

 

 

5.   3. Define user/users that can use this tool and installation path directory

 

 

 

 

 

 

 

 

 

6.   4. Define Data Storage Folder

 

 

 

 

 

 

 

 

 

 

7.  5. Define Reports Folder

 

 

 

 

 

 

 

 

 

8.   6. Install

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

9.   7. Launch the tool

 

 

 

 

 

 

 

 

 

10 8.  Select Data Collector Group

 

 

 

 

 

 

 

 

 

11 9. An example of Data Collector Group

 

 

 

 

 

 

 

 

 

12 10. View result report

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Install Exchange with Disasterrecovery oprion

08/28/2007

Forty Days and Forty Nights

Should disaster strike, you should be well prepared for the recovery process if you have taken the steps required ahead of time. Of course, when it comes time to play magic man and get the network up and running again, you will need more than just your backup media. The following is a short (very short) list of things I would recommend to keep on hand in the event this sort of catastrophic disaster should find its way into your world:

  • Replacement hardware that is identical to the original hardware.
  • Software setup CD-ROMs; for Windows 2000 Server and Exchange 2000 Server plus any other applications your network requires.
  • New routers, firewalls, WAN circuits and other network hardware devices as required for reconnecting your network.
  • Good Internet connectivity if you plan on restoring the capability for sending mail across your firewall.
  • Time, lots and lots and lots and lots of time—get the picture?

You have a couple of different levels of disaster recovery that are supported in Exchange 2000 Server. You can perform the following:

  • Recovering an entire Exchange 2000 Server implementation
  • Recovering a single Exchange 2000 Server
  • Recovering individual Exchange 2000 Server databases
  • Recovering mailboxes of deleted users

Now, let me clarify a little bit here…the first two items in the list above are truly disaster recovery situations that will require the full disaster recovery process as we will discuss in the next situation. The last two items in the list above are much simpler recovery actions, will require only minutes of your time and will not be discussed in this article.

The Heat Is On

When the day comes that you have to put your disaster recovery plan into action, you will find that the process is fairly simple conceptually, but can be much more difficult when it comes to actually executing it. Exchange 2000 Server provides a means within itself to help restore a system or server, but this must be done after rebuilding the Windows 2000 server itself. The basic process to perform a disaster recovery is outlined in the following steps:

  1. Reinstall Windows 2000 Server on the computer, taking care to ensure that the following items are observed:
    1. Install the same version of Windows 2000 that you had installed on the server previously: Server, Advanced Server or Datacenter Server.
    2. Install Windows 2000 to the same volume and path as it was installed during the previous installation.
    3. Configure the server with the same name as during the previous installation.
    4. Configure the installation to have all of the components installed in the previous installation.
    5. Install Windows 2000 as a stand-alone server; do not join the server to a domain during Windows 2000 installation or thereafter.
  2. Restore the system volume to the new server using NTBACKUP as follows:
    1. Launch the Backup utility by clicking Start > Programs > Accessories > System Tools > Backup.
    2. Click the Restore Wizard icon to start the restoration.
    3. Click Next on the Welcome to the Restore Wizard window to continue.
    4. From on the What to Restore window, choose the media and the backup set from within that group that you want to restore. If you do not see the media you want to restore from, click Import Media to open a new window enabling you to browse to the media you wish to work with. Select the files within the group to be restored. Click Next to continue after making all of your selections.
    5. On the Completing the Restore Wizard screen, you can review the settings that you have supplied. If all settings are acceptable, click Next to continue. If the settings are not acceptable, click Advanced to configure advanced restoration options.
    6. On the Where to Restore window, you will need to decide the location to which the restored files will be copied. In this case (assuming that all volumes and paths have been created properly), you need to choose Original Location and click Next.
    7. On the How to Restore screen you will need to specify what to do if the restore process detects a file in the restore location that is the same as a file trying to be restored. In this situation, I prefer to select Always replace the file on disk, but you can make your selection according to your preferences. When you have made your selection, click Next to continue.
    8. On the Advanced Restore Options window, select which special options you want applied to your restoration and click Next to continue. If you want additional information on the advanced options, search Windows 2000 Server online help for “To set advanced backup options”.
    9. Click Finish on the Completing the Restore Wizard window to begin restoring the selected files.
    10. Click Close to finish the process when the restore completes.
  3. Restore the system state to the new server using NTBACKUP by following the same procedure as for the system volume, but this time selecting the System State data to be restored.
  4. Run Exchange 2000 Server setup in Disaster Recovery mode as follows:
    1. From a command prompt, launch the Exchange 2000 Server Installation Wizard in Disaster Recovery mode by entering X:SetupI386Setup.exe /DisasterRecovery, where X is the location of the Exchange 2000 Server setup CD-ROM.
    2. The window as shown in Figure 1 will open and you can then proceed to install Exchange 2000 Server as you normally would. Remember that you must select every component that was originally installed on the computer to the action Disaster Recovery. If originally installed components are not selected for Disaster Recovery, then you must manually select them.


Figure 1 – The Exchange 2000 Server Installation Wizard in Disaster Recovery mode.

    1. An important note if you are trying to accomplish this procedure by using the Exchange 2000 Server online help files—The directions provided are wrong in that you are directed to use the following command to perform the Disaster Recovery installation: X:SetupI386SetupDisasterRecovery. As you can obviously see, this will not provide the desired result.
  1. Restore the your Exchange 2000 Server databases using NTBACKUP by following the same procedure as for the system volume, but this time selecting the media and group that contains your Exchange 2000 Server databases. The following amplifying instructions apply to restoring databases. For more information, see the “Prepare to Restore Information” topic in the Exchange 2000 Server online help.
    1. Verify that the Exchange Server services are running on the server in question (a departure from previous versions of Exchange Server). See the “Monitor Services Used by Exchange” topic in the Exchange 2000 Server online help for more information on this.
    2. Dismount the databases to be restored. See the “Dismount an Information Store” topic in the Exchange 2000 Server online help for more information on this action.
    3. Select the media and databases to be restored. Click Start Restore to continue. Figure 2 shows this step of the process.


Figure 2 – Preparing to restore the Exchange 2000 Server databases.

    1. On the Restoring Database Store window (shown in Figure 3), specify a directory to store the log and patch files during the restore in the Temporary location for log and patch files. Be careful to ensure that the specified location has enough disk space to store the files. DO NOT specify the Temporary location directory to be same as the original location of the database of log files, or the restore process will not work.


Figure 3 – Selecting a temporary location for the log and patch files.

    1. If you are restoring a full backup without any incremental backups, select Last Backup Set to start log file replay after restoring the database. If you are restoring a backup with incremental backups, do not select this option until you are restoring the last incremental backup.
    2. If you want the database to be mounted as soon as the restoration process is complete, select the Mount Database After Restore option.
    3. To begin restoring the database, click OK.
  1. You’re done—finally! Time to test and deploy your newly restored Exchange 2000 Server implementation. However, if you are running the Key Management Server, the Site Replication Service or participating in an Exchange 2000 Server cluster you will have additional work left to complete. I will discuss these scenarios in a separate article.

The process to restore a single server is the same as the aforementioned procedure for restoring an entire Exchange 2000 Server system. The only difference is that you will only be working with one specific server, and thus you will choose your restoration options accordingly.

Wrap-up

You may have noticed that you have to go through three restoration steps in this process: restoring the System Volume, restoring the System State and restoring the Exchange 2000 Server databases. If you try to restore system data and Exchange data, you will receive the warning dialog box as shown in Figure 4.


Figure 4 – Error when attempting to restore system data and Exchange data at the same time.

The NTBACKUP utility that ships with Windows 2000 is replaced by an updated version during the installation of Exchange 2000 Server. This updated version allows for online backups of the Exchange 2000 Server files.

Although no amount of preparation can prevent disaster from striking, you can take steps to minimize the impact of such a disaster when one occurs. Even though the process to get your network up and running again smoothly could take days or even a week or two, it’s still a better solution than having nothing at all to fall back on. Always remember the rule of the seven P’s and you will be in a much better position when the dreaded day comes to be.

Read all from source...

WinRM that has now been updated to support the WS-Management industry standard

08/23/2007

 

 




 

 

 As time goes on, you will see more references to WinRM, especially with Windows Server 2008. Windows 2003 R2 had a form of WinRM that has now been updated to support the WS-Management industry standard.

Who should be interested in this? People that manage servers remotely and need a firewall friendly protocol to use. People that are looking into deploying Windows Server 2008 and especially Windows Server 2008 Core. People that need to interface with the BMC adapters on servers from remote.

Anyway, KB
936059 updates Windows XP SP2 and Windows Server 2003 WinRM components to bring them more in line with what Windows Vista and Windows Server 2008 are using. 

New Microsoft Office Communications Server 2007 TechNet Virtual labs

08/23/2007

Experiment with the newest features and familiarize yourself with Microsoft Office Communications Server 2007 in a free, online virtual environment.

 

TechNet Virtual labs are simple—no complex setup or installation is required. You need to sign up (did I mention it's free?) with your passport account, and after you do that you will gain access to the online labs. The labs themselves are based on pre-configured virtual machines, so there are no hardware or software pre-requisites, and no installation to perform.

 

 

The Office Communications Server 2007 topics of the newest Virtual labs are:

 

  • Deploying and configuring

     

  • Configuring and using conferencing

     

  • Using management and troubleshooting tools

     

  • Compliance and archiving

     

Check out the Microsoft Office Communications Server 2007 Virtual labs

 

Links to the newest Virtual Labs are:

 

 

MS Office 2007 virual version with Softgrid

08/21/2007

Hi all,

Microsoft have published an article that describe how to make Office 2007 virtualization, please read this article, try to virtualize it and if you have feedback about this, please write an email to my address ale@caloni.net

I will publish any issue about this virtualization....

good luck!