Sync Screensaver not working

[pdesmith]

Hi wondered if anyone can help. Everything has been working fine, then I had to reinstall Windows and hence Maxivista on my primary PC. I set everything backup but since then, after a given period of time the screen saver keeps starting on my secondary monitor / PC, according to its domain policy which I can't change.

This means the screen saver comes on and the PC locks itself. i then have to VNC to it to unlock and fire the monitor back up. This seems to happen regardless of whether its being used and more frustratingly, regardless of the settings in Maxivista. I've ticked synchronise screen saver and prevent hibernation with no effect. Both PCs are XP Pro, primary is using Maxivista Version 3.0.28 ext_A, as before.

Any ideas?

Thanks.

[admin]

Our apologies for the inconvenience but if your user account has no privileges to change your screensaver settings, then MaxiVista cannot override this restriction.

This has been configured by your admin. Please resolve this issue with your admin.

[pdesmith]

OK thanks understood. However, that same domain policy was in place on the secondary machine before I had to reinstall on the primary, yet Maxivista worked fine. How does Maxivista on the Primary invoke or keep alive the second screen - presumably not just as a local user would?

Phil

[kforeman]

ok, I'm having the same issues, except mine started when i upgraded from V3 to V4. when I was running V3, I had the sync option set and my secondary pc's screen saver didn't start up unless the following:
1. The primary pc's screen saver started
2. I shut down the server side of V3.

Is there an issue in 4.0.11?

Kyle

[pdesmith]

I never found a fix for this - but thankfully found a registry hack to get round the domain screensaver policy - the GUI options were greyed out. I never had to do this with a previous install so its frustrating!

P

[kforeman]

hey p, can you share the hack?

thanx

Kyle

[pdesmith]

Hey Kyle,

Yep sure. You need local admin rights but I just used this page:
http://blogs.technet.com/markrussinovic ... tings.aspx

A very wordy description of a simple operation - I juts used Regedit, found the keys mentioned and changed them, rather than all that Regmon stuff described.

Worked for me.

Phil