Prevent screen lock when closing RGS remote session

[sphen]

We have purchased zBoost for several of our machines and it has been working well. On one machine we would like to make sure that the windows lock screen does not come up when the rgs remote session is closed. We have changed the config as best as we can but cannot find a way to prevent the screen lock. any ideas on how to accomplish this?  config below:

Thank you!

##### HP ZCentral Remote Boost
##### Sender Properties
##### Uncomment a property to override its default value.

## Logging levels: DEBUG, INFO, WARN, ERROR, FATAL
# Rgsender.Log.Level=DEBUG
## Path to logging file:
# Rgsender.Log.Filename=rg.log
## Maximum Log Filesize in Kbytes
# Rgsender.Log.MaxFileSize=5120

## Sets the maximum image update rate that the Sender transmits to the
## Receiver. If the value is set to zero, the update rate will be unlimited.
# Rgsender.MaxImageUpdateRate=30

## Sets the preferred image CODEC.
## Both the Sender and Receiver must support the specified CODEC.
## The available CODECs are:
## NC (HP3) The default since release 5.0
## JPEG-LS Lossless, available since 5.3.1
# Rgsender.ImageCodec.Preferred=NC

## Enable or disable the Sender disconnecting all Receivers when the
## primary user logs out.
Rgsender.IsDisconnectOnLogoutEnabled=0

## The methods for detecting image changes on the display. All changes
## are sent to the Receiver as image updates.
## The "GPU" uses the GPU hardware to quickly compare one full screen
## to a previous full screen.
## The "Comparitron" method uses the system's CPU to compare one full
## screen to a previous full screen.
## The "ChangeList" method is only supported on non-compositing Desktop
## Managers.
## Enter the methods in priority order of usage. If a method is not currently
## supported in the system, the next method in the list will be tried.
# Rgsender.PreferredDisplayMethods=GPU ChangeList Comparitron

## Enable or disable the collaboration notification dialog
# Rgsender.IsCollaborationNotificationEnabled=1

## Enable or disable session reconnection during session logout or
## Fast User Switching.
# Rgsender.IsReconnectOnConsoleDisconnectEnabled=1

## Sets the time in seconds to wait for a system logon event to
## complete. If the logon does not occur within "ConsoleLogonTimeout",
## the Sender will be shut down.
# Rgsender.ConsoleLogonTimeout=30

## The timeout in msecs at after the connection will be closed.
# Rgsender.Network.Timeout.Error=30000

## Automatically generate a certificate for network transport encryption.
## If you use your own certificates, turn this property off.
# Rgsender.Network.GenerateCertificate=1

## Determines whether or not the Sender will accept connections
## from Receivers on all network interfaces or not.
# Rgsender.Network.IsListenOnAllInterfacesEnabled=1

## If the Rgsender.Network.IsListenOnAllInterfacesEnabled property is
## set to 0, these properties specify which network interfaces will be
## used to accept connections from Receivers. On Linux, these
## generally correspond with "eth0", "eth1", etc. On Windows, these
## correspond with the order specified in Control Panel -> Network
## Connections -> Advanced -> Advanced Settings -> Adapters and
## Bindings -> Connections (Note that 1394 Connections and Loopback
## interfaces are ignored and do not affect the numbering of the
## network interfaces).
# Rgsender.Network.Interface.0.IsEnabled=0
# Rgsender.Network.Interface.1.IsEnabled=0
# Rgsender.Network.Interface.2.IsEnabled=0

## A network interface will only be used to accept connections from
## Receivers if it is enabled using either
## Rgsender.Network.IsListenOnAllInterfacesEnabled or one of the
## Rgsender.Network.Interface.n.IsEnabled properties AND if the IP
## Address associated with that network interface falls within the
## range of IP Addresses specified with this subnet mask (in CIDR
## notation).
# Rgsender.Network.AllowIpAddressSubnet=255.255.255.255/32

## Port used for communication between Sender and Receiver.
## Must match the port setting on the Receiver. Default is 42966.
## Note that HPVelocity only works on port 42966.
# Rgsender.Network.Port=42966

## Cause the Sender local display to blank and local keyboard and mouse
## input to block when primary user is connected.
Rgsender.IsBlankScreenAndBlockInputEnabled=0

## Configure the USB ACL files. There is a ruleset and a schema file.
## Both are required for the ACL functionality to work correctly. The
## default ruleset allows all USB device connections. The Sender
## monitors the ruleset file for changes. If the ruleset file becomes
## inaccessible, the Sender will disconnect USB devices after an error
## period has expired. This error period is controlled via the
## RulesetErrorTimeout property. The property is specified in
## milliseconds and defaults to 5 seconds.
# Rgsender.Usb.Acl.RulesetPath=hprDefaultUsbAcl.xml
# Rgsender.Usb.Acl.SchemaPath=hprUsbAcl.xsd
# Rgsender.Usb.Acl.RulesetErrorTimeout=5000

## Remote Clipboard
# Rgsender.Clipboard.IsEnabled=1

## Enables multiple users to connect to a locked desktop before logon.
# Rgsender.IsClassicEasyLogonEnabled=0

## Remote audio enables an audio stream from the Sender to the
## Receiver for playback.
# Rgsender.Audio.IsEnabled=1

## The timeout in msecs on the Collab Notification UI dialog box.
# Rgsender.CollabUI.Dialog.Timeout=15000

## The delay in msecs after the active user stops making inputs (like
## mouse movements) before another user can take control of the floor
## in a collaboration session. This value can range from 0.5 seconds to
## 15 seconds and defaults to 0.5 seconds.
# Rgsender.RequestFloorControlTime=500

## Allow authenticated collaborators to connect without prompting for
## authorization.
Rgsender.Collaboration.AlwaysAcceptCollaborators=1

## Sets the preferred order that the Sender will attempt to checkout licenses in.
# Rgsender.PreferredLicenseOrder=Preload General HDI Trial

## Sets the maximum number of threads to utilize for image encoding.
## If the value is set to zero, the size will be the number of cores on the system.
# Rgsender.Encoder.ThreadPoolSize=0

## Disconnect VMware SVGA displays from the desktop on Windows VMware
## clients when Nvidia displays are available and enabled.
# Rgsender.Compatibility.Displays.ConfigureVmwareDisplaysForBestPerformance=0

## When ConfigureVmwareDisplaysForBestPerformance is enabled, define
## the behavior when a disconnection happens. Re-enabling the VMware displays
## allows access from vSphere. This can also cause Windows to
## rearrange the desktop
# Rgsender.Compatibility.Displays.ReEnableVmwareDisplaysOnRGSDisconnect=0

## Enable enhanced resolution matching for Windows systems with Nvidia graphics.
## Valid settings are on, off, and auto.
# Rgsender.Compatibility.Displays.AllowNvidiaResolutionMatching=auto

##### Smartcard properties:
# Rgsender.Smartcard.IsEnabled=1

## Load an EDID on headless Windows system with Nvidia graphics. Once this property is enabled
## this EDID will not be unloaded until the property is disabled.
# Rgsender.Compatibility.Displays.ForceEdidOnHeadless=0

##### Support properties:
##### The following properties are for support troubleshooting.

## LiveUDP enable. Default is 1 (enabled).
# Rgsender.Network.HPVelocity.Enabled=1
## The mode HPVelocity should operate in upon successful registration. Default is 1 (Protecting).
## 1=Protecting, 2=1-Way Monitoring
# Rgsender.Network.HPVelocity.LiveUdpMode=1
## LiveUDP congestion control algorithm. Default is 1 (Standard)
## 1=Standard, 2=Friendly
# Rgsender.Network.HPVelocity.LiveUdpCongestionControlAlgorithm=1
## The target loss rate the HPVelocity Live UDP plugin should use. Default is 4 (0.04%)
## 4=0.04%, 10=0.1%, 20=0.2%, 40=0.4%
# Rgsender.Network.HPVelocity.LiveUdpTargetLossRate=4

## Optimization to improve smart card performance over high latency connections.
# Rgsender.Smartcard.IsCacheEnabled=1

## Allow use of legacy security settings so 7.4 and earlier Receivers can connect
## without configuring certificates. Not recommended for highest security.
# Rgsender.EnableLegacySecurity=0

[KellyRGS]

Unfortunately you cannot leave the screen unlock when leaving an RGS/Remote Boost session.  Leaving the desktop unlocked when leaving a session would leave the desktop unsecured. 

I work on the behalf of HP.

[MFS_Adam]

Kelly,

This is a terrible (and show-stopping -- literally!) regression.

Support for this feature was fully implemented in RGS, although not enabled by default.  I understand that this could pose a security risk in some situations, but is very useful in others.  If we go down the "could pose a risk" road, any remote login could be bad...

My local use case is instrument control -- a computer that is located physically next to an instrument (with local keyboard, mouse, and monitor) occasionally needs to be controlled or observed from remote.  The local console should always be visible in my application -- not having it visible is bad. 

With RGS, we could specify Rgsender.IsBlankScreenAndBlockInputEnabled=0 and maintain local and remote access -- even after remote disconnect.  

A secondary use case for my operation is logging in to multiple view-only sessions that display on remote monitors.  These displays allow both teaching and a remote command-center of multiple screens from machines scattered around.  With the new Zcentral Remote behavior, any network problems that interrupt remote monitors cause the local console to re-lock.  This is bad.  

If a local user has already authenticated, the horse is out of the barn -- the desktop is already "unsecured".  This new (to Zcentral Remote) "feature" seems to take away control from the user.  I'm fine with the current behavior as default, but please let users disable the logoutWhenRemoteDisconnects !  It's very heavy-handed to restrict behavior based on an expectation of use case.

[KellyRGS]

I have already created this request to our planning group, but will add on you to the request as well.  You mention that in RGS you could set the property to unblank the screen, and disconnect and the desktop would not lock.  I am very surprised by this.  Can you tell me which version you saw this behavior in?  Thank you for providing your use case.  Could you send me a private email with your contact and company info so I can add that to the existing request for this?

[MikeInTVNews]

We absolutely need the Sender computer to remain logged in after the remote user disconnects.  Our use case for RGS Sender is in live TV news production - if the remote user has a network issue and disconnects, the local machine's session *must* remain accessible and functioning.   Please advise on any workarounds that would enable disabling the "Automatic Desktop Locking" feature ASAP. Thank you!!    

[MikeInTVNews]

Please add my info to the case as well, I emailed you privately. Thank you!