Automatic instantiation of remote COM from other operating systems
-
Hello all, I have a COM component on a remote server with no DllSurrogate = "" value set in the remote registry. So, the instantion could not be done in the server side only. I made a method to access the remote registry primitives, using the pipe \\PIPE\winreg and also using the rpc.rcacn_np transport. So, this way I'm able to modifying the registry remotely, putting the DllSurrogate="" and performing the COM instantiation. Everything is working fine, but now I must do all of this without file and print sharing, which means that I'll not be able to use the PIPE anymore. So I'm looking for some COM with DllSurrogate="" already enabled that expose some function to modify my component. Or some service working at port 135 or 445 with some exposed methods to do the same thing, this way I can access using the rpc.rcacn_ip_tcp. So, any ideas. Thanks in advance.
Raphael Amorim Dantas Leite
-
Hello all, I have a COM component on a remote server with no DllSurrogate = "" value set in the remote registry. So, the instantion could not be done in the server side only. I made a method to access the remote registry primitives, using the pipe \\PIPE\winreg and also using the rpc.rcacn_np transport. So, this way I'm able to modifying the registry remotely, putting the DllSurrogate="" and performing the COM instantiation. Everything is working fine, but now I must do all of this without file and print sharing, which means that I'll not be able to use the PIPE anymore. So I'm looking for some COM with DllSurrogate="" already enabled that expose some function to modify my component. Or some service working at port 135 or 445 with some exposed methods to do the same thing, this way I can access using the rpc.rcacn_ip_tcp. So, any ideas. Thanks in advance.
Raphael Amorim Dantas Leite
Hello, In the case you described I prefer to use WMI (Windows Management Instrumentation). It's an ultimate tool for making a kind of administrative work both on a local and remote computer under Windows XP & 2000. WMI "System Registry Provider" gives a full control on registry DB. You have to have administrative rights to perform any registry write operations on a remote PC, of course. If you are interested in using WMI, write me, I may share a simple project with you as an example of administration via WMI. Regards, ISerik
-
Hello, In the case you described I prefer to use WMI (Windows Management Instrumentation). It's an ultimate tool for making a kind of administrative work both on a local and remote computer under Windows XP & 2000. WMI "System Registry Provider" gives a full control on registry DB. You have to have administrative rights to perform any registry write operations on a remote PC, of course. If you are interested in using WMI, write me, I may share a simple project with you as an example of administration via WMI. Regards, ISerik
Using WMI from Linux? The only way is using the COM WBEM Scripting locator and it's not automated by default. We MUST change the registry like I said.
Raphael Amorim Dantas Leite VC++, Java and C# programmer. Win32 and PocketPC enviroments