sun script once for users

[Guest]

I want a script to be run for a user only the first time he/she logs on to my
Domain.how can i do this.if I but that script in his/her logon script,it
would be run so many time,which I don' want.what should I do?

 

[Lanwench [MVP - Exchange]]

In

I want a script to be run for a user only the first time he/she logs
on to my Domain.how can i do this.if I but that script in his/her
logon script,it would be run so many time,which I don' want.what
should I do?

What is the script supposed to do?

 

[Guest]

it is supposed to change ACL of the user so that a group called
"ProfileAdmins" are granted modify and delete permission over his/her profile
folder and all of its subfolder and file.

so as you can see,
1.there is no need to run it everytime,just once is enough
2.evenif I leave it running for many times,as the profile size grow,it would
impose an increadibly heavy load on profile server.suppose 10 user login
concurrently,each having a 700MB Profile.poor server!

 

[Lanwench [MVP - Exchange]]

In

it is supposed to change ACL of the user so that a group called
"ProfileAdmins" are granted modify and delete permission over his/her
profile folder and all of its subfolder and file.

so as you can see,
1.there is no need to run it everytime,just once is enough
2.evenif I leave it running for many times,as the profile size
grow,it would impose an increadibly heavy load on profile
server.suppose 10 user login concurrently,each having a 700MB
Profile.poor server!

Well - first off, I suggest that you never allow a profile to achieve that
rather frightening size....use folder redirection and don't store any user
data in the profile folders if you can avoid it. If you're using roaming
profiles, you can set up the permissions on the *server* copy of the
profile, which I'd find more useful myself.

That said - you could set up the script to copy a file to the folder and
then check for the presence of it - if it exists, it can exit. I'm not a
scripting person, but I'm sure there are more sophisticated ways to do
this - you might try posting in
microsoft.public.windows.server.active_directory for more help, as this
group is really for workstation security issues.