Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

About vk5pj

  • Birthday 07/30/1959

Profile Information

  • Gender
  • Location
    Gawler, South Australia
  • Interests
    Radio, electronics and oh yes those silly computers

vk5pj's Achievements


Newbie (1/14)



  1. Not really sure why this helped but removing a value from here did it for me. before <UILanguageFallback>en-US</UILanguageFallback> after <UILanguageFallback></UILanguageFallback> now when I run sysprep, the machine comes up as EN-AU as intended, so I am not going to argue. here is the full block (near bottom of sysprep.xml) <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>en-AU</UILanguage> </SetupUILanguage> <UILanguage>en-US</UILanguage> <UILanguageFallback></UILanguageFallback> <UserLocale>en-AU</UserLocale> <SystemLocale>en-AU</SystemLocale> <InputLocale>0409:00000409</InputLocale> </component>
  2. Hi Morrell well its image time again so the whole saga starts again today. Have fiddled some more with my unattend.xml today and installing a fresh image on our sample PC for the new delivery. Not expecting too much to be different as I thought I had tried most options. Will update the thread if I have any news. Peter.
  3. Hi Anyweb, this process is not being done in a SCCM task sequence, the sysprep action in this case is being done manually from the CMD line to prepare it for a manual capture using imagex, we then ship the captured WIM file to our hardware vendor for them to pre-load onto the hardware we are purchasing. We have a dummy Hostname in the unattend.xml that we then use a VBscript to search and replace during the first boot up sequence of Windows, this prompts the technician to enter a HOSTname and then we insert that into the unattend.xml file instead of our dummy name. Doing this cuts down on the: boot, change name, reboot, join domain, reboot sequence that had to occur previously to put a new PC onto the network with the correct hostname. (we like to know which classroom each PC is in when something goes wrong) The unattend.xml was built from scratch in the "Windows System Image Manager" and then copied to the c: drive of the PC before sysprep.exe is run. This process is based on this article: http://community.spiceworks.com/topic/427460-sysprep-to-change-computer-name I had noticed that the correct language order was not being honoured last year (Windows 7) but just relied on Group Policy to fix up the order for me but thought I should try to find out why this happens for this years PC's (windows 8.1 x64). At present it is still a mystery as to why us-ENG is the top of the language order. Regards, Peter Sumner
  4. looks like this is a dead end, thought for sure there would be a NOOB user who knew the answer to this.
  5. Hi, not yet, still get eng-US as the default language after I load the sysprep'd image to a PC. The desired eng-AU is there in the list but not selected as the default language. getting a flat spot on the forehead from this one as it takes so long to build test check, build test check. Maybe I should try multiple sysprep's on the one image but did not want to pollute my testing. Peter
  6. Hi tribe81, yes in my unattend.xml I have this: <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>en-AU</UILanguage> </SetupUILanguage> <UILanguage>en-AU</UILanguage> <UILanguageFallback>en-US</UILanguageFallback> <UserLocale>en-AU</UserLocale> <SystemLocale>en-AU</SystemLocale> <InputLocale>en-AU</InputLocale> </component> Tried it with the fall back language set to en-AU and it did not improve the outcome. maybe I should have posted this snip at the start. Peter.
  7. Hi, I have been loading an image from SCCM onto a new hardware platform that we plan to purchase for the 2015 deployment across the school. We are lucky enough to be able to send the completed image to the vendor (we use imagex to create a WIM to be sent to them) to be loaded onto each PC in the factory. When testing the image after having run SYSPREP and rebooted I can see it's default language is eng-US and not eng-AU that was specified in the unattend.xml file used. Other than relying on group policy to change this order for me later on, does anyone have any ideas why the selection of the default language is unattend.xml is not honoured after the image is syspreped and rebooted? Regards, Peter Sumner Down-under in Australia
  8. Hi Rocketman, your mention of the PXE flag sparked a thought, for some unknown reason the PXE flag is never being set on a computer record. When I go to clear the PXE flag (usually in a fit of anger) I find it has never been set. This may be a part of my overall problem, I think that WDS is responsible for keeping a track of the PXE boots so might have to poke around there on a quiet day. We are not using "unknown computer support" we manually register new computers via NetbiosName and MAC, it would seem I have to keep digging. Regards, Peter
  9. Hi, further to my original post, I have found that I can seemingly do as many PXE boots as I like if the TS never gets to the point where the SCCM client is installed and allowed to communicate back to the SCCM server. I found this yesterday when trying to get another TS to run, I had many failures in the early part of the TS where it crashed and burned before the SCCM client step. I was able to keep using one PC and its client record for over 10 boots but after I had found my error and had gotten past the point where the SCCM client initialised, the next PXE boot was then again exiting early :angry:. So it would seem that on a non domain joined machine, when the client initialises it makes a change to the client record in SCCM that triggers this fault. At this point I have no idea what this change might be, I do know if I delete the client record in SCCM and then recreate it after a while it will all work again. Regards, vk5pj (peter)
  10. Hi, during the re-build of our reference image for win 7 and the start of a reference image for Win 8.1 under SCCM 2012 I have noticed that after two or three builds, the records for the client PC's no longer work. In the logs on each of my test PC's I can see reported the error of "no task sequence can be found for this computer" yet only 30 minutes before hand they were happily building via the same TS. When it occurs, the boot goes through to the stage where it says "preparing network settings" then at this point it reboots. One is a physical PC and two are esx VM's. I have used these platforms many times before when on SCCM 2007 and never had a hitch but notice that in SCCM 2012 this has become a common thing for us. It would seem that the only way to get them working again is wait two days (over a weekend worked) between builds or delete the record for each computer and then generate them again after waiting for SCCM to delete them entirely. I am hoping this is a silly configuration mistake we have made or others may have an insight into what might be wrong. regards, vk5pj (Peter)
  • Create New...