I followed the guided tour when setting up our K2000, but when it gets to the part of installing the WAIK, I noticed it's the Windows 7 version. We're SLOWLY still migrating to Windows 7 but need to continue Windows XP unstalls. I seem to keep getting an error on an XP install (something about a Property.dll) and I'm thinking it may be because of the Win7 WAIK. Soooo, I tried downloading and using the KBOX Media Manager to upload the Windows XP WAIK, but I get an error while uploading that says: "Boot environment build exited with non-zero exit code: 1" It seems like this is a general error stating "it didn't work".

Any way I can install XP with XP Media? Or are we the last people still installing XP?
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
Dan,

You need to build the boot environment on a Windows 7 box, with the Windows 7 WAIK link provided in the documentation. Once you do this, the boot environment will boot up any machine and can still capture and deploy Windows XP.

Hope this helps,

Corey
Answered 02/24/2011 by: cserrins
Red Belt

Please log in to comment
0
I get the same error and don't know what to do to make this work.

Jane
Answered 11/28/2011 by: jfrasier
Seventh Degree Black Belt

Please log in to comment
0
So I am confused about whether I can build a Boot Environment for Windows XP.

In the Manual

[center]You build new KBEs on a Windows computer that has both the Windows AIK and Media Manager.
Note: On Windows XP, .Net is required to build the KBE.[/center]In a post by tstaub:

[center]Creating the KACE Boot Environment (KBE - WinPE3) is not supported on WinXP.

KBE is created by the Windows Automated Installation KIT (AIK) for Windows 7
Here are the Supported OS for AIK: (referenced: http://go.microsoft.com/fwlink/?LinkId=136976 ) [/center]
Answered 11/28/2011 by: jfrasier
Seventh Degree Black Belt

Please log in to comment
0
I used Live Chat and found out that it didn't work using IP for the host, but it did work using the name. Figure that one out.
Answered 11/28/2011 by: jfrasier
Seventh Degree Black Belt

  • I'm having the same problem after recently upgrading to 3.6.98680 in early May. I've also tried to create the 64-bit KBE using the actual host name and not the IP address but I still get "Boot environment build exited with non-zero exit code:1" What in the world is going on here?
Please log in to comment
0
jfraiser,

Media Manager requires XP or higher and .net, because you can use that to upload Source Media. However, to upload a Boot Environment, you should stay with Windows 7 and WAIK for 7. You should be able to use IP or host name in Media Manager.

Corey
Answered 11/28/2011 by: cserrins
Red Belt

Please log in to comment
0
Here I am again. I upgraded my Kace 2000 to 3.4. I decided to make a new KBE but I am getting that same error as before.

Boot environment build exited with non-zero exit code: 1

I used the KBE_x86_34 for a deployment and it seemed to work fine, so maybe I don't really need to make a new one?

Thanks.
Answered 03/02/2012 by: jfrasier
Seventh Degree Black Belt

Please log in to comment
0
Something in your driver share is causing a conflict. Clean out any duplicate or new drivers, recache and rebuild.
Answered 03/02/2012 by: mpace
Red Belt

Please log in to comment
0
non-zero exit code is usually associated from using the wrong version of WAIK, make sure you are using WAIK for Windows 7. You can check by opening Start | All Program | Microsoft Windows AIK | Documentation | PE User's Guide.
The title bar should state for Windows 7, the Vista one doesn't state this in the title bar, but does show Vista on the page that comes up.

You can download WAIK for Windows 7 here: http://go.microsoft.com/fwlink/?LinkId=136976

But if the KBE_34 works for you, you are good to go.
Answered 03/03/2012 by: cserrins
Red Belt

Please log in to comment
0

I also got error "Boot environment build exited with non-zero exit code: 1" after upgrading to version 3.4

Reason is that they password protect the preinst share.

The solution is to download the new media manager from libary source media.
You will see that there is an option in the new media manager to fill in a password. This is the password you fill in Settings and maintenance, control panel, Driver/restore share password.

Please rate if this is also your solution.

Answered 10/08/2012 by: wollie
Orange Belt

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

Share