• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 9172, created on Oct 20, 2010, last review on Mar 3, 2016

  • Applies to:
  • Operations Automation
  • Business Automation
  • Odin Business Automation Standard
  • Plesk Automation
  • Service provider products licensing

Symptoms

How do I access my Odin Request Tracker Account?

Resolution

For Parallels Desktop, Parallels Access and other Cross-Platform Applications, see this article.

  1. If you have never logged into the Odin Support Request Tracker before please, follow this link to activate your account.

    Step 1: Please enter your registered email address (the one you used to submit your support request);

    Step 2: Enter a number of any of your support tickets that have been submitted with the email address indicated under Step 1;

    Note: If you do not receive an e-mail with your ticket number after you have submitted your support request, please check your Junk E-mail folder.

    Step 3: Click on "Activate Account" button. Account activation email will be sent to you;

    Step 4: Open the email and click on the link from this email to activate your account and set your password in the Odin Request Tracker system. After you set your password, you will be automatically logged in for the first time.

  2. If you have previously logged into the Odin Support Request Tracker but forgot your password please follow this link.

    Step 1: Please enter your Login and Email address and click on "Send";

    Note: Your Login is your Email address.

    Step 2: Open the email and click on the link from this email to set up new password;

    Step 3: Enter new password (twice) and click on "Submit". New password will be saved and you will be automatically logged in.

Search Words

login to RT

Create an support account

Odin request tracker

b3c1d11fb3662455ba66138907667703 6311ae17c1ee52b36e68aaf4ad066387 198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 400e18f6ede9f8be5575a475d2d6b0a6 e0aff7830fa22f92062ee4db78133079 5356b422f65bdad1c3e9edca5d74a1ae 0fb3394a2c69b44bea0b259a86272ad9

Email subscription for changes to this article
Save as PDF