Local farmers came across pieces of a clay figure, and these shards led. Today in History: 1974 The Terracotta Army is discovered in Xi'an, ChinaOn March 29, 1974, the first in an extensive collection of terra-cotta warriors was discovered in Xian, China.
Any suggestion would be much appreciated!Ĭan someone share a "real" plan about this? I only see theory about it, but I want to be able to see a REAL REAL plan (without confidential information, of course).thanks So the end result is that domain cad and ody see each other but not domain gregg. I do know that when i browse the network from the domain ody or domain cad it will show each other domain's servers/pcs. Those 2 are usually maintained by vendors. As far as the FSMO roles on those i'm not sure of. Domain cad and domain ody are housed on 2k3 boxes. Domain gregg is housed on 2 2k8r2 virtual machines, and 1 has the FSMO roles. Under dameware it used to show the domain cad and domain ody under the "microsoft windows network" tab on the left but now it shows "No PDC". Since then we have not been able to browse via "DameWare NT utilities", or by "Network" browser from the workstations/servers on domain gregg. However, we left the servers, ones on all 3 domains, on the same subnet. Riddle me this, we switched over our workstation IP's on domain gregg from a .x subnet to 10.1.x.x.
The other 2 domains are used for specific applications that had to be separate from our primary domain for legal/security policies. Domain Gregg is our primary domain where all of our workstations are joined to, and where most of our servers reside. Domain Gregg, Domain cad, and domain ody are the 3 domains in question.
0 kommentar(er)
