We have a forest domain with 2 child domains. Each child domain has it's own WDS server, and each child domain runs on their own subnet (child-domain-1: 10.100.x.x range, child-domain-2: 192.168.x.x range). Both of these networks are bridged too, so we can communicate with one another.
When we image machines within child-domain-1, clients sometimes boot to the WDS server of child-domain-2. It takes quite a few reboots/on-offs to get to boot correctly.
Is there anyway to correct this? child-domain-1 clients should ONLY boot to the WDS server of child-domain-1, and child-domain-2 clients should ONLY boot to the WDS of child-domain-2. It's quite annoying, and I've configured each to only connect to their respective domains.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
We have a forest domain with 2 child domains. Each child domain has it's own WDS server, and each child domain runs on their own subnet (child-domain-1: 10.100.x.x range, child-domain-2: 192.168.x.x range). Both of these networks are bridged too, so we can communicate with one another.
When we image machines within child-domain-1, clients sometimes boot to the WDS server of child-domain-2. It takes quite a few reboots/on-offs to get to boot correctly.
Is there anyway to correct this? child-domain-1 clients should ONLY boot to the WDS server of child-domain-1, and child-domain-2 clients should ONLY boot to the WDS of child-domain-2. It's quite annoying, and I've configured each to only connect to their respective domains.
Share this post
Link to post
Share on other sites