Hi
We found a possible bug.
Using ASG-RD 2015 patch 5.
If we do a .csv connection sync where the connection already exist in ASG.
Example:
ConnectionName;ConnectionDestination;ConnectionProtocol;FolderName
TEST-RDPPROTOCOL;127.0.0.1;RDP;Customer1
TEST-BLANKPROTOCOL;127.0.0.2;;Customer2
Where the protocol from the .csv in known for TEST-RDPPROTOCOL, set to RDP, but unknown for TEST-BLANKPROTOCOL, set as blank in the .csv.
ASG overwrites already set config, for the example TEST-BLANKPROTOCOL was set to SSH in ASG.
But when the sync is done with ConnectionProtocol set to blank (nothing beetween ;; ) ASG seems to hardcode RDP as some kind of default.
Ideally we would think this is intentional for new connections where the Protocol is unknown. Then it is smart to use RDP as the default protocol. However if the protocol is already configured as SSH or something else, ASG should keep that value when the sync imformation is blank.
Let me know if you did not understand the case
We found a possible bug.
Using ASG-RD 2015 patch 5.
If we do a .csv connection sync where the connection already exist in ASG.
Example:
ConnectionName;ConnectionDestination;ConnectionProtocol;FolderName
TEST-RDPPROTOCOL;127.0.0.1;RDP;Customer1
TEST-BLANKPROTOCOL;127.0.0.2;;Customer2
Where the protocol from the .csv in known for TEST-RDPPROTOCOL, set to RDP, but unknown for TEST-BLANKPROTOCOL, set as blank in the .csv.
ASG overwrites already set config, for the example TEST-BLANKPROTOCOL was set to SSH in ASG.
But when the sync is done with ConnectionProtocol set to blank (nothing beetween ;; ) ASG seems to hardcode RDP as some kind of default.
Ideally we would think this is intentional for new connections where the Protocol is unknown. Then it is smart to use RDP as the default protocol. However if the protocol is already configured as SSH or something else, ASG should keep that value when the sync imformation is blank.
Let me know if you did not understand the case