A domain is a logical grouping of network computers that share a central directory
database. A directory database contains user accounts and security
information for the domain. This database, which is known as the directory, is the database
portion of Active Directory service—the Windows 2003 directory service. In a domain, the directory resides on computers that are configured as domain controllers.
A domain controller is a server that manages all security-related aspects of user
and domain interactions, centralizing security and administration
A domain does not refer to a single location or specific type of network configuration.
The computers in a domain can share physical proximity on a small LAN or they can
be located in different corners of the world. They can communicate over any number
of physical connections, including dial-up connections, Integrated Services Digital Network
(ISDN) circuits, Ethernet networks, token ring connections, frame relay networks,
satellite links, and leased lines.
The benefits of a domain include the following:
1. Centralized administration because all user information is stored in the Active
Directory database. This centralization allows users to manage only a single user
name and password, and enables domain administrators to control which users
can access resources on any computer that is a member of the domain.
2. A single logon process for users to gain access to network resources (such as file,
print, and application resources) for which they have permissions. In other words,
you can log on to one computer and use resources on another computer in the
network as long as you have appropriate permissions to access the resource.
3. Scalability, so that you can create very large networks with hundreds or thousands
of computers.
A typical Windows 2003 domain includes the following types of computers:
Domain controllers running Windows Server 2003 Each domain controller
stores and maintains a copy of Active Directory. In a domain, you create a user
account in Active Directory only once. When a user logs on to a computer in the
domain, a domain controller authenticates the user by checking the directory for
the user name, password, and logon restrictions. When there are multiple domain
controllers in a domain, they periodically replicate their directory information so that each domain controller has a copy of Active Directory. Domain controllers do
not maintain a local user database.
Member servers running Windows Server 2003 A member server is a server
that is a member of a domain, but is not configured as a domain controller. A
member server does not store directory information and cannot authenticate users.
Member servers provide shared resources such as shared folders or printers.
Client computers running Windows XP Professional or Windows 2000
Professional Client computers run a user’s desktop environment and allow the
user to gain access to resources in the domain.
Showing posts with label Remote Assistance. Show all posts
Showing posts with label Remote Assistance. Show all posts
December 3, 2009
How to Work with Workgroups
A Windows XP Professional workgroup is a logical grouping of networked computers
that share resources, such as files and printers. A workgroup is also called a peer-topeer
network because all computers in the workgroup can share resources as equals
(peers) without requiring a dedicated server.
Each computer in the workgroup maintains a local security database, which is a list of user
accounts and resource security information for the computer on which it resides. Using a
local security database on each workstation decentralizes the administration of user
accounts and resource security in a workgroup.
Because workgroups have decentralized administration and security, the following are
true:
■ A user must have a user account on a local computer if that user wants to log on
to that computer locally (that is, by sitting down at that computer).
■ Any changes to user accounts, such as changing a user’s password or adding a
new user account, must be made on each computer in the workgroup. If you forget
to add a new user account to one of the computers in your workgroup, the
new user cannot log on to that computer and cannot access resources on it.
Workgroups provide the following advantages:
■ Workgroups do not require a domain controller to hold centralized security information,
making workgroups much simpler to configure and manage.
■ Workgroups are simple to design and implement. Workgroups do not require the
extensive planning and administration that a domain requires.
■ Workgroups provide a convenient networking environment for a limited number
of computers in close proximity. However, a workgroup becomes impractical in
environments with more than 10 computers.
that share resources, such as files and printers. A workgroup is also called a peer-topeer
network because all computers in the workgroup can share resources as equals
(peers) without requiring a dedicated server.
Each computer in the workgroup maintains a local security database, which is a list of user
accounts and resource security information for the computer on which it resides. Using a
local security database on each workstation decentralizes the administration of user
accounts and resource security in a workgroup.
Because workgroups have decentralized administration and security, the following are
true:
■ A user must have a user account on a local computer if that user wants to log on
to that computer locally (that is, by sitting down at that computer).
■ Any changes to user accounts, such as changing a user’s password or adding a
new user account, must be made on each computer in the workgroup. If you forget
to add a new user account to one of the computers in your workgroup, the
new user cannot log on to that computer and cannot access resources on it.
Workgroups provide the following advantages:
■ Workgroups do not require a domain controller to hold centralized security information,
making workgroups much simpler to configure and manage.
■ Workgroups are simple to design and implement. Workgroups do not require the
extensive planning and administration that a domain requires.
■ Workgroups provide a convenient networking environment for a limited number
of computers in close proximity. However, a workgroup becomes impractical in
environments with more than 10 computers.
December 2, 2009
How did u Configure and Use Remote Assistance
A Remote Assistance session requires that both the user needing help and the expert
user actively participate in establishing the connection. The session is established in the
following phases:
1. The user that needs help sends a Remote Assistance invitation to the expert user.
2. The expert user responds to the invitation.
3. The user accepts the expert user’s assistance.
To send a Remote Assistance invitation, use these steps:
1. From the Start menu, select Help And Support.
2. In the Help And Support Center, under Ask For Assistance, select Invite A Friend
To Connect To Your Computer With Remote Assistance, and then select Invite Someone To Help You.
3. Select the method that you want to use to create the invitation, as shown in Figure
18-18. You can send invitations directly by using Windows Messenger, by using an e-mail attachment, or by saving an invitation file and transmitting it to the helper user (for example, you could save the file to a shared folder on the network).
4. When prompted, enter the requested information, including your name, a message, when the invitation should expire, and (optionally) a password to be used to establish the connection.
5. Click Send Invitation
Note When an invitation is sent through an e-mail attachment or saved as a file, the file has a .MsRcIndicent extension. An expert user must respond to an invitation to continue the process. If the invitation is by using Windows Messenger, you must accept the invitation that is presented in the Messenger pop-up window. If the invitation is sent by e-mail, you must open the attached invitation. If the invitation file is transmitted in some other fashion, you must access and open it. If a password is required, you must enter the password in the
Remote Assistance dialog box. Tip Using Windows Messenger to establish a Remote Assistance connection is the easiest method because the Windows Messenger connection can usually be established regardless of whether there are firewalls on either the user’s or the expert helper’s network. If you use another method of establishing a Remote Assistance session, you must configure a firewall to allow the connection. Like Remote Desktop, Remote Assistance uses TCP port 3389 by default. Windows then notifies the user requiring assistance that the request has been accepted. The user must click Yes in the Remote Assistance dialog box as a final indication of acceptance, and Remote Assistance then establishes the connection.
user actively participate in establishing the connection. The session is established in the
following phases:
1. The user that needs help sends a Remote Assistance invitation to the expert user.
2. The expert user responds to the invitation.
3. The user accepts the expert user’s assistance.
To send a Remote Assistance invitation, use these steps:
1. From the Start menu, select Help And Support.
2. In the Help And Support Center, under Ask For Assistance, select Invite A Friend
To Connect To Your Computer With Remote Assistance, and then select Invite Someone To Help You.
3. Select the method that you want to use to create the invitation, as shown in Figure
18-18. You can send invitations directly by using Windows Messenger, by using an e-mail attachment, or by saving an invitation file and transmitting it to the helper user (for example, you could save the file to a shared folder on the network).
4. When prompted, enter the requested information, including your name, a message, when the invitation should expire, and (optionally) a password to be used to establish the connection.
5. Click Send Invitation
Note When an invitation is sent through an e-mail attachment or saved as a file, the file has a .MsRcIndicent extension. An expert user must respond to an invitation to continue the process. If the invitation is by using Windows Messenger, you must accept the invitation that is presented in the Messenger pop-up window. If the invitation is sent by e-mail, you must open the attached invitation. If the invitation file is transmitted in some other fashion, you must access and open it. If a password is required, you must enter the password in the
Remote Assistance dialog box. Tip Using Windows Messenger to establish a Remote Assistance connection is the easiest method because the Windows Messenger connection can usually be established regardless of whether there are firewalls on either the user’s or the expert helper’s network. If you use another method of establishing a Remote Assistance session, you must configure a firewall to allow the connection. Like Remote Desktop, Remote Assistance uses TCP port 3389 by default. Windows then notifies the user requiring assistance that the request has been accepted. The user must click Yes in the Remote Assistance dialog box as a final indication of acceptance, and Remote Assistance then establishes the connection.
