PXE Boot Solution for VDI

How to PXE boot the Zero Client in Horizon View to access the linked clones using TFTP server.
We are planning to use the old desktops as the Zero Clients. We want to boot from the PXE boot to access the non persistence linked clones or persistence disks . Is that possible to access by PXE boot.
Used Product. Horizon View 6.

No problem ... found my answer here : Is it possible to install PVM without DHCP in local network?

Similar Messages

PXE boot support for Xen PV -- OVM 3.1.1

I thought with 3.1.1 PXE boot support would be included for full PV vm install. Has someone achieved this?

No problem ... found my answer here : Is it possible to install PVM without DHCP in local network?

PXE Booting pc for Image deployment

Hi Folks,
our sccm 2012 system was working fine then all of a sudden has stopped working, when we try to image a pc using F12 we get this error message, can anyone help me out resolving this issue.
I've already uninstalled/installed pxe/wds but still getting this error, I've also create our boot images fresh but still the same.

Is this reproducible? Or is it only happening to a single machine or multiple different machines? If it is on only this machine, do what Paul states. The disk on the workstation is the issue.
-Tony

Capturing an image to use for PXE boot

I'm using Windows Deployment Services in conjunction with Windows Deployment Terminal (Windows Server 2008) to capture an image from one of our workstations to use as a PXE boot image for future computers. I've created the capture image and PXE booted
to that image, which brings up the "Image Capture" wizard. After capturing the image, I created an install image in WDS using the same .wim file. After trying to PXE boot, the workstation yet again brings up the "Image Capture" wizard.
I then right clicked the image under Boot Images (in WDS) and selected "Create Discover Boot Image." A loading window pops up, but always ends with an error saying something to the extent of the image doesn't have WDSClient Binaries. Does anyone
know what this is or how to fix this? Or even if I'm going about it the right way? If anyone has any advice, I'd appreciate it.

Hi,
Yes, you can.
Here are the rough steps:
1.
Install and configure the WDS Server.
2.
Add the Windows 7 boot image to WDS.
3.
Create a Capture Boot Image and add it to Boot Image.
4.
Create a reference Windows 7 computer (install Windows 7, Office and other applications as you like)
5.
Sysprep the Windows 7 computer.
6.
PXE boot the reference Windows 7 computer into capture image on the boot screen and then capture the image.
7.
Upload the captured image to WDS server.
8.
PXE boot clients, choose the captured image to install the system.
Please refer to this link
http://social.technet.microsoft.com/Forums/windowsserver/en-US/be3af7db-b71b-4b14-b166-fef83cde0ac6/deploy-windows-7-from-waik-with-some-application-added?forum=winserversetup
I had the similar problem couple of years back
UMESH DEUJA MCP,MCTS,MCSA,CCNA

Policy retreiving for client that is pxe booting

Wanna ask, to which management point server does a client will retrieve its policy prior to executing the TS? Does it based on the ip address boundary range?
Which logfile I can see to reoubleshoot client pxe issue? is it smspxe.log?

Short answer is: it doesn't. But we have to break down what's happening.
Remember when you PXE boot you are actually operating at Layer 2 still, and the WDS services are answering a broadcast. So no MP enters the picture before a TS runs _at_all_, instead it's the Distribution Point (which controls the WDS/PXE services
in 2012) that is connecting to the client and providing the TS.
You can actually see this happening on the SMSPXE.log (I'm going from memory on the log name, sorry if i got it wrong) in the SMS_DP$\sms\logs when the PXE servive gets the mac, matches it against the DB then provides the TS available.
Again we are basically doing this at layer 2, even though the client will eventually get an IP and use said IP to TFTP download said image...
More depth here:
http://blogs.technet.com/b/pingpawan/archive/2014/01/12/deep-dive-pxe-boot-flow-for-sccm-2007-2012.aspx
EDIT: to speculate on your question a bit: so if there are multiple DPs in the same subnet, or there is possibly IPHelper in the picture in some way ... the DP that answers is basically random unless a response delay is set (can be done on the DP in
in the MMC).

Machines cannot PXE boot using SCCM 2012 DP

There are a lot of posts about PXE boot, but I can't find the common thread to tie them all together. My test machines cannot PXE boot.
My lab environment is very simple:
10.10.0.0/24 subnet
10.10.0.10 = W2k8 R2 DC, DHCP, DNS
10.10.0.11 = SCCM2012 (on W2k8R2 with SQL Server 2008 SP3 and CU4)
All machines are Hyper-V virtual machines connecting through the same virtual network.
Setup the PXE service from DP properties. I let SCCM install WDS. WDS in Server Manager does not have a server node, but the WDS service is running. DP PXE tab is configured as follows:
"Enable PXE support for clients" is checked
"Allow this distribution point to resond to incoming PXE requests" is checked
"Enable unknown computer support" is checked
"Require a password when computers use PXE" is not checked
"User device affinity" is set to "Allow user device affinity with automatic approval"
PXE is configured to respond on all network interfaces
The PXE server response delay is 0 seconds
The DHCP server has options configured as follows:
Option 66: 10.10.0.11
Option 67: smsboot\x86\wdsnbp.com
Both DP and MP on SCCM server are configured for HTTP.
Both x86 and x64 boot images have been distributed to DP. The media was updated after PXE was enabled on the DP.
Both x86 and x64 boot images have "Deploy this image from the PXE service point" enabled on the Data Source tab of their properties.
I have tried both unknown computer task sequence and a computer import task sequence (old computer association). They all end in abortpxe.com
Complete PXE response is as follows:
=================================================================
PXE Network Boot 03.23.2009
(C) Copyright 2009 Microsoft Corporation, All Rights Reserved
CLIENT MAC ADDR: 00 DD CC BB AA 00 GUID: 532D27E3-A184-4D27-A822-30A8B6F4A39D
CLIENT IP: 10.10.0.106 MASK: 255.255.255.0 DHCP IP: 10.10.0.10
GATEWAY IP: 10.10.0.5
Download WDSNBP...
Architecture: x64
WDSNBP started using DHCP Referral.
Contacting Server: 10.10.0.11 (Gateway: 0.0.0.0)
The detalis below show the information relating to the PXE boot request for
this computer. Please provide these details to your Windows Deployment Services
Administrator so that this request can be approved.
Pending Request ID: 6
Contacting Server: 10.10.0.11
TFTP Download: smsboot\x64\abortpxe.com
PXE Boot aborted. Booting to next device
===========================================================
From the smspxe.log:
]LOG]!><time="16:31:39.445+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6402">
<![LOG[Client Identity: {C9929C4D-735A-4973-8659-4D3D5D5E4F92}]LOG]!><time="16:31:39.445+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6428">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:31:39.480+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:31:39.505+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:31:39.505+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:31:39.533+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:31:39.553+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:32:00.963+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:01.008+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:01.027+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.027+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.084+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="16:32:01.108+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6402">
<![LOG[Client Identity: {C9929C4D-735A-4973-8659-4D3D5D5E4F92}]LOG]!><time="16:32:01.108+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6428">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:01.151+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:01.174+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.174+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.209+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:32:05.230+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:05.290+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:05.325+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:05.325+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:05.366+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
=============================================================================================
I've been hammering this for about 10 hours now (or to be honest, it's been hammering me) and it must be something very simple I'm missing. I have a feeling that I'm doing something I used to do in 2007 and whatever that is, it does not work in
2012.
If I connect using boot media, Task Sequences execute perfectly.
TIA,
Tom

Option 66: 10.10.0.11
Option 67: smsboot\x86\wdsnbp.com
Pending Request ID: 6
Contacting Server: 10.10.0.11
TFTP Download: smsboot\x64\abortpxe.com
PXE Boot aborted. Booting to next device
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
Those options are fine when using DHCP options. They must be configured right because ConfigMgr does send a reply to the client ("abortpxe"). It basically tells you that ConfigMgr knows the MAC address and/or SMBIOSGUID of the client, but cannot find
a deployment for it.
Just find ResourceID 16777218 in the console (you might have to add the ResourceID column) and double check if there's an deployment available (properties of the client with resourceID 16777218).
Torsten Meringer | http://www.mssccmfaq.de
Your answer really helped me. I was searching for 2 days trying to find a computer in Config Manager. Your suggestion to "Just
find ResourceID 16777218 in the console (you might have to add the ResourceID column) and double check if there" was the trick to finding the computer in Config Manager. Thanks for all of your help
Gregory Campbell System Administrator

OSD to Surface fails to PXE Boot and returns PXEGetPXEData Failed with 0x80004005

Scenario: When trying to Image Windows 8.1 to a Surface Pro, Surface Pro 2 and Surface Pro 3 I have downloaded the latest Surface Firmware and Drivers (August 18th 2014 I believe), the NIC's are in the x64 PXE Boot Image. I have verified that no DHCP Option
67 is set, and that SpanningTree PortFast is enabled. All other Images function correctly, Windows 7 Sp1 works. We use the Microsoft USB NIC, and we PXE boot and download the PXE Image fine, then it comes into windows and goes to detect the NIC, at which point
it fails and reboots.
The Surface has had Firmware update on it to the latest.
It appears the NIC just stops working, which makes me think that the latest Driver pack for Surface does not contain the PXE boot versions for their NIC.
Trying the Docking Station (which utilizes NIC ASIX AX888772) exhibits the same problem.
The NIC stays active until the OSD Screen comes up, it fails trying to load the Surface NIC though (or the NICs in the Driver pack they just released do not include a PXE Boot Driver...the Drivers once imported do not show any as being Boot Critical...which
make me think this is the case even more so.
Doing a USB PXE Boot also fails to load the NIC.
Going to F8 and doing IPCONFIG /RENEW verifies the NIC is not active.
I see tons of postings on the Surface being a nightmare to image.
Errors:
Failed to Download pxe variable file. Code (0x0000001)
PXEGetPXEData Failed with 0x80004005
Anybody having any other experiences out there, or have anything else they could think to try?
David Baur

(or the NICs in the Driver pack they just released do not include a PXE Boot Driver...the Drivers once imported do not show any as being Boot Critical...which make me think this is the case even more so.
There are no "PXE boot versions" of drivers at all. What you described just indicates that there is no driver in winpe that matches the hardware. WinPe is based on the respective version of the full os so you have to add Win8.x drivers to the boot image.
The architecture also has to match. Have you added NIC drivers to the boot image at all?
NIC drivers are never boot critical if I am not mistaken.
Torsten Meringer | http://www.mssccmfaq.de

Yoga 13 - Compatible USB to ethernet devices for PXE booting

Hi there,
I've recently been looking for a means to pxe boot the lenovo yoga 13 to enable me to then image it. After reading that pxe booting is possible I went out and bought a StarTech usb to ethernet adaptor (USB21000S2) but have had no luck so far.. In other postsI've read that pxe booting is only supported if using the official lenovo usb to ethernet adaptor. We're using FOG as our imaging solution (if thats of any use)
Please can someone confirm if only the official adaptor is supported.
Regards
Simon

Were you able to find any? I am also very interested in finding one. I just ordered one of these the lenovo 0A36322 to see if it will work, but it is only 100mb and not sure if it will work or not.

PXE Boot/Ip helper address for staging OS-es

Hi,
In our production environment there is already a PXE-server SCCM 2007. Now, we're setting up an SCCM 2012-server which we would like to test staging/OS-deployment also.
Is it safe to say we need to add the ip of the SCCM 2012 "066 Boot Server Host Name" to stage. Note: on switches (Cisco) this is ip helper address, correct?
Please clarify.
NOTE: is there an option to make it work WITHOUT needing a new VLAN?
J.
Jan Hoedt

DHCP options and IP helper addresses have the same end goal but are completely different things.
IP Helpers automatically forward broadcast requests to a destination system thus "bridging" subnets for services like DHCP and PXE.
DHCP scope options directly instruct the NIC to boot from a specific PXE server.
So, yes, it is possible to manipulate where a client PXE boots from, but it takes an integral understanding of how PXE works, of how IP Helpers work, and of how NICs initiate a PXE boot when either IP Helpers or DHCP scope options are in place (and
thus DHCP also). Because *none* of this really has anything to do with ConfigMgr or even Microsoft itself, there really is no Microsoft guidance except that IP Helpers are preferred and are the Microsoft supported solution. A great starting reference
is at http://en.wikipedia.org/wiki/Preboot_Execution_Environment
Jason | http://blog.configmgrftw.com
Is there any official Microsoft documentation that outlines why IP Helpers are preferred over scope options?

Server 2008 configured for PXE boot with UIU and GhostCast

Right now, I am in the process of switching over from UIU 4, to UIU 5, and the implementation is completely different. We used GhostCast to push images out before, but the new UIU uses WIM files to pull the drivers off the server. I had a few
questions about reconfiguring the new server.
Currently, we have a server 2003 machine running ghost cast. It pulls its images off of a server 2008 machine. The server 2008 machine can be accessed remotely. So my first question is, can this be configured to allow remote connections
with the new setup?
The things I have been reading have said that you need to enable DNS, AD, and DHCP, however if we connect this to a WAN, will it conflict with that? Or can we configure only one of the ethernet ports to see this? Sorry kind of new to this.
I guess my main concern is, can we set up a separate domain for GhostCasting, while still being connected to an external domain?

Hi,
I’m not sure what you really want to do. For PXE boot, I think DHCP is always required just like Microsoft deployment solution WDS and MDT.
The two products are third products, so I don’t know the detail information about how they work. Based on my experience, they should be based on broadcast or multicast.
If so it could be a bad idea if you install it on a server facing the internet.
I think you can also ask in the third party forums that provide the products.
Thanks for understanding.

The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed. WDS not PXE booting!

This morning came in to find clients were not getting there bootfiles through PXE. I checked the logs to find the following events related to WDS.
The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed
The Open Procedure for service "WDSServer" in DLL "C:\Windows\system32\wdssrv.dll" failed
The Open Procedure for service "WDSMC" in DLL "C:\Windows\system32\wdsmc.dll" failed
Has anyone seen this or have a link to a resolution?
tconners

Hotfix loaded but didn't help.
Found a few articles referring to rebuilding the perf counter library. I ran "lodctr /R" failed first time then worked the second time. I believe the errors:
The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed
The Open Procedure for service "WDSServer" in DLL "C:\Windows\system32\wdssrv.dll" failed
The Open Procedure for service "WDSMC" in DLL "C:\Windows\system32\wdsmc.dll" failed
Are gone but PXE boot still fails.
Do you think I might have to uninstall WDS and reinstall? "Using SCCM console to just remove PXE"
tconners

M having a macbook, after successful shut down it is booting up automatically is there any solution for this?

M having a macbook, after every successful shut down it is booting up automatically. Is there any solution for this?

There isn't a separate app icon for Facetime for the iPhone like there is for the iPad and iPod Touch. Facetime is built into the iPhone's iOS.
Here a refresher on how it works:
iOS: Using Facetime, http://support.apple.com/kb/ht4319

Looing for PXE-Boot option on T430s

Hello
I am in the process of testing a Thinkpad T430s to possibly do a mass purchase for our company. We use SCCM
to manage imaging, patching / updates etc. I am trying to PXE boot but but I am getting an error which may have to do with
SCCM but as an extra measure I am trying to locate PXE Boot option in the BIOS but can't seem to find anything.
ANy suggestions would be appreciated

do you see Wake On Lan and/or Ethernet LAN Option ROM on the Network menu under the Config tab in your BIOS.
apologies if you don't. all i've got to check is my X220 in front of me, at the moment.
regards.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
PM requests for individual support are not answered. If a post solves your issue, please mark it so.
X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
I am not a Lenovo employee.

Thin Client IP phones for VDI solution

Is it possible to have a Cisco IP phone to act as a thin Client for VDI solution?
Can anybody suiggest me

Hello Sivakalam2
You ask an excellent question, and one that will likely trigger a heated discussion. I've had interest in the same topic for several years, and surprisingly found very little online. Everyone makes a thick client. WebRTC is a development project which is making inroads toward thin client softphone functionality. It's an excellent concept, but I haven't seen a production-ready client, yet. (Not saying there aren't any; I just have not seen them.)
Then I came upon this info in the Cisco Unified Communications System 9.0 SRND:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/9x/collabor.html
Cisco Virtualization Experience Client Architecture
Cisco Virtualization Experience Client (VXC) endpoints enable the end users to have secure real-time access to content and business applications as well as a rich collaborative user experience. These endpoints provide access to collaboration services that are part of the larger Cisco Virtualization Experience Infrastructure (VXI) solution. For information on a complete end-to-end VXI solution design, refer to the documentation available at
http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns1100/landing_vxi.html
Deploying Cisco Virtualization Experience Clients
Cisco Virtualization Experience Clients (VXC) are endpoints in the Cisco Unified Communications portfolio; however, they are more than just simple endpoints because they interact with a user's working environment by providing voice, video, and virtual desktop capability and functionality. A user's work environment can assume various profiles (for example, task worker, knowledge worker, or mobile worker), and Cisco has various Virtualization Experience Clients to meet those different needs.
The Cisco VXC 2111 and VXC 2112 provide an integrated form factor that is paired with a Cisco Unified IP Phone 8961, 9951, or 9971 for a fully integrated voice, video, and virtual desktop environment. The Cisco VXC 2211 and VXC 2212 provide a standalone form factor that can be used as simply a virtual desktop (for a task worker), or they can be paired with an IP phone for a fully integrated user environment. The Cisco VXC 4000 provides a software-only solution by using a re-purposed PC to provide the user with voice and virtual desktop functionality, while the Cisco VXC 6215 provides a Linux-based thin client for fully integrated voice, video, and virtual desktop in a single device.
I do not have direct experience with these clients yet, having upgraded to CUCM9 recently. I'm definitely going to research it now. There's much more info in the SRND link above to read.
Thanks
TZ

OSD: pxe boot fails with "failed to get infromation for MP:/"

Hi,
We face an issue on pxe boot. It boots into pxe then tries to apply network settings but then reboots.
Ipconfig is ok, smsts.log says "failed to get information for MP:/oursccmserver.
Troubleshooting:
*PXE is working fine when client as well as sccm-server are in same subnet, it fails when in different subnets.
*Firewall is fully opened, no connections blocked.
*Ping to sccm-server works fine on dns
Please advise.
J.
smsts.log:
Missing root CA environment variable from variables file   TSPxe   26/03/2014 16:37:11   288 (0x0120)
Support Unknown Machines: 0   TSPxe   26/03/2014 16:37:11   288 (0x0120)
Custom hook from X:\\TSConfig.INI is    TSPxe   26/03/2014 16:37:11   288 (0x0120)
No hook is found to be executed before downloading policy   TSPxe   26/03/2014 16:37:11   288 (0x0120)
Authenticator from the environment is empty.   TSPxe   26/03/2014 16:37:11   288 (0x0120)
Need to create Authenticator Info using PFX   TSPxe   26/03/2014 16:37:11   288 (0x0120)
Initialized CStringStream object with string: {40AB3050-A926-4BA5-9D17-7423F93CBCD5};2014-03-27T00:37:11Z.   TSPxe   26/03/2014 16:37:11   288 (0x0120)
Set media certificate in transport   TSPxe   26/03/2014 16:37:11   288 (0x0120)
Set authenticator in transport   TSPxe   26/03/2014 16:37:11   288 (0x0120)
CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.ourcompany.com:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA   TSPxe   26/03/2014 16:37:11   288 (0x0120)
[TSMESSAGING] AsyncCallback(): -----------------------------------------------------------------   TSPxe   26/03/2014 16:37:11   288 (0x0120)
[TSMESSAGING] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered   TSPxe   26/03/2014 16:37:11   288 (0x0120)
[TSMESSAGING]                : dwStatusInformationLength is 4
   TSPxe   26/03/2014 16:37:11   288 (0x0120)
[TSMESSAGING]                : *lpvStatusInformation is 0x8
   TSPxe   26/03/2014 16:37:11   288 (0x0120)
[TSMESSAGING]            : WINHTTP_CALLBACK_STATUS_FLAG_INVALID_CA is set
   TSPxe   26/03/2014 16:37:11   288 (0x0120)
[TSMESSAGING] AsyncCallback(): -----------------------------------------------------------------   TSPxe   26/03/2014 16:37:11   288 (0x0120)
WinHttpReceiveResponse (hRequest, NULL), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8927)   TSPxe   26/03/2014 16:37:11   288 (0x0120)
failed to receive response with winhttp; 80072f8f   TSPxe   26/03/2014 16:37:11   288 (0x0120)
m_pHttpTransport->Send (0, 0, pServerReply, nReplySize), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5159)   TSPxe   26/03/2014 16:37:11   288 (0x0120)
MPKeyInformation.RequestMPKeyInformationForMedia(szTrustedRootKey), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9410)   TSPxe   26/03/2014 16:37:11   288 (0x0120)
Failed to get information for MP: http://oursccmserver.ourcompany.com. 80072f8f.   TSPxe   26/03/2014 16:37:11   288 (0x0120)
Jan Hoedt

Hi,
Have you check Mpcontrol.log on the MP server and Smspxe.log?
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

PXE Boot Solution for VDI

Similar Messages

Maybe you are looking for