1

Hi:

Don’t know if anyone can help, but figured i’d try. Migrating from 2012R2 to 2025. Used a 2022 jump box and migration from 2012R2 went fine. Going from 2022 to 2025 (have two DCs, same exact problem) went fine for most part but the DHCP Scope Option is missing in 2025s. The DHCP server is activated and ready to lease IPs in event viewer. I did a rplsummary and it checks fine, no errors. Any ideas, greatly appreciated?

Thanks,

John

6 Spice ups
2

2025 is known to have issues with DCs.

Is your DC also the DHCP server, it’s not clear but this isn’t best practise if it is.

1 Spice up
3

I was trying to make it the DHCP server. The 2022 is still issuing the IPs right now.

1 Spice up
4

Did you change DFS to DFSR.

Can you show a screenshot of your issue?

As a new user you’ll need to wait for a mod to approve it.

I wouldn’t recommend DHCP on your DC though.

DHCP is not replicated either, you have to migrate the scopes using export and import.

2 Spice ups
5

No for the first one, didn’t even know, or to migrate it.

Missing scope under Server Options in both.

DC01
DC01435×507 34.3 KB
.

So the DHCP scope won’t come over? It transferred/populated to the 2022 from the 2012R2.

1 Spice up
6

You need to migrate DFS to DFSR. You should do some research on this.

Did you export and re-import your configuration from your older DHCP?

1 Spice up
7

No, but apparently i’ll have to. The 2022 server is still up, I can export, then import. I thought it would transfer/populate over.

1 Spice up
8

DHCP does not replicate.

It should be a separate system.

You will also need to adjust DNS on the scopes if your IPs have changed for DNS.

1 Spice up
9

Good thing I asked, I was going to do a MS ticket. IPs are staying the same so good to go with DNS other than pointing to the new 2025 server.

1 Spice up
10

Slight correction - FRS to DFSR. If we’re talking about migration of SYSVOL replication.

To migrate DHCP, you either have to export/import, or setup DHCP failover (and then break it, and setup again - per migration).

Always make sure to check that DHCP options (at the server and scope levels) actually did transfer over (especially if rebuilding the DHCP failover - I think options don’t transfer).

1 Spice up
11

You are correct, apologies, DFS is a sofa / couch company in the UK, clearly their adverts (commercials) are having an impact.

12

If you right click the ‘IPv4’ does the option for scope not appear?

have you connected to the correct server? right click ‘DHCP’ at the top of that screen and add the current DHCP server.

DHCP is a role - it is not part of core AD - do not expect it to migrate itself.
If you need to move DHCP from one server to another you need to migrate - the simplest method is add the new server as failover partner, then remove old.

1 Spice up
13

One other question, it looks like DNS came over to the new server or is there anything I have to do to migrate that?

14

Active Directory data, and DNS (because DNS is so tightly integrated with Active Directory) are automatically replicated when you promote a new domain controller. Other roles: DHCP, Global Catalog, FSMO roles, etc, need to be moved independently.

15

Thanks, just wanted to confirm. Want to finish this server migration from 2012 (did a 2022 jump server) to 2025, just need to finish configuring DHCP and i’m done.