Hello ITNinja,

We're using AD (LDAP) to import our users into the Kace. A problem we have ran into is that we use both the mail attribute and the proxyaddresses attribute in AD.

We use Google Apps For Education as our email providor and the way it works is the mail attribute is used to create the user account and the proxyaddresses is used for all the user aliases. Of which every user has at least one alias. Basically the account is the user staff code and the proxyaddresses is the actual email address that the user uses when emailing. 

Now I've tried setting the mail attribute in Kace to import from the proxyaddresses in AD and it still rejects the mail as an unknown user:

It's as though the Kace is comparing my entire reply to field from my replied email rather than parsing out the email address. 

Thank you for submitting a problem ticket. I was unable to find you as
'Tyler Grusendorf <tgrusendorf@croftonhouse.ca>' in my list of authorized
users, so I was unable to log your problem into the system. Please logon
directly via http://support.croftonhouse.ca/ and submit your problem there
or contact your system administrator for access to the help system.

> From: Tyler Grusendorf <tgrusendorf@croftonhouse.ca>
> Date: Fri, 13 Sep 2013 11:53:32 -0700
> To: IT Support <ITSupport@support.croftonhouse.ca>
> Subject: Re: [TICK:245] NEW TICKET: Test


So my Question(s):

First off Is there a way to have the Kace map both the mail attribute and proxyaddresses attribute to the mail attribute in Kace during import (or a custom rule maybe?)

Secondly is my full reply to name reply from google being parsed or what?


Any help would be appreciated!


1 Comment   [ - ] Hide Comment


  • We have just went live with the K1000 and are experiencing these same issues since we are also a Google Apps customer. Did you ever find a solution?
    • Unfortunately No.
      The only thing I could do is set default send as email (in Google using the mail API) and import only the primary email alias from AD. But then every time I import I have to go though the list of users with several aliases and fix them in Kace. Even this way our results would vary if users changed their send as address between API pushes.

      We have pretty much abandoned the ticket by email and tell everyone to login to the web interface to submit a ticket.
Please log in to comment

Answer this question or Comment on this question for clarity



For your first question, I've seen it done, but it took KACE support (professional services) making a change on the back end.  Not sure about the second question.

Answered 09/16/2013 by: jknox
Red Belt

Please log in to comment