Anthony_McAuley
28 Sep 2004, 12:11pm
Hi all.
Please excuse my ignorance here, but it's the first time I've encountered PXE in a domain environment and therefore do not know if I'm using the correct terminology :)
We've got a domain from an aquired company that uses PXE to boot PCs running Windows NT4. Disabling the PXE stops the NT4 machine from booting correctly, and investigation has shown that roughly 8 configuration files are pulled down from a LINUX box. We have tried copying those files locally, and that seemed to be successful but it only worked for a short while before the PC reverted back to it's original state :banghead:
My question is this : is there an easy way to stop these PCs from booting via the network and make them stand-alone (but networked in a domain) Windows NT4 machines, without having to reinstall the operating system on them all. This is in a buisness and factory environment so downtime is a premium.
Thanks for taking the time to read this, and I hope someone out there has the answers I seek :)
Please excuse my ignorance here, but it's the first time I've encountered PXE in a domain environment and therefore do not know if I'm using the correct terminology :)
We've got a domain from an aquired company that uses PXE to boot PCs running Windows NT4. Disabling the PXE stops the NT4 machine from booting correctly, and investigation has shown that roughly 8 configuration files are pulled down from a LINUX box. We have tried copying those files locally, and that seemed to be successful but it only worked for a short while before the PC reverted back to it's original state :banghead:
My question is this : is there an easy way to stop these PCs from booting via the network and make them stand-alone (but networked in a domain) Windows NT4 machines, without having to reinstall the operating system on them all. This is in a buisness and factory environment so downtime is a premium.
Thanks for taking the time to read this, and I hope someone out there has the answers I seek :)