SBS_LOGIN_SCRIPT.bat

Discussion in 'Windows Small Business Server' started by Manuel, Feb 2, 2006.

  1. Manuel

    Manuel Guest

    Ok, this one's got me a little stomped. It started a few weeks ago and I
    went and ordered a couple more licenses because I thought that would fix it
    but it didn't. I will tell you the problem.

    Any new user that I create is not running the SBS_LOGIN_SCRIPT.bat that is
    normally configured to them by default. Now, when you go to Start > Run and
    type "\\ServerName\clients\Setup\setup.exe /s ServerName" without the quotes,
    then the script runs just fine and the client gets configured (ie. Outlook
    profile information so that the user doesn't have to manually configure it).

    I double-checked the assigned applications to each computer and is as it
    should be. To test, I created a test user and made sure that the script was
    in the Profile tab next to "Logon script:". Went over to the workstation,
    logged on and nothing right after logging on Start > Run and typed the path
    and parameters that are dictated in the script and it was configured. I hope
    this is enough information. There are no error messages not even in Event
    Viewer. It simply doesn't run. Please help!
    Thank you,
    Manuel
     
    Manuel, Feb 2, 2006
    #1
    1. Advertisements

  2. You've probably already checked this, but when you go to the Profile tab in
    the properties of the affected users in AD, does it show the login script?
    Obviously that user has the rights to run it since you can invoke it
    manually.

    Also, just for grins, try creating another logon script that does something
    simple like invoking notepad.exe or calc.exe and assign that login script
    to the user. Grant read and execure to everyone.

    Let us know what you find out.

    Jim
     
    Jim Martin [MSFT], Feb 2, 2006
    #2
    1. Advertisements

  3. Manuel,

    In addition to what Jim mentioned.. you might want to confirm that the
    machines are truly still part of the domain. In that, if the user does have
    the login script configured to be used with the account, then you might try
    putting a pause statement in the login script. Idea being that when the
    user logs on and the logon script is running at all then you should have a
    command prompt window open and paused. If that doesn't show up, then I'd
    really wonder if the users are actually logging on using cached credentials
    and not really getting domain validated.

    If this use to work and then stopped working for all users.. then did
    anything change on the server? For example, was it re-installed even using
    the same domain/server names? Which would be a different domain as far as
    the machines are concerned. Or was the server dcpromo'ed down/back up?


    ---

    Hope that helps,
    David Copeland
    Microsoft Small Business Server Support

    This posting is provided "AS IS" with no warranties, and confers no rights.


    SBS Newsgroups:

    SBS v4.x: microsoft.public.backoffice.smallbiz
    SBS 2000: microsoft.public.backoffice.smallbiz2000
    SBS 2003: microsoft.public.windows.server.sbs
     
    David Copeland [MSFT], Feb 3, 2006
    #3
  4. Manuel

    Manuel Guest

    Man, I feel like an idiot!! I did most of what Jim and David (thanks to both
    of you for replying by the way) said to test this. If you notice on my
    original question I mention having to type the whole path and parameter --
    "\\ServerName\clients\Setup\setup.exe /s ServerName".
    What I forgot to mention, which should have given me the biggest clue was
    that I could not access "\\ServerName\NETLOGON" directly.

    Turns out that somehow back in the day I might've accidentally changed the
    share permissions on SYSVOL and NETLOGON because when I checked again today,
    only Administrator had FC and no one else. Gave it the proper permissions and
    bingo...problem solved. Can't believe something so simple was missed. Thanks
    Jim! Though the stuff you mentioned to check or do was already done and
    checked the "Grant read and execute to everyone" sentence kind of gave me the
    idea to check the permissions.
     
    Manuel, Feb 3, 2006
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.