Google
 

Wednesday, January 9, 2008

page 5 Excersie 2. 1: lnstallation of Windows 2003 Enterprise Edition



• Press Next to accept the Typical settings option if you have one of the following situations:

• You have a functional DHCP on your network.

• You have a computer running Internet Connection Sharing (ICS).

• You’re in a workgroup environment and do not plan to have any other servers or Active Directory at all, and all other workgroup members are configured in the same manner.

• Otherwise select Custom Settings and press Next to customize your network settings. Highlight the TCP/IP selection and press Properties.

• In the General tab enter the required information. You must specify the IP address of the computer, and if you don’t know what the Subnet Mask




continuing next page 6



page 4 Excersie 2. 1: lnstallation of Windows 2003 Enterprise Edition

Current System Locale - Affects how programs display dates, limes, currency, and numbers. Choose the locale that matches your location.

Current Keyboard Layout - Accommodates the special characters and symbols used in different languages. Your keyboard layout determines which characters appear when you press keys on the keyboard.

• If you don’t need to make any change just press NEXT.

• If you do need to make changes press Customize and add your System Locale etc.

• Type your name and organization.

• Type the product key.

• Enter the appropriate license type and number of purchased licenses.

• Type the computer name & a password for the local Administrator.



account. The local Administrator account resides in the SAM of the computer, not in Active Directory. If you will be installing in a domain, you need either a pre-assigned computer name for which a domain account has been created, or the right to create a computer account within the domain.

• If you enter a password that is blank or does not match the required complexity settings you will get a warning message.

• Select the date, time, and time zone settings.

• Setup will now install the networking components.

• After a few seconds you will receive the Networking Settings window, if you have a NIC that is not in the HCL (see the What’s the HCL? page) and Windows Server 2003 cannot detect it, or if you don’t have a NIC at all, setup will skip this step and you will immediately go to the final phase of the setup process.


continuing next page 5

page 3 Excersie 2. 1: lnstallation of Windows 2003 Enterprise Edition. The text-based portion of the Setup program







• Setup will then begin copying necessary files from the installation point

(CD, local 1386 or network share).

Note: If you began the installation process from an MS-DOS floppy, make sure you have and run SMARTDRV from the floppy, otherwise the copying process will probably last more than an hour, perhaps even more. With SMARTDRV (or if setup was run by booting from CD) the copying will probably last a few minutes, no more than 5 max.

• The computer will restart in graphical mode, and the installation will continue.

The GUI-based portion of the Setup program

  • The setup process reboots and loads a GUI mode phase.
  • It will then begin to load device drivers based upon what it finds on your computer. You don’t need to do anything at this stage.
  • Click Customize to change regional settings, if necessary.

continuing page 4

page 2 Excersie 2. 1: lnstallation of Windows 2003 Enterprise Edition

• If the hard disk is unpartitioned, you can create and size the partition on which you will install Windows Server 2003.

• If the hard disk is already partitioned, but has enough unpartitioned disk space, you can create an additional partition in the unpartitioned space.

• If the hard disk already has a partition that is large enough, you can install Windows Server 2003 on that partition. If the partition has an existing operating system, you will overwrite that operating system if you accept the default installation path. However, files other than the operating system files, such as program files and data files, will not be overwritten.

• If the hard disk has an existing partition, you can delete it to create more unpartitioned space for the new partition. Deleting an existing partition erases all data on that partition.

• If you select a new partition during Setup, create and size only the partition on which you will install Windows Server 2003. After installation, use Disk Management to partition the remaining space on the hard disk.

Select a file system for the installation partition. After you create the partition on which you will install Windows Server 2003, you can use Setup to select the file system with which to format the partition. Windows Server 2003 supports the NTFS file system in addition to the file allocation table (FAT) and FAT32 file systems. Windows Server 2003, Windows XP Professional, Windows 2000, and Windows NT are the only Microsoft operating systems that you can use to gain access to data on a local hard disk that is formatted with NTFS. If you plan to gain access to files that are on a local Windows Server 2003 partition with the Microsoft Windows 95 or Windows 98 operating systems, you should format the partition with a FAT or FAT32 file system. We will use NTFS.


continue page3


Monday, January 7, 2008

Excersie lnstallation of Windows 2003 Enterprise Edition

Excersie 2. 1: lnstallation of Windows 2003 Enterprise Edition. The text-based portion of the Setup program

The setup process begins loading a blue-looking text screen (not GUI). In that phase you will be asked to accept the EULA and choose a partition on which to install 2003, and if that partition is new, you’ll be asked to format it by using either FAT, FAT32 or NTFS.

• Start the computer from the CD.

• You can press F6 if you need to install additional SCSI adapters or other mass-storage devices. If you do you will be asked to supply a floppy disk with the drivers and you CANNOT browse it (or a CD for that matter). Make sure you have one handy.

• If you want, you can press F2 to run the ASR sequence. For that you need a good backup created by the Windows Server 2003 backup program, and the ASR floppy disk. If you plan to install a new copy of 2003 - don’t do anything.

• Setup will load all the needed files and drivers.

• Select To Setup Windows Server 2003 Now. If you want, and if you have a previous installation of the OS, you can try to fix if by pressing R. If not, just press ENTER.

• Read and accept the licensing agreement and press F8 if you accept it.

• Select or create the partition on which you will install Windows Server 2003. Depending upon your existing disk configuration choose one of the following:



Next page2

Monday, December 31, 2007

Installing Windows Server 2003 prosidure


Installing Windows Server 2003

Plan your installation

When you run the Windows Server 2003 Setup program, you must provide

Information about how to install and configure the operating system. Thorough

planning can make your installation of Windows Server 2003 more efficient

by helping you to avoid potential problems during installation. An understanding

of the configuration options will also help to ensure that you have properly

configured your system.

Here are some of the most important things you should take into consideration

when planning for your Windows Server 2003 installation:

• Check System Requirements

• Check Hardware and Software Compatibility

• Determine Disk Partitioning Options

• Choose the Appropriate File System: FAT, FAT32, NTFS

• Decide on a Workgroup or Domain Installation

• Complete a Pre-Installation Checklist

After you made sure you can go on, start the installation process.

Operating Systems from Which You Can Upgrade

If you upgrade, Setup automatically installs Windows Server 2003, Enterprise Edition, into the same folder as the currently installed operating system. You can upgrade to Windows Server 2003, Enterprise Edition, from the following versions of Windows:

• Windows NT Server 4.0 with Service Pack 5 or later

• Windows NT Server 4.0, Terminal Server Edition, with Service Pack 5 or later

• Windows NT Server 4.0, Enterprise Edition, with Service Pack 5 or later

• Windows 2000 Server

• Windows 2000 Advanced Server

• Windows Server 2003, Standard Edition

Note: If you have a version of Windows NT earlier than 4.0, you cannot upgrade directly to a product in the, Windows Server 2003 family. You must first upgrade, to Windows NT 4.0 and apply Service Pack 5 before upgrading to a product in the Windows, Server 2003 family.

System Requirements and Hardware Compatibility

Before upgrading or installing your server, make sure that you have chosen hardware that supports Windows Server 2003, Enterprise Edition.

System Requirements

To ensure adequate performance, make se that computers on which you install or upgrade to Windows Server 2003, Enterprise Edition, meet the following requirements:

For an x86-based computer:

• One or more processors with a recommended minimum speed of 550 Mhz (minimum supported speed is 133 MHz). A maximum of eight processors per computer is supported. Processors from the Intel Pentium! Celeron family, AMD K6/Athlon/Duron family, or compatible processors are recommended.

• 256 megabytes (MB) of RAM recommended minimum (128 MB minimum H supported, 32 gigabytes (GB) maximum).

For computers with more than 4 GB of RAM, be sure to check the hardware compatibility information in the Windows Catalog at:

http://www.microsoft.com/windows/catalog/

For an Itanium architecture-based computer:

• One or more processors with a minimum speed of 733 MHz. A maximum of eight processors per computer is supported.

. 1 GB of RAM minimum, 64 GB maximum.

For computers with more than 4 GB of RAM, be sure to check the hardware

compatibility information in the Windows Catalog at:

http:/!www.microsoft.comfwindows/catalog/

• A hard disk partition or volume with enough free space to accommodate the setup process To ensure that you have flexibility in your later use of the operating system, it is recommended that you allow considerably more space than the minimum required for running Setup, which is approximately 1 .25 GB to 2 GB on an x86-based computer and 3 GB to 4 GB on an itanium architecture-based computer. The larger amount of space is required if you are running Setup across a network instead of from a CD-ROM, or if you are upgrading on a FAT or FAT32 partition (NTFS is the recommended file system).

In addition, a domain controller upgrade from Windows NT 4.0 could require much more space than other upgrades, because the existing user accounts database can expand by as much as a factor of ten during the upgrade, as Active Directory functionality is added.

Note: The setup process requires the free disk space described in the previous paragraphs. After Setup is finished, actual hard disk space used for the operating system will be more than the free space required for Setup, because of space needed for the paging file, for any optional components you install, and (on domain controllers) for user accounts and other Active Directory information. The usual size for the paging file is 1 .5 times the size of the RAM. For information about the paging file, optional components, user accounts, and information stored in Active Directory, see Help and Support Center. To open Help and Support Center, after completing Setup, click Start, and then click Help and Support.

• VGA or higher-resolution monitor (Super VGA 800x600 or higher recommended), keyboard, and (optionally) a mouse or other pointing device.

As an alternative, for operation without a monitor or keyboard, you can choose a remote diagnostic and support processor that is designed for products in the Windows Server 2003 family. For details, see the hardware compatibility information in the Windows Catalog at:

http://www.microsoft.com/windows/catalog/

For CD-ROM installation:

• A CD-ROM or DVD drive.

For network installation:

• One or more network adapters and related cables that are designed for products in the Windows Server 2003 family. For details, see the hardware compatibility information in the Windows Catalog at:

http://www.microsoft.com/windows/catalog/

• A server from which to offer network access for the Setup files. For additional hardware-based functionality:

• Appropriate hardware for the functionality you require. For example, if you plan to support network clients, the servers and clients must have appropriate network adapters and cables. As another example, if you require a server cluster, the entire cluster solution must be listed as compatible with Windows Server 2003, Enterprise Edition. For details about your hardware, see the hardware compatibility information in the Windows Catalog at:

http://www.microsoft.com/windows/catalog/

Hardware Compatibility

One of the most important steps to take before upgrading or installing your server is to confirm that your hardware is compatible with products in the Windows Server 2003 family. You can do this by running a reinstallation compatibility check from the Setup CD or by checking the hardware compatibility information at the Windows Catalog Web site. Also, as part of confirming hardware compatibility, check to see that you have obtained updated hardware device drivers and an updated system BIOS (or for an Itanium architecture- based computer, the correct firmware).

Regardless of whether you run a reinstallation compatibility check, Setup checks hardware and software compatibility at the beginning of an installation or upgrade and displays a report if there are incompatibilities.

Running a reinstallation compatibility check from the Setup CD: You can run a hardware and software compatibility check from the Setup CD. The compatibility check does not require you to actually begin an installation - or upgrade. To run the check, insert the Setup CD in the CD-ROM drive and, when a display appears, follow the prompts for checking system compatibility. You will be offered the option to download the latest Setup files (through Dynamic Update) when you run the check. If you have Internet connectivity, it is recommended that you allow the download.

Another way to run the compatibility check is to insert the Setup CD in the CD ROM drive, open a command prompt, and type:

d:\i386\winnt32/checkupgradeonly where d represents the CD-ROM drive. Checking hardware and software compatibility information on the Microsoft Web site.

Another way to confirm that your hardware and software are designed for products in the Windows Server 2003 family is to check the hardware and software compatibility information in the Windows Catalog at:

http://www.microsoft.com/windows/catalog/

Note that one type of hardware no longer supported is the Micro Channel bus.

Beginning the installation process

You can install Windows Server 2003 in several methods - all are valid and good, it all depends upon your needs and your limitations.

For example, you can install directly from a CD by booting your computer with the CD, or you can also copy the 1386 folder from a CD and run the setup process by going into the 1386 folder and using the WINNT or WINNT32 command (depending upon your existing operating system).

If doesn’t matter how you run the setup process, but the moment it runs - all setup methods look alike





Thursday, December 27, 2007

Description of Remote Desktop for Administrator &NTFS inhancement

Remote Desktop for Administrator

It provides remote access to most configuration settings, to diagnose a problem and test multiple solutions quickly. Remote desktop for Administration allows access to servers from anywhere in the work!. You can perform time- consuming batch administrative ‘such as tape backup’s remotely.Using remote desktop you can upgrade server applications and operating systems remotely.


NTFS Enhancement

i) Default Root Security on NTFS Partitions

With Windows 2000, the default root directory permissions on NTFS partitions gave everyone full control. For Windows Server, the root directory permissions have been tightened such that non-Administrators cannot write into the roof directory nor can non-Administrators modify files created by other users off of the root. Users will not be able to accidentally or maliciously place Trojans in the roof directory for subsequent invocation by administrators.



ii) NTFS Read-Only Volumes

This feature provides the ability to indicate an NT File System (NTFS) volume as read-only. An administrator occasionally requires the need to indicate an NTFS volume as read-only during backup operations. This enables the backup utility to mount the NTFS volume shadow copy as read- only.

iii) NTFS SetShortName for Backup

Windows NT File System (NTFS) allows both short and long filenames. The short filenames are implicitly created by NTFS when an application creates the file, subject to the tunnel cache state. Currently, when files are copied, backed up or restored, the short filenames are not preserved. There are also applications that use these short filenames to refer to files and they are not correctly backed up or restored. This feature enables the use of short file names to be preserved and correctly copied, backed up, restored. A user backs up a file server that includes registry entries that refer to short filenames and later needs to restore the files. All file names will be correctly preserved and restored.


Terminal Services Enhancements

In Windows Server 2003 Terminal Services uses RDP v 5.2. Using this remote

desktop protocol you get following enhancements:

• Remote access to Console / Session 0

• Audio redirection

• Serial/parallel port mapping

• PnP remote printer drivers

• Local drive mapping

• Session mapping

• Video enhancements include

• Full screen connection bar

• Increased resolution 1600 x 1200

• Color depth 24 bit.

• Speed optimization includes reduction in client graphical robustness based on connection speed

• Tighter default security settings.