Duplicate GUIDs error, when booting from floppy disk for RIS

No these images are not sysprepped I thought they did not need to be.

I thought the SID and the GUID were completely different numbers?

When I image a machine with the floppy it gives the same GUID everytime no matter what. Because of this I decided not to prestage the machines. I deleted the machines, I tried to make before, out of AD and then replicated the changes through Sites and Services. Imaged each machine and then changed the default GUID that it adds with a GUID I get from Hyena (AD like software). Once I replicate the changes I can install an image on another machine.
This way is slow and hokey, but for now it works. I have to find a better way before we can do our upgrade.

I didn't get any response with my last posting so I hope I'm doing this correctly.

Thanks
Shawn

HES_NSA,

  Did you ever find a better way?  I am having the same problem, my 3COM 3C2000T Gigabit NICs all have the same GUID: {00000000-0000-0000-0000-000000000001}.

First things first...Have you tried to boot from the NIC, instead of using the floppy? It just works better, taking your time to get this to work is worth it.
This will be done in the BIOS, Boot order. If there is no option in the BIOS then try a BIOS update, I had to do this for our Dells. It may be possible that you have to turn the option on in order to be able to tell the BIOS to boot from the NIC. For our Dells I think it was under an option in the NIC card it's self...called On w/MBA, I think the newer NICs say On w/PXE. Either way you select one of these options then save your changes in the BIOS, exit and come back in. Then you should see the NIC as an option in the Boot Order.
Also, are you going into the RIS server and changing the name for the new PC. If you have forgotten to do this and then try to do it on the fly it takes RIS a while to recognize the change, meaning you will still get the error for another 5 minutes. You can speed up that process by stoping and starting the binlsvc. {from command prompt..."net stop binlsvc"; then "net start binlsvc"}. Another trick I had to use to get AD to recognize all the changes...go into AD sites and Services and replicate to changes (like deleting the PCs) accross the domain so it didn't think they were still there.

RIS likes 3com; I went through alot to get this thing working, and everytime I hit a new kind of network card ( IBM, Broadcom) I have different problems.

Shawn,

Thanks for the idea of NOT using the boot floppy, I've had the same problmes and looked all over the internet to find the error of the invalid computer name error 00004E23.  We already had 3com nics so once I changed the bios all worked fine.  

One workaround that I did find is that by using different nic cards you could use the ris boot floopy for a one-shot install but then you couldn't reuse that nic to do another ris install.  Even after a few months...  Once thing that I did notice is that when you use the boot floopy it wont grab the GUID it will come up with all 0's with the MAC address at the end.  So my guess is that when you use the nic a second time to do a RIS install it will see a duplicate computer because of course all the 0's and mac address match the previous computer.  I've tried all kinds of things to get rid of this duplication including RESET ACCOUNT (reset computer account), reboot the server, messed around with DHCP settings, throw things... ect...

Once I used the 3com tftp boot and not the floppy it grabbed the GUID correctly, I even tried re-imaging the same computer 3 times and it worked everytime.  I'm all about using a 3-com cards for RISing.

Lee

Hi

I am having the exact same problem as HES_NSA

I installed RIS in my domain and used it to install win2k on one computer.
Later, after thinking that I'm all set, I installed Ghost 8 Corporate ed. on the RIS server, that let me add a new item to the RIS menu -> boot into ghost.exe, that was I am able to but a PXE-supported nic right into ghost and use ghostcast to clone images.

I cloned one image succesfuly and ever since I've been getting the same message:

"The server (server name) has detected duplicate GUIDs in the directory services. The Duplicate existing machine names are: (no names are given)"

I've been wondering clueless trying to figure this out in numerous sites and after seeing this question here, I signed-up but there's no actual answer here either.

I downloaded PSGetSID but that doesn't help because it only scans for a specifiec computer SID (hoping that SID = GUID) and I already disjoined one of the computers I cloned from the domain and deleted its account but I still get the same message.

PLEASE I would really appreciate any help with this.

Also, if there's any other way I can use PXE to ghost computers I would like to know about it.

Moran Lankry
SigValue LTD