| Anonymous | Login | 2024-04-25 10:03 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0014281 | ClearCenter | app-active-directory - Active Directory Connector | public | 2017-04-10 07:49 | 2018-10-30 19:47 | ||||
| Reporter | dloper | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | feature | Reproducibility | always | ||||
| Status | resolved | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 7.3.0 Updates | ||||||||
| Target Version | 7.6.0 Updates | Fixed in Version | 7.4.0 Updates | ||||||
| Summary | 0014281: Test time on target server before domain join and abort with warning if the time drift exceeds 1 minute. | ||||||||
| Description | Time synchronicity is crucial to keeping AD connected as is DNS a test mechanism should be made to test both DNS and time before a domain join and a troubleshooting button to validate DNS and time should be included in the app to limit support tickets that arise when the customer's equipment drifts in DNS resolution or time. The following test can be performed against the time server of the AD machine using CIFS: net time -S server_name_or_IP The result is automatically translated to the local time zone so it should match the 'date' command except for the timezone in the date command. For example, side by side results can be produced by the following: net time -S 192.168.1.10 && date | cut -f 1,2,3,4,6 -d ' ' | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0005341) dloper (administrator) 2017-04-11 12:21 |
abs () { [ $1 -lt 0 ] && echo $((-$1)) || echo $1; } && abs $(expr $(date -d "$(net time -S $(egrep "^password server" /etc/samba/smb.conf | awk -F" = " '{ print$2 }'))" "+%s") - $(date "+%s")) if the result is greater then 60 then there is a problem. |
|
(0005551) user2 2017-05-03 14:20 |
There's no timezone information returned. That makes time comparisons dodgy at best. The check will still be done, but it will be non-fatal. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2017-04-10 07:49 | dloper | New Issue | |
| 2017-04-11 12:21 | dloper | Note Added: 0005341 | |
| 2017-04-25 20:13 | user2 | Status | new => confirmed |
| 2017-04-25 20:37 | user2 | Status | confirmed => resolved |
| 2017-04-25 20:37 | user2 | Fixed in Version | => 7.3.0 Updates |
| 2017-04-25 20:37 | user2 | Resolution | open => fixed |
| 2017-04-25 20:37 | user2 | Assigned To | => user2 |
| 2017-05-03 14:20 | user2 | Note Added: 0005551 | |
| 2017-08-12 18:45 | user2 | Target Version | 7.3.0 Updates => 7.4.0 Updates |
| 2017-08-12 18:45 | user2 | Fixed in Version | 7.3.0 Updates => 7.4.0 Updates |
| 2018-07-16 12:59 | user2 | Target Version | 7.4.0 Updates => 7.5.0 Updates |
| 2018-10-30 19:47 | user2 | Target Version | 7.5.0 Updates => 7.6.0 Updates |
|
Issue History |