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

ASF subversion and git services commented on VCL-1116:
------------------------------------------------------

Commit 4724fdb35dadf70e776dc77db18d9e0c64c8fea3 in vcl's branch 
refs/heads/develop from Josh Thompson
[ https://gitbox.apache.org/repos/asf?p=vcl.git;h=4724fdb ]

VCL-1116 - use database hostnames for ad joined computers

addomain.php: modified fieldDisplayName: added case for usedbhostnames

addomain.js:
-added ADdomain.prototype.colformatter to set displayed value for Use Database 
Hostnames field to 'true' or 'false'
-modified inlineEditResourceCB: always set value for usedbhostnames instead of 
only setting it when it is set to 1
-modified saveResourceCB: set usedbhostnames for the item in the dojo store 
when saving an item


> 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
>             Fix For: 2.5.1
>
>
> 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)

Reply via email to