XP RIS error

[shabadoo]

I have been using RIS to deploy XP for over one year now. Recently I got
some new systems in, and had to create another image for these. When I got
to the point of using riprep to push it up, I get this error "Domain
Controller Detected" during the wizard. This is at the compatibility screen,
and if you click on details it says "This utility cannot be run on a Windows
2000 Domain Controller". The box in question only has XP w/SP1 loaded from
the CD, with a small application for the client. There must be some logical
reason why this would occur, because this workstation is not a DC.

Thanks for any help you can give me...

shabadoo

 

[NIC Student]

Have you tried reinstalling the update to RIPREP from this article:

How to Deploy Windows XP Images from Windows 2000 RIS Servers
http://support.microsoft.com/default.aspx?scid=kb;en-us;304314

 

[shabadoo]

Thanks for the reply...I tried this and get the same result. I am able to
deploy other XP images with no problems, so it must be something simple that
I just don't know about.

 

[NIC Student]

I have only heard of this one other time. Do you get the error if you:

1. RIS an XP machine.
2. Do not patch it in any way.
3. Run RIPREP on it.

Have you patched the RIS server to Win2K SP4? Do so.

Are you deploying XP SP1 images or base XP with no SP?

Is the cd-based image on the RIS server XPSP1 or XP plain vanilla?

Please advise.

 

[shabadoo]

1-No
2-Have not tried this yet
3-YES, this is the only time I see this error
RIS server has SP4
I am deploying XP SP1 images, and XP plain images
I have both the plain and a copy of XPSP1 as my CD based images

Thanks...

 

[NIC Student]

I understand that your RIS works ok until you RIPREP a machine that has been
patched. I would start by identifying which update is causing the problem.

Note that patches that change the ntoskrnl.exe will generate an error,
although it is normally the "you don't have the cd-based version ....".
Make sure the ntoskrnl hasn't been updated and try to install one patch at a
time to see what is causing the prob.

--
Scott Baldridge
Windows Server MVP, MCSE


"shabadoo"

 

[shabadoo]

I was able to resolve the issue by pulling down the CD based XPSP1 image,
and then pushing that back up with nothing added. I then added each of the 3
security patches one at a time and was able to push the image up each time.
I then tweaked the image adding the few small applications needed for the
client one at a time and still had no issue. I really thought doing this in
baby steps would eventually get me to whatever was causing the issue in the
first place. Unfortunately it has not happened since. I had previously tried
this on 3 different Optiplex GX270's, and putting the OP Sys on 3 different
ways. Each of these potential images had the same things my image currently
has, but none of them would work. I still don't understand what caused the
error. Even though they now work for me, does any of this point to what
would have caused it? I want to be able to help someone else in the future.


Thanks for your help...

 

[NIC Student]

If you really wanted to know, you could install the three small apps and as
you do, use Winstall discover (discoz.exe) to make an MSI of the
installation. Then use the Winstall console to analyze the installed files
to see if a system file was installed or altered. What I just said is way
more work than I would ever do - I'm glad you have a solution, even if it is
a mystery.

 

[JB]

I am having the same issue with a new Gateway Profile 5. I have
several other PC images for XP that work just fine and did not get
this error when creating them. I used MS Select (XP Pro w/ SP1). I
also did just an XP Pro w/o SP1 and loaded SP1 separtly without any
success. Any help would be appreciated.

Thanks,

JB

 

[NIC Student]

Well, can you RIS the new machines with an existing RIS image, not tweak it
at all, then RIPPREP it? If you can then start there and add what you need
and test after each addition to see when it errors out. That will point out
the problem "tweak".