Rebooting 2003 server automatically?

  • Thread starter Thread starter Mark N.
  • Start date Start date
M

Mark N.

I used to run shutdown.exe with a batch script via the AT command in Server
2000, but now that I'm upgrading to Server 2003, it appears that batch files
are untrusted by the OS. So, how can I get around this or is there a better
way to reboot a server automatically after-hours?

Thanks,
Mark
 
What happens when you try to run the batch script?

Andrew Hodes
MCP, MCSA, MOS Master http
 
I used to run shutdown.exe with a batch script via the AT command in Server
2000, but now that I'm upgrading to Server 2003, it appears that batch files
are untrusted by the OS. So, how can I get around this or is there a better
way to reboot a server automatically after-hours?
Click to expand...

1) Regularly rebooting a file server is almost always a cover-up of some
other flaw; that flaw should be corrected.

2) AFAIK batch files need special treatment under NT5.2 only if they are
invoked from a remote location by UNC or mapped network drive letter.
Bring the batch file to the server locally, or declare the remote host a
member of the "Local intranet" in Internet Explorer (I'm not making this
up). Use the form file://servername.
 
1) Regularly rebooting a file server is almost always a cover-up of some
other flaw; that flaw should be corrected.
Click to expand...

I reboot once per week just because this is Windows - it isn't Linux or
Novel... 'nuf said...
Can't do it during working hours.


2) AFAIK batch files need special treatment under NT5.2 only if they are
invoked from a remote location by UNC or mapped network drive letter.
Bring the batch file to the server locally, or declare the remote host a
member of the "Local intranet" in Internet Explorer (I'm not making this
up). Use the form file://servername.
Click to expand...

These batch files are local and are called by the AT command.
 
What happens when you try to run the batch script?
Andrew Hodes
MCP, MCSA, MOS Master http
Click to expand...


Well, the ones that are supposed to run via the AT command simply never run.
If I try to launch them manually, I get a dialog that warns me about the
potential hazards of such files and asks me if I'm sure that I want to open
it. If I say, "yes" it will open and run just fine. I suspect that when
the AT command tries to execute these batch files, it encounters a similar
problem but can't handle the challenge from the OS and so, nothing happens?
That's my best guess as to what's happening.
I have another batch file that used to automatically download Sophos virus
defs and it's encountering the same problem...

Thanks,
Mark
 
I reboot once per week just because this is Windows - it isn't Linux or
Novel... 'nuf said...
Can't do it during working hours.
Click to expand...

I have more than one Windows 2003 server that has not been rebooted in
many months, all are under load, stable, and seem to be running fine
24/7.
 
I reboot once per week just because this is Windows - it isn't Linux or
Novel... 'nuf said...
Can't do it during working hours.
Click to expand...

I'm not averse to Microsoft-bashing myself, but rebooting a server just
because it's Windows seems a bit harsh and unwarranted. No properly
administered server should require it. What exact errors do you
encounter if you don't reboot?
These batch files are local and are called by the AT command.
Click to expand...

I can't replicate that. Double-clicking a local batch file on a NT5.2
server will execute it without any warning. Only if the batch file
itself or any executable it might call is remote will I get warnings.

I have plenty of scheduled batch files running on NT5.2 servers, albeit
not through AT but through the GUI "Scheduled Tasks". Any reason why you
don't want to use that?
 
I have more than one Windows 2003 server that has not been rebooted in
many months, all are under load, stable, and seem to be running fine
24/7.
Click to expand...


I only have one that actually gives me trouble and that one's running an
early version of Firebird. The rest are pretty stable, but I've always
scheduled my servers for a weekend reboot - for many years. Call it
superstition or whatever, but I've always done it.
 
I'm not averse to Microsoft-bashing myself, but rebooting a server just
because it's Windows seems a bit harsh and unwarranted. No properly
administered server should require it. What exact errors do you
encounter if you don't reboot?
Click to expand...

No errors really. What is harsh about rebooting a server? That concerns
me - am I causing damage of some sort?



I can't replicate that. Double-clicking a local batch file on a NT5.2
server will execute it without any warning. Only if the batch file
itself or any executable it might call is remote will I get warnings.
Click to expand...

I'm not certain, but it may be related to Sophos Antivirus? I just ran a
batch file on another 2003 server without any problem. I will have to dig
in a bit more now that I've discovered this.

I have plenty of scheduled batch files running on NT5.2 servers, albeit
not through AT but through the GUI "Scheduled Tasks". Any reason why you
don't want to use that?
Click to expand...

It's not that I don't want to use it, I just never have. I have a batch
script that sets the AT command on fifteen of my servers with just a
double-click and I've just always used that. I'll see if the GUI version
works any differently.
 
I only have one that actually gives me trouble and that one's running an
early version of Firebird. The rest are pretty stable, but I've always
scheduled my servers for a weekend reboot - for many years. Call it
superstition or whatever, but I've always done it.
Click to expand...

I've seen that practice many places, and it's mostly due to one of two
things - crappy software installed on the server (even in the NT4 days)
or bad drivers/hardware on the server.

I had a PDC/BDC running NT 4/sp3a for over three years without a reboot
at a factory, this was common. In most installs I get to spec ALL of the
hardware, down to drive vendor, scsi card vendor, memory vendor, etc...
It really makes a difference.
 
No errors really. What is harsh about rebooting a server? That concerns
me - am I causing damage of some sort?
Click to expand...

OK, I misformulated: I didn't mean to say that rebooting a server is
harsh but that blaming Microsoft for it is.

No damage that I can think of, except you might be masking other errors.
I'm not certain, but it may be related to Sophos Antivirus? I just ran a
batch file on another 2003 server without any problem. I will have to dig
in a bit more now that I've discovered this.
Click to expand...

I don't mean to sound rude, but I would have expected some rudimentary
testing on your side before you bring your problem into this newsgroup.
It's not that I don't want to use it, I just never have. I have a batch
script that sets the AT command on fifteen of my servers with just a
double-click and I've just always used that. I'll see if the GUI version
works any differently.
Click to expand...

That seems like a perfectly satisfactory and highly effective setup. I
only mentioned the GUI to fully describe my environment where batch
files work, concentrating on the differences to your description.
 
I don't mean to sound rude, but I would have expected some rudimentary
testing on your side before you bring your problem into this newsgroup.
Click to expand...

Gee, that one did slip my mind and I apologize for wasting your time. How
'bout killfiling me?
 
Back
Top