Reloading a registry entry

[Guest]

Hello,

I am using XP SP2 clients connected to Neware 6.5 servers.

I work for a school corporation and a couple of the students are visually
impared and have a hard time seeing their mouse pointer. I was givin
specific cursor files for those students to use. I added to the students
logon script so that if those specific students log in, the cursor file is
copied to "C:\Windows\Cursors" and their HKCurrentUser registry is edited to
make them use that cursor.

The problem is that even with those changes made, it doesn't actually change
their mouse pointer the first time they log in. They have to log in, then
log off, then login again, then it changes their pointer.

I believe the reason is because the login script doesn't run until their
desktop is already created. Is there something I could add to the login
script that would be similar to clicking the apply button after chaning your
mouse pointer?

Any help is appreciated, thanks

Robert

 

[Lanwench [MVP - Exchange]]

In

Hello,

I am using XP SP2 clients connected to Neware 6.5 servers.

I work for a school corporation and a couple of the students are
visually impared and have a hard time seeing their mouse pointer. I
was givin specific cursor files for those students to use. I added
to the students logon script so that if those specific students log
in, the cursor file is copied to "C:\Windows\Cursors" and their
HKCurrentUser registry is edited to make them use that cursor.

The problem is that even with those changes made, it doesn't actually
change their mouse pointer the first time they log in. They have to
log in, then log off, then login again, then it changes their pointer.

I believe the reason is because the login script doesn't run until
their desktop is already created. Is there something I could add to
the login script that would be similar to clicking the apply button
after chaning your mouse pointer?

Any help is appreciated, thanks

Robert

Not sure how this will work since you're not using a Windows domain, but the
issue might be resolvable via "Always wait for network" in group policy.
It's a PITA to manage policies without active directory, but you could do
this on each computer:

Computer Configuration / Administrative Templates / System / Logon.
Double-click Always wait for the network at computer startup and logon and
Enable this policy.

 

[Guest]

See if this works:
1. Hold the Window key and hit 'R'
2. Type GPEdit.msc and hit enter
3. Navigate to User Configuration\Administrative Templates\System\Scripts
4. Set the "Run logon scripts synchronously" setting to "Enabled"

That should do it. Let us know if it works. I have never tried that with a
cursor before.

 

[Lanwench [MVP - Exchange]]

In

See if this works:
1. Hold the Window key and hit 'R'
2. Type GPEdit.msc and hit enter
3. Navigate to User Configuration\Administrative
Templates\System\Scripts
4. Set the "Run logon scripts synchronously" setting to "Enabled"

That should do it. Let us know if it works. I have never tried that
with a cursor before.

I think you meant to reply to supersonic_oasis, not to me...