After booting into K2000 Boot Environment, Cursor is constantly jumping around

I am fairly new to managing our K2000 and I am running into an issue. For all of my HP desktops, I am able to sysprep and capture images without an issue. Recently I have started to add Panasonic Toughbook images onto our K2000. With some of the newer CF31 models, after I PXE boot and choose the Kace Boot Environment, the cursor on my screen constantly jumps around. I cannot get it to stop and cannot continue through with the imaging process. I have tired disabling the touchpad and only using a USB mouse, but I have the same issue. I tried creating a new KBE, but it is less reliable from the previously built one from last year. Does anyone have suggestions to fix this? I cannot capture these Toughbooks with the cursor constantly moving.

5 Comments   [ + ] Show comments
  • Have you included the drivers for the Toughbook in the KBE? - chucksteel 4 years ago
    • No I have not. The Admin guide only says to get the KBE drivers from their support site, and that is all I have been using. Just like the other response, if I download these drivers, where in the samba share do I save them? - dfsalazar04 4 years ago
  • I work with Toughbooks a lot. How are you building your KBE's?

    When I create my KBE's:
    I use this Driver pack:ftp://ftp.panasonic.com/computer/software/pe5x64_driverpack.zip

    Even though it is a driver pack for Windows 8, I use this in conjunction with a Windows 10 based KBE. - Desktop Jockey 4 years ago
    • Man. This helps me a ton. Quest support told me I only need the KBE drivers from their support drive in our Samba share. This makes sense that I would need these included. Where do you save these specifically? \\(K2000IP)\Drivers\windows_7_x64? Also, should I be getting these drivers from each PC manufacture I use? All of the folders in the Drivers folder are empty except for the "kbe_windows_x64" and "kbe_windows_x86", which I got directly from the Quest support site. - dfsalazar04 4 years ago
  • You will need to unzip the drivers to "\\K2000\drivers\kbe_windows_x64". If there are any other files or folders in that directory, remove them (Or zip them up).

    Then Recache the KBE Drivers and try to remake the kbe

    I do not know if HP makes a Windows PE driver Pack. If they do, then you can do the same thing for HP machines. - Desktop Jockey 4 years ago
    • What about the KBE drivers from Quest Support? Remove those as well? I just don't want to break the HP machines that I have working now.

      Also, how can I bake these into a Win 7 ISO? I have this same cursor problem when I try to load Win 7 Pro SP1 on a newly formated Toughbook HDD. - dfsalazar04 4 years ago
    • EDIT: Or are you trying to say I should have a KBE for each type of Manufacture I image with KACE (One for HP, one for Panasonic, one for Lenovo, etc.)? - dfsalazar04 4 years ago
      • Well you can try to combine the drivers but you may end up with a conflict. To get the Panasonics working, I would first create a KBE specifically for those.

        You can compress the current contents of the kbe_windpws_x64 folder and leave the zip in there. (So you dont lose your previous config) - Desktop Jockey 4 years ago
  • Does the computer have onboard GPS, if so the mouse and the GPS receiver can be confused. - jayrobinson 4 years ago
  • The drivers from the WINPE10 driver pack works for me on 99% of computers, there are two or three DELL and Lenovo Models, where we had to build "Tailored" KBEs for those machines ONLY. What I do is I add the machine brand and model on the KBE name itself.... - Channeler 4 years ago

Answers (0)

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ