moving member (BDC) to its own DNS/AD site containers.

%3CLINGO-SUB%20id%3D%22lingo-sub-1844202%22%20slang%3D%22en-US%22%3Emoving%20member%20(BDC)%20to%20its%20own%20DNS%2FAD%20site%20containers.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1844202%22%20slang%3D%22en-US%22%3E%3CP%3EI%20didnt%20build%20it%2C%20just%20manage%20it.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20domain%20that%20has%204%20trusts%20to%204%20separate%20sites.%26nbsp%3B%20Total%20sites%20is%205.%3C%2FP%3E%3CP%3EWhen%20the%20Domain%20was%20built%20and%20the%20servers%20are%20were%20added%20for%20some%20reason%20they%20added%20two%20sites%20together.%26nbsp%3B%20So%20Site%201%20and%20Site%202%20are%20tied%20into%20the%20same%20DNS%20Site%2C%20Same%20Domains%20and%20Trusts%20site%2C%20etc..%3C%2FP%3E%3CP%3EI%20need%20to%20separate%20site%202%20so%20its%20in%20its%20own%20little%20containers%20like%20the%20other%20sites%20are.%26nbsp%3B%20We%20also%20have%20extensive%20GPOs%20that%20deal%20with%20Site2%20as%20well%20as%20all%20other%20sites.%3C%2FP%3E%3CP%3EThe%20main%20reason%20we%20are%20doing%20this%20is%20due%20to%20PaperCut%20Mobility.%26nbsp%3B%20Basically%20its%20like%20google%20cloud%20print.%26nbsp%3B%20When%20have%20site%201%20and%20site%202%20share%20the%20same%20DNS%20container%20-%20papercut%20relies%20on%20DNS%20to%20push%20printers%20out.%26nbsp%3B%20But%20due%20to%20having%20two%20servers%20in%20this%20container%20I%20can%20not%20separate%20it%20as%20we%20are%20currently%20configured%20with%20Papercut.%26nbsp%3B%20Primary%20objective%20is%20to%20seperate%20Site%202%20so%20it%20has%20its%20own%20DNS%20site%2Fcontainer%20containing%20its%20subnet%20of%20IP%20addresses%20and%20authoritive%2Fprimary%20servers%2C%20and%20AD%20basically%20having%20the%20same%20thing.%26nbsp%3B%20I%20dont%20know%20if%20this%20can%20be%20done%20without%20removing%20the%20server%20from%20the%20domain%20and%20adding%20it%20back%20in%2C%20and%20how%20that%20will%20effect%20the%20GPO's%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1844202%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EContainers%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDNS%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

I didnt build it, just manage it.  

I have a domain that has 4 trusts to 4 separate sites.  Total sites is 5.

When the Domain was built and the servers are were added for some reason they added two sites together.  So Site 1 and Site 2 are tied into the same DNS Site, Same Domains and Trusts site, etc..

I need to separate site 2 so its in its own little containers like the other sites are.  We also have extensive GPOs that deal with Site2 as well as all other sites.

The main reason we are doing this is due to PaperCut Mobility.  Basically its like google cloud print.  When have site 1 and site 2 share the same DNS container - papercut relies on DNS to push printers out.  But due to having two servers in this container I can not separate it as we are currently configured with Papercut.  Primary objective is to seperate Site 2 so it has its own DNS site/container containing its subnet of IP addresses and authoritive/primary servers, and AD basically having the same thing.  I dont know if this can be done without removing the server from the domain and adding it back in, and how that will effect the GPO's?

0 Replies
www.000webhost.com