Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

GUP policy conflict

Created: 15 Feb 2012 • Updated: 15 Feb 2012 | 5 comments
This issue has been solved. See solution.

Hi all,

More of a question than an issue. If I created a liveupdate policy and setup up a multiple gup policy that pointed to the hostname and the direct of the ip of the gup would this cause any issues?

Reason I'm asking is we recently had a machine that could not identify the gup from hostname as soon as we used the ip it worked fine. But on other estates we look after some of the gups do not have the pleasure of a static ip address.

Comments 5 CommentsJump to latest comment

pete_4u2002's picture

it could be hostname may not have resolved. If name resoultion is proper clients would contact the GUP on hostname.

GeoGeo's picture

I know the machine isn't resolving with the hostname that's why I'm trying to confirm that there won't be any issues with putting the hostname and ip address of same gup in the same policy. As policy donates if the machine bcomes a gup.

Please review ideas and vote there could be something useful :)

https://www-secure.symantec.com/connect/security/ideas

pete_4u2002's picture

there won't be any issue , however if the IP address changes, then the existing machine with that IP address will be GUP.

SOLUTION
GeoGeo's picture

Cheers Pete for your quick responce just wanted to confirm that.

Please review ideas and vote there could be something useful :)

https://www-secure.symantec.com/connect/security/ideas