I think the only issue is that if your server is using a RAID controller you may need to get the DOS drivers for the RAID controller.. which could be a bit of extra hassle.
You can ghost NT no problem.
Pay particular attention do DMA mode if the disks are IDE.
Drives should be in the same mode..
If you ghost NTFS, you might need to add some switches to the ghost command, depending on the version off ghost you are using.
You will fond out which by getting the help file of your ghost software.
You will definitely need to change the SID. I know there are Freeware programs out there to do this. I have used something called changesid (I can't remember where it came from though).
I think you need only change the SID if you're cloning the machine so that 2 or more are on the network at the same time.
If you back up a machine using GHOST with the intention of being able to roll the machine back to a setup on a given date, then there is no need to replace current SID with a new one.
In other words there cannot be 2 of the same SID on the same network - which would only arise if you copied a machine image to multiple machines as a time saving setup tool.
GHOSTWALKER does this from Symantec - supplied with GHOST. Boot with GHOSTWALKER DISK follow instructions.
The only recommendation I have is NOT to image NT 4.0 Server that is a PDC or a BDC. It doesn't work and is not recommended by Microsoft or any of the image vendors I have contacted.
I've set-up a standalone server using Windows 2000 Server software. I've loaded all of our company's standard softwares on this server. Actually, our company have more than 1,000 machines to upgrade so I decided to put up a server in order to expedite the upgrade (through ghost). I've created the boot disk as well with the necessary script. When I start ghosting the PC, it boots through the network but always ending up with the annoying error: "error 53: the computer name specified in the network path cannot be located".
Can anyone help me on this matter. If you require further details, pls. let me know.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.