j-gray 33 Posted October 2 Share Posted October 2 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? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,935 Posted October 2 Administrators Share Posted October 2 Please raise a support ticket for further investigation of the issue. Quote Link to comment Share on other sites More sharing options...
j-gray 33 Posted October 3 Author Share Posted October 3 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. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.