Ran into this about 12 years ago. A guy on the dev team decided to setup his own DHCP server. Screwed up all sorts of stuff. Can't remember for sure what we did, but I think after we realized that it wasn't actually an issue with our known DHCP servers, we decided to talk to the dev team and found out that is what he had done.
It amazes me how many people just don't think about it - they have a problem, they think they know how to solve it, and just slap something onto the network.
While this was my initial thought as well, he has asked about doing this simultaneously. Which fog generally isn't "all at once go".
It kind of is...I was using FOG to do multicast imaging 7 years ago. We're talking 30-60 machines at a clip.
Sure it can do it but that doesn't mean that you should do it. It's about network performance and if you're not setup for it you'll encounter massive slowdowns
Mutlicast is the way to go. You can even do it over broadcast domains. It sounds like you didn't have multicast configured correctly? Even doing 60 machines we didn't see any network slowness associated with imaging.
I think your knowledge of FG is not allowing you to do this, just create a new interface with the desired subnet and leave or tick DHCP option. And they you can do it what you want with it. Create an IPv4 policy to give access to internet to the new interface.
So what we are pretty sure we have narrowed it down to is a WiFi device that reports the temperature of the refrigerator to an online portal that sends out notifications when there is an out of range event.
There is an inside the fridge sensor and that sends the information to a receiver outside the fridge. The receiver part is what has the WiFi built in. I think the inside sensor to outside receiver communicate using 900 Mhz.
There are a lot of options rather than spending weeks figuring out such a dumb issue.
Having to bring in a local tech or get a swing machine are actually much more intensive than looking at it remotely for a while. But seems doubtful that it will take weeks. Only has had a few minutes of being looked at, and only today.
Oh, didn't realize it was like that. No local IT, no other available infrastructure or anything kind of limits things a lot.
Yeah, a LOT. If we were local and it was one of two (or more) machines, yeah, we'd happily reinstall. As it is, we are scared of the backup device failing. Which isn't terrible as it is ONLY a backup device. But taking the server offline... we are pretty dependent on it.
I have some warnings and errors in the event viewer that I'm going through now. Is there any reason to have IPv6 enabled if we're not using it? A lot of warnings in there about IP6 supposed to be static only.
I wouldn't disable ipv6 unless you are unable to find and fix the real root cause of an issue in which disabling ipv6 may mask.
The whole crux of my ask was - the desire to buy as few Windows Server CALs as possible.
This is unrelated to the question asked, though.
you know i have noticed you and dash really communicate differently. not good or bad, just different. then you both have trouble understanding the other. from the many threads i have read with you two, that is the common theme i have seen.
I'd assume part of it is that I am highly literal. That tends to be a root of many communications issues for me in general.
yeah i think your right you are literal. i had to adjust my communication with you. that was my fault though, i am used to having to be so unliteral with my users because i would lose them that i got into that bad habit lol. i know for me, i was not explaining my thoughts in a well laid out way and that made me harder to understand and threw you off. did i do better that time?
So coming back to this (because I was setting some more stuff up), it seems that Windows DHCP Server does understand the RFC, that is why it actually sees and uses the entire machine ID sent by default.
It is other devices like my EdgeRouters that I have to use the MAC address.
The only problem with the machine ID scheme is that I have no idea what it is before the machine is created.
Granted this is mostly my problem because I always use DHCP reservations instead of static IP addresses (evil fucking things, those).
I continue to force the new systems to use the hardware ID, because I want to only track the MAC address hex info.