I've read about, and I currently use multiple OSD task sequences including a generic capture sequence to capture any pre imaged/ configured windows operating system.
I have 7 OSD advertisments using the standard x86 boot wim.
I have 1 advertisment that utilizes a custom boot wim. Its named accordingly to custom_x86. It has a few custom steps to map a drive, prompt for the image creation name during PE and then capture the local C: drive to a share on my SCCM server. It works perfectly.
(We are essentially, for the short term (long long story) using this method to capture and image our clients. Yes it's like ghost and I realize that, but it's what I have to work with and it's quite functional. We are a mixed environment with 90% Novell systems that have no MS client installed. We are migrating this summer to an all MS/ AD environment. So, this is a short term solution as we have so many images. We are shutting off Zen imaging in about 2 weeks and this will be our solution until June. We are a large school district with so many apps it's sickening. Once we get migrated to AD, we will utilize SCCM fully for all our clients. Lets put it this way... after June 1, I'm looking at imaging roughly 8,000 PC's/ Laptops with SCCM on a new Win 7 image. Then utilizing a new WSUS instance and managing packaging apps etc.
My question is this...
What/ where determines the boot wim file the PXE process will utilitze? The last advertised TS?
Is there something more I can do to have my "capture TS" advertised also while pushing the 7 other TS advertisments utilizing the standard x86 boot wim? I gather it might just be one custom, scripted boot wim for all instances? Any instight is very appreciated. Still an SCCM newb here...
When I boot and get the capture advertisment, I still get my entire list of TS's, but if I choose to image a machine, it runs to a screen telling me to use my capture media and reboot. Essentially failing.
When I boot and get the sstandard x86 advertisment, I get my list of TS's and can push an image down successfully.
I need a way to use one boot wim and either push or pull an image.
Thanks for this site and sharing your knowledge. I reference it constantly and can't say enough good things!
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
I've read about, and I currently use multiple OSD task sequences including a generic capture sequence to capture any pre imaged/ configured windows operating system.
I have 7 OSD advertisments using the standard x86 boot wim.
I have 1 advertisment that utilizes a custom boot wim. Its named accordingly to custom_x86. It has a few custom steps to map a drive, prompt for the image creation name during PE and then capture the local C: drive to a share on my SCCM server. It works perfectly.
(We are essentially, for the short term (long long story) using this method to capture and image our clients. Yes it's like ghost and I realize that, but it's what I have to work with and it's quite functional. We are a mixed environment with 90% Novell systems that have no MS client installed. We are migrating this summer to an all MS/ AD environment. So, this is a short term solution as we have so many images. We are shutting off Zen imaging in about 2 weeks and this will be our solution until June. We are a large school district with so many apps it's sickening. Once we get migrated to AD, we will utilize SCCM fully for all our clients. Lets put it this way... after June 1, I'm looking at imaging roughly 8,000 PC's/ Laptops with SCCM on a new Win 7 image. Then utilizing a new WSUS instance and managing packaging apps etc.
My question is this...
What/ where determines the boot wim file the PXE process will utilitze? The last advertised TS?
Is there something more I can do to have my "capture TS" advertised also while pushing the 7 other TS advertisments utilizing the standard x86 boot wim? I gather it might just be one custom, scripted boot wim for all instances? Any instight is very appreciated. Still an SCCM newb here...
When I boot and get the capture advertisment, I still get my entire list of TS's, but if I choose to image a machine, it runs to a screen telling me to use my capture media and reboot. Essentially failing.
When I boot and get the sstandard x86 advertisment, I get my list of TS's and can push an image down successfully.
I need a way to use one boot wim and either push or pull an image.
Thanks for this site and sharing your knowledge. I reference it constantly and can't say enough good things!
Share this post
Link to post
Share on other sites