I couldn't find any pages on silently installing the windows phone desktop app. The file is downloaded as an exe and the /s -s or /silent or -silent don't appear to work.
http://www.windowsphone.com/en-gb/How-to/wp8/windows-phone-app-for-desktop
However if you want a silent install you can retrieve the msi file by running the exe, the msi can then be found in C:\ProgramData\Applications\Cache mine was titled {E786AE85-8A30-4CF2-BF70-57404A5CD684}v1.0.1720.1.msi
You can then just use msiexec /i "{E786AE85-8A30-4CF2-BF70-57404A5CD684}v1.0.1720.1.msi" /qn
Thursday 12 September 2013
Friday 16 August 2013
OOBE Still asks for Computer Name even though it's set in Deployment Wizard
Something else that annoyed me for a while was that the OOBE prompt for a computer name would appear even though one is set using the MDT Rules and the Deployment wizard. There is a glitch with unattend.xml's. If you are using the x86/AMD64_Microsoft-Windows-Shell-Setup_netrual under specialize and the computer name field is left blank it will ask. You need to instruct it to write an empty value by right clicking the value in WSIM or it will assume it needs to ask.
Another annoying problem sorted.
Another annoying problem sorted.
Thursday 15 August 2013
HP Elitepad 900 Deploying Windows 8: UEFI and MDT2012
I have been having a bit of a nightmare the last few weeks. We have an Elitepad 900 on loan from HP to trial with our sales staff, of course if we are wanting to give out 30-50 of these we want to use our MDT infrastructure. I have finally got it working but there are a fair few hurdles.
UEFI Native Mode Only
The only ways to boot an Elitepad 900 is using a UEFI enabled PXE or USB boot device running Windows PE4.0. So basically this means for PXE boot you need to be running Server 2012, you also need to use the Windows ADK and not the Windows AIK, as that gives you PE4.0. Which leads to hurdle number 2.
MDT2012 cannot locate an ADK or AIK Install
So I have my Server2012 with MDT2012 U1 and the latest ADK (8.1) however MDT2012 reports it cannot find it. I tried allsorts with this one, in the end I rolled back to the ADK 8.0 and the problem went away. http://www.microsoft.com/en-gb/download/details.aspx?id=30652 A lot of links take you to the 8.1 Preview so it's worth checking.
So now we can create our PE4.0 boot media. You will need to add the Elitepad drivers to get network support, you may also want to add the drivers for the touch screen. You need the Driver and Firmware update pack from here . You will need to extract it with the /e /f <foldername> before importing it.
One thing to note if you aren't aware UEFI boot requires a FAT32 device, it cannot read NTFS.
It's worth noting you don't need to modify your task sequences for UEFI despite what HP tell you to do if you read their deployment guide. MDT2012 is UEFI aware and if the device is in native mode it will set an IsUEFI variable to True and will automatically partition the drives accordingly despite the task sequence being set to MBR it will create the EFI, MSR and NTFS partitions.
So now we can boot into our deployment environment and run the deployment wizard. It all runs well until it gets to the Install Operating System Task which leads to hurdle number 3.
LTIApply FAILURE ( 5616 ): 87: Verify BCDBootEx
I spent days on this one due to a few red herrings, but as always it is actually quite straight forward, although as a result it does mean that it's impossible to deploy to a native UEFI device without making this modification.
The LTIApply.log file (From c:\windows\temp\deploymentlogs) shows the command that caused the error cscript.exe //nologo "\\server\deploymentshare$\Scripts\ztiRunCommandHidden.wsf" ""\\server\deploymentshare$\Tools\X86\BCDBoot.exe" C:\windows /l en-US /s V: /f UEFI"
It turns out that this version of BCDBoot.exe is 6.1 not 6.2 so it's from some point in the Windows 7 era hence doesn't support the UEFI command. This file isn't actually required as it is included in the source so I just removed it, the other utilities in there are just as old so it may be worth removing them as well.
Once the BCDBoot.exe has been removed Windows 8 will deploy successfully.
I have since discovered the source for this is the fact I was replicating from our older system, so in a pure 2012/PE4.0 environment this situation wouldn't occur.
UEFI Native Mode Only
The only ways to boot an Elitepad 900 is using a UEFI enabled PXE or USB boot device running Windows PE4.0. So basically this means for PXE boot you need to be running Server 2012, you also need to use the Windows ADK and not the Windows AIK, as that gives you PE4.0. Which leads to hurdle number 2.
MDT2012 cannot locate an ADK or AIK Install
So I have my Server2012 with MDT2012 U1 and the latest ADK (8.1) however MDT2012 reports it cannot find it. I tried allsorts with this one, in the end I rolled back to the ADK 8.0 and the problem went away. http://www.microsoft.com/en-gb/download/details.aspx?id=30652 A lot of links take you to the 8.1 Preview so it's worth checking.
So now we can create our PE4.0 boot media. You will need to add the Elitepad drivers to get network support, you may also want to add the drivers for the touch screen. You need the Driver and Firmware update pack from here . You will need to extract it with the /e /f <foldername> before importing it.
One thing to note if you aren't aware UEFI boot requires a FAT32 device, it cannot read NTFS.
It's worth noting you don't need to modify your task sequences for UEFI despite what HP tell you to do if you read their deployment guide. MDT2012 is UEFI aware and if the device is in native mode it will set an IsUEFI variable to True and will automatically partition the drives accordingly despite the task sequence being set to MBR it will create the EFI, MSR and NTFS partitions.
So now we can boot into our deployment environment and run the deployment wizard. It all runs well until it gets to the Install Operating System Task which leads to hurdle number 3.
LTIApply FAILURE ( 5616 ): 87: Verify BCDBootEx
I spent days on this one due to a few red herrings, but as always it is actually quite straight forward, although as a result it does mean that it's impossible to deploy to a native UEFI device without making this modification.
The LTIApply.log file (From c:\windows\temp\deploymentlogs) shows the command that caused the error cscript.exe //nologo "\\server\deploymentshare$\Scripts\ztiRunCommandHidden.wsf" ""\\server\deploymentshare$\Tools\X86\BCDBoot.exe" C:\windows /l en-US /s V: /f UEFI"
It turns out that this version of BCDBoot.exe is 6.1 not 6.2 so it's from some point in the Windows 7 era hence doesn't support the UEFI command. This file isn't actually required as it is included in the source so I just removed it, the other utilities in there are just as old so it may be worth removing them as well.
Once the BCDBoot.exe has been removed Windows 8 will deploy successfully.
I have since discovered the source for this is the fact I was replicating from our older system, so in a pure 2012/PE4.0 environment this situation wouldn't occur.
Subscribe to:
Posts (Atom)