Jump to content

TrevorKillick

Administrators
  • Posts

    780
  • Joined

  • Last visited

  • Days Won

    33

Posts posted by TrevorKillick

  1. @Cizzling

    At this moment both are not possible, however, supporting multiple teams is the next highest priority change in the backlog for Live Chat. This will likely be done using Service Domains and something similar to service subscriptions the exact details of this have not been decided on yet but when support for multiple teams is provided is very likely going to be possible to restrict who has access.

    Kind Regards

    Trevor Killick

    • Thanks 1
  2. @Lyonel

    Perfect thank you, looking at the code and the Github docs the AssetTypes section has changed in recent versions of the tool to the following format:
     

    "AssetTypes": [
        {
            "AssetType": "Server",
            "Query": "AND OASysEncl.ChassisTypes0 IN (2, 17, 18, 19, 20, 21, 22, 23)",
            "AssetIdentifier": {
                "DBColumn": "MachineName",
                "Entity": "Asset",
                "EntityColumn": "h_name"
            }
        },
        {
            "AssetType": "Laptop",
            "Query": "AND OASysEncl.ChassisTypes0 IN (8, 9, 10, 14)",
            "AssetIdentifier": {
                "DBColumn": "MachineName",
                "Entity": "Asset",
                "EntityColumn": "h_name"
            }
        },
        {
            "AssetType": "Desktop",
            "Query": "AND OASysEncl.ChassisTypes0 IN (3, 4, 5, 6, 7, 12, 13, 15, 16, 17)",
            "AssetIdentifier": {
                "DBColumn": "MachineName",
                "Entity": "Asset",
                "EntityColumn": "h_name"
            }
        },
        {
            "AssetType": "Virtual Machine",
            "Query": "AND OASysEncl.ChassisTypes0 = 1",
            "AssetIdentifier": {
                "DBColumn": "MachineName",
                "Entity": "Asset",
                "EntityColumn": "h_name"
            }
        }
      ],

    If you update this part of the configuration file it should resolve this new error you are seeing.

    Kind Regards

    Trevor Killick

  3. @Aaron Summers

    So the list of background jobs is maintained only in server memory so when the service get an automatic update and restarts the list is cleared. There have not been any updated recently so not sure when this list has cleared, you can re-run the index with "new" only option and it should continue where it left off if it had not already completed. 

    Kind Regards

    Trevor Killick

  4. @chathway

    That's great, with regards to the new line characters I have added a new Pre Import action of 'Trim' which will remove any pre and post whitespace as well as any new lines inside the string, this is available in the latest Import tool I just need to get the Hornbill Administration update out so you can select the action. 

    I will post back once this is available.

    Kind Regards

    Trevor Killick

  5. @chathway

    Apologies the error was a crash due to a coding error for handling invalid regex, the latest version 3.1.2 has been released this morning with a fix: https://github.com/hornbill/goLDAPUserImport/releases/tag/v3.1.2

    The errors you should have been getting for this are:

    2018/08/13 08:07:36 [ERROR] Regex Error: error parsing regexp: invalid or unsupported Perl syntax: `(?=`
    2018/08/13 08:07:36 [ERROR] Regex Error: error parsing regexp: invalid or unsupported Perl syntax: `(?<`

    GoLang the language used to build the import tool does not support these regex functions. 

    I managed to get both Department and Sub-Department matching with the following:

    :(.*?)(?:,[A-Z]+=|$)
    ^[^:]+

    Screen Shot 2018-08-13 at 08.29.20.png

    As for the carriage return issue I tested this on Friday when Dan mentioned you were having issues replacing them have you got a text extract from AD containing an example of the text you are trying to edit?

    Kind Regards

    Trevor Killick

  6. @Paul Alexander

    The Server will mark any email where one or more recipients failed to receive the email as unread, this indicator is shown with the red error against the Sent Items folder, it currently is also possible to manually mark an email is unread which will also add to this counter, if you check the unread items in the folder you can find out if there were any errors for any of the recipients with the colour of the envelope next to each recipient any with a red folder encountered an error.

    Kind Regards

    Trevor Killick

  7. @Richard Williams

    There is a wiki page here: https://wiki.hornbill.com/index.php/Shared_Mailboxes

    1) In Hornbill Administration go to System -> Email -> Shared Mailboxes

    2) Select the shared mailbox with the issue

    3) Select Inbound Mail Services tab

    4) Click on the pop or imap service and in the dialogue you can change the username and password, there is also a test button that should verify the credentials.
    Screen Shot 2018-08-08 at 13.09.52.png
    Kind Regards

    Trevor Killick

  8. @HGrigsby

    A fix is due in the next Server release in the meantime you can prevent reports being run multiple times by manually removing the erroneous duplicate scheduled jobs.

    1) In Hornbill go to the Menu -> Home -> Scheduled Job
    Screen Shot 2018-08-08 at 11.44.06.png

    2) In the List of Scheduled jobs find the name of the report in question

    3) Hover the mouse of the jobs and you will see the delete button

    Screen Shot 2018-08-08 at 11.44.24.png

    They are ordered from oldest to newest and you will want to keep the last scheduled job that was a duplicate of if there are three in the list only delete the first two going top down leaving the last record in the list.

    You may notice duplicates for other reports, these can have the same workaround applied if required.

    Kind Regards

    Trevor Killick

  9. 16 minutes ago, Victor said:

    So my graphics card is vintage now... it should be worth more than a new one then!!!

    My Mac has a 780... 

    @Dan Munns Nice rig, not going to wait for the price drop after the next gen GTX cards drop? 

×
×
  • Create New...