Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 6291 views
  • Users 0 members are here
Options
Suggested
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

Update Manager Distribution Shares

Navar Holmes

In the Update to side is just share using the short name of the server  \\server1\SophosUpdate

On the available is the FQDN of the server \\server.domain.com\SophosUpdate

See how Sophos is 100 dependent on DNS it only makes sense to add the FQDN to the Update to side. 

We have multiple DNS servers from older domains and some PCs in the old domains cant resolve to the short name but they can to the FQDN.

 

What is the drawback for added the FQDN?



This thread was automatically locked due to age.
Parents
  • 0

    Hello Navar Holmes,

    the Default share (\\server\SophosUpdate) is always in the Update to: pane and can't be removed.
    If your endpoints can't locate the server by its NetBIOS name you can use the FQDN, an alias, or the IPv4 address in the Updating Policy. A share used in one of the policies is automatically added to the Available list - but as in your case these names point to the Default share you don't have to shouldn't add them to the Update to: list (this could even cause problems and definitely adversely affects performance).

  • 0 in reply to QC

    Confused.  You say I can use the FQDN but then you say don't do it as it will cause issues.

    If the NetBIOS is the default and can't be changed then it looks to me that this is a flaw as the NetBIOS should never be used, only FQDN should be used.

    Is there a way to fix this and set all configurations to FQDN?

  • 0 in reply to Navar Holmes

    Hello Navar Holmes,

    please note that there's the Update Manager (SUM) configuration with the distribution share(s) as seen from the server hosting the SUM and then there are the Updating Policies where the locations are specified as seen from the endpoints.
    If an FQDN is required so that the endpoints can locate the share - fine. Specify whatever name is suitable, you can use different names in different policies for the same physical share. But do not add these names to the Distribute to list in the SUM configuration. Still confused?

    a way to fix this
    to fix what? That the SUM configuration uses \\server\SophosUpdate\ for the default share and not \\Server.domain.local\SophosUpdate\?

    Christian

Reply
  • 0 in reply to Navar Holmes

    Hello Navar Holmes,

    please note that there's the Update Manager (SUM) configuration with the distribution share(s) as seen from the server hosting the SUM and then there are the Updating Policies where the locations are specified as seen from the endpoints.
    If an FQDN is required so that the endpoints can locate the share - fine. Specify whatever name is suitable, you can use different names in different policies for the same physical share. But do not add these names to the Distribute to list in the SUM configuration. Still confused?

    a way to fix this
    to fix what? That the SUM configuration uses \\server\SophosUpdate\ for the default share and not \\Server.domain.local\SophosUpdate\?

    Christian

Children
No Data
Unfiltered HTML