Windows 10 and OSD

[ADutch1]

Awesome! Looking forward to it!

[alexdinia]

Hello,
OS Deployment support (bare metal and re-imaging) for Windows 10 has just been released.
Please look for site version 55.
New MDTBundleCreator 3.8.12 needed. Bare Metal server level (7.1.1.19) unchanged with respect to August release.

Best regards

[ADutch1]

NIIIIIIICE! Thank you!

[vpopovi]

Hi Alessandro,

When trying to upload a Windows 10 ISO through Image Library dashboard an error message is displayed saying invalid version.

Has the support for Windows 10 been fully implemented?

Thanks,
Vlad

[vtripodi]

Hi Vlad

which flavor are you trying to import? Do you have other info/error in %USERPROFILE%\OSDeployment\rbagent.trc (in the machine where the console is running)?

Regards,
Viviana

[vpopovi]

Hi Viviana,

We are trying to import Windows 10 Pro 64-bit ISO image. The ISO was downloaded using Microsoft’s Windows 10 Media Creation Tool (MediaCreationToolx64.exe)

Here is the log from %USERPROFILE%\OSDeployment\rbagent.trc:

[2015/10/22 12:14:51] IBM Tivoli Provisioning Manager for Images Web extension 64 bits v.7.1.1.19 (270.40)
[2015/10/22 12:14:51] Licensed Materials - Property of IBM. - INTERNAL
[2015/10/22 12:14:51] (C) Copyright IBM Corporation 1998, 2015.
[2015/10/22 12:14:51] All Rights Reserved. IBM, the IBM logo, and Tivoli are trademarks of IBM Corporation in the United States, other countries or both.
[2015/10/22 12:14:51] Bootable: \\.\PHYSICALDRIVE0
[2015/10/22 12:14:51] Running in offline mode
[2015/10/22 12:14:51]  A <NOT> LoadPakUtils: loading from rbagent.pak
[2015/10/22 12:14:51]  A <NOT> LoadPakUtils: successfully loaded
[2015/10/22 12:14:52]  A <NOT> Loading server extensions if available
[2015/10/22 12:14:52]  A <NOT> Working in offline, extensions are disabled
[2015/10/22 12:14:52]  A <NOT> No ServerID has been defined
[2015/10/22 12:14:52] ISOFS:Unknown Volume identifier: -ESD_ISO                         -
[2015/10/22 12:14:52]  A <ERR> Invalid source provided.
[2015/10/22 12:14:52]  A <ERR> Source must be an installation media for:  -Windows Vista or later  -Windows Server 2008 or later  -RedHat Enterprise Linux 5 or later  -Suse Linux 11 or later  -VMware ESXi 5 or later 
[2015/10/22 12:14:52]  A <ERR> Cannot find anything of the following: \sources\install.wim; /isolinux; /suse 
[2015/10/22 12:14:52]  A <ERR> RbAgent command rad-temmksetup has failed [AGT:4394]

Thanks,
Vlad

[vtripodi]

Hi Vlad

the Windows 10 Pro x64 that can be downloaded from MSDN can be imported and deployed. The file is named en_windows_10_multiple_editions_x64_dvd_6846432.iso and contains both Pro and Home flavors.

I reproduced your error importing the iso created using the Microsoft media creation tool so I tried to mount the iso with the dism command and I got an error:
2015-10-23 10:59:30, Error DISM DISM WIM Provider: PID=3552 WIM open failed. - CWimImageInfoCollection::Initialize(hr:0x80070005)

The issue needs further investigation so I suggest to open a PMR.

[Knakerton]

Could someone help me out a little bit. I’m kinda new to IBM Endpoint Manager. My problem is that there is no win10 in “OS to capture”

I have updated the Bare Metal server level to 7.1.1.19 but I have difficulties in installing the WADK 10 in Bundle and Media Manger -> MDT Bundle Creators.

“Install MDT Bundle Creator” -button does not install the WADK10 even after I press “Upload MDT Bundle from target” and pressing “sync” says that the Bundle creator is up to date. Deployment Kit version is currently 8.1.

I feel like I’m missing something really obvious.

[vtripodi]

The “Install MDT Bundle Creator” will install all prerequisite software (so also WADK 10) and the MDT Bundle creator on the target you specify following the wizard.
Ensure that the taget has direct internet access and that another version of WADK is not already installed. Moreover, in the creator install wizard select the WADK 10 option (default is WADK 8).
Finally, check the results of the action to see if it completes.

The Sync button updates the MDT Bundle creator if a newer version is available. It does not update the prerequisite software and it does not create the MDT Bundle.

Note that the “Upload MDT Bundle from target” requires that the machine where the console is running can access the MDT Bundle folder. I mean that if the created MDT Bundle is remote the folder must be mounted in the console machine so that you can browse till that folder.

I hope this helps.

[Knakerton]

l

Thanks for the help!

I deleted the old WADK and I was able to update the machine to WADK 10 from Bundle and Media Manager. Now the Bundle and Media tells that the computer has Deployment kit WADK 10.0, MDT Bundle Creator 3.8.14.0 and MDT version is 2013. How should I proceed to get the win10 option in Capture Image?

[vtripodi]

In the MDT Bundle Creators view you should now have:
Target Status Deployment Kit MDT Bundle Creator Version MDT Version
hostname Available WADK 10.0 3.8.14 2013U1

Note that MDT is 2013 Update 1 build version 8298. This is the Microsoft official build.

If prerequisite software and the creator are at the right level, you can create the MDT Bundle. Select the creator machine and then the button “Create MDT Bundle” . Here you can specify the option “Create a new MDT Bundle only” if you already have the windows 10 OS Resources imported in the environment. If this is not the case leave the default selection “Create both MDT Bundle and OS Resources”. In the latter case you need to copy/mount the windows 10 iso file in the creator machine and to specify the path to file in the wizard.

When the action Generate Bundle is completed you can import the MDT Bundle. Remember to copy the bundle folder so that it is accessible from your console (locally in the machine where the console is running or in a mounted path).

[Knakerton]

I managed to install the Creator to the target machine and created the MDT bundle + OS resource as you suggested. Generate Bundle went through and I uploaded the MDT bundle from the target machine (I had previously placed the ISO to drive C: on the target machine). Now I have a new MDT bundle on the MDT resources tab.

Capture Image now shows Windows 10 as a selection. You are a life saver! Thank you!

[vpopovi]

Hi Viviana,

Thank you for the reply. I was able to import the Windows 10 Pro x64 ISO downloaded directly from the Microsoft product web site.

We would like to perform an in-place upgrade of our Windows 7 systems to Windows 10. Unfortunately, it appears that the in-place upgrade is not supported by BigFix OSD. MDT 2013 U1 supports an in-place upgrade to Windows 10 as explained in the following article from Technet.

Are there any plans to include this feature in BigFix OSD?

Thanks,
Vlad

[vtripodi]

Hi Vlad

the in-place upgrade is not currently supported by BigFix OSD.
As your point is very interesting I suggest to open a RFE so we can evaluate and eventually include this feature soon. Thank you.

Regards,
Viviana

[vpopovi]

Hi Viviana,

We have created an RFE for the in-place upgrade to Windows 10. Below is the link to it:

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=80513

I would encourage everyone to vote for those who are interested in this feature. As you know, Microsoft is offering a free upgrade for Windows 7 and 8 users (OEM). This offer expires in July 2016.

Thanks,
Vlad

[Entaille]

It is a bit concerning to me that there’s only a handful of ‘votes’ for this feature. It seems pretty important but has low visibility, is this how your team prioritizes development work (based on the votes?)

It seems a bit crazy to me that any available feature in the base MDT isn’t supported in BigFix, since BigFix is just layering on top of it.

We too have a large number of machines that we’d like to do an in place upgrade on to migrate to Windows 10. Do we have any idea of how long it’d be before this is supported?

[asecoman]

Hi Enaille,
This forum is indeed a valuable source of input to prioritizes our development work, but it is not the only one. The requirement to support the in place upgrade of Windows 10 was received also via other channels.

The requirement was accepted and will be delivered in the next release that is currently under development. It should become available in 1Q 2016.

Hope this helps.
Best Regards
Antonio

[Entaille]

excellent news, thanks for the update.

[jgstew]

concerning to me that there’s only a handful of ‘votes’ for this feature

The RFE system isn’t well used. It is meant more for long term planning of new features, those in the 1 to 3 year time frame.

This forum is the best way to get traction on things that are more short term that should be addressed like this, but it is still a good idea to file an RFE anyway because it it something that can be referred to by project managers.

See this post for related reading: How to ask for IBM product help: PMRs, RFEs, and more

[paolofalsi]

Windows 10 in-place upgrade feature is available in BigFix OS Deplyment 3.9 Beta code - You (Customers or IBMers) can contribute the IBM BigFix OS Deployment 3.9 Beta Program accessing Beta Wiki Page:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W41cefdb169f4_4fdd_b71e_793844420ddb/page/IBM%20BigFix%20OS%20Deployment%20v3.9%20%20-%20Beta%20Program%20wiki%20page