dhcp and wsus joining from old AD and join to a new ad with new na

hi! Thank you all for the reply, the reason i'm thinking of joining-rejoining
of domain for my dhcp and wsus server is to avoid changing of domain name
directly on my existing AD. I'm thinking of creating a new AD in a new sets
of machines and then move the services 1 by 1 from my current AD.

The question is that will disjoining and joining of domain for my current
dhcp (besides changing of suffix name in the scope option) and wsus server
create any issue?

Thanks.

In news:759A2A50-B791-4443-8B4A-348DF46FB5DE@microsoft.com,
dkblee <dkblee@discussions.microsoft.com>, posted the following:
> hi! Thank you all for the reply, the reason i'm thinking of
> joining-rejoining of domain for my dhcp and wsus server is to avoid
> changing of domain name directly on my existing AD. I'm thinking of
> creating a new AD in a new sets of machines and then move the
> services 1 by 1 from my current AD.
>
> The question is that will disjoining and joining of domain for my
> current dhcp (besides changing of suffix name in the scope option)
> and wsus server create any issue?
>
> Thanks.

I'm not sure I understand the question. Do you want to disjoin the DHCP
server from your domain? Or is the question regarding renaming your whole
domain, or are you simply disjoiing a client machine from one domain and
joining it to another? If so, the Primary DNS Suffix will change on the
machine to the domain it will belong to. It will then register (if
everything is working properly) to the zone for the domain you are joining
it to.

Or if deciding to rename a domain because of WSUS or DHCP, I wouldn't bother
going through the process, unless your current domain name is a single label
name domain. Otherwise, it will not be worth it.

WSUS is tied into the AD domain the machine is installed that it is joined
to. This allows you to target machines based on either GPO targeting or
direct.

Ace