Discussion Locked

Need a temporary 2000 Scheduler tool

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I need a low cost 2000 scheduler that can fire off .exes per our specs.

We will be looking at high end Enterprise level solutions in the future, but I need to migrate a bunch of old apps off of a bunch of old servers and onto a Win2k advanced server box, and need a solution for a short time only. I am willing to pay a reasonable shareware fee or purchase a lower end Packaged App, but don't want to get into the Enterprise level stuff for this as we are in the discovery process on that end ofthings but are not ready to decide until we review MS AppCenter/AppServer next month.

This needs to be as bugfree as is reasonably possible to expect as it will affect production sites.

6 replies

by ntoz

Is there a reason your not using the built in Scheduler in Windows 2000? Its as cheep as they come as its part of the OS? If you required special requirments it doesnt provide you can always kick off a WSH to do what you need and then use the Scheduler service to run it.

by testmaster

I perhaps should have been specific that the developers have ascertained that this solution will not work for technical reasons having to do with running stored procedures on machines in another address space and domain.
It is the solution we are using for machines "Local" to each other, but does not work well in the Enterprise across the WAN which encompasses servers in 197 locations throughout the world... But I thank you for pointing it out.

by ntoz

I understand your need from your follow-up, I still have to pose one more suggestion though, have you tried using a combination of the Schedualer, WSH and Runas.exe? You should be able to use a combination of the three and a plain text file that youcan list all locations in. In firing the script you could use WSH to parse the text file that contains the list of locations and the runas to use the appropriate token in which to fire off your commands.

Pete

by testmaster

Hmmm... we are getting closer... but how do we deal with the authentication across domains? Especially an untrusted one? Can you give me an example of how this would be written? I am willing to conceed the answer points to you on your next message if we can get something concrete I can take to the team in the morning.

by ntoz

What do trusts have to do with anything? If you have a valid userid and password in the domains you need to execute something, trusts dont matter. With WSH, if your "Developers are worth anything", they should be able to script the whole thing in short order, even if it means 190 different userid's and passwords. Even if you had a high $$$ tool you would still have to supply a valid userid and password for every domain you wanted to execute what ever it was your doing! In fact to come right down to it, if you were relying on trusts, you would still have the same issues with a High $$$ tool anyway, so whats the point?

by testmaster

You are assuming we are all on the same trusted network segments and that an entity outside the firewall has the priveledge to run an .exe on the boxes in question. That is not the case. The point is that we will be doing that with an Enterprise tool (high $$$, as you say, yes), in 2000 native mode, and relying on active directory security, which greatly simplifies the need. There are other complications I cannot get into without you signing an NDA, which is not necessaary to this discussion. Let me put it another way.
We have an ISP for one miniscule portion of the network, which cannot be migrated until this is done and the Developers fix a LOT of code. But, the migration has a schedule, and come hell or high water the ISP will be gone June 1. We do NOT trust anything coming from this domain, and there is a way we deal with it that will go away once I reach that point, but to get there I need a bandaid.
I am willing to grant you 2000 points to detail the solution for me.
Stillinterested?

This discussion is closed to new replies.