Autopopulate Outlook 2000 Login Information

[Lori]

I had posted this question back in 12/2007 & got a reply that it's not
"possible unless the PC is in the same domain as the Exchange server or the
person logs into Windows with the same credentials as used for the Exchange
mailbox." Since so much time has passed I thought I'd re-post & see if any
work-arounds have developed since then...:

I have a Win2K PC in a workgroup running Office 2000. I have a domain with
an Exchange server which this PC accesses via Outlook 2000. (Note: Joining
the domain is NOT an option.)

I would like to add Outlook to the Startup folder so it launches
automatically on reboot (the users have a penchant for rebooting the PC even
though they've been told NOT to). However, when I launch Outlook it prompts
for the login, password & domain. The people using the PC are not allowed to
have this information. And herein lies the problem.

Is it possible to somehow auto-populate this information within Outlook so
it will launch AND LOGIN on its own!?

Thanks in advance for your suggestions!

 

[neo [mvp outlook]]

Setting a couple of registry keys can populate the username and domain, but
not the password. Since you mention that this should always be a
stand-alone machine, have you tried this type of setup to see if you get
your desired results?

1) On the Win2K machine, set the Workgroup name the same as the NETBIOS name
of the domain.

2) The auto-logon id you use on the workstation should match an account on
the domain.

3) The password on the Win2K local account must match the password on the
domain account.

Other than that, I'm assuming that your environment allows NTLM
authentication.

 

[Lori]

1, 2 & 3 - No can do. That particular PC & a few others are running a
program which requires the workgoup name, account name & pw to be completely
different.

--
Life moves pretty fast. If you don't stop and look around once in a while,
you could miss it.

Setting a couple of registry keys can populate the username and domain, but
not the password. Since you mention that this should always be a
stand-alone machine, have you tried this type of setup to see if you get
your desired results?

1) On the Win2K machine, set the Workgroup name the same as the NETBIOS name
of the domain.

2) The auto-logon id you use on the workstation should match an account on
the domain.

3) The password on the Win2K local account must match the password on the
domain account.

Other than that, I'm assuming that your environment allows NTLM
authentication.