PENDING Cascade of wsus servers linked to sup

[Texmex]

Hello everyone,

I'm currently trying to get a SUP server to communicate with a WSUS server which itself is attached to another WSUS server.
So far, no problem.
For very strict security reasons, I can't access the Internet from this WSUS server close to the SUP, but I have to retrieve it via synchronization from another WSUS server.
In my WSUS close to the SUP server, I've set the Upstream server as the Internet front-end.
My plan here works very well because the WSus server close to the Internet does have Internet, and therefore retrieves an initial synchronization of metadata and datas.
The problem I'm having is that if I force a synchronization of updates in mecm, the Upstream server of the WSUS connected to my SUP changes...
I've noticed that from time to time the configuration goes away and comes back to the Upstream Mecm server (which breaks the operation of my wsus cascade).
Do you have any ideas on how to make this configuration sustainable?
I know that my configuration is particular, but for very strong constraints of security of a customer I cannot do otherwise than a solution of this type.

Thank you

 

[Prajwal Desai]

I am not sure why that configuration change is occurring in your setup. Without examining the setup, its difficult to tell. Logs can help here, but I can recommend reaching out to MS support for this issue.