multiple GUP scenario, SEPM update
while testing a 12.1 RU1 multiple GUP scenario I noticed that clients without a GUP provided in their subnet are waiting the time defined in the "Maximum time that clients try to download updates from a Group Update Provider before trying the default management server" and then use the SEPM for updates. Seems like if you enable multiple GUP functionality, clients they always wait if for some reason they can't use a GUP.
I thought the "maximum time" is about the client trying to connect to a non-responding GUP but not when there is no GUP provided in the subnet. When there is [EDIT] no [/EDIT] GUP in the subnet the client should use the SEPM immediately.
Question: Is the behaviour intended?
Sylink-log says "[Content] <LuThreadProc---->GUP is in startup wait. Exiting." while waiting.