Jump to content


TimLancer

Build & Capture Windows 7 problem - possible network issue?

Recommended Posts

Long time lurker, first time poster. Niall, your guide has been invaluable and Microsoft is lucky that people like you exist in the community. I'm sure it's a lot of hard work without much thanks - so THANK YOU!


I followed your SCCM 2012 guides to setup a fresh install of SCCM 2012R2 Update 1 on a VM running Server 2012 + SQL 2012 + MDT 2013.


My goal is to have a Windows 7 64-bit 'fat' image with Office 2013 + all Windows Updates installed that I can then use in a separate Deploy sequence. I am using a standard TS and not a MDT TS for the Build & Capture because I read somewhere that it was easier to use the standard to Build & Capture sequence to capture and then the MDT sequence to deploy.


If I follow your Build & Capture guides for Windows 7 (also referencing the Windows 8 one because I'm using the install.wim method) everything APPEARS to go successfully. No errors appear on screen during the Build & Capture sequence and an image file is created. However after the image is created and the Build & Capture machine reboots, I'm asked to enter a computer name, an administrator password, time zone, etc. All things that I thought were spelled out in the Build & Capture task sequence. This makes me nervous that something isn't working properly behind the scenes. Additionally the root of C: still has a SMSTSLog folder.


Digging through the SMSTS.log, I can see several failures that usually indicate a problem with DNS. I'm confused at how I have network during 99% of the process but then name resolution fails *right* after the Prepare OS step? I'm using VMware 5.1 and the VM is a standard Windows 7 64-bit template using the e1000 adapter. It's my understanding that the e1000 adapter works in all the recent flavors of WinPE.


DHCP is running on a Server 2003 machine in the same subnet as the SCCM server and VM and DNS entries are correct in the scope and in the DHCP Server Options. I'm able to hit F8 during the Build & Capture sequence and I can verify the IP is correct, I can nslookup against the SCCM server, and ping.


Things I've tried so far:


* Recreated my boot files just in case (with ADK 8.1) and updated my DPs

* Deleted all my TSes, and OS Installers

* Download a fresh Windows 7 Enterprise with SP1 64-bit from Microsoft's site and imported it again

* Created a new Build & Capture task sequence. The only modifications I made to the stock SCCM Build & Capture sequence are: Modify the 'Partition Disk 0 - BIOS' step so it only creates a single primary partition (not using BitLocker) and setting SMSMP=mysccmhost.domain.local

* Resetting the SCCMNA password

* Creating an SCCMNA2 account and specifying it under the Software Distribution Network Access Account tab (based on other folks' experiences)

* Deleted the Build & Capture VM's device out of the collection and re-added it

* Recreated the Build & Capture VM from scratch


Any ideas at all? I spent the past two days going line by line through your guides again double checking everything I've done.

smsts.log

smsts.log

  • Like 1

Share this post


Link to post
Share on other sites

Additionally can anyone tell me if it's alright to remove the Apply Updates and Capture The Reference Machine steps? I'd like to accelerate my testing process, right now I'm making some changes, crossing my fingers, and then coming back hours later to see if it worked. If I remove Apply Updates and Capture The Reference Machine then I'll be able to see my failure faster.

 

Obviously no updates will be applied and no image will be put up - but that doesn't seem to be the root of my problem.

 

I saw in front of the TS today and waited for it to finish the 'Prepare OS' step. I hit F8 right then at that second, and a nslookup failed. Here's the fun part - an ipconfig showed that DHCP was OFF, yet the adapter had an IP address (the IP it had the last time it obtained a lease) *and* I could ping anything I wanted by IP. If I specified a server in the nslookup command I got back a result. So why would it no longer be on DHCP -after- the sysprep but before the capture? I thought this was supposed to be the easy/automated part :)

Share this post


Link to post
Share on other sites

Just to take DHCP out of the equation, I manually specified an IP address during my Build & Capture sequence. I hit F8 during the sequence and confirmed it was using the static I specified and was able to nslookup and ping. I am getting the same name resolution error in my logs as I did before. Disappointing, but at least I eliminated DHCP as a variable in this issue.

 

Right now I'm out of ideas on what to try next. Am I weird by actually looking at my SMSTS.log file? Are other people considering the fact that an image goes up and the VM reboots into Windows (well that little mini-setup wizard) as the process being 100% successful?

 

Right now with my almost-vanilla TS I'm able to install Windows, apply updates, install applications, and put an image up. Should I just ignore my errors and deploy?

Share this post


Link to post
Share on other sites

Long time lurker, first time poster. Niall, your guide has been invaluable and Microsoft is lucky that people like you exist in the community. I'm sure it's a lot of hard work without much thanks - so THANK YOU!

 

 

Thanks Tim !

 

sorry just saw this now, apologies for not answering sooner.

 

as regards this

 

 

However after the image is created and the Build & Capture machine reboots, I'm asked to enter a computer name, an administrator password, time zone, etc. All things that I thought were spelled out in the Build & Capture task sequence.

 

I wouldn't worry about that, simply take the capture WIM file and deploy it to a new computer or vm, what happens then ?

Share this post


Link to post
Share on other sites

No apologies necessary! And again - thanks! I was hoping for any reply, let alone one from the guru B)

 

I wouldn't worry about that, simply take the capture WIM file and deploy it to a new computer or vm, what happens then ?

 

If I take that captured WIM file, import it, and then Deploy with a TS everything seems to go fine! After the image is brought down the system comes up and the SCCM Client is installed and configured for my organization.

 

Now that you say it's not big deal I feel a bit silly about over analyzing it.

 

I wanted to avoid a potential scenario where my image was 'sort of' broken and I deployed anyway - and then had problems down the line. I'd hate to deploy to 1,200 clients today and not have a problem until down the road when I try to do an upgrade or something.

 

This is all stemming from nightmares of setting up a hardware agnostic image in the Windows XP days - ignoring a sysprep error that didn't SEEM to hang up the whole process could come back later to really screw you over.

Share this post


Link to post
Share on other sites

Tim, once you have captured the WIM, the device is in WinPE so it reboots into the full OS.

 

The screen prompting for computer name, language, time zone etc. (out of box experience or OOBE) is completely normal!!! When deploying your captured image in a deployment task sequence, SCCM injects the information you enter in the relevant steps (apply OS, apply windows settings etc.) into the unattend xml file.

 

So it sounds to me like you build and capture has performed perfectly and unlike some, you have nothing to worry about. Put your feet up!...

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...