R
Robert R Kircher, Jr.
My current deployment method has been RIS. I have 4 images which install
any PC I put on the network. Some have PXE network cards other need the use
of a PXE floppy. It all works great. If there are driver changes I just
change the $OEM$ folders and update the SIF file. Perfect.
All of this is running on a single Server AD environment. This server runs
AD, DHCP, DNS, WINS et al.
Well now I've updated to SP2 and installed WDS and nothing works. My PXE
boots give me a message about no boot image found and I'm getting a WDServer
error, Event ID 769 and 770 in my event log. I'm very frustrated that what
once worked flawlessly now is useless.
Can anyone shed some light on how to use WSD with legacy images? Is there
any white papers that help us migrate from RIS to WDS? Can I create new XP
and 2003 server images under WDS?
Any help would be greatly appreciated.
--
Rob
"A disturbing new study finds that studies are disturbing"
any PC I put on the network. Some have PXE network cards other need the use
of a PXE floppy. It all works great. If there are driver changes I just
change the $OEM$ folders and update the SIF file. Perfect.
All of this is running on a single Server AD environment. This server runs
AD, DHCP, DNS, WINS et al.
Well now I've updated to SP2 and installed WDS and nothing works. My PXE
boots give me a message about no boot image found and I'm getting a WDServer
error, Event ID 769 and 770 in my event log. I'm very frustrated that what
once worked flawlessly now is useless.
Can anyone shed some light on how to use WSD with legacy images? Is there
any white papers that help us migrate from RIS to WDS? Can I create new XP
and 2003 server images under WDS?
Any help would be greatly appreciated.
--
Rob
"A disturbing new study finds that studies are disturbing"