You are not logged in.

Announcement

[2017.09.08] DeployStudio build v1.7.8 (checksum, release note).
[2016.08.26] DeployStudio build v1.6.19 (release note).
[2013.02.23] DeployStudio last universal build v1.5.17 (release note).

#1 2017-07-28 16:11:04

js2010
Member
Registered: 2014-06-06

using sysprepped 2016 windows bootcamp image on 2017 imac - bsod

Is there something about the 2017 imacs (iMac18,1) that's not compatible with a sysprepped imac 2016 image?  I noticed there's an "NVMe SSD"  in the device manager now.  Or is the partitioning somehow different?

Last edited by js2010 (2017-07-30 18:46:51)

Offline

#2 2017-07-29 00:32:19

js2010
Member
Registered: 2014-06-06

Re: using sysprepped 2016 windows bootcamp image on 2017 imac - bsod

Sending a .ntfs.gz image from a 2016 imac to a 2017 imac results in a "RAW" fs volume in diskpart, as opposed to an "NTFS" fs.

Last edited by js2010 (2017-07-29 00:33:02)

Offline

#3 2017-07-29 23:44:21

js2010
Member
Registered: 2014-06-06

Re: using sysprepped 2016 windows bootcamp image on 2017 imac - bsod

Could it be a physical block size change?  https://twocanoes.com/usb-c-macbook-macbook-pro-physical-block-size  Going from one 2017 imac to another works.

Last edited by js2010 (2017-07-31 16:37:54)

Offline

#4 2017-08-25 15:07:40

js2010
Member
Registered: 2014-06-06

Re: using sysprepped 2016 windows bootcamp image on 2017 imac - bsod

Now my old image works on an imac18,3, but the new image from an imac18,1 won't.  So weird.

Offline

#5 2017-09-26 21:15:49

chndrcks
Member
Registered: 2012-12-31

Re: using sysprepped 2016 windows bootcamp image on 2017 imac - bsod

Have you found a solution for this? I believe I'm having a similar problem. I tried restoring our image from the previous model on to an 18,2 model and I'm getting the same result you did. I can fix that individual machine by booting into winpe and running a few bcd commands manually, but even when I save that fixed image, I'm unable to restore to a different 18,2 machine.

Offline

#6 2017-09-26 21:38:06

js2010
Member
Registered: 2014-06-06

Re: using sysprepped 2016 windows bootcamp image on 2017 imac - bsod

I just use 2 images depending on the Device Block Size ("diskutil info /" to get it), 512 bytes or 4906 bytes.  Some new macs have the old block size. 

How do you fix it with bcd?

Offline

#7 2017-10-02 21:25:39

chndrcks
Member
Registered: 2012-12-31

Re: using sysprepped 2016 windows bootcamp image on 2017 imac - bsod

I'm doing something a little bit unusual, but it works on all except for the machines with 4k block size.

Our PCs are using SCCM for their imaging and for a variety of reasons, we wanted to continue imaging with DeployStudio while leveraging our SCCM Task Sequences. So I came up with a way to do that - basically I create a prestaged device and capture/deploy that with deploystudio. So after the Restore Windows workflow is applied, the machine boots into winpe and runs the task sequence. On the machines with 4k sectors, that winpe environment fails to boot. I can fix it by booting off a usb drive into a winpe environment and running the following commands:

(I assign the EFI partition the letter s:)
bcdboot.exe c:\windows /s S: /f UEFI
del s:\efi\microsoft\Boot\BCD /f /q
copy c:\EFI\Microsoft\Boot\BCD S:\efi\Microsoft\Boot /y
BCDEdit.exe /Store S:\EFI\Microsoft\Boot\BCD /Set {ramdiskoptions} ramdisksdidevice partition=c:
BCDEdit.exe /Store S:\EFI\Microsoft\Boot\BCD /Set {Default} device ramdisk=[C:]\sources\boot.wim,{ramdiskoptions}
BCDEdit.exe /Store S:\EFI\Microsoft\Boot\BCD /Set {Default} osdevice ramdisk=[C:]\sources\boot.wim,{ramdiskoptions}
BCDEdit.exe /Store S:\EFI\Microsoft\Boot\BCD -set {bootmgr} device partition=S:

Offline

Board footer

Powered by FluxBB