Upgrading to RPS 6.15 communications with GV2 panels with firmware less than 7.06 stop working
Possible causes and solution(s)
Symptoms
After upgrading to RPS 6.15, communications with GV2 panels with firmware less than 7.06 stop working
Causes
Starting with RPS 6.15, the RPS Proxy service "Log on as" user was changed from "Local System" to a standard Windows user called "RPSsvc". This RPSsvc user is created by the RPS installer and is given no special permissions beyond being assigned to the "Users" group. Most of the time this is just fine because the RPS Proxy service doesn't typically require any special permissions beyond that of a normal user. However, there are some circumstances where Windows security policies might interfere with RPS Proxy operations. One example is that RPS Proxy cannot properly bind to the UDP7700 port to listen for panel replies when communicating with older panels using the legacy "Datagram 00" protocol (e.g. GV2 panels with firmware less than 7.06 or original G Series panels with firmware less than 7.00).
Solution
The ideal solution would be to work with IT administrators to identify what is blocking the RPSsvc user and to give that user only the rights necessary to perform normal operations. But it is also possible to revert the RPS Proxy service to use the Local System account as it had in previous versions of RPS. This can be done by opening the Services console and modifying the RPS Proxy "Log on as" user:
Click the Start menu or the Search bar in the taskbar and search for "Services.msc"
Select the Services search result
Scroll through the list of services to find RPSProxy
Right-click RPSProxy and choose Properties
Click the Log On tab (A) then select Local System account (B)
Click OK to save that change
Right-click RPSProxy and choose Restart to cause the service to start as the new "Log on as" user.
Related content
͏ ͏ Stay up to date |
Get in touch |
You are on |
---|---|---|
Bosch Building Technologies
|
͏ ͏ Corporate information |
Legal Notice |
Data Protection Notice |
California Privacy |
CCPA-and-Canadian-Privacy-Disclosure |
Terms of use |