Hi, 

I've made a Server 2012 image with 12 months worth of MS MSU files and uploaded it to the K2200 and created a deployment with the image.

As soon  as the network install gets past preinstallation tasks and cleans the C drive and creates a boot partition,  it reboots the machine and complains about no MBR record being found.

I set up a USB drive with boot partition and copied over my modified image, which is now just over 5GB in size.  Server 2012 installed with no problems, so I have to assume that the K2200 is having a problem with the image.

Anyone know a trick to get this to work?  

Or am I hooped trying to use a DISM image?

Nothing in the log files lept out at me.

 

Thanks.

Answer Summary:
Cancel
4 Comments   [ + ] Show Comments

Comments

  • No, the diskpart script is the same one I've been using all along, and is the one that the K2200 came with when we purchased it; I know it's misleading with the missing boot mgr message, but I'm guessing that's what's happening after preinstall and when the 2200 starts deploying the 2012 image; maybe the boot sector is getting overwritten for some reason. I get nothing just a black screen and reboot after preinstall tasks complete.

    I just used it today with a standard 2012 ISO. It's definitely successfully cleaning and putting the bootsect.exe on the drive.

    Here's the commands I used to make the DISM image; I'm just wondering if there's a DISM command I can use to make the image work with the k2200 for a network install. In one example of language pack update, the guy had a /bootable switch, maybe something like that?

    Here's my powershell script I made. It's barebones to get the packages slipstreamed into the image.
    -------------------------------------------------------------------------------------------------------------------
    set-executionpolicy unrestricted

    dism /cleanup-wim #cleans up any old dism mounts

    dism /mount-wim /wimfile:c:\ISO\sources\install.wim /index:2 /mountdir:c:\mount #mount image onto folder

    $i = 1

    $folders = (Get-ChildItem C:\Updates).count #get folder count from updates

    while ($i -le $folders){dism /image:c:\mount /add-package:c:\updates\$i;$i++} #recursively step through each folder in "updates" and add packages

    dism /unmount-wim /mountdir:c:\mount /commit #commit changes and unmount

    cd "c:\program files (x86)"

    .\oscdimg -bC:\ISO\boot\etfsboot.com -h -u2 -m -lwin8 C:\ISO\ C:\win8.iso

    ---------------------------------------------------------------------------------------------------------------------
    because you asked, here's the preinstall tasks:

    select disk 0
    clean
    create partition primary
    select partition 1
    active
    assign
    exit

    format /q /y /fs:ntfs c:

    bootsect.exe /NT60 c:

    Thanks for your time.
  • Will it deploy if you don't slipstream any packages?
  • one thing I notice you are calling the script and mounts from the c drive, but you format that in your preinstall tasks which will wipe all files from it. if your iso is on a boot stick what drive letter does that become?
    • Ah good call, the folder you mount a wim to with DISM has to already exist, it won't create the folder automatically. If you're formatting the C drive and then trying to mount to C:\Mount, that won't work.
  • Yes, nhenye, it does deploy without slipstreamed packages perfectly from a USB. So the USB is usually like letter J on my computer. I don't see why C drive would be a problem, but I could force Kace to assign a different letter in preinstall and see what happens just for kicks.

    In terms of the mount point, I'm doing that on my desktop. Good call though I will add a md statement to create the proper folders for anyone using it. I've already got those folders so I was just reusing them.

    Sorry, english is my first language but I'm not always the best at communicating through the written word.

    So I'm making the image on my desktop with that powershell script and c:\mount c:\updates and c:ISO already exist. I unpack the Stock ISO into ISO, mount the install.wim /index2 (Server 2012 Standard GUI) to c:\mount. After unmounting and turning back into an ISO (it's now 5GB and the original was under 4) Uploading the finished ISO to the K2200 and using it in a new deployment.

    Sorry if I'm missing the obvious. I'm going to look at all the different DISM commands and see if I'm missing anything. There isn't a whole lot of documentation and just examples without any commentary and why you do things. And I've yet to find a guide where the modified image is used in a network install.

    Again thanks for the feedback, I'll keep trying. If I figure it out on my own I'll post the answer.
    • I would be curious what you find to be the issue. Is there any reason you wouldn't be capturing a WIM image of your deployment rather than creating a scripted install?
Please log in to comment

Answers

0

Sounds like your diskpart script may be the issue, can you post it?  Does the USB image have the same script?

Answered 11/05/2013 by: nheyne
Red Belt

Please log in to comment
0

hmm, well as luck would have it the latest Kace update just added a 2nd option for uploading images.

 

You can select a windows image instead of k-image.  The Windows Image is file based instead of sector based.  It's actually a very nice improvement, the image is half the size of the k images I made and very fast to deploy (under 30 minutes).  Because it's file based it's platform agnostic so I've imaged a few machines today with all the windows updates built in.  

 

I guess my question has been answered in a roundabout way as I won't need to make my own DISM image and upload it.  

 

Cheers

Answered 11/07/2013 by: trevzilla
Senior Yellow Belt

  • wims are the way to go
    http://www.itninja.com/blog/view/wim-storage-freeing-up-space-on-your-k2000-if-you-are-using-wim-s
    http://www.itninja.com/blog/view/do-you-want-to-store-your-wim-s-externally-with-k2000-v3-5-like-we-did-with-3-4
Please log in to comment
Answer this question or Comment on this question for clarity