1) As per the Screenshot 1 , when we have the option checked " Use default management server " and use a default Symantec LiveUpdate server checked for a group the is also using a Single GUP . Now when the clients try to download defs what will be the sequence like . Would it be like this ?
Clients will first try to download defs from the single gup configured for the respective group
If GUP is not available they will download it from the management server
If even SEPM is not availble they will get it from the Internet ?
Is this will be the sequence for downloading ?
Ans: you are spot on, first the GUP, if it fails then SEPM even if SEPM fails it goes onto Symantec Liveupdate server
2) As per the Screenshot 2 if we have unchecked the option to use Symantec LiveUpdate Server . They won't go to the internet if both SEPM and GUP is not availble and the sequence will be the same try GUP first if not availble then go to SEPM ?
Ans: Once again your are abosultly correct, First Gup if it fails then SEPM, this will go on a loop until the clients gets its updates from either one of the source
3) As per the Screenshot 3 , What are the best practices for the SIngle, Multiple and Explicit GUPs when we are talking about " Group Update Provider Settings " i.e Maximum Disk Cache size allowed for downloading Updates , Delete content if unused for (days) , Maximum number of simeltenous downloads to clients etc. Keeping into mind we will be keeping 90 content revisions on SEPM , the GUPs we have are running Server OS's and have good resources . I need to what parameters do you set for these settings and what are their benifets.
Ans: Well it depends, for Ex you a really good server as dedicated server as a GUP and have about 2 to 4 thousands of machines to be updated. I would recommend it as following.
i.e Maximum Disk Cache size allowed for downloading Updates 4 GB
Delete content if unused for (days) : 2 to 3 days
Maximum number of simeltenous downloads to clients etc: 100