So I am building a POC for App-v running on MS Surface 2/3, and started by successfully running a Windows 8.1 Enterprise VM, and successfully connect via DirectAccess and App-v publishing servers sync, sync also works on Windows 2012 RDS configured as a Citrix XenDesktop server.

However, on the Surface, I always get error 19102, 19203 both with errors I have yet to find in other threads 0x45500D27 - 0x80072F8F in the logs.  

I can browse to the publishing site and do see the XML page (empty because I am globally publishing to the machines)

Running powershell Get-AppvPublishingServer | Sync-AppvPublishingServer

Sync-AppvPublishingServer : Application Virtualization Service failed to complete requested operation.
Operation attempted: RefreshPublishingServer.
Internet Error: 0x80072F8F - Content decoding has failed
Error module: Publishing. Internal error detail: 45500D2780072F8F
Please consult AppV Client Event Log for more details.
At line:1 char:28

This Surface was imaged using SCCM 2012 with Windows 8.1 Enterprise, using the wim file image, etc.  I re-imaged the machine and manually installed the app-v client with the same result.

Next, I manually installed Windows 8.1 Enterprise from media, with the same result again. 

I never see any error in the publishing server(s) IIS logs from the surface when a sync is occurring.  

The only differences I see between the working and non-working machines is that it doesn't work on the surface, and bitlocker is enabled on the surface.  It works on a VM running in Fusion on a Macbook.  It works on Windows 2012 R2 as well.

Has anyone ever come across this issue?  It is pretty much a showstopper for me as this is meant primarily for Surfaces.

Tried this on another Surface 2 - the result - also re-downloaded the ISO and re-checksummed it (the original checked out fine too though).

This time, I simply joined the machine to the domain, getting the correct policies, and tried to sync the publishing servers, same result as above.

I also created a new windows 8.1 Enterprise VM, followed the above steps, and it worked without error.

What can possibly cause this?  It is very strange.  Could it be something to do with the network drivers of the surface, etc?  Far fetched but like I said, I never see attempts to sync via IIS with the surface.

Ruled out so far, firewall, PKI issues, it being an isolated case, etc.  

Hello,

What happens on a different physical machine?

Is the VM and the physical machine placed in the same OU?

The only thing that comes to mind that might be unique about a Surface device is the power configuration (support for connected standby). What happens if you exclude the device from power policies?

See Surface Pro 3 Hibernation Doesnt Occur on Enterprise Install from the Ask The Core Team blog. \

Brandon
MDOP for IT Professionals on TechNet

May On Troubleshooting HTTP Streaming give you a hint.

/vkleinerde