Student Academic blog

if you got error while inststalling Team Foundation.You must install Service Pack 2 or later to complete installation. This service pack must be installed before you install this Microsoft Team Foundation product.

ALL, Windows vista,

What Is Scheduler?

Windows has a built-in scheduler that allows you to set up such tasks. In XP, it is accessed through Start/Programs/Accessories/System Tools/Scheduled Tasks.

You can schedule any application that can be run via command line or by clicking an icon, using multiple scheduling options.

How To Use Scheduler

I thought the best way to do this was to demonstrate. I am going to assume that I want to run Freecell on the first and third Mondays of the month at 9 a.m.

1. Start up scheduler. Choose Start/Programs/Accessories/System Tools/Scheduled Tasks. The scheduled task window will open.
2. Double-click Add Scheduled Task. The wizard will start. Click Next.
   
3. Choose the application. Or click Browse to select one not in the list. Click Next.
   
4. Choose when to run it. I have selected Monthly. Click Next.
   
5. Choose the time, day and when. I have chosen 9 a.m., on the first Monday of every month. Click next.
   
6. Add logon information. This allows the computer to run it, regardless of who is logged on. Click next.
   
7. Edit the job. Check the Open Advanced Properties. This will give access to the “guts” of the job. Click Finish.
   
8. Click on the Schedule Tab. Then click on Multiple Schedules. This will allow us to set up the third Monday.
   
9. Click New to set up the new schedule time. The drop down list shows all schedules for this job.
10. Fill in the information. Add 9 a.m. for the third Monday.
    

It is very easy to automate your computer using Scheduler. Everything from simple jobs to complex maintenance can be run through this utility.

ALL, Windows, Window Server 2003 windows

In Windows Server 2008 file system quotas are managed with the File Server Resource Manager (FSRM) console (which is installed as a role service in the File Services role), the command line utility dirquota, or with Windows PowerShell using a COM API.

Figure 1: Windows Server 2008 File Server Resource Manager

There are two kinds of quota available - hard quotas which set a limit and enforce it, and soft quotas which set a limit but only report on it.  Soft quotas are useful for monitoring disk space use.  Quotas are commonly applied using quota templates, which are a mechanism for easily applying the same quota settings to one or more folders.  Quota Templates are the recommended way to configure quotas and FSRM includes some example templates which cover a range of scenarios, including using both hard and soft quota types.

Before we start to configure quotas which will generate e-mail messages, the quota File Server Resource Manager needs to be configured with an SMTP server, and optionally, the default administrator recipients, and the default “from” address.

Like all aspects of quota management, the FSRM settings can be applied using three different tools and you can choose the method appropriate to your needs.

To configure FSRM using the FSRM console:

1. Launch the File Server Resource Manager
2. Select the root node, labelled “File Server Resource Manager”
3. In the Action Pane click “Configure Options...”
4. Enter an SMTP server and if desired configure the other settings

   

5. Click the “OK” button

To configure FSRM using the command line:

1. Open an elevated command prompt window
2. Enter the command “dirquota admin options /From:quota-admin@example.com /AdminEmails:quota-admin@example.com /SMTP:smtp.example.com”

To configure FSRM using Windows PowerShell:

1. Open Windows PowerShell
2. Enter these commands (or save them as a script and run it):

Quota Example – Home directories with a 5GB limit

A common use of file system quotas is to put limits on the size of user’s personal storage space (folders which are often referred to as home directories) on a file server.  The requirements of this scenario are to limit the space each user can use to 5GB, alert administrators when 90% of the quota has been reached, and automatically apply quotas to new home directories.  The solution requires the implementation of new quota template and an auto apply quota.

Step 1: Create the new quota template

The first step is to create a new template, which we will use later to apply the quota to the file system.  Using a template means we can easily make changes to all folders where we have applied the template quota settings.  The template can be created using the FSRM, the dirquota command line tool, or PowerShell, meaning you can choose the tool with which you feel comfortable with and that fits most of your scenarios.

To create the new quota template using the FSRM:

1. Launch the File Server Resource Manager
2. Expand “Quota Management” -> “Quota Templates”
3. In the Action Pane click “Create Quota Template”
4. Enter the template name and set the space limit

   

   Note: To set a soft quota (for monitoring only) check the “Soft Quota” radio button

5. Click the “Add” button to add a notification threshold
6. Set the notification percentage to 90, check the “Send e-mail to the following administrators”, and enter an appropriate destination e-mail address. You can also customise the message text.

   

7. Click the “OK” button twice

To create the new quota template using the dirquota command line utility:

1. Open an elevated command prompt (or Windows PowerShell) window
2. Create a text file called notification.txt containing the text of the notification message (an example of this text message can be downloaded from this article)
3. Enter this command:
   

Note: To set a soft quota (for monitoring only) change “/Type:Hard” to “/Type:Hard”

To create the new quota using Windows PowerShell:

1. Open Windows PowerShell
2. Enter these commands (or save them as a script and run it):

Step 2: Create the Quota

The next step is to use the new quota template to apply the quota to the file system.

In this example we’ll say that the home directories are all subfolders of C:\Home.  Because we want any new home folders to automatically have the quota applied we need to create an Auto apply Quota.  Auto apply quotas are applied to all existing subfolders and any future folders.

To create the quota using the FSRM:

1. Launch the File Server Resource Manager
2. Expand “Quota Management” -> “Quotas”
3. In the Action Pane click “Create Quota”
4. Enter the quota path and choose the appropriate template

   

    

5. Click the “Create” button

To create the quota using the dirquota command line tool:

1. Open an elevated command prompt window
2. Create a text file called notification.txt containing the text of the notification message (an example of this text message can be downloaded from this article)
3. Enter the command “dirquota autoquota add /Path:C:\Home /SourceTemplate:"Default Home Directory (5GB Limit)"”

To create the quota using Windows PowerShell:

1. Open Windows PowerShell
2. Enter these commands (or save them as a script and run it):
   

Quota Exceptions / Folder-Specific Quotas

Naturally there will be occasions when a folder needs to be excluded from a template or auto apply quota.  In these situations you can easily add a specific quota for that folder to either increase the limit or to disable the quota entirely.

To create the quota exception using the FSRM:

1. Launch the File Server Resource Manager
2. Expand “Quota Management” -> “Quotas”
3. Select the folder you wish to make the exception for
4. In the Action Pane click “Edit Quota Properties...”
5. Enter new limit for the quota

   

6. Click “OK”

To create the quota exception using the dirquota command line tool:

1. Open an elevated command prompt window
2. Enter the command ...
   “dirquota quota add /Path:C:\Home\John_Smith /SourceTemplate:"Default Home Directory (5GB Limit)" /Limit:10GB /Overwrite”

To create the quota exception using Windows PowerShell:

1. Open Windows PowerShell
2. Enter these commands (or save them as a script and run it):

How Quotas Affect Clients

When a client maps a network drive to a folder which has a hard quota applied the size of the volume and the amount of available disk space shown is equal to the quota settings.

Figure: Mapped drive showing hard quota limit as volume size

When a hard quota is met or exceeded clients will receive a message telling them that the volume is out of disk space.

Figure: Insufficient disk space message

Viewing Quotas

Administrators can view hard and soft quotas using FSRM, and viewing quotas this way can be a quick method for finding large folders or large consumers of space.

Figure: Quotas in File Server Resource Manager

ALL, Windows

Deploying the Failover Cluster Feature

Before you can configure Windows 2008 Servers to act as clusters, you must install the Failover Cluster feature. To do so, begin by opening the Server Manager, and selecting the Features container. Click the Add Features link, and Windows will display a list of the various features that you can install. Select the Failover Clustering check box, as shown in Figure A, and click Next. At this point, you will see a warning message telling you that a server restart will be required. You don’t have to do anything to acknowledge the message though. Just click the Install button to install the feature.  When the installation process completes, click Close and reboot your server if necessary. Now, perform this procedure on your second cluster node.

Figure A

Select the Failover Cluster option, and click Next.

The Failover Cluster Management Console

When we set up clustering in Windows Server 2003, we used a wizard for the configuration process, but we had to call the wizard from the command line via the Cluster command. Although the Cluster command still exists in Windows Server 2008, the individual commands that I showed you in Part 1 for invoking the cluster wizard no longer work. The good news is that you no longer have to launch the wizard from the command line. In Windows Server 2008, Microsoft gives us an administrative tool that you can use to perform various clustering functions.  You can access this tool by selecting the Failover Cluster Management command from the server’s Administrative Tools menu.

Creating the Cluster

You are now ready to create our cluster. As before, we are going to be creating an active and a passive node, which I will be referring to as Node 1 and Node 2. We can get started by opening the Failover Cluster Management Console on Node 1. When the console opens, click the Create Cluster link, found in the console’s Management section. When you do, Windows will launch the Create Cluster Wizard.

Click Next to clear the wizard’s Welcome dialog, and the wizard will prompt you to enter the names of the cluster nodes. Enter the name of Node 1, and click the Add button. Once Windows validates the server’s name and adds it to the list, repeat the process by entering the name of Node 2 and clicking the Add button. When both cluster nodes have been added to the list, click Next.

You should now see a dialog warning you that Microsoft does not support the use of clusters unless the cluster configuration can be validated. You are now presented with the option of running a validation wizard. Choose the option labeled Yes, When I Click Next, Run Configuration Validation Tests, and Then Return to the Process of Creating the Cluster

Click Next, and the wizard will take you to an introductory dialog, as shown in Figure B,that describes the validation process. Go ahead and click Next to move on. You are now asked if you want to run all of the validation tests, or if you want to select specific tests to run. Choose the option to run all of the tests and click Next. You should now see a screen that confirms the tests that you are about to perform. Click Next to begin the validation tests. When the validation tests complete, you may receive some warnings (particularly in regard to storage), but you should not receive any errors. Click Finish.

Figure B

This dialog introduces you to the validation tests.

Now that the validation is complete, Windows returns us to the Create Cluster Wizard. At this point, you must enter the name and IP address that you wish to assign to the cluster, as shown in Figure C. Be sure to make note of which names and addresses you use, because you will need to reference them again later on.

Figure C

Enter the name and IP address that you want to assign to the cluster.

After entering the cluster’s name and IP address, click Next, and you should see a summary screen outlining the details of the cluster that you are creating. Take a moment to read the summary and make sure that everything is correct. Assuming that all is well, click Next, and Windows will create your cluster. When the process completes, click Finish.

Configuring Networking for the Cluster

Now that you have finished creating the cluster, you must make sure that the network adapters are configured properly for the cluster. Windows Server 2008 normally does a pretty good job of automatically configuring the network interfaces for you, but it is still important to double check the configuration.

Navigate through the Failover Cluster Management Console to Failover Cluster Management | <your cluster name> | Networks. You should now see listings for both of your network segments, as shown in Figure D. They should be listed as Cluster Network 1 and Cluster Network 2 respectively.

Figure D

Both networks should be displayed in the Failover Cluster Management Console.

Right click on Cluster Network 1, and choose the Properties command from the shortcut menu. When you do, you will see a properties sheet for the connection. Make sure that this is the connection isn’t the private segment that you are reserving for communication between cluster nodes. Now, verify that the Allow Cluster to Use this Connection option is selected You should also make sure that the Allow Clients to Connect Through This Network check box is selected. Click OK to close the properties sheet.

Now, right click on Cluster Network 2, and select the Properties command from the resulting shortcut menu. This network connection should be the private segment that services the cluster nodes. Once again, you want to make sure that the Allow Cluster to Use This Network Connection option is selected. However, the Allow Clients to Connect Through This Network option should not be selected. Click OK to close the properties sheet and return to the Failover Cluster Management Console.

Configure the Node and File Share Majority Quorum

In the previous article, I explained that a majority node set cluster has to have more than two nodes, because otherwise there is no node majority in a failover situation. Since CCR only works on two node clusters though, we need to create a file share witness on our hub transport server. This allows the file share that we create to take the place of the third cluster node.

The first thing that we need to do is to create a share on a hub transport server that can be used as the file share witness. To do so, go to your hub transport server, and open a Command Prompt window. You must now enter the following commands:

In the code above, we are granting the cluster access to the FSM_DIR_CCR folder on our hub transport server. You will notice that every time I reference the cluster name, I am putting a dollar sign after the cluster name. The dollar sign tells Windows that we are granting access to a computer account rather than to a user account.

Now that we have prepared our hub transport server, we need to configure the cluster quorum settings. To do so, go back to one of your cluster nodes and open the Failover Cluster Management Console.  Once the console opens, right click on the listing for your cluster, and select the More Actions | Configure Cluster Quorum Settings commands from the resulting shortcut menus.

At this point, Windows will launch the Configure Cluster Quorum Wizard. Click Next to clear the wizard’s Welcome screen, and you will be taken to a screen that asks you to select the quorum configuration that you want to use. Choose the Node and File Share Majority (For Clusters With Special Configurations) option, as shown in Figure E, and click Next.

Figure E

Choose the Node and File Share Majority option.

The next screen that you will encounter asks you for the path to the file share that you want the cluster to use. Enter the path to the share that you created earlier in UNC format (\\<your hub transport server’s name)\FSM_DIR_CCR). You can see an example of this in Figure F. Click Next, and the wizard will take you to a confirmation screen. Take a moment to make sure that the information that is presented on this screen appears correct, and then click Next. Windows will now configure the quorum settings. When the process completes, click Finish.

Figure F

Enter the path to the file share that you created.

Installing Exchange Server

Now that we have created our cluster, it is time to install Exchange Server 2007. There are a few things that you need to take into account prior to beginning the installation process.

For starters, I am assuming that both of your cluster nodes have the Exchange Server prerequisites installedYou should also  keep in mind is that the Clustered Mailbox Server role cannot coexist on a server with any other Exchange Server roles. This means that at a minimum you will already need to have an Exchange 2007 hub transport server and client access server in place prior to deploying your clustered mailbox server.

One last thing that you need to keep in mind is that if you are going to be installing Exchange onto a Windows Server 2008 based cluster, then you must install Exchange 2007 SP1 or higher. You can’t install the RTM release and then upgrade to SP1 later on. You must start with SP1 or higher. If you are going to be installing Exchange onto Windows Server 2003, then you can install Exchange 2007 with or without the service pack, although it is always preferable to use the latest service pack.

Configuring the Active Node

The process for setting up the active node isn’t all that different from configuring a typical mailbox server. Since we must begin by setting up the active node, you should perform these steps on Node 1.

Begin the installation process by double clicking on Setup.exe. When the Exchange Server 2007 splash screen appears, click on Step 4: Install Microsoft Exchange Server 2007 SP1. This will cause Setup to launch the installation wizard.

The first screen that you will see is really nothing more than a welcome screen. You can just click Nextto skip it. You will now be prompted to accept the server’s license agreement. After doing so, click Next.

The next screen that you will encounter asks you whether or not you want to enable error reporting. Whether or not you want to use error reporting is really up to you. After you make your decision, click Next.

The following screen will ask you if you want to perform a typical Exchange Server installation or a custom installation. You can only configure a clustered mailbox server by performing a custom installation. Therefore, choose the Custom Exchange Server Installation option, and click Next.

You will now be prompted to select the Exchange Server roles that you want to install. Select the Active Clustered Mailbox Server Role check box, as shown in Figure G. When you do, all of the other options will be grayed out, because the clustered mailbox server role cannot coexist with any other Exchange Server role.

Figure G

Select the Active Clustered Mailbox Role check box.

Click Next, and Setup will ask you what type of clustered mailbox server you want to create. Choose the Cluster Continuous Replication option. Before continuing, you must enter the name that you want to assign to your clustered mailbox server, as shown in Figure H. This is the name that will be unique to Exchange Server.

Figure H

Choose the Cluster Continuous Replication option and then enter the name that you want to use for your clustered mailbox server.

Click Next, and you will be prompted to enter the server’s IP address. You should enter the IP address that will be unique to Exchange Server.

Click Next, and Setup will perform a prerequisite check to make sure that all of the necessary components are in place. Assuming that the check succeeds, click the Install button to begin the installation process.

When the installation process completes, click Finish. You may see a message telling you that a restart is required before placing the server into production. If you receive such a message, just click OK to acknowledge it. Rather than restarting the server immediately, we need to stop the clustered mailbox server service, and move it to our passive node. As you will recall though, we haven’t actually installed Exchange onto the passive node yet. This makes things a little bit messy, but it isn’t going to cause us any problems. My personal preference is to perform this operation from the command line, but you can use the Failover Clustering Console.

To stop the Clustered Mailbox Service, open the Exchange Management Shell, and enter the following command:

Stop-ClusteredMailboxServer <your clustered mailbox server name> -StopReason Setup –Confirm:$False

Stopping the Clustered Mailbox Service allows our passive node to take ownership of the service.  You can now safely restart Node 1. When the node restarts though, Node 2 still has ownership of the clustered mailbox server. To fix this, open a command prompt window (not EMS) and enter the following command:

Cluster Group <your clustered mailbox server name> /Move:<the name of node 1>

Once the move has completed, we just need to start the Clustered Mailbox Service. To do so, open the Exchange Management Shell and enter the following command:

Start-ClusteredMailboxServer <your clustered mailbox server name>

Installing the Passive Node

Now that our active node is operational, we can install our passive node. Begin the installation process by double clicking on Setup.exe. When the Exchange Server 2007 splash screen appears, click on Step 4: Install Microsoft Exchange Server 2007 SP1. This will cause Setup to launch the installation wizard.

The first screen that you will see is really nothing more than a welcome screen. You can just click Next to skip it. You will now be prompted to accept the server’s license agreement. After doing so, click Next.

The next screen that you will encounter asks you whether or not you want to enable error reporting. Whether or not you want to use error reporting is really up to you. After you make your decision, click Next.

The following screen will ask you if you want to perform a typical Exchange Server installation or a custom installation. You can only configure a clustered mailbox server by performing a custom installation. Therefore, choose the Custom Exchange Server Installation option, and click Next.

You will now be prompted to select the Exchange Server roles that you want to install. Select the Passive Clustered Mailbox Role. Once again, the other roles will be grayed out to prevent you from selecting them, but the management tools will be installed automatically. You also have the option on this screen of specifying a database path. If you do enter a non default path, it must match the path used by the active node.

Click Next, and Setup will perform a readiness check to make sure that the server has been properly prepared. When the readiness check completes, click the Install button. When the installation completes, click Finish.

Once again, you will receive a message telling you that your server needs to be restarted. This time though, you can restart the server without having to do anything special because this is a passive node.

ALL, Windows

When a single Web Server machine isn’t enough to handle the traffic on your Web site it’s time to look into building a Web Farm that uses multiple machines on the network acting as a single server. to handle a application and maintain the web server to run smoothly.

Virtual IP address with three Load Balancing Cluster is configured.When a request comes to Cluster server , machine intercept the request for theIP , re routes the request to the Machine , Main Cluster Load Balancing based on rules

three server A is main and B,C are re routes by A on the request shown in figure.

ALL, IIS, Windows, Window Server 2003