How do you double-boot a Win 2003 server box? The Boot.ini file is set as read-only, system, and hidden to prevent unwanted editing. To change the Boot.ini timeout and default settings, use the System option in Control Panel from the Advanced tab and select Startup.
What do you do if earlier application doesn’t run on Windows Server 2003? When an application that ran on an earlier legacy version of Windows cannot be loaded during the setup function or if it later malfunctions, you must run the compatibility mode function. This is accomplished by right-clicking the application or setup program and selecting Properties –> Compatibility –> selecting the previously supported operating system.
If you uninstall Windows Server 2003, which operating systems can you revert to?
Win ME, Win 98, 2000, XP. Note, however, that you cannot upgrade from ME and 98 to Windows Server 2003.
How do you get to Internet Firewall settings? Start –> Control Panel –> Network and Internet Connections –> Network Connections.
What are the Windows Server 2003 keyboard shortcuts?
Winkey opens or closes the Start menu. Winkey + BREAK displays the System Properties dialog box. Winkey + TAB moves the focus to the next application in the taskbar. Winkey + SHIFT + TAB moves the focus to the previous application in the taskbar. Winkey + B moves the focus to the notification area. Winkey + D shows the desktop. Winkey + E opens Windows Explorer showing My Computer. Winkey + F opens the Search panel. Winkey + CTRL + F opens the Search panel with Search for Computers module selected. Winkey + F1 opens Help. Winkey + M minimizes all. Winkey + SHIFT+ M undoes minimization. Winkey + R opens Run dialog. Winkey + U opens the Utility Manager. Winkey + L locks the computer.
What is Active Directory?
Active Directory is a network-based object store and service that locates and manages resources, and makes these resources available to authorized users and groups. An underlying principle of the Active Directory is that everything is considered an object—people, servers, workstations, printers, documents, and devices. Each object has certain attributes and its own security access control list (ACL).
Where are the Windows NT Primary Domain Controller (PDC) and its Backup Domain Controller (BDC) in Server 2003? The Active Directory replaces them. Now all domain controllers share a multimaster peer-to-peer read and write relationship that hosts copies of the Active Directory.
How long does it take for security changes to be replicated among the domain controllers?
Security-related modifications are replicated within a site immediately. These changes include account and individual user lockout policies, changes to password policies, changes to computer account passwords, and modifications to the Local Security Authority (LSA).
What’s new in Windows Server 2003 regarding the DNS management?
When DC promotion occurs with an existing forest, the Active Directory Installation Wizard contacts an existing DC to update the directory and replicate from the DC the required portions of the directory. If the wizard fails to locate a DC, it performs debugging and reports what caused the failure and how to fix the problem. In order to be located on a network, every DC must register in DNS DC locator DNS records. The Active Directory Installation Wizard verifies a proper configuration of the DNS infrastructure. All DNS configuration debugging and reporting activity is done with the Active Directory Installation Wizard.
When should you create a forest?
Organizations that operate on radically different bases may require separate trees with distinct namespaces. Unique trade or brand names often give rise to separate DNS identities. Organizations merge or are acquired and naming continuity is desired. Organizations form partnerships and joint ventures. While access to common resources is desired, a separately defined tree can enforce more direct administrative and security restrictions.
How can you authenticate between forests?
Four types of authentication are used across forests: (1) Kerberos and NTLM network logon for remote access to a server in another forest; (2) Kerberos and NTLM interactive logon for physical logon outside the user’s home forest; (3) Kerberos delegation to N-tier application in another forest; and (4) user principal name (UPN) credentials.
What snap-in administrative tools are available for Active Directory? Active Directory Domains and Trusts Manager, Active Directory Sites and Services Manager, Active Directory Users and Group Manager, Active Directory Replication (optional, available from the Resource Kit), Active Directory Schema Manager (optional, available from adminpak)
What types of classes exist in Windows Server 2003 Active Directory?
Structural class. The structural class is important to the system administrator in that it is the only type from which new Active Directory objects are created. Structural classes are developed from either the modification of an existing structural type or the use of one or more abstract classes.
Abstract class. Abstract classes are so named because they take the form of templates that actually create other templates (abstracts) and structural and auxiliary classes. Think of abstract classes as frameworks for the defining objects.
Auxiliary class. The auxiliary class is a list of attributes. Rather than apply numerous attributes when creating a structural class, it provides a streamlined alternative by applying a combination of attributes with a single include action.
88 class. The 88 class includes object classes defined prior to 1993, when the 1988 X.500 specification was adopted. This type does not use the structural, abstract, and auxiliary definitions, nor is it in common use for the development of objects in Windows Server 2003 environments.
How do you delete a lingering object?
Windows Server 2003 provides a command called Repadmin that provides the ability to delete lingering objects in the Active Directory.
What is Global Catalog? The Global Catalog authenticates network user logons and fields inquiries about objects across a forest or tree. Every domain has at least one GC that is hosted on a domain controller. In Windows 2000, there was typically one GC on every site in order to prevent user logon failures across the network.
How is user account security established in Windows Server 2003? When an account is created, it is given a unique access number known as a security identifier (SID). Every group to which the user belongs has an associated SID. The user and related group SIDs together form the user account’s security token, which determines access levels to objects throughout the system and network. SIDs from the security token are mapped to the access control list (ACL) of any object the user attempts to access.
If I delete a user and then create a new account with the same username and password, would the SID and permissions stay the same? No. If you delete a user account and attempt to recreate it with the same user name and password, the SID will be different.
What do you do with secure sign-ons in an organization with many roaming users? Credential Management feature of Windows Server 2003 provides a consistent single sign-on experience for users. This can be useful for roaming users who move between computer systems. The Credential Management feature provides a secure store of user credentials that includes passwords and X.509 certificates.
Anything special you should do when adding a user that has a Mac? "Save password as encrypted clear text" must be selected on User Properties Account Tab Options, since the Macs only store their passwords that way.
What remote access options does Windows Server 2003 support?
Dial-in, VPN, dial-in with callback.
Where are the documents and settings for the roaming profile stored?
All the documents and environmental settings for the roaming user are stored locally on the system, and, when the user logs off, all changes to the locally stored profile are copied to the shared server folder. Therefore, the first time a roaming user logs on to a new system the logon process may take some time, depending on how large his profile folder is.
Where are the settings for all the users stored on a given machine? \Document and Settings\All Users
What languages can you use for log-on scripts? JavaScipt, VBScript, DOS batch files (.com, .bat, or even .exe)
Tuesday, June 29, 2010
Saturday, June 12, 2010
Remote OS Installation
Remote OS Installation
One of the most challenging and costly functions performed by IT staff today is deploying a new operating system to client computers on a network. The Windows® 2000 operating system Remote OS Installation feature was created to meet this need to deploy an operating system throughout an enterprise network without having to physically attend to each client computer. The Remote Installation Services (RIS) takes advantage of the new Dynamic Host Configuration Protocol (DHCP)-based remote boot technology to assist IT staff with deploying Windows 2000 Professional remotely—reducing and, in some cases, eliminating the need to visit the desktop. This document outlines the steps necessary to install, configure, and use RIS.
On This Page
Introduction Installing the Windows 2000 Remote Installation Services Authoring RIS within the Active Directory Setting Required User Permissions Installing Client Computers Using Remote Installation Configuring Remote Installation Services Client Installation Options Remote Installation Preparation Wizard (RIPrep) Remote Installation Boot Disk Option Remote Boot ROM PXE Architecture Conclusion Appendix A: Remote Installation Server and Workstation Hardware Requirements Appendix B: Frequently Asked Questions Related Links
Introduction
Remote Installation Services (RIS) ships as part of the Windows® 2000 Server operating system. This document outlines the steps necessary to install, configure, and use RIS.
RIS was designed to reduce the costs incurred by pre-installing or physically visiting each client computer to install the operating system (OS). By combining RIS with other Windows 2000 IntelliMirror™ management technologies features—User Data Management, Software Installation and Maintenance, and User Settings Management—companies benefit from better disaster recovery with easier OS and application management.
Prerequisites
See Appendix A below to ensure that both your server and client hardware meet the remote installation hardware requirements.
The drive on the server where you choose to install RIS must be formatted with the NTFS file system. RIS requires a significant amount of disk space and cannot be installed on the same drive or partition on which Windows 2000 Server is installed. Ensure that the chosen drive contains enough free disk space for at least one full Windows 2000 Professional compact disc—a minimum of approximately 800 megabytes (MB)–1 gigabyte (GB).
RIS requires several other services that also ship as part of Windows 2000 Server. These services can be installed on individual servers, or all on a single server, depending on your network design:
Domain Name Service (DNS) Server. Remote installation relies on DNS for locating the directory service and client machine accounts. You can use any Windows 2000 Active DirectoryTM service-compliant DNS server, or you can use the DNS server provided with Windows 2000 Server.
Dynamic Host Configuration Protocol (DHCP) Server. RIS requires a DHCP server to be present and active on the network. The remote boot-enabled client computers receive an IP address from the DHCP server before contacting RIS.
Active Directory. RIS relies on Windows 2000 Active Directory for locating existing client machines as well as existing RIS servers. RIS must be installed on a Windows 2000-based server that has access to Active Directory. This can be a domain controller or a server that is a member of a domain with access to the Active Directory.
To ensure a successful installation, you must install and configure the additional services described above in order for RIS to function. In addition, make sure that you have both the Windows 2000 Server and Professional CDs available.
Before beginning this step-by-step guide, you need to build the common infrastructure, which specifies a particular hardware and software configuration. The common infrastructure is covered in the Common Infrastructure step-by-step guide, "Part 1: Installing a Windows 2000 Server as a Domain Controller" http://www.microsoft.com/windows2000/techinfo/planning/server/serversteps.asp. If you are not using the common infrastructure, you need to make the appropriate changes to this instruction set.
Although not required, we also recommend reading and performing the exercises available in the Step-by-Step Guide to Understanding the Group Policy Feature Set. It addresses how Group Policy works and can be applied in the context of remote installations.
Prerequisites for Client Installations
Ensure that the client computer's network card has been set as the primary boot device within the system BIOS. When the client computer boots and is configured with the network card as the primary boot device, it requests a network service boot from the remote installation server on the network. Once contacted, the RIS server prompts users to press the F12 key to download the Client Installation wizard. Users should be instructed to press F12 only if prompted, and only if they need a new OS installation or access to maintenance and troubleshooting tools. Once the OS has been installed via RIS, the user can ignore the request to press F12 during future client computer reboots. If using the RIS boot floppy disk, simply insert the boot floppy into the drive and start the client computer. The computer boots from the floppy disk, and the user is requested to press F12 to initiate the network service boot. When the RIS boot floppy disk is used, the user must remove the boot floppy at some point after pressing F12 and before the text mode portion of setup completes.
Note: Compaq computer systems provide the ability to press the F12 key during power up on PC98 or Net PC-based systems. In this case, the user is required to press F12 on the Compaq Splash screen, and then press F12 again when prompted by the RIS server.
Top of page
Installing the Windows 2000 Remote Installation Services
The following instructions help you install, configure, and use the Windows 2000 Remote Installation Services.
Install Remote Installation Services
On a Windows 2000 Server, click Start, point to Settings, and click Control Panel.
Double-click Add/Remote Programs.
Double-click Add/Remove Windows Components.
Scroll down and select Remote Installation Services and Click Next.
Insert the Windows 2000 Server CD-ROM into the CD drive and click OK . The necessary files are copied to the server.
Note: After the CD is entered, a dialog box asks if you want to upgrade to the operating system. Click No and exit this screen.
Click Finish to end the wizard.
You are prompted to restart your computer. Click Yes.
When the server is done rebooting, logon as a local administrator.
To set up Remote Installation Services
Click Start, click Run, and type RISetup.exe. This starts the Remote Installation Services (RIS) Setup wizard.
The Welcome screen appears, indicating some of the requirements to successfully install RIS. Click Next.
The next screen prompts you to enter the server drive and directory where you would like to install the RIS files. The default drive and directory will be the largest non-system, non-boot, NTFS-formatted drive. In our example, this would be E:\RemoteInstall. Click Next.
Note: The drive on which you choose to install RIS must be formatted with the NTFS file system. RIS requires a significant amount of disk space and cannot be installed on the same drive or partition on which Windows 2000 Server is installed. Ensure that the chosen drive contains enough free disk space for at least one full Windows 2000 Professional compact disc —a minimum of approximately 800 MB–1GB.
The setup wizard prompts you to either enable RIS at the end of setup, or disable the service to allow modification of specific server options before servicing client computers. These options are:
Respond to clients requesting service. This option controls whether this RIS server responds to client computers requesting service at the end of setup. If this option is checked, the server will respond to clients and provide them with OS installation options. If unchecked, this RIS server will not respond to clients requesting service.
Do not respond to unknown client computers. This option controls whether this server responds to unknown client computers requesting a remote installation server. A client computer is known if a managed computer account object exists for it within Active Directory. This allows the administrator to offer only authorized—that is, pre-staged within the Active Directory—computers the OS installation options from this RIS server. This setting also provides support for multiple Remote Boot or Install servers from different vendors on one physical network. For example, if another vendor's remote install/boot server exists on the same network as the RIS server, you cannot control which server answers the client computer's request. Setting this option and pre-staging client computers ensures that this RIS server will service only pre-staged client computers.
For the purpose of this guide, select Respond to client computers requesting service and click Next.
The setup wizard prompts you for the location of the Windows 2000 Professional installation files. RIS supports the remote installation of Windows 2000 Professional only. Insert the Windows 2000 Professional CD into the server's CD drive and type the drive letter containing the CD (or browse to a network share that contains the installation source files). Click Next.
The wizard prompts you to enter the directory name that will contain the workstation files on the RIS server. This directory is created beneath the directory specified in Step 3 above. The directory name should reflect its contents—for example, Win2000.pro. Click Next to accept the default name of win2000.pro.
You are prompted for a friendly description and help text that describes this OS image. The friendly description and help text is displayed to users or IT staff during the client installation wizard (OSChooser) at initial startup on a remote client. For example, if this workstation OS will be tailored to sales staff, then a friendly description might be "Windows 2000 Professional for Sales Staff." The help text is displayed when the user selects the description within the Client Installation wizard. Make sure you provide clear help text to your users, to ensure that they choose the correct OS option at installation time. For this exercise, click Next to accept the default name of Microsoft Windows 2000 Professional.
At this point, you are presented with a summary screen indicating the choices you have made. Click Finish to confirm your choices. Once the installation wizard completes, you are ready to either service client computers, or additionally configure the RIS settings.
Wait while the wizard installs the service and settings you have selected. This takes several minutes. When it is finished, a screen appears as in Figure 1 below:
Figure 1: Completed RIS installation.
Click Done.
Now that RIS is successfully installed, you must authorize the RIS server within Active Directory. If you do not authorize the RIS server, it will fail to service client computers requesting a network service boot. The next section outlines these steps.
Top of page
Authoring RIS within the Active Directory
RIS allows you to control which RIS servers can service client computers on the network. For a RIS server to operate, it must first be authorized within Active Directory. If the RIS server is not authorized within Active Directory, client computers requesting service will not be able to contact the RIS server and will not be answered.
To authorize a RIS server within Active Directory, you must be logged on as an enterprise administrator or a domain administrator of the root domain. You can complete the following steps on any domain controller, member server of the domain, or a Windows 2000 Professional workstation that has installed the Administrator Tools Package containing the DHCP Server Management snap-in. This guide performs the authorization on a domain controller: specifically, the domain controller that would have been created by running Part I of the Common Infrastructure step-by-step guide.
Click Start, point to Programs, point to Administrative Tools and click DHCP. The following snap-in appears as in Figure 2 below:
Figure 2: DHCP Snap-In
Right-click DHCP in the upper-left corner of the DHCP screen, and select > Manage Authorized Servers. If your server is not already listed, click Authorize, and enter the IP address of the RIS server. Click > Yes when prompted to verify that the address is correct.
At this point, your RIS server is authorized within Active Directory and is now able to respond to client computers requesting service.
Note: If you authorize the RIS server on a non-domain controller computer, follow these steps to install the Administrator Tools Package: Click Start, click Run, and type adminpak.msi on a Server system. From a Professional based system, execute adminpak.msi from the Windows 2000 Server CD.
Top of page
Setting Required User Permissions
If users are allowed to use RIS to install their own client computers, the administrator must ensure that those users have been granted the correct permissions for creating machine accounts within the domain. The permissions granted using the steps below will allow users to create computer accounts anywhere in the domain.
Click Start, point to Programs, point to Administrative Tools, and click Active Directory Users and Computers.
Right-click the Domain Name (Reskit.com) at the top of the snap-in, and click the Delegate Control option.
A wizard starts. Click Next.
Click Add to add users who are allowed to install their own computers using Remote OS Installation.
For the purpose of this guide, highlight Everyone and click Add. Click OK.
Click Next to continue.
Check the Join a Computer to the Domain option, and click Next.
Click Finish. Users can now create computer account objects during the OS installation using the RIS service.
You can now either use the default RIS settings and immediately begin servicing client computers, or you can make changes to the RIS settings first. In either case, review the section titled "Prerequisites for Client Installations" above before servicing the first client computer.
Top of page
Installing Client Computers Using Remote Installation
This section describes the steps required to successfully install Windows 2000 Professional on a Net PC, a Managed PC (PC 98 compliant system), or a PC that contains a network card supported by the remote installation boot floppy. To ensure a successful client installation, complete all prerequisites listed at the beginning of this document.
Reboot your client machine from either the remote floppy or the PXE boot ROM. When prompted, press the F12 key to start the download of the client installation wizard.
Press Enter at the welcome screen.
For the user name, type Jon Grande (this user is created using the Common Infrastructure step-by-step guide discussed in the Prerequisites Section above.) Press the Tab key twice. For this instruction set, the password is left blank and the domain name should be entered as reskit.com. Press Enter to continue.
You will get a warning message that all data on the client machine hard drive will be deleted. To continue, press Enter.
A computer account and a global unique ID for this workstation are displayed. Press Enter to begin Setup. The Windows 2000 Setup program begins.
If prompted, type the Product Key (found on the back of the Windows 2000 Professional CD case) and click > Next. (Note: This step can be avoided by specifying the product key in the .sif file; see Windows 2000 Online Help for assistance in making this change to the .sif file.)
After the installation is complete, the user is prompted to log on to the network with an existing user account, password, and logon domain.
At this point, you have successfully configured and installed a remote operating system using RIS. See below for additional information on configuration options.
Top of page
Configuring Remote Installation Services
This section outlines the specific RIS configuration options that can be configured. If desired, these optional steps should be performed using the Active Directory Users and Computer snap-in on the RIS server.
Note: Although not covered in this guide, you can administer the majority of the RIS configuration settings from a Windows 2000 Professional client. To administer a RIS server from a Windows 2000 Professional client, install the Administrator Tools package AdminPak.msi that ships as part of the Windows 2000 Server CD. The Administrator Tools package can be deployed or installed from the\System32 directory on the server.
Click Start, point to Programs, point to Administrative Tools, and click Active Directory Users and Computers.
You are presented with your Active Directory tree as in Figure 3 below:
Figure 3: Active Directory Users and Computers Snap-In
There are two areas of administration concerning the configuration of the RIS server settings:
Remote installation server properties, which allow you to determine how this RIS server responds to client computers that request service.
Advanced settings, which provide additional flexibility regarding the ways in which client computers are installed.
Locate your RIS server computer object within the Active Directory Users and Computers snap-in. Depending on the type of server, domain controller, or member server of a domain, the server's computer object can be located in the Domain Controller Active Directory container or another container specified by the administrator at install time.
Click Domain Controllers in the left pane.
Right-click HQ-RES-DC-01 in the right pane.
Click Properties.
Click the Remote Install tab. The property page appears as in Figure 4 below :
Figure 4: RemoteInstall Options
The server options control how this RIS server responds to remote client computers requesting service.
Click Advanced Settings on the RIS server property page.
Click the down arrow next to the Generate client computer names using drop-down box as in Figure 5 below.
Figure 5: Client under Advanced
The administrator can define the automatic computer naming policy that is used during OS installation to provide the computer with a unique name. The computer name is used to identify the client computer on the network, similar to the older NetBIOS name used in previous versions of the Windows NT® and Windows operating systems.
This tab also allows you to define a default Active Directory container for client computer account object creation. You can group clients within a specific directory service domain or organizational unit (OU). During OS installation, Windows 2000 setup queries these settings to ensure the client computer is configured according to what the administrator has specified. These are the options:
Default directory service location. This option specifies that the computer account object for the client computer will be created in the default Active Directory computer accounts location. The default Active Directory location is set to the Computers container within the Active Directory. The client computer becomes a member of the same domain as the RIS server installing the client.
Same location as the user setting up the computer.This options pecifies that the client computer account object will be created within the same Active Directory container as the user setting up the machine. For example, if Jon logs on within the Client Installation wizard and his user account currently resides within the "Users" Active Directory container, the client computer account is created within the "Users" container in the Active Directory.
A specific directory service location. This option allows the administrator to set a specific Active Directory container where all client computer account objects installed from this server are created. It is assumed that most administrators will select this option and specify a specific container for all remote installation client computer account objects to be created in.
Note: If an end user is setting up the client computer, the user must have the appropriate rights to create the computer account within the domain or OU chosen. For more information on giving users computer account creation permissions, please see the RIS online Help.
Note: In order for all client computers using the RIS feature for OS installation to contain the same settings, all remote installation servers need to be configured in the exact same way. This release does not support replication of OS images or RIS configuration settings between RIS servers.
Specify the desired user name parameters and directory service location and click Apply.
Click the Images tab.
The Images tab is used for managing the client operating system images installed on a RIS server. Its options allow an administrator to add, remove, or modify the properties of an operating system image.
There are two types of images that can be displayed on the Images tab:
CD-based.A CD-based image is simply a copy of the Windows 2000 Professional CD. This installs only the base operating system without applications or configuration settings.
Remote Installation Preparation (RIPrep). RIPrep images are a combination of the OS, locally installed applications, and configuration settings. Many companies standardize on a single type of OS installation across their organization. Administrators can now use RIS to install the base OS, then add corporate standard applications and configure the installation exactly as they want. Once the workstation is configured appropriately, the administrator runs the Remote Installation Preparation Wizard (RIPrep) utility to create that image on an available RIS server. Once the image is replicated on the RIS server, new client computers requesting an OS installation can download the image. For more information on the RIPrep wizard and feature set, please see the section, "Using the Remote Installation Preparation Wizard" below.
Use the Addoption to add a new CD-based OS image or to associate an unattended setup answer file (*.sif) to an existing CD-based image on the RIS server. You can associate a number of unattended setup answer files to a single OS-based CD Image. This allows the administrator to offer users a variety of unattended Windows 2000 installation types, each performing a different type of installation from the same OS image on the RIS server. RIS installs a default unattended setup installation (.sif) file with the default OS image that was added during RIS installation.
Note: You cannot use the Add option on the Images tab to add an RIPrep image, nor can you use the Add option to associate additional unattended setup answer files to a RIPrep image.
Use the Remove option to remove the unattended setup answer file (*.sif) that is associated with the OS image. Note that this option removes only the .sif file. You should not remove the physical OS image completely until all client computers have upgraded beyond that version. To remove the OS image from the remote installation server, use Windows Explorer to delete the directory and subdirectories containing the image.
Use the Propertiesoption to change the friendly description and help text that describes the operating system image. If you want to change the description of an OS image, click the Image you want to modify and click Properties. The dialog box appears as in Figure 6 below:
Figure 6: Image Properties
If you replace the existing friendly description and help text with new text, all users of the client installation from that point forward see the new text descriptions. You can also use the Properties option to view specific image attributes, such as OS version, language, and the type of image (CD or RIPrep).
Click Cancel to make no changes.
Click the Tools tab if you wish to view its options.
The Tools tab is available for independent software vendors (ISVs) or original equipment manufacturers (OEMs) that would like to use their pre-boot tools with RIS. ISVs or OEMs need to provide an external setup program that adds their respective tool to the \RemoteInstall directory tree. Once added, the tool shows up on the Tools tab and is available to administrators and users of the Client Installation wizard.
The Tools option also allows ISVs or OEMs to provide pre-OS installation maintenance and troubleshooting tools to administrators, IT staff, or users. This provides administrators with an easy way to update client computer systems, such as the system BIOS.
After making the desired changes, close Active Directory snap-in.
Top of page
Client Installation Options
There are four installation options that you can choose to present to a user of the Client Installation wizard. These options are:
Automatic setup
Custom setup
Restart a previous setup attempt
Maintenance and troubleshooting
The installation options available to any given user are determined by the specific Remote Installation Services Group Policy settings. For example, you can choose to provide all members of the Help Desk Security group access to all of the installation options, yet restrict general network users to the Automaticsetupand Maintenance and troubleshootingoptions. This prevents user confusion and helps guide the user to the correct choices for OS installation. By default, users are given the right to automatic setup only.
Automatic Setup
The Automatic setup option is the default installation option enabled for all users of the Client Installation wizard. If this is the only installation option available to a user, when the user logs on within the Client Installation wizard, the automatic setup option is not displayed. Instead, the Client Installation wizard jumps directly to the OS images selection screen. If there is only one OS image offered, the user simply logs on within the Client Installation wizard and is asked to confirm the installation. If more than one OS image is available for installation, the user has a choice of which OS to install. Note that you can configure the RIS server to limit the OS images the user can see. For more information on restricting OS image access, see the section "Restricting OS Image Options" below.
By using an unattended installation setup answer file (*.sif), you can create several unattended OS installations that are associated with one CD-based OS image on the remote installation server. You can customize which items are installed, as well as how the specific OS options are configured during OS install.
For example, you can choose to create a specific OS unattended setup answer file (*.sif) that installs the TCP/IP protocol, sets the display resolution to 800 x 600, and sets a specific company or department name. You can provide a friendly description for this OS image that the user can relate to, such as Windows 2000 Professional for Sales Staff. The friendly description is configurable after the initial posting of the workstation OS image on the RIS server (see the preceding section on configuring options on the RIS server). When a user logs on, a list of OS installation images is displayed for the user to choose from.
When the user selects one of the operating system images, a message displays stating that an operating system is about to be installed on this computer, and that the operating system requires the local hard disk to be repartitioned and formatted, thus erasing all data that currently resides on the disk.
Note: An administrator can edit the "Caution.osc" screen using the Notepad.exe program to provide a friendly message regarding the repartition and format of the local hard disk.
Custom Setup
The Custom setup option allows you to override the automatic computer name assignment, as well as the computer account creation mechanism. You are prompted to manually enter a computer name or the Active Directory location where the computer account should be created.
Note: The Custom setup option can also be used to pre-stage a client computer into the Active Directory before delivery of the PC to the end user. Windows 2000 Remote Installation Services do not support fully unattended installations on machines that contain ISA or non Plug and Play aware devices.
Restart a Previous Setup Attempt
This option provides the ability to restart a failed setup attempt. If you started to install the OS and for some reason lost your connection to the RIS server, you can reboot the client computer, press F12 when prompted for a network service boot, and choose the Restart a Previous Setup Attempt. This restarts the installation of the previous installation attempt without asking for the computer name or Active Directory location previously entered before the initial failure.
Maintenance and Troubleshooting
This option provides access to third-party ISV and or OEM Pre-OS maintenance and troubleshooting tools.
Restricting Client Installation Options
To restrict the client installation options for users of RIS within your organization, apply the appropriate Group Policy settings for the RIS servers on your network.
Click Start, point to Programs, point to Administrative tools, and click Active Directory Users and Computers.
Locate the Active Directory container where you would like the RIS policy settings to be set. By default, the RIS policy settings are applied within the Default Domain Policy Object, which is located at the root of your domain.
Right-click Reskit.com in the left pane, and click the Properties option.
Click the Group Policy tab from the top of the Properties dialog box.
Click the Default Domain Policy object and click Edit.
Expand the User Configuration option by clicking the + next to it (unless it is already expanded), and then expand the Windows Settings option in the same way. Click the Remote Installation Services option as in Figure 7 below.
Figure 7: Group Policy RIS Choice Options
Double-click the Choice Options in the right pane.
Each Choice Option allows for a specific setting, as follows:
Allow. If this option is selected, the users that this policy is applied to are offered the installation option.
Don't Care. If this option is selected, the administrator accepts the policy settings of the parent container. For example, if the administrator for the entire domain has set RIS specific policy, and the administrator of this container has chosen the Don't Care option, the policy that is set on the domain is applied to all users who are affected by that policy.
Deny. If this option is set, the users affected by this policy are not allowed to access that installation option within the Client Installation wizard.
Close the Choice Options and other windows, and close the Active Directory Users and Computers Snap-In.
Restricting OS Image Options
RIS provides the administrator flexibility in the amount of control users have in choosing the OS that is installed on their computer. The administrator can configure the RIS servers to guide users through a successful OS installation without requiring the user to select the correct OS image.
By setting explicit user or group security permissions on the unattended setup answer file (*.sif) for a given OS image, you can determine which OS options a user can see and install. You can choose to allow all users of RIS to choose from all of the OS images available on a given RIS server, or you can restrict the user to only a select few that are appropriate for that user or group of users.
Click Start, point to Programs, point to Accessories, and click Windows Explorer.
Click the + next to My Computer
Click the + next to New Volume
Click the + next to RemoteInstall
Click the + next to Setup
Click the + next to English (or whatever language you are using)
Click the + next to Images
Click the + next to win2000.pro
Click the + next to i386
Click Template. A sample directory structure is shown in Figure 8 below.
Figure 8: Templates
Note: Each CD-based OS image that you add to a RIS server has an associated \Templates directory that contains the image's associated unattended setup answer files (*.sif).
Depending on the level of restriction that you want to establish, you can set specific access permissions on the \Templates directory or in the individual unattended setup answer files within this directory. If you have not associated additional unattended answer files to the base OS image, you will only see one SIF file (Ristndrd.sif) within the \Templates directory.
Right-click the \Templates directory, and click the Properties option. The property page for the \Templates folder appears.
Select the Security tab. A dialog box appears as in Figure 9 below:
Figure 9: Template Properties
In this example, the existing security permissions allow all users access to this OS image from within the Client Installation wizard.
To restrict access to this OS image, select the Everyone group, and click Remove. This removes user access to this OS image. If a normal user were to run the Client Installation wizard at this point, the user would not have access to any available OS image to install.
Click Add, and select the security group or individual users that should be allowed access to this OS image. Click Add to add them to the authorized list, and then click OK twice. The default permissions that are set for each user or security group are sufficient for use with RIS.
Note: Selecting individual users for specific access can become an administrative burden. Instead group your users by security group and apply the security group to the \Templates directory for OS image access. In this way, if you add users to the security group, they already have access to the correct OS image.
Important Note Never remove the permissions assigned to the Administrators group for a .SIF file. Doing so will prevent the RIS components themselves from accessing the file and prevent proper client installations.
At this point, you are ready to service client computers with RIS. Ensure that all services are running, all configuration settings have been made, and that the client computers adhere to the minimum requirements as described above.
Top of page
Remote Installation Preparation Wizard (RIPrep)
The Remote Installation Preparation wizard (RIPrep.exe) provides the ability to prepare an existing Windows 2000 Professional installation, including locally installed applications and specific configuration setting, and replicate that image to an available RIS server on the network. The RIPrep feature currently supports replication of a single disk single partition (C Drive only) with Windows 2000 Professional installation. This means that the OS and all of the applications that make up the standard installation must reside on the C: drive before running the wizard.
First use RIS to remotely install the base Windows 2000 Professional OS on a client computer. Next, install any desired applications on the client computer. Configure the installation to adhere to any company policies; for example, you might choose to define specific screen colors, set the background bitmap to a company-based logo, or set intranet proxy server settings within Internet Explorer. Once the workstation is configured and tested, run the Remote Installation Preparation wizard (RIPrep.exe) from the RIS server that will receive the RIPrep-based OS image.
The destination computer does not need to have the same hardware as the source computer used to create the image, with the exception that the Hardware Abstraction Layer (HAL) drivers must be the same. For example, both computers must be ACPI (Advanced Configuration and Power Interface)-based or both must be non ACPI-based). In many cases, workstation-class computers do not require unique HAL drivers. The RIPrep utility uses the new Plug and Play support that ships with Windows 2000 for detecting any differences between the source and the destination computer hardware during image installation time.
To run the Remote Installation Preparation wizard (RIPrep.exe)
Install the base Windows 2000 Professional OS from an available RIS server on a supported client computer.
Install any applications locally on the client computer. Configure the client computer with any specific corporate standard desktop settings. Be sure the client installation is exactly as you want it to be. Once the image is replicated to the RIS server, you cannot alter its configuration.
Connect to the RIS server where you want to replicate this image, as follows:
Click Start , click Run, and type the following command in the Open text box:\\RISservername\Reminst\Admin\I386\RIPrep.exe
where RISservername is the computer name of the destination RIS server. In our example, this is HQ-RES-DC-01. Reminst is the Remote Installation Share that is created when you installed the RIS service on the server. Admin is the directory that contains the RIPrep.exe that launches the remote installation.
At this point, the Remote Installation Preparation wizard starts and you are presented with a welcome screen that describes the feature and its functionality. Click Next.
You are prompted to enter the name of the RIS server where you would like to replicate the contents of the client hard disk. By default, the RIS server that the wizard (RIPrep.exe) is being run from is automatically filled in (in our example, Reskit.com). Click Next.
You are prompted to provide the name of the directory on the RIS server where this image will be copied. The image is created under the \remoteInstall\setup\OS Language\Images directory. Click Next.
You are prompted to provide a friendly description and help text describing this image. The friendly description and help text are displayed to users of the Client Installation wizard during OS image selection. Provide enough information that a user can distinguish between images. Click Next.
The wizard displays a summary screen of your selections. After you have reviewed them, click Next.
The image preparation and replication process begins. The system is prepared and files are copied to the RIS server specified. Once the replication of the image completes, any remote boot enabled client computer can select the image for a local installation.
Top of page
Remote Installation Boot Disk Option
The remote installation boot disk can be used with computers that do not contain a remote boot-enabled ROM on the network card. The boot disk is designed to simulate the PXE boot process for computers that lack a supported DHCP PXE-based remote boot ROM. The boot disk generator utility is called RBFG.EXE and is located within the \RemoteInstall\admin directory on every Remote Installation Server.
The RBFG.exe utility is also contained within the Administrator Tools package that ships with Windows 2000 Server. The Administrator Tools package can be deployed across your organization using either Systems Management Server 2.0 or using the new Software Management feature, which is part of the Group Policy infrastructure.
Creating a Remote Installation Boot Floppy
To create a Remote Installation Boot Floppy, run the RBFG.exe utility from the RIS server either on a client computer that is connected to the RIS server or a computer with the administrator tools package installed.
Click Start, click Run, and in the Open text box, type RBFG.exe, and click OK.
Note: The RBFG.exe utility does not allow you to add network adapters). To create a remote installation boot disk, insert a disk into the appropriate drive and then select Create Disk.
Top of page
Remote Boot ROM PXE Architecture
Remote Installation Services uses DHCP for IP address assignment to clients. When a new DHCP- PXE-based remote boot client computer is powered on for the first time, the client requests an Internet Protocol (IP) address, and the IP address of an active boot server via the DHCP protocol. As part of the initial request, the client computer sends out its globally unique identifier (GUID or UUID), which is used to uniquely identify the client machine within the Active Directory, in the case of Windows 2000 Remote Installation Services.
From the RIS server, the client computer receives:
Its own IP address from DHCP.
The IP address of the RIS server.
The name of a boot image the client computer will need to request when contacting the RIS server for initial service.
Once the client request is made, the first RIS server to respond will check Active Directory to see if this client has been pre-staged or not. RIS does this by checking in Active Directory for a computer account object that has the unique GUID/UUID.
The PXE process is used every time a remote boot ROM-enabled client requests a network service boot. Remote boot/installation server vendors implement their own process to download the first image.
Top of page
Conclusion
The information presented in this guide has provided the technical details required to install, configure, and use Microsoft Remote Installation Services.
Remote Installation Services require several of the Windows 2000 Server technologies—Active Directory, DHCP server, and the DNS server services. The remote installation server also requires that client computers contain either the new DHCP PXE-based remote boot capable ROMs or a network card supported by the remote installation boot floppy.
Top of page
Appendix A: Remote Installation Server and Workstation Hardware Requirements
Server Hardware Requirements
See the Product Compatibility page to verify that your server meets the minimum requirements for Windows 2000 Server.
Pentium or Pentium II 200 megahertz (MHz) recommended (166 MHz minimum)
64 MB RAM minimum. If additional services such as the DS, DHCP, and DNS are installed then the minimum amount of RAM is 96 or 128 MB
2-GB drive dedicated to the Remote Installation Servers directory tree
10 or 100 megabits per second (Mbps) network adapter card. (100 Mbps preferred.)
Note: You should dedicate an entire hard drive or partition specifically to the Remote Installation Services directory tree. (SCSI-based disk controller/disks are preferred.)
Client Hardware Requirements
See the Product Compatibility page to make sure that your workstation meets the minimum requirements for Windows 2000 Professional.
Pentium 166 MHz or greater NetPC client computer
32 MB of RAM
1.2-GB drive minimum
PXE DHCP-based boot ROM version .99c or greater or a network adapter supported by the RIS boot floppy.
Best Practice: Always check with the manufacturer of your network adapter to get the latest version of the PXE ROM.
Network Cards supported by RIS Boot Floppy
3 Com Network Adapters
3c900 (Combo and TP0)
3c900B (Combo, FL, TPC, TP0)
3c905 (T4 and TX)
3c905B (Combo, TX, FX)
AMD Network Adapters
AMD PCNet and Fast PC Net
Compaq Network Adapters
Netflex 100 (NetIntelligent II)
Netflex 110 (NetIntelligent III)
Digital Equipment Corporation (DEC) Network Adapters
DE 450
DE 500
Hewlett-Packard Network Adapters
HP Deskdirect 10/100 TX
Intel Corporation Network Adapters
Intel Pro 10+
Intel Pro 100+
Intel Pro 100B (including the E100 series)
SMC Network Adapters
SMC 8432
SMC 9332
SMC 9432
One of the most challenging and costly functions performed by IT staff today is deploying a new operating system to client computers on a network. The Windows® 2000 operating system Remote OS Installation feature was created to meet this need to deploy an operating system throughout an enterprise network without having to physically attend to each client computer. The Remote Installation Services (RIS) takes advantage of the new Dynamic Host Configuration Protocol (DHCP)-based remote boot technology to assist IT staff with deploying Windows 2000 Professional remotely—reducing and, in some cases, eliminating the need to visit the desktop. This document outlines the steps necessary to install, configure, and use RIS.
On This Page
Introduction Installing the Windows 2000 Remote Installation Services Authoring RIS within the Active Directory Setting Required User Permissions Installing Client Computers Using Remote Installation Configuring Remote Installation Services Client Installation Options Remote Installation Preparation Wizard (RIPrep) Remote Installation Boot Disk Option Remote Boot ROM PXE Architecture Conclusion Appendix A: Remote Installation Server and Workstation Hardware Requirements Appendix B: Frequently Asked Questions Related Links
Introduction
Remote Installation Services (RIS) ships as part of the Windows® 2000 Server operating system. This document outlines the steps necessary to install, configure, and use RIS.
RIS was designed to reduce the costs incurred by pre-installing or physically visiting each client computer to install the operating system (OS). By combining RIS with other Windows 2000 IntelliMirror™ management technologies features—User Data Management, Software Installation and Maintenance, and User Settings Management—companies benefit from better disaster recovery with easier OS and application management.
Prerequisites
See Appendix A below to ensure that both your server and client hardware meet the remote installation hardware requirements.
The drive on the server where you choose to install RIS must be formatted with the NTFS file system. RIS requires a significant amount of disk space and cannot be installed on the same drive or partition on which Windows 2000 Server is installed. Ensure that the chosen drive contains enough free disk space for at least one full Windows 2000 Professional compact disc—a minimum of approximately 800 megabytes (MB)–1 gigabyte (GB).
RIS requires several other services that also ship as part of Windows 2000 Server. These services can be installed on individual servers, or all on a single server, depending on your network design:
Domain Name Service (DNS) Server. Remote installation relies on DNS for locating the directory service and client machine accounts. You can use any Windows 2000 Active DirectoryTM service-compliant DNS server, or you can use the DNS server provided with Windows 2000 Server.
Dynamic Host Configuration Protocol (DHCP) Server. RIS requires a DHCP server to be present and active on the network. The remote boot-enabled client computers receive an IP address from the DHCP server before contacting RIS.
Active Directory. RIS relies on Windows 2000 Active Directory for locating existing client machines as well as existing RIS servers. RIS must be installed on a Windows 2000-based server that has access to Active Directory. This can be a domain controller or a server that is a member of a domain with access to the Active Directory.
To ensure a successful installation, you must install and configure the additional services described above in order for RIS to function. In addition, make sure that you have both the Windows 2000 Server and Professional CDs available.
Before beginning this step-by-step guide, you need to build the common infrastructure, which specifies a particular hardware and software configuration. The common infrastructure is covered in the Common Infrastructure step-by-step guide, "Part 1: Installing a Windows 2000 Server as a Domain Controller" http://www.microsoft.com/windows2000/techinfo/planning/server/serversteps.asp. If you are not using the common infrastructure, you need to make the appropriate changes to this instruction set.
Although not required, we also recommend reading and performing the exercises available in the Step-by-Step Guide to Understanding the Group Policy Feature Set. It addresses how Group Policy works and can be applied in the context of remote installations.
Prerequisites for Client Installations
Ensure that the client computer's network card has been set as the primary boot device within the system BIOS. When the client computer boots and is configured with the network card as the primary boot device, it requests a network service boot from the remote installation server on the network. Once contacted, the RIS server prompts users to press the F12 key to download the Client Installation wizard. Users should be instructed to press F12 only if prompted, and only if they need a new OS installation or access to maintenance and troubleshooting tools. Once the OS has been installed via RIS, the user can ignore the request to press F12 during future client computer reboots. If using the RIS boot floppy disk, simply insert the boot floppy into the drive and start the client computer. The computer boots from the floppy disk, and the user is requested to press F12 to initiate the network service boot. When the RIS boot floppy disk is used, the user must remove the boot floppy at some point after pressing F12 and before the text mode portion of setup completes.
Note: Compaq computer systems provide the ability to press the F12 key during power up on PC98 or Net PC-based systems. In this case, the user is required to press F12 on the Compaq Splash screen, and then press F12 again when prompted by the RIS server.
Top of page
Installing the Windows 2000 Remote Installation Services
The following instructions help you install, configure, and use the Windows 2000 Remote Installation Services.
Install Remote Installation Services
On a Windows 2000 Server, click Start, point to Settings, and click Control Panel.
Double-click Add/Remote Programs.
Double-click Add/Remove Windows Components.
Scroll down and select Remote Installation Services and Click Next.
Insert the Windows 2000 Server CD-ROM into the CD drive and click OK . The necessary files are copied to the server.
Note: After the CD is entered, a dialog box asks if you want to upgrade to the operating system. Click No and exit this screen.
Click Finish to end the wizard.
You are prompted to restart your computer. Click Yes.
When the server is done rebooting, logon as a local administrator.
To set up Remote Installation Services
Click Start, click Run, and type RISetup.exe. This starts the Remote Installation Services (RIS) Setup wizard.
The Welcome screen appears, indicating some of the requirements to successfully install RIS. Click Next.
The next screen prompts you to enter the server drive and directory where you would like to install the RIS files. The default drive and directory will be the largest non-system, non-boot, NTFS-formatted drive. In our example, this would be E:\RemoteInstall. Click Next.
Note: The drive on which you choose to install RIS must be formatted with the NTFS file system. RIS requires a significant amount of disk space and cannot be installed on the same drive or partition on which Windows 2000 Server is installed. Ensure that the chosen drive contains enough free disk space for at least one full Windows 2000 Professional compact disc —a minimum of approximately 800 MB–1GB.
The setup wizard prompts you to either enable RIS at the end of setup, or disable the service to allow modification of specific server options before servicing client computers. These options are:
Respond to clients requesting service. This option controls whether this RIS server responds to client computers requesting service at the end of setup. If this option is checked, the server will respond to clients and provide them with OS installation options. If unchecked, this RIS server will not respond to clients requesting service.
Do not respond to unknown client computers. This option controls whether this server responds to unknown client computers requesting a remote installation server. A client computer is known if a managed computer account object exists for it within Active Directory. This allows the administrator to offer only authorized—that is, pre-staged within the Active Directory—computers the OS installation options from this RIS server. This setting also provides support for multiple Remote Boot or Install servers from different vendors on one physical network. For example, if another vendor's remote install/boot server exists on the same network as the RIS server, you cannot control which server answers the client computer's request. Setting this option and pre-staging client computers ensures that this RIS server will service only pre-staged client computers.
For the purpose of this guide, select Respond to client computers requesting service and click Next.
The setup wizard prompts you for the location of the Windows 2000 Professional installation files. RIS supports the remote installation of Windows 2000 Professional only. Insert the Windows 2000 Professional CD into the server's CD drive and type the drive letter containing the CD (or browse to a network share that contains the installation source files). Click Next.
The wizard prompts you to enter the directory name that will contain the workstation files on the RIS server. This directory is created beneath the directory specified in Step 3 above. The directory name should reflect its contents—for example, Win2000.pro. Click Next to accept the default name of win2000.pro.
You are prompted for a friendly description and help text that describes this OS image. The friendly description and help text is displayed to users or IT staff during the client installation wizard (OSChooser) at initial startup on a remote client. For example, if this workstation OS will be tailored to sales staff, then a friendly description might be "Windows 2000 Professional for Sales Staff." The help text is displayed when the user selects the description within the Client Installation wizard. Make sure you provide clear help text to your users, to ensure that they choose the correct OS option at installation time. For this exercise, click Next to accept the default name of Microsoft Windows 2000 Professional.
At this point, you are presented with a summary screen indicating the choices you have made. Click Finish to confirm your choices. Once the installation wizard completes, you are ready to either service client computers, or additionally configure the RIS settings.
Wait while the wizard installs the service and settings you have selected. This takes several minutes. When it is finished, a screen appears as in Figure 1 below:
Figure 1: Completed RIS installation.
Click Done.
Now that RIS is successfully installed, you must authorize the RIS server within Active Directory. If you do not authorize the RIS server, it will fail to service client computers requesting a network service boot. The next section outlines these steps.
Top of page
Authoring RIS within the Active Directory
RIS allows you to control which RIS servers can service client computers on the network. For a RIS server to operate, it must first be authorized within Active Directory. If the RIS server is not authorized within Active Directory, client computers requesting service will not be able to contact the RIS server and will not be answered.
To authorize a RIS server within Active Directory, you must be logged on as an enterprise administrator or a domain administrator of the root domain. You can complete the following steps on any domain controller, member server of the domain, or a Windows 2000 Professional workstation that has installed the Administrator Tools Package containing the DHCP Server Management snap-in. This guide performs the authorization on a domain controller: specifically, the domain controller that would have been created by running Part I of the Common Infrastructure step-by-step guide.
Click Start, point to Programs, point to Administrative Tools and click DHCP. The following snap-in appears as in Figure 2 below:
Figure 2: DHCP Snap-In
Right-click DHCP in the upper-left corner of the DHCP screen, and select > Manage Authorized Servers. If your server is not already listed, click Authorize, and enter the IP address of the RIS server. Click > Yes when prompted to verify that the address is correct.
At this point, your RIS server is authorized within Active Directory and is now able to respond to client computers requesting service.
Note: If you authorize the RIS server on a non-domain controller computer, follow these steps to install the Administrator Tools Package: Click Start, click Run, and type adminpak.msi on a Server system. From a Professional based system, execute adminpak.msi from the Windows 2000 Server CD.
Top of page
Setting Required User Permissions
If users are allowed to use RIS to install their own client computers, the administrator must ensure that those users have been granted the correct permissions for creating machine accounts within the domain. The permissions granted using the steps below will allow users to create computer accounts anywhere in the domain.
Click Start, point to Programs, point to Administrative Tools, and click Active Directory Users and Computers.
Right-click the Domain Name (Reskit.com) at the top of the snap-in, and click the Delegate Control option.
A wizard starts. Click Next.
Click Add to add users who are allowed to install their own computers using Remote OS Installation.
For the purpose of this guide, highlight Everyone and click Add. Click OK.
Click Next to continue.
Check the Join a Computer to the Domain option, and click Next.
Click Finish. Users can now create computer account objects during the OS installation using the RIS service.
You can now either use the default RIS settings and immediately begin servicing client computers, or you can make changes to the RIS settings first. In either case, review the section titled "Prerequisites for Client Installations" above before servicing the first client computer.
Top of page
Installing Client Computers Using Remote Installation
This section describes the steps required to successfully install Windows 2000 Professional on a Net PC, a Managed PC (PC 98 compliant system), or a PC that contains a network card supported by the remote installation boot floppy. To ensure a successful client installation, complete all prerequisites listed at the beginning of this document.
Reboot your client machine from either the remote floppy or the PXE boot ROM. When prompted, press the F12 key to start the download of the client installation wizard.
Press Enter at the welcome screen.
For the user name, type Jon Grande (this user is created using the Common Infrastructure step-by-step guide discussed in the Prerequisites Section above.) Press the Tab key twice. For this instruction set, the password is left blank and the domain name should be entered as reskit.com. Press Enter to continue.
You will get a warning message that all data on the client machine hard drive will be deleted. To continue, press Enter.
A computer account and a global unique ID for this workstation are displayed. Press Enter to begin Setup. The Windows 2000 Setup program begins.
If prompted, type the Product Key (found on the back of the Windows 2000 Professional CD case) and click > Next. (Note: This step can be avoided by specifying the product key in the .sif file; see Windows 2000 Online Help for assistance in making this change to the .sif file.)
After the installation is complete, the user is prompted to log on to the network with an existing user account, password, and logon domain.
At this point, you have successfully configured and installed a remote operating system using RIS. See below for additional information on configuration options.
Top of page
Configuring Remote Installation Services
This section outlines the specific RIS configuration options that can be configured. If desired, these optional steps should be performed using the Active Directory Users and Computer snap-in on the RIS server.
Note: Although not covered in this guide, you can administer the majority of the RIS configuration settings from a Windows 2000 Professional client. To administer a RIS server from a Windows 2000 Professional client, install the Administrator Tools package AdminPak.msi that ships as part of the Windows 2000 Server CD. The Administrator Tools package can be deployed or installed from the
Click Start, point to Programs, point to Administrative Tools, and click Active Directory Users and Computers.
You are presented with your Active Directory tree as in Figure 3 below:
Figure 3: Active Directory Users and Computers Snap-In
There are two areas of administration concerning the configuration of the RIS server settings:
Remote installation server properties, which allow you to determine how this RIS server responds to client computers that request service.
Advanced settings, which provide additional flexibility regarding the ways in which client computers are installed.
Locate your RIS server computer object within the Active Directory Users and Computers snap-in. Depending on the type of server, domain controller, or member server of a domain, the server's computer object can be located in the Domain Controller Active Directory container or another container specified by the administrator at install time.
Click Domain Controllers in the left pane.
Right-click HQ-RES-DC-01 in the right pane.
Click Properties.
Click the Remote Install tab. The property page appears as in Figure 4 below :
Figure 4: RemoteInstall Options
The server options control how this RIS server responds to remote client computers requesting service.
Click Advanced Settings on the RIS server property page.
Click the down arrow next to the Generate client computer names using drop-down box as in Figure 5 below.
Figure 5: Client under Advanced
The administrator can define the automatic computer naming policy that is used during OS installation to provide the computer with a unique name. The computer name is used to identify the client computer on the network, similar to the older NetBIOS name used in previous versions of the Windows NT® and Windows operating systems.
This tab also allows you to define a default Active Directory container for client computer account object creation. You can group clients within a specific directory service domain or organizational unit (OU). During OS installation, Windows 2000 setup queries these settings to ensure the client computer is configured according to what the administrator has specified. These are the options:
Default directory service location. This option specifies that the computer account object for the client computer will be created in the default Active Directory computer accounts location. The default Active Directory location is set to the Computers container within the Active Directory. The client computer becomes a member of the same domain as the RIS server installing the client.
Same location as the user setting up the computer.This options pecifies that the client computer account object will be created within the same Active Directory container as the user setting up the machine. For example, if Jon logs on within the Client Installation wizard and his user account currently resides within the "Users" Active Directory container, the client computer account is created within the "Users" container in the Active Directory.
A specific directory service location. This option allows the administrator to set a specific Active Directory container where all client computer account objects installed from this server are created. It is assumed that most administrators will select this option and specify a specific container for all remote installation client computer account objects to be created in.
Note: If an end user is setting up the client computer, the user must have the appropriate rights to create the computer account within the domain or OU chosen. For more information on giving users computer account creation permissions, please see the RIS online Help.
Note: In order for all client computers using the RIS feature for OS installation to contain the same settings, all remote installation servers need to be configured in the exact same way. This release does not support replication of OS images or RIS configuration settings between RIS servers.
Specify the desired user name parameters and directory service location and click Apply.
Click the Images tab.
The Images tab is used for managing the client operating system images installed on a RIS server. Its options allow an administrator to add, remove, or modify the properties of an operating system image.
There are two types of images that can be displayed on the Images tab:
CD-based.A CD-based image is simply a copy of the Windows 2000 Professional CD. This installs only the base operating system without applications or configuration settings.
Remote Installation Preparation (RIPrep). RIPrep images are a combination of the OS, locally installed applications, and configuration settings. Many companies standardize on a single type of OS installation across their organization. Administrators can now use RIS to install the base OS, then add corporate standard applications and configure the installation exactly as they want. Once the workstation is configured appropriately, the administrator runs the Remote Installation Preparation Wizard (RIPrep) utility to create that image on an available RIS server. Once the image is replicated on the RIS server, new client computers requesting an OS installation can download the image. For more information on the RIPrep wizard and feature set, please see the section, "Using the Remote Installation Preparation Wizard" below.
Use the Addoption to add a new CD-based OS image or to associate an unattended setup answer file (*.sif) to an existing CD-based image on the RIS server. You can associate a number of unattended setup answer files to a single OS-based CD Image. This allows the administrator to offer users a variety of unattended Windows 2000 installation types, each performing a different type of installation from the same OS image on the RIS server. RIS installs a default unattended setup installation (.sif) file with the default OS image that was added during RIS installation.
Note: You cannot use the Add option on the Images tab to add an RIPrep image, nor can you use the Add option to associate additional unattended setup answer files to a RIPrep image.
Use the Remove option to remove the unattended setup answer file (*.sif) that is associated with the OS image. Note that this option removes only the .sif file. You should not remove the physical OS image completely until all client computers have upgraded beyond that version. To remove the OS image from the remote installation server, use Windows Explorer to delete the directory and subdirectories containing the image.
Use the Propertiesoption to change the friendly description and help text that describes the operating system image. If you want to change the description of an OS image, click the Image you want to modify and click Properties. The dialog box appears as in Figure 6 below:
Figure 6: Image Properties
If you replace the existing friendly description and help text with new text, all users of the client installation from that point forward see the new text descriptions. You can also use the Properties option to view specific image attributes, such as OS version, language, and the type of image (CD or RIPrep).
Click Cancel to make no changes.
Click the Tools tab if you wish to view its options.
The Tools tab is available for independent software vendors (ISVs) or original equipment manufacturers (OEMs) that would like to use their pre-boot tools with RIS. ISVs or OEMs need to provide an external setup program that adds their respective tool to the \RemoteInstall directory tree. Once added, the tool shows up on the Tools tab and is available to administrators and users of the Client Installation wizard.
The Tools option also allows ISVs or OEMs to provide pre-OS installation maintenance and troubleshooting tools to administrators, IT staff, or users. This provides administrators with an easy way to update client computer systems, such as the system BIOS.
After making the desired changes, close Active Directory snap-in.
Top of page
Client Installation Options
There are four installation options that you can choose to present to a user of the Client Installation wizard. These options are:
Automatic setup
Custom setup
Restart a previous setup attempt
Maintenance and troubleshooting
The installation options available to any given user are determined by the specific Remote Installation Services Group Policy settings. For example, you can choose to provide all members of the Help Desk Security group access to all of the installation options, yet restrict general network users to the Automaticsetupand Maintenance and troubleshootingoptions. This prevents user confusion and helps guide the user to the correct choices for OS installation. By default, users are given the right to automatic setup only.
Automatic Setup
The Automatic setup option is the default installation option enabled for all users of the Client Installation wizard. If this is the only installation option available to a user, when the user logs on within the Client Installation wizard, the automatic setup option is not displayed. Instead, the Client Installation wizard jumps directly to the OS images selection screen. If there is only one OS image offered, the user simply logs on within the Client Installation wizard and is asked to confirm the installation. If more than one OS image is available for installation, the user has a choice of which OS to install. Note that you can configure the RIS server to limit the OS images the user can see. For more information on restricting OS image access, see the section "Restricting OS Image Options" below.
By using an unattended installation setup answer file (*.sif), you can create several unattended OS installations that are associated with one CD-based OS image on the remote installation server. You can customize which items are installed, as well as how the specific OS options are configured during OS install.
For example, you can choose to create a specific OS unattended setup answer file (*.sif) that installs the TCP/IP protocol, sets the display resolution to 800 x 600, and sets a specific company or department name. You can provide a friendly description for this OS image that the user can relate to, such as Windows 2000 Professional for Sales Staff. The friendly description is configurable after the initial posting of the workstation OS image on the RIS server (see the preceding section on configuring options on the RIS server). When a user logs on, a list of OS installation images is displayed for the user to choose from.
When the user selects one of the operating system images, a message displays stating that an operating system is about to be installed on this computer, and that the operating system requires the local hard disk to be repartitioned and formatted, thus erasing all data that currently resides on the disk.
Note: An administrator can edit the "Caution.osc" screen using the Notepad.exe program to provide a friendly message regarding the repartition and format of the local hard disk.
Custom Setup
The Custom setup option allows you to override the automatic computer name assignment, as well as the computer account creation mechanism. You are prompted to manually enter a computer name or the Active Directory location where the computer account should be created.
Note: The Custom setup option can also be used to pre-stage a client computer into the Active Directory before delivery of the PC to the end user. Windows 2000 Remote Installation Services do not support fully unattended installations on machines that contain ISA or non Plug and Play aware devices.
Restart a Previous Setup Attempt
This option provides the ability to restart a failed setup attempt. If you started to install the OS and for some reason lost your connection to the RIS server, you can reboot the client computer, press F12 when prompted for a network service boot, and choose the Restart a Previous Setup Attempt. This restarts the installation of the previous installation attempt without asking for the computer name or Active Directory location previously entered before the initial failure.
Maintenance and Troubleshooting
This option provides access to third-party ISV and or OEM Pre-OS maintenance and troubleshooting tools.
Restricting Client Installation Options
To restrict the client installation options for users of RIS within your organization, apply the appropriate Group Policy settings for the RIS servers on your network.
Click Start, point to Programs, point to Administrative tools, and click Active Directory Users and Computers.
Locate the Active Directory container where you would like the RIS policy settings to be set. By default, the RIS policy settings are applied within the Default Domain Policy Object, which is located at the root of your domain.
Right-click Reskit.com in the left pane, and click the Properties option.
Click the Group Policy tab from the top of the Properties dialog box.
Click the Default Domain Policy object and click Edit.
Expand the User Configuration option by clicking the + next to it (unless it is already expanded), and then expand the Windows Settings option in the same way. Click the Remote Installation Services option as in Figure 7 below.
Figure 7: Group Policy RIS Choice Options
Double-click the Choice Options in the right pane.
Each Choice Option allows for a specific setting, as follows:
Allow. If this option is selected, the users that this policy is applied to are offered the installation option.
Don't Care. If this option is selected, the administrator accepts the policy settings of the parent container. For example, if the administrator for the entire domain has set RIS specific policy, and the administrator of this container has chosen the Don't Care option, the policy that is set on the domain is applied to all users who are affected by that policy.
Deny. If this option is set, the users affected by this policy are not allowed to access that installation option within the Client Installation wizard.
Close the Choice Options and other windows, and close the Active Directory Users and Computers Snap-In.
Restricting OS Image Options
RIS provides the administrator flexibility in the amount of control users have in choosing the OS that is installed on their computer. The administrator can configure the RIS servers to guide users through a successful OS installation without requiring the user to select the correct OS image.
By setting explicit user or group security permissions on the unattended setup answer file (*.sif) for a given OS image, you can determine which OS options a user can see and install. You can choose to allow all users of RIS to choose from all of the OS images available on a given RIS server, or you can restrict the user to only a select few that are appropriate for that user or group of users.
Click Start, point to Programs, point to Accessories, and click Windows Explorer.
Click the + next to My Computer
Click the + next to New Volume
Click the + next to RemoteInstall
Click the + next to Setup
Click the + next to English (or whatever language you are using)
Click the + next to Images
Click the + next to win2000.pro
Click the + next to i386
Click Template. A sample directory structure is shown in Figure 8 below.
Figure 8: Templates
Note: Each CD-based OS image that you add to a RIS server has an associated \Templates directory that contains the image's associated unattended setup answer files (*.sif).
Depending on the level of restriction that you want to establish, you can set specific access permissions on the \Templates directory or in the individual unattended setup answer files within this directory. If you have not associated additional unattended answer files to the base OS image, you will only see one SIF file (Ristndrd.sif) within the \Templates directory.
Right-click the \Templates directory, and click the Properties option. The property page for the \Templates folder appears.
Select the Security tab. A dialog box appears as in Figure 9 below:
Figure 9: Template Properties
In this example, the existing security permissions allow all users access to this OS image from within the Client Installation wizard.
To restrict access to this OS image, select the Everyone group, and click Remove. This removes user access to this OS image. If a normal user were to run the Client Installation wizard at this point, the user would not have access to any available OS image to install.
Click Add, and select the security group or individual users that should be allowed access to this OS image. Click Add to add them to the authorized list, and then click OK twice. The default permissions that are set for each user or security group are sufficient for use with RIS.
Note: Selecting individual users for specific access can become an administrative burden. Instead group your users by security group and apply the security group to the \Templates directory for OS image access. In this way, if you add users to the security group, they already have access to the correct OS image.
Important Note Never remove the permissions assigned to the Administrators group for a .SIF file. Doing so will prevent the RIS components themselves from accessing the file and prevent proper client installations.
At this point, you are ready to service client computers with RIS. Ensure that all services are running, all configuration settings have been made, and that the client computers adhere to the minimum requirements as described above.
Top of page
Remote Installation Preparation Wizard (RIPrep)
The Remote Installation Preparation wizard (RIPrep.exe) provides the ability to prepare an existing Windows 2000 Professional installation, including locally installed applications and specific configuration setting, and replicate that image to an available RIS server on the network. The RIPrep feature currently supports replication of a single disk single partition (C Drive only) with Windows 2000 Professional installation. This means that the OS and all of the applications that make up the standard installation must reside on the C: drive before running the wizard.
First use RIS to remotely install the base Windows 2000 Professional OS on a client computer. Next, install any desired applications on the client computer. Configure the installation to adhere to any company policies; for example, you might choose to define specific screen colors, set the background bitmap to a company-based logo, or set intranet proxy server settings within Internet Explorer. Once the workstation is configured and tested, run the Remote Installation Preparation wizard (RIPrep.exe) from the RIS server that will receive the RIPrep-based OS image.
The destination computer does not need to have the same hardware as the source computer used to create the image, with the exception that the Hardware Abstraction Layer (HAL) drivers must be the same. For example, both computers must be ACPI (Advanced Configuration and Power Interface)-based or both must be non ACPI-based). In many cases, workstation-class computers do not require unique HAL drivers. The RIPrep utility uses the new Plug and Play support that ships with Windows 2000 for detecting any differences between the source and the destination computer hardware during image installation time.
To run the Remote Installation Preparation wizard (RIPrep.exe)
Install the base Windows 2000 Professional OS from an available RIS server on a supported client computer.
Install any applications locally on the client computer. Configure the client computer with any specific corporate standard desktop settings. Be sure the client installation is exactly as you want it to be. Once the image is replicated to the RIS server, you cannot alter its configuration.
Connect to the RIS server where you want to replicate this image, as follows:
Click Start , click Run, and type the following command in the Open text box:\\RISservername\Reminst\Admin\I386\RIPrep.exe
where RISservername is the computer name of the destination RIS server. In our example, this is HQ-RES-DC-01. Reminst is the Remote Installation Share that is created when you installed the RIS service on the server. Admin is the directory that contains the RIPrep.exe that launches the remote installation.
At this point, the Remote Installation Preparation wizard starts and you are presented with a welcome screen that describes the feature and its functionality. Click Next.
You are prompted to enter the name of the RIS server where you would like to replicate the contents of the client hard disk. By default, the RIS server that the wizard (RIPrep.exe) is being run from is automatically filled in (in our example, Reskit.com). Click Next.
You are prompted to provide the name of the directory on the RIS server where this image will be copied. The image is created under the \remoteInstall\setup\OS Language\Images directory. Click Next.
You are prompted to provide a friendly description and help text describing this image. The friendly description and help text are displayed to users of the Client Installation wizard during OS image selection. Provide enough information that a user can distinguish between images. Click Next.
The wizard displays a summary screen of your selections. After you have reviewed them, click Next.
The image preparation and replication process begins. The system is prepared and files are copied to the RIS server specified. Once the replication of the image completes, any remote boot enabled client computer can select the image for a local installation.
Top of page
Remote Installation Boot Disk Option
The remote installation boot disk can be used with computers that do not contain a remote boot-enabled ROM on the network card. The boot disk is designed to simulate the PXE boot process for computers that lack a supported DHCP PXE-based remote boot ROM. The boot disk generator utility is called RBFG.EXE and is located within the \RemoteInstall\admin directory on every Remote Installation Server.
The RBFG.exe utility is also contained within the Administrator Tools package that ships with Windows 2000 Server. The Administrator Tools package can be deployed across your organization using either Systems Management Server 2.0 or using the new Software Management feature, which is part of the Group Policy infrastructure.
Creating a Remote Installation Boot Floppy
To create a Remote Installation Boot Floppy, run the RBFG.exe utility from the RIS server either on a client computer that is connected to the RIS server or a computer with the administrator tools package installed.
Click Start, click Run, and in the Open text box, type RBFG.exe, and click OK.
Note: The RBFG.exe utility does not allow you to add network adapters). To create a remote installation boot disk, insert a disk into the appropriate drive and then select Create Disk.
Top of page
Remote Boot ROM PXE Architecture
Remote Installation Services uses DHCP for IP address assignment to clients. When a new DHCP- PXE-based remote boot client computer is powered on for the first time, the client requests an Internet Protocol (IP) address, and the IP address of an active boot server via the DHCP protocol. As part of the initial request, the client computer sends out its globally unique identifier (GUID or UUID), which is used to uniquely identify the client machine within the Active Directory, in the case of Windows 2000 Remote Installation Services.
From the RIS server, the client computer receives:
Its own IP address from DHCP.
The IP address of the RIS server.
The name of a boot image the client computer will need to request when contacting the RIS server for initial service.
Once the client request is made, the first RIS server to respond will check Active Directory to see if this client has been pre-staged or not. RIS does this by checking in Active Directory for a computer account object that has the unique GUID/UUID.
The PXE process is used every time a remote boot ROM-enabled client requests a network service boot. Remote boot/installation server vendors implement their own process to download the first image.
Top of page
Conclusion
The information presented in this guide has provided the technical details required to install, configure, and use Microsoft Remote Installation Services.
Remote Installation Services require several of the Windows 2000 Server technologies—Active Directory, DHCP server, and the DNS server services. The remote installation server also requires that client computers contain either the new DHCP PXE-based remote boot capable ROMs or a network card supported by the remote installation boot floppy.
Top of page
Appendix A: Remote Installation Server and Workstation Hardware Requirements
Server Hardware Requirements
See the Product Compatibility page to verify that your server meets the minimum requirements for Windows 2000 Server.
Pentium or Pentium II 200 megahertz (MHz) recommended (166 MHz minimum)
64 MB RAM minimum. If additional services such as the DS, DHCP, and DNS are installed then the minimum amount of RAM is 96 or 128 MB
2-GB drive dedicated to the Remote Installation Servers directory tree
10 or 100 megabits per second (Mbps) network adapter card. (100 Mbps preferred.)
Note: You should dedicate an entire hard drive or partition specifically to the Remote Installation Services directory tree. (SCSI-based disk controller/disks are preferred.)
Client Hardware Requirements
See the Product Compatibility page to make sure that your workstation meets the minimum requirements for Windows 2000 Professional.
Pentium 166 MHz or greater NetPC client computer
32 MB of RAM
1.2-GB drive minimum
PXE DHCP-based boot ROM version .99c or greater or a network adapter supported by the RIS boot floppy.
Best Practice: Always check with the manufacturer of your network adapter to get the latest version of the PXE ROM.
Network Cards supported by RIS Boot Floppy
3 Com Network Adapters
3c900 (Combo and TP0)
3c900B (Combo, FL, TPC, TP0)
3c905 (T4 and TX)
3c905B (Combo, TX, FX)
AMD Network Adapters
AMD PCNet and Fast PC Net
Compaq Network Adapters
Netflex 100 (NetIntelligent II)
Netflex 110 (NetIntelligent III)
Digital Equipment Corporation (DEC) Network Adapters
DE 450
DE 500
Hewlett-Packard Network Adapters
HP Deskdirect 10/100 TX
Intel Corporation Network Adapters
Intel Pro 10+
Intel Pro 100+
Intel Pro 100B (including the E100 series)
SMC Network Adapters
SMC 8432
SMC 9332
SMC 9432
Friday, June 11, 2010
Mounted Drive
This article describes how to create a mounted drive by using Disk Management in Microsoft Windows XP and in Microsoft Windows Server 2003. A mounted drive is a drive that is mapped to an empty folder on a volume that uses the NTFS file system. Mounted drives function as any other drives, but they are assigned drive paths instead of drive letters. When you view a mounted drive in Windows Explorer, it appears as a drive icon in the path in which it is mounted. Because mounted drives are not subject to the 26-drive-letter limit for local drives and mapped network connections, use mounted drives when you want to gain access to more than 26 drives on your computer. For example, if you have a CD-ROM drive with the drive letter E, and an NTFS volume with the drive letter F, mount the CD-ROM drive as F:\CD-ROM. You can then free the drive letter E, and gain access to your CD-ROM drive directly by using F:\CD-ROM.You can also use mounted drives when you need additional storage space on a volume. If you map a folder on that volume to another volume with available disk space (for example, 2 gigabytes), you extend the storage space of the volume by 2 gigabytes (GB). With mounted drives, you are not limited by the size of the volume in which the folder is created. Mounted drives make your data more accessible and give you the flexibility to manage data storage based on your work environment and system usage. These are additional examples by which you can use mounted drives:
To provide additional disk space for your temporary files, you can make the C:\Temp folder a mounted drive.
When space starts to run low on drive C, you can move the My Documents folder to another drive with more available disk space, and then mount it as C:\My Documents.Use the Disk Management snap-in to mount a drive on a folder on a local volume. The folder in which you mount the drive must be empty, and must be located on a basic or dynamic NTFS volume.
To provide additional disk space for your temporary files, you can make the C:\Temp folder a mounted drive.
When space starts to run low on drive C, you can move the My Documents folder to another drive with more available disk space, and then mount it as C:\My Documents.Use the Disk Management snap-in to mount a drive on a folder on a local volume. The folder in which you mount the drive must be empty, and must be located on a basic or dynamic NTFS volume.
Windows Server 2003 - Tips
Windows Server 2003 - Tips
Here is a selection of my favourite Windows Server 2003 tips. My aim is to provide variety, so I hope you will discover at least one valuable tip.
1) Disable the original Administrator account
In Windows Server 2003, for the first time, you CAN disable the Administrator account. My point is that every hacker knows that Windows has a username called Administrator, so defend it by disabling the account. (Right Click the Administrator, Disable) Obviously you must create another account with administrative privileges.
There are two variations of this tip.
a) You could disable the account from logging on across the network
b) You could rename the account and create a dummy administrator to confuse would be hackers
2) View Advanced Features
As you are an expert, display all those hidden menus and folders.
a) Go to the Active Directory Users and Computers, Select View (Menu) then check: Advanced Features. Now you should see the 'LostAndFound' folder and so be able to check for any orphaned users.
b) Select the DNS Icon, View (Menu), Advanced. This brings the DNS 'Cached Lookups' folder into view.
c) Device Manager, Show Hidden Devices. This useful for troubleshooting Non Plug and Play devices.
3) The easiest way to bring up the System Icon
Here is my favourite keyboard short cut: (Windows Key) + Pause/Break (Key)
4) Remote Desktop
The idea is to connect to the Windows Server 2003 from your XP Desktop. Configure Remote Desktop from the System Icon, Remote (tab), Remote Desktop. This will save you that long walk to the server room.
When you are logged on to your XP machine go to Accessories, Communication, Remote Desktop connection. Incidentally, remote desktop was voted the top reason to migrate to XP and here it is on Server 2003.
5) Troubleshooting Error Messages.
a) Start, Help and Support, Troubleshooting Strategies (Bullet point 5) Here is a wonderful selection of tools to lead you methodically through a problem. Each hardware device will have its own troubleshooters. They are excellent for making sure you have not overlooked something obvious.
b) Start, Help and Support, Error and Event Log Messages. Just type in the error message which you find in the Event Viewer, make sure you are on line, and Microsoft will help diagnose the cause and Orion Network Performance Monitor (NPM) v10
Solarwinds' Orion performance monitor will help you discover what's happening on your network. Also this utility will guide you through troubleshooting; the dashboard will indicate whether the root cause is a broken link, faulty equipment or resource overload. Because it produces network-centric views, the NPM is intuitive to navigate, and you can export the results to Microsoft Visio.
Perhaps Orion's best feature is the way it suggests solutions. Moreover, if problems arise out of the blue, then you can configure Orion NPM v10 to notify members of your team what's changed and how to fix it.
If you are interested in troubleshooting, and creating network maps, then I recommend that you take advantage of Solarwinds'
6) To display your Username and Computer Name on the 'My Computer'
Here is a tip for those who like to hack the registry.
Preliminary step, show the 'My Computer' icon, go to Control Panel, Display, Desktop (Tab), Customize Desktop, Check My Computer.
Principle: Find the setting for the My Computer object in the HKey_Classes_Root, substitute two variables for the original setting. Warning:This is a particularly difficult registry change to make so export the registry FIRST. Regedit, File (menu), Export.
Getting Started
a) Use regedit to locate [HKEY_CLASSES_ROOT\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D} rename LocalizedString to LocalizedString.Old. I advice this step in case anything goes wrong and you want to revert to how it was.
b) Create a new VALUE type Expand_SZ name it LocalizedString Set the value of LocalizedString to %Username% at %Computername%
Press F5 to refresh the 'My Computer', there is no need to logoff and certainly do not reboot.
7) Configure a short cut to 'Run As' a different user.
This tip only works on short cuts. So create a short cut to one of your key programs, for example Active Directory Users and Computers. Right click the short cut, Properties, Advanced (Button), Run with Different Credentials. The idea behind 'Run As' is to encourage you to log on as an ordinary user, and then use 'elevated rights' when you need to run the administrative tools. What it does is save you having to log off and then logon again as the administrator.
8) Taskbar appearance
Right Click the Grey Bar at the bottom of the screen, Properties - check out all the settings.
Here is a selection of my favourite Windows Server 2003 tips. My aim is to provide variety, so I hope you will discover at least one valuable tip.
1) Disable the original Administrator account
In Windows Server 2003, for the first time, you CAN disable the Administrator account. My point is that every hacker knows that Windows has a username called Administrator, so defend it by disabling the account. (Right Click the Administrator, Disable) Obviously you must create another account with administrative privileges.
There are two variations of this tip.
a) You could disable the account from logging on across the network
b) You could rename the account and create a dummy administrator to confuse would be hackers
2) View Advanced Features
As you are an expert, display all those hidden menus and folders.
a) Go to the Active Directory Users and Computers, Select View (Menu) then check: Advanced Features. Now you should see the 'LostAndFound' folder and so be able to check for any orphaned users.
b) Select the DNS Icon, View (Menu), Advanced. This brings the DNS 'Cached Lookups' folder into view.
c) Device Manager, Show Hidden Devices. This useful for troubleshooting Non Plug and Play devices.
3) The easiest way to bring up the System Icon
Here is my favourite keyboard short cut: (Windows Key) + Pause/Break (Key)
4) Remote Desktop
The idea is to connect to the Windows Server 2003 from your XP Desktop. Configure Remote Desktop from the System Icon, Remote (tab), Remote Desktop. This will save you that long walk to the server room.
When you are logged on to your XP machine go to Accessories, Communication, Remote Desktop connection. Incidentally, remote desktop was voted the top reason to migrate to XP and here it is on Server 2003.
5) Troubleshooting Error Messages.
a) Start, Help and Support, Troubleshooting Strategies (Bullet point 5) Here is a wonderful selection of tools to lead you methodically through a problem. Each hardware device will have its own troubleshooters. They are excellent for making sure you have not overlooked something obvious.
b) Start, Help and Support, Error and Event Log Messages. Just type in the error message which you find in the Event Viewer, make sure you are on line, and Microsoft will help diagnose the cause and Orion Network Performance Monitor (NPM) v10
Solarwinds' Orion performance monitor will help you discover what's happening on your network. Also this utility will guide you through troubleshooting; the dashboard will indicate whether the root cause is a broken link, faulty equipment or resource overload. Because it produces network-centric views, the NPM is intuitive to navigate, and you can export the results to Microsoft Visio.
Perhaps Orion's best feature is the way it suggests solutions. Moreover, if problems arise out of the blue, then you can configure Orion NPM v10 to notify members of your team what's changed and how to fix it.
If you are interested in troubleshooting, and creating network maps, then I recommend that you take advantage of Solarwinds'
6) To display your Username and Computer Name on the 'My Computer'
Here is a tip for those who like to hack the registry.
Preliminary step, show the 'My Computer' icon, go to Control Panel, Display, Desktop (Tab), Customize Desktop, Check My Computer.
Principle: Find the setting for the My Computer object in the HKey_Classes_Root, substitute two variables for the original setting. Warning:This is a particularly difficult registry change to make so export the registry FIRST. Regedit, File (menu), Export.
Getting Started
a) Use regedit to locate [HKEY_CLASSES_ROOT\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D} rename LocalizedString to LocalizedString.Old. I advice this step in case anything goes wrong and you want to revert to how it was.
b) Create a new VALUE type Expand_SZ name it LocalizedString Set the value of LocalizedString to %Username% at %Computername%
Press F5 to refresh the 'My Computer', there is no need to logoff and certainly do not reboot.
7) Configure a short cut to 'Run As' a different user.
This tip only works on short cuts. So create a short cut to one of your key programs, for example Active Directory Users and Computers. Right click the short cut, Properties, Advanced (Button), Run with Different Credentials. The idea behind 'Run As' is to encourage you to log on as an ordinary user, and then use 'elevated rights' when you need to run the administrative tools. What it does is save you having to log off and then logon again as the administrator.
8) Taskbar appearance
Right Click the Grey Bar at the bottom of the screen, Properties - check out all the settings.
Thursday, January 21, 2010
To create Invisible drive
ஒரு குறிப்பிட்ட டிரைவை My Computer லிருந்து மறைய வைக்க ஒரு டிரிக்..,
Start சென்று Run -ல் 'Regedit ' என டைப் செய்து என்டர் கொடுக்கவும்.
இதில் கீழ்கண்ட லொகேஷனுக்கு செல்லவும்.
A: 1
B: 2
C: 4
D: 8
E: 16
F: 32
G: 64
H: 128
I: 256
J: 512
K: 1024
L: 2048
M: 4096
N: 8192
O: 16384
P: 32768
Q: 65536
R: 131072
S: 262144
T: 524288
U: 1048576
V: 2097152
W: 4194304
X: 8388608
Y: 16777216
Z: 33554432
All: 67108863
இப்பொழுது உங்கள் கணினியை Restart செய்ய வேண்டும். அவ்ளோதான்!
உங்கள் டிரைவ் மறைந்து விடும்.
குறிப்பு:
உங்கள் 'C' (System Drive) டிரைவை மறைக்க முடியாது
Start சென்று Run -ல் 'Regedit ' என டைப் செய்து என்டர் கொடுக்கவும்.
இதில் கீழ்கண்ட லொகேஷனுக்கு செல்லவும்.
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer
அதில் 'Explorer' ல் ரைட் பட்டன் கிளிக் செய்து New மற்றும் "DWORD Value" ஐ தேர்வு செய்து அதற்கு 'NoDrives' என பெயரிடவும்.
பிறகு NoDrive ஐ இரண்டு முறை கிளிக் செய்து, அதனுடைய Properties ல் 'Base Unit ல் Decimal ஐ தேர்வு செய்யவும்.
பிறகு எந்த டிரைவை மறைக்க வேண்டுமோ அதனுடைய வேல்யூவை கொடுக்கவும்.
A: 1
B: 2
C: 4
D: 8
E: 16
F: 32
G: 64
H: 128
I: 256
J: 512
K: 1024
L: 2048
M: 4096
N: 8192
O: 16384
P: 32768
Q: 65536
R: 131072
S: 262144
T: 524288
U: 1048576
V: 2097152
W: 4194304
X: 8388608
Y: 16777216
Z: 33554432
All: 67108863
நீங்கள் உங்களுடைய 'E' டிரைவை மறைக்க விரும்பினால் வேல்யூ - 16 என்று கொடுக்கலாம். இதில் சிறப்பான ஒரு செய்தி என்னவென்றால், ஒருவேளை ஒன்றுக்கு மேற்பட்ட டிரைவ் களை மறைக்க வேண்டுமெனில் அதனுடைய மதிப்பை மட்டும் கூட்டினால் போதுமானது. உதாரணமாக 'E' ஐயும் 'G' டிரைவையும் மறைக்க மதிப்பு -80, அதாவது 64+16.
இப்பொழுது உங்கள் கணினியை Restart செய்ய வேண்டும். அவ்ளோதான்!
உங்கள் டிரைவ் மறைந்து விடும்.
மறுபடியும் தோன்ற வைக்க Registry -ல் அந்த குறிப்பிட்ட Key Value ஐ 0 ஆக மாற்றினாலோ அல்லது அந்த Key ஐ Delete செய்தாலோ போதுமானது.
குறிப்பு:
உங்கள் 'C' (System Drive) டிரைவை மறைக்க முடியாது
Monday, January 18, 2010
harddisk
நாம் புதிதாக மடிகணினி வாங்கும் பொழுது, வழக்கமாக அதில் விண்டோஸ் 7 அல்லது விஸ்டா இயங்குதளம் ஏற்கனவே நிறுவப்பட்டிருக்கும். இப்படி வாங்கிய மடிக் கணினிகளில் பல பேருக்கு ஏற்படுகின்ற சிக்கல் ஒன்று உண்டு. நம்மில் பலர் டெஸ்க் டாப் கணினிகளில் அதிகமாக பயன்படுத்தி பழக்கப்பட்டவர்கள், அதில் நமக்கு தேவையான கோப்புகளை நமது வசதிக்கு ஏற்றவாறு D,E,F என எந்த பார்ட்டிஷன்களிலும் வைத்துக் கொள்வது வழக்கம்.
ஆனால் பல மடிக்கணினிகளில் வன்தட்டின் கொள்ளளவு 320GB / 500GB என எவ்வளவு இருந்தாலும், இரண்டு பார்ட்டிஷன்கள் மட்டுமே இருக்கும், அதிலும் ஒன்று (C) இயங்குதளத்திற்கும் மற்றொன்று (D) ரெகவரிக்கும் மட்டுமே இருக்கும். அந்த 'ரெகவரி பார்ட்டிஷனை தொடாதே' என எச்சரிக்கை வேறு ஒருபுறம் பயமுறுத்தும். என்ன செய்வது நாமோ D for DATA, G for Games என பழக்கப்பட்டவர்கள். இதற்கு தீர்வாக பார்ட்டிஷன் மேஜிக் போன்ற பல மென்பொருட்கள் இருந்தாலும், விண்டோஸ் 7 மற்றும் விஸ்டாவில் உள்ளிணைக்கப் பட்டுள்ள வசதியை பயன்படுத்தி,ஏற்கனவே உள்ள C பார்ட்டிஷனின் அளவை குறைத்து, புதிதாக ஒரு பார்ட்டிஷனை எப்படி நிறுவுவது எனப் பார்க்கலாம்.
விண்டோஸ் 7 / விஸ்டாவில் ஸ்டார்ட் பட்டனை கிளிக் செய்து Control Panel சென்று சர்ச் பாக்ஸில் Partition என டைப் செய்து வரும் லிங்கில் Disk Management திரையை திறந்து கொள்ளுங்கள்.
Disk Management திரையில் நீங்கள் சுருக்க விரும்பும் பார்ட்டிஷனை (உதாரணமாக C Drive) வலது கிளிக் செய்து “Shrink Volume” ஐ கிளிக் செய்யுங்கள்.
இனி திறக்கும் Shrink C: என்ற வசனப் பெட்டியில் அந்த பார்ட்டிஷனை எவ்வளவு சுருக்க வேண்டும் என்பதை MB -யில் கொடுக்க வேண்டும். உதாரணமாக 100 GB அளவுள்ள பார்ட்டிஷனை 80 GB அளவாக சுருக்க Enter the amount of space to shrink in MB என்பதற்கு நேராக 20000 என கொடுக்க வேண்டும்.
இனி உங்கள் வன் தட்டில் Unallocated பார்ட்டிஷன் ஐ வலது கிளிக் செய்து புதிய பார்ட்டிஷனை உருவாக்கிக் கொள்ளலாம்.
இதே போல பார்ட்டிஷனை விரிவு படுத்த உங்கள் வன்தட்டில் உபயோகப்படுத்தாத அதிகப்படியான இடம் இருந்தால் Shrink Volume க்கு முன்னதாக உள்ள Extend Volume எனும் வசதியை தேர்வு செய்து தேவையான பார்ட்டிஷனை விரிவு படுத்தலாம்.
USB டிரைவ்-. NTFS
NTFS File சிஸ்டம் என்பது அதிக பாதுகாப்பும், வேகமும் கொண்டதாகும்.
ஆரம்ப காலங்களில் விற்பனைக்கு வந்த USB டிரைவ்கள் குறைந்த கொள்ளளவு கொண்டதாக இருந்தது. எனவே அதற்கு NTFS File சிஸ்டம் தேவைப்படாமல் இருந்தது. ஆனால் தற்போது சந்தையில் விற்பனைக்கு வருகின்ற USB Drive கள் அதிக கொள்ளளவு கொண்டதாக உள்ளதால் இதனை NTFS File system மூலம் ஃபார்மேட் செய்வது பாதுகாப்பானதாகும்.
வழக்கமாக USB Drive -ஐ ஃபார்மேட் செய்ய முற்படுகையில் அதில் FAT - option மட்டுமே இருக்கும். NTFS -option - ஐ கொண்டுவர என்ன செய்ய..,
USB drive ஐ கணினியில் பொருத்துங்கள்.
My Computer - ஐ ரைட் கிளிக் செய்து Device Manager க்கு செல்லுங்கள்.
Select Disk Drives and expand
Right Click on USB drive and select Properties
Goto policies tab and select Optimize for performance and press OK
Open My Computer, Click on USB Drive and select Format Option
Now you can have NTFS option there.
NTFS enabled USB Drives are write-able only on one PC and becomes read only on all other PCs. Hence, we can read and write on our own PC and transfer files to elsewhere without any fear of virus.
ஆரம்ப காலங்களில் விற்பனைக்கு வந்த USB டிரைவ்கள் குறைந்த கொள்ளளவு கொண்டதாக இருந்தது. எனவே அதற்கு NTFS File சிஸ்டம் தேவைப்படாமல் இருந்தது. ஆனால் தற்போது சந்தையில் விற்பனைக்கு வருகின்ற USB Drive கள் அதிக கொள்ளளவு கொண்டதாக உள்ளதால் இதனை NTFS File system மூலம் ஃபார்மேட் செய்வது பாதுகாப்பானதாகும்.
வழக்கமாக USB Drive -ஐ ஃபார்மேட் செய்ய முற்படுகையில் அதில் FAT - option மட்டுமே இருக்கும். NTFS -option - ஐ கொண்டுவர என்ன செய்ய..,
USB drive ஐ கணினியில் பொருத்துங்கள்.
My Computer - ஐ ரைட் கிளிக் செய்து Device Manager க்கு செல்லுங்கள்.
Select Disk Drives and expand
Right Click on USB drive and select Properties
Goto policies tab and select Optimize for performance and press OK
Open My Computer, Click on USB Drive and select Format Option
Now you can have NTFS option there.
NTFS enabled USB Drives are write-able only on one PC and becomes read only on all other PCs. Hence, we can read and write on our own PC and transfer files to elsewhere without any fear of virus.
My கம்ப்யூட்டர்
My computer ஐ ரைட் கிளிக் செய்து properties செல்லவும். இதில் General tab-ல் 'Registered to' கீழே முதல் வரியில் இருப்பது உரிமையாளர் பெயர், இரண்டாவது வரியில் இருப்பது நிறுவனத்தின் பெயர்.
இதை மாற்றும் வழி இதோ,
Start -> Run இதில் regedit என டைப் செய்து enter அடிக்கவும்.
ரிஜிஸ்டரி எடிட்டரில் கீழே குறிப்பிட்ட பகுதிக்கு செல்லவும்.
HKEY_LOCAL_MACHINE
SOFTWARE
Microsoft
Windows NT
CurrentVersion இல் கிளிக் செய்து வலதுபுறமுள்ள பேனில்
நிறுவனத்தின் பெயரை மாற்ற RegisteredOrganization -ஐ இரட்டை கிளிக் செய்து Value data -ல், புதிய நிறுவனத்தின் பெயரை டைப் செய்து OK கொடுக்கவும்.
உரிமையாளர் பெயரை மாற்ற RegisteredOwner ஐ இரட்டை கிளிக் செய்து Value data -ல் புதிய பெயரை டைப் செய்து OK கொடுக்கவும்.
ரிஜிஸ்டரி எடிட்டரை மூடிவிட்டு கணினியை மறுபடி துவக்கவும்.
இப்பொழுது மை கம்ப்யூட்டரை வலது கிளிக் செய்து ப்ராப்பர்டீஸ் சென்று பாருங்கள்.
மாற்றம் தெரியும்.
இதை மாற்றும் வழி இதோ,
Start -> Run இதில் regedit என டைப் செய்து enter அடிக்கவும்.
ரிஜிஸ்டரி எடிட்டரில் கீழே குறிப்பிட்ட பகுதிக்கு செல்லவும்.
HKEY_LOCAL_MACHINE
SOFTWARE
Microsoft
Windows NT
CurrentVersion இல் கிளிக் செய்து வலதுபுறமுள்ள பேனில்
நிறுவனத்தின் பெயரை மாற்ற RegisteredOrganization -ஐ இரட்டை கிளிக் செய்து Value data -ல், புதிய நிறுவனத்தின் பெயரை டைப் செய்து OK கொடுக்கவும்.
உரிமையாளர் பெயரை மாற்ற RegisteredOwner ஐ இரட்டை கிளிக் செய்து Value data -ல் புதிய பெயரை டைப் செய்து OK கொடுக்கவும்.
ரிஜிஸ்டரி எடிட்டரை மூடிவிட்டு கணினியை மறுபடி துவக்கவும்.
இப்பொழுது மை கம்ப்யூட்டரை வலது கிளிக் செய்து ப்ராப்பர்டீஸ் சென்று பாருங்கள்.
மாற்றம் தெரியும்.
Bluetoohkey
விண்டோஸில் மறைந்திருக்கும் Bluetooth மென்பொருள் எதுவென்று.
Start க்கு சென்று Run -ல்
fsquirt
என டைப் செய்து என்டர் கொடுங்கள்.
இப்பொழுது Bluetooth File Transfer Wizard என்ற விண்டோ திறக்கும்.
இந்த Wizard ஐ பயன்படுத்தி உங்கள் Bluetooth device -ல் File Transfer செய்யலாம்.
Start க்கு சென்று Run -ல்
fsquirt
என டைப் செய்து என்டர் கொடுங்கள்.
இப்பொழுது Bluetooth File Transfer Wizard என்ற விண்டோ திறக்கும்.
இந்த Wizard ஐ பயன்படுத்தி உங்கள் Bluetooth device -ல் File Transfer செய்யலாம்.
சோர்ட் கட் KEY
நமது கீ போர்டில் உள்ள விண்டோஸ் கீயை நம்மில் பலர் உபயோகிப்பதில்லை. ஆனால் அதன் முழு பயன்பாட்டையும் தெரிந்து கொண்டால், அவசியம் அந்த கீயை உபயோகிப்பீர்கள் என நம்புகிறேன்.
1. விண்டோஸ் கீ - Start மெனு
2. விண்டோஸ் கீ + D - திறந்திருக்கும் அனைத்து விண்டோக்களையும் மினிமைஸ்/ரிஸ்டோர் செய்ய.
3. விண்டோஸ் கீ + E - விண்டோஸ் எக்ஸ்ப்ளோரர் ஐ திறக்க.
4. விண்டோஸ் கீ + F - விண்டோஸ் Search for files.
5. விண்டோஸ் கீ + Ctrl + F - Search for computer
6. விண்டோஸ் கீ + F1 - Help and Support Center
7. விண்டோஸ் கீ + R - Run கமேண்ட்
8. விண்டோஸ் கீ + break - சிஸ்டம் ப்ராப்பர்டீஸ்
9. விண்டோஸ் கீ + shift + M - Undo minimize all windows
10. விண்டோஸ் கீ + U - Utility Manager ஐ திறக்க.
Computer Management
Computer Management என்பது 'Services, Applications, Disk tools மற்றும் User and Group Administration' ஆகியவற்றை ஒரே குடையின் கொண்டுள்ள கருவியாகும்.
மை கம்ப்யூட்டரில் வலது கிளிக் செய்து இதில் 'Manage' கிளிக் செய்தால் 'Computer Management' என்ற விண்டோ திறக்கும். இந்த விண்டோவில் இடதுபுறமுள்ள pane ல் 'system Tools, Storage மற்றும் Services and Applications' ஆகிய பகுதிகள் இருக்கும். ஒவ்வொன்றிலும் கிளிக் செய்திட வலதுபுறமுள்ள pane ல் அதன் விபரங்கள் பட்டியலிடப்படும். இதில் ஒவ்வொன்றிலும் என்ன வசதிகள் தரப்பட்டிருக்கின்றன என்பதை சுருக்கமாக பார்ப்போம்.
System Tools:-
இந்த பகுதியில் கணினியின் கண்காணிப்பு, பயனாளர்கள் மற்றும் பயனாளர் குழுக்களுக்கு வழங்கப்படும் உரிமைகள் சம்பந்தப்பட்ட அனைத்து கருவிகளும் கொடுக்கப்பட்டுள்ளன.
இதில் Shared Folders ஐ கிளிக் செய்தால் 'Shares, Sessions மற்றும் open files' ஆகிய மூன்றும் பட்டியலில் வரும். 'Shares' ஐ தேர்வு செய்தால் Network Shared Folders மற்றும் Windows Administrator ஆல் ரிமோட் அக்ஸஸ் இற்காக உருவாக்கப்பட்ட Shared Folders ஐ பார்க்கலாம். இதில் ஏதாவது குறிப்பிட்ட Folder இன் பகிர்வை நீக்க அந்த ஃபோல்டரில் வலது கிளிக் செய்து Sharing and Security யில் Share this Folder என்பதை uncheck செய்து விடுங்கள்.
Sessions என்பது தற்பொழுது உங்கள் கணினிக்கு தொடர்பிலிருக்கும் பயனாளர்கள் பற்றிய தகவல்கள், பயனாளர்களின் வகை, கணினியின் பெயர், திறந்துள்ள கோப்புகளின் எண்ணிக்கை, தொடர்பு கொண்ட நேரம் ஆகியவற்றை காண்பிக்கும். ஒருவேளை நீங்கள் எதிர்பாராத ஒரு பயனாளர் தொடர்பிலிருந்தால், அவர் இப்பொழுது உங்கள் கணினியில் எந்த ஃபோலடரிலிருந்து எந்த கோப்பை உபயோகித்துக் கொண்டிருக்கிறார் என்பதை 'Open Files' ஐ கிளிக் செய்வதன் மூலம் அறிந்து கொள்ளலாம். ஒரு அட்மினிஸ்டிரேட்டராக நீங்கள் அதை முடக்கவும் செய்யலாம்.
Local Users and Groups:-
உங்கள் கணினியில் உள்ள பயனாளர்கள் பற்றிய விவரங்களை அளிக்கும். புதிய பயனாளர் கணக்கு உருவாக்குவது, கணக்கை முடக்குவது, நீக்குவது, கடவுசொல்லை உருவாக்குவது, மாற்றுவது மற்றும் குறிப்பிட்ட பயனாளர் மறுமுறை லாகின் ஆகும்பொழுது கட்டாயமாக கடவுசொல்லை மாற்றும்படி கட்டளை கொடுப்பது என பல உபயோகமான கருவிகள் இருப்பதால் இது ஒன்றுக்க்கு மேற்பட்ட பயனர்களை கொண்ட கணினிக்கு மிகவும் உபயோகமானதாகும்.
Storage:-
இந்த பகுதியில் Disk Defragmenter மற்றும் Disk Management ஆகிய முக்கியமான கருவிகளும் Removable Storage கருவியும் உள்ளன.
இதில் Disk Defragmentation என்பது அனைவரும் அறிந்திருக்க வாய்ப்புகள் இருப்பதால் அதை இந்த பதிவில் தவிர்த்துவிடலாம்.
Disk Management ல் Partitions உருவாக்குவது மற்றும் Format மிகவும் எளிதாக செய்யலாம். இது நமது ஹார்ட் டிஸ்கில் உள்ள அனைத்து partitions மற்றும் சிடி/டிவிடி போன்ற அனைத்து வால்யூம்களையும் காண்பிக்கும். இந்த கருவியின் மூலம் Dos Command அல்லது Stratup Disk எதுவும் இல்லாமல் partition களை உருவாக்க முடியும். ட்ரைவ்களுக்கு தேவையான ட்ரைவ் லெட்டர்களையும் கொடுக்க முடியும்.
புதிய partition ஐ உருவாக்க, Unpartition Space ல் வலது கிளிக் செய்து New Partition ஐ கிளிக் செய்து, உங்களுக்கு தேவையான partition வகையை தேர்வு செய்து (Primary, Extended or Logical) அடுத்து வரும் திரையில் partition size, Volume Label மற்றும் partition வகை (FAT32/NTFS). Format வகையையும் தேர்வு செய்து கொள்ளலாம்.
எச்சரிக்கை:-
இந்த கருவியை உப்யோகிக்கும் பொழுது மிகவும் கவனமாகவும், வல்லுனர்களின் ஆலோசனையின்படியும் உபயோகிக்கவும்.
Services and Applications:-
இந்த கருவியை உபயோகித்து ஒரு குறிப்பிட்ட Service ஐ Start, Restart, Stop மற்றும் Pause செய்யலாம்.
இதிலுள்ள மற்றொரு அவசியமான (நொடியில் உங்கள் கோப்புகளை தேட..,) கருவியைப்பற்றி இந்த பதிவில் பார்க்கவும்.
மை கம்ப்யூட்டரில் வலது கிளிக் செய்து இதில் 'Manage' கிளிக் செய்தால் 'Computer Management' என்ற விண்டோ திறக்கும். இந்த விண்டோவில் இடதுபுறமுள்ள pane ல் 'system Tools, Storage மற்றும் Services and Applications' ஆகிய பகுதிகள் இருக்கும். ஒவ்வொன்றிலும் கிளிக் செய்திட வலதுபுறமுள்ள pane ல் அதன் விபரங்கள் பட்டியலிடப்படும். இதில் ஒவ்வொன்றிலும் என்ன வசதிகள் தரப்பட்டிருக்கின்றன என்பதை சுருக்கமாக பார்ப்போம்.
System Tools:-
இந்த பகுதியில் கணினியின் கண்காணிப்பு, பயனாளர்கள் மற்றும் பயனாளர் குழுக்களுக்கு வழங்கப்படும் உரிமைகள் சம்பந்தப்பட்ட அனைத்து கருவிகளும் கொடுக்கப்பட்டுள்ளன.
இதில் Shared Folders ஐ கிளிக் செய்தால் 'Shares, Sessions மற்றும் open files' ஆகிய மூன்றும் பட்டியலில் வரும். 'Shares' ஐ தேர்வு செய்தால் Network Shared Folders மற்றும் Windows Administrator ஆல் ரிமோட் அக்ஸஸ் இற்காக உருவாக்கப்பட்ட Shared Folders ஐ பார்க்கலாம். இதில் ஏதாவது குறிப்பிட்ட Folder இன் பகிர்வை நீக்க அந்த ஃபோல்டரில் வலது கிளிக் செய்து Sharing and Security யில் Share this Folder என்பதை uncheck செய்து விடுங்கள்.
Sessions என்பது தற்பொழுது உங்கள் கணினிக்கு தொடர்பிலிருக்கும் பயனாளர்கள் பற்றிய தகவல்கள், பயனாளர்களின் வகை, கணினியின் பெயர், திறந்துள்ள கோப்புகளின் எண்ணிக்கை, தொடர்பு கொண்ட நேரம் ஆகியவற்றை காண்பிக்கும். ஒருவேளை நீங்கள் எதிர்பாராத ஒரு பயனாளர் தொடர்பிலிருந்தால், அவர் இப்பொழுது உங்கள் கணினியில் எந்த ஃபோலடரிலிருந்து எந்த கோப்பை உபயோகித்துக் கொண்டிருக்கிறார் என்பதை 'Open Files' ஐ கிளிக் செய்வதன் மூலம் அறிந்து கொள்ளலாம். ஒரு அட்மினிஸ்டிரேட்டராக நீங்கள் அதை முடக்கவும் செய்யலாம்.
Local Users and Groups:-
உங்கள் கணினியில் உள்ள பயனாளர்கள் பற்றிய விவரங்களை அளிக்கும். புதிய பயனாளர் கணக்கு உருவாக்குவது, கணக்கை முடக்குவது, நீக்குவது, கடவுசொல்லை உருவாக்குவது, மாற்றுவது மற்றும் குறிப்பிட்ட பயனாளர் மறுமுறை லாகின் ஆகும்பொழுது கட்டாயமாக கடவுசொல்லை மாற்றும்படி கட்டளை கொடுப்பது என பல உபயோகமான கருவிகள் இருப்பதால் இது ஒன்றுக்க்கு மேற்பட்ட பயனர்களை கொண்ட கணினிக்கு மிகவும் உபயோகமானதாகும்.
Storage:-
இந்த பகுதியில் Disk Defragmenter மற்றும் Disk Management ஆகிய முக்கியமான கருவிகளும் Removable Storage கருவியும் உள்ளன.
இதில் Disk Defragmentation என்பது அனைவரும் அறிந்திருக்க வாய்ப்புகள் இருப்பதால் அதை இந்த பதிவில் தவிர்த்துவிடலாம்.
Disk Management ல் Partitions உருவாக்குவது மற்றும் Format மிகவும் எளிதாக செய்யலாம். இது நமது ஹார்ட் டிஸ்கில் உள்ள அனைத்து partitions மற்றும் சிடி/டிவிடி போன்ற அனைத்து வால்யூம்களையும் காண்பிக்கும். இந்த கருவியின் மூலம் Dos Command அல்லது Stratup Disk எதுவும் இல்லாமல் partition களை உருவாக்க முடியும். ட்ரைவ்களுக்கு தேவையான ட்ரைவ் லெட்டர்களையும் கொடுக்க முடியும்.
புதிய partition ஐ உருவாக்க, Unpartition Space ல் வலது கிளிக் செய்து New Partition ஐ கிளிக் செய்து, உங்களுக்கு தேவையான partition வகையை தேர்வு செய்து (Primary, Extended or Logical) அடுத்து வரும் திரையில் partition size, Volume Label மற்றும் partition வகை (FAT32/NTFS). Format வகையையும் தேர்வு செய்து கொள்ளலாம்.
எச்சரிக்கை:-
இந்த கருவியை உப்யோகிக்கும் பொழுது மிகவும் கவனமாகவும், வல்லுனர்களின் ஆலோசனையின்படியும் உபயோகிக்கவும்.
Services and Applications:-
இந்த கருவியை உபயோகித்து ஒரு குறிப்பிட்ட Service ஐ Start, Restart, Stop மற்றும் Pause செய்யலாம்.
இதிலுள்ள மற்றொரு அவசியமான (நொடியில் உங்கள் கோப்புகளை தேட..,) கருவியைப்பற்றி இந்த பதிவில் பார்க்கவும்.
விண்டோஸ் டாஸ்க் MANAGER
வழக்கமாக விண்டோஸ் எக்ஸ்பியில் Task Manager ஐ நாம் 'Not Responding' என பிழைச் செய்தி வரும்பொழுது, 'End Task' செய்வதற்கு மட்டுமே அதிகமாக பயன்படுத்துகிறோம். அதன் இன்னும் சில அவசியமான பயன்பாடுகளை இங்கு பார்க்கலாம்.
டாஸ்க் மேனேஜருக்கு செல்ல கீழ்கண்ட வழிகள் உள்ளன.
1. Ctrl + Alt + Del.
2. Ctrl + Shift + Esc
3. Task Bar-ல் காலியாக உள்ள இடத்தில் மௌசின் வலது பொத்தானை அழுத்துவதன் மூலம்.
டாஸ்க் மேனேஜரில் 'Applications, Processes, Perfomance, Networking' மற்றும் 'Users' டேபுகள் உள்ளன.
Applications:-
நமது கணினியில் தற்பொழுது இயங்க்கிக்கொண்டிருக்கும் அப்ளிகேஷன்கள் இங்கு பட்டியலிடப்பட்டிருக்கும்.
சில சமயங்களில் ஒருசில அப்ளிகேஷன்கள் 'Not Responding' என வரும்பொழுது, இங்குள்ள பட்டியலில் அந்த குறிப்பிட்ட அப்ளிகேஷனில் வலது கிளிக் செய்து End Task செய்யலாம். ஒன்றுக்கு மேற்பட்ட அப்ளிகேஷன்களை ஷிப்ட் கீயை அழுத்தி தேர்ந்தெடுத்து பின் வலது கிளிக் செய்து End Task செய்யலாம்.
இந்தப் பட்டியலில் ஏதாவது ஒரு அப்ளிகேஷனை வலது கிளிக் செய்து அதில் Go to Process கிளிக் செய்தால் அந்த குறிப்பிட்ட அப்ளிகேஷனின் EXE file -இன் மெமரி உபயோகத்தை அறிந்து கொள்ளலாம். அப்ளிகேஷன் பெயரும் exe பைலின் பெயரும் மாறுபடலாம்.
ஒரு ஃபோல்டரிலிருந்து மற்றொரு ஃபோல்டருக்கு கோப்புகளை டிராக்(Drag) செய்யும் பொழுது, அந்த இரு விண்டோக்களும் ஒன்றுக்கு மேல் ஒன்றாக ஓவர்லேப் ஆகாமல் சரியாக Tile மோடில் arrange செய்யப்பட்டிரா விட்டால் சிரமமாக இருக்கும். அதற்கு ஒரு எளிய வழி விண்டோஸில் இங்கு மட்டுமே உண்டு. இரண்டு அல்லது அதற்கு மேற்பட்ட விண்டோக்களை ஒன்றின்மீது மற்றொன்று வராமல் திரையில் ஒரே அளவில் வரிசைப்படுத்த, அந்த அப்ளிகேஷன்களை, Applications tab- ல் தேர்ந்தெடுத்து வலது கிளிக் செய்து 'Tile Horizontally / Vertically' என்பதை தேர்வு செய்யலாம்.
Processes:-
இந்த டேபில், நம் கணினியின் பிராசஸரையும், மெமரியையும் எந்த பிராசஸ் எவ்வளவு உபயோகிக்கிறது என்பது இங்கு பட்டியலிடப்பட்டிருக்கும். CPU / Mem usage - Tiltle லில் கிளிக் செய்வதன் மூலம் அஸென்டிங்/டெஸென்டிங் மாறிக்கொள்ளலாம். தேவையில்லாத அல்லது அதிக மெமரியை உபயோகிக்கும் எந்த ப்ராசஸையும் வலது கிளிக் செய்து End Process செய்யலாம்.
தற்பொழுது வரும் சில வைரஸ் மற்றும் வெர்ம்கள் ஒரு ப்ராசஸ் ஆகவே அமர்ந்து கணினியின் வேகத்தை குறைத்துவிடுகிறது. இதுபோன்ற ப்ராசஸ்களையும் இனம் கண்டு End Process செய்து விடலாம். (உதாரணம்: Svcchost, msblast.exe, Wowexec.)
வழக்கமாக நாம் மினிமைஸ் செய்யும் அப்ளிகேஷன்கள் சில சமயங்களில் RAM இல் சிறிதும் மற்றவை Virtual memory க்கு சென்றுவிடும் வாய்ப்பு உள்ளது. virtual memory யில் எவ்வளவு உபயோகப்படுத்தப் பட்டுள்ளது என்பதையும் மற்றும் CPU, Mem usage தவிர பிற உபயோகங்களை டேபில் சேர்க்க View menu விற்கு சென்று Select Column கிளிக் செய்து சேர்த்துக் கொள்ளலாம்.
Performance:-
இந்த டேபில் CPU/ Memory usage ஆகியவற்றை வரைபடம் மூலம் கொடுக்கப்பட்டிருக்கும்.
டிப்ஸ்:-
தற்சமயம் உபயோகிக்காத அப்ளிகேஷன்களை மினிமைஸ் செய்வதன் மூலம் மெமெரி உபயோகத்தை கணிசமான அளவில் குறைக்க முடியும்.
Options menu -வில் Hide when minimized கிளிக் செய்து மினிமைஸ் செய்துவிட்டால், டாஸ்க் மேனேஜர் ஒரு சிறிய பச்சை நிற ஐகானாக உங்கள்
சிஸ்டம் ட்ரேயில் தெரியும். அதில் கர்சரை கொண்டுபோனால் சிபியு உபயோக சதவீதத்தை அறிந்து கொள்ளலாம்.
டாஸ்க் மேனேஜருக்கு செல்ல கீழ்கண்ட வழிகள் உள்ளன.
1. Ctrl + Alt + Del.
2. Ctrl + Shift + Esc
3. Task Bar-ல் காலியாக உள்ள இடத்தில் மௌசின் வலது பொத்தானை அழுத்துவதன் மூலம்.
டாஸ்க் மேனேஜரில் 'Applications, Processes, Perfomance, Networking' மற்றும் 'Users' டேபுகள் உள்ளன.
Applications:-
நமது கணினியில் தற்பொழுது இயங்க்கிக்கொண்டிருக்கும் அப்ளிகேஷன்கள் இங்கு பட்டியலிடப்பட்டிருக்கும்.
சில சமயங்களில் ஒருசில அப்ளிகேஷன்கள் 'Not Responding' என வரும்பொழுது, இங்குள்ள பட்டியலில் அந்த குறிப்பிட்ட அப்ளிகேஷனில் வலது கிளிக் செய்து End Task செய்யலாம். ஒன்றுக்கு மேற்பட்ட அப்ளிகேஷன்களை ஷிப்ட் கீயை அழுத்தி தேர்ந்தெடுத்து பின் வலது கிளிக் செய்து End Task செய்யலாம்.
இந்தப் பட்டியலில் ஏதாவது ஒரு அப்ளிகேஷனை வலது கிளிக் செய்து அதில் Go to Process கிளிக் செய்தால் அந்த குறிப்பிட்ட அப்ளிகேஷனின் EXE file -இன் மெமரி உபயோகத்தை அறிந்து கொள்ளலாம். அப்ளிகேஷன் பெயரும் exe பைலின் பெயரும் மாறுபடலாம்.
ஒரு ஃபோல்டரிலிருந்து மற்றொரு ஃபோல்டருக்கு கோப்புகளை டிராக்(Drag) செய்யும் பொழுது, அந்த இரு விண்டோக்களும் ஒன்றுக்கு மேல் ஒன்றாக ஓவர்லேப் ஆகாமல் சரியாக Tile மோடில் arrange செய்யப்பட்டிரா விட்டால் சிரமமாக இருக்கும். அதற்கு ஒரு எளிய வழி விண்டோஸில் இங்கு மட்டுமே உண்டு. இரண்டு அல்லது அதற்கு மேற்பட்ட விண்டோக்களை ஒன்றின்மீது மற்றொன்று வராமல் திரையில் ஒரே அளவில் வரிசைப்படுத்த, அந்த அப்ளிகேஷன்களை, Applications tab- ல் தேர்ந்தெடுத்து வலது கிளிக் செய்து 'Tile Horizontally / Vertically' என்பதை தேர்வு செய்யலாம்.
Processes:-
இந்த டேபில், நம் கணினியின் பிராசஸரையும், மெமரியையும் எந்த பிராசஸ் எவ்வளவு உபயோகிக்கிறது என்பது இங்கு பட்டியலிடப்பட்டிருக்கும். CPU / Mem usage - Tiltle லில் கிளிக் செய்வதன் மூலம் அஸென்டிங்/டெஸென்டிங் மாறிக்கொள்ளலாம். தேவையில்லாத அல்லது அதிக மெமரியை உபயோகிக்கும் எந்த ப்ராசஸையும் வலது கிளிக் செய்து End Process செய்யலாம்.
தற்பொழுது வரும் சில வைரஸ் மற்றும் வெர்ம்கள் ஒரு ப்ராசஸ் ஆகவே அமர்ந்து கணினியின் வேகத்தை குறைத்துவிடுகிறது. இதுபோன்ற ப்ராசஸ்களையும் இனம் கண்டு End Process செய்து விடலாம். (உதாரணம்: Svcchost, msblast.exe, Wowexec.)
வழக்கமாக நாம் மினிமைஸ் செய்யும் அப்ளிகேஷன்கள் சில சமயங்களில் RAM இல் சிறிதும் மற்றவை Virtual memory க்கு சென்றுவிடும் வாய்ப்பு உள்ளது. virtual memory யில் எவ்வளவு உபயோகப்படுத்தப் பட்டுள்ளது என்பதையும் மற்றும் CPU, Mem usage தவிர பிற உபயோகங்களை டேபில் சேர்க்க View menu விற்கு சென்று Select Column கிளிக் செய்து சேர்த்துக் கொள்ளலாம்.
Performance:-
இந்த டேபில் CPU/ Memory usage ஆகியவற்றை வரைபடம் மூலம் கொடுக்கப்பட்டிருக்கும்.
டிப்ஸ்:-
தற்சமயம் உபயோகிக்காத அப்ளிகேஷன்களை மினிமைஸ் செய்வதன் மூலம் மெமெரி உபயோகத்தை கணிசமான அளவில் குறைக்க முடியும்.
Options menu -வில் Hide when minimized கிளிக் செய்து மினிமைஸ் செய்துவிட்டால், டாஸ்க் மேனேஜர் ஒரு சிறிய பச்சை நிற ஐகானாக உங்கள்
சிஸ்டம் ட்ரேயில் தெரியும். அதில் கர்சரை கொண்டுபோனால் சிபியு உபயோக சதவீதத்தை அறிந்து கொள்ளலாம்.
வோர்ட் டாகுமென்ட் RECOVREY
நாம் மைக்ரோசாப்ட் வேர்டில் ஏதாவது டாக்குமெண்டை பல பக்கங்கள் டைப் செய்து விட்டு சில சமயங்களில் சேமிக்காமலேயே வேர்டு-ஐ மூடி விடுவோம். பிறகு அந்த டாக்குமெண்ட் மறுபடி வேண்டுமே என்ன செய்வது என திண்டாடி, வேறு வழியில்லாமல், மறுபடி உக்கார்ந்து டைப் செய்ய வேண்டிய நிலைக்கு தள்ளப்படுவோம்.
இப்படி சேமிக்காமல் விட்ட கோப்புகளை மறுபடி பெறுவது எப்படி?
வேர்டை திறந்து கொள்ளுங்கள். Tools மெனுவிற்கு சென்று, Options ஐ கிளிக் செய்யுங்கள். இதில் File Locations என்ற டேபை கிளிக் செய்யுங்கள். இங்கு AutoRecover files என்பதற்கு நேராக blank ஆக இருந்தால், உங்கள் டாக்குமெண்டை ரெகவர் செய்ய இயலாது. அல்லாமல், Location தரப்பட்டிருந்தால் அந்த குறிப்பிட்ட லோகேஷனுக்குச் (விண்டோஸ் எக்ஸ்ப்ளோரரில்) சென்று, டாகுமெண்டை திறந்துவிடலாம்.
AutoRecovery ஐ enable செய்து வைப்பது எப்பொழுதுமே பாதுகாப்பானதாகும். இதை எப்படி செய்வது.
Tools மெனுவிற்குச் சென்று Options சென்று Save என்ற டேபில் உள்ள 'Save AutoRecover info every:' என்பதை தேவு செய்து, பின் அதற்கான நேரத்தையும் (உதாரணமாக 5 நிமிடங்கள்) கொடுத்து, File Locations டேபிற்குச் சென்று AutoRecover Files ஐ கிளிக் செய்து, "Modify..." -ல் அதற்கான லோகேஷனையும் கொடுத்துவிட்டால் போதும்.
விண்டோஸ் TRICKS
நாம் அடிக்கடி உபயோகிக்கும் ப்ரோகிராம்களை ஸ்டார்ட் மெனுவில் கொண்டு வர Pin to Start Menu என்ற வசதி வலது கிளிக் Context menu வில் உள்ளது. ஆனால் நாம் அடிக்கடி உபயோகிக்கும் ஃபோல்டர்களை விண்டோஸ் XP மற்றும் விஸ்டாவில் ஸ்டார்ட் மெனுவில் கொண்டுவர என்ன செய்யலாம்.
Search Box இல் Regedit என டைப் செய்து ரிஜிஸ்டரி எடிட்டரை திறந்து கொள்ளுங்கள். அதில் இடது புற பேனில்
HKEY_CLASSES_ROOT\Folder\shellex\ContextMenuHandlers\
என்ற பகுதிக்குச் சென்று {a2a9545d-a0c2-42b4-9708-a0b2badd77c8} என்ற கீயை உருவாக்குங்கள், அதற்கு வேல்யு எதுவும் கொடுக்க வேண்டியதில்லை.
அவ்வளவுதான். இனி உங்களுக்கு தேவைப்படும் ஃபோல்டரை Shift Key ஐ அழுத்தியபடி, வலது கிளிக் செய்து Pin to Start Menu என்பதை கிளிக் செய்தால், அது உங்கள் ஸ்டார்ட் மெனுவில் வந்து விடும்.
இந்த வசதி தேவியில்லை எனில், அந்த கீயை டெலிட் செய்தால் போதுமானது.
ரிஜிஸ்டரி எடிட்டரில் மாற்றம் செய்ய தயக்கமாக இருந்தால், கீழே உள்ள சுட்டிகளிலிருந்து, ரிஜிஸ்டரி கோப்புகளை தரவிறக்கி, தேவையானதை ரன் செய்து கொள்ளுங்கள்.
ஜிமெயில் TIPS
ஜிமெயில் உபயோகிப்பவர்கள் ஏதாவது ஒரு படத்தை அனுப்ப வேண்டி இருந்தால் வழக்கமாக Attachment மூலமாகவே படங்களை இணைக்கிறோம். அவ்வாறு அல்லாமல் மெயில் டெக்ஸ்ட் இன் இடையில் படங்களை இன்சர்ட் செய்வது எப்படி என்பதை பார்க்கலாம். (நாம் பிளாக்கரில் டெக்ஸ்ட் களுக்கு இடையில் படங்களை இணைப்பது போல.. )
முதலில் உங்கள் ஜிமெயில் கணக்கில் நுழையுங்கள். பிறகு வலது மேல் மூலையிலுள்ள Settings லிங்கை கிளிக் செய்யுங்கள். 'Labs' என்ற லிங்கை கிளிக் செய்தால் அதில் நிறைய வசதிகள் தரப்பட்டிருப்பதை பார்க்கலாம்.
அதில் Inserting Images க்கு நேராக Enable என்பதை தேர்வு செய்து கீழே உள்ள Save Changes பொத்தானை கிளிக் செய்து சேமித்து கொள்ளுங்கள்.
வழக்கமாக ஜிமெயில் கம்போஸ் திரை கீழே உள்ள படத்திலிருப்பது போல் இருக்கும்.
Inserting Images ஐ enable செய்த பிறகு கீழே உள்ள படத்தில் இருப்பது போல காட்சியளிக்கும்.
இனி நீங்கள் தேவையான டெக்ஸ்ட் ஐ டைப் செய்யும்பொழுது இடையில் படங்களை இணைக்க Compose mail - toolbar இல் உள்ள Insert Image பட்டனை கிளிக் செய்து, தேவையான படங்களை Browse செய்து insert செய்து விடலாம்.
இதனுடைய சிறப்பம்சம், இப்படி இணைத்த படங்களை பெரிதாக்கவோ அல்லது சிறிதாக்கவோ இயலும்.
Subscribe to:
Posts (Atom)
.gif){kind=link}
.gif){kind=link}
.gif){kind=link}
