Mar 4, 2011 at 11:40 AM
Edited Mar 4, 2011 at 12:49 PM
I'm slightly [or perhaps that should be 'very') confused. Tried to write this out fully so apolgises for the long post but hope you good good people can find time to read through it :)
Been looking at the custom boot wizard and have started making something up with it and the results are 50/50 good and bad really.
Just to explain the situation, we are already using SCCM OS deployment and using this WebService for a few things such as using it to add a computer to a specific collection etc.
Because I cant really stop what's currently setup (as a bunch of staff will not be able to do deploy new Win7 machines) I'm trying to make this Custom Boot Wizard in a testing Collection environment to keep things neatly out of the way.
The boot image seems to work fine, and I was going to move the MDT Wizard off of the boot disk to help speed up testing, but the files attached on article mentioned in the above one, are no longer downloadable unfortunately, so I've had to stick with the
imagex mounting and unmounting technique to update the scripts as I tweak them, then updating the boot image so the changes are distributed to the DP's :)
I'm just using the default files in the Custom Boot Wizard download - obviously tweaked where it say to - and I've also had a little look at the CustomBootWizard files too using the handy MDT Wizard Editor - changed a bit of text thats displayed, but nothing
that would break anything :)
I'm currently a bit stuck/confused with two issues.....
Because we have the OS deployment setup and working using the normal WinPE / SCCM boot image, i've made this custom boot wizard boot image, and have advertised it with PXE enabled to a new test collection, then added a test computer resource to this collection
(one already known to SCCM) and used "Hidden" in the Description on other collections that have PXE / OSD TS's on them so that dont appear. I've left out Hidden from one collection that has a Task Sequence attached to it (the one currently being used by the
techies to deploy Win7 at the moment) in order for it to display in the custom boot wizard.
The test machine boots using this custom boot image, and I eventually get the HTA GUI appear - looking correct with my little tweaks :) - but unfortunately now showing any Collections / Task Sequences listed i.e. i get "No Operating Systems are available
for this site. Please contact your local IS Support." displayed.
The confusion here I've run into is that the OS deployment Task Sequences themselves shouldnt have a boot image attached to them (in this setup) otherwise the machine just boots into that boot image rather than our specificly advertised custom boot
image, but both the OSD TS and the Custom Boot Image TS advertisements need to be "available to PXE".... correct? Or am I muddled?
(remember, i cant stick it on Unknown Computers / All Systems until i've finished it etc, as cant interrupt the existing TS's and setups)
Edit: forgot to add that even though the resource computer is attached to both the Custom Boot Wizard and the Win7 Test Collection's, and neither have Hidden in the description of the Collection, neither are listed when booting into that machine via the
custom boot image :S
Also, while I can use the WebService directly aka pointing to it in a browser, I dont get anything when I try and GetOSDCollections test invoke.... I just get:
<?xml version="1.0" encoding="utf-8" ?>
<ArrayOfCollection xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://maikkoster.com/Deployment" />
in the resulting page, and thats it. Which is a bit odd considering I'm running that as me, and I've got full access across SCCM (being i set it up etc).
er.... I'll come back to it... I've got a bit of a mental block now and I need to pop out :)