Emerson Exchange 365

• Not Answered

DeltaV Screensaver Does Not Run in a Virtual Machine Connected via DeltaV Remote Desktop Connection

Hi, 

I have a question with Screen Saver function in a Virtual Machine. The version of Virtual Studio is 2.3.1. This a domain.

Does any one here know of a work around for the screensaver function to work in Virtual Machines via DRDC?

I have followed the work arounds in KBAs AP-0800-0075, NK-1400-0046 and NK-1700-0295. But the work-arounds did not work.

I am not sure if using GPO to configure the screensaver settings in Virtual Machines is applicable. 

I appreciate for any inputs, suggestions

Napsterrific

• 21 Nov 2017 6:39 AM
• Cancel

3 Replies

• Neil Castro

  

  • 21 Nov 2017 10:12 AM

  Hello Nap,
  
  In our previous project we made the DeltaV screensaver on DRDC to work.
  
  We just have to configure it using the Windows user that is used by the operator to login remotely to the virtual station. In case they use different users to login to Windows remotely then all these users need to configure DeltaV screensaver individually.
  
  You know my email address. You can send me a private message if you need more help since this topic has a lot of path and do not want to confuse readers of this post in case your issue becomes more complex.
  
  Regards,
  Neil Castro

  • Cancel
• dave_marshall

  

  • 29 Nov 2017 3:17 PM

  Hi Nap,

  I have run into a similar issue when using a thin client to connect to a DeltaV operator station via RDP.  In an RDP session, Microsoft disables the On Idle detection capabilities that would normally launch the screen saver.

  In my case, I was using the DeltaV screen saver to perform a DeltaV user auto-logout. To achieve this I did 2 things:

  1. Configured the DeltaV Screensaver with the settings I wanted (auto log-out, etc)
  2. Used a 3rd party application called System Scheduler (Pro version) from Splinterware. At the time it was $30.

  The System Scheduler application is a Windows Task Scheduler replacement. It it not limited when an RDP session is connected to the host system. Configuration of an On Idle task is pretty simple. The only challenging part is knowing how to launch the screen saver itself. Here are the file paths for the DeltaV screen saver:

  • x32: C:\Windows\System32\DeltaVScreenSaver.scr

  • x64:C:\Windows\SysWOW64\DeltaVScreenSaver.scr

  Good luck!

  Dave

  • Cancel
• Youssef.El-Bahtimy

  

  • 8 Dec 2017 6:51 PM

  In reply to dave_marshall:

  Dave, I understand that DRDC is different than RDP, so I'm not sure if your solution is for one or the other (or both). I have had problems with DeltaVScreenSaver and Terminal services (RDP) since version 7, I am fighting with a v.11 system presently that is virtualized, (but on VMware and not HyperV, not sure why there would be a difference).
  
  What's funny is for my current setup, 3 terminal servers are working perfectly, only 1 is not. The only difference between the one hold out is it has 4 sessions which are reserved for a node, and one wide open session. The completely functioning servers have 4 sessions all reserved for a node.
  
  I recall having a problem with the screensaver and a mixed-session setup in the past, the reasoning being that the 'autologin' feature gets confused by having to handle sessions that are reserved for a node and those that are not.
  
  Anyway, I wrote my own application to overcome this over 10 years ago at my last employer and would employ it to this day if it were still mine to support and use.

  • Cancel