[jira] [Commented] (VCL-1116) use database hostnames for ad joined computers

["Junaid Ali (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/VCL-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798406#comment-16798406 ] 

Junaid Ali commented on VCL-1116:
---------------------------------

Added commit 

https://gitbox.apache.org/repos/asf?p=vcl.git;a=shortlog;h=refs/heads/VCL-1116_use_database_hostnames_for_ad_joined_computers

> use database hostnames for ad joined computers
> ----------------------------------------------
>
>                 Key: VCL-1116
>                 URL: https://issues.apache.org/jira/browse/VCL-1116
>             Project: VCL
>          Issue Type: Bug
>          Components: database, vcld (backend), web gui (frontend)
>    Affects Versions: 2.5
>            Reporter: Junaid Ali
>            Priority: Major
>
> Currently the VM's created use reverse DNS lookup to create their computer hostnames. Also the DNS suffix is set to the name retrieved using the reverse DNS lookup. For environments where the DNS domain does not match the active directory domains this can cause issues with accessing Windows Distributed File Shares (DFS). The windows client needs to use the same DNS suffix as the active directory domain.
> This fix creates a new column within the addomain table, so you can choose when you want to enable this setting (default is disabled). The web frontend has capability to toggle this setting within the ADDomain settings. 
> There is a secondary issue with the reboot subroutine where the SSH service becomes available and the management node starts working on it, but then the cygwin reset happens that causes intermittent SSH connection issues making the process unreliable. Setting the SSHD service startup mode to manual for all cases where cygwin reset will occur will overcome this issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)