Where do I start with replacing the whole MS AD stack
-
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Dashrender said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
@Dashrender said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
@JaredBusch said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.
Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.
Once that is done, you can work towards changing DNS.
yeah, that will take awhile.
really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?
It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.
You could just create reservations in the new DHCP server and have the existing windows DHCP server not renew requests.
He's changing static IP'ed devices to DHCP with reservations.
Are you agreeing with me or stating something Donohue is doing?
he's telling you what I need to do.
I think you missed my point.
You can create a reservation on the new DHCP server and have it waiting, turn off the old DHCP server. Then just go to the clients and set them to DHCP.
Walah, reservations active.
OK sure, that's true - but he also has to change all of the things that point to the old IP to point to the new one - or at least point to a DNS name if he wasn't using that before, which seems like he wasn't, otherwise the static or dynamic IP wouldn't matter.
-
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Dashrender said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
@Dashrender said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
@JaredBusch said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.
Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.
Once that is done, you can work towards changing DNS.
yeah, that will take awhile.
really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?
It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.
You could just create reservations in the new DHCP server and have the existing windows DHCP server not renew requests.
He's changing static IP'ed devices to DHCP with reservations.
Are you agreeing with me or stating something Donohue is doing?
he's telling you what I need to do.
I think you missed my point.
You can create a reservation on the new DHCP server and have it waiting, turn off the old DHCP server. Then just go to the clients and set them to DHCP.
Walah, reservations active.
DHCP has nothing to do with it.. FFS....
He has all the devices (well a lot) with static IP addresses.. Having any DHCP server running, Windows or otherwise, does not affect how long it will take him to update all those devices.
-
@JaredBusch said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Dashrender said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
@Dashrender said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
@JaredBusch said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.
Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.
Once that is done, you can work towards changing DNS.
yeah, that will take awhile.
really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?
It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.
You could just create reservations in the new DHCP server and have the existing windows DHCP server not renew requests.
He's changing static IP'ed devices to DHCP with reservations.
Are you agreeing with me or stating something Donohue is doing?
he's telling you what I need to do.
I think you missed my point.
You can create a reservation on the new DHCP server and have it waiting, turn off the old DHCP server. Then just go to the clients and set them to DHCP.
Walah, reservations active.
DHCP has nothing to do with it.. FFS....
He has all the devices (well a lot) with static IP addresses.. Having any DHCP server running, Windows or otherwise, does not affect how long it will take him to update all those devices.
Or the things that point to them.
-
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
Walah, reservations active.
-
@scottalanmiller said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
Walah, reservations active.
-
@scottalanmiller said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
Walah, reservations active.
Tomato tomatto
-
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
Tomato tomatto
Chaning the pronunciation does not change the spelling.
-
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@scottalanmiller said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
Walah, reservations active.
Tomato tomatto
-
I just want to confirm, the general idea is that the DHCP server is static, and EVERYTHING else is just a reservation?
-
@Donahue said in Where do I start with replacing the whole MS AD stack:
I just want to confirm, the general idea is that the DHCP server is static, and EVERYTHING else is just a reservation?
Why statically assign at all? You're in a tight spot because you've already statically assigned a lot of devices.
Instead, just create reservations and let DHCP handle it from there.
-
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Donahue said in Where do I start with replacing the whole MS AD stack:
I just want to confirm, the general idea is that the DHCP server is static, and EVERYTHING else is just a reservation?
Why statically assign at all? You're in a tight spot because you've already statically assigned a lot of devices.
Instead, just create reservations and let DHCP handle it from there.
I dont want to be static anymore, I want to use reservations. are you saying yes to my question above?
-
@Donahue said in Where do I start with replacing the whole MS AD stack:
I just want to confirm, the general idea is that the DHCP server is static, and EVERYTHING else is just a reservation?
Not everything.
You AD server is not. That is just begging for trouble in the super rare case that the DHCP is not available when it boots.
Your hypervisor should not be either. Then your router. Those things are about it.Then you make reservations for the things that need a fixed IP like application servers, storage devices, and printers.
Finally you make a reservation for things you simply want in a certain place like switches and such.
Then just let DHCP go wild for the rest. Because there is seriously no reason that you need to care about desktops and desk phones, etc.
-
@Donahue yes, don't assign IP addresses manually on your systems.
Use DHCP Reservations instead.
-
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Donahue yes, don't assign IP addresses manually on your systems.
Use DHCP Reservations instead.
That's what he said. I have no idea WTF you are going on about.
-
@JaredBusch said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Donahue yes, don't assign IP addresses manually on your systems.
Use DHCP Reservations instead.
That's what he said. I have no idea WTF you are going on about.
He's going in circles and not understanding what is being said. Hence it gets explained in a different manner.
-
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@JaredBusch said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Donahue yes, don't assign IP addresses manually on your systems.
Use DHCP Reservations instead.
That's what he said. I have no idea WTF you are going on about.
He's going in circles and not understanding what is being said. Hence it gets explained in a different manner.
I understood @JaredBusch, I dont think you understood me.
-
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@JaredBusch said in Where do I start with replacing the whole MS AD stack:
@DustinB3403 said in Where do I start with replacing the whole MS AD stack:
@Donahue yes, don't assign IP addresses manually on your systems.
Use DHCP Reservations instead.
That's what he said. I have no idea WTF you are going on about.
He's going in circles and not understanding what is being said. Hence it gets explained in a different manner.
WUT?
-
Apparently Fortigate wont let me create reservations outside of the lease pool. I even tried setting an excluded range, but it simply will not allow me to do it.
I can either:
- Get a different DHCP server
- Abandon using reservations
- Open the lease pool to the entire scope and live with the mixed results
- Open the lease pool to the entire scope and create 254 dummy reservations to be edited later.
My plan was to have 10.0.0.1/22 as my network, with the lease pool of 10.0.1.0 thru 10.0.3.254 and 10.0.0.2 thru 10.0.0.255 reserved for all these devices using reservations.
-
@Donahue said in Where do I start with replacing the whole MS AD stack:
Apparently Fortigate wont let me create reservations outside of the lease pool. I even tried setting an excluded range, but it simply will not allow me to do it.
I can either:
- Get a different DHCP server
- Abandon using reservations
- Open the lease pool to the entire scope and live with the mixed results
- Open the lease pool to the entire scope and create 254 dummy reservations to be edited later.
My plan was to have 10.0.0.1/22 as my network, with the lease pool of 10.0.1.0 thru 10.0.3.254 and 10.0.0.2 thru 10.0.0.255 reserved for all these devices using reservations.
- replace fortigate
-
@Donahue said in Where do I start with replacing the whole MS AD stack:
Apparently Fortigate wont let me create reservations outside of the lease pool. I even tried setting an excluded range, but it simply will not allow me to do it.
I can either:
- Get a different DHCP server
- Abandon using reservations
- Open the lease pool to the entire scope and live with the mixed results
- Open the lease pool to the entire scope and create 254 dummy reservations to be edited later.
My plan was to have 10.0.0.1/22 as my network, with the lease pool of 10.0.1.0 thru 10.0.3.254 and 10.0.0.2 thru 10.0.0.255 reserved for all these devices using reservations.
Even windows lets you make the full scope and then blackout ranges.
Most Linux systems let you make a reservation anywhere within the subnet of the scope, even outside of the start and stop range also specified.
