First try "Scripted Installation" demo
I'm following the demo and I'm on Step 3 "Scripted Installations". When I'm at the target PC, I do a network boot and it works. I get the Kace window, and it maps X: and then a bit later it tries to map Y: to \\k2000\peinst. This fails with a "system error 1231". Basically it is unable to map the drive. I can see from the appliance that the target PC was using 192.168.40.82 as an address. But if I do an IPCONFIG in the DOS window of the target PC, it doesn't seem to have an IP address - and I'm unable to ping it. If I go to my PC, I am able to map \\k2000\peinst - so the drive share is available.
Any ideas?
Thanks
Any ideas?
Thanks
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
chrisgrim
13 years ago
pgpete,
If you do IP config and have no IP address, it is most likely that the KBE doesn't have the network driver for your system. If you upload the driver to the KBE directory on the driver share and then get the WAIK and rebuild the KBE, you should be fine. This is documented in the K2000 Admin Guide under Manually Adding Drivers, and Building a New Windows KBE. It is also written up in this FAQ: http://www.kace.com/support/kb/index.php?action=artikel&cat=59&id=935&artlang=en, which can be found by searching the web site for KBE Drivers.
Chris...
If you do IP config and have no IP address, it is most likely that the KBE doesn't have the network driver for your system. If you upload the driver to the KBE directory on the driver share and then get the WAIK and rebuild the KBE, you should be fine. This is documented in the K2000 Admin Guide under Manually Adding Drivers, and Building a New Windows KBE. It is also written up in this FAQ: http://www.kace.com/support/kb/index.php?action=artikel&cat=59&id=935&artlang=en, which can be found by searching the web site for KBE Drivers.
Chris...
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
