Currently, it's just the one machine, but this machine is to become the base
image for the rest of the deployment (34 more machines).

"Ron Lowe" wrote:

"sean" wrote in message
...
Greetings,

Let me start with that I have read the previous thread about this message
and DNS needing to be pointed at the AD DC only, also I have verified this
on
my network and it is the case. According to all the other threads and
other
web postings I've read, they give the same resolution, but in my case, it
doesn't seem to be it. The AD DC is the only DNS server on this network
and
it is pointing to iself for DNS with hints to fall back on and it hands
out
the info to the clients via DHCP, where they receive the only DNS info is
the
AD DC, but I still get the "please wait...." that can be stopped for the
moment with the three finger salute. Any suggestions where I should look
next. Also, this is happening on only a few machines from one source Ghost
image.

Thanks


Is this affecting one machine, or many machines?
Anything in the event viewer of the problem machines?


--
Best Regards,
Ron Lowe
MS-MVP Windows Networking