Database Profiles disappear from registry

SysOp wrote:

I'm glad you finally started to understand that this is most certainly NOT an issue with 24x7.

When you save to remote server using 24x7 Remote Control, you connect to the server via 24x7 facilities, the Windows terminal server is not in play. That's why you get the registry stuff saved. When you do it via the terminal server (a.k.a RDP), all your changes are virtualized by Windows, which all happens outside of 24x7 control and transparently to 24x7. You close your session, and your changes are gone.

Let's close this issue. This is not caused by 24x7. There are no questions about it. Please follow the instructions we provided earlier.

I do not understand your logic. The remote config entry in the "Softtree Technologies, Inc" folder makes the Remote Control work by simulating a remote connection. When you create a remote connection the database profiles and job queues are copied from the 24x7 server to your local machines registry. When you start a remote control session there is in fact is no real remote control, all the scheduler stuff is run on the local machine.

The moment you press "save remote" the local changes are synchronised with the 24x7 server. This is where it all goes wrong. 24x7 tries to rewrite the database profiles, but it only succeeds in deleting the entries. This can be clearly seen by watching registry activity with regmon.

I was somehow hoping that with this new information you would be able to pinpoint the problem?

Just to be sure you understand, in the situation described above there is no rdp involved. All is done using the 24x7 server and local installations of 24x7.

Quote:

The remote config entry in the "Softtree Technologies, Inc" folder makes the Remote Control work by simulating a remote connection. When you create a remote connection the database profiles and job queues are copied from the 24x7 server to your local machines registry. When you start a remote control session there is in fact is no real remote control, all the scheduler stuff is run on the local machine.

I think you are still missing that the "local machine" is not a physical environment. You are doing it on the server in a virtual local session. As soon as you logoff from that session, Windows wipes out all your changes. During the session it redirects all registry and file writes to a session specific location somewhere under HKEY_CURRENT_USER while they are supposed to be saved in HKEY_LOCAL_MACHINE.

Because it appears that you started using 24x7 Remote Control, I can suggest another method for making the changes sticky. Make sure the 24x7 server on the Windows server is run in service mode. I mean you run it as a Windows service. From your machine or from another user session, using 24x7 Remote Control connect to the 24x7 server. Make the changes. Save them. They should stick. Windows doesn't virtualize changes made from Windows services.