anyweb

it should, what name are you entering in that field ? can you share your smsts.log files so I can take a look

open a cmd prompt at the HTA and cd to the folder where the scripts for contacting the webserver are located then, execute the cmdline to run the ChangeComputerName.wsf script to do the computernaming, the first time you try it don't include any parameters, what output do you see ? next time you run it include the parameters it expects, what output do you see ? to add more logging in cmtrace (make sure it's open with the ChangeComputerName.log in view) then execute the script in debug mode like so ChangeComputerName.wsf /debug:true this should reveal the source of your issues but for a pointer, from you error above it's not finding the prefix as you are either calling the wrong URL or the parameters speficied are not correct, which could be true as the webservice you show in your screenshot has different parameter names to the one in your customsettings.ini

yes it's normal two places and only if needed in the boot wim in the winpe portion of the OS start windows deployment services (the gui) and see if the service is started or not and where it refers to

you could try disabling the install language pack sections and see what happens, to add an ou selection you'll have to code something yourself, it's not that hard and others have asked about that already here diffuser is depreceated in Windows 8 and onwards, see my previous HTA releases for the steps to add it back, good luck

nope this takes care of it all

can you explain what you mean here.... do you mean that was the time displayed in Windows ? are you set to sync with internet time or do you have ntp servers configured ?

well i think you should call microsoft and alert them to this, I haven't heard of others with the same exact issue, and can you confirm that you are only seeing the issue when there is NO battery power left.

were all three bought at the same time ? have you contacted Microsoft about the issue ? it sounds to me like the battery is running out of power and that it's reverting the date/time to when the device was manufactured

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