zartanch
asked on
How to properly do a Windows 2000 Server Ghost Image?
Hi,
I've created many Ghost Images for the servers we use for customers.
However, recently more and more I get an error that crashes the server twice weekly which is horrible for customers:
///
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x80485ac0
Debug session time: Fri May 20 20:42:03.968 2005 (GMT-4)
System Uptime: not available
///
I can sometimes do a repair Windows install and it 'seems' to do the trick. But I would feel a lot more confident if I could just create a proper Ghost Image to start with.
So here's some questions:
- How do I properly do a Ghost Image of a server that has the same motherboard (Asus P4P800-MX)
- Do I go all the way and install SP4, the Chipset Drivers, Directx, Video Drivers AND all Windows Updates?
- Or do I just install SP4 and do everything later on deployment?
Your help would be appreciated... nothing is worse than setting up a customer with a server that will crash or reboot itself the first week. :(
I've created many Ghost Images for the servers we use for customers.
However, recently more and more I get an error that crashes the server twice weekly which is horrible for customers:
///
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x80485ac0
Debug session time: Fri May 20 20:42:03.968 2005 (GMT-4)
System Uptime: not available
///
I can sometimes do a repair Windows install and it 'seems' to do the trick. But I would feel a lot more confident if I could just create a proper Ghost Image to start with.
So here's some questions:
- How do I properly do a Ghost Image of a server that has the same motherboard (Asus P4P800-MX)
- Do I go all the way and install SP4, the Chipset Drivers, Directx, Video Drivers AND all Windows Updates?
- Or do I just install SP4 and do everything later on deployment?
Your help would be appreciated... nothing is worse than setting up a customer with a server that will crash or reboot itself the first week. :(
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
<< post edited for profanity by humeniuk PE - 22 May 2005 >>
First of all, after reading your post it looks like you're ghosting a lot of servers for quite some time now.
The guys above me here all have good advice/pointers. But since you're a guy with lots of experience in ghosting, and along that time came across a lot of ghosting errors/problems, we dont need to tell you about that images only work for the same hardware, chipsets, drivers, .....
No, if you 're sure about those devices and settings, look at the way you're ghosting. Maybe youre image is worned out? Maybe the router/switch/hub/cable/..
Go out, find a 200% working server, image that one again, use that image for youre troubled servers and tell us if you got the problem.
MrAruba
First of all, after reading your post it looks like you're ghosting a lot of servers for quite some time now.
The guys above me here all have good advice/pointers. But since you're a guy with lots of experience in ghosting, and along that time came across a lot of ghosting errors/problems, we dont need to tell you about that images only work for the same hardware, chipsets, drivers, .....
No, if you 're sure about those devices and settings, look at the way you're ghosting. Maybe youre image is worned out? Maybe the router/switch/hub/cable/..
Go out, find a 200% working server, image that one again, use that image for youre troubled servers and tell us if you got the problem.
MrAruba
ASKER
Thanks, these are for cookie cutter "servers" for low-cost hosting.
That's the reason we don't use server boards on anything but demanding hosting like database or email servers.
This is for recreational and game servers.
That's the reason we don't use server boards on anything but demanding hosting like database or email servers.
This is for recreational and game servers.
I'm a bit worried about the idea of ghosting servers for different functions. I have no probs with ghosting a server to move disks, or resize partitions, but it sounds like you're trying to use it for rollouts.
I'd be more wondering that there was something screwed in the original Ghost image or -gasp- the P4P800-MX has inherent issues with W2k Server. I mean you are using a consumer grade motherboard, not a Business Grade server motherboard.