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
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
Post a Comment