Boot Environment for Windows XP
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?
Any way I can install XP with XP Media? Or are we the last people still installing XP?
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
cserrins
13 years ago
Posted by:
jfrasier
12 years ago
Posted by:
jfrasier
12 years ago
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]
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]
Posted by:
jfrasier
12 years ago
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.
Comments:
-
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? - Mattman66 10 years ago
Posted by:
cserrins
12 years ago
Posted by:
jfrasier
12 years ago
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.
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.
Posted by:
mpace
12 years ago
Posted by:
cserrins
12 years ago
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.
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.
Posted by:
wollie
12 years ago
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.