Jump to content

Recommended Posts

Posted

My main DC updated last night. It completed the updates, Stalled on 100% with the do not turn off dialogue. Eventually I had to manually restart the server this morning which caused no end of problems with the server freezing solid when you logged in. Finally rebooted it into safe mode and ran scan disk on all drives. I then rebooted all of the servers, logged back in and left it for 10 minutes at which point it gave me a "failure to open security options dialogue" error. Rebooted it again and it seems to be fine.

 

Nothing showing up in event viewer to say what went wrong either.

 

Hell of a way to start the day.

 

Server 2008 64bit edition.

  • Thanks 1
Posted
Your pretty brave to be running your DC's on 2008 already! I wouldn't touch them for a couple of years yet personally.
Posted
Your pretty brave to be running your DC's on 2008 already! I wouldn't touch them for a couple of years yet personally.

 

they are up to service pack 1 already. They are no where near as clunky as 2003. The 64bit version just zips along. Login times are down to 5 seconds, 10 on the older systems.The old 2003 server was 45seconds - 3 minutes.

 

New servers = time to change the whole network. Completely new AD. :)

Posted
Hell of a way to start the day.

 

Mmm.. so have you turned off automagic installation of updates now like the rest of us (who prefer to pick and choose when we have our disasters)?

 

I got my very first blue screen the other day.. had been installing a few new features, then WebDav and an associated KB, but somewhere in there a couple of AU secfixes.. and it bluescreened when I shut it down (started up again OK though). I wonder..

 

They are no where near as clunky as 2003

 

::shrug:: Very few fresh installs on (presumably) new h/w are as clunky as some box you've been abusing for years.

 

I haven't seen anything scary about 2K8 yet. The only real drawback is the lack of quality info. Try googling for pretty much anything and there's truckloads of 'posturing' posts on the obvious shiny bits (e.g. bloggs with GBs of pointless screenshots that essentially amount to "I've played with X before you have! Na an na naah naaah!") or out at the other extreme, Powershell equivalents of Perl PGP sigs. Not a lot in the way of those quietly stated little tips and tricks that just makes admin's life easier - as in the stuff that really counts.

Posted
Your pretty brave to be running your DC's on 2008 already! I wouldn't touch them for a couple of years yet personally.

 

We are running server 2008, so its the Lancs GFL. Its a pretty solid OS

Posted
they are up to service pack 1 already. They are no where near as clunky as 2003. The 64bit version just zips along. Login times are down to 5 seconds, 10 on the older systems.The old 2003 server was 45seconds - 3 minutes.

 

New servers = time to change the whole network. Completely new AD. :)

 

2008 here too, mostly it's fine

 

Apart from MMCs which are unbelieveably sloooooooooooow.

 

I've certainly had enough of the event viewer :(

Posted
2008 here too, mostly it's fine

 

Apart from MMCs which are unbelieveably sloooooooooooow.

 

I've certainly had enough of the event viewer :(

 

I agree they have over complicated many areas.

  • 4 weeks later...
Posted

Same thing happened again today, everything installs correctly but hangs on reboot.

 

Its the 64bit version of server 2008, I shall be doing updates from now ar 3:15 to see if a manual reboot works.

 

The other servers install and reboot fine.

Posted

The only real drawback is the lack of quality info. Try googling for pretty much anything and there's truckloads of 'posturing' posts on the obvious shiny bits (e.g. bloggs with GBs of pointless screenshots that essentially amount to "I've played with X before you have! Na an na naah naaah!") or out at the other extreme, Powershell equivalents of Perl PGP sigs. Not a lot in the way of those quietly stated little tips and tricks that just makes admin's life easier - as in the stuff that really counts.

 

I am waiting for Mark Minasi to come out with a new book. He hasnt let me down so far :)

  • 2 weeks later...
Posted

Update:

 

Its not the updates that are the problem, its rebooting in general. A few other people are reporting problems, BIOS & Driver updates along with Anti Virus are fingered as likely culprits. So That narrows it down some :(

Posted

SMB 64 2008.

 

I have removed NOD32 and the HP management software, it restarted just fine. I'm not convinced its fixed by a long way but memory usage has dropped back from 91% to 25%. I'm not at all happy with leaving the server vulnerable so I will have to do something smartish as I think nod32 is definitely at fault.

Posted
SMB 64 2008.

 

I have removed NOD32 and the HP management software, it restarted just fine. I'm not convinced its fixed by a long way but memory usage has dropped back from 91% to 25%. I'm not at all happy with leaving the server vulnerable so I will have to do something smartish as I think nod32 is definitely at fault.

 

Isn't there a current open bug report related to ESET NOD32 and Server 2008. IIRC, I'm pretty sure there is a problem between the both of them.

  • Thanks 1
Posted
Isn't there a current open bug report related to ESET NOD32 and Server 2008. IIRC, I'm pretty sure there is a problem between the both of them.

 

Could well be, my other 2008 server works just fine, but its the 32bit version of 2008 and has 4 gigs of ram.

Posted
Could well be, my other 2008 server works just fine, but its the 32bit version of 2008 and has 4 gigs of ram.

 

Does the 64 server run ok without NOD32 on it? You could always call them up and ask whats going on, it is a server after all and needs to be protected at all costs.

Posted (edited)

Is it called NOD32 'cos it's 32bit ? 32bit running on a 64bit OS.........

 

From M$:

 

Can I run 32-bit programs on a 64-bit computer?

 

Many programs designed for a computer running a 32-bit version of Windows will work on a computer running 64-bit versions of Windows without any changes. However, in some cases there might be differences in performance. If a 32-bit program uses embedded drivers, the drivers might not work in the 64-bit environment. If you have a 64-bit computer, it's best to run programs designed to run on a 64-bit computer.

 

I have no plans on going 64bit yet 'cos of lack of drivers - if and when I do I will certainly be using as much 64 bit software as I can.

I seem to remember many years ago 16bit macros killing 32bit citrix sessions - [ CPU hogging ] - also the big push on PII CPUs when they came out - 16bit OS's running on 32bit CPUs - whats the point ????!!!!!

Edited by mattx

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...