Answered by:
Account Prepopulation

Question
-
Does anyone have a short list of what is required for Communicator or the Live Meeting client to automatically determine account information?
I am asking because on some of our test computers, everything was "automagically" picked up (I'm not even sure from where, possibly Outlook or the AD?), and getting Communicator and Live Meeting up and running was as simple as running the setup program and launching the apps. No need to enter sign-in information or credentials.
We have the autodiscover information correctly set in DNS, yet on some computers it asks for the sign-in name as well as account information in the client software, while others require nothing. In a third case, no information was necessary to launch and sign in to the Communicator client, but it then prompted for credentials when expanding a group.
One thing I have noticed is that the magic doesn't mappen on PCs that once had the Communicator 2005 clients installed.
So basically, does anyone have any experience and can share their thoughts? Ideally I'd like all of our domain computers automatically pick up sign in information and never have to rely on users to type in their credentials.
Thursday, May 31, 2007 2:42 PM
Answers
-
Hi,
One of our users having the issue discovered a potential solution that I haven't tested yet.
We noticed in the stored credentials, it was prepopulating the username field with lwd01-w2k\username, where lwd01-w2k is our domain's NETBIOS name. She replaced the credentials in the logon window to lwd01.lwa\username, where lwd01.lwa is our domain's DNS (Windows 2000+) name. She then reported that since then, Communicator has been logging in automatically.
Monday, July 16, 2007 5:35 PM -
I just wanted to follow up on my previous post. Yes, this solution worked. I suppose the old version stored the NETBIOS domain name in the registry or elsewhere that Communicator picked up on. Putting in the Windows 2000 domain name corrected the issue.
Old username stored: LWD01-W2K\username - password prompt appeared at logon
New username stored lwd01.lwa\username - automatically logged in
Friday, July 27, 2007 2:09 PM
All replies
-
I know that computers that are part of the domain should auto logon. Are the computers that prompt for credentials joined to your domain?Friday, June 1, 2007 6:22 AM
-
Yes, the computers are domain members. I think it has something to do with the fact that Communicator 2005 was previously installed on the PC. Anything I could check in the registry?Friday, June 1, 2007 4:33 PM
-
I have been trying to find out if there were any issues, with having 2005 previously, but have not so far. I myself have had 2005 and 2007 on the same machine before with no problems.
Can you give an update on your status? Have you tried anything else?
Monday, July 2, 2007 8:11 PM -
Hi Kevin,
Can you let us know the status of your issue?
Monday, July 9, 2007 10:33 PM -
Hi Kevin,
Can you lat me know your current status?
Friday, July 13, 2007 8:48 PM -
Hi,
One of our users having the issue discovered a potential solution that I haven't tested yet.
We noticed in the stored credentials, it was prepopulating the username field with lwd01-w2k\username, where lwd01-w2k is our domain's NETBIOS name. She replaced the credentials in the logon window to lwd01.lwa\username, where lwd01.lwa is our domain's DNS (Windows 2000+) name. She then reported that since then, Communicator has been logging in automatically.
Monday, July 16, 2007 5:35 PM -
I just wanted to follow up on my previous post. Yes, this solution worked. I suppose the old version stored the NETBIOS domain name in the registry or elsewhere that Communicator picked up on. Putting in the Windows 2000 domain name corrected the issue.
Old username stored: LWD01-W2K\username - password prompt appeared at logon
New username stored lwd01.lwa\username - automatically logged in
Friday, July 27, 2007 2:09 PM