Category:DRUSHTI: Difference between revisions
Created page with "category:Tetra Clients category:DRUSHTI ==DRUSHTI KT Session 13-July-2026 - Tetra Support Staff - TAKSHAY== <HTML5video type="youtube" width="640" height="480" autop..." |
Add YouTube video summaries and fix broken video embeds (HTML5video -> EmbedVideo) |
||
| Line 4: | Line 4: | ||
==DRUSHTI KT Session 13-July-2026 - Tetra Support Staff - TAKSHAY== | ==DRUSHTI KT Session 13-July-2026 - Tetra Support Staff - TAKSHAY== | ||
{{#ev:youtube|a08WqGbYj2I|640}} | |||
'''Video summary:''' KT session on Drushti, described as the very first BSP client Tetra ever onboarded. Unlike most BSP clients, Tetra's support scope here is narrow and specific: Drushti runs its own single Zimbra Business-edition server (Ubuntu 22) that Tetra does not manage day-to-day -- support is limited to the Zert license-monitoring agent and license-activation issues only, contacted through an intermediary (Nitin), since Drushti itself is downstream of another party in the resale chain. Covers Zert's install requirements (small VM, ~1GB RAM, 50-60GB storage, must have port 389 LDAP connectivity to the Zimbra server) and the standard fix when license usage stops reporting correctly after the client restores their Zimbra server from backup onto new hardware: since Zert licenses are tied to a device ID, the old (now-orphaned) device ID has to be deleted/deactivated in the Zimbra BSP portal and a fresh one created and reactivated for the rebuilt server. | |||
Latest revision as of 02:53, 25 July 2026
DRUSHTI KT Session 13-July-2026 - Tetra Support Staff - TAKSHAY[edit]
Video summary: KT session on Drushti, described as the very first BSP client Tetra ever onboarded. Unlike most BSP clients, Tetra's support scope here is narrow and specific: Drushti runs its own single Zimbra Business-edition server (Ubuntu 22) that Tetra does not manage day-to-day -- support is limited to the Zert license-monitoring agent and license-activation issues only, contacted through an intermediary (Nitin), since Drushti itself is downstream of another party in the resale chain. Covers Zert's install requirements (small VM, ~1GB RAM, 50-60GB storage, must have port 389 LDAP connectivity to the Zimbra server) and the standard fix when license usage stops reporting correctly after the client restores their Zimbra server from backup onto new hardware: since Zert licenses are tied to a device ID, the old (now-orphaned) device ID has to be deleted/deactivated in the Zimbra BSP portal and a fresh one created and reactivated for the rebuilt server.