This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Will non-managed endpoints (faculty, staff, students personal computers) update Primary location from new package?

Our university has an update server (websum) to update off campus, non-managed, endpoints.  The primary location address for these endpoint is websum.win.university.edu/.

This update server was publically accessible until a recent change in our network.  We now have nat in place so a 1 to 1 IP reservation has been setup for this server that includes its internal address and external address.  Now the non-managed endpoints off campus should get their updates from websum.university.edu instead of websum.win.university.edu.

I have created a package to reflect the new update location but exsiting clients are not updating the primary update location to point to new server.  As of now, the only fix I have thought of is installing the new package ontop of the current installation.

Thanks,

Dusty



This thread was automatically locked due to age.
  • Hello Dusty,

    act fast- think later ... sorry, no, absolutely no offence meant [:D]
    Problem is, you have to 2) provide something (a script, documentation - but you probably don't want to give out the clear-text password) to change the update location on the unmanaged endpoints and 1) to communicate this.

    Not addressing either: I'd use a temporary DNS alias for websum.win.university.edu which points to websum.university.edu. Probably IT (or whoever)  wants to get rid of the win subdomain. A possible way is to configure the CID with an updating policy (sauconf.xml). Endpoints should apply this policy on the next update. Except for some oddballs most endpoints will stop using the old name within days. But this is only relevant if you can't keep the alias.

    Christian

  • Christian,


    Thanks for the possible solution.  I will look into it and will report with results.