This post was continued from Getting started with Microsoft Windows Server Update Services, Part VI: Disconnected network(1). From the previous, you have already exported the WSUS’s meta data and update files. On this post, I’ll show how to import files and metadata to the disconnected WSUS server (the imported server).
In case that you have WSUS server separated from the Internet, you can’t get updates directly. Microsoft has provided a solution by setting up another WSUS server which can connect and update from the Internet. Next, download updates from the Internet to this server and then export updates and metadata to files and copy (may be via backup tape) to the WSUS server which is on the disconnected network.
After 4 parts have passed, you have finished basic configuration on WSUS server. Next, you need to configure client computers to contact the WSUS server to get some updates. The best way is to configure from the domain group policy so that you only configure once. Then, the policy will be apply to all clients in the domain but this approach requires you to have an active directory in domain. In this post, I’ll show how to configure clients using group policy to get updates from the WSUS server.
Note: You can also configure clients that in a non-active directory, too. But I won’t cover in this article.
Nessus vulnerability scanner is a tool which can discover and analyze vulnerabilities in the system so that IT staff can fix that holes and hence the system becomes more secure. Before scanning the system, it is necessary to update Nessus’s plugins to make sure that it’s up-to-date and will able to detect the latest vulnerabilities. If you have a disconnected network from the Internet, you need to update the Nessus’s plugins manually.
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.
Have you ever concern about security of your data? What if someone stolen your storage device or laptop which you have some privacy information on there? Or you have some private data that keep on a PC or laptop and don’t want other to access them.
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.
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 2.5 License.