SOLVED Unable to retrieve Policy when PXE Booting with SCCM 2012

Status
Not open for further replies.

John Mercer

Member
12
0
1
Hi

i am having trouble getting our PXE OS Deployment working correctly.
I am presented with error 0x80004005 when Trying to retrieve policy
Attached is the smsts.log from a client machine that attempted to retrieve a policy.

Can anyone help?
 

Attachments

  • smsts.log
    34.7 KB · Views: 23
Solution
Hi Prajwal,

So - where im running a seperate build network for the deployment of machines, which uses a different IP range of 192.168.14.50-192.168.14.100, which wasnt a defined boundary as that wasnt set up when i first installed SCCM, so wasnt there to be discovered.

I have manually created a boundary with an ip range of 192.168.14.50 to 192.168.14.100, and created a boundary group called 'build network' - and associated that boundary group to my distribution point. I am just about to test it.

Prajwal Desai

Forum Owner
Staff member
3,637
441
183
Is the network access account configured ?.

failed to request for client TSPxe 8/11/2017 9:19:31 AM 1396 (0x0574)
SyncTimeWithMP() failed. 80072ee7. TSPxe 8/11/2017 9:19:31 AM 1396 (0x0574)
Failed to get time information from MP: http://SCCM-AGENT01.internal.cloudpay.net. TSPxe 8/11/2017 9:19:31 AM 1396 (0x0574)


Setting the time correctly in the BIOS / firmware should resolve the issue.
 
OP
J

John Mercer

Member
12
0
1
Is the network access account configured ?.

failed to request for client TSPxe 8/11/2017 9:19:31 AM 1396 (0x0574)
SyncTimeWithMP() failed. 80072ee7. TSPxe 8/11/2017 9:19:31 AM 1396 (0x0574)
Failed to get time information from MP: http://SCCM-AGENT01.internal.cloudpay.net. TSPxe 8/11/2017 9:19:31 AM 1396 (0x0574)


Setting the time correctly in the BIOS / firmware should resolve the issue.

Hi Prajwal,

thanks for getting back to me - yes, this is an error i see and i still cannot get a client to find a task sequence when searching for policy.
I have checked the BIOS date and time on the client i am trying to image, and it appears to be the same as the Server (a virtual server, so no BIOS to set) - and i notice the timestamp on the smsts.log from the client is different than the server AND also the client's specified BIOS time/date....

please see attached

I am attaching a prestart command to the boot images that should sync the time with the SCCM server, which i am about to try.

Does it look like this is the problem to you? The date/time isnt correct even though it seems to report that it is?
 

Attachments

  • smsts.log
    34.5 KB · Views: 12
OP
J

John Mercer

Member
12
0
1
Hi Prajwal,

still have problems with this....
the basic config is as follows

a Virtual server running SCCM, with its own DHCP and DNS services
It has 2 network interfaces, one to the corporate domain, one to an isolated 'build' network. The Domain interface is on 10.14.x.x. and the build network on 192.168.x.x. DNS and DHCP service the 192.168.x.x interface to give requesting clients an IP and correctly route FQDN based requests to the 192.168.x.x build interface. As soon as you enter password on PXE boot, it tries to recieve policy, and fails after a little time. The SMSTS log on the client seems to suggest it cant find the sccm01-adv FQDN, and thusly cant download the content required - falling over. Windows Firewall is disabled, and all internal firewalls have ports open to allow traffic on the ports utilised by SCCM/its services.

Ill admit, im getting to my wits end a bit with this - i cant see where the problem lies.

Please find attached my most recent client log smsts.log

Can you help at all? Im getting a bit stuck here........
 

Attachments

  • smsts.log
    34.6 KB · Views: 5

Prajwal Desai

Forum Owner
Staff member
3,637
441
183
From the log file, i still see the same set of errors and I strongly believe this has to be an issue with time/clock. Can you boot the VM > go to bios > check if the date and time matches with that of management point ?.

unknown host (gethostbyname failed) TSPxe 8/17/2017 11:54:10 AM 572 (0x023C)
hr, HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9093) TSPxe 8/17/2017 11:54:10 AM 572 (0x023C)
sending with winhttp failed; 80072ee7 TSPxe 8/17/2017 11:54:10 AM 572 (0x023C)
End of retries TSPxe 8/17/2017 11:54:10 AM 572 (0x023C)
Send (pReply, nReplySize), HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,2034) TSPxe 8/17/2017 11:54:10 AM 572 (0x023C)
failed to send the request TSPxe 8/17/2017 11:54:10 AM 572 (0x023C)
DoRequest (sReply, true), HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,6016) TSPxe 8/17/2017 11:54:10 AM 572 (0x023C)
Failed to get client identity (80072ee7) TSPxe 8/17/2017 11:54:10 AM 572 (0x023C)
ClientIdentity.RequestClientIdentity (), HRESULT=80072ee7 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1547) TSPxe 8/17/2017 11:54:10 AM 572 (0x023C)
failed to request for client TSPxe 8/17/2017 11:54:10 AM 572 (0x023C)
SyncTimeWithMP() failed. 80072ee7. TSPxe 8/17/2017 11:54:10 AM 572 (0x023C)
Failed to get time information from MP: http://SCCM01-ADV.internal.cloudpay.net. TSPxe 8/17/2017 11:54:10 AM 572 (0x023C)
 
OP
J

John Mercer

Member
12
0
1
Can you tell me about boundary and boundary group configuration ?. Is the network access account configured ?.
Boundaries - what would you like to know? We have 20 boundaries, automatically picked up by the discovery methods - that identify the various geographic locations. 1 Boundary group, for Default-Site-First-Name..... (see pic 1 and 2)

Network access account is set to my domain account as it is domain admin (pic 3)
 

Attachments

  • boundary_group.png
    boundary_group.png
    27.2 KB · Views: 33
  • boundaries.png
    boundaries.png
    217.8 KB · Views: 32
  • NAA.png
    NAA.png
    71.8 KB · Views: 30
OP
J

John Mercer

Member
12
0
1
Hi Prajwal - turns out it was hitting the wrong gateway, directing it off in another direction. Setting the gateway correctly in DHCP allows it to find task sequences now :)

Next problem - it says it cant find the files for the configuration manager client package, even though they are distributed.....
It is the standard configuration manager client package that comes with SCCM..... i seem to have a recollection of having to change that for a different version, but i cant recall where this is or how to do it? Does this ring a bell with you?
 

Prajwal Desai

Forum Owner
Staff member
3,637
441
183
"Next problem - it says it cant find the files for the configuration manager client package, even though they are distributed" - can you post the screenshot of the error ?. Try redistributing that package to the DP's once, confirm if it has been distributed to DP.
 
OP
J

John Mercer

Member
12
0
1
"Next problem - it says it cant find the files for the configuration manager client package, even though they are distributed" - can you post the screenshot of the error ?. Try redistributing that package to the DP's once, confirm if it has been distributed to DP.

You cannot - it doesnt alloy you to distribute it again, it cant find a distribution point as its already been done - i have however selected the 'Update distribution point'

You can see from the captured image 1 that it cannot find the content for CP100001 (Configuration Manager Client) - but if you look in capture 2 - you can see its clearly marked as distributed................
 

Attachments

  • Capture.PNG
    Capture.PNG
    17.9 KB · Views: 28
  • dist status.png
    dist status.png
    63.5 KB · Views: 25

Prajwal Desai

Forum Owner
Staff member
3,637
441
183
Content location request for CP100001:2 failed. (Code 0x80040102)
hr, HRESULT=80040102 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,2757)
Failed to resolve PackageID=CP100001 TSPxe
(*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040102 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,3575)
m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::policy::TaskSequence::ResolvePolicy | TS::policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040102 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1469) TSPxe 8/17/2017 4:05:02 PM 1460 (0x05B4)
Failed to resolve selected task sequence dependencies. Code(0x80040102)
hrReturn, HRESULT=80040102 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,445)
ThreadToResolveAndExecuteTaskSequence failed. Code(0x80040102) TSPxe

The error Code 0x80040102 has a relation with boundaries, boundary groups, security devices and/or the network access account.
Can you confirm if the correct DP is associated with the boundary group ?. The PXE client is unable to resolve the package. A similar issue was resolved here - https://prajwaldesai.com/community/...sk-sequence-dependencies-code-0x80040102.733/
 
OP
J

John Mercer

Member
12
0
1
Hi Prajwal,

So - where im running a seperate build network for the deployment of machines, which uses a different IP range of 192.168.14.50-192.168.14.100, which wasnt a defined boundary as that wasnt set up when i first installed SCCM, so wasnt there to be discovered.

I have manually created a boundary with an ip range of 192.168.14.50 to 192.168.14.100, and created a boundary group called 'build network' - and associated that boundary group to my distribution point. I am just about to test it.
 
Solution
OP
J

John Mercer

Member
12
0
1
Hi Prajwal,

So - where im running a seperate build network for the deployment of machines, which uses a different IP range of 192.168.14.50-192.168.14.100, which wasnt a defined boundary as that wasnt set up when i first installed SCCM, so wasnt there to be discovered.

I have manually created a boundary with an ip range of 192.168.14.50 to 192.168.14.100, and created a boundary group called 'build network' - and associated that boundary group to my distribution point. I am just about to test it.
its working!!! :)
 
Status
Not open for further replies.