So I know this might sounds like two separate issues but they will relate, I promise. haha
I am implementing WDS/MDT for the 2nd time in my career for a company who did not have a proper imaging solution. Long story short, the previous company only had one site and the current one I'm working for has a total of 24 locations under one domain.
Each site has it's own DC, Computer Workstation OU for that site and site code and a utility server that hosts WDS/MDT
For example Our New Jersey site code is called HINJ.
Our WDS/MDT server is located on an utility server which local to that location.
I want to use DFS NameSpace and Replication to sync all my sites with the same deployment share. All the sites have matching task sequences, software, OS and etc... with the exception of the following two lines in the rules tab: OSDComputername=
and
MachineObjectOU=OU=
Example rule for naming New Jersey, Kentucky and Corp Computers:
(In New Jersey's rules) OSDComputername=HINJ-%SerialNumber%
(In Kentucky's rules) OSDComputername=HFDH-%SerialNumber%
(In Corp's rules) OSDComputername=CORP-%SerialNumber%
When join computer to the domain rule:
(In New Jersey's rules) MachineObjectOU=OU=Win-10-Workstations,OU=HINJ,DC=MYDOMAIN,DC=com
(In Kentucky's rules) MachineObjectOU=OU=Win-10-Workstations,OU=HFDH,DC=MYDOMAIN,DC=com
(In Corp's rules) MachineObjectOU=OU=Win-10-Workstations,OU=CORP,DC=MYDOMAIN,DC=com
From my understanding with DFS Replication, if all the site's reference Corp's Deployment share, then the rules for each site are always going to get changed to whatever is set as the DFS Primary Member (Corp's Deployment Share) folder which tells me
that I will have manually change the rules back to the site's specific information each time replication happens.
Is there a better way to manage all 24 shares? Am I over thinking or under thinking this?
Hopefully I wrote this out clear enough to understand my issue. Thanks in advance.