Distributing SETI across a network?

[seaquake]

Spy Report!

We're watching you

 

[IndyJaws]

Gee, thanks for putting the pressure on me to get this approved and up and running

 

[Crazee]

Indy,

Don't worry about DSLR. Just do the best you can and if it is approved, I am sure that people here will help you all you need.

Whether you get it on 1 machine or 400 machines, we appreciate whatever you are able to give!

 

[Evadman]

We dont care if you get it running on NO machines, we like the company anyway

Welcome to the TeAm!

 

[SoulAssassin]

<< After securing permission, I would recomend the following:

1. Install SETIQ on your PC or one that isn't used much, preferably with a static IP address, although the computer name can be used depending on how your network is setup. You can schedule it to either flush and fetch WUs all day, or connect between certain hours. If it is your PC, you can set it up to fetch/flush WUs after hours when you aren't there.

I haven't noticed SETIQ taking up much resources when I've been on the PC running my SETIQ

2. Point your SETIQ to fetch/flush to Orange Kid's SETIQ, that way you have a double check (and more stats!) www.orangekid.teamanandtech.com:5017
3. Install SETIDRIVER as a service on each PC. Set the service to manual. Make sure SETIDRIVER is pointing to your SETIQ. If running your own SETIQ isn't possible, point them to Orange Kid's. Also set the # of WUs per PC to hold several days worth of WUs.
4. Setup a schedule task on each PC to start SETIDRIVER at an appropriate time each night.
5. Setup a schedule task on each PC to stop SETIDRIVER at an appropriate time each morning.
6. Have fun! >>



Rather than setup the AT job on each workstation to stop/start the service, if you can dump all the wrkstation names into a text file you can do a xnet stop/start from your local workstation. Xnet is in the NT/2K resource kit.

Optimally you would leave it running 24x7 but if you have other admins who might start wondering what this process is chewing up 100% cpu, you may want to only run it after hours. And then again, if we go under the assumption that you have permission to do this, screw it, run it all the time. They shouldn't see any performance hit worth talking about.

 

[SoulAssassin]

<< Hey all!

Can I distribute the program over the network? Would it require SMS (or something similar) to do the remote installation, or can it be placed in a startup folder?
>>



You can distribute via an SMS job, SMS automated jobs are not my specialty so I can offer little assistance other than saying it's possible. If you have telnet started on these machines you could write a batch file that would push it out or if you really wanted to you could distribute via a group policy but that might be more headache than it's worth.

There's a million ways to do it other than walking to each workstation, w/out an intricate knowledge of your network it's hard to say what's the best.

 

[Shuxclams]

Glad to hear that it works for you.













SHUX

 

[IndyJaws]

Quick update:

Talked to the SysAdmin tonight. He thought it would be cool.

Now if I can figure out a way to get it installed across the network without requiring the users to have admin rights to get the script to run, we'll be in business



<< Rather than setup the AT job on each workstation to stop/start the service, if you can dump all the wrkstation names into a text file you can do a xnet stop/start from your local workstation. Xnet is in the NT/2K resource kit.

Optimally you would leave it running 24x7 but if you have other admins who might start wondering what this process is chewing up 100% cpu, you may want to only run it after hours. And then again, if we go under the assumption that you have permission to do this, screw it, run it all the time. They shouldn't see any performance hit worth talking about. >>



How does xnet work? What would it do for me? I checked Microsoft's site, and did not see the kit available for download.

I have no problems running it 24x7 (hey, more WU's!), since most of the PC's are used for either terminal emulation software or Excel spreadsheets (and the occasional Web surfing). I assume the service will throttle back if CPU cycles are required for something else, like actual work

Getting closer...

Edit: I forgot to mention earlier that although I brought up SMS, we won't have it installed until late Q1 2002. So that shouldn't figure in to the options.

 

[Smoke]

I'm rubbing my hands together and grinning from ear to ear in sweet anticipation.

 

[Shuxclams]

SHUX

 

[IsOs]

Any of these computers using Outlook 2000, Adobe Pagemaker, Illustrator 8 or 9, Microsoft Office 2000, or Norton Anti-Virus 2002? There are issues running the client version of SETI.

 

[Sukhoi]

Office 2000 has issues? I'm running Office 2000 Standard on Win98SE and I haven't had any noticeable problems.

 

[CADsortaGUY]

no issues - Yet - here with office 2000 on Win2K using the service install AND no issues yet running the Cli, SETIDriver, and SetiSpy - 2 similar boxes different installs

 

[teriba]

I've had no issues with Windows 95, 98, ME, XP and Office 97, 2000, XP. This looks like quite a nice project! I hope you get it set up soon for the race

 

[Baldy18]

Outlook 2K and SETI I know have issues but I haven't noticed anything with the others although I don't use all of them. I've heard that Outlook 97 and XP don't have issues with SETI though.

 

[Shuxclams]

What kind of issues? I have the "Keyboard" install, the normal "seticommandline-3.03 + SETILog" type and my version of the W2K service installed on Win98SE/W2K machines running O2K - Small Business Edition/Professional including Outlook 2000, a few different Adobe products and Norton antivirus 2001 or 2002, I havent heard about this outlook issue, what is it, what are the symptoms?










SHUX

 

[Baldy18]

Outlook 2K suffers from small hessitations. Personally I use NAV 2002 and haven't noticed anything although it may hessitate also. I think if you don't scan your whole drive you don't notice it.

 

[IBhacknU]

IndyJaws... regarding your previous questions about a performance hit with SetiQ, you won't even notice it. I see you've already got it loaded, but even once 400 machines come a knock'n, me says you'll be fine.

W E L C O M E !

 

[IsOs]

Programs using disk swapping like the one I mentioned experienced delay while the disk is being accessed. People who regularly uses the program will definitely noticed the difference and most likely will report it as problem. In a corporate office, it's possible that the user will call the program's technical support which will lead to the discovery of SETI.

 

[IndyJaws]

<< Any of these computers using Outlook 2000, Adobe Pagemaker, Illustrator 8 or 9, Microsoft Office 2000, or Norton Anti-Virus 2002? There are issues running the client version of SETI. >>



Yes, we use Outlook 2000, Office 2000 and NAV (which is server-controlled, rather than host-based). As much as I would like to run the service 24x7, me thinks it would probably be best to use the scheduling option in Shuxclams script to set the hours to downtime.

Has anyone figured out a way to distribute without requiring the workstations to be logged in as an administrator? That's the only thing holding me up now!

 

[Smoke]

me thinks it would probably be best to use the scheduling option in Shuxclams script to set the hours to downtime.

400 running half the time beat the hell out of 400 w/o SETI.

 

[Shuxclams]

The hours its set for 16hrs of Wu time a day plus all weekend, that should be plenty of time for most machines to pop at least 1 Wu, so 200 Wu's a day aint a bad average. Actually, thats a really good average. :Q Beats the hell out of mine..... :disgust: heh-heh










SHUX

 

[IBhacknU]

<< Has anyone figured out a way to distribute without requiring the workstations to be logged in as an administrator? >>

???

 

[SoulAssassin]

<<
How does xnet work? What would it do for me? I checked Microsoft's site, and did not see the kit available for download.

I have no problems running it 24x7 (hey, more WU's!), since most of the PC's are used for either terminal emulation software or Excel spreadsheets (and the occasional Web surfing). I assume the service will throttle back if CPU cycles are required for something else, like actual work

Getting closer...

Edit: I forgot to mention earlier that although I brought up SMS, we won't have it installed until late Q1 2002. So that shouldn't figure in to the options. >>



xnet works just like just except you can use it on a remote computer. Ever user xcopy and copy? Here's an example:

xnet start \\machinename\servicename

So if I'm on my local machine named mymachine and I want to start it a service named seti on yourmachine I would drop to a cmd prompt and type:

xnet start \\yourmachine\seti

xnet is part of the Resource Kit and is a commercial package, you won't be able to find it online. Going out on a limb, one of the LAN admins at your company should have a copy. If not, PM me and I might be able to provide some futher direction.

 

[SoulAssassin]

<<

<< Any of these computers using Outlook 2000, Adobe Pagemaker, Illustrator 8 or 9, Microsoft Office 2000, or Norton Anti-Virus 2002? There are issues running the client version of SETI. >>



Yes, we use Outlook 2000, Office 2000 and NAV (which is server-controlled, rather than host-based). As much as I would like to run the service 24x7, me thinks it would probably be best to use the scheduling option in Shuxclams script to set the hours to downtime.

Has anyone figured out a way to distribute without requiring the workstations to be logged in as an administrator? That's the only thing holding me up now! >>



Ok, this is what I'm thinking. I believe you said earlier that you had access to remotely edit the registry on these boxes. First thing you need to do is get a text file of all the workstations you'll be working on. This will be needed to do my previously recommended xnet start/stop as well as this part of it. If you don't know where you're putting everything your SOL if you know what I mean.

This is just a general overview, I'll try to actually work on the scripts later. If someone else wants to get a head start, feel free. I may not have time until the middle of next week to work on this.

Basically it works like this, we need to write a batch file which will remotely edit the registry on each individual machine to add an entry to the runonce key. Upon next logon from any user it will call a script residing on your workstation that will install the service. The runonce key clears itself after it's run once (hence the name) so you won't have multiple instances on each workstation.

Another, not as clean, but easier method would be to write a script that adds a shortcut to the all users/startup folder that would call the install script. I would test this on a couple boxes manually first though. Since you mentioned that you have a mixed environment of NT/2K boxes you're going to have to pay attention to the correct install dir (c:\winnt\profiles vs c:\docume~1). You would have to pay attention to setiq to see when the machines d/l a packet, map back out there, remove the shortcut to the install script or put a line in the beginning of the install script to check for the existance of the executable (if exist c:\seti\seti.exe goto quit


I pretty much just rambled on there, somewhere in the mix are a few really good ideas. If I went back and reread it some of it probably wouldn't make sense but you get the idea. Unfortunately I'm going to be out of town over the next couple of days and won't be able to move forward with this. I'm sure there's plenty of good script writers out there who can take this all the way. If I get a chance to write any snippets I'll post them.

Good luck.