Showing posts with label windows server. Show all posts
Showing posts with label windows server. Show all posts

Wednesday, April 16, 2008

Assigning User Rights for Windows 2000, Server 2003, and XP continue...

If you are familiar with the complete list of rights used by Windows NT, you'll see that the privileges that Windows Server 2003 uses are similar to those, with a few additions. These are the privileges you can use with Windows Server 2003:

  • Debug programs—Thisright allows a programmer to do low-level debugging. It is helpful for applications developers and administrators. However, as in most networks, this right should be granted only on laboratory or development systems, and not on a production server. It is not a good idea to allow application development to be performed on the same computer that is a production server that network users make use of. The reason for this is obvious. The application being tested or created on a development system can potentially cause the server to crash, or corrupt data.
  • Manage auditing and security log—This right lets the user determine those objects and resources that will be recorded in the security log file, and view the events produced by the auditing.

Each of the previous privileges can be enabled for specific user accounts or groups. Some of these rights, however, are granted to groups by default. For example, the Backup Operators group can use the backup utility to back up files to offline storage, despite the protections that are in place for these files. This does not, however, give the Backup Operators group the capability of viewing or modifying files. Members of this group can just use the backup utility to save files to another media, such as a tape.

Internet 2010

Wednesday, March 19, 2008

Telnet continue...

The Log On tab functions the same as for other services. You should be familiar with how services work on Windows Server before using this tab or the Recovery tab. For example, using the Log On tab, you can select the user account that the service is run under. The AUTHORITY \ LocalService account is typical for the Telnet service as well as many other services for Windows Server 2003. For Windows 2000 Server, the LocalSystem account is generally used for running services. At the bottom of the Log On tab, you can choose a hardware profile for which the service can be enabled or disabled. Select the particular hardware profile you want to modify and use the Enable or Disable button.

The Recovery tab, determines how the service will be restarted if the service fails for some reason.

The options available on the Recovery tab are:

The Restart Computer Options button enables you to specify the number of minutes after which the computer will restart, if you have chosen that option in the preceding fields. You can see that you can also enter a message to display to users on the network who are using the Telnet service to inform them that the service is either not available or being restarted, depending on the options you selected on the Recovery tab. Use the Restart Computer Options button on the Recovery tab to display this dialog box.

The last tab, Dependencies, is used to list the other services that must be running before the Telnet service can be started. If one of these services fails, for example, the Telnet service itself can fail. And if there is a problem in restarting one of these services after the computer reboots (if you chose that option), the Telnet service will not restart. In this case, you should check the Event Viewer to determine the reason that a service that Telnet depends on isn't restarting. If the Telnet service fails because a dependent service fails, you might consider using a script file to check for and restart dependent services.

Tuesday, March 18, 2008

Sun Network Information System

NIS is used on Unix networks to keep important system files, such as the password file, synchronized among a group of servers. Remember that on Unix systems, each server has a password file, a user group file, and other important files that are managed locally on each server by default. This is similar to using a Windows computer in a standalone manner where each Windows computer has its own user account database.

NIS uses a database of maps that contain entries for the files the system administrator chooses to keep synchronized. For redundancy purposes, a master NIS server can be used along with slave NIS servers that receive updates from the master server.

Internet 2010

SFU version 3.5 contains a component that can be used to allow a Windows Server domain controller to operate as a NIS server. The Windows server can operate as either a master or slave NIS server. However, if it is to operate as a slave server, the master NIS server on the network must also be a Windows server. This is due to the way NIS is implemented in Windows Server: The information that Unix NIS servers store in a map database is stored in the Active Directory. The Active Directory schema is extended to include a class for each NIS map. Then objects are created based on this class for each map entry.

NIS uses its own protocol to send updates from a master NIS server to slave servers. The Active Directory, on the other hand, has its own method for replication information to other Active Directory replicas. The two methods are not compatible. That's the reason why a Windows domain controller cannot be made a slave NIS server to a Unix master NIS server. However, Microsoft does provide support for the NIS protocol so that Unix systems can become slaves to a Windows 2000 master NIS server! So, if you decide to integrate NIS into the Windows 2000 portion of your network, you'll have to make a Windows domain controller the master NIS server.

The advantages of using NIS should be obvious. On Unix networks, NIS relieves the administrator of having to manually coordinate important system files on multiple servers. By incorporating the SFU NIS server into the network on a Windows domain controller, you can use the tools designed around the Active Directory to manage not only your Windows users but also users on your Unix systems.

Another advantage to using a Windows-based NIS server is that the Active Directory is a hierarchical database, whereas the NIS database format is a flat namespace. You can place NIS maps into any container in the Active Directory, such as an organizational unit (OU). You can probably figure out from this that you can support multiple NIS domains in the same Active Directory database.

Monday, March 17, 2008

Do You Need to Upgrade the Operating System or Applications? continue...

There's one good reason to go ahead with the upgrade to the Windows 2003/XP platforms: support. This issue can be a minor one if you've already prepared your own support infrastructure, such as keeping personnel trained. One inexpensive way to do this is to subscribe to Microsoft's MSDN (Microsoft Developer's Network). MSDN gives you a superset of the documentation and knowledge articles that you can get from msdn .microsoft .com. Even though the articles on the Web site may be aged out over time, you can always turn to your CDs (or DVDs, if you chose that option) to find support for Windows 2000 as the next few years go by. Microsoft also offers a subscription to TechNet, which is a scaled-down version of the MSDN subscription. I suggest that you subscribe to one or the other as your budget permits. In a large network, the MSDN subscription is a small cost to pay for the many benefits (from programming to operating systems) you'll get.

Tip

Another option you might want to consider is the Microsoft Action Pack. This is a subscription that supplies Microsoft Partners with operating systems, Exchange Server, and a few other software items. If you do not need the development tools that come with an MSDN subscription, you can at least preview newer operating systems and some software by becoming a Microsoft Partner. You can sign up as a partner by becoming a reseller, or even a consultant.

Internet 2010

If you already have trained personnel for the current operating system and applications, support isn't that much of an issue for your network. Yet, Windows Server 2003 and Windows XP might be a good choice mainly because of the additional functionality and security improvements they provide. For example, Windows XP Professional has a user-friendly task-oriented GUI (although you can choose to revert to the classic Windows interface). Other important features of Windows XP Professional include a solution to what is called (in Microsoft documentation) DLL hell. Applications that now overwrite DLLs (dynamic link libraries) in the Windows environment (Windows 9X/Me excepted) are now stored in application-specific directories, so the core DLLs located in the system files directory remain untouched (except by Microsoft updates, of course). This can solve a lot of headaches for network administrators who are deploying new applications. So, if your network adopts new applications frequently, upgrading might be a good choice as opposed to a network that requires only minor upgrades for applications.

Windows XP also has many other new features, some that make the user experience easier and some of which solve problems that exist in Windows 2000. For example, the capability to set checkpoints and roll back to a previous state on the computer is an important one. This feature is called System Restore. If you or a user makes a change to the desktop's configuration or installs an application that causes problems, it's easy to simply use System Restore to go back to the previous configuration of the desktop without having to remove programs and diagnose other configuration changes. System Restore enables you to create these checkpoints yourself (for example, just before you make the changes), and automatically creates checkpoints on a periodic basis and when some changes are made to the operating system or applications. However, it's best to create a checkpoint yourself (a simple matter) before making changes to the desktop computer.

Tip

For more information about DLL hell and System Restore, see Platinum Edition Using Windows XP, published by Que Publishing (ISBN 07897279001.

System Restore is not a free lunch. It works by saving critical system files, including Registry settings, on the hard disk so that it will have the necessary information to restore your computer if you choose to roll back to a previous state. If disk space is important, this feature might not suit your environment. System Restore requires, at a minimum, 200MB of disk space. However, you can change this to a larger value to keep old restore points around for a longer period of time.

Windows XP is also available in an x64 version that supports the 64-bit extensions found in the latest desktop and workstation processors from Intel (processors that support EM64T) and AMD (processors that support AMD64). Although drivers must be rewritten to run for 64-bit operation, the user interface of the x64 edition of Windows XP is virtually identical to the original 32-bit version. If you need a native 64-bit edition of Windows, this is the way to go.

There are many other features that Windows XP offers for desktop users that go far beyond the scope. You might want to check out these features on Microsoft's Windows Web pages for Windows XP. There are many white papers and other documents available on Microsoft's Web site. Some changes are cosmetic—such as stacking multiple instances of a single program into one item on the toolbar when the toolbar has become overpopulated—to the new interface—to the capability to enable another user to take control of the desktop and assist a user with problems. Many of these new features are also offered by third-party products. However, if you have not yet invested in these kinds of products, you might find the features that Windows XP offers for desktop users—not to mention the features to make life easier for your help desk staff—worth the upgrade.

Windows Server 2003 versions are another story altogether. You'll find Windows Server 2003 Standard Edition, Windows 2003 Enterprise Server, and Windows 2003 Web Server, as well as numerous specialized versions such as Storage Server, SQL Server, and many others.

If you support Itanium servers, there are two versions of Windows Server 2003 optimized for Itanium: Enterprise Edition and Datacenter Edition. For 64-bit (x64) servers based on Intel Xeon and AMD Opteron processors, there are three versions available: Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition.

With all that said, let's now get on upgrading to Windows 2000 and then Windows 2003 if your network consists now of Windows NT 4.0.

Tip

Whatever you decide, check Microsoft's Web site and examine all the white papers and other documentation available to determine whether you'll benefit from an upgrade to Windows 2000, Windows XP, or Windows Server 2003.

Internet Blogosphere