0
What else can I help you with?
What is the different between local user and domain User?
local users account on local PC. he don't have to log another PC in the network. about domain domain is a logical group of network, all users are create in domain on the server that's y user can log-in in domain any where. u can set policies for user on server not a particular PC.
What type of a domain group is most like the local group on a member server?
This the answer straight from the book:Domain local groups in a Windows Server 2003 mixed or interim domain are limitedto the domain controller on which they reside. This is very similar to the way localgroups on a member server are limited to the computers on which they reside.Unless the domain functional level is raised to Windows 2000 native or WindowsServer 2003, the domain local groups cannot be used for permission assignmenton any servers in the domain other than the domain controllers.
Difference between local user account and domain user account?
The local user is the person who actually uses the account to do the work they are paid to do. A domain user could be a network administrator
Which of the following objects can be added to a domain local group when a domain is configured to the Windows Server 2003 mixed domain functional level?
Users.
Explain the difference between a local name server and an authoritative name server?
A host's authoritative name server provides the "official" translation of a hostname to an IP address (among other things). A host's local name server is a proxy to the DNS system: the host first queries its local name server for a mapping; the local name server then obtains the mapping on the behalf of the querying host.
Who arranges windows directories?
domain administrator is responsible for arranging, managing, modifying, deletion of directories in domain/windows server in domain. The local administrator or any user who is member of administrator group can do it also on the local windows system.
When can a domain local group be converted to a universal group?
Always, because it has no restrictions when the domain functional level is •Windows 2000 native or Windows Server 2003: You can convert universal groups to domain local groups or to global groups
Which group scope modifications in server 2003 are not permitted?
global to universal,universal of global, global to domain local
What to write as Network Domain and Server Name when working on your local machine. Im installing Apache 2.0.58 on a XP machine?
If your PC is not a part of a domain it doesn't matter which name you put over there (Network Domain). Server Name is a network name for your PC which can be used instead of ip address.
What is the difference between a domain local group global group and a universal group?
Global Group: Members of Global Group can come only from local domain but members can access resources in any domain. Domain Local Group: Members of Local Group can come from any domain but members can access resources only in local domain. Universal Group: Members can come from any domain and members can access resource in any domain. Hope this is easy:)
What is the difference between iterative queries and recursive queries of dns?
Recursive queries When a client system sends a recursive query to a local name server, that local name server must return the IP address for the friendly name entered, indicate that it can't find an address, or return an error saying that the requested address does not exist. Name servers do not refer the client system requesting a recursive query to other DNS servers. When answering recursive queries, the originating client does not receive address information directly from any DNS server other than the local name server. Typically, the local name server will first check DNS data from its own boot file, cache, database, or reverse lookup file. If the server is unsuccessful in obtaining the answer from those local sources, it may contact other DNS servers for assistance using iterative queries and then pass the information it receives back to the client that originated the name resolution request. Iterative queries In iterative queries, name servers return the best information they have. Although a DNS server may not know the IP address for a given friendly name, it might know the IP address of another name server likely to have the IP address being sought, so it sends that information back. The response to an iterative query can be likened to a DNS server saying, "I don't have the IP address you seek, but the name server at 10.1.2.3 can tell you." The process is straightforward. Here's one example in which a local name server uses iterative queries to resolve an address for a client: The local name server receives a name resolution request from a client system for a friendly name (such as www.techrepublic.com). The local name server checks its records. If it finds the address, it returns it to the client. If no address is found, the local name server proceeds to the next step. The local name server sends an iterative request to the root (the "." in .com) name server. The root name server provides the local name server with the address for the top-level domain (.com, .net, etc.) server. The local name server sends an iterative query to the top-level domain server. The top-level domain server replies with the IP address of the name server that manages the friendly name's domain (such as techrepublic.com). The local name server sends an iterative request to the friendly name's domain name server. The friendly name's domain name server provides the IP address for the friendly name (www.techrepublic.com) being sought. The local name server passes that IP address to the client. It seems complicated, but the process completes in a matter of moments. Or, if an address isn't found, a 404 error message is returned to the client.
Difference between a Local Group Policy and a Domain Group Policy?
Microsoft recommends that access control to computer resources be administered by using groups. In this way, many users that have similar needs for resources can be dropped into a group that has the correct permissions already configured instead of individually modifying each user account. Group permissions to access resources are configured using group policy. A policy usually addresses one very specific aspect of a system's configuration. There are many policies that can be configured for a group to control system access and behavior. Local group policy addresses only users who are physically logging into one particular machine such as the server itself or a stand alone operating system. To log into a machine locally, a user must create a unique ID/Password pair that authenticates the local user to the local physical system. Once authenticated to the local physical machine, group policy according to which local group the user is assigned is initiated. Domain authentication as well as domain group policy is maintained centrally by the server for the domain. Even if a user has configured a local ID/Password pair for their local physical computer, a different and unique ID/Password pair is created to log onto the domain. When a domain user is created, they also must be assigned to a domain group. Once the server for the domain authenticates the domain user, the policy for the domain group the user belongs to is initiated. These policies are centrally administered by the domain administrator instead of each computer in the domain being configured separately for each user. Domain group policy can be configured to control access and behavior for any resource on the entire domain including resources on client computers. Local group policy can only control what is on the local machine at which a user is sitting. Finally, domain group policy supersedes any local group policy.
