Kedubes AS Gelar 'Golden Ticket Obama'
VIVAnews - Jelang kedatangan Presiden Amerika Serikat (AS) Barack Obama, Kedutaan Besar AS menggelar kompetisi 'Golden Ticket'. Pemenangnya, akan mendapat perjalanan pendidikan gratis ke AS. Bahkan berkunjung ke tempat-tempat yang punya arti bagi Obama.
"Lima orang finalis akan dipilih untuk tampil di sebuah acara khusus yang ditayangkan di televisim di mana para juri akan memilih tiga orang pemenang," tulis siaran pers dari Kedubes AS yang diterima VIVAnews, Kamis 18 Maret 2010.
Bagaimana caranya untuk mengikuti kompetisi 'Golden Ticket'? Mudah. Peserta tinggal menjadi penggemar akun Facebook Kedubes AS di Jakarta dan menulis esai.
Selain perlombaan 'Golden Ticket', Kedutaan AS juga menggunakan teknologi digital untuk berhubungan dengan masyarakat Indonesia.
Bagi para Tweeps, pengguna Twitter, Kedubes AS juga membuka akun di @usembassyjkt. Khusus untuk lomba ini Kedubes AS menggunakan hashtags khusus yakni #ObamadiRI and #INAUSA.
"Ini mendorong partisipasi melalui polling di halaman penggemar (fan page) Facebook Kedubes AS," tulis rilis Kedubes.
Bagi pemenang akan mendapat perjalanan yang sangat menarik. Hadiah perjalanan yang disponsori oleh Kedubes AS ini akan mencakup kunjungan ke Hawaii tempat Obama dilahirkan.
Selain itu, pemenang juga akan dibawa ke Chicago tempat Obama memulai karir politiknya, dan Washington, D.C. di mana Obama kini menjadi Presiden AS.
dikutip oleh VIVA news
installation Windows 2000 Server
Step #1: Plan your installation
When you run the Windows 2000 Server Setup program, you must provide information about how to install and configure the operating system. Thorough planning can make your installation of W2K more efficient by helping you to avoid potential problems during installation. An understanding of the configuration options will also help to ensure that you have properly configured your system.
I won't go into that part right now but here are some of the most important things you should take into consideration when planning for your Windows Server 2000 installation:
• Check System Requirements
• Check Hardware and Software Compatibility
• Determine Disk Partitioning Options
• Choose the Appropriate File System: FAT, FAT32, NTFS
• Decide on a Workgroup or Domain Installation
• Complete a Pre-Installation Checklist
After you made sure you can go on, start the installation process.
Step #2: Beginning the installation process
You can install Windows 2000 Server in several methods - all are valid and good, it all depends upon your needs and your limitations.
• Manual installations usually come in 3 flavors:
• Boot from CD - No existing partition is required.
• Boot from the 4 Setup Boot Disks, then insert the CD - No existing partition is required.
• Boot from an MS-DOS startup floppy, go to the command prompt, create a 4GB FAT32 partition with FDISK, reboot, format the C partition you've created, then go to the CD drive, go into the I386 folder, and run the WINNT.EXE command.
• Run an already installed OS, such as Windows NT 4.0 Server. From within NT 4.0 go to the I386 folder in the W2K installation CD and run the WINNT32.EXE command.
• If you want to upgrade a desktop OS such as Windows 98 into Windows 2000 Professional you can follow the same procedure as above (You cannot upgrade Windows 98 into W2K Server).
There are other non-manual installation methods, such as using an unattended file along with a uniqueness database file, using Sysprep, using RIS or even running unattended installations from within the CD itself, but we won't go into that right now.
It doesn't matter how you run the setup process, but the moment it runs - all setup methods look alike.
Step #3: The text-based portion of the Setup program
The setup process begins loading a blue-looking text screen (not GUI). In that phase you will be asked to accept the EULA and choose a partition on which to install W2K, and if that partition is new, you'll be asked to format it by using either FAT, FAT32 or NTFS.
1. Start the computer from the CD.
2. You can press F6 if you need to install additional SCSI adapters or other mass-storage devices. If you do you will be asked to supply a floppy disk with the drivers and you CANNOT browse it (or a CD for that matter). Make sure you have one handy.
3. Setup will load all the needed files and drivers.
4. Select To Setup W2K Now. If you want, and if you have a previous installation of the OS, you can try to fix it by pressing R. If not, just press ENTER.
5. In case your server is a new one, or it is using a new hard disk that hasn't been partitioned yet, you'll get a warning message. Read it, and if you want to continue, press C.
6. Read and accept the licensing agreement and press F8 if you accept it.
7. Select or create the partition on which you will install W2K. Depending upon your existing disk configuration choose one of the following:
• If the hard disk is not yet partitioned, you can create and size the partition on which you will install Windows 2000. Press C.
• If the hard disk is new and you want to create a partition that will span the entire hard disk's size - press Enter.
Other optionsL
• If the hard disk is already partitioned, but has enough unpartitioned disk space, you can create an additional partition in the unpartitioned space.
• If the hard disk already has a partition that is large enough, you can install Windows 2000 on that partition. If the partition has an existing operating system, you will overwrite that operating system if you accept the default installation path. However, files other than the operating system files, such as program files and data files, will not be overwritten.
• If the hard disk has an existing partition, you can delete it to create more unpartitioned space for the new partition. Deleting an existing partition erases all data on that partition.
If you select a new partition during Setup, create and size only the partition on which you will install Windows 2000. After installation, use Disk Management to partition the remaining space on the hard disk.
8. Select a file system for the installation partition. After you create the partition on which you will install W2K, you can use Setup to select the file system with which to format the partition. W2K supports the NTFS file system in addition to the file allocation table (FAT) and FAT32 file systems. Windows Server 2003, Windows XP Professional, Windows 2000, and Windows NT are the only Microsoft operating systems that you can use to gain access to data on a local hard disk that is formatted with NTFS. If you plan to gain access to files that are on a local W2K partition with the Microsoft Windows 95 or Windows 98 operating systems, you should format the partition with a FAT or FAT32 file system. We will use NTFS.
9. Setup will then begin copying necessary files from the installation point (CD, local I386 or network share).
10. Note: If you began the installation process from an MS-DOS floppy, make sure you have and run SMARTDRV from the floppy, otherwise the copying process will probably last more than an hour, perhaps even more. With SMARTDRV (or if setup was run by booting from CD) the copying will probably last a few minutes, no more than 5 max.
11. The computer will restart in graphical mode, and the installation will continue.
Step #4: The GUI-based portion of the Setup program
The setup process reboots and loads a GUI mode phase.
It will then begin to load device drivers based upon what it finds on your computer. You don't need to do anything at this stage.
If your computer stops responding during this phase (the progress bar is stuck almost half-way, and there is no disk activity) - shut down your computer and begin removing hardware such as PCI and ISA cards. If it works for you then later try to figure out how to make that specific piece of hardware work (it's probably not in the HCL).
1. Click Customize to change regional settings, if necessary.
• Current System Locale - Affects how programs display dates, times, currency, and numbers. Choose the locale that matches your location, for example, French (Canada).
• Current Keyboard Layout - Accommodates the special characters and symbols used in different languages. Your keyboard layout determines which characters appear when you press keys on the keyboard.
If you don't need to make any changes just press Next.
If you do need to make changes press Customize and add your System Locale etc.
Note for Hebrew users: In W2K it is NOT SAFE to install Hebrew language support at this phase!!! Trust me, do it later. If you don't listen to me, good chances are that you'll get ???? fonts in some Office applications such as Outlook and others.
Read the Install Hebrew on Windows 2000 page for more info.
2. Type your name and organization.
3. Type the product key.
If you'd like to skip this step in the future, please read Install Windows 2000 Without Supplying the CD Key.
4. Enter the appropriate license type and number of purchased licenses.
5. Type the computer name and a password for the local Administrator account. The local Administrator account resides in the SAM of the computer, not in Active Directory. If you will be installing in a domain, you need either a pre-assigned computer name for which a domain account has been created, or the right to create a computer account within the domain.
6. Choose which components to install or remove from the system.
7. Select the date, time, and time zone settings.
6. Setup will now install the networking components.
After a few seconds you will receive the Networking Settings window. BTW, if you have a NIC that is not in the HCL (see the What's the HCL? page) and W2K cannot detect it, or if you don't have a NIC at all, setup will skip this step and you will immediately go to the final phase of the setup process.
Press Next to accept the Typical settings option if you have one of the following situations:
• You have a functional DHCP on your network.
• You have a computer running Internet Connection Sharing (ICS).
• You're in a workgroup environment and do not plan to have any other servers or Active Directory at all, and all other workgroup members are configured in the same manner.
Otherwise select Custom Settings and press Next to customize your network settings.
7. Highlight the TCP/IP selection and press Properties.
In the General tab enter the required information. You must specify the IP address of the computer, and if you don't know what the Subnet Mask entry should be - you can simply place your mouse pointer over the empty area in the Subnet Mask box and click it. The OS will automatically select the value it thinks is good for the IP address you provided.
Lamer note: In the above screenshot I've configured the computer with a valid IP address for MY network, along with the Default Gateway and the address of MY DNS server. Your settings may differ.
If you don't know what these values mean, or if you don't know what to write in them, press cancel and select the Typical Settings option. You can easily change these values later.
8. In the Workgroup or Domain window enter the name of your workgroup or domain.
• A workgroup is a small group of computers on a network that enables users to work together and does not support centralized administration.
• A domain is a logical grouping of computers on a network that has a central security database for storing security information. Centralized security and administration are important for computers in a domain because they enable an administrator to easily manage computers that are geographically distant from each other. A domain is administered as a unit with common rules and procedures. Each domain has a unique name, and each computer within a domain has a unique name.
If you're a stand-alone computer, or if you don't know what to enter, or if you don't have the sufficient rights to join a domain - leave the default entry selected and press Next.
If you want to join a domain (NT 4.0 domain of W2K/2003 Active Directory domain) enter the domain's name in the "Yes, make this computer a member of the following domain" box.
To successfully join a domain you need the following:
• The person performing the installation must have a user account in Active Directory. This account does not need to be the domain Administrator account.
and
• The computer must have an existing computer account in the Active Directory database of the domain that the computer is joining, and the computer must be named exactly as its domain account is named.
or
• The person performing the installation must have appropriate permission to create a domain account for the computer during installation.
Also, you need to have connectivity to the domain's domain controllers (only to the PDC if on an NT 4.0 domain) and a fully functional DNS server (only in AD domains). Read the Joining a Domain in Windows XP Pro and Requirements when Joining a Domain pages for more on this issue.
Enter the Active Directory domain name (in the form of xxx.yyy, for example: DPETRI.NET) or the NetBIOS name of the NT 4.0 domain (in the form of xxx, for example: DPETRI). Press Next.
Note: If you provide a wrong domain name or do not have the correct connectivity to the domain's DNS server you will get an error message.
A username/password window will appear. Enter the name and password of the domain's administrator (or your own if you're the administrator on the target domain).
Note: Providing a wrong username or password will cause this phase to fail.
9. Next the setup process will finish copying files and configuring the setup. You do not need to do anything.
10. After the copying and configuring phase is finished, if Windows Server 2003 finds that you have a badly configured screen resolution it will advise you to change it and ask you if you see the new settings right.
11. Setup finishes and displays the finish window. Unfortunately, you must press Finish in order to reboot..
12. Windows 2000 reboots and you should get the CTRL-ALT-DEL window.
13. That's it! you're done!
When you run the Windows 2000 Server Setup program, you must provide information about how to install and configure the operating system. Thorough planning can make your installation of W2K more efficient by helping you to avoid potential problems during installation. An understanding of the configuration options will also help to ensure that you have properly configured your system.
I won't go into that part right now but here are some of the most important things you should take into consideration when planning for your Windows Server 2000 installation:
• Check System Requirements
• Check Hardware and Software Compatibility
• Determine Disk Partitioning Options
• Choose the Appropriate File System: FAT, FAT32, NTFS
• Decide on a Workgroup or Domain Installation
• Complete a Pre-Installation Checklist
After you made sure you can go on, start the installation process.
Step #2: Beginning the installation process
You can install Windows 2000 Server in several methods - all are valid and good, it all depends upon your needs and your limitations.
• Manual installations usually come in 3 flavors:
• Boot from CD - No existing partition is required.
• Boot from the 4 Setup Boot Disks, then insert the CD - No existing partition is required.
• Boot from an MS-DOS startup floppy, go to the command prompt, create a 4GB FAT32 partition with FDISK, reboot, format the C partition you've created, then go to the CD drive, go into the I386 folder, and run the WINNT.EXE command.
• Run an already installed OS, such as Windows NT 4.0 Server. From within NT 4.0 go to the I386 folder in the W2K installation CD and run the WINNT32.EXE command.
• If you want to upgrade a desktop OS such as Windows 98 into Windows 2000 Professional you can follow the same procedure as above (You cannot upgrade Windows 98 into W2K Server).
There are other non-manual installation methods, such as using an unattended file along with a uniqueness database file, using Sysprep, using RIS or even running unattended installations from within the CD itself, but we won't go into that right now.
It doesn't matter how you run the setup process, but the moment it runs - all setup methods look alike.
Step #3: The text-based portion of the Setup program
The setup process begins loading a blue-looking text screen (not GUI). In that phase you will be asked to accept the EULA and choose a partition on which to install W2K, and if that partition is new, you'll be asked to format it by using either FAT, FAT32 or NTFS.
1. Start the computer from the CD.
2. You can press F6 if you need to install additional SCSI adapters or other mass-storage devices. If you do you will be asked to supply a floppy disk with the drivers and you CANNOT browse it (or a CD for that matter). Make sure you have one handy.
3. Setup will load all the needed files and drivers.
4. Select To Setup W2K Now. If you want, and if you have a previous installation of the OS, you can try to fix it by pressing R. If not, just press ENTER.
5. In case your server is a new one, or it is using a new hard disk that hasn't been partitioned yet, you'll get a warning message. Read it, and if you want to continue, press C.
6. Read and accept the licensing agreement and press F8 if you accept it.
7. Select or create the partition on which you will install W2K. Depending upon your existing disk configuration choose one of the following:
• If the hard disk is not yet partitioned, you can create and size the partition on which you will install Windows 2000. Press C.
• If the hard disk is new and you want to create a partition that will span the entire hard disk's size - press Enter.
Other optionsL
• If the hard disk is already partitioned, but has enough unpartitioned disk space, you can create an additional partition in the unpartitioned space.
• If the hard disk already has a partition that is large enough, you can install Windows 2000 on that partition. If the partition has an existing operating system, you will overwrite that operating system if you accept the default installation path. However, files other than the operating system files, such as program files and data files, will not be overwritten.
• If the hard disk has an existing partition, you can delete it to create more unpartitioned space for the new partition. Deleting an existing partition erases all data on that partition.
If you select a new partition during Setup, create and size only the partition on which you will install Windows 2000. After installation, use Disk Management to partition the remaining space on the hard disk.
8. Select a file system for the installation partition. After you create the partition on which you will install W2K, you can use Setup to select the file system with which to format the partition. W2K supports the NTFS file system in addition to the file allocation table (FAT) and FAT32 file systems. Windows Server 2003, Windows XP Professional, Windows 2000, and Windows NT are the only Microsoft operating systems that you can use to gain access to data on a local hard disk that is formatted with NTFS. If you plan to gain access to files that are on a local W2K partition with the Microsoft Windows 95 or Windows 98 operating systems, you should format the partition with a FAT or FAT32 file system. We will use NTFS.
9. Setup will then begin copying necessary files from the installation point (CD, local I386 or network share).
10. Note: If you began the installation process from an MS-DOS floppy, make sure you have and run SMARTDRV from the floppy, otherwise the copying process will probably last more than an hour, perhaps even more. With SMARTDRV (or if setup was run by booting from CD) the copying will probably last a few minutes, no more than 5 max.
11. The computer will restart in graphical mode, and the installation will continue.
Step #4: The GUI-based portion of the Setup program
The setup process reboots and loads a GUI mode phase.
It will then begin to load device drivers based upon what it finds on your computer. You don't need to do anything at this stage.
If your computer stops responding during this phase (the progress bar is stuck almost half-way, and there is no disk activity) - shut down your computer and begin removing hardware such as PCI and ISA cards. If it works for you then later try to figure out how to make that specific piece of hardware work (it's probably not in the HCL).
1. Click Customize to change regional settings, if necessary.
• Current System Locale - Affects how programs display dates, times, currency, and numbers. Choose the locale that matches your location, for example, French (Canada).
• Current Keyboard Layout - Accommodates the special characters and symbols used in different languages. Your keyboard layout determines which characters appear when you press keys on the keyboard.
If you don't need to make any changes just press Next.
If you do need to make changes press Customize and add your System Locale etc.
Note for Hebrew users: In W2K it is NOT SAFE to install Hebrew language support at this phase!!! Trust me, do it later. If you don't listen to me, good chances are that you'll get ???? fonts in some Office applications such as Outlook and others.
Read the Install Hebrew on Windows 2000 page for more info.
2. Type your name and organization.
3. Type the product key.
If you'd like to skip this step in the future, please read Install Windows 2000 Without Supplying the CD Key.
4. Enter the appropriate license type and number of purchased licenses.
5. Type the computer name and a password for the local Administrator account. The local Administrator account resides in the SAM of the computer, not in Active Directory. If you will be installing in a domain, you need either a pre-assigned computer name for which a domain account has been created, or the right to create a computer account within the domain.
6. Choose which components to install or remove from the system.
7. Select the date, time, and time zone settings.
6. Setup will now install the networking components.
After a few seconds you will receive the Networking Settings window. BTW, if you have a NIC that is not in the HCL (see the What's the HCL? page) and W2K cannot detect it, or if you don't have a NIC at all, setup will skip this step and you will immediately go to the final phase of the setup process.
Press Next to accept the Typical settings option if you have one of the following situations:
• You have a functional DHCP on your network.
• You have a computer running Internet Connection Sharing (ICS).
• You're in a workgroup environment and do not plan to have any other servers or Active Directory at all, and all other workgroup members are configured in the same manner.
Otherwise select Custom Settings and press Next to customize your network settings.
7. Highlight the TCP/IP selection and press Properties.
In the General tab enter the required information. You must specify the IP address of the computer, and if you don't know what the Subnet Mask entry should be - you can simply place your mouse pointer over the empty area in the Subnet Mask box and click it. The OS will automatically select the value it thinks is good for the IP address you provided.
Lamer note: In the above screenshot I've configured the computer with a valid IP address for MY network, along with the Default Gateway and the address of MY DNS server. Your settings may differ.
If you don't know what these values mean, or if you don't know what to write in them, press cancel and select the Typical Settings option. You can easily change these values later.
8. In the Workgroup or Domain window enter the name of your workgroup or domain.
• A workgroup is a small group of computers on a network that enables users to work together and does not support centralized administration.
• A domain is a logical grouping of computers on a network that has a central security database for storing security information. Centralized security and administration are important for computers in a domain because they enable an administrator to easily manage computers that are geographically distant from each other. A domain is administered as a unit with common rules and procedures. Each domain has a unique name, and each computer within a domain has a unique name.
If you're a stand-alone computer, or if you don't know what to enter, or if you don't have the sufficient rights to join a domain - leave the default entry selected and press Next.
If you want to join a domain (NT 4.0 domain of W2K/2003 Active Directory domain) enter the domain's name in the "Yes, make this computer a member of the following domain" box.
To successfully join a domain you need the following:
• The person performing the installation must have a user account in Active Directory. This account does not need to be the domain Administrator account.
and
• The computer must have an existing computer account in the Active Directory database of the domain that the computer is joining, and the computer must be named exactly as its domain account is named.
or
• The person performing the installation must have appropriate permission to create a domain account for the computer during installation.
Also, you need to have connectivity to the domain's domain controllers (only to the PDC if on an NT 4.0 domain) and a fully functional DNS server (only in AD domains). Read the Joining a Domain in Windows XP Pro and Requirements when Joining a Domain pages for more on this issue.
Enter the Active Directory domain name (in the form of xxx.yyy, for example: DPETRI.NET) or the NetBIOS name of the NT 4.0 domain (in the form of xxx, for example: DPETRI). Press Next.
Note: If you provide a wrong domain name or do not have the correct connectivity to the domain's DNS server you will get an error message.
A username/password window will appear. Enter the name and password of the domain's administrator (or your own if you're the administrator on the target domain).
Note: Providing a wrong username or password will cause this phase to fail.
9. Next the setup process will finish copying files and configuring the setup. You do not need to do anything.
10. After the copying and configuring phase is finished, if Windows Server 2003 finds that you have a badly configured screen resolution it will advise you to change it and ask you if you see the new settings right.
11. Setup finishes and displays the finish window. Unfortunately, you must press Finish in order to reboot..
12. Windows 2000 reboots and you should get the CTRL-ALT-DEL window.
13. That's it! you're done!
Step #1: Plan your installation
When you run the Windows 2000 Server Setup program, you must provide information about how to install and configure the operating system. Thorough planning can make your installation of W2K more efficient by helping you to avoid potential problems during installation. An understanding of the configuration options will also help to ensure that you have properly configured your system.
I won't go into that part right now but here are some of the most important things you should take into consideration when planning for your Windows Server 2000 installation:
• Check System Requirements
• Check Hardware and Software Compatibility
• Determine Disk Partitioning Options
• Choose the Appropriate File System: FAT, FAT32, NTFS
• Decide on a Workgroup or Domain Installation
• Complete a Pre-Installation Checklist
After you made sure you can go on, start the installation process.
Step #2: Beginning the installation process
You can install Windows 2000 Server in several methods - all are valid and good, it all depends upon your needs and your limitations.
• Manual installations usually come in 3 flavors:
• Boot from CD - No existing partition is required.
• Boot from the 4 Setup Boot Disks, then insert the CD - No existing partition is required.
• Boot from an MS-DOS startup floppy, go to the command prompt, create a 4GB FAT32 partition with FDISK, reboot, format the C partition you've created, then go to the CD drive, go into the I386 folder, and run the WINNT.EXE command.
• Run an already installed OS, such as Windows NT 4.0 Server. From within NT 4.0 go to the I386 folder in the W2K installation CD and run the WINNT32.EXE command.
• If you want to upgrade a desktop OS such as Windows 98 into Windows 2000 Professional you can follow the same procedure as above (You cannot upgrade Windows 98 into W2K Server).
There are other non-manual installation methods, such as using an unattended file along with a uniqueness database file, using Sysprep, using RIS or even running unattended installations from within the CD itself, but we won't go into that right now.
It doesn't matter how you run the setup process, but the moment it runs - all setup methods look alike.
Step #3: The text-based portion of the Setup program
The setup process begins loading a blue-looking text screen (not GUI). In that phase you will be asked to accept the EULA and choose a partition on which to install W2K, and if that partition is new, you'll be asked to format it by using either FAT, FAT32 or NTFS.
1. Start the computer from the CD.
2. You can press F6 if you need to install additional SCSI adapters or other mass-storage devices. If you do you will be asked to supply a floppy disk with the drivers and you CANNOT browse it (or a CD for that matter). Make sure you have one handy.
3. Setup will load all the needed files and drivers.
4. Select To Setup W2K Now. If you want, and if you have a previous installation of the OS, you can try to fix it by pressing R. If not, just press ENTER.
5. In case your server is a new one, or it is using a new hard disk that hasn't been partitioned yet, you'll get a warning message. Read it, and if you want to continue, press C.
6. Read and accept the licensing agreement and press F8 if you accept it.
7. Select or create the partition on which you will install W2K. Depending upon your existing disk configuration choose one of the following:
• If the hard disk is not yet partitioned, you can create and size the partition on which you will install Windows 2000. Press C.
• If the hard disk is new and you want to create a partition that will span the entire hard disk's size - press Enter.
Other optionsL
• If the hard disk is already partitioned, but has enough unpartitioned disk space, you can create an additional partition in the unpartitioned space.
• If the hard disk already has a partition that is large enough, you can install Windows 2000 on that partition. If the partition has an existing operating system, you will overwrite that operating system if you accept the default installation path. However, files other than the operating system files, such as program files and data files, will not be overwritten.
• If the hard disk has an existing partition, you can delete it to create more unpartitioned space for the new partition. Deleting an existing partition erases all data on that partition.
If you select a new partition during Setup, create and size only the partition on which you will install Windows 2000. After installation, use Disk Management to partition the remaining space on the hard disk.
8. Select a file system for the installation partition. After you create the partition on which you will install W2K, you can use Setup to select the file system with which to format the partition. W2K supports the NTFS file system in addition to the file allocation table (FAT) and FAT32 file systems. Windows Server 2003, Windows XP Professional, Windows 2000, and Windows NT are the only Microsoft operating systems that you can use to gain access to data on a local hard disk that is formatted with NTFS. If you plan to gain access to files that are on a local W2K partition with the Microsoft Windows 95 or Windows 98 operating systems, you should format the partition with a FAT or FAT32 file system. We will use NTFS.
9. Setup will then begin copying necessary files from the installation point (CD, local I386 or network share).
10. Note: If you began the installation process from an MS-DOS floppy, make sure you have and run SMARTDRV from the floppy, otherwise the copying process will probably last more than an hour, perhaps even more. With SMARTDRV (or if setup was run by booting from CD) the copying will probably last a few minutes, no more than 5 max.
11. The computer will restart in graphical mode, and the installation will continue.
Step #4: The GUI-based portion of the Setup program
The setup process reboots and loads a GUI mode phase.
It will then begin to load device drivers based upon what it finds on your computer. You don't need to do anything at this stage.
If your computer stops responding during this phase (the progress bar is stuck almost half-way, and there is no disk activity) - shut down your computer and begin removing hardware such as PCI and ISA cards. If it works for you then later try to figure out how to make that specific piece of hardware work (it's probably not in the HCL).
1. Click Customize to change regional settings, if necessary.
• Current System Locale - Affects how programs display dates, times, currency, and numbers. Choose the locale that matches your location, for example, French (Canada).
• Current Keyboard Layout - Accommodates the special characters and symbols used in different languages. Your keyboard layout determines which characters appear when you press keys on the keyboard.
If you don't need to make any changes just press Next.
If you do need to make changes press Customize and add your System Locale etc.
Note for Hebrew users: In W2K it is NOT SAFE to install Hebrew language support at this phase!!! Trust me, do it later. If you don't listen to me, good chances are that you'll get ???? fonts in some Office applications such as Outlook and others.
Read the Install Hebrew on Windows 2000 page for more info.
2. Type your name and organization.
3. Type the product key.
If you'd like to skip this step in the future, please read Install Windows 2000 Without Supplying the CD Key.
4. Enter the appropriate license type and number of purchased licenses.
5. Type the computer name and a password for the local Administrator account. The local Administrator account resides in the SAM of the computer, not in Active Directory. If you will be installing in a domain, you need either a pre-assigned computer name for which a domain account has been created, or the right to create a computer account within the domain.
6. Choose which components to install or remove from the system.
7. Select the date, time, and time zone settings.
6. Setup will now install the networking components.
After a few seconds you will receive the Networking Settings window. BTW, if you have a NIC that is not in the HCL (see the What's the HCL? page) and W2K cannot detect it, or if you don't have a NIC at all, setup will skip this step and you will immediately go to the final phase of the setup process.
Press Next to accept the Typical settings option if you have one of the following situations:
• You have a functional DHCP on your network.
• You have a computer running Internet Connection Sharing (ICS).
• You're in a workgroup environment and do not plan to have any other servers or Active Directory at all, and all other workgroup members are configured in the same manner.
Otherwise select Custom Settings and press Next to customize your network settings.
7. Highlight the TCP/IP selection and press Properties.
In the General tab enter the required information. You must specify the IP address of the computer, and if you don't know what the Subnet Mask entry should be - you can simply place your mouse pointer over the empty area in the Subnet Mask box and click it. The OS will automatically select the value it thinks is good for the IP address you provided.
Lamer note: In the above screenshot I've configured the computer with a valid IP address for MY network, along with the Default Gateway and the address of MY DNS server. Your settings may differ.
If you don't know what these values mean, or if you don't know what to write in them, press cancel and select the Typical Settings option. You can easily change these values later.
8. In the Workgroup or Domain window enter the name of your workgroup or domain.
• A workgroup is a small group of computers on a network that enables users to work together and does not support centralized administration.
• A domain is a logical grouping of computers on a network that has a central security database for storing security information. Centralized security and administration are important for computers in a domain because they enable an administrator to easily manage computers that are geographically distant from each other. A domain is administered as a unit with common rules and procedures. Each domain has a unique name, and each computer within a domain has a unique name.
If you're a stand-alone computer, or if you don't know what to enter, or if you don't have the sufficient rights to join a domain - leave the default entry selected and press Next.
If you want to join a domain (NT 4.0 domain of W2K/2003 Active Directory domain) enter the domain's name in the "Yes, make this computer a member of the following domain" box.
To successfully join a domain you need the following:
• The person performing the installation must have a user account in Active Directory. This account does not need to be the domain Administrator account.
and
• The computer must have an existing computer account in the Active Directory database of the domain that the computer is joining, and the computer must be named exactly as its domain account is named.
or
• The person performing the installation must have appropriate permission to create a domain account for the computer during installation.
Also, you need to have connectivity to the domain's domain controllers (only to the PDC if on an NT 4.0 domain) and a fully functional DNS server (only in AD domains). Read the Joining a Domain in Windows XP Pro and Requirements when Joining a Domain pages for more on this issue.
Enter the Active Directory domain name (in the form of xxx.yyy, for example: DPETRI.NET) or the NetBIOS name of the NT 4.0 domain (in the form of xxx, for example: DPETRI). Press Next.
Note: If you provide a wrong domain name or do not have the correct connectivity to the domain's DNS server you will get an error message.
A username/password window will appear. Enter the name and password of the domain's administrator (or your own if you're the administrator on the target domain).
Note: Providing a wrong username or password will cause this phase to fail.
9. Next the setup process will finish copying files and configuring the setup. You do not need to do anything.
10. After the copying and configuring phase is finished, if Windows Server 2003 finds that you have a badly configured screen resolution it will advise you to change it and ask you if you see the new settings right.
11. Setup finishes and displays the finish window. Unfortunately, you must press Finish in order to reboot..
12. Windows 2000 reboots and you should get the CTRL-ALT-DEL window.
13. That's it! you're done!
When you run the Windows 2000 Server Setup program, you must provide information about how to install and configure the operating system. Thorough planning can make your installation of W2K more efficient by helping you to avoid potential problems during installation. An understanding of the configuration options will also help to ensure that you have properly configured your system.
I won't go into that part right now but here are some of the most important things you should take into consideration when planning for your Windows Server 2000 installation:
• Check System Requirements
• Check Hardware and Software Compatibility
• Determine Disk Partitioning Options
• Choose the Appropriate File System: FAT, FAT32, NTFS
• Decide on a Workgroup or Domain Installation
• Complete a Pre-Installation Checklist
After you made sure you can go on, start the installation process.
Step #2: Beginning the installation process
You can install Windows 2000 Server in several methods - all are valid and good, it all depends upon your needs and your limitations.
• Manual installations usually come in 3 flavors:
• Boot from CD - No existing partition is required.
• Boot from the 4 Setup Boot Disks, then insert the CD - No existing partition is required.
• Boot from an MS-DOS startup floppy, go to the command prompt, create a 4GB FAT32 partition with FDISK, reboot, format the C partition you've created, then go to the CD drive, go into the I386 folder, and run the WINNT.EXE command.
• Run an already installed OS, such as Windows NT 4.0 Server. From within NT 4.0 go to the I386 folder in the W2K installation CD and run the WINNT32.EXE command.
• If you want to upgrade a desktop OS such as Windows 98 into Windows 2000 Professional you can follow the same procedure as above (You cannot upgrade Windows 98 into W2K Server).
There are other non-manual installation methods, such as using an unattended file along with a uniqueness database file, using Sysprep, using RIS or even running unattended installations from within the CD itself, but we won't go into that right now.
It doesn't matter how you run the setup process, but the moment it runs - all setup methods look alike.
Step #3: The text-based portion of the Setup program
The setup process begins loading a blue-looking text screen (not GUI). In that phase you will be asked to accept the EULA and choose a partition on which to install W2K, and if that partition is new, you'll be asked to format it by using either FAT, FAT32 or NTFS.
1. Start the computer from the CD.
2. You can press F6 if you need to install additional SCSI adapters or other mass-storage devices. If you do you will be asked to supply a floppy disk with the drivers and you CANNOT browse it (or a CD for that matter). Make sure you have one handy.
3. Setup will load all the needed files and drivers.
4. Select To Setup W2K Now. If you want, and if you have a previous installation of the OS, you can try to fix it by pressing R. If not, just press ENTER.
5. In case your server is a new one, or it is using a new hard disk that hasn't been partitioned yet, you'll get a warning message. Read it, and if you want to continue, press C.
6. Read and accept the licensing agreement and press F8 if you accept it.
7. Select or create the partition on which you will install W2K. Depending upon your existing disk configuration choose one of the following:
• If the hard disk is not yet partitioned, you can create and size the partition on which you will install Windows 2000. Press C.
• If the hard disk is new and you want to create a partition that will span the entire hard disk's size - press Enter.
Other optionsL
• If the hard disk is already partitioned, but has enough unpartitioned disk space, you can create an additional partition in the unpartitioned space.
• If the hard disk already has a partition that is large enough, you can install Windows 2000 on that partition. If the partition has an existing operating system, you will overwrite that operating system if you accept the default installation path. However, files other than the operating system files, such as program files and data files, will not be overwritten.
• If the hard disk has an existing partition, you can delete it to create more unpartitioned space for the new partition. Deleting an existing partition erases all data on that partition.
If you select a new partition during Setup, create and size only the partition on which you will install Windows 2000. After installation, use Disk Management to partition the remaining space on the hard disk.
8. Select a file system for the installation partition. After you create the partition on which you will install W2K, you can use Setup to select the file system with which to format the partition. W2K supports the NTFS file system in addition to the file allocation table (FAT) and FAT32 file systems. Windows Server 2003, Windows XP Professional, Windows 2000, and Windows NT are the only Microsoft operating systems that you can use to gain access to data on a local hard disk that is formatted with NTFS. If you plan to gain access to files that are on a local W2K partition with the Microsoft Windows 95 or Windows 98 operating systems, you should format the partition with a FAT or FAT32 file system. We will use NTFS.
9. Setup will then begin copying necessary files from the installation point (CD, local I386 or network share).
10. Note: If you began the installation process from an MS-DOS floppy, make sure you have and run SMARTDRV from the floppy, otherwise the copying process will probably last more than an hour, perhaps even more. With SMARTDRV (or if setup was run by booting from CD) the copying will probably last a few minutes, no more than 5 max.
11. The computer will restart in graphical mode, and the installation will continue.
Step #4: The GUI-based portion of the Setup program
The setup process reboots and loads a GUI mode phase.
It will then begin to load device drivers based upon what it finds on your computer. You don't need to do anything at this stage.
If your computer stops responding during this phase (the progress bar is stuck almost half-way, and there is no disk activity) - shut down your computer and begin removing hardware such as PCI and ISA cards. If it works for you then later try to figure out how to make that specific piece of hardware work (it's probably not in the HCL).
1. Click Customize to change regional settings, if necessary.
• Current System Locale - Affects how programs display dates, times, currency, and numbers. Choose the locale that matches your location, for example, French (Canada).
• Current Keyboard Layout - Accommodates the special characters and symbols used in different languages. Your keyboard layout determines which characters appear when you press keys on the keyboard.
If you don't need to make any changes just press Next.
If you do need to make changes press Customize and add your System Locale etc.
Note for Hebrew users: In W2K it is NOT SAFE to install Hebrew language support at this phase!!! Trust me, do it later. If you don't listen to me, good chances are that you'll get ???? fonts in some Office applications such as Outlook and others.
Read the Install Hebrew on Windows 2000 page for more info.
2. Type your name and organization.
3. Type the product key.
If you'd like to skip this step in the future, please read Install Windows 2000 Without Supplying the CD Key.
4. Enter the appropriate license type and number of purchased licenses.
5. Type the computer name and a password for the local Administrator account. The local Administrator account resides in the SAM of the computer, not in Active Directory. If you will be installing in a domain, you need either a pre-assigned computer name for which a domain account has been created, or the right to create a computer account within the domain.
6. Choose which components to install or remove from the system.
7. Select the date, time, and time zone settings.
6. Setup will now install the networking components.
After a few seconds you will receive the Networking Settings window. BTW, if you have a NIC that is not in the HCL (see the What's the HCL? page) and W2K cannot detect it, or if you don't have a NIC at all, setup will skip this step and you will immediately go to the final phase of the setup process.
Press Next to accept the Typical settings option if you have one of the following situations:
• You have a functional DHCP on your network.
• You have a computer running Internet Connection Sharing (ICS).
• You're in a workgroup environment and do not plan to have any other servers or Active Directory at all, and all other workgroup members are configured in the same manner.
Otherwise select Custom Settings and press Next to customize your network settings.
7. Highlight the TCP/IP selection and press Properties.
In the General tab enter the required information. You must specify the IP address of the computer, and if you don't know what the Subnet Mask entry should be - you can simply place your mouse pointer over the empty area in the Subnet Mask box and click it. The OS will automatically select the value it thinks is good for the IP address you provided.
Lamer note: In the above screenshot I've configured the computer with a valid IP address for MY network, along with the Default Gateway and the address of MY DNS server. Your settings may differ.
If you don't know what these values mean, or if you don't know what to write in them, press cancel and select the Typical Settings option. You can easily change these values later.
8. In the Workgroup or Domain window enter the name of your workgroup or domain.
• A workgroup is a small group of computers on a network that enables users to work together and does not support centralized administration.
• A domain is a logical grouping of computers on a network that has a central security database for storing security information. Centralized security and administration are important for computers in a domain because they enable an administrator to easily manage computers that are geographically distant from each other. A domain is administered as a unit with common rules and procedures. Each domain has a unique name, and each computer within a domain has a unique name.
If you're a stand-alone computer, or if you don't know what to enter, or if you don't have the sufficient rights to join a domain - leave the default entry selected and press Next.
If you want to join a domain (NT 4.0 domain of W2K/2003 Active Directory domain) enter the domain's name in the "Yes, make this computer a member of the following domain" box.
To successfully join a domain you need the following:
• The person performing the installation must have a user account in Active Directory. This account does not need to be the domain Administrator account.
and
• The computer must have an existing computer account in the Active Directory database of the domain that the computer is joining, and the computer must be named exactly as its domain account is named.
or
• The person performing the installation must have appropriate permission to create a domain account for the computer during installation.
Also, you need to have connectivity to the domain's domain controllers (only to the PDC if on an NT 4.0 domain) and a fully functional DNS server (only in AD domains). Read the Joining a Domain in Windows XP Pro and Requirements when Joining a Domain pages for more on this issue.
Enter the Active Directory domain name (in the form of xxx.yyy, for example: DPETRI.NET) or the NetBIOS name of the NT 4.0 domain (in the form of xxx, for example: DPETRI). Press Next.
Note: If you provide a wrong domain name or do not have the correct connectivity to the domain's DNS server you will get an error message.
A username/password window will appear. Enter the name and password of the domain's administrator (or your own if you're the administrator on the target domain).
Note: Providing a wrong username or password will cause this phase to fail.
9. Next the setup process will finish copying files and configuring the setup. You do not need to do anything.
10. After the copying and configuring phase is finished, if Windows Server 2003 finds that you have a badly configured screen resolution it will advise you to change it and ask you if you see the new settings right.
11. Setup finishes and displays the finish window. Unfortunately, you must press Finish in order to reboot..
12. Windows 2000 reboots and you should get the CTRL-ALT-DEL window.
13. That's it! you're done!
Installing Terminal Services Instalasi Terminal Services
There are three components necessary to understand when you are installing and enabling the Windows 2000 Terminal Services. Ada tiga komponen yang diperlukan untuk memahami ketika anda menginstal dan memungkinkan Windows 2000 Terminal Services. The following list briefly describes these components: Daftar berikut ini menjelaskan secara singkat komponen-komponen ini:
• Server - The computer in which nearly all of the computing resources reside that will be used in the Terminal Services networking environment. Server - komputer di mana hampir semua sumber daya komputasi tinggal yang akan digunakan dalam lingkungan jaringan Terminal Services. The server will receive and process the keystrokes and mouse movements that take place at the client computer. Server akan menerima dan memproses penekanan tombol dan gerakan mouse yang terjadi pada komputer klien. The server displays the desktop and running applications within a window on the client computer. Menampilkan server desktop dan menjalankan aplikasi dalam sebuah jendela pada komputer klien.
• Messaging - This communication occurs between the server and clients by way of the Remote Desktop Protocol (RDP). Pesan - Komunikasi ini terjadi antara server dan klien dengan cara Remote Desktop Protocol (RDP). RDP is an application-layer protocol that relies on TCP/IP. RDP adalah sebuah protokol layer aplikasi yang mengandalkan pada TCP / IP.
• Clients - The computer on the network from which it is possible to open a window containing a terminal session. Klien - komputer di jaringan yang dimungkinkan untuk membuka jendela yang berisi sesi terminal. In this window is the remote desktop running on the server. Dalam jendela ini adalah remote desktop yang berjalan pada server. Applications and windows that are opened on this desktop are actually running on the server. Aplikasi dan jendela-jendela yang sedang dibuka di desktop ini benar-benar berjalan di server.
Enabling Terminal Services in Application Server Mode Mengaktifkan Terminal Services di Application Server Mode
To enable Terminal Services in Application Server mode on the domain controller, the information technology (IT) administrator logs on to server as the administrator and performs the following procedures. Untuk mengaktifkan Terminal Services Application Server dalam modus pada domain controller, teknologi informasi (TI) administrator log on ke server sebagai administrator dan melakukan prosedur berikut.
To enable Terminal Services: Untuk mengaktifkan Terminal Services:
1. Click Start , point to Settings , click Control Panel , and then double-click Add/Remove Programs . Klik Mulai, arahkan ke Pengaturan, klik Panel Kontrol, kemudian klik dua kali Add / Remove Programs.
2. Click Add/Remove Windows Components to start the Windows Components Wizard. Klik Add / Remove Windows Components untuk memulai Windows Components Wizard. In the Components list, to add or remove a component, click to select a check box. A shaded box indicates that only part of the component will be installed. Select the Terminal Services check box, and then click Next . Pada daftar Komponen, untuk menambah atau menghapus komponen, klik untuk memilih kotak centang. Sebuah kotak berbayang menunjukkan bahwa hanya sebagian dari komponen akan diinstal. Pilih kotak centang Terminal Services, kemudian klik Next.
3. In the Windows Components Wizard with Terminal Services selected, click Details to see what is included in the component. Dalam Windows Components Wizard dengan Terminal Services yang dipilih, klik Rincian untuk melihat apa yang termasuk dalam komponen. You will see the two following sub-components: Anda akan melihat dua sub-komponen berikut:
o Client Creator Files - Enables the creation of installation floppy disks for Terminal Services Client computers. Klien Pencipta File - Memungkinkan penciptaan disket instalasi Terminal Services Client untuk komputer.
o Enable Terminal Services - Enables the Terminal Services software on your computer. Aktifkan Terminal Services - Terminal Services Mengaktifkan perangkat lunak pada komputer Anda.
4. Click Next to continue. Klik Next untuk melanjutkan.
5. On the next screen, you are prompted to install Terminal Services to run in one of two modes: Pada layar berikutnya, Anda akan diminta untuk menginstal Terminal Services untuk berjalan dalam salah satu dari dua mode:
o Remote Administration - This mode permits two Terminal Services client connections to the server. Remote Administration - Mode ini memungkinkan dua klien Layanan Terminal koneksi ke server. This mode does not require licensing, but allows only members of the Administrators group to access the server. Modus ini tidak memerlukan lisensi, tapi hanya memungkinkan anggota grup Administrators untuk mengakses server. This is an excellent choice for non-Terminal Services servers, to enable remote control-type access to remote servers. Ini adalah pilihan yang sangat baik untuk non-Terminal Services server, untuk mengaktifkan remote control-tipe akses ke server remote.
o Application Server - This mode permits more than two simultaneous connections by non-administrators, but requires the Terminal Services Licensing service to be installed on a domain controller (for which you can use any server in a workgroup environment). Application Server - Mode ini memungkinkan lebih dari dua koneksi simultan oleh non-administrator, tapi membutuhkan layanan Terminal Services Licensing yang harus diinstal pada kontroler domain (dimana Anda dapat menggunakan server dalam lingkungan workgroup). A Terminal Services Client Access License is also required for non-Windows 2000 Professional clients. Sebuah Terminal Services Client Access License juga diperlukan untuk non-Windows 2000 Professional klien.
NOTE: Terminal Services Licensing is a required component that licenses clients on a Terminal server in Application Server mode. For computers that are in a Windows 2000 domain, Microsoft recommends that you do not enable Terminal Services Licensing on the same computer with Terminal Services. CATATAN: Terminal Services Licensing adalah komponen yang diperlukan lisensi klien pada server di Terminal modus Application Server. Untuk komputer yang ada di Windows 2000 domain, Microsoft menyarankan anda tidak mengaktifkan Terminal Services Licensing pada komputer yang sama dengan Terminal Services.
6. In Terminal Services Setup, verify that Application Server mode is selected, and then click Next . Dalam Terminal Services Setup, memverifikasi bahwa Application Server mode dipilih, dan kemudian klik Next.
NOTE : In Terminal Services Setup, you may see programs listed that will not work properly when Terminal Services is enabled. CATATAN: Dalam Terminal Services Setup, Anda dapat melihat daftar program yang tidak akan bekerja dengan baik bila diaktifkan Terminal Services. You need to reinstall these programs for multisession access by using the Add/Remove Programs tool after you enable Terminal Services. Anda perlu menginstal ulang program-program ini untuk Multisession akses dengan menggunakan Add / Remove Programs alat setelah Anda mengaktifkan Terminal Services.
7. In the next screen, click the appropriate option to specify whether you want permissions to be compatible with Windows 2000 Users or with Terminal Server 4.0 Users . Pada layar berikutnya, klik pilihan yang sesuai untuk menentukan apakah Anda ingin izin agar kompatibel dengan Windows 2000 Pengguna atau dengan Terminal Server 4,0 Pengguna. Use the Permissions compatible with Windows 2000 Users option for the most secure environment in which to run applications. Gunakan Permissions kompatibel dengan Windows 2000 User pilihan untuk lingkungan yang paling aman di mana untuk menjalankan aplikasi.
8. In Terminal Services Licensing Setup, specify whether you want the license server to serve your entire enterprise or your domain/workgroup, and then provide the directory location for the database. Wait for the installation to finish, and then click Finish . Dalam Terminal Services Licensing Setup, tentukan apakah Anda ingin agar server lisensi untuk melayani seluruh perusahaan atau domain / workgroup, dan kemudian memberikan lokasi direktori untuk menyimpan database. Tunggu sampai instalasi selesai, dan kemudian klik Selesai. In the Add/Remove Programs window, click Close . Dalam Add / Remove Programs jendela, klik Tutup.
NOTE : The required files are copied to your hard disk, and you can use server software after you restart the computer. CATATAN: file yang dibutuhkan akan disalin ke hard disk, dan Anda dapat menggunakan perangkat lunak server setelah Anda me-restart komputer.
Troubleshooting Troubleshooting
1. If an application is not working properly, it may be due to one of the following reasons: Jika aplikasi tidak berfungsi sebagaimana mestinya, hal itu mungkin karena salah satu alasan berikut:
o Applications that lock files or DLLs may not run properly because there is the possibility that more than one user will try to use the application at the same time. Aplikasi yang mengunci file atau DLL mungkin tidak berjalan semestinya karena ada kemungkinan bahwa lebih dari satu pengguna akan mencoba untuk menggunakan aplikasi pada waktu yang sama.
o Applications that use the computer name or IP address for identification may have trouble if more than one user at a time attempts to run the application. Aplikasi yang menggunakan nama komputer atau alamat IP untuk identifikasi mungkin mengalami masalah jika lebih dari satu pengguna pada suatu waktu mencoba untuk menjalankan aplikasi.
2. The e-mail address that you provided is not valid; Verify that the e-mail address is valid. E-mail yang Anda berikan tidak valid; Buktikan bahwa alamat e-mail valid.
REFERENCES REFERENSI
For additional information about how to activate a license server, click the ar...
For additional information about how to activate a license server, click the article number below to view the article in the Microsoft Knowledge Base: Untuk informasi tambahan tentang cara mengaktifkan server lisensi, klik nomor artikel di bawah ini untuk melihat artikel pada Basis Pengetahuan Microsoft:
237811 (http://support.microsoft.com/kb/237811/EN-US/ ) How to Activate a Terminal Services License Server and Install CALs Over the Internet 237.811 (http://support.microsoft.com/kb/237811/EN-US/) Cara Mengaktifkan Lisensi Terminal Services Server dan Instal CALs Over Internet
For additional information about how to activate a license server, click the following article number to view the article in the Microsoft Knowledge Base: Untuk informasi tambahan tentang cara mengaktifkan server lisensi, klik nomor artikel berikut untuk melihat artikel dalam Basis Pengetahuan Microsoft:
306622 (http://support.microsoft.com/kb/306622/EN-US/ ) How To Activate a License Server by Using Terminal Services Licensing in Windows 2000 306.622 (http://support.microsoft.com/kb/306622/EN-US/) Cara Mengaktifkan Server dengan Menggunakan Lisensi Terminal Services Licensing pada Windows 2000
For additional information about how to connect your computer client machines to Terminal Services, click the following article numbers to view the articles in the Microsoft Knowledge Base: Untuk informasi tambahan tentang cara menghubungkan komputer Anda mesin klien untuk Terminal Services, klik nomor artikel berikut untuk melihat artikel pada Basis Pengetahuan Microsoft:
306566 (http://support.microsoft.com/kb/306566/EN-US/ ) How To Connect Clients to Terminal Services By Using a Terminal Services Client in Windows 2000 306.566 (http://support.microsoft.com/kb/306566/EN-US/) Cara Menghubungkan Klien ke Terminal Services Dengan Menggunakan Terminal Services Client pada Windows 2000
306573 (http://support.microsoft.com/kb/306573/EN-US/ ) How to Connect Clients to Terminal Services by Using Client Connection Manager 306.573 (http://support.microsoft.com/kb/306573/EN-US/) Cara Menghubungkan Klien untuk Terminal Services oleh Klien Menggunakan Connection Manager
For additional information about how to secure your connection between the client and server, click the following article number to view the article in the Microsoft Knowledge Base: Untuk informasi tambahan tentang cara untuk mengamankan koneksi antara klien dan server, klik nomor artikel berikut untuk melihat artikel dalam Basis Pengetahuan Microsoft:
306561 (http://support.microsoft.com/kb/306561/EN-US/ ) How To Secure Communication Between a Client and Server with Terminal Services 306.561 (http://support.microsoft.com/kb/306561/EN-US/) Cara yang Aman Komunikasi Antara Client dan Server dengan Terminal Services
For additional information about how to deactivate or reactivate a license server, click the following article number to view the article in the Microsoft Knowledge Base: Untuk informasi tambahan tentang cara menonaktifkan atau mengaktifkan kembali lisensi server, klik nomor artikel berikut untuk melihat artikel dalam Basis Pengetahuan Microsoft:
306578 (http://support.microsoft.com/kb/306578/EN-US/ ) How To Deactivate or Reactivate a License Server Using Terminal Services Licensing 306.578 (http://support.microsoft.com/kb/306578/EN-US/) Cara Nonaktifkan atau Aktifkan Server Menggunakan sebuah Lisensi Terminal Services Licensing
• Server - The computer in which nearly all of the computing resources reside that will be used in the Terminal Services networking environment. Server - komputer di mana hampir semua sumber daya komputasi tinggal yang akan digunakan dalam lingkungan jaringan Terminal Services. The server will receive and process the keystrokes and mouse movements that take place at the client computer. Server akan menerima dan memproses penekanan tombol dan gerakan mouse yang terjadi pada komputer klien. The server displays the desktop and running applications within a window on the client computer. Menampilkan server desktop dan menjalankan aplikasi dalam sebuah jendela pada komputer klien.
• Messaging - This communication occurs between the server and clients by way of the Remote Desktop Protocol (RDP). Pesan - Komunikasi ini terjadi antara server dan klien dengan cara Remote Desktop Protocol (RDP). RDP is an application-layer protocol that relies on TCP/IP. RDP adalah sebuah protokol layer aplikasi yang mengandalkan pada TCP / IP.
• Clients - The computer on the network from which it is possible to open a window containing a terminal session. Klien - komputer di jaringan yang dimungkinkan untuk membuka jendela yang berisi sesi terminal. In this window is the remote desktop running on the server. Dalam jendela ini adalah remote desktop yang berjalan pada server. Applications and windows that are opened on this desktop are actually running on the server. Aplikasi dan jendela-jendela yang sedang dibuka di desktop ini benar-benar berjalan di server.
Enabling Terminal Services in Application Server Mode Mengaktifkan Terminal Services di Application Server Mode
To enable Terminal Services in Application Server mode on the domain controller, the information technology (IT) administrator logs on to server as the administrator and performs the following procedures. Untuk mengaktifkan Terminal Services Application Server dalam modus pada domain controller, teknologi informasi (TI) administrator log on ke server sebagai administrator dan melakukan prosedur berikut.
To enable Terminal Services: Untuk mengaktifkan Terminal Services:
1. Click Start , point to Settings , click Control Panel , and then double-click Add/Remove Programs . Klik Mulai, arahkan ke Pengaturan, klik Panel Kontrol, kemudian klik dua kali Add / Remove Programs.
2. Click Add/Remove Windows Components to start the Windows Components Wizard. Klik Add / Remove Windows Components untuk memulai Windows Components Wizard. In the Components list, to add or remove a component, click to select a check box. A shaded box indicates that only part of the component will be installed. Select the Terminal Services check box, and then click Next . Pada daftar Komponen, untuk menambah atau menghapus komponen, klik untuk memilih kotak centang. Sebuah kotak berbayang menunjukkan bahwa hanya sebagian dari komponen akan diinstal. Pilih kotak centang Terminal Services, kemudian klik Next.
3. In the Windows Components Wizard with Terminal Services selected, click Details to see what is included in the component. Dalam Windows Components Wizard dengan Terminal Services yang dipilih, klik Rincian untuk melihat apa yang termasuk dalam komponen. You will see the two following sub-components: Anda akan melihat dua sub-komponen berikut:
o Client Creator Files - Enables the creation of installation floppy disks for Terminal Services Client computers. Klien Pencipta File - Memungkinkan penciptaan disket instalasi Terminal Services Client untuk komputer.
o Enable Terminal Services - Enables the Terminal Services software on your computer. Aktifkan Terminal Services - Terminal Services Mengaktifkan perangkat lunak pada komputer Anda.
4. Click Next to continue. Klik Next untuk melanjutkan.
5. On the next screen, you are prompted to install Terminal Services to run in one of two modes: Pada layar berikutnya, Anda akan diminta untuk menginstal Terminal Services untuk berjalan dalam salah satu dari dua mode:
o Remote Administration - This mode permits two Terminal Services client connections to the server. Remote Administration - Mode ini memungkinkan dua klien Layanan Terminal koneksi ke server. This mode does not require licensing, but allows only members of the Administrators group to access the server. Modus ini tidak memerlukan lisensi, tapi hanya memungkinkan anggota grup Administrators untuk mengakses server. This is an excellent choice for non-Terminal Services servers, to enable remote control-type access to remote servers. Ini adalah pilihan yang sangat baik untuk non-Terminal Services server, untuk mengaktifkan remote control-tipe akses ke server remote.
o Application Server - This mode permits more than two simultaneous connections by non-administrators, but requires the Terminal Services Licensing service to be installed on a domain controller (for which you can use any server in a workgroup environment). Application Server - Mode ini memungkinkan lebih dari dua koneksi simultan oleh non-administrator, tapi membutuhkan layanan Terminal Services Licensing yang harus diinstal pada kontroler domain (dimana Anda dapat menggunakan server dalam lingkungan workgroup). A Terminal Services Client Access License is also required for non-Windows 2000 Professional clients. Sebuah Terminal Services Client Access License juga diperlukan untuk non-Windows 2000 Professional klien.
NOTE: Terminal Services Licensing is a required component that licenses clients on a Terminal server in Application Server mode. For computers that are in a Windows 2000 domain, Microsoft recommends that you do not enable Terminal Services Licensing on the same computer with Terminal Services. CATATAN: Terminal Services Licensing adalah komponen yang diperlukan lisensi klien pada server di Terminal modus Application Server. Untuk komputer yang ada di Windows 2000 domain, Microsoft menyarankan anda tidak mengaktifkan Terminal Services Licensing pada komputer yang sama dengan Terminal Services.
6. In Terminal Services Setup, verify that Application Server mode is selected, and then click Next . Dalam Terminal Services Setup, memverifikasi bahwa Application Server mode dipilih, dan kemudian klik Next.
NOTE : In Terminal Services Setup, you may see programs listed that will not work properly when Terminal Services is enabled. CATATAN: Dalam Terminal Services Setup, Anda dapat melihat daftar program yang tidak akan bekerja dengan baik bila diaktifkan Terminal Services. You need to reinstall these programs for multisession access by using the Add/Remove Programs tool after you enable Terminal Services. Anda perlu menginstal ulang program-program ini untuk Multisession akses dengan menggunakan Add / Remove Programs alat setelah Anda mengaktifkan Terminal Services.
7. In the next screen, click the appropriate option to specify whether you want permissions to be compatible with Windows 2000 Users or with Terminal Server 4.0 Users . Pada layar berikutnya, klik pilihan yang sesuai untuk menentukan apakah Anda ingin izin agar kompatibel dengan Windows 2000 Pengguna atau dengan Terminal Server 4,0 Pengguna. Use the Permissions compatible with Windows 2000 Users option for the most secure environment in which to run applications. Gunakan Permissions kompatibel dengan Windows 2000 User pilihan untuk lingkungan yang paling aman di mana untuk menjalankan aplikasi.
8. In Terminal Services Licensing Setup, specify whether you want the license server to serve your entire enterprise or your domain/workgroup, and then provide the directory location for the database. Wait for the installation to finish, and then click Finish . Dalam Terminal Services Licensing Setup, tentukan apakah Anda ingin agar server lisensi untuk melayani seluruh perusahaan atau domain / workgroup, dan kemudian memberikan lokasi direktori untuk menyimpan database. Tunggu sampai instalasi selesai, dan kemudian klik Selesai. In the Add/Remove Programs window, click Close . Dalam Add / Remove Programs jendela, klik Tutup.
NOTE : The required files are copied to your hard disk, and you can use server software after you restart the computer. CATATAN: file yang dibutuhkan akan disalin ke hard disk, dan Anda dapat menggunakan perangkat lunak server setelah Anda me-restart komputer.
Troubleshooting Troubleshooting
1. If an application is not working properly, it may be due to one of the following reasons: Jika aplikasi tidak berfungsi sebagaimana mestinya, hal itu mungkin karena salah satu alasan berikut:
o Applications that lock files or DLLs may not run properly because there is the possibility that more than one user will try to use the application at the same time. Aplikasi yang mengunci file atau DLL mungkin tidak berjalan semestinya karena ada kemungkinan bahwa lebih dari satu pengguna akan mencoba untuk menggunakan aplikasi pada waktu yang sama.
o Applications that use the computer name or IP address for identification may have trouble if more than one user at a time attempts to run the application. Aplikasi yang menggunakan nama komputer atau alamat IP untuk identifikasi mungkin mengalami masalah jika lebih dari satu pengguna pada suatu waktu mencoba untuk menjalankan aplikasi.
2. The e-mail address that you provided is not valid; Verify that the e-mail address is valid. E-mail yang Anda berikan tidak valid; Buktikan bahwa alamat e-mail valid.
REFERENCES REFERENSI
For additional information about how to activate a license server, click the ar...
For additional information about how to activate a license server, click the article number below to view the article in the Microsoft Knowledge Base: Untuk informasi tambahan tentang cara mengaktifkan server lisensi, klik nomor artikel di bawah ini untuk melihat artikel pada Basis Pengetahuan Microsoft:
237811 (http://support.microsoft.com/kb/237811/EN-US/ ) How to Activate a Terminal Services License Server and Install CALs Over the Internet 237.811 (http://support.microsoft.com/kb/237811/EN-US/) Cara Mengaktifkan Lisensi Terminal Services Server dan Instal CALs Over Internet
For additional information about how to activate a license server, click the following article number to view the article in the Microsoft Knowledge Base: Untuk informasi tambahan tentang cara mengaktifkan server lisensi, klik nomor artikel berikut untuk melihat artikel dalam Basis Pengetahuan Microsoft:
306622 (http://support.microsoft.com/kb/306622/EN-US/ ) How To Activate a License Server by Using Terminal Services Licensing in Windows 2000 306.622 (http://support.microsoft.com/kb/306622/EN-US/) Cara Mengaktifkan Server dengan Menggunakan Lisensi Terminal Services Licensing pada Windows 2000
For additional information about how to connect your computer client machines to Terminal Services, click the following article numbers to view the articles in the Microsoft Knowledge Base: Untuk informasi tambahan tentang cara menghubungkan komputer Anda mesin klien untuk Terminal Services, klik nomor artikel berikut untuk melihat artikel pada Basis Pengetahuan Microsoft:
306566 (http://support.microsoft.com/kb/306566/EN-US/ ) How To Connect Clients to Terminal Services By Using a Terminal Services Client in Windows 2000 306.566 (http://support.microsoft.com/kb/306566/EN-US/) Cara Menghubungkan Klien ke Terminal Services Dengan Menggunakan Terminal Services Client pada Windows 2000
306573 (http://support.microsoft.com/kb/306573/EN-US/ ) How to Connect Clients to Terminal Services by Using Client Connection Manager 306.573 (http://support.microsoft.com/kb/306573/EN-US/) Cara Menghubungkan Klien untuk Terminal Services oleh Klien Menggunakan Connection Manager
For additional information about how to secure your connection between the client and server, click the following article number to view the article in the Microsoft Knowledge Base: Untuk informasi tambahan tentang cara untuk mengamankan koneksi antara klien dan server, klik nomor artikel berikut untuk melihat artikel dalam Basis Pengetahuan Microsoft:
306561 (http://support.microsoft.com/kb/306561/EN-US/ ) How To Secure Communication Between a Client and Server with Terminal Services 306.561 (http://support.microsoft.com/kb/306561/EN-US/) Cara yang Aman Komunikasi Antara Client dan Server dengan Terminal Services
For additional information about how to deactivate or reactivate a license server, click the following article number to view the article in the Microsoft Knowledge Base: Untuk informasi tambahan tentang cara menonaktifkan atau mengaktifkan kembali lisensi server, klik nomor artikel berikut untuk melihat artikel dalam Basis Pengetahuan Microsoft:
306578 (http://support.microsoft.com/kb/306578/EN-US/ ) How To Deactivate or Reactivate a License Server Using Terminal Services Licensing 306.578 (http://support.microsoft.com/kb/306578/EN-US/) Cara Nonaktifkan atau Aktifkan Server Menggunakan sebuah Lisensi Terminal Services Licensing
Langganan:
Postingan (Atom)