Jump to content

OS X FQDN after moving to the cloud


Recommended Posts

Since moving to the cloud, we have multiple OS X systems that seem to revert to hostname.local instead of FQDN in the EP Console.

Under computer properties, FQDN is reflected correctly as hostname.domain. This is also reflected correctly under each system Details tab. However, the workstations still show as hostname.local in the console.

We have several tasks scheduled to rename computers based on FQDN and this works for some, but not for most. The task is configured to run against 'All'.

Any reason why they would revert to hostname.local and why the rename task doesn't work even when they have the correct FQDN in the EP Console?

Link to comment
Share on other sites

Thanks. I've already got three cases open with support for different issues and it usually takes months. I was hoping for some community feedback in the event anyone else is experiencing this issue.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...