The requested software cannot be located problem in sccm 2007

try refreshing the distribution point for the software, also check your boundaries and make sure that the machine requesting the software is within the distribution point boundary, otherwise make sure your advertisement allows it to fall back to unprotected distribution points.  Also make sure that to see if this is set to download before running, if you have set it to download before running, try making it run from DP and see if that works.

Thanks for the quick answer can u please provide me with soome guide on this boundaries story how do i define the boundaries and how do i make sure the target machien is in the boundry.

2- i tried to make it run from DP to no avail. Where can im go from. Here?

Does the package status show that is has successfully been targeted and installed to the distribution point?  Have you checked the log files under c:\windows\system32\ccm\logs?  try zip those up on an affected machine and post them here.  maybe zip up the distribution points logs files as well which should be under their program files install location for the site system files.

I would be careful about amending the settings on a Site System that is not yours to control.  If your role is package deployment, then I would get the other SCCM administrator to make any changes.

actually yes the status shows it has been succesfully transfered i have seen the tiles myself on the distribution point server.

2 attached are the logs of the affected machien.\

3- the SCCM is installed on a server and the the distribution point is on a diffrent server so would u please kindly let me know which logs do u need exactly and wher i can find them? logs-accefted-machien.zip

Have you tried manually uninstalling and reinstalling the client on this machine to ensure its WMI is not corrupt?

no i havent the problem is i dont know that much about SCCm and yet i have to solve alot of problems within it, so i would really appriciate knwoing how to uninstall the cleint or at least where can i find the client software again.

LocationServices.log is saying this:

LSGetGPSiteCode: Failed to Get Site Code from Group Policy Reg key [Software\Microsoft\SMS\Mobile Client] (80070002)      LocationServices      03/01/2012 13:54:30      6196 (0x1834)
ProcessPendingSiteAssignment      LocationServices      03/01/2012 13:54:30      6196 (0x1834)
LSGetAutoAssignFlagFromWMI      LocationServices      03/01/2012 13:54:30      6196 (0x1834)
Executing Task LSRefreshLocationsTask      LocationServices      03/01/2012 13:54:30      6196 (0x1834)
LSSendLocationRequests      LocationServices      03/01/2012 13:54:30      6196 (0x1834)
LSGetHomeMPFromWMI      LocationServices      03/01/2012 13:56:14      5376 (0x1500)
LSGetSiteCodeFromWMI      LocationServices      03/01/2012 13:56:14      1848 (0x0738)
LSGetSiteCodeFromWMI : Site code returned from WMI is <100>      LocationServices      03/01/2012 13:56:14      1848 (0x0738)


That tells me the group policy you are using to apply the site code is not being read and so its attempting to query WMI instead.  Its not recommended to user Group Policy for Site code assignments at all.  It can be an absolute headache to troubleshoot and if you move machines between boundaries without makign sure the correct policy is appying, it will not pick up the correct site code.  You also cannot remove the Group Policy assignment without scripting or manually hacking the registry to remove those policy keys.  Hence why i wouldnt suggest it at all.

so what do u suggest now as a soultion for this issue, how can i get the system back on its feat?

i dont get it site 100 is supposed to be the right site.though autodetect in the client returns site 02. i dont know honesty why would it behave like that, any help will be much appriciated though.

Can i assume the content its requesting is the CD burner software?

yes. it is a cd burning software.
but this is just the software im testting with the entire SCCM infrastructure is behaving like that i cant publish any software anywhere.

your CAS.log is trying to talk to :
HTTPPost(URL='http://VM0015.SCHELDE.COM/ccm_system/request'): Failed with code 0x80040231.

but your client location log is showing that your management point is:
Current Management Point is VM0047.SCHELDE.COM with version 6487

Does site code 100 belong to VM0047?

Has this machine recently moved locations?

either in AD to pick up new group policies, or physically around different VLans?

Does site code 100 belong to VM0047?
how can i check that? im sorry the questions are noob i know but well im sitll learning

+ like i said this is not th eonly machien suffering from the problem this is just the test machien.
but every machien is exaclty the same when it comes to this prolem i cant publish to any machien in the company.

i cant make so much of it, hopefully you will be able to give ms some guidance on how to get this system to work.

and i have just recieved confirmation the system hasnt been moved in the network, nothing has left its place.

ok are you the only SCCM administrator having to pick up this system?
If so, I will then talk you through all the settings you should check but with your limited knowledge its risky and is going to take time.

Firstly I'm going to get a better idea of your environment.
How many Primary servers do you have including your Central server?
How many Secondary servers do you have?
How many Distribution points do you have?

Are all these servers and all the machines they support in the same office or are they in multiple offices?
Do you manage the AD infrustructure as well or have access to check group policies?
Is this the only package that wont deploy or do all packages fail for all machines?

In your SCCM console, do you add packages to your central site and then distribute them down to all your primary, secondary & distribution points?

If you do, you should be able to see a listing of the site codes for each site (DP).
Also you can see what the server name is for each site code by looking under the Central Site Database under Site Management, and then under each site listed, expand Site Settings then Site Systems to get the names of the servers and their roles (i.e. management points and distribution points)

Dear sir.
1-we have three sites one main server in the headquarters and two secondary sites in other buldings connected through site to site High speed connections. the sites are nombered 100 101 and 102

2- each site has its own distribution point.

3- the primary site has three servers and the two secondary sites each has one server.

4- each and every package we create gets copied to all three distribution points.

5- how we create the packages is in the relatively standard way,
we creat a package and connect it to a collection and an advertisment and then we assign computers to it when we want to publish it to certain computers, this is the short version of the story.

your CAS.log is trying to talk to :
HTTPPost(URL='http://VM0015.SCHELDE.COM/ccm_system/request'): Failed with code 0x80040231.

but your client location log is showing that your management point is:
Current Management Point is VM0047.SCHELDE.COM with version 6487

Does site code 100 belong to VM0047?

as an answer to that question.

server  0047 is a part of site 100 indeed site 100 has three servers in it vm0046 ,47 and  48 the distribution point is on server vm0048.

the managment point is on server 0047 though.

so what what server names does 102 belong to?  is it vm0015?

negative site 102 is a secodary site with server name vm0051 not vm0015

well its worth to mention that this server vm0015 is not in our system anymore.

ok well its trying to talk to the IIS services on vm0015.  was that server decommissioned properly?  i.e. all sccm roles and services removed, and ensured that the primary server no longer communicated with it before decommissioning it?

i gathered the needed information about what vm0015 was from the network admin.
the VM0015 was a standalone SCCM server that ran for a year or something and then they made the new system with all its servers and they ran side by side and then they decommisioned the old one and it wasnt well decomissioned they just took it offline.
and i have no possibility of restoring it or renabling it.

hopefully there could be a resolution for this issue

ok so you are saying that the machines you are trying to deploy the package to are registered under site code 102?  

For site database 100, under site management, then 102-vm051, then Site Settings, Boundaries

What boundaries do you see there?

Also, tell me what your group policy that is applying to those machines has set for SCCM site settings, eg site code.

no im truying to deploy a package that is under 100 that is where it its attached i guess.

there also is another problem i removed the configuration client from the test machien and im truying to install it again and itsnot working

here is the log

<![LOG[==========[ ccmsetup started in process 2264 ]==========]LOG]!><time="12:54:54.053+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:9010">
<![LOG[Version: 4.0.6487.2000]LOG]!><time="12:54:54.053+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:2068">
<![LOG[GetAdaptersAddressess entry point is supported.]LOG]!><time="12:54:54.053+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmiputil.cpp:118">
<![LOG[DhcpGetOriginalSubnetMask entry point is supported.]LOG]!><time="12:54:54.053+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmiputil.cpp:181">
<![LOG[Adapter {84BC232D-27D0-481C-A215-863BBD1A398B} is DHCP enabled. Checking quarantine status.]LOG]!><time="12:54:54.053+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmiputil.cpp:509">
<![LOG[Current AD site of machine is NL-Vlissingen-Stad]LOG]!><time="12:54:54.068+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="lsad.cpp:457">
<![LOG[Attempting to query AD for assigned site code]LOG]!><time="12:54:54.068+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="lsad.cpp:1766">
<![LOG[Executing query (&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=2886819077)(MSSMSRangedIPHigh>=2886819077))))]LOG]!><time="12:54:54.100+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="lsad.cpp:1801">
<![LOG[Executing query (&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=172.17.93.0)(mSSMSRoamingBoundaries=NL-Vlissingen-Stad)))]LOG]!><time="12:54:54.100+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="lsad.cpp:1862">
<![LOG[This client might be within the boundaries of more than one site - AD SiteCode search matched 2 entries]LOG]!><time="12:54:54.209+-60" date="01-04-2012" component="ccmsetup" context="" type="2" thread="2144" file="lsad.cpp:1915">
<![LOG[The client will be assigned to the first valid site]LOG]!><time="12:54:54.209+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="lsad.cpp:1916">
<![LOG[LSGetAssignedSiteFromAD : Trying to Assign to the Site <002>]LOG]!><time="12:54:54.209+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="lsad.cpp:1922">
<![LOG[The MP name retrieved is 'VM0015.SCHELDE.COM' with version '6487l' and capabilities '<Capabilities SchemaVersion="1.0">
</Capabilities>']LOG]!><time="12:54:54.209+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="lsad.cpp:2869">
<![LOG[Retrieving client operational settings from AD.]LOG]!><time="12:54:54.209+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="lsad.cpp:4931">
<![LOG[ClientOperationalSettings search filter is '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=002))']LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="lsad.cpp:4673">
<![LOG[Command line: "\\vm0047\SMS_100\Client\ccmsetup.exe" ]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:4102">
<![LOG[CCMHTTPPORT:    80]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:8008">
<![LOG[CCMHTTPSPORT:    443]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:8023">
<![LOG[CCMHTTPSSTATE:    0]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:8041">
<![LOG[CCMHTTPSCERTNAME:    ]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:8069">
<![LOG[FSP:    VM0015.SCHELDE.COM]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:8084">
<![LOG[CCMFIRSTCERT:    0]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:8126">
<![LOG[Config file:      ]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:4497">
<![LOG[Retry time:       10 minute(s)]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:4498">
<![LOG[MSI log file:     ]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:4499">
<![LOG[MSI properties:   SMSSITECODE=002 CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="VM0015.SCHELDE.COM" CCMFIRSTCERT="0"]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:4500">
<![LOG[Source List:]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:4508">
<![LOG[MPs:]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:4527">
<![LOG[                  VM0015.SCHELDE.COM]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:4542">
<![LOG[Updated security on object C:\WINDOWS\ccmsetup\.]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmsetup.cpp:8849">
<![LOG[Sending Fallback Status Point message, STATEID='100'.]LOG]!><time="12:54:54.224+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:9326">
<![LOG[sending with winhttp failed; 80072ee7]LOG]!><time="12:54:54.256+-60" date="01-04-2012" component="FSPStateMessage" context="" type="3" thread="2144" file="fsputillib.cpp:1253">
<![LOG[Downloading file \\vm0047\SMS_100\Client\ccmsetup.exe]LOG]!><time="12:54:55.270+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:5162">
<![LOG[Downloading \\vm0047\SMS_100\Client\ccmsetup.exe to C:\WINDOWS\ccmsetup\ccmsetup.exe]LOG]!><time="12:54:55.270+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:5259">
<![LOG[File download 10% complete (61440 of 611168 bytes).]LOG]!><time="12:54:55.270+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmsetup.cpp:8694">
<![LOG[File download 20% complete (122880 of 611168 bytes).]LOG]!><time="12:54:55.270+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmsetup.cpp:8694">
<![LOG[File download 30% complete (184320 of 611168 bytes).]LOG]!><time="12:54:55.270+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmsetup.cpp:8694">
<![LOG[File download 40% complete (245760 of 611168 bytes).]LOG]!><time="12:54:55.270+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmsetup.cpp:8694">
<![LOG[File download 50% complete (307200 of 611168 bytes).]LOG]!><time="12:54:55.270+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmsetup.cpp:8694">
<![LOG[File download 60% complete (368640 of 611168 bytes).]LOG]!><time="12:54:55.270+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmsetup.cpp:8694">
<![LOG[File download 70% complete (430080 of 611168 bytes).]LOG]!><time="12:54:55.270+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmsetup.cpp:8694">
<![LOG[File download 80% complete (491520 of 611168 bytes).]LOG]!><time="12:54:55.270+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmsetup.cpp:8694">
<![LOG[File download 90% complete (552960 of 611168 bytes).]LOG]!><time="12:54:55.270+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmsetup.cpp:8694">
<![LOG[File download 100% complete (611168 of 611168 bytes).]LOG]!><time="12:54:55.285+-60" date="01-04-2012" component="ccmsetup" context="" type="0" thread="2144" file="ccmsetup.cpp:8694">
<![LOG[Download complete.]LOG]!><time="12:54:55.285+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:5337">
<![LOG[Running as user "kiwan01"]LOG]!><time="12:54:55.285+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:2690">
<![LOG[Detected 107831 MB free disk space on system drive.]LOG]!><time="12:54:55.285+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:463">
<![LOG[DetectWindowsEmbeddedFBWF() Detecting OS Version]LOG]!><time="12:54:55.285+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:509">
<![LOG[Client OS Version is 6.1, Service Pack Version 1]LOG]!><time="12:54:55.285+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:533">
<![LOG[Client OS is not a supported Windows Embedded Platform]LOG]!><time="12:54:55.285+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:535">
<![LOG[Successfully ran BITS check.]LOG]!><time="12:54:55.301+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:7105">
<![LOG[Failed to send HTTP request. (Error at WinHttpSendRequest: 12007)]LOG]!><time="12:54:55.301+-60" date="01-04-2012" component="ccmsetup" context="" type="2" thread="2144" file="ccmsetup.cpp:5901">
<![LOG[DownloadFileByWinHTTP encountered an unrecoverable error.]LOG]!><time="12:54:55.301+-60" date="01-04-2012" component="ccmsetup" context="" type="3" thread="2144" file="ccmsetup.cpp:5948">
<![LOG[Sending Fallback Status Point message, STATEID='308'.]LOG]!><time="12:54:55.301+-60" date="01-04-2012" component="ccmsetup" context="" type="1" thread="2144" file="ccmsetup.cpp:9326">
<![LOG[sending with winhttp failed; 80072ee7]LOG]!><time="12:54:55.301+-60" date="01-04-2012" component="FSPStateMessage" context="" type="3" thread="2144" file="fsputillib.cpp:1253">

it keeps refering to the vm0015 which does not even exist, how can i correct this 0015 issue as apparently this is main caus eof all evil now, 0015 has to be replaced with 0047

is your advertisement set to fallback to unprotected distribution points?  if its ticked to fallback, then make sure your package is distributed to your primary site which remains unprotected.

Perhaps removing the decommissioned from the roles would remove the entries from the db.
This has to be done at a minimum. All the servers as DP, MP etc should be online.

You can check the errors/alerts on the bottom side of the SCCM console.

I find it so hard to understand why a company with a 3 site infrastructure is running without a fulltime SCCM admin.

the only way to remove vm0015 as a site database would be to use SQL queries on your SQL database to remove it and if you get it wrong, you can mess up your entire infrastructure.

In AD, under the System\System Management containers, you will see the site code 002 listed there.  Delete those entries.  Also make sure you have no DNS cached entries for that either.

Next check your boundaries in site 100 and make sure that you remove any boundaries for site 002.  If it will not let you delete the boundaries (because generally they are created on 002 and passed up to 100) then you will need to run SQL commands on the database to remove any boundaries for site 002.

the package is on the primary point of the primary site. and the omputer im truying ti publish to is also on the primary site.within the boundaries of the primary site.

when you try push out the client from 100-vm047 this is what i'm seeing:

<![LOG[Current AD site of machine is NL-Vlissingen-Stad]LOG]!>
<![LOG[Attempting to query AD for assigned site code]LOG]!>
<![LOG[Executing query (&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=2886819077)(MSSMSRangedIPHigh>=2886819077))))]LOG]!>
<![LOG[Executing query (&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=172.17.93.0)(mSSMSRoamingBoundaries=NL-Vlissingen-Stad)))]LOG]!>
<![LOG[This client might be within the boundaries of more than one site - AD SiteCode search matched 2 entries]LOG]!>
<![LOG[The client will be assigned to the first valid site]LOG]!>
<![LOG[LSGetAssignedSiteFromAD : Trying to Assign to the Site <002>]LOG]!>
<![LOG[The MP name retrieved is 'VM0015.SCHELDE.COM' with version '6487l' and capabilities '<Capabilities SchemaVersion="1.0">
</Capabilities>']LOG]!>
<![LOG[Retrieving client operational settings from AD.]LOG]!>
<![LOG[ClientOperationalSettings search filter is '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=002))']LOG]!>


so this tells me 2 things:
1) you still have SLP information for vm0015 - 002 in AD sitting under System\System Management container.   Remove this data and also any DNS entries that match.
2) you have Group Policies applying to this machine to tell it what site to communicate with.  So remove the GPO you have that is applying SCCM setttings.  you shouldnt need to use GPO's as long as you use boundaries.  when you're using boundaries, it will talk to the management point within its own boundary and pick up necessary settings from it.

once you have removed the SCCM policies from Group Policy, you will need to delete certain keys on the local machine to remove the policy entirely as it doesnt delete the policy settings even when you remove the GPO.  this is why you were getting this other error in LocationServices.log
LSGetGPSiteCode: Failed to Get Site Code from Group Policy Reg key [Software\Microsoft\SMS\Mobile Client] (80070002)

So remove the client from the machine, remove the policies, remove the left over SLP and DNS settings for vm0015-002 then delete this key in the registry:
"HKLM\Software\Microsoft\SMS\Mobile Client\"

i have followed all your advice points and i actually can see a diffrence in the system some stuff actually started to work

2- I ran GPresult on the system i found its affected by two GPos. i inspected them but i dont seeom to be able to find where the rules that govern the sccm agent might be, can u actually point me where to look.?

actually if you dont mind i would like to go through all the settings of the SCCM envirnment with you to make sure its operating in optimum and ultimate capacity. as this is now my major concern as a new network administrator in this company

I'm glad things are starting to get better now :)
lets focus this question on the original request and you can open a new question for the health of your SCCM infrustructure for us to go through each point, that way people benefit from a search for health and dont get confused on this post with all the added extras.

So now when you deploy your client to your machine, is it picking up the correct site code?  Are you now able to deploy the software package in question?

Yes it actually did.
though there are wiered things happening.

1- i tried to deploy software to machiens and it worked perfectly,
2- i tried to deploy OS images via task sequences it works normally well but on three of the test computers the system skips the computer name promt and installs automatically.

Were all these machines in SCCM already and listed as having a client, being assigned and not obsolete?

If not, then your unknown collection is holding the variable for the computername, but your other collections dont have it and it will then just pick up the existing name of the machine.

The ones that built without the prompt, were they named as MININT-****?

those three systems has been once a mmber of SCCM and has bene decommisioned im using them now for the tests.
but only these three are skipping the computer name option.
i also checked the unknown computer collection and found nothing in it.

the thing is someone deleted these computer accounts from sccm so, they dont exist anymore, they just get the name automatically and continue the os deployment

the three computer accounts at question are also not in AD

you wont see machines listed in the Unknown computer collection.  It is used mainly for building unknown machine accounts.

right click the unknown collection and choose Modify Collection Settings
Then go to the Collection Variables tab
If you do not see the OSDComputerName variable listed there, press the Star button and type in
OSDComputerName
untick the option to not display it as its not necessary to hide an empty variable.

For known computers in SCCM, its probably picking up this variable from one of your other collections like All Systems.

i dont understand your last coment clearly sir.
i created the requested variable in all unkown systems
in the name i typed OSDComputerName unticked do not display and left the value empty and clicked ok but still i dont see anything in it

I am a woman ;)

You wont see anything in it, but what you will notice is this:

The machines you built that were not in AD or in SCCM, will now recieve the OSDComputerName prompt while building machines.  So to test this, delete one of the new machines you built from SCCM and try building it again.  As long as SCCM has no object for that machine in its All Systems collection, it becomes an Unknown machine to SCCM and therefore will receive that variable prompt when building.

aha thanks madam,
ill try this .. but it is correct to leave the value empty for this one. right?

yes because you want the ability to fill in the value of the computer name.  if you dont leave it blank and instead put a computer name in it, then it wont prompt you to fill it in at build time and will always use the value you entered into that variable on that collection.

well i have done that variable thing but then i got the machien got the name OSDComputerName and that is not the name that we want to give the machien we want to be able to choose the name ourselves

that is correct, what you need to do is double click the actual word OSDComputerName and it will bring up a prompt for you to type in the machine name.

there is an alternative method you can use as well.

You can use Computer Association to pre-populate a collection with machine names and their MAC addreses.  

You create a new collection (or possibly you already have one setup for this) and assign your relevant Task Sequences to it.
Then under the Operating System node, right click Computer Association and choose Import Computer Information.  
Select Import a single computer and press next.
Type in the Computer Name and the MAC address of the machine you want to build and press next.  (you dont have to fill in the other information unless you know you have duplicate MAC addresses on your network)  Press Next again on the next confirmation screen.
Then Select to add the computer to the following collection and choose the collection you have setup for this process and press next, next and close.

Then go to that collection and make sure you can see the object listed there.  if not, just right click the collection and choose refresh.

Now when you try build that machine, it knows it and will give it the name you gave it as long as you dont have OSDComputerName variable on that collection.   When you have that variable on a collection, no matter if SCCM knows what its called, you will HAVE to fill it in each time you build a machine otherwise it remains a blank variable and SCCM will build the machine with a default MININT-**** name.  So its really only advisable to put that variable on the Unknown Computer collection.

welll
here is the trick none of the above has worked,
these systems that i have mentioned didnt display even display the OSD computername.
other systems asked for the name twice like expected
1st with OSD computername and the other viA THE VB SCRIPTin the task sequence

i tried the reports to search for the mac adress of the machien but returned no result.

i seriously have no clue.. its not showing in the reports. as a mac adress, can i look for GUID values then?

i tried clearing the last PXE image. flushed the DNS cache of the deployment server to no avail., and only these three systems are insisting to behave that wiered.

you're misunderstanding the point.

Computer Assocation is for unknown machines.  You cannot report off an unknown as its object doesnt exist in SCCM.  So boot up the machine, get its MAC address, then do the computer association to add it to a collection (try the collection that your Task Seqeunce is assigned to).  

So, to ensure that one of these 3 systems is definitely an unknown, make sure it has no AD computer object so that any AD discovery scans are not bringing it back into SCCM, update and then refresh the All Systems collection and ensure the object is not listed there either (under its last name given, i.e. MININT or its previous correct name)


If the machine object is already in SCCM and its not picking up the script that is a different story all together.  If its in SCCM it wont get the OSDComputerName variable as you only added that to the unknown collection.   If your task sequences are using Scripts to get this data, then you dont even need to have that variable on the unknown collection as you already have a mechanism in place to collect this data.

If your script is not prompting for the name, then there are other things we can investigate.  But an easier method for now would be to add the OSDComputerName variable onto the All Systems collection to see if it picks it up.  If the variable is on the Unknown and the All Systems and it still does not prompt the machine for that data, then yet again we have a new issue to investigate.

lets try something entirely different.  As these 3 machines are still actually building and the only thing they are failing to do is set the machine name, then lets investigate the SMSTS.log file.

This log file resides in a few places depening on how far into the build its gotten.
so it will either be on the boot image partition x:\windows\system32\Temp\SMSTSLOG\smsts.log
or C:\_SMSTasksequence\SMSTSLOG\smsts.log
or C:\Windows\System32\CCM\Logs\smsts.log (there will be 2 when it hits this point, one with a date which is the one you want)

So upload this log file from one of the affected machines after its finished building and we can then assess what may be failing within it.

actually, the machien accounts are not in active directory and not in sccm like i said before they are no where at all, there is no single reference of these three machiens in the entire system.
1- no active direcotry computer accounts or objects.
2-no SCCM objects or acounts.

and i have the MAC addresses of the three machiens i tried to prestage machien names to be obtained to these mac adresses, but never the less these three machiens had a mind of thier own.
actually i followed what you told me to the letter.

OK does your task sequence specify an OU and domain name for them to be added to?  Or does it just join a workgroup and the script is supposed to handle the rest?

If they do at least build, then try get me the smsts.log file.

yes its the first one actually
the task sequence adds them to the OU .and joins the domain. this is not scripted.

so once these 3 are built, are they in a workgroup or do they show as being joined to the domain?

i have resetted one of these machiens again after alot of changes ill let it make its run and ill look at it after being done ill look in it ill get all the log files u asked about, and ill report back to you on the name it hijacked from the system and from there i hope we can reach a turning point.

ill get back to you with the requested information early in the morning as there will be no more time today to manage that today.

Dear madam.
thanks for your help up to now
as agreed im sending you the log file from the machien that has a mind of its own and chooses its own machien name during the deployment.
i hope you can tell me where the problem is cuz i couldnt make much of it. smsts-20120105-162525.log

i hope to hear something from you soon,

Dear Expert.
i hope you are still willing to help me solve my issues here with SCCM and its functionality, we have been through quite a long part and most of it is working now just some small parts that need to be adapted.
thanks alot

Hi Arghosrho,

I was away on the weekend.  Back to solve this for you.

The PC name for the SMSTS.log file you've given me is PC8353.  This shows me it is being named correctly.  Is this not correct?  
If SCCM was not picking up the original name of the machine or failing to apply the machine name, you would get a MININT-****** type name.

well here is the hitch,
how htis company here organizes its business is kindda wiered.

this machiene had this name indeed. but then they wanna install it again and give it another name because that particular name PC8353 has been given to a new machien.

what they want is that by the deployment they get to call this machien what they want. what happens on the other hand is that the machien takes a name on its own. and we wanna stop that from happening.

the log file in your hands is from one of those machiens that actually didnt execute the naming script and installed autmatically. they didnt even dispaly the OSDComputer name variable you instructed me to add to the task sequence.

what happens is a bit wiered cuz before we try to re-deploy we delete the machiene from SCCM and from active directory and then we try to redeploy so supposedly this machien should be seeen as an unkown computer. am i right?

i hope im not making it too confusing.

make sure when you delete PC8353 from AD and SCCM that its not on any other sites.  e.g. not on 101 or 102.  when you delete objects from secondary sites, it replicates that change to the primary.  when you delete objects from the primary, it does not replicate this change down.

If you have more than one AD DC, then ensure that the DC you are deleting the object from has successfully replicated that to all its DCs (AD sites)

Ensure the object is still not sitting in the build provisioning collection you entered from Computer Association.  Make sure you update and refresh your All Systems collection to make sure its actually gone.  reset PXE to make sure it forgets that computer as well.

and how exaclty can i delete something from the secondary site,.
where im sititng i can only see the collections in the computer managment. how can i take it from there.

sorry for the confusion, i meant your other primaries... but on rereading this I see that this machine is under the central primary.   if you had your AD discoveries running on the lower primaries, you would have to make sure the object is removed from that site.

the smsts.log file did not really show as much info as I was expecting to see.  It seemed to run through the os deployment and stop even though i can see you had loads of apps to install.  Did these install at all?  or did it just install the BES client and leave it at that?  thats what it looks like it did.

What model of machine are these 3 machines?  What do they say in their BIOS as i see you have a lot of queries for different models of machines and I have seen some BIOS info incorrectly filled in by hardware vendors and so can be skipped in any query process.

those three machiens are just like any other machien company wide. no hardware changes whatsoever.
the thing is the same task sequence works everywhere on every other machien as it should be only these three refuse to ask for a machien name when we deploy them using PXE and they just take that name,
there is one other thing though. i discovered that those three machiens has been shared by the same user.

can this be a reason for the trouble?

can you upload an smsts log file from one of the machines that work?  that way i can do a comparison on them and see if i can spot anything.

what i'm not actually seeing in the log file you uploaded was the formating, partitioning, and placement of the OS.  only the BES client install and the validation of all the task sequence tasks.  maybe the log file is being overwritten because of length, so could you try do this as a test....

create a duplicate of the task sequence and give it a new name, then disable all the steps for the extra installs and only leave the OS deployment, disk partition, driver install and pc script naming.  then create a new collection for it, add those 3 machines to the collection, and assign the new task sequence to that collection.  that way the smsts log file will contain just what we are troubleshooting and nothing else and so wont overwrite itself as the size of the file gets too big.

Is it possible to get a copy of your PC naming script?

yes sure, ill work on it but now im seriously getting crazy from this SCCM deployment.,
suddenly the OSD system started behaving diffrently.
usually by deploying OS to a machien we got the choice between three diffrent deployments that we have right now the system gives us this message.
see the attached file
IMG-20120113-00351.jpg

this is right now the most pressing issue.
i hope u can help me on with this asap. cuz this project has actually startd to get to my nerves. as if its possesed by an evil power stopping it from functioning

have you put a schedule onto one of your task sequence advertisments thereby making it a mandatory task sequence?

you should become a university teacher.
that was the problem now everything is running as it was.
getting back to the problem we had.

i went to SMSpxe.log to see what the deployment service is doing with this particular computer and i got this from the log.

i am 100% positive that this MAC adress does not exist in the system i even serached some table in the Site database manually and i found nothing he says computer found in database. how and where i have no idea.

<![LOG[Executing LookupDevice(FD2CB800-1DB4-11E0-0000-3CD92B702D3D, 3C:D9:2B:6D:2D:B1)]LOG]!><time="10:27:22.500+-60" date="01-16-2012" component="smspxe" context="" type="0" thread="2612" file="database.cpp:394">
<![LOG[CDatabaseProxy :: LookupDevice succeeded: 3732 1 0 0]LOG]!><time="10:27:22.500+-60" date="01-16-2012" component="smspxe" context="" type="0" thread="2612" file="database.cpp:444">
<![LOG[MAC=3C:D9:2B:6D:2D:B1 SMBIOS GUID=FD2CB800-1DB4-11E0-0000-3CD92B702D3D > Device found in the database. MacCount=0 GuidCount=1]LOG]!><time="10:27:22.500+-60" date="01-16-2012" component="smspxe" context="" type="0" thread="2612" file="pxehandler.cpp:341">
<![LOG[[172.017.002.113:4011] Recv From:[172.017.093.009:68] Len:303 18fc470]LOG]!><time="10:27:22.516+-60" date="01-16-2012" component="smspxe" context="" type="0" thread="3000" file="smspxe.cpp:663">
<![LOG[Executing GetBootAction(3732, VM0048)]LOG]!><time="10:27:22.516+-60" date="01-16-2012" component="smspxe" context="" type="0" thread="2612" file="database.cpp:519">
<![LOG[No Boot Action for Device (3732) found]LOG]!><time="10:27:22.516+-60" date="01-16-2012" component="smspxe" context="" type="0" thread="2612" file="database.cpp:586">
<![LOG[ProcessDatabaseReply: No Advertisement found in Db for device]LOG]!><time="10:27:22.516+-60" date="01-16-2012" component="smspxe" context="" type="0" thread="2612" file="pxehandler.cpp:501">
<![LOG[[172.017.002.113:4011] Recv From:[172.017.002.113:9000] Len:274 125c1f0]LOG]!><time="10:27:30.509+-60" date="01-16-2012" component="smspxe" context="" type="0" thread="3000" file="smspxe.cpp:663">
<![LOG[Executing LookupDevice(46746E94-D140-497A-8C46-5463A8F006FD, FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF)]LOG]!><time="10:27:30.509+-60" date="01-16-2012" component="smspxe" context="" type="0" thread="2612" file="database.cpp:394">
<![LOG[CDatabaseProxy :: LookupDevice succeeded: 0 0 0 0]LOG]!><time="10:27:30.509+-60" date="01-16-2012" component="smspxe" context="" type="0" thread="2612" file="database.cpp:444">
<![LOG[MAC=FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF SMBIOS GUID=46746E94-D140-497A-8C46-5463A8F006FD > Device not found in the database.]LOG]!><time="10:27:30.509+-60" date="01-16-2012" component="smspxe" context="" type="0" thread="2612" file="pxehandler.cpp:349">

Its finding this machine has a GUID that matches another object in your database:

GUID:FD2CB800-1DB4-11E0-0000-3CD92B702D3D

try searching for this GUID in the All Systems Query

i dont have a query called all systems. i have alot of reports here but i didnt find one for all systems only

I am surprised by that as its a default query that is there from site installation, so it must have been deleted then.  

you are looking under the Queries node and not the Reports node?
If its not there, create a new Query under the Queries Node called All Systems, and select the type to be System Resource and then edit the query and paste this into it:
select Name, SMSAssignedSites, IPAddresses, IPSubnets, OperatingSystemNameandVersion, ResourceDomainORWorkgroup, LastLogonUserDomain, LastLogonUserName, SMSUniqueIdentifier, ResourceId, ResourceType, NetbiosName from sms_r_system

system not foudn in the query.

restart your WDS service on your pxe server and then try again and post the log.

de WDS is showing wiered symptoms.. when i look at it says windows deployment server not configured. when i try to configure it nothing happens! the wizard goes all the way a network share is configured and that was it, and the Windows Deployment services not configured never goes away

you must not configure it!!  

SCCM configures it for you.  When you build a site system that has PXE on it, you install WDS but do not configure it.  Then when you add the PXE role to the SCCM site, it automatically configures and links to the WDS services.  If it has done a configuration, i'd do a check to make sure you can still build.

All I wanted you to do was restart the Windows Deployment Service from the Services console.

well i guess i made a mistake just now as i clicked on Configure server and i pointed it to the right remote install folder now i see that its configured and i se einstall images , boot images, pending requests but they are all empty. do i have to do something about that? or is this correct.

no they should not be empty.... and now you have a big task on your hands to fix this.

you have to now undistribute all your boot images and any other images you have deployed to the pxe share.  once its reported success of the removal of that, you need to remove the PXE role from the server.  once the status's show that this task is complete, you need to uninstall WDS from the server and wait to make sure it has completed successfully and reboot the server if it doesnt prompt you to do so.

Then reinstall WDS and DO NOT launch it or do anything with it after install.  reboot the server, then add the PXE role for the site back in SCCM and once thats complete, distribute your boot images and any other images you had distributed there.

hmm,
there is somehting i wanna tell ou first.
1-the deployments are still working fine we have tried to deploy 3 computers and it is working perfectly fine.

2- i didnt publish anything through WDS all ive done was click on configure and then poin tit to the share which is on drive E: thas all, and that is why they are all empty in WDS but in SCCM everything is working perfectly fine and they look normal there.
i thought i might inform you about this first..
do i still need to undistribute all the images?

by the way i pointed WDS to the RemoteInstall server used by SCCM  and the wiered thing is nothing is affected all system deployments even after restarting the system are running flowlessly

how am i supposed to undistribute the packages?

if building machines still work then dont do anythign with WDS

i actually have done what u said.
i undistributed.
uninstalled
removed role.
restarted
added role.
redistributed by refreshing distribution points.
system buidling is working perfeclty again. but still these wiered machiens ae not being accepted. its
the symptoms look wiered. it keeps saying unaproved. while on other systems everything works like a charm

what do you mean it keeps saying unapproved?  so the objects come into sccm but then get marked as unapproved?  i thought you said they were not building?

yes they are not building i guess i miss expressed.
wha ti meant is the message that says

the detials 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 reqyest can be approved.

Pending request: 25
contacting server xxx.xxx.xxx.xxx
tftp download smsboot\x64\abortpxe.com

thas what im getting on this machien. and all other three machines that suffer from this case

have you tried updating your x64 and x86 boot images?  even if it uses the x86 boot image, it will still require the x64 boot image to be present if the architecture of the machine supports x64.  I have also seen an issue in the past whereby booting starts failing until the boot images are updated to another version.  specifically this was around v1 of the boot image not working but updaing dp's to v2 worked.

it may be worth a try unless you've already done this?

Well i have just updates everything to no avail.. All the dpa are on v4 now

They are all Bare metal with new HDD

i thought it might help if you saw the error screen.,
all three machiens suffering from this show this screen.

 

i hope u can help me with this issue as its becomming really pressing why certian machiens accept the installations and some other machiens dont/

can you get a client manually installed on one of these machines and try the above post i sent?

do your other machines receive IPs via referral?

i tried the above advice
maciens installed autmatically without asking for a machien name.. they gave themselves machiennames that are already in use by other machiens.

ok then for those other machines that are already on your network, please get the UUID, GUID, and MAC addresses and run comparisons on them.  When you pxe boot them, hit pause button and write down the data you see there, then compare and see if any of it matches.  Open the objects for the duplicate machine names and compare everything.  more than likely the GUID or MAC addresses are the same.

i have already done that the only thing i found in common was the resource number. the machien has a resource number that belongs to another machien. so it takes the mac adress and the GUID based somehow on that resource number and it says in the log Device found. and that there is no advertisment for it,

do you have any 3rd party sccm tools installed?
If not, i suggest installing:
http://myitforum.com/cs2/blogs/rhouchins/archive/2008/04/09/sccm-right-click-tools.aspx

once thats installed, for the machines that are already existing and are correct (not the ones being duplicated by the incorrect builds), right click the objects in SCCM and choose Client Tools, then regenerate GUID.

can you give me a copy of your task sequence and the computer naming script