Hi Jim,
1. logon script via policies:
322241 HOW TO: Assign Scripts in Windows 2000
http://kb/article.asp?id=Q322241
2. Assigning it to a local user:
315245 How to Assign a Logon Script to a Profile for a Local User
http://kb/article.asp?id=Q315245
- no limitations on having computer and user in the same OU, provided there
are good reasons for the same
--
Thanks
Sabin Nair M.S(Computer Engg.), MCSE, MCSA
Directory Services Team
Microsoft Corp.
"Please do not send e-mail directly to this alias.
This alias is for newsgroup purposes only."
"Jim Carney" <(E-Mail Removed)> wrote in message
news:033101c361ca$c09145e0$(E-Mail Removed)...
> and there's no limitation on having the computer's and
> user in the same OU?
>
> and as far as the actual login script, can i leave that on
> the individual pcs i want to do this for, or do i need to
> put in on the network share, and point their logon gp at
> it? (its only 5 computers that need this feature, but i
> want to understand why things work the way they do, so i
> can make better decisions)
>
> thank you very much for your help so far!
> >-----Original Message-----
> >Hi Jim,
> >
> >If you are applying a policy to an OU, there are two
> considerations:
> >
> >1. If you are enabling a user policy (applying to users -
> User Config Part
> >of the policy), you need the users to be in that OU
> >2. If you are enabling a computer policy (applying to
> computers - Computer
> >Confg Part of the policy), you need the computers in that
> OU
> >
> >Logon scripts can be applied via:
> >1. Group Policy
> >2. Specify in the User Account properties
> >
> >In your case, you may have to have both user and computer
> in the OU, since
> >the services policy is a computer policy, scripts (if
> applied via policy) is
> >a user policy.
> >
> >Thanks
> >Sabin Nair M.S(Computer Engg.), MCSE, MCSA
> >Directory Services Team
> >Microsoft Corp.
> >
> >"Please do not send e-mail directly to this alias.
> >This alias is for newsgroup purposes only."
> >
> >"Jim Carney" <(E-Mail Removed)> wrote in message
> >news:00a501c361c6$efdc58c0$(E-Mail Removed)...
> >> I am trying to run a logon script that starts the print
> >> spooler service, and a logoff that stops it.
> >>
> >> i have a very simple
> >> @echo off
> >> net stop spooler /y
> >>
> >>
> >> and one for the starting script.
> >> however it won't run unless the user has admin
> privelages.
> >> now i have tried to go to the group policy editor in
> >> active directory and given users the ability to modify
> the
> >> spooler service. i added the system account, the domain
> >> user, the user, the domain admin accounts. the system
> >> account and admin acounts got full rights. the other two
> >> got rights to read - and start stop the service.
> >>
> >> so far it does not seem to be working. i applied the
> >> policy in the default logon policy of the OU that all my
> >> user accounts are contained in. i've read that you
> should
> >> make a new OU and move all the computer accounts into
> that
> >> you want this kind of thing to work on. however i cannot
> >> tell if that's just one method for doing this, or the
> only
> >> way.
> >> also the logon scripts i put on each individual pc. do i
> >> need to put them on a network share for this to work?
> >> any advice would be greatly appreciated.
> >
> >
> >.
> >