/build/static/layout/Breadcrumb_cap_w.png

Dell KBE Manipulator Architecture bug

All,

I'm trying to upload a new KBE boot image where I customized the inputlocate with DSM.
The KBE Manipulator gives me the option to Select KBE Architecture.

Since I want to deploy an X64 OS, I select x64 as architecture.
The proposed name is also changed to x64 so this seems to work perfectly.
However when I check Show Summary, the KBE Architecture is still x86.
After uploading the KBE to Dell KACE, it's also marked in the webpage that's a x86 image..

Is this a bug in the latest version (3.7.1.0) of the KBE Manipulator?
If yes, can this please be fixed and where can I download a previous version of the KBE Manipulator to upload my custom boot.wim asap?

Thanks in advance!

Regards,

Sven


2 Comments   [ + ] Show comments
  • I'm running into the same problem. The system that I'm running KBEM on is Windows 7 x64. - pklimmek 8 years ago
  • Hi, I'm having the same behavior, Win 7 Pro x64. I installed WAIK and WADK for 8.1. When I start KBEM (v 3.7.1.0), I can choose which toolkit to use. But when I select KBE x64 it's stays on x86.

    Regards,
    Dimitri - bruyld01 8 years ago

Answers (6)

Posted by: cserrins 8 years ago
Red Belt
2
There was a defect with the Summary Screen in 3.7.1.0 reporting the wrong architecture when x64 was chosen.  Please run kbem again and download/install the update to 3.7.1.1 which resolves this issue.

Apologies
-Corey
Posted by: Silencer001 8 years ago
Orange Senior Belt
1


Alright, thanks SMal.tmcc! Attached you can find the screenshot of the Dell KACE console.
I just uploaded the first entry "TEST FOR ITNINJA" today with the old KBE Manipulator ==>  NOK
The last entry was the one which caused me to create this threat ==> NOK
The middle entry was uploaded by the new version which fixed the bug ==> OK

All of these images were uploaded with the same settings in the KBE Manipulator => Architecture: x64

Thanks again guys!!

Comments:
Posted by: SMal.tmcc 8 years ago
Red Belt
0
I helped test the KBEM v 3.7.1 and did not run across that bug.  what OS and byte is your tech station?  which tool kit are you using? 

Comments:
  • Hi SMal.tmcc, thanks for your comment. I'm running Windows 8.1 Enterprise x64 and I've installed MDT 2013 on this workstation. - Silencer001 8 years ago
  • Hi SMal.tmcc. Did you have time to test this on a windows 8.1 x64 system? User "pklimmek" is experiencing the same issue on a windows 7 x64 system. Thanks in advance! - Silencer001 8 years ago
    • been buried with imaging will have time to test on a x64 win 7 machine today. I do not currently have a win 8.1 test machine available. I pinged the author of the KBEM also about this problem. - SMal.tmcc 8 years ago
      • No worries, SMal.tmcc. Would be awesome if you could get back to me what you concluded after testing this yourself. Also thanks for pinging the author so this issue could get resolved asap. Thx!! - Silencer001 8 years ago
Posted by: SMal.tmcc 8 years ago
Red Belt
0
Did some research and it comes down to you are using the MDT2103 and the kbem does not recognize that program as a valid file source.  You need to install WADK for 8.1

see the requirements

http://www.itninja.com/question/kbe-manipulator

https://www.microsoft.com/en-us/download/details.aspx?id=39982

Comments:
  • Thanks for checking this out SMal.tmcc. I thought the ADK 8.1 was part of the MDT 2013?! I just tried to download the WADK for 8.1 and instead of "install", I can "add/change" current features and "Windows Preinstallation Environment (Windows PE)" is already installed.. So I guess I should be alright? Thx for the quick reply and suggestion! - Silencer001 8 years ago
    • it still may not work the WADK installs in a different subdirectory and the KBEM looks at certain directories to determine what tools are installed on your workstation. C:\Program Files\Microsoft Deployment Toolkit vs C:\Program Files (x86)\Windows Kits\8.1\ - SMal.tmcc 8 years ago
      • OK, I can follow this.. I tested this on a clean VM (Windows 8.1), installed the ADK (no MDT installation) and the paths you refer to are indeed different. But the KBE is still showing up as x86.. :-( Any other ideas? - Silencer001 8 years ago
Posted by: bruyld01 8 years ago
White Belt
0
Hi guys, 

I'm having the same behavior on a Win 7 Pro x64. I installed WAIK and even WADK for 8.1. When I start KBEM I can choose which toolkit to use but when I select x64 KBE architecture and check the readme file or upload it, it's x86. 
Somebody knows the fix?



Regards, 
Dimitri


Posted by: SMal.tmcc 8 years ago
Red Belt
0
On a fresh image I installed WADK, K2000 Kedia Manager, then KBEM 3.7.1.0

I found the KBEM installed at c:\program files\dell\kace\kbe manipulator\   and calling the x64 version
s63L7F.jpeg

started and choose x64
xvqD2A.jpeg

checked summary and it shows x86 (have reported this)
koKUyj.jpeg

let it upload (shows as x64 in the k2000)
ozH6ej.jpeg

booted a test station
f6R2hn.jpeg

and it gives me x64 images in my deployment.
4dVFgc.jpeg





Comments:
  • Hi all, I would like to thank everyone for their quick intervention!! I can confirm that this bug is fixed in the latest build!! Tests were done on a Windows 8.1 x64 computer with MDT 2013 installed.

    @SMal.tmcc: I've done the tests again with the old build and the KACE Console was still reporting KBE x86 as Operating System. I loaded this boot image in a VM and x64 images were visible.. Pretty weird.. I've made a screenshot, but can't seem to find a way to upload to the forums? Anyways, no need anymore since it's fixed..

    @Corey: Thanks for the bugfix!! - Silencer001 8 years ago
    • you can only upload images in the post or in the "answer this question" you cannot post pics under replies - SMal.tmcc 8 years ago

Don't be a Stranger!

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

Sign up! or login

Share

 
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