Professional Documents
Culture Documents
Local user profile : A local user profile is created the first time you log on
to a computer and is stored on a computer's local hard disk. Any changes
made to your local user profile are specific to the computer on which you
made the changes.
Hi go through these documents. Also they would ask about the boot process of a computer. as
to how it boots up & what is the sequence. and some general t/s and not to forget vista....n y is
it betr than xp.....not just the g u i?
1) What is Active Directory
2) What are FSMO Roles? Explain Each Role
3) What is a Global Catalog
4) What are Group Policies
5) What is the difference between a Domain and Workgroup
6) What is the relationship between tree and a forest
7) What is the file name of Active directory and where is it stored….ANS:ntds.dit
8) What are the different types of backups explain them
9) Where is system State and what does it contain
10) What is the difference between NTFS and FAT file system
11) What is a logical Partition and Physical Partition in Active Directory
12) How do you install Active Directory
13) Can Active Directory be uninstalled? if yes how? if no why
14) What is DNS?
15) What is router frequency, NAT, how it work, what router does, which protocol it uses
16) OSI layer & protocols in each layer
17) what is ping (packet internet gropher) & its protocol (ICMP) -- ping is used to check
connectivity to an IP
The Five FSMO Roles
Short for Flexible Single Master Operations, it is a feature of Microsoft's Active Directory.
The schema master FSMO role holder is the domain controller responsible for performing
updates to the directory schema.
There are just five operations where the usual multiple master model
breaks down, and the Active Directory task must only be carried out on
one Domain Controller. FSMO roles:
1. PDC Emulator - Most famous for backwards compatibility with
NT 4.0 BDC's. However, there are two other FSMO roles which
operate even in Windows 2003 Native Domains, synchronizing the
W32Time service and creating group policies. I admit that it is
confusing that these two jobs have little to do with PDCs and
BDCs.
2. RID Master - Each object must have a globally unique number
(GUID). The RID master makes sure each domain controller
issues unique numbers when you create objects such as users or
computers. For example DC one is given RIDs 1-4999 and DC
two is given RIDs 5000 - 9999.
3. Infrastructure Master - Responsible for checking objects in
other other domains. Universal group membership is the most
important example. To me, it seems as though the operating
system is paranoid that, a) You are a member of a Universal
Group in another domain and b) that group has been assigned
Deny permissions. So if the Infrastructure master could not
check your Universal Groups there could be a security breach.
4. Domain Naming Master - Ensures that each child domain has a
unique name. How often do child domains get added to the
forest? Not very often I suggest, so the fact that this is a FSMO
does not impact on normal domain activity. My point is it's worth
the price to confine joining and leaving the domain operations to
one machine, and save the tiny risk of getting duplicate names or
orphaned domains.
5. Schema Master - Operations that involve expanding user
properties e.g. Exchange 2003 / forestprep which adds mailbox
properties to users. Rather like the Domain naming master,
changing the schema is a rare event. However if you have a
team of Schema Administrators all experimenting with object
properties, you would not want there to be a mistake which
crippled your forest. So its a case of Microsoft know best, the
Schema Master should be a Single Master Operation and thus a
FSMO role.
Uninstall Active Directory
2.
The Active Directory Installation Wizard appears. Click Next at the Welcome screen.
3.
You have an option to select This server is the last domain controller in the domain. If
you select this option, the wizard attempts to remove the domain from the forest. Do not
select this option. Click Next.
4.
At the Administrative Password screen, enter and confirm the password that you want to
assign to the local Administrator account after Active Directory is removed. Click Next.
5.
At the Summary screen, verify that the information is correct and then click Next to proceed
with the removal.
6.
The wizard proceeds to remove Active Directory. After it finishes, the wizard displays a
completion screen. Click Finish to close the wizard.
7.
Click Restart to restart the domain controller.