Import w10 image from installation folder

Hello,

I tried to import a w10 from installation folder.
My machine is a w7 x64 system and I have all the Tools (wadk 10…) installed.
I did the install.esd modification in install.wim.
But each time the Bigfix console said : run the console in acomputer with wadk 10 or in a w10 machine…
I tried with a fresh install of w10 + Bigfix console in and I have the same message.
Thanks for your help

Hello, what you mean saying that you did the install.esd modification in install.wim?
Are you trying to import an .iso from a folder? Is the install.wim contained in the
.iso in .esd format? how did you verify the compression format? Is it named .esd?
Could you eventually provide us the .iso so we can try here?.

Hello,

Yes I’m triyng to import an .iso from a folder.
Yes, the install is an esd format. So, I follow your documentation
http://www.ibm.com/support/knowledgecenter/SS63NW_9.2.0/com.ibm.tem.life.doc_9.2/Lifecycle_Man/OSD_Users_Guide/c_problem_import_win10_esd.html

But I always have the same message.

I will try to send you the ISO.

Thks for your help,

MG

Hello, I sent you a private message :wink:

After a lot of tests, I’m wondering if W10 release 16.07 is not the problem.
If you see the Microsoft documentation, it seems that it is necessary to have the latest WAIK10
and the MDT 2013 update 2 to operate.
These MDT and WAIK versions are not detected by Bigfix in my machines.

with the WAIK 10 and MDT 2013 from Bigfix and a recent ISO from Microsoft, the system could never open a .esd format (even if the original esd is converted and verified).

Please help !

Hello, I was not able to ftp for getting the iso you are using. If it is possible
please open a pmr and put it on ecurep

we have to investigate because with the last level of code available you should not need
any manual steps in case the install.wim is in .esd format.
Which level of fixpack is your bare metal running? 16.07 should be the anniversary build
that we have imported here without any need of manual steps.

when open the pmr togheter with the .iso you are using put on ecurep also
the rbagent.trc traces that you can find under %userprofile%OSdeployment

I have already opened a PMR. 16752,923,848.

I have different Bare Metal Servers. (see picture).

I will upload the iso and the rbagent.trc.

Hello, we have tried here to import the .iso attached in pmr
provided and we have same message you are having about
the prerequisite to install the console on a windows10 machine or
install WADK10. The reason is that since the install image inside
the .iso is in .esd (compressed format), in order IEM to be able
to convert the .esd format, it needs some utilities that are
coming with WADK10. So, in order to import that .iso, without
doing any manual steps, you needs to install WADK10 or
run the bigfix console on a windows 10 machine.
In order the code is able to manage .esd format, it is required
the fixpack20 7.1.1.20 (290.13) since the changes in code for
managing .esd format are contained in rbagent version 7.1.1.20
(290.13)

we have reproduced this behavior with the .iso you have provided where
we have console installed on windows 7 64 bit with wadk10.
We will keep you informed on progress on the investigation through the pmr, and we will
inform if there is a way to go around the problem

Very good.
I’m waiting for good news ! :slight_smile:

Hello,
For everybody, The staff (many thanks)found the problem and give me a workaround.

Hello, thanks for providing information about version of WADK10         
installed.                                                              
We have found that there is a problem in the code for which the  version of WADK10 you have is not correctly detected even if it is installed on 
the machine.                                                            
We are going  to open a defect to  have this fixed                      
The feature we are interested in for leveraging dism command and        
convert the install.esd is "Windows Deployment Tools".                  
In the meantime please run the following workaround                     
                                                                        
1) deinstall WADK10 from the machine where console is running.          
2)deinstall any possible "windows deployment Tools" that could be on    
your  machine (for example if you have a previous version 8)            
3) Install WADK10 GA feature "Windows Deployment Tools"                 
4) After the installation is completed verify that on you machine (where
bigfix console is installed) you have the following entry in your       
registry                                                                
if the machine is a 64 bit machine                                      
SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall    
\\{56B71DBF-E9C9-B173-3298-78D76AA6A70B}                                
or                                                                      
SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\{56B71DBF-E9C9-
B173-3298-78D76AA6A70B}                                                 
if the machine is a 32 bit machine                                      
 Clicking on the 56B71DBF-E9C9-B173-3298-78D76AA6A70B key, you should   
 have "Windows Deployment Tools",                                       
 Display Version 10.0.26264.                                            
 5) Once you have verified that you have the                            
 56B71DBF-E9C9-B173-3298-78D76AA6A70B entry in the                      
 registries at that path, you can reimport the .iso.                    
 We have tried the steps for workaround and even if the converting      
 for .esd takes lot of  time to complete, it is successfully at the end.
 Let us know if workaround works in your environment    as well         
                                                                        
I'll inform you about the defect (APAR)                                 
number and the date the official fix if going to be released