Skip Navigation

Startup

When the desktop app starts for the first time, it performs the following actions:
  1. Look for the 
    AtHoc
    [edition] user key under HKCU.
    1. If the key does not exist, it is created using values from the machine key which was created during installation:
      HKLM\Software\SysWow6432Node\
      AtHoc
      [edition]
      .
    2. If the key is present, it reads several values to prepare for communication with the server: alternateBaseUrlIndex, BASEURL or alternateBaseUrl(n), PROVIDER ID, TOKEN, and UID.
  2. Create Start menu shortcuts for the generic desktop app edition (
    AtHoc
    [edition] Desktop).
  3. Get the base URL. Attempt to connect to the server and request baseurl.asp passing two parameters on the query string: organization ID and a random string created from a new GUID.
  4. Complete a Sign on (SO).  The first SO after installing the desktop app passes a negative PID in query string parameter 00 and 0 in parameter 2. The server returns the user ID token, session ID, and provider. The desktop app passes the user ID and token in subsequent SO operations. If SO is successful, the desktop app creates a new Start menu folder with the name of the organization, deletes the contents of the generic client Start menu, and creates new shortcuts in the new folder.
    Any shortcuts that are added to the “
    AtHoc
    [edition] Desktop” shortcut folder are moved to the organization-named shortcut folder when the desktop app restarts.
  5. Create data files. Data files are updated during operation. For example, when an alert is received or when a GU occurs. Data files are replaced each time the desktop app starts. Data files are stored in the user folder:
    C:\Users\<user>\AppData\Local\
    AtHoc
    [edition]
    Each time the client starts it deletes the files in 
    C:\Users\[profile name]\AppData\Local\
    AtHoc
    [edition]
     and downloads new copies.