|
Home > Archive > 70-217 > May 2002 > Thu 70-217 Question of the Day
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Thu 70-217 Question of the Day
|
|
| wbafrank 2002-05-02, 10:49 am |
|  And today's poser is ....
Q67. After you demote a domain controller to a server, the object that represents the server in the Active Directory Sites and Services Manager snap-in remains. Why?
A. The server object is a "container" in the Active Directory and may hold child objects that represent configuration data for other services installed on your computer. Because of this, the Dcpromo utility does not automatically remove the server object.
B. The server object is a "container" in the Active Directory and may hold Group Policy Objects that represent configuration data for other services installed on your computer.
C. The server object is a "container" in the Active Directory and may hold child objects that represent configuration data for other services installed on your computer. Because of this, the Dcpromo utility automatically removed the server object.
D. The server object is a PDC in the Active Directory and may hold parent objects that represent configuration data for other services installed on your computer. Because of this, the Dcpromo utility does not automatically remove the server object.
Good Luck .... see you tomorrow for the answer!! | |
| lamngocliem 2002-05-02, 11:21 am |
| My answer is A. | |
| Sexy Lexy 2002-05-02, 2:43 pm |
| Expoliting my ignorance yet again but I would say D as a server can not act as a container. An OU is the lowest container object, this would point to D but like yesterdays question, I am still learning.
 | |
| KScheler 2002-05-02, 5:10 pm |
| I'll say "A". | |
| Slinky 2002-05-03, 9:34 am |
| quote:
Originally posted by Sexy Lexy
Expoliting my ignorance yet again but I would say D as a server can not act as a container. An OU is the lowest container object, this would point to D but like yesterdays question, I am still learning.
In Active Directorty Sites and Services a server can indeed act as a container. If you click on the server you will see "NTDS settings". Inside there you will find the connection object. | |
| wbafrank 2002-05-03, 2:41 pm |
| quote:
Originally posted by wbafrank
And today's poser is ....
Q67. After you demote a domain controller to a server, the object that represents the server in the Active Directory Sites and Services Manager snap-in remains. Why?
A. The server object is a "container" in the Active Directory and may hold child objects that represent configuration data for other services installed on your computer. Because of this, the Dcpromo utility does not automatically remove the server object.
B. The server object is a "container" in the Active Directory and may hold Group Policy Objects that represent configuration data for other services installed on your computer.
C. The server object is a "container" in the Active Directory and may hold child objects that represent configuration data for other services installed on your computer. Because of this, the Dcpromo utility automatically removed the server object.
D. The server object is a PDC in the Active Directory and may hold parent objects that represent configuration data for other services installed on your computer. Because of this, the Dcpromo utility does not automatically remove the server object.
Good Luck .... see you tomorrow for the answer!!
And the answer is ....
Correct Answers: A
CAUSE
This issue occurs because the server object is a "container" in the Active Directory and may hold child objects that represent configuration data for other services installed on your computer. Because of this, the Dcpromo utility does not automatically remove the server object.
RESOLUTION
WARNING: If the server object contains any child objects named "NTDS Settings," these are objects that represent the server as a domain controller and should be automatically removed by the demotion process. If this does not work, or a demotion could not be performed (for example, on a computer with malfunctioning hardware) these objects must be removed by using the Ntdsutil utility before you delete the server object.
After an administrator verifies that all other services with a dependency on the server object have been removed, or if the domain controller is being rebuilt and the decommissioning of the server could not be performed gracefully, an administrator can delete the server:
1. Click Start, point to Programs , point to Administrative Tools , and then click Active Directory Sites and Services Manager .
2. Double-click the Sites branch to expand it, and then double-click the appropriate site's branch (the site the server resides in) to expand it.
3.Double-click the server's container, right-click the server object, and then click Delete.
4. Click Yes when you are prompted to confirm deleting the object.
NOTE : This process may not finish successfully for either of the following reasons:
1. If you receive a message that states the server is a container that contains other objects, verify that the appropriate decommissioning of services has completed before continuing.
2. If you receive a message that states the DSA object cannot be deleted, you may be attempting to delete an active domain controller.
For more information about the Ntdsutil utility, refer to the Support Tools documentation on the Windows 2000 CD-ROM in the \Support\Tools folder.
MORE INFORMATION
An administrator may safely delete the server object in the Active Directory Sites and Services Management snap-in after all services have been removed and no child objects exist. | |
| Sexy Lexy 2002-05-04, 11:42 am |
| I stand corrected, the explainations really help in understading the subject.
Way to go wbafrank!
|
|
|
|
|