Network Boot Disk & DC Authentication

Does anybody know if it is feasible to create a network
boot disk that will allow authentication to a W2K3 domain
controller for ghosting purposes?
I currently have a boot disk that will successfully login
to a P2P W2K3 server and perform the ghost process,
however when the W2K3 server is promoted to a domain
controller, the process fails when requesting password
authentication. I used the FQDN in my batch process and
still have no success.
It would seem idiotic for MS to not allow a function such
as this to be performed, but then again they want
everybody to use RIS instead of GHOST.

TIA for any input.

"Bwalker" <(E-Mail Removed)> wrote in message
news:024201c48aea$17bb2ea0$(E-Mail Removed)...
> Does anybody know if it is feasible to create a network
> boot disk that will allow authentication to a W2K3 domain
> controller for ghosting purposes?

User the Ghost Server. You don't log into anything, you just activate the
NIC driver and that is all. The Ghost Client searchs for the listening
Ghost Server via the Session Name.

> I currently have a boot disk that will successfully login
> to a P2P W2K3 server and perform the ghost process,
> however when the W2K3 server is promoted to a domain
> controller, the process fails when requesting password
> authentication.

2003 Domains by default will not allow a DOS, Win95, NT4 Pre-SP3 to log into
them,...unless you want to hack the registry and reduce the security of the
entire domain.

811497 - Error Message When Windows 95 or Windows NT 4.0 Client
Logs On to Windows Server 2003 Domain
http://support.microsoft.com/default...b;en-us;811497

> I used the FQDN in my batch process and
> still have no success.

Never use a FQDN with a DOS client. FQDNs will never function without DNS to
provide for the name resolution.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com