PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 12/14/2015 11:48 AM by  Greg Moeller
Trying to do the Infor10 Upgrade
 5 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Greg Moeller
Private
Private
Veteran Member
(4034 points)
Veteran Member
Posts:1438


Send Message:

--
12/02/2015 11:04 AM

    Old 9.0.1 system Solaris Unix and Oracle database

    New 10.0.8 system Windows and SQL Server database

    We've run into a huge snag.  The old way, we used to store our employee number in an unused field in our corporate AD structure.

    After conversion, we are running into the fact that our employee numbers are not in the samacctname field, and we can't just switch to use the samacctname field because of some of the users being > the max number of characters allowed by the Lawson OS identifier.

     

    Anyone else struggle with this?  What was/were your solution(s)?

     

    TIA,

    -Greg

    Greg Moeller
    Private
    Private
    Veteran Member
    (4034 points)
    Veteran Member
    Posts:1438


    Send Message:

    --
    12/02/2015 11:22 AM
    To clarify a little.

    We used the corporate AD to log into the network, but we found that the bind would work on a different field, so decided to convert all of our employee logins to Lawson to use the actual employee ID.

    It's been working great!!! But apparently version 10 comes with some other "requirements"??
    Kwane McNeal
    President
    Private
    Veteran Member
    (1380 points)
    Veteran Member
    Posts:460


    Send Message:

    --
    12/02/2015 11:48 AM
    Greg, there's more to this. Call me 505-433-7744
    Kwane McNeal
    President
    Private
    Veteran Member
    (1380 points)
    Veteran Member
    Posts:460


    Send Message:

    --
    12/02/2015 11:57 AM
    Just left you a voicemail on your office line with some info, and feel free to call
    Greg Moeller
    Private
    Private
    Veteran Member
    (4034 points)
    Veteran Member
    Posts:1438


    Send Message:

    --
    12/02/2015 4:17 PM
    Thanks for your input, Kwane!!
    Greg Moeller
    Private
    Private
    Veteran Member
    (4034 points)
    Veteran Member
    Posts:1438


    Send Message:

    --
    12/14/2015 11:48 AM
    Just to update everyone:
    We are able to proceed binding to an alternate attribute in our corporate AD structure. With a slight caveat. We still have to use the actual SamAcctName as the identity for the OS.
    We will now see the SamAcctName in the print managers, etc. But we'll still be able to maintain the login of employee number.
    You are not authorized to post a reply.