This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.
How can I make AD more robust?
I'm a systems administrator in a windows 2008R2 domain. How else can I make AD more robust besides deleting orphaned objects and accounts?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
What definition of robust do you have in mind? I actually resist deleting accounts because of times when references to these accounts persist in offline storage and it's useful to be able to recover some idea of who they belonged to if the need should arise.
Of more concern, in my opinion, is replication stability across different sites and your ability to recover AD in the face of some disaster scenarios.
Of more concern, in my opinion, is replication stability across different sites and your ability to recover AD in the face of some disaster scenarios.
My definition of robust in reference to AD would be the frequency and ease of replication across sites and removal of orphaned objects (excluding accounts) and I do agree with you on the ease of recovery
from disaster scenarios.
from disaster scenarios.
I'm not sure there's a lot to be done besides creating additional domain controllers. Maybe if you could explain a bit more about what you're trying to achieve...
Originally the question was asked during an interview and I just wanted to know if there was more that could be done in addition to what that has been mentioned previously.
Hmmm. Did you not get the job? Is this the question that gave you the most trouble?
As a hypothetical, asked in an interview, I'd guess that they were probing for more general knowledge about AD and the underlying mechanisms it uses for replication and protection in an environment subject to many possible types of failure. But why bring up orphaned objects and accounts? It occasionally happens that an interviewer asks a poorly thought out question; you have to be a mind reader to get what they're really after.
As a hypothetical, asked in an interview, I'd guess that they were probing for more general knowledge about AD and the underlying mechanisms it uses for replication and protection in an environment subject to many possible types of failure. But why bring up orphaned objects and accounts? It occasionally happens that an interviewer asks a poorly thought out question; you have to be a mind reader to get what they're really after.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial