How does the SBS_LOGIN_SCRIPT.bat get into the user properties

In a new install of SBS 2K3, when you create a user, usig one of the preconfigured templates, the user profile login script box has SBS_LOGIN_SCRIPT.bat in it...

where does that come from?!  If you look at the user template, it's not there.  I thought that was the point of the template - to have fields filled in already with info.  But when I look at the template, that field is blank.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It has one really good purpose these days, otherwise you can think of it as a leftover from days gone by since you are better off doing your scripting through the GPO now instead of individual user bat files.

The default bat file insures that when you connect a client computer that all of its specified client applications are installed and updated.  In addition it does check a few things to insure they are applied via the GPO.

LookingForITHelpAuthor Commented:
but how does that file name get inserted into the user properties?!  it's not in the user template.

and a similar note - how do you se tthe default user profile path the \\server\profiles\%username%.  It's a pain typing it for each user.

The one entry in the script is that setup file.  Does that need to be there all the time or can you rem it out?  The initial apps get installed the first time.  It seems to be creating the message about the user not having rights to do installs.
Leave it there all the example of use would be when you updated your sbs with xp service pack time the clients logged in they would be updated.

if the computer and user were set up properly through the sbs wizards there shouldn't be any issue with user rights on the client installs.  just make sure user is a local admin on their computer.

in regards to setting multiple profile paths at the same time, you can actually select as many users as you want (using control or shift key) and then set the path property using the %username% as you mentined above and it will extrapolate that into the correct path for each.

one thing to note since you are planning on using roaming profiles, don't use the encrypted file system (EFS) and don't turn on offline folder caching.

as far as 'how does the filename get inserted into the user properties'....uhh, never cared to find out :)  just one of those things that has always worked.  it's not part of the template though because it's a required part of connecting a computer to the sbs domain....not optional as far as the server is concerned.  I've always assumed it's part of the add user wizard.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LookingForITHelpAuthor Commented:

your quote:  just make sure user is a local admin on their computer.

doesn't that open them up to getting spyware / malware?  I thought you are supposed to lock them down and make them just a user?  But yeah, then you can't push apps out to them?

I am coming from a workgroup mindset and very eagerly looking to not have to go to each desktop to tweak things - I was thinking domains free you from most / all of that, but am getting dienchanted with seeing htat isn't the case?!  OK, you can remote desktop to each PC with the server management apps, but still...
You can do quite a lot using AD and policy maker what exactly do you want to do with the individual pc's or users.

The sbs login script is there just to compliment the features that are in essence the network in a box you do not have to use them however they are very handy, if you wanted to you can apply applications to users - then give them elevated permissions using Active directory such as domain admins if you wanted to (I am sure I will get eaten for saying that) but the purpose is just to let them log in get their apps get their config then you remove them, you will have printers installed outlook configured internet explorer configured oh its just great.

Now am sure there is a much better way to do it so lets see what everybody else has to say.

What we normally do when setting up sbs is after the server has gone in you deploy applications and because we would always go around and check the pcs we log in as admin it installs all it needs to and then away you go.

Other option is (policy maker) a magic magic piece of software.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.