I don't think you may switch, because the APIs used for sending broadcasts by Mercury are provided by the Netware Client and the use of APIs is hardcoded in Mercury. There is no output by the coremodule like "send <user> <subject>".
But may be I missunderstand your environment. I understand you're having a Novell Netware Server with Novell Accountmanagement (which ever) and Mercury configured for use of this accountmanagement. In this case Mercury assumes a Novell Netware Client for full functionality. SEND respective the Novell-APIs know about Netware Users and are capable identifiying a workstation, where the Netware user is logged in.
NET SEND only knows about local users on Windows or users in a Windows DOMAIN/Active Directory. In this case the pre-condition using NET SEND is the same username on Windowsworkstation/-domain than on Netware. But even than there is no support in Mercury for Windows Accountmanagement and in consequence no use of APIs for NET SEND.
Sorry
Olaf
<p>I don't think you may switch, because the APIs used for sending broadcasts by Mercury are provided by the Netware Client and the use of APIs is hardcoded in Mercury. There is no output by the coremodule like "send &lt;user&gt; &lt;subject&gt;".
</p><p>But may be I missunderstand your environment. I understand you're having a Novell Netware Server with Novell Accountmanagement (which ever) and Mercury configured for use of this accountmanagement. In this case Mercury assumes a Novell Netware Client for full functionality. SEND respective the Novell-APIs know about Netware Users and are capable identifiying a workstation, where the Netware user is logged in.
NET SEND only knows about local users on Windows or users in a Windows DOMAIN/Active Directory. In this case the pre-condition using NET SEND is the same username on Windowsworkstation/-domain than on Netware. But even than there is no support in Mercury for Windows Accountmanagement and in consequence no use of APIs for NET SEND.
</p><p>Sorry</p><p>&nbsp;&nbsp; Olaf</p><p>&nbsp;
&nbsp;</p>