For most of the month we have been struggling to figure out why our
Win2K Remote Installation Servers suddenly stopped working. A power
failure and several other variables masked the cause of the problem.
Yesterday, I stumbled across a posting in
microsoft.public.win2000.setup_deployment from 2002-08-19 by Jeroen de
Jong. If you upgrade your RIS servers to SP3 and leave the DC's that
the RIS server authenticates with at SP2 you will not be able to deploy
pre-staged PC's. You will only be able to RIS, if "Do not respond to
unknown client computers" is unchecked on the Remote Install tab of the
RIS server's computer object in the AD. To solve the problem update
your DC's to SP3. While this may be "old news," Microsoft has not
documented this bug in any way that I have located.

As a footnote, if your production environment precludes you from
updating all DC's quickly, it appears that you can open the Active
Directory Users and Computers MMC on the RIS server and tell it to
connect to a DC that is on SP3. This appears to have the effect of
forcing the RIS process to communicate with that specific DC.

Jonathan DeMersseman
University of Kentucky
College of Arts & Sciences

oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Delivery co-sponsored by Prometric - More than testing, learning.
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
http://www.prometric.com

Prometric, part of The Thomson Corporation, is the leader in
technology-enabled testing and assessment services for information
technology certification, academic admissions, professional licensure and
certifications, computer-based driver's licensing, and corporate testing.
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]