Login script asking for a password...?

Questions?

What machine did you upgrade first?
What procedure did you use?

The procedure states to you need to upgrade the PDC first, and complete the installation by running the Active Directory Installation Wizard. Specifically, for domain controllers you need to use the Active Directory Installation Wizard, it installs the Active Directory service on your domain controller.

Is this heading in the right direction? If so let me know And we can do a more complete process.

yag

Sorry to say, I didn't have this problem when I upgraded so most of this is the usual script troubleshooting methods.

What happens if you excute the script manually? Does it still map the proper drivers? Add a pause to the end of the script and remove the @echo off or echo off lines so that you can trouble shoot the script further. More then likely it is a premissions problem. What happens if you map the drives by hand, i.e. net use z: \\formerbdc\share ? You can browse the former bdc shares, but can others? Is the former bdc an AD server as well? Above all else check the premissions and check other peoples accounts. Make sure to check the share and file premissions on each share.

Yager: I did upgrade the PDC first, and ran the active directory install wizard.
I then had some trouble upgrading the BDC, in fact I endded up copying all data files to the old PDC, then did a fresh install on the aborted BDC. other than that, all seemed to go well. Any Ideas?

Aaron: I didn't try mapping by hand, but I did do or try every thing else. permissions are all right(double and triple checked 'em), although I can't help but think it has something to do with rights and permissions on the old BDC...the old PDC works! I executed on multiple machine/users, same result. I executed the script after the logon(browsed to the logon.bat file and executed) The old BDC is part of the Active Directory, I originally installed the old BDC as a member server, then ran DCPROMO..thinking that might be the problem, Same result in both situations.
Thanks for the help..I'll try mapping by hand

Problem solved! It was a DNS thing. I didn;t have my DNS properly configured so the domain couldn't resolve to former BDC's netbios name ADMIN.
Thanks for the input.