Windows 10 and OSD

ADutch1 · August 7, 2015, 7:51pm

Trying to capture a Windows 10 PC to create an image but it’s not an option in “OS to capture”. Any update on when OSD is supporting Windows 10?

hmmarkka · August 10, 2015, 12:50pm

This information would be really nice to know. Any planned dates for Windows 10 supported BigFix release?

ADutch1 · August 10, 2015, 3:13pm

Looks like they uploaded a new OSD version today… 7.1.1.19 (08/10/15)

I will install that one and see if it supports Windows 10.

alexdinia · August 11, 2015, 7:13am

Hi all,
Bare metal server 7.1.1.19, together with the new OSD (3.8) site that will be published later today, still do not support Windows 10.
This is due to Microsoft not yet having released MDT 2013 U1, that allows deployment of Windows 10.

OSD team has performed all the necessary activity to be able to support Windows 10. As soon as Microsoft releases MDT, we will run the needed regression tests and publish a site refresh to add this support.

ADutch1 · August 18, 2015, 12:44pm

Looks like MDT 2013 UPD 1 just was released 08/17!

alexdinia · August 19, 2015, 8:55am

Thank you! We started working on it. I will update when we are able to release an OSD site refersh to support Win10.

Best regards
Alessandro

StefanoBelluomini · August 20, 2015, 12:09am

Thanks for the update, Alessandro.

ADutch1 · September 2, 2015, 1:35pm

Any update on a release date? Thanks!

alexdinia · September 2, 2015, 8:26pm

We will be releasing a site refresh (with new MDT bundle) no later than September 15th.
Best regards

ADutch1 · September 2, 2015, 8:43pm

Awesome! Looking forward to it!

alexdinia · September 10, 2015, 3:25pm

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 · September 10, 2015, 3:26pm

NIIIIIIICE! Thank you!

vpopovi · October 22, 2015, 4:14am

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 · October 22, 2015, 6:16am

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 · October 22, 2015, 4:15pm

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 · October 23, 2015, 9:27am

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 · November 2, 2015, 9:48am

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 · November 2, 2015, 10:14am

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 · November 3, 2015, 6:35am

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 · November 3, 2015, 11:17am

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).