Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

About goudviske

  • Birthday 08/03/1982

Profile Information

  • Gender
  • Location

goudviske's Achievements


Newbie (1/14)



  1. Ok nevermind that, seems I needed to add some generic drivers to the .wim file Installation does proceed now but seems to be stuck at the Welcome / Login screen You see Machine\Administrator Circle thing turning Welcome Then after a long time, you get: Unable to find litetouch.wsf needed to continue this deployment Any thoughts ?
  2. Hi, Short version: Tried deploying win 8 to HP Elitepad tablet computers. When trying to deploy over PXE, I encountered some issues (more here http://www.windows-noob.com/forums/index.php?/topic/8045-trying-to-deploy-over-pxe-uefi-x86-with-wds-2012/), I think they're related to pxe booting a x86 uefi machine, which my wds 2012 doesn't seem to like... After a couple of days I thought why not try to deploy it over USB, created a task sequence, configured media on the WDS and tried deploying it. At first I hit some issues related to disk partitioning, that seemed to be resolved, but maybe it isn't entirely. What happens now is: - Elitepad boots on USB - Task sequence performs a few tasks - prepares - formats the disk (uefi) - injects drivers - uses imagex to expand the previously captured .wim - reboots Then when rebooting I get a new style of blue screen. This shows: the operating system couldn't be loaded because a critical system driver is missing or contains errors file: \windows\system32\drivers\megasas2.sys Error Code: 0xc000035e I suppose it has something to do with drivers for the storage controller, but I don't quite get what's wrong, the drivers are installed correctly in the .wim, so after restoring that should be ok, and also they are injected during the earlier phases. I think it may have something to do with which partition is active, but I can't seem to get it resolved. Any thoughts/ideas/... ? Thanks
  3. Hi, Specifications state that it does support PXE boot, and it only has a UEFI firmware (32 bit, the Atom chip is x86) (no legacy mode), so yes I believe it does. Btw, I have got the same issue when trying to boot another laptop when legacy bios is disabled, or when trying to boot a vm with UEFI enabled
  4. Hi, thank you for the very very fast reply, I believe it does. Also there's information regarding PXE booting from HP itself in this document http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c03698024/c03698024.pdf So I think it's safe to assume it does support network boot, also the option has been enabled
  5. Hi, I've been reading a lot on these forums the last couple of weeks, mostly regarding SCCM etc, but at the moment I've got an issue I haven't been able to wrap my head around. We're using a standard win 2k8 r2 domain environment. This environment used to contain a server with MDT 2010 and WDS 2008 (server 2008 r2), used for deploying win7 etc, the environment used to work pretty well. Then somebody thought it was a good idea to buy some tablet computers, to be specific the HP Elitepad 900. Specs for this tablet computer indicate it is able to do PXE boot (there is an ethernet port on the docking), but due to limitations this only works using UEFI (BIOS not supported). After a lot of reading I found that wds 2008 does not support x86 uefi, so the server was upgraded (no fresh install) to windows server 2012 (with wds 2012) and mdt 2012 update 1. Legacy computers are still able to PXE boot correctly (and complete installation), but UEFI machines, or machines starting in UEFI mode can't do this at the moment. What happens is: - boot the computer over network (or tablet), we mainly want the elitepad to get working (x86 uefi), but I've also tried booting another machine using x64 UEFI with the same result - the following is shown: >>Start PXE over IPv4, Press [ESC] to exit... Station IP address is x.x.x.x Server IP address is x.x.x.x NBP filename is boot\x86\wdsmgfw.efi NBP filesize is xxxxx bytes Downloading NBP File Succeed to download NBP file. [EDIT] Not sure if it's NEP or NBP file, not very clear on the screen Then the screen changes and I see: Windows Depoyment Services (server IP: x.x.x.x) Contacting Server (x.x.x.x): - (this is like turning / - \ - / - \ ...) ESC= Exit After a while (timeout)the computer shows: Windows Deployment Services encountered an error: Error Code: 0x102 ENTER=Reboot What I've tried/changed so far: Changed the NBP filename in DHCP options, it used to be boot\x86\wdsnbp.com (when not using UEFI), before changing this I simply got network error when trying to network boot. Added NIC (and other) drivers in WDS 2012, regenerated the boot image afterwards etc. Tried reinstalling WDS on a newly installed windows server 2012 (without mdt) in standalone mode. Other stuff I can't think of at the moment :-) PXE booting of our SCCM 2012 update 1 (only used for updates & endpoint protection at the moment), but with the same result Any thoughts/ideas? I have a feeling I'm overlooking something stupid, but then again it may not be stupid. Thank you [EDIT] Sorry I should have posted this in http://www.windows-noob.com/forums/index.php?/forum/43-windows-deployment-services-wds/ [/EDIT]
  • Create New...