UNSOLVED
Latitude D520 Ghost Image
I work in a school & have recently taken delivery of 40 Latitude D520 laptops. I took an image of one of them using Ghost v7.5, which worked well until I tried to test the image by reloading it onto the same laptop. The key code I had used in the answer file was our volume license key, but after the new image had loaded, I was prompted to change the license key as the one I had used was the wrong one!! According to Dell, each key code they use is burnt into the bios of each machine & is serial number specific, so even if I had used their key code for that build, I would probably not have been able to use that image on any other laptop than the one used to create the image! - simply it was useless!
So, back to the drawing board, I started from scratch & rebuilt the same laptop using our own Windows XP disk & volume license code. I installed all critical Windows updates, & all other programs as before, then installed the Ghost Client software. All good so far. Unfortunately, I was not able to get any further as the laptop did not appear (even after waiting for several days!!) in the list of workstations in the Ghost Console. Neither did it appear in the list of Source machines when I tried to create a new image task.
I spoke to our school's curriculum support (CSE), but after asking me lots of relevant questions, it would appear I did everything correctly & they are as stumped as me. Dell don't seem to have much knowledge when it comes to Ghost, so I didn't bother them again.
Admittedly we are using an old version of Ghost, but why would it create the image of the original Dell build & not my new vanilla XP build with exactly the same setup & programs, etc?
If anyone can help I would be very grateful
- You will be pleased to know that I have successfully created an image of my laptop - many thanks for your help.In addition to adding the firewall exception in active directory, I also installed the .net 1.1 framework plus relevant Windows updates on my laptop as I realised that they were on the original Dell build. I then took the laptop off the domain & rejoined it.I guess we will never know which of these things fixed the problem, but I'm just happy that it now works.Thanks again :)
- Yes we do have Windows Firewall enabled and when I checked the program exceptions, the one for Ghost Client was configured at a low level in the Active Directory structure, so I have copied it across to the Default Domain Policy to see if that makes any difference. Many thanks for your help - watch this space!
dfrey
1 Message
289
0
Posted October 18th, 2006 01:00