Re: SBS_LOGIN_SCRIPT.bat does not run for one user on one machine only

Tech-Archive recommends: Speed Up your PC by fixing your registry

Jim Behning SBS MVP wrote:
On Sat, 12 Apr 2008 10:59:08 -0700, "kj [SBS MVP]"
<KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote:

JimJ wrote:
I have a workstation that has been in storage for a while that we
reactivated. I connected the workstation and updated everything
using my login. Everything went fine. The original user of the
workstation logged in and the SBS_LOGIN_SCRIPT.bat didn't run, none
of the printers configured and anytime they tried to access files
such as "My Documents" it asked for uname/pswd. They have full
rights to use this workstation, they can successfully log into any
other workstation without problem and anyone else can log into this
workstation (the problem child) witout problem. I force changed the
password at the server thinking that that may force the correct
login sequence, the user used the new password and then changed it
themselves and all worked well except the same problem exists. It
appears that there is something registered in the workstation that
causes a "local" login (just a guess) even though I confirmed that
the domain was listed properly on the login dialog box. Security
event registered the login.
Any suggestions??

Jim

Likely the workstation domain account is out of sync, or you added
another workstation with the same name as this one.

Either resolve the name conflict, if one exists. Or, you can switch
the workstation back to "workgroup", reboot, rejoin the domain,
reboot, and then it should work fine. This should be done only if
you originally used the wizards to setup the workstation. If not,
stop at the workgroup step and proceed to use the wizards to connect
the computer to the SBS domain.

Tidbit. Join to workgroup with lots of OKs except do not reboot. Join
to domain and then reboot. You can save a few minutes of reboot time.
Also note you need to make a local administrator account with a known
password before you start doing this just in case.
See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx

Yeah, doesn't that bite when you end up with no local admin password? Good
reminder Jim.

I've been a bit leary of doing the domain/workgrou/domain without reboots on
"real" machines, but never had one belly-up doing so in the lab. Guess I'm
being overly conservative with this as I hear this being done commonly these
days.

maybe I'll just go do a bunch of netdom remove, netdom joins until I feel
better about it.

--
/kj


.

Relevant Pages

  • Connecting a remote workstation to a domain
    ... Login as administrator on the workstation and create a VPN-connection ... remark that you will have to reboot the workstation. ...
    (microsoft.public.windows.server.sbs)
  • Connecting a remote workstation to a domain
    ... Login as administrator on the workstation and create a VPN-connection ... remark that you will have to reboot the workstation. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Login Script wont run on a particular machine
    ... Reinstalled Windows XP and everything worked ... like net use work in this workstation. ... Nothing on the SBS server event log, ... I have a particular machine that won't run a login script. ...
    (microsoft.public.windows.server.sbs)
  • Re: different environment fails to fill a dataset
    ... Andrew J. Kelly SQL MVP ... what I have done since we last talked was to create a SQL Server login ... on the test workstation. ... These are the connection strings. ...
    (microsoft.public.sqlserver.clients)
  • Re: SBS_LOGIN_SCRIPT.bat does not run for one user on one machine only
    ... password for a resource on SBS and took the option to 'remember this'. ... Cpanel, user accounts, manage passwords, clear out any remembered passwords. ... I connected the workstation and updated everything using my ... login sequence, the user used the new password and then changed it ...
    (microsoft.public.windows.server.sbs)