Dear All,

Please advise for step by step how to deploy OS with K2000.

Thanks,

PS.For your information, I already use WAIK to upload image Windows 7 (x64) to K2000 but after my client BootPXE it show 2 error message

ERROR: Unable to determine server IP address from DHCP

WARNING: Using hardcoded K2000 IP address as fallback

ERROR: Unable to mount K2000 share at \\192.168.1.190\peinst

but I confirm I never set share drive on K2000. so please advise me for how to deploy OS with K2000 thanks

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

5

From that same screen where you get the error what are the results of running IPCONFIG?

It sounds like you do not have the correct drivers in your KBE. I would add the correct ones and build a new KBE.

 

These links may help.

http://www.kace.com/support/resources/kb/article/how-to-create-a-kbe-pre-boot-environment

K1000 KKE's: https://support.software.dell.com/k1000-systems-management-appliance/kb?k=KKE

Answered 09/17/2012 by: dugullett
Red Belt

  • Hi dugullett,

    I get this error when I try to bootPXE from my client machine. and I create new KBE already. Any idea?
    • Does IPCONFIG return anything? Are you able to PXE any other machines?
Please log in to comment

Answers

4

with "ERROR: Unable to determine server IP address from DHCP"

Check that your options 66&67 are configured on that subnet you are booting on

see page 37 of

http://www.kace.com/support/resources/~/media/Files/Support/Documentation/K2000-Admin-Guide-v34.ashx

Answered 09/18/2012 by: SMal.tmcc
Red Belt

Please log in to comment
3

It could be that you do not have propper drivers injected into your boot media, OR that your media is unable to pick up the DHCP information for your KBOX, this usually happens when you're running another tandem pxe boot service (here we run KACE and WDS as two side by side boot services) or if your DHCP options arent configured correctly, either way you'll need to get a hold of the KNIT (link provided below) and punch in the static information for your KBOX.

http://www.kace.com/support/resources/kb/article/KACE-Native-Imaging-Toolkit-for-K2000-v-3-4-ONLY

The links provided by dugullett should help you on the way to recreating your boot media also.

Answered 09/17/2012 by: Roonerspism
Second Degree Brown Belt

  • Dear Roonerspism,

    For our company we use switch level 3 for DHCP and Dell Technical advise we use this config for that switch. (Please see below)

    ip dhcp pool name
    network ip subnet

    bootfile k2000.0

    next-server ip_of_kbox

    default-router gateway

    dns-server dns1 dns2 dn3

    lease 0 4

    Did you have experience before about use switch level 3 for deploy OS with K2000? Please advise me thanks
  • So long as the iphelper is configured on your core/switching infrastructure that should all be good (I'm the soe/deployment guy here not so much the infrastructure guru)
    Maybe try the KNIT and build some boot media which references the kbox ip directly just in case. I've never used the K2 with a switch as the dhcp, always win2k8r2. It may be that the current boot media is looking for the options usually provided by operating system bound dhcp servers and your switch is unable to serve this information.
Please log in to comment
1

Dear All,

Now I can setup level 3 Switch for PXE Boot already but I still can't deploy OS to client machine so could you please advise me step by step how to setup script on K2000 for deploy OS to client.

PS. After I PXE Boot my client machine can detect K2000 and loading image but after restart it show error:

Bootmgr is missing

Press Ctrl+Alt+ Del to restart

Answered 09/25/2012 by: manpang
Fourth Degree Green Belt

  • most likely partitions of target are different then script
Please log in to comment
0

I had the same problem running virtual machine environment... and the problem solved it self when i installed correct NIC... so try to download correct driver for your NIC and see what happen...

Answered 11/25/2013 by: dlistar
Second Degree Blue Belt

Please log in to comment
0

Drivers is still not right yet. 

Answered 09/27/2012 by: Aaron Cool
Red Belt

  • Dear Aaron,

    I don't think so because I use Driver Harvesting Utility from K2000 to capture all driver on that test laptop to K2000 so why driver is not correct? please advise me thanks
Please log in to comment
Answer this question or Comment on this question for clarity