Re: SBS 2003 R2 Shutdown Problem
- From: "Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 14 Jan 2008 15:49:55 -0800
Switch to scripted shutdowns, tie it to a group policy, and you should solve the problem. It has on every SBS network I've run across so far that's had the problem.
--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel
"dpnews" <dpnews@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:3C4BBE79-002A-4025-ABF6-37793EA9DB59@xxxxxxxxxxxxxxxx
thanks for your reply.
We are running kaspersky av. Did not previously have any shutdown problems
with this solution
"Steve" wrote:
Trend is an antivirus program (with additional features) that is commonly
used on SBS boxes.
"dpnews" <dpnews@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:60D490B1-0B94-4F7A-957C-0F64E7B20AB7@xxxxxxxxxxxxxxxx
> Many thanks for everyones comments.
>
> What is Trend ?
>
> The other thing I forgot to mention is that just before christmas we > added
> a
> win 2003 std R2 server to run terminal services. The sbs2003 server is
> configured as the license server.
>
> I have only just noticed that reboot or shutdown does not work as we > have
> not had to reboot the machine until now.
>
> "kj [SBS MVP]" wrote:
>
>> Charlie Russel - MVP wrote:
>> > Now that's a good idea! I like it. Thanks, KJ. I'm such a die-hard
>> > command line guy that I honestly haven't gotten nailed by >> > forgetting.
>> > But I've known enough others who have, certainly.
>>
>> Besides us old dogs who, even with an icon on the desktop would forget
>> from
>> time to time, the UPS system shutdowns, software addons /installs >> (less
>> often an issue on SBS) windows updates, and about anything else >> besides a
>> blue screen will run the shutdown script.
>>
>>
>> >
>> > The other thing I would do if I had a Trend environment is to do a
>> > similar script for Trend as I have done for Exchange. Manually
>> > shutting down Trend before you begin the restart. And call that
>> > script after the exchange, I suspect, though I'd have to experiment.
>> >
>> >
>> > "kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
>> > news:%238EfqXtVIHA.4140@xxxxxxxxxxxxxxxxxxxxxxx
>> >> Charlie Russel - MVP wrote:
>> >>> Trend can be an issue, if you're running it. But there are >> >>> machines
>> >>> seeing this with no trend on them. I'd suggest using shutdown
>> >>> command scripts that first shutdown Exchange, then shutdown the
>> >>> server. I wrote some a while back and they're posted on Susan
>> >>> Bradley's blog for everyone to use. And they seem to solve the
>> >>> problem on those machines that have shown it in the past. But it
>> >>> means you have to change habits and always use them - if you >> >>> forget
>> >>> and auto-reboot from the GUI the scripts can't help you.
>> >>
>> >> Old dog Exchange guys were always forgeting... until it was too
>> >> late. If you create a group policy object - computer shutdown >> >> script
>> >> (linked to the domain controllers OU) then you need not worry about
>> >> forgeting - it'll just run for you ! (DCs that don't happen to have
>> >> Exchange Services work fine with your script and other similar >> >> ones)
>> >>
>> >>>
>> >>> google Charlie shutdown site:msmvps.com/blogs/bradley - the first
>> >>> hit is:
>> >>> http://msmvps.com/blogs/bradley/archive/2007/11/17/charlie-russel-on-shutdown.aspx
>> >>>
>> >>>
>> >>>
>> >>> "dpnews" <dpnews@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >>> news:00CD8555-7378-4617-BF9A-6BC14C51645A@xxxxxxxxxxxxxxxx
>> >>>> We have a SBS 2003 R2 Server that appears to hang on shutdown. I
>> >>>> left it for
>> >>>> over 24hours (over the weekend) and it had not shutdown. After >> >>>> 10
>> >>>> minutes or
>> >>>> so the screen goes blank and thats it. You have to manually >> >>>> power
>> >>>> off the server and restart it. As we are running mirrored raid >> >>>> the
>> >>>> Intel matrix system then forces a rebuild of the array. This >> >>>> seems
>> >>>> to corrupt the access
>> >>>> 2000 database that we use for our main system. When users first
>> >>>> log back in
>> >>>> they can open the database but shortly after any users who open >> >>>> the
>> >>>> database
>> >>>> get a repair required errror.
>> >>>>
>> >>>> What I would like to know is does anyone have any ideas about >> >>>> what
>> >>>> might be
>> >>>> causing the problem and if not is there any log files or any >> >>>> other
>> >>>> method of
>> >>>> tracking what processes are happening (or not as the case may be)
>> >>>> when the system is trying to shutdown or restart.
>> >>>>
>> >>>> Cheers
>> >>>> Dave
>> >>
>> >> --
>> >> /kj
>>
>> -- >> /kj
>>
>>
>>
.
- References:
- Re: SBS 2003 R2 Shutdown Problem
- From: Charlie Russel - MVP
- Re: SBS 2003 R2 Shutdown Problem
- From: kj [SBS MVP]
- Re: SBS 2003 R2 Shutdown Problem
- From: Charlie Russel - MVP
- Re: SBS 2003 R2 Shutdown Problem
- From: kj [SBS MVP]
- Re: SBS 2003 R2 Shutdown Problem
- From: dpnews
- Re: SBS 2003 R2 Shutdown Problem
- From: Steve
- Re: SBS 2003 R2 Shutdown Problem
- From: dpnews
- Re: SBS 2003 R2 Shutdown Problem
- Prev by Date: Re: Shadow copies hungs sbs 2k3 1/14/2008 7:12 AM PST
- Next by Date: RE: DNS Issue with VPN clients through ISA Server
- Previous by thread: Re: SBS 2003 R2 Shutdown Problem
- Next by thread: Free backup utility?
- Index(es):
Relevant Pages
|
Loading