Troubleshooting SEP client => GUP conectivity
I need some guidence with troubleshooting client to gup conecctivity.Have sep 12 clients,using multiple gup`s setting in a policy.Some clients in the branch offices download their updates from their local gup,others contact SEPM although the policy prevents failover to the SEPM.This causes problems due to the increased network traffic.I know that the first steps are pinging and telneting the GUP computer,but what next?I guess that will be using sylink monitor?
I have a couple of questions.
1.The sep client must have conectivity to the SEPM in order to download the GUP list and i know that the client keeps a copy of the list localy.Is it possible to allow access from the client to the SEPM for some period of time so that the client copies the gup list localy and then cut the comunication with the sepm.Will the client keep the local gup list forever????
2.After successfully pinging/telenting the SEPM and the GUP computer the next step is using the sylink monitor?If that`s the case should i enable sylink debugging prior to using the sylink monitor or that is just "an alternative to using sylink monitor" as described in the link below
3.Does the GUP have a local log that`s used just for that role?