RIS - invalid domain was specified

  • Thread starter Thread starter John Smith
  • Start date Start date
J

John Smith

Error: "An invalid domain was specified. Would you like to proceed
for now and try joining a domain later."

I get this error during the mini-setup portion of RIS when the PC is
added to the domain.

I have been seeing these errors more frequently lately, but it is not
with every image and only on certain hardware types. My sifs are all
identical (except for the stuff that has to be unique; HAL, Help Text,
etc).

What is stranger to me is that if I click "NO" and then manually click
next on the "Add PC to Domain/Workgroup Screen" (which already has the
correct domain filled in), login with the same credentials that I used
to start the RIS, it adds the PC, and finishes the setup. I was
thinking maybe driver issues, but then why would it still let me add
the workstation, and not do it unattended. It is more annoying than
anything as the image and everything else works beautifully. I cannot
really find any documentation on this error. I am sure that it is
something that I am missing, but am getting frusturated, and am hoping
that someone has resolved this before.

Any help would be appreciated.

-John
 
Do you think it is caused by network conditions? Is your domain entered as
fully qualified (domain.com rather than domain)? Are you using the custom
install when this happens?

It will be hard to guess, maybe you will have to keep some notes to try and
narrow down what is happening.

--
Scott Baldridge
Windows Server MVP, MCSE


"John Smith"
 
I am thinking that it might be network conditions. I haven't had a
chance to really play with it more since I posted the original
message. I am using the custom install, and the FQDN. I am just
using the %SERVERDOMAIN% variable in the login.osc, and
%MACHINEDOMAIN% in the sif. I think it is related to our site setup
(or lack there of). Kinda a long story, but we had some issues with
some other services when we seperated our sites in AD, and haven't had
time to resolve everything, so rolled back. In short the clients
aren't always authenticating to the local DC. I am pretty sure that
is the issue, but we don't have any login issues, or issues joining
PC's manually, so I thought it could be something else. I'll follow
up with more when I get a sec to play. In any case we need to get the
sites seperated.

Thanks for the feedback.
 
Back
Top