SCCM 2012 (Build from instalation source)

[ptotham]

I have recently started testing sccm 2012, but have run into some problems with my task sequence:

 

 

the build gets to the stage of formatting the hdd drive does the format and then skips straight through the rest of the steps with no error message, I have looked at the smsts.log file but cant see myself why it wouldn't be working could someone please have a look at the log and tell me where I am going wrong.

 

I have attached a screenshot of my task sequence and my smsts.log file

smsts.txt

[localzuk]

This is the sequence we use. You seem to be missing some steps.

 

Have you done a build & capture?

 

As far as I can see, an install sequence should be:

 

Restart in Windows PE

Partition the disk

Apple Data Image (which you generated from your Build and Capture task) (Image 1-1, so the 300Mb bit of disk)

Apply the OS (2-2 of the same image above, to the C: drive) - Apply an unattend.xml file here

Apply settings such as user name and organisation (product key is applied via your unattend.xml in the step before)

Apply network settings (domain to join, OU to put the machine in, account to use)

Apply Drivers

Apply any extra driver packs

Setup Windows and Configuration Manager

Any extra steps (application install etc...)

 

I'd recommend looking at Portal - www.windows-noob.com for the relevant tutorials.

[Sagima]

With sccm 2012 use the wim on the installation media as the install image. Don't try and use installation source - i didn't get it to work like it did in 2007

 

You'll need to add a task sequence variable just before that as the wim on the windows 7 media goes to D.

 

Add -> General -> set task sequence variable

 

[jaminben]

I personally never had much luck using SCCM to capture an image but found MDT to be a much better solution and once the image is built I simply copy it over to the SCCM server. MDT uses the same principles as SCCM (task sequences etc so shouldn't be too hard to set up).

 

Just an alternative....

Edited March 6, 2014 by jaminben

[localzuk]

That seems like a lot of work when SCCM should handle it all anyway.

[ptotham]

This is the sequence we use. You seem to be missing some steps.

 

Have you done a build & capture?

 

As far as I can see, an install sequence should be:

 

Restart in Windows PE

Partition the disk

Apple Data Image (which you generated from your Build and Capture task) (Image 1-1, so the 300Mb bit of disk)

Apply the OS (2-2 of the same image above, to the C: drive) - Apply an unattend.xml file here

Apply settings such as user name and organisation (product key is applied via your unattend.xml in the step before)

Apply network settings (domain to join, OU to put the machine in, account to use)

Apply Drivers

Apply any extra driver packs

Setup Windows and Configuration Manager

Any extra steps (application install etc...)

 

I'd recommend looking at Portal - www.windows-noob.com for the relevant tutorials.

 

thanks for your feed back, I am not trying to build from a wim image that is why there is not the steps in the build for that, I have copied the content of my windows 7 cd up to my server and then imported that into sccm (this is how I have it setup in sccm2007).

[localzuk]

It doesn't work that way in 2012 any more - B&C with a wim is the recommended way to do it.

[ptotham]

It doesn't work that way in 2012 any more - B&C with a wim is the recommended way to do it.

 

does it work, if you use the install.wim on the windows 7 CD?

[Arthur]

That seems like a lot of work when SCCM should handle it all anyway.

You're missing the point.

[localzuk]

You're missing the point.

 

Not missing the point - its not necessary for everyone to have a custom default profile. We don't here - pupils have mandatory profiles and we've yet to find a reason to have one for staff.

 

does it work, if you use the install.wim on the windows 7 CD?

 

I believe so. You have to make sure you include the Task Sequence Variable in it though, per this article - http://www.petervanderwoude.nl/post/how-to-apply-the-default-install-wim-of-windows-7-to-c-with-configmgr-2012/ otherwise you end up installing to D:\ or something like that.

Edited March 6, 2014 by localzuk

[Arthur]

Not missing the point

You are because that's not the only reason for using MDT with SCCM.

[localzuk]

The OP looks to be trying to setup a simple imaging task. MDT is muddying the issue. Suggesting it as a fix is much like saying "replace your motorbike with a truck"!

[jaminben]

Suggesting it as a fix is much like saying "replace your motorbike with a truck"!

 

Was just suggesting an alternative

[ptotham]

have just run through the create the build and capture task sequence and deployed it to unknow computers but when i run the ts it comes back saying that the ts failed because (a package code which references config manager client package) cant be located on the distribution point but when i look on the server at distribution status - content status I can see its there and correct

[Sagima]

You can right-click the task sequence itself and select distribute content. If anything is missing it should let you add it to a distribution point. there won't be an available distribution point if everything is ready.

[ptotham]

You can right-click the task sequence itself and select distribute content. If anything is missing it should let you add it to a distribution point. there won't be an available distribution point if everything is ready.

 

thanks for your response sagima, when i try to distribute content again no distribution point available which says to me everything is there and I even re validate the package and redistributed on the distribution point through the properties settings but still no joy.

[snagrat]

Post the new smsts log and we'll take a look.

 

Now you actually have an error I should give you enough info in smsts to find the cause.

[Sam_Brown]

What are the benefits of doing a B&C over installing from install.wim from the Windows 7 DVD?

 

I tried a few times to get B&C working but always seemed to mess up installing the Config Client so I went with installing from the install.wim and it worked fine first time so I never bothered to go back and look at getting B&C working when the current way we do it worked fine. Most workstations image in < 60 minutes.

[free780]

But the amount of updates must be huge.

[Sam_Brown]

Most of our updates just get installed once the laptops are out and about in use.

 

I never managed to get updates deploying at build time. Is it easy enough to get sorted? I might have to look into it the next time we refresh all our workstations.

[free780]

Well you can just use ztiwindowsupdate.wsf from mdt. I do a build and capture using mdt and then import the image into sccm. But its a pretty thin image. I like the image to be fairly up to date otherwise its a pretty poor experience for the user if it takes weeks for the laptop to be up to date. Not to mention bits chugging away in the background.

[Sam_Brown]

Must admit I've never used MDT before. Not entirely sure what it can do to be honest. I went straight from WDS to SCCM. I do agree with you by the way. Having updates already in the base image would be preferable. I'm not justifying the way it's currently set up when there are things I can implement to improve the current system (although it works well at the moment luckily).

 

Is there a way to take the standard install.wim from the Windows 7 and slip stream the updates in or is B&C the way to go?

[free780]

If you have the software update point set up you can just update the install.wim offline. I've not done it myself.

[snagrat]

I just build a Win7 virtual machine any old way and then capture it as and when required. I use the SCCM capture media to capture it.

 

I update the OS via the web through this machine then use the SUP to manage it when deployed.

 

Just keeps things simple

[ptotham]

snagrat please find attached my smstslogs file thank you for taking a look.

smstslog.txt