Jump to content


anyweb

using SCCM 2012 in a LAB - Part 7. Build and Capture Windows 7 X64

Recommended Posts

hi Denis !

 

Hi Niall!

As promice i post my questions here:

 

1. Can you properly tell how distribute Windows Updates in work environment with SCCM 2012? Not deploy to captured image, but administering it same simle as i can do it with WSUS? What about Drivers, Tools, other updates from WSUS categories???

 

2. In your LAB you use Build and Capture scenario, but in work environment i have to make some changes on Windows (change settings, interface, install programs, put shortcuts). In MDT i can use Sysprep and Capture scenario. When i wrote this post i found pinned topik about this http://www.windows-n...configmgr-2012/

but then i have other question: what profit from using SCCM to capture image, if i can't do this with PXE boot? I can do bootble ISO myself and use ImageX whitout SCCM....

 

3. In my work environment suddenly in users Software Center appeared as update 'Build and Capture Windows 2008 Server' (i forgot to check option Do not show in Software Center) and when user choose 'Install All', his notebook disk was formated. How it could be, user do not know password for PXE boot ?

 

Sorry my English.

Thank for you understanding!

 

1. did you follow this guide

2. I prefer the build and capture process as it is 100% automated, however you can also do this

3. what collection did you deploy this task sequence to ? was it all systems ? if so now you know not to do this again and consider these ideas.

 

keep up the good work

cheers

niall

Share this post


Link to post
Share on other sites

Thank you for answer.

About #1 question - Deploying Windows updates,

Yes, i follow this lab, and all updates packages distribute to clients, all works fine.

But i can't understand concept of monthly distribute updates. How i have to automate it? Is i must every month manualy create new packege for many collection, for office, for other type of updates ?

If so, i think WSUS more useful for me.

Share this post


Link to post
Share on other sites

Finally managed to crack it. Posting here for others with the same issue. Basically, further down in your guide, you've got:

 

if you get any errors about packages not being found then enable the following setting in Data Access for all packages in your task sequence including the boot image:- copy the contents in this package to a package share on distribution points

 

post-1-0-94235500-1320659351.png

 

Note: once you have enabled the setting above your Deployment distribution settings gets a new drop down menu choice, access content directly from a distribution point when needed by the running task sequence

 

post-1-0-75319600-1320674392.png

 

and then try again.. our client is being built

 

I did this and hey presto, it worked, woo hoo!!

You may want to move this bit further up in your guide, as people like me who experience these errors, will not read further on and see the above until they've got the issue sorted.

 

Thanks

  • Like 1

Share this post


Link to post
Share on other sites

Dear

Are you very powerfull people and i very need your help for undestand what happend.

I have problem in the point 4

 

when i try to add a boot image i recevied that error

Error: Data Source Information

• Source location: \\srv-itpa-cfgm01\sources\os\win7x64ent_ita\sources\boot.wim

• Boot Image: 1 - Microsoft Windows PE (x64)

 

Error: Package Information

• Name: boot image x64

 

Error: Errors

• You can not import this boot image. Only finalized boot images are supported. For more information press F1.

Grazie ancora

 

 

I explain what i do:

 

1i copy the all cd folder in the share folder

2: when ask to me to browse i file i select the sources and the file boot.wim

3: select windows pe(x64)

4: Run

5 See the error:((((((((

 

 

what i wrong, i used iso of win 7 enterprise x64

 

i dont undestand..... please if you have time help me.

 

A big kiss

Share this post


Link to post
Share on other sites

I need some help here. I got stuck in the step4 Customise our boot images and then Distribute the Boot images to DP's. I pulled out the smsprov log and it keep gives me error, and I can't continue.

 

Error setting property (TransformAnalysisDate) 0x80041002! SMS Provider 5/11/2012 9:01:31 AM 5096 (0x13E8)

Error setting property (TransformReadiness) 0x80041002! SMS Provider 5/11/2012 9:01:31 AM 5096 (0x13E8)

 

Please give me some advise here,

My problem is when doing Step 10. PXE boot our new Virtual Machine

and here are my screenshot and in the capture4.jpg, it didn't run into the task sequence for a password and it will jump back to the original OS bootup (XP)

post-16018-0-16082800-1337306415_thumb.jpg

post-16018-0-18196400-1337306427_thumb.jpg

post-16018-0-33511900-1337306438_thumb.jpg

post-16018-0-40502500-1337306447_thumb.jpg

Share this post


Link to post
Share on other sites

Hi,

 

Thanks for some very nice guides - keep up the good work :)

 

A question though:

My Build and Capture stalls during action: Install Updates

 

aXfHE.png

 

Any suggestions what could be wrong?

Im wondering why there are 11 Updates, but theres alot more than 11 updates approved im SCCM?

 

Regards,

f-andersen

Share this post


Link to post
Share on other sites

are you sure the updates are on your distribution points ? how many updates are deployed to your build and capture windows 7 X64 collection ?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

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.