"No assigned task sequence" when using PXEboot from different subnet?

[nem]

Hi,

 

Ive been following some guides here to help me set up our existing SCCM2012 (not installed SP1 yet) for deployment (previously it only handled SCEP).

After configuring and testing deployment within the same subnet i decided to go ahead with trials in the net where most of the deployments will happen.

I configured the DHCP server with option 66 and 67 without problems but when i went to try the deployment i encountered the error.

 

The pc will PXE boot successfully but it fails after checking policy assignments.

 

SMSTS.log:

CLibSMSMessageWinHttpTransport::Send: URL: AXXE13VM.AXXE.com:80  CCM_POST /ccm_system/request	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Request was succesful.	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Decompressing reply body.	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
::DecompressBuffer(65536)	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Decompression (zlib) succeeded: original size 280, uncompressed size 672.	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Request client ID: GUID:DAA20757-CED8-470F-BF25-BAB672C4B9A4	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Response client ID: GUID:DAA20757-CED8-470F-BF25-BAB672C4B9A4	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Retrieving Policy Assignments:	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Successfully read 0 policy assignments.	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Retrieving collection variable policy.	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Found 0 collection variables.	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Retrieving machine variable policy.	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Found 0 machine variables.	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Setting machine/collection variables in the task sequencing environment.	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
Exiting TSMediaWizardControl::GetPolicy.	TSPxe	05.03.2013 11:10:56	1256 (0x04E8)
WelcomePage::OnWizardNext()	TSPxe	05.03.2013 11:10:56	1208 (0x04B8)
Loading Media Variables from "X:\sms\data\variables.dat"	TSPxe	05.03.2013 11:10:56	1208 (0x04B8)
CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,150)	TSPxe	05.03.2013 11:10:56	1208 (0x04B8)
SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\tscore\tsremovablemedia.cpp,387)	TSPxe	05.03.2013 11:10:56	1208 (0x04B8)

No assigned task sequence.	TSPxe	05.03.2013 11:10:56	1208 (0x04B8)

From what i gather here everything works as it should, but something is preventing SCCM from seeing this machine as valid for deployment hence no policy available?

I have removed and re-added the machine to the collection for which i want to run deployment thinking this might fix it.

I have double checked to see wether i got more than one computer with the same GUID.

I dont think there is anything wrong with my collections considering deployment works on subnet A (same as sccm server) but fails on subnet B ?

 

Any advice out there will be greatly appreciated. I can supply more information if needed, just let me know what you need!

 

Thanks in advance!

[nem]

Seems i didnt approve the computer in question... Is there an easy way to check if a computer is approved or not?

And i didnt have to do this for the virtual machines i used to build the deployment images.. Does it have to do with which subnet they are on? Or the fact that client type is set to "Computer" for the client i had to approve, while the two other virtual machines are set to "None"?

[Rocket Man]

If it was a default OOB install and configuration of SCCM 2012 then the setting to approve any system in a trusted domain is automatic, so there should no be reason as to why you should have to manually approve a system if it is on the same domain, regardless if it is on a different subnet, not unless you have changed this setting to not automatically approve?

 

A typical scenario where you may have to manually approve systems is with Workgroup clients as they do not get automatically approved as they are not on the trusted domain.(they are on a Workgroup)

 

 

EDIT: The affected systems on subnetB have got the site code??... regardless if they have or have not got the client installed? If not then this may be a clear indication that your boundaries for site assignment is not configured properly!