Logon Script

levi.rogers · 10-06-2006, 04:35 PM

I was wondering if it would be possible to write a logon script that could run a registry fix to a group of computers.

The situation:

One group of our computers are very locked down and each has roughly seven different users that log onto them regularly. We did not use roaming profiles for this because these machines have essentially only one function, thus we didn't want to use up the overhead in order to implement roaming profiles for these users.
However, we use folder redirection for the my documents folder in order to keep a users my documents folders on a file server that is backed up daily. Sometimes syncronization cannot work with certain files(database files for example) and thus it throws an error out, even if this user has never used that file(it is really a linked file to another server).
We did find a fix for this in which you turn off the error reporting on file synch in the registry. This works fine, however it is user specific and I really don't want to log in as every single user and run this damn fix. The other problem is that these users are purposefully locked down to not be able to edit the registry, turn about, I can't have them run this file.
The good thing is that this group of users/computers is seperated off from all other users within its OU, it is its own policies, logon script, etc. So I was wondering if I could write a script that could go out and fetch this registry fix and run it on logon. It would also need to be able to account for when the entry is already there to avoid run time errors.

Any ideas?

LR

levi.rogers · 10-10-2006, 08:05 PM

I managed to get this one on my own. The script wasn't as difficult as I thought it would be. Oddly enough I didn't have to even put the following:

On Error Resume Next

Because it simply rewrites the registry entry without you telling it too.

Worked well.

I was dissapointed that noone jumped up with an answer or at least and F.U..

Oh well....

10-06-2006, 04:35 PM	#1 (permalink)
levi.rogers Registered User Join Date: Jun 2006 Location: Mid-West Posts: 111 OS: WinXP Pro	Logon Script I was wondering if it would be possible to write a logon script that could run a registry fix to a group of computers. The situation: One group of our computers are very locked down and each has roughly seven different users that log onto them regularly. We did not use roaming profiles for this because these machines have essentially only one function, thus we didn't want to use up the overhead in order to implement roaming profiles for these users. However, we use folder redirection for the my documents folder in order to keep a users my documents folders on a file server that is backed up daily. Sometimes syncronization cannot work with certain files(database files for example) and thus it throws an error out, even if this user has never used that file(it is really a linked file to another server). We did find a fix for this in which you turn off the error reporting on file synch in the registry. This works fine, however it is user specific and I really don't want to log in as every single user and run this damn fix. The other problem is that these users are purposefully locked down to not be able to edit the registry, turn about, I can't have them run this file. The good thing is that this group of users/computers is seperated off from all other users within its OU, it is its own policies, logon script, etc. So I was wondering if I could write a script that could go out and fetch this registry fix and run it on logon. It would also need to be able to account for when the entry is already there to avoid run time errors. Any ideas? LR

10-10-2006, 08:05 PM	#2 (permalink)
levi.rogers Registered User Join Date: Jun 2006 Location: Mid-West Posts: 111 OS: WinXP Pro	Don't worry about it. I managed to get this one on my own. The script wasn't as difficult as I thought it would be. Oddly enough I didn't have to even put the following: On Error Resume Next Because it simply rewrites the registry entry without you telling it too. Worked well. I was dissapointed that noone jumped up with an answer or at least and F.U.. Oh well....