I have noticed that over the last month that our KBOX 2000 sys. has slowed down alot. Takes 5-10 minutes to PXE boot and then the images that are 8 gig images are taking over a hour to deploy. Is anyone else having this issue?

Thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
These items come to mind:
1) Your KBox is filling up with images
2) You swapped the network, or re-routed traffic the on the segment your KBOX is on.
3) You have thottled down your BU(bandwith utilization).
4) The computers you are imaging are slower.

Try using a network tool to sniff packets and see what is going on.

Let me know if this helps.
Answered 12/28/2009 by: amccoppin
Senior Yellow Belt

Please log in to comment
0
have you made driver changes recently?

Did you clear out the drivers when you updated to 3?
Answered 12/31/2009 by: dtuttle
Purple Belt

Please log in to comment
0
What version of the Kbox server (2100 or 2200) and server software (version 3.1.26500 ?) are you running? In a physical box or virtual? How many drivers are in your ALL and KPE directories? Have you created an ISO Boot Environment? Are you using WinPE or MiniNT for your Factory (Driver Detection) Mode?

- Eric
Answered 01/14/2010 by: ericwalrod
Senior Yellow Belt

Please log in to comment
1
It basically was a driver issue on my end. I updated the Boot environments and then cleaned out all of the drivers and then reloaded the newest driver package and it cut the time in half.

Thanks for the ideas.
Answered 02/23/2010 by: choctawnation
Senior Yellow Belt

Please log in to comment
0
How exactly did you update the boot environment and reloaded the newest drivers? We also have the issue of it taking 5-10 minutes.
Answered 07/22/2011 by: tjbel
Yellow Belt

Please log in to comment
1
tjbel, here's how you can do it:

Access the driver share of your K2000 through the UNC path \drivers">\\<k2000>\drivers, where <k2000> is either the IP address of the K2000 or the DNS name. Your user name will be <k2000>\admin, password by default is "admin", but can be changed from the General Settings section of the Control Panel.

Once there, you can go into the KBE folders (kbox_winpe3_xXX for 3.2, kbe_windows_xXX for 3.3), backup and remove (all?) drivers and copy the newest driver pack drivers into the appropriate architecture's folders. Do not place both x86 and x64 drivers into either of the KBE driver folders.

You can get the latest KBE driver pack here:
http://downloads.kace.com/support/downloads/drivers/3.2/KBE_driver_pack.zip

Once the drivers are copied over, you will need to first re-cache the drivers, and then build a new KBE boot environment using the Media Manager. This new KBE boot environment will include the drivers that were added above.

Here is how to create a KBE pre-boot environment:
http://www.kace.com/support/kb/index.php?action=artikel&cat=70&id=1058&artlang=en
Answered 07/23/2011 by: warmep
Second Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity