New DC, Cannot set an AS/400 profile name in Active Directory

20 pts.
Tags:
Active Directory
AS/400
It worked on our old DC. When I would right click on a user name in AD and go to Set AS/400 Profile Name it used to bring up an AS/400 Admin Console box where I could specify an accompanying AS/400 user id. After migrating to a new controller, I still get the same option (Set AS/400 profile name). However when I select it the AS/400 Admin Console box where I can specify the accompanying AS/400 user id does not appear.
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • TheRealRaven
    I don't know of any Set AS/400 Profile Name option nor any AS/400 Admin Console feature in AD nor on any DC. It seems plausible that they relate to some 3rd-party product that needs to be configured before it knows about any "AS/400" that it should communicate. It's also plausible that it can discover "AS/400s" if you take appropriate options.

    One likely possibility is that you have some product related to 'Single Sign-On' (SSO).

    What are you trying to do in AD? If you explain what you're trying to get done, maybe it'll give a clue how we can help.
    34,990 pointsBadges:
    report
  • djb387

    Let me give you some more background on this. Instead of using a NAS or a file server, we keep our home, shared and public data on the AS/400 system. It is accessed via IBM Netserver service. When users login to their PC's they run a login script.This login script performs an Active Directory lookup for the user's AS/400 profile and uses this to log in to the AS/400 for drive mappings. This  AS/400 user profile is added to the user's Active Directory account in the manner I specified in my original post.                                                                                               Since we have migrated to a new DC, I am no longer able to add this AS/400 user profile to newly created AD user accounts. The option Set AS/400 User Profile Name is there when I right-click on the AD user account-but when I click on it, it does not bring up a window where I could specify the AS/400 name like I could before. As a result I am not able to bind an AS/400 name to an Active Directory user  account, which means that the script will not run, thus  cannot get drive mappings. Hope this helps clarify what we are trying to do. Other background info if it is helpful. We migrated from a Windows 2003 DC to a Windows 2008R2 DC. I am pretty sure we don't have any 3rd party or single signon programs. I looked on our old domain controller and did not see anything. I also spoke with IBM about this and they say that all is ok on the AS/400 side. DNS is set up correctly. We verified the connection between both machines and we are also able to ping the new DC. Hope this clarifies things a bit. Thanks for your help.                     

    20 pointsBadges:
    report
  • TheRealRaven
    Then it seems that someone on your organization (or outside consultant) in the past added a custom AD attribute for this. (It's definitely not standard.) It's unlikely that anyone outside can be a lot of help without much more detail that you might not want to put in a public forum. (Maybe.)

    If you no longer have one on staff, you should find a local AD professional to look into your AD structure to see if any related forms or VB or PowerShell (or whatever) scripts can be located, and then determine how to reactivate them.

    Of course, the original work should have been documented. Those docs should be the first thing you look for.
    34,990 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: