vijaykumar
New Member
- Joined
- Aug 10, 2010
- Messages
- 2
- Thread Author
-
- #1
We have a requirement to change key board properties (Repeat delay, Repeat rate and Cursor blink rate) and Default Input language programmatically.
Our application is run under user context which is different from the user who is currently logged-on to the machine.
For ex: If User1 is logged-in to the machine. Our application will be running under User2 (administrator) context.
Our requirement is, when application running in User2 context, changed/updated keyboard properties and input language must reflect for all users who log in to that machine afterwards. To meet this requirement, we’re using Group Policy Object (GPO).
In Windows XP, once changes written to GPO, One must log off and then log on again for the changes to take effect. For the changes to take effect for another user, the computer must be switched off, and then switched on again. One computer restart will ensure reflection of changes for another user.
On Windows 7 systems, for the settings to take effect, one should shut the system down and then restart it. After restarting, one should log on, log off immediately, and then log on again. Here, it requires additional log off and log on for changes to take effect.
Is there any alternative approach to avoid additional log off and log on for Windows 7 systems? Or is it a defect in windows 7 system? If so, when this will get addressed?
Our application is run under user context which is different from the user who is currently logged-on to the machine.
For ex: If User1 is logged-in to the machine. Our application will be running under User2 (administrator) context.
Our requirement is, when application running in User2 context, changed/updated keyboard properties and input language must reflect for all users who log in to that machine afterwards. To meet this requirement, we’re using Group Policy Object (GPO).
In Windows XP, once changes written to GPO, One must log off and then log on again for the changes to take effect. For the changes to take effect for another user, the computer must be switched off, and then switched on again. One computer restart will ensure reflection of changes for another user.
On Windows 7 systems, for the settings to take effect, one should shut the system down and then restart it. After restarting, one should log on, log off immediately, and then log on again. Here, it requires additional log off and log on for changes to take effect.
Is there any alternative approach to avoid additional log off and log on for Windows 7 systems? Or is it a defect in windows 7 system? If so, when this will get addressed?
Solution
- Joined
- Mar 14, 2023
- Messages
- 98,013
When dealing with changing keyboard properties and default input language programmatically under a different user context on Windows systems, especially in scenarios where you want these changes to affect all users who log into the machine subsequently, Group Policy Objects (GPOs) are commonly used to enforce such system-wide settings. The behavior you described about the changes taking effect after a restart or multiple log-ons is not a defect in Windows 7. It's more of a design feature related to the application of GPO settings and how the Windows operating system applies these changes. Here are some insights and suggestions regarding this scenario:
Alternative Approaches:
- Scheduled Task: Instead of relying solely on GPOs, you could schedule a task to run a script that applies these settings. This script could run with the necessary permissions to make system-wide changes without the need for manual intervention from users.
- Customized Solution: Develop a custom solution that leverages the Windows API to change the keyboard properties and input language without relying on GPOs. This could provide more flexibility in managing these settings programmatically.
Windows 7 Behavior:
- In Windows 7, restarting the system is often required for system-wide changes like these to take effect. This behavior ensures that the changes are applied uniformly to all users on the machine.
Microsoft Updates:
- Microsoft periodically releases updates and patches to improve Windows functionality and address known issues. It's possible that in later updates to Windows 7, the behavior related to applying GPO settings could have been optimized.
Automation Tools:
- Consider using automation tools like PowerShell scripts or other scripting languages to apply these settings programmatically. These tools can streamline the process of making system-wide changes without the need for manual intervention. By exploring these alternative approaches and utilizing automation tools, you can potentially streamline the process of applying keyboard properties and language settings across all user accounts on Windows 7 systems. Additionally, staying updated with Microsoft updates may also reveal improvements in how GPO settings are applied in the future.