anyweb

ok well the next time you have this issue do as follows, PXE boot or USB boot the device and press f8, type date and verify the date, do the same for time, what date/time does it revert to on all 3 devices ? is it the same or is it way off,

definetly a weird issue and from my time looking at it i couldn't figure it out, the logs look ok, the status looks ok, so perhaps you are missing a hotfix, have you tried applying cu4 yet ?

and have you verified that the machine built is using the actual updated wim and not the previous un-updated wim ?

glad to hear it's working the way it should Alan !

can you do a teamviewer session and i take a look

check these out Customising Windows 7 deployments - part 1. Changing the keyboard layout using unattend.xml Customising Windows 7 deployments - part 4. Deploying Language Packs Offline using MDT 2010 Update 1 Customising Windows 7 deployments - part 6. Adding multiple keyboard layouts and multiple languages [Mar 2012]

look at the smsts.log and see what happens when that step runs, does it error out, if so whats the error ?

is the battery going dead and somehow the cmos battery is returning to an manufacturing date time ?

press f8 before it reboots and see if you have a valid ip address, also read the smsts.log in x:\windows\temp\smstslog it'll reveal the problem

have you seen this yet ? CM12 in a Lab - How can I sync the BIOS date in WinPE to avoid PXE boot failure with System Center 2012 R2 Configuration Manager ?

if you had used my script then you wouldn't have that problem ;-)

reply from 1E below...

i've pinged 1E, they should reply soon

where are you attempting thiat from and is your server really using that fqdn ?

now that rings a bell, thanks for posting it.

during setup windows and configmgr Windows is laid down and after installing device drivers it boots into Windows... does that help ? nic drivers inserted into your boot wim are only for WinPE sections of the task sequence, for the rest of the task sequence use the apply driver package step where it injects drivers into Windows

are you using the correct version of the client, ? which one did you use and what version of configuration manager are you running

can you show me a screenshot of that, does smsprov.log reveal anything further ? are you trying the import directly on the primary or on a remote console ?

ok what hardware are you testint this on ? looks like you have no network, probably due to lack of a network driver for the computer in question, if you press f8 and test that you can ping the fqdn of the mp during osd what happens have you added any network drivers to your boot image for this hardware ?

have you checked the C:\MININT\SMSOSD\OSDLOGS\bdd.log yet ? it should contain lines explaining what is wrong have you verified that not only are you updating the MDT deploymemt share but that you are also updating the boot wim stored in WDS, as updating the deployment share does not do this for you and it'll use your old bootstrap.ini until you do open Windows Deployment Services, go to the Boot Images folder, right click and then Replace the current boot image with the one just rebuilt.

thank you ! it requires manual work, when i put together the new scripts i have to manually download the stuff and when i get to the download page after selecting one or more downloads and clicking next, i view the html source and pull the urls from there

what does your appenforce.log tell you ?

fix your multicast issues first as they appear first in the smsts.log, one or more of your packages is enabled for multicast, most likely it's the operating system wim image, did you check that ?

I wouldn't be too concerned about capturing that driver, you can always uninstall it in the deploy image if you believe it's causing an issue, or use hyperv and not have this problem.

well if it's a local user then why are you specificying a domain ? try inputting the server ip there instead