There is a built-in command on Windows XP and Windows 2003 which can gather system configuration information to display in command-line mode. This command works on Windows only. With this command, you can get System Information on both local or remote computer so you don’t have to login or remote desktop to the remote computer.
This post is continued from Getting started with Microsoft Cluster Service, Part VI: Create a MSSQL server cluster (1).
Well, 5 parts have passed and now you should familiar with MSCS. This part, you’ll learn how to create another clustering service which is an important service that support clustering by design. It is Microsoft SQL Server. To setup MS SQL Server clustering, you’ll need to own a license of an enterprise edition of MS SQL Server. Next, I’ll show how to setup Microsoft SQL Server 2005 cluster. Like the previous part, I decide to separate this part into 2 posts because it’s a quite long part.
When you have installed WSUS 3.0 SP1, the configuration wizard appears to let you configure WSUS for the first time. You can configure to synchronize updates from Microsoft Update directly or other WSUS server, specify proxy server for WSUS, determine which products you want to synchronize, determine which classification (critical updates, tools, drivers, service pack, etc.) of updates you want.
After all the requirements have been installed successfully in the previous part, I’m going to install WSUS in this part. The updates will be stores on locally at C:\WSUS and I’ll keep information on Windows Internal Database which will be installed while installing WSUS. If you plan to keep lot of updates or service many client computers, I would recommend using Microsoft SQL Server for performance issue. For a web site for client computers to connect to this WSUS server, I’ll let WSUS create a new web site on port 8530 instead of port 80 which is a common port and may be expose security issue.
In this part, I’ll show how to install software requirements for WSUS on Windows Server 2003.
Microsoft Windows Server Update Services (WSUS) is a Windows service that helps in distribution Microsoft’s updates to clients in network. It downloads updates from Microsoft Update and installs the updates to client computers in network so that each computer doesn’t need access to the Internet and download updates from Microsoft website itself. Hence, if you have a lot of computers that running Windows that require updates in your network, you can save a lot of bandwidth of the Internet connection. Also, WSUS enables centralized management. It has an administrative console that summarizes current updates available on the server and updated status of each client computer that connect to the WSUS server.
This post continue from last post “Getting started with Microsoft Cluster Service, Part V: Create a file server cluster (1)”. I decide to separate this part since it’s quite long to be keep in a post. In this post, I’ll create File Share resource which depends on all of the resources that I’ve created in the prevoius post. Then, I’ll bring all the resources online to complete create a file server cluster. After that, I’ll try to failover the file server cluster service from one node to another node.
In this part and next following post, I’m going to create a file server cluster that has 2 nodes which are BKKSQL010 and BKKSQL020. This part, I’ll create a group to hold all resouces for the file server cluster. Then, I’ll create a physical disk resource (Disk R:) on the server cluster to keep my shared files. Next, I’ll create a virtual IP address for client to access the shared folder. Last step in this part, I’ll create a network name resource to the IP address so I can access the shared folder through this name besides the IP address. I’ll cover how to create a file share resource on the next post.
From previous part, I have a server cluster ‘BKKCluster.virtual.com’ with a node on BKKSQL010. With a node, I can’t use failover feature of the cluster (Failover means switching applications and services from one node to another node). Therefore, I need to add another node to this cluster server to enable failover feature. In this part, I’ll show how to add node (BKSQL020) to the cluster server.
From last part, I have complete configured the requirement for creating a server cluster. Now I’ll create a new cluster server name ‘BKKCluster’ and add ‘BKKSQL010′ as a first node on the cluster server.
In this part, I’ll show how to add new disks on both servers (BKKSQL010 and BKKSQL020) as shared disks using Microsoft iSCSI Initiator. The first disk will be a quorum disk on Q: drive which has capacity 512 MB. The second disk will be a shared disk to keep applications and services on R: drive which has capacity 8 GB.
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 2.5 License.