The first answer is actually a bit off the main topic, but let me digress for a moment and talk about it before returning to the main item: workgroups. When I say, “Reduce the number of servers,” I’m talking about an unfortunate side effect of running Windows for Workgroups, Windows 9x/ME, Windows NT, 2000, or XP workstations—they all have the capability to become peer-to-peer servers. The browse masters don’t distinguish between industrial-strength servers running NT Server and low-octane peer-to-peer servers, so you could end up with a browse list that’s supposed to only list your servers, but actually lists all of your servers and workstations. In general, I think peer-to-peer networking is a bad idea. If a piece of data is important enough to be used by two employees, then it’s a company asset that should be backed up regularly and so should go on a managed file server, not a desktop machine that’s probably backed up once a decade. My recommendation is this: Disable the peer-to-peer sharing option on your Windows for Workgroups, Windows 9x/ME, Windows NT, 2000, and XP workstations. How you do this depends on the operating system of the work- stations in question. In NT 3.x and 4, open the Control Panel and then the Services applet; locate the service called Server and stop it, as well as disabling it for future reboots. In Windows 9x, go to Control Panel/Network/File and Print Sharing and make sure both options, to share files and printers, are unchecked. In Windows for Workgroups, make sure the sharing control in Network Setup is set not to enable file or printer sharing. In Windows 2000 and later, right-click My Computer and choose Manage, then find the Services folder and stop the Server service. (You’ll see more
A single Microsoft Small Business Server2003 Standard or Professional, Microsoft Small Business Server 2000, or Small Business Server 4.5 system A single server running WindowsServer2003, Windows 2000 Server, Windows NT 4.0 Server, Novell NetWare 4.2/ 5.1/ 6.x, Red Hat Linux, SuSE Linux, or other supported OS
For the DL380 server, we configured one of the six physical drives into a logical volume of approximately 36GB using the default RAID controller parameters. The operating system was installed on this volume. We then configured four drives connected to the SmartArray 5i controller into a single logical RAID 0 data volume of approximately 140 GB using the default RAID controller parameters described above. After installing the specific operating system, we used the disk management utilities to create four basic volumes on the single logical RAID 0 volume for a total of four volumes of approximately 36GB each. Figure 21 below shows the file system parameters used for each of the operating systems tested on the DL380 server.
Administrators who manage these distributed, remote servers need a solution that helps them limit network traffic over slow WAN connections, ensure the availability of files during WAN outages or server failures, and ensure that branch servers are backed up correctly. The Distributed File System solution in the Microsoft® WindowsServer™ 2003 R2 operating system helps administrators address these challenges by providing two technologies, DFS Namespaces and DFS Replication, which, when used together, offer simplified, fault-tolerant access to files, load sharing, and WAN-friendly replication.
With Windows 2000 load balancing, you can easily add and remove nodes to the cluster. Windows 2000 Advanced Server allows for up to 32 nodes, so you can start off with 8 nodes and increase that number when necessary. When you configure Application Center 2000, you’ll see this is an integral part of producing appropriate High-Availability solutions. Your load won’t always be the same. Take, for instance, an ecommerce site that sells gifts on the Internet. In December, around Christmas time, the amount of hits, requests, and sales for the sight generally increases exponentially. That said, you’d want to design your load-balanced solution to be able to function normally with eight servers (you see how to baseline and monitor performance in Chapter 8), and then add servers to the group when times of availability need to be increased. You’ll also want to be able to remove these servers when you finish. The beauty of this solution is you can lease server hardware when and where you need it, instead of keeping equipment you need to account for on hand all year. What’s important to understand here is you’re allotted that functionality, so you can plan for it because this chapter is where your initial design work takes place. If you need four servers to begin with, you’ll have to baseline the servers on hand, and then, during periods of high activity and use, baseline again. You’ll find your load is either over what you expected and you’ll need to add a server or you’ll find it’s under your expectations and you can survive the additional hits with the hardware you have. Either way, you can only determine this by performance monitoring the systems and knowing how many hits you get a month. All of this is covered in the last chapter of the book.
This article contains recommendations that may help you protect a computer that is running WindowsServer 2 R2, WindowsServer 2008, WindowsServer2003, MicrosoftWindows 2000, Windows XP, or Windows Vista fro viruses. This article also contains information to help you minimize the effect of antivirus software on system a network performance.
▪ Effective User Service Management. IntelliMirror ® – the ability to provide users with consistent access to their applications, roaming user profiles, and user data, from any managed computer – even when they are disconnected from the network, is enabled by WindowsServer2003 technologies such as Active Directory, Group Policy, Software Installation, Windows Installer, Folder Redirection, Offline Folders, and Roaming User Profiles. This also enables centralized backup of user data and configuration files by the IT organization. The volume shadow copy capabilities enable automated point-in-time backups of user data and provide self- service capabilities to allow users to find and restore lost or corrupted files. Together, these capabilities result in high levels of user productivity, satisfaction, and data safety.
– Virtual “Scripts” directory is not created when IIS is enabled. MetaFrame Presentation Server Setup installs a .Dll file—Wpnbr.dll—in a virtual directory called “Scripts.” This file is required if you are using the Web Interface for port sharing.
2.2.1 Manage DNS Zone Settings 2.2.2 Manage DNS Record Settings 2.2.3 Manage DNS Server Options 2.3 DNS Tools Might Include 2.3.1 System Monitor 2.3.2 Event Viewer 2.3.3 Replication Monitor 2.3.4 DNS Debug Logs Chapter 2: Review Questions Chapter 2: Review Answers
the network is to be a central, secure, managed file storage area. By centralizing file storage on a server, it becomes an order of magnitude easier to ensure the safety, integrity, recoverability, and availability of the core files of your business. Instead of having files spread all across the network on individual client com- puters, you have them in a single place—easier to share among collaborators, easier to back up, easier to recover in the event of a disaster, and easier to secure so that only those people who should have access to a file, do. The downside to having all your important files in a single location is the potential for a single point of failure and the need for high availability of the files, since your business depends on them. This makes it imperative that you carefully manage the underlying disks that support your file storage and that those disks be both redundant and thoroughly backed up.
There are five versions of WindowsServer2003, not including MicrosoftWindows Small Business Server, which is in a category by itself. MicrosoftWindowsServer2003, Stan- dard Edition is designed to meet the requirements of small-sized to medium-sized busi- nesses, and it includes all the necessary file and printer sharing, secure Internet connectivity, and collaboration capabilities to do so. MicrosoftWindowsServer2003, Enterprise Edition is for medium-sized to large-sized businesses and provides a stable enterprise infrastructure, which enables deployment of line-of-business applications and is appropriate for high-performance e-commerce solutions. MicrosoftWindowsServer2003, Web Edition is optimized for hosting a Web site, Web services, and applications. MicrosoftWindowsServer2003, Datacenter Edition is designed for business-critical solutions that require excellent performance and absolute stability under load, such as the performance required by enterprise database applications and high-volume transac- tion processing. MicrosoftWindows Compute Cluster Server2003 is a special, x64-only, version of WindowsServer2003 that is designed for easy and automatic deployment of high-performance computing (HPC) clusters. It is based on WindowsServer2003 Stan- dard x64 Edition, but it does not support installation of R2.
▪ Windows System Resource Manager (WSRM). WSRM enhances application availability and quality of service by providing control over application CPU and memory utilization, making it easier to run mixed application workloads on a single server. You can use WSRM to manage multiple applications on a single computer, users on a computer on which Terminal Services are installed, IIS app pools, or virtual machines. Managing resources with WSRM improves system performance and reduces the chance that applications, services, or processes will interfere with the rest of the system. This aligning of IT resources with business priorities creates a more consistent and predictable experience for users of applications and services running on the computer. WSRM’s accounting tracks resource usage, which results in improved understanding of application resource utilization; this accounting data can serve as the basis for charge backs and capacity planning. WSRM is offered on 32-bit and 64-bit versions of WindowsServer2003, Enterprise and Datacenter Editions.
The general administration of Windows servers is divided into four administrative categories. These include general server, hardware, backup and restore, and remote administration. Table 1-1 outlines the administrative activities that you must perform on an ongoing basis to ensure proper operation of the services you deliver to your user community. It also identifies the frequency of each task. You may or may not agree with the frequency of the activities outlined in Table 1-1. You may not even need to perform all of these activities because you don’t use some of the services mentioned here. This is why you should personalize this book. Use a highlight marker to mark the procedure number for each of the procedures you actually will use. That way, it will be simpler and faster for you to locate the procedures you use the most.
With Windows 2000, a global catalog server must be contacted for every login attempt; otherwise, the login will fail (unless there is no network connectivity, which would result in a cached login). This is necessary to process all universal groups a user may be a member of. When a client attempts to authenticate with a domain controller, that domain controller contacts a global catalog server behind the scenes to enumerate the user's universal groups. See Recipe 7.9 for more details. If you have domain controllers in remote sites and they are not enabled as global catalog servers, you may run into a situation where users cannot login if the network connection to the network with the closest global catalog server fails.
Module 4: Implementing User, Group, and Computer Accounts This module explains how to plan and implement Active Directory user, group, and computer accounts. It also explains how to create multiple user and computer accounts by using command-line utilities tools, such as CSVDE and LDIFDE, and how to manage accounts by using Windows Script Host. The module also explains how to implement User Principle Name (UPN) suffixes.
The total time for the LabSim for Microsoft’s Managing and Maintaining a Server2003 Environment Exam 70-290 course is approximately 28 hours and 50 minutes. The time is calculated by adding the approximate time for each section which is calculated using the following elements:
a standard modem connection to perform upstream data requests: Responses were then sent down to you via the much faster satellite link. MSN’s satellite offering is no longer available, but Microsoft’s partner company, Starband, now offers satellite Internet service. It is also available through a few other vendors, such as EarthLink’s DirecWAY satellite. DirecPC is now offering a two-way satellite service of its own. Satellite Internet is touted as a broadband alternative to DSL. Although this is some- what true, satellite Internet is not as fast as DSL. File downloads are fast, but there are more pauses and delays during Web surfing. This delay is partly an inevitable aspect of the technology. Sending a request signal from your computer to a satellite thousands of miles in space, having that request relayed to a land-based Web server, having the requested page sent back up to the satellite, and then having it relayed back down to your satellite dish adds up to tremendous network latency, even when transmissions are made at the speed of light! Satellite Internet works with a satellite modem similar to a DSL modem. You typically attach the modem to an available USB port on your com- puter. The satellite modem also connects to a home satellite dish installed on your roof or a pole in your yard using coaxial cables similar to those used for cable TV. Sending and receiving transmissions are sent to a satellite, which are then sent to a hub where the transmissions are sent over the Internet, as shown in the following graphic.
For over 8 years, HOBLink JWT has remained the leading Java RDP client for remote access to Windows Terminal Services on Windows 2000 Server, WindowsServer2003, and Microsoft XP Professional. No other RDP client has achieved such an acceptance, or is being used on a global scale in banking, insurance, government, public facilities and educational areas.
Supports local drive access on a variety of platforms -- including all versions of Windows, Mac and UNIX -- as well as server drive remapping to provide client drives using their native drive letters. The Terminal Server base platform supports this feature for client