I've two use cases in which one of our customer asking and wondering:
What differs BigFix OSD from Microsoft SCCM OSD, and what makes me to choose and prefer to use BigFix OSD rather than Microsoft SCCM OSD.
If I have some relay in some location or a VLan, then this relay for some reason has been moved to another location with different IP and different VLan, so what happens and the impact on the clients assigned to that relay in the old location.
Can’t help you with the 1st, don’t really have/use OSD, nor have any knowledge of SCCM OSD. As far as the second, it's nearly impossible to judge based on the info you’ve provided… How is the relay assigned? Is it with “manual selection or automatic”? If Automatic, do you use relay affiliations? If yes, do you assign relays to any (add “*” as part of the relay & client affiliation); Does the new location & IP have connectivity to the clients? Do you use nameoverride setting on relay to force config via IP or do you have it as hostname? Was the DNS record of the relay server updated, so all that endpoints resolve the hostname to the new IP address?
Those are just the question I can think of off top of my head that will have an impact to how things would work and essentially change the answer to your question… Provide a bit more detailed description about your environment’s setup and we should be able to give a definitive response.
Then it should continue to work, assuming the traffic is allowed. Obviously, if you now have a closer relay you may want to consider repointing them but they should continue to work as are.
You mean that they will continue to reach and connect to that relay even if it is far away. And in that case the traffic will be increased and then the relay lost its advantage to reduce the network load.
If I'm wrong correct me.
Yes, it would but that is assuming the traffic is allowed: i.e. all endpoints that point to the relay retain traffic to the new IP - whichever port you are using (default 52311) over tcp & udp + icmp bidirectionally; then it will not have a problem to continue to work as is. That said, if there is big network latency you may want to review as you may see delays with downloads and such but from pure connectivity standpoint if traffic is there, it should work as is.
Generally, BigFix OSD requires less maintence of the Bare Metal Server, especially if you are deploying a large number of them to handle deploying the same images into multiple regions.
BigFix synchronizes the images on Bare Metal Servers using the same relay download.hoerarchy as other patch and SWD content, so there's no need for additional WAN ports or replication to a single-source.
BigFix OSD also supports deployment of Linux images in addition to Windows.
The customer told me that the MS SCCM is also able to deploy both Linux and Windows as a package, so this point doesn't matter for him. So, I need a reply more persuasive and more reliable to end this debate.
I think you should probably reach out to your Technical Advisor, they may be able to put together a better head-to-head comparison. If you don't know who your TA is, send me a private message and I'll help figure that out. I expect they will have a better comparison between OSD and SCCM. Do you think that'll be helpful?