rj07thomas

glad you've got it working! and sorry it took a bit of working out.

Hi, I found this link - https://communities.intel.com/thread/43218?start=0&tstart=0 - which suggests a lot of people have had trouble with this NIC. Somebody mentions getting things working with a very specific version- 18.5- of the e1d63x64.inf driver, rather than e1d62x64.inf. Unfortunately I don't have access to this NIC so can't test it but it might be worth a go- at least 2 people seem to have got PXE working with this inf file.

Entirely incidentally and off track (as I don't know that they definitely PXE boot), if you're looking around for a USB Ethernet adapter then you could do worse than this: http://www.uk.insight.com/en-gb/productinfo/network-adapters/0003659476-00000001. We've just got a bunch of Surface Pro 3s, and while they're fantastic they have no LAN and 1 USB. This adapter is brilliant- LAN, 3 x USB and has a power supply so I guess you can use powered USB devices with it. Perfect addition to the Surface. Anyway, that's beside the point...

Hm, ok. I didn't honestly think you'd have missed the time discrepancy but thought it was worth mentioning! Bit puzzled now; intel have version 20.1 of those cards drivers at https://downloadcenter.intel.com/product/60019/Intel-Ethernet-Connection-I217-LM, do the updates on the distribution points work cleanly? When I was using the wrong driver, the "Update distribution points" bit would fail and the drivers wouldn't get added to the boot image (i.e. a graceful fail). Like I say, my problem could have been a driver issue too until I located the correct XXx bit driver. One of the things I did was trawl through the .inf files to make sure my model of NIC was listed (82566DM-2, installs as just a Pro/1000). Hope you get somewhere with this, it drove me nuts. Plus, it was only the one PC. And it wouldn't reboot because of the BIOS issue, so I ended up with it sat on my desk so I could hit F1 each time. Not sure the effort was worth it as we only have a handful of OptiPlex 755s and don't know we'll re-use them...

Hi, hope any of these might help. Have had a similar problem recently (yesterday), the fix was either finally getting the right driver (an Intel Pro/1000) or the BIOS clock was wrong. This PC was an old OptiPlex 755, so you shouldn't be having time problems with new kit. I think I was using the NT5.x driver to start with, switched to the NT6.x one. And sorry to ask a stupid question, are the drivers definitely in the boot image? Not exactly a fix, but have you tried a USB NIC?

Hi all, I just wanted to say I'm not ignoring you! Believe it or not, more than a week later and I still don't have a reliable W7 capture although with Peter33's comment I'm having more luck with a Hyper-V VM with 8GB of RAM. I've continued to forget key things- like the SMSSLP Line :-( - but it is rebuilding again now and has 192 updates, which is encouraging as my last update batch was 190. I also had some automated updates rules in place, so I started from scratch with them as I couldn't tell whether the updates were causing problems. I'm back to static update packages/ groups now, which isn't ideal but for a gold build doing a new build every few months with a bigger batch of updates shouldn't be too much of an issue.

ah, thanks both. Re: windowsupdate.log do you mean on the client or server? Sorry, probably a daft question. Peter33- thank you! I'm trying to do this on loads of different clients, including virtual, so there's a chance I can knock up a Hyper-V VM with bucket loads of memory, tho' of course this isn't going to help if it's a memory leak. It's just really odd that the W8.1 build went through really smoothly, I'm used to forgetting really obvious things when deploying (like forgetting to include SMSSLP=, which annoys me because it's such a stupid, easy mistake) but these builds have actually been going through to the update process. Anyway, thanks for your suggestions- I've got something more concrete to go on now. P.S .neither of you know anyone or any resources that might help with a really annoying cipher suite error from iis through a firewall? Completely off the point but worth mentioning!

Hi, I was wondering if anyone had come across this before? Doing a build 'n' capture of W7, downloads all the updates just fine and starts installing them but then gets stuck on a particular update. No particular error, just hangs. So far, stuck at 145 of 190 and 179 of 190. ?

Hi simulacra75, well the "fix" is far from perfect and isn't a fix. I created another instance of SQL on the same host, using the CD that MS supply with SC which is "free" for SC use (I know "free" is the wrong word but it kind of is). After finding a post talking about dynamic ports, I reconfigured all the ports to static on this instance and then the move worked, so at least I've taken the database off the evaluation copy of SQL. Fingers crossed that's enough to keep us going. Thanks for all your help and suggestions and hope you have a good day.

Hi Simulacra75, thanks for that and I'll give this a go!

hi simulacra75, thanks for this but I've just put the computer account into all nodes and it doesn't work...

Hi, I have SCCM up and running happily, on a stand-alone server with SQL Enterprise in eval mode. Fine, everything working lovely and it can do build, capture, install etc. "Perfect". Now I want to move the database to our SQL cluster. Backup the database, move the backup and restore it onto the cluster. Fine, no problem. Start SetupWPF on the SCCM server, go to the SQL maintenance page, start the move to the cluster. This is where it falls over: there are 4 repeated lines, talking about self-signed certificates. These repeat endlessly until I think the process times out. I don't know why SQL is even bothered about certificates as it shouldn't be using SSL (deliberately). I've followed numerous posts online about this problem but to no avail. Is there either (a)an easy way around this or ( can I somehow move the database from within SCCM and bypass SetupWPF? I don't want to delete SCCM and start again, I'd have thought moving the database would be relatively trivial. Here are the errors: *** Failed to connect to the SQL Server, connection type: SMS ACCESS. Configuration Manager Setup 03/10/2014 09:18:41 2544 (0x09F0) INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure Configuration Manager Setup 03/10/2014 09:18:41 2544 (0x09F0) *** [08001][-2146893019][Microsoft] SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup 03/10/2014 09:18:44 2544 (0x09F0) *** [08001][-2146893019][Microsoft][sql Server Native Client 11.0]Client unable to establish connection Configuration Manager Setup 03/10/2014 09:18:44 2544 (0x09F0) I'd be really grateful for any help- the eval will expire soon and I don't understand why it's even using SSL. I've tried attaching various certificates to the destination SQL Cluster and it just crashes SQL, so I'm guessing that's not the answer.

Thanks- really appreciate it, it's kind of where we need it to be now so hopefully I can move my focus onto an Exchange 2007- 2013 upgrade !

Hi Niall, Thanks for this- and yes, that was exactly the problem. I redeployed everything from the captured image right through to the deployment task and that works, I can now see 97 updates. Sorry for wasting your time on this one- this is the biggest thing that catches me out (still) with SCCM is having to redeploy everything every time you make a change. Thanks again for all your help and hope you have a good weekend, Rhidian

Hi, I'm pretty sure they're installing during the build- I'll take another look, but the "install updates" step is running- it's downloading and installing xx updates without problems, and then I boot into the build and it shows xx updates (weirdly, this count has gone down so I'm guessing MS must have bundled some updates into others or decommissioned some). Thanks again, Rhidian

Hi Niall, Just one more favour- could you point me in the right direction as far as the capture logs are concerned? I'll configure network discovery, but I'm just curious as to why the capture process isn't capturing an OS that I know is patched. Many thanks for all your help, Rhidian

Hi, and wow- thanks for your reply, much faster thank TechNet social! It's the build process... or more specifically, the capture. I think you may have hit the nail on the head with boundaries- it is in an AD boundary, but like you said is a workgroup member so this won't work. What I don't get is that it is installing the updates, because when I boot into the "built" image there are 97 updates. It will capture the image fine, but seems to miss the updates. However, I really appreciate your help and will give re-configuring the boundary a go so that it's on an IP range rather than AD. Much appreciated, purely on a sanity basis! Rhidian

Apologies if anyone's seen this before- I posted it up on TechNet social 2 days ago and have only had 71 views, no responses! I have an SCCM 2012 R2 test environment. I've deliberately avoided modifying the AD schema etc so as to impact our environment as little as possible. I have a few packages working- Java, QuickTime etc. some are compulsory, some are optional. Just messing around really to proved a proof-of-concept. I've also built up 2 tasks: a build and capture (W7ProSP1), and a deploy for the captured image. The B&C process seems to go perfectly. It partitions the disk, applies the base OS, installs the updates and captures it. No errors, no hangs. I know the updates are applied because when it boots into the built OS, there are 97 updates in "Windows Updates". The PC (hyper-V) is a workgroup member, as is necessary for sysprep. I've even set (one at a time) the SMSSLP and SMSMP properties in the client options to point to the sole SCCM server. They both seem to make sure the updates are located, downloaded and installed properly I run the deploy task against the same machine, and it goes perfectly. It downloads the correct WIM, applies it, reboots, sorts out Windows and the SCCM Client, and presents me with a login screen. Perfect. I Go to "Windows Updates", and there are just 3 updates, not 97 as I would expect. What am I missing? Everything appears to be 100% correct, apart from the fact that the capture process is either ignoring the 97 updates somehow, or is capturing some fictitious build from Mars. I've removed the "install updates" step from deploy stage- this actually works, but kind of defeats the point of having a "gold" build- this image should now contain 97 updates, 96 of which were downloaded as part of the build and capture process. This surely must be an easy fix- it's 99% of the way there, it's simply refusing to capture the updated copy of Windows 7. I've been through a few phases of the updates just not working (usually to do with stupidity :-)), but like I say if I boot into the just-built image it does have all the updates, so I can't figure out why the capture phase isn't getting these. This is driving me slightly nutty, so any help really appreciated.