RE: [sniffer] Persistent Server setup with SrvAny Resource Kit tool

Oh, and yes, net start shows the Sniffer service running and I have a LicenseID.persistent.stat fine on both of my IMail/Declude/Sniffer servers and it is periodically updated (cat or type the file and you will see that the data it contains updates every second, I believe). Bill -Original

RE: Re[2]: [sniffer] Persistent Server setup with SrvAny Resource Kit tool

Mine doesn't look like this and it works fine. I just have: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sniffer\Parameters] Application=D:\\IMAIL\\Sniffer\\Win32\\MyLicenseKey.exe AuthKey persistent -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On

RE: [sniffer] Persistent Server setup with SrvAny Resource Kit tool

Hi, Oh, and yes, net start shows the Sniffer service running That can be misleading. The Sniffer service shows running, because srvany.exe is executing! (Check your task manager, you'll see an instance of srvany.exe - that's why it shows running.). It showed running on my end all the time.

RE: [sniffer] Your Sniffer Setup

Hi Keith, It's pretty straightforward: A) Download the Windows 2000 Server Resource Kit utilities. B) Locate the path to srvany.exe. C) run: instsrv Sniffer c:\path-to-resource-kit\srvany.exe Sniffer is just the name that will appear in the services applet later D) Start RegEedit and

RE: [sniffer] Your Sniffer Setup

See http://support.microsoft.com/default.aspx?scid=kb;en-us;137890 for simplified instructions. Bill -Original Message- From: Andy Schmidt [mailto:[EMAIL PROTECTED] Sent: Monday, November 01, 2004 6:26 AM To: 'Keith Johnson' Subject: RE: [sniffer] Your Sniffer Setup Hi Keith, It's

RE: [sniffer] Your Sniffer Setup

Hi Landry: These simplified instructions only apply if the application needs no parameters, as it only covers the application key: Value Name: Application Data Type : REG_SZ String : path\application.ext If there was a SnifferPersistent.exe that needed no further options,

RE: [sniffer] Your Sniffer Setup

Thanks Andy and Bill, will give this a go on our beta server. Thanks again for the time and expertise Keith -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Schmidt Sent: Monday, November 01, 2004 12:11 PM To: [EMAIL PROTECTED] Subject: RE:

RE: [sniffer] Your Sniffer Setup

Andy, these simplified instructions work just fine with Sniffer, as I can certainly attest. Bill -Original Message- From: Andy Schmidt [mailto:[EMAIL PROTECTED] Sent: Monday, November 01, 2004 9:11 AM To: [EMAIL PROTECTED] Subject: RE: [sniffer] Your Sniffer Setup Hi Landry: These

RE: [sniffer] Your Sniffer Setup

Hi Bill, Thanks. That's curious. I'm not at all doubting your experiences - I'm just trying to reconcile the KB article (which says to ONLY define the path, program name and extension) with the Sniffer documentation (which says, you must define the persistent option and your authorization code).

Re: [sniffer] Your Sniffer Setup

Andy, Bill, et al. When the persistent Sniffer was first offered, I typed up the attached directions that I cribbed from the KB when alerted to it by Bill. I am forwarding this as a message attachment since the archives are down currently. I haven't yet upgraded to the latest version, but at

Re: [sniffer] Your Sniffer Setup

This might be there in the event that you need to quote certain arguments or handle special characters??? I've found some different requirements for command line arguments and special characters such as which require either quoting them or using an octal encoded value (I'm no expert on this