Supporting Windows

Mouse settings are definetly per user. I would suggest using Group Policy for those settings. If you can't use GP, you can write a script that will load the hive of each user (via their ntuser.dat file) who already have an account on the system, and then do the same for Default user. This will apply the settings to all users who currently have a local account, as well as any new users since they will pull from Default. HKU\Default is not what you think it is, this is not the default profile. C:\Users\Default\NTUser.dat is.

So you would load the hive, modify the registry as needed, and unload the hive. Then move on to the next user. Not too difficult to script out.

Thanks for you help.

GPO will be user config which will be relatively the same but what you had mentioned in regards to HKU\Default - thanks for clarifying this as I was drawing straws...my last alternative is to look at ntuser.dat in the default profile. 

I will initially manually try to test this before scripting as I found active setup to add the keys to HKCU for the current profile only worked after a re-logon which is not practical for users who use remote connect is someway....image asking admin users to re-logon to affect a mouse change :-)

But thanks for pointing me in a direction - really appreciate it!

Just did a small scale test with mouse trail setting. Didn't take effect until I logged back in after I set the setting manually. But when I loaded the default hive, modified the mouse trail value, unloaded, then logged in as a new user, the mouse was trailing without the need to log off/on. This should hopefully work for you, since the setting would be applied before the log-in so that should take effect right away. But yes test away.

I found the same result by edited the HKCU key and that is the question of issue of making the changes stick straight away without a relogon....the settings I am changing will resolve mouse "lag" over IRMC or ILO remote settings and did not want to make a procedure of relogon really....

But did you try to edit HKCU while logged in as that CU? If so, yes that would be expected given your other results. If you script it out, it will hit the users before they log in and should take effect during the next log-in. Try running this batch file...

REG load HKEY_USERS\TempHive "C:\Users\Default\NTUSER.DAT"
REG ADD HKEY_USERS\TempHive\Control Panel\Mouse /V ENTERVALUEHERE /T REG_SZ /D ENTERDATAHERE /F
REG unload HKEY_USERS\TempHive

Then log in as a new user (who has not already logged into the computer) and see if the changes take effect right away.