Would this be the right thinking for child domains?


hi,


building out sharepoint environment, have dev/prod domains (mentioned before in previous thread). however, hosting number of infrastructure servers in network such wsus, dhcp, wds, etc. sharepoint environments need visibility of dhcp needs serve many servers in entire network, regardless of in domain structure.

thinking can create 2 child domains under parent domain called infrastructure (which hosts relevant infrastructure servers), comprise of respective dev , prod sharepoint environments.


there flaw in design? it's either or 3 seperate flat domains under forest.



thanks

i never heard deploying share point there requirment new child domain. requires "replication directory change" permission in existing domain. what trying accomplish?

best regards biswajit biswas disclaimer: posting provided "as is" no warranties or guarantees , , confers no rights. mcp 2003,mcsa 2003, mcsa:m 2003, ccna, mcts, enterprise admin



Windows Server  >  Directory Services



Comments

Popular posts from this blog

Domain migration ERR3:7075 Failed to change domain affiliation, hr=8007054a This operation is only allowed for the Primary Domain Controller of the domain

2008 Windows Deployment Server Properties Error

How do a find data in one file, search for it in another file and if not found, write a custom message to another file