Sabo

We have some users that get prompted for their Active Directory user name and password when they access the Altiris worker console. Other users don't get prompted. Does anyone have any ideas why this might be happening, or where I can begin to troubleshoot it?

Thanks in advance.

I should add that I've looked at Altiris Knowledgebase article # 20177 and it doesn't appear to be related to that as far as I can tell.

Bill Sullivan

1. Are their AD accounts in the same directory as the successful ones?
2. On their computer, are there any Kerberos errors in the event log?
3. What does the event log say when they have a failed login? (Check both security and system)

Hopefully this steers you in the right direction

Sabo

I appreciate the response. To my knowledge, most, if not all of the AD accounts are in the same directory. I haven't discerned any type of patter there. I've only looked at the event log of one machine that prompts the user for their AD name and password. I didn't see any Kerberos messages, and there were no other messages generated in either the system or security logs.

I have no idea whether this has something with the way that Altiris authenticates through AD, or if it is related to something else. I don't get prompted for my AD username and password when I access the Altiris app, some people do and others don't. The user whose machine I checked said she gets prompted once but then she won't get prompted again for several hours. So, she has to type her AD username and password once or twice a day. I'm not even sure where to check for this.

Thanks again.

vmenez

1. Your contact info for the worker is responsible in pushing the credentials to the worker list.

Is the NT id in the contact list and in the AD the same? If not,

2. Update the worker's contact info by removing the email address.

3. Create a new contact with the correct NT id and email address.

4. Edit the worker's info in the worker's list with the new NT id.

It will ask you which to use, the old credentials in the contact list or the new one. Select the new one.

That should do it I hope.

Sabo

Thanks for your response. I have all kinds of weird things going on with this authentication process. Some updates:

1) Before I was not getting prompted for credentials but some others were.
2) Last week I had some automatic updates pushed down to my machine which included something for IE.
3) After my machine rebooted I could no longer access Altiris, getting an error message of "You must use IE6 or higher" (I use IE7).
4) I uninstalled IE7 which put me back to IE6 automatically, then reinstalled IE7, then updates were pushed automatically again.
5) After this, I can access Altiris again but get prompted for my Active Directory username and password when I first log in. This did not happen before.

I hate browser-based apps. Ugh.

There is another issue as well, and I may need to just open up another thread on this, but I have another user that is unable to access Altiris through Internet Explorer at all. He gets a message stating "You are not authorized to use Helpdesk at this time". When he logs in through Firefox he can access it with no problems. When he logs into the Altiris Test server through IE he can access it with no problems. Altiris production box through IE gives him the above error message. He told me yesterday that he noticed when he logged into his My Helpdesk console that his credentials showed his publicweb AD account rather than his main AD account, which could be where the problem is stemming from. However, when I look him up under the worker screen it shows his correct AD account, not publicweb. Where is this coming from? I wish I had been involved in the initial setup of this system so maybe I would have a better understanding of how it authenticates.

If anyone has any ideas, I would greatly appreciate it.
Thanks!

TRYDL

Didnt see anyone discuss IE settings and the automatic passing of user credentials from it to IIS.

This article covers the gist of it

Configuring Internet Explorer for Automatic Logon

__________________
3rd Floor Garage Door Operator

Sabo

I've tried this on a couple of machines having the credential problem and it seems to be working. Thanks for your help.