Announcement

Collapse
No announcement yet.

Best practice for an application domain?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Best practice for an application domain?

    Hello,

    I have this AD structure:
    - a root domain (in a remote datacenter);
    - several child domains, one for each country.
    We have to deploy some applications that are forest-wide (such as enterprise antivirus console, enterprise asset management etc.) and not strictly tied to a single country, but are enterprise-wide, and will be moved to the remote datacenter.

    What is the best practice for this situation?
    Installing these services under the root domain? (It sounds inelegant to me)
    Or create an "application-only" domain and install the services there? (breaking our "rule" of country domains.)
    Or else, choose a country willing to manage these services?

    Thanks to anyone willing to help.

  • #2
    Re: Best practice for an application domain?

    TBH, I dont think there is any "best practice"
    (Although MS no longer recommend separate domains for everything)
    If you don't want to break your country domain structure, how about a separate tree in your existing forest?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment

    Working...
    X