Eswar Koneti

this doesnt cause the failure for secondary site installation but once the site installed,it may not be able to publish its info to AD system management container.

from client prespective to know which DP the client is accessing for installing packages ,you can refer locationservices.log from c:\windows\system32\ccm\logs

To Disable auto-update notification: Create or open the mms.cfg file in a text editor. Add the following auto-update setting: AutoUpdateDisable=1 Save the mms.cfg file with UTF-8 encoding in the correct system location for the user's operating system. Close and restart Flash Player or the browser in which Flash Player is running for the new setting to take effect. For more info http://kb2.adobe.com...7/16701594.html

may be you can create package with batch file(it includes list of DLL files with command regsvr32.exe DLL file path name) and run the batch on the computers to update the DLL files.

what does ConfigMgrSetup.log and ConfigMgrPrereq.log log files. These files are located at the root of the system drive on the secondary site computer. this should gives you some information about the problem.

odd one.you may have to refresh the collection once to see the changes also verify if the computers are exits in SCCM Database. If you are in SCCM R3,it has funcitonlity to add resource to collection.

Go with SCCM SP2 with R2/R3 to aviod adding the unknown computers MAC addresses about Unknown computer support http://blogs.msdn.com/b/steverac/archive/2008/09/21/unknown-computers-in-sccm-2007-r2-overview.aspx how it works : http://blogs.msdn.com/b/steverac/archive/2008/09/21/unknown-computers-in-sccm-2007-r2-how-it-works.aspx

(AFAIK ) if there are more than 1 task sequence(some has x86 boot image and x64) assigned to unknown computer,when the system do pxe boot, it select the boot image which is compatiable to hardware and list all the avilable task sequences to select. what is the issue you are facing here ?

so from the logs,you see the last hardware inventory sent on 12-10 .check if you have enabled any site manitannce tasks which deletes the aged inventory data etc. http://technet.microsoft.com/en-us/library/bb632595.aspx

if it is blank on all clients not sent their inventory information to site server .You should look at inventoryagent.log file if the clients are healthy.

use the criteria not in,that should do the trick here. like select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.ProdID = "IE8" and SMS_G_System_ADD_REMOVE_PROGRAMS.ProdID not in (select SMS_R_System.ResourceId from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.ProdID = "IE8-MUI") Thsi will list all the computers in collection which are installed IE8 and not installed with IE8-MUI

if you want to remove the computers from SCCM databse which are not in AD ,you can do ths via site maintanance tasks (http://technet.microsoft.com/en-us/library/bb693646.aspx) Or else look at this script : http://myitforum.com/cs2/blogs/matbe/archive/2011/05/03/delete-computers-from-sccm-that-have-been-removed-from-ad.aspx (use at your own Risk )

chek this thread...http://social.technet.microsoft.com/Forums/en-US/configmgrinventory/thread/94f769b5-e87d-42bf-9463-7fff2dadd634 Once you have done the changes into MO file,you can create sccm report http://eskonr.com/2009/12/sccm-report-for-computers-asset-information-including-sn-number-and-model-name/ OR http://eskonr.com/2010/11/collection-query-report-to-get-computer-modelserial-number-for-a-given-computer/

I see, then probably he should look into discovery method logs and collection evalutaor logs for errors.

not infront of my lab to check but you can check peters' blog on Collections in SCCM 2012 beta2 http://www.petervanderwoude.nl/post/a-collection-of-changes-to-the-collections-in-configmgr-2012/. can you check under device collection ?

which collection are you looking at ? can you check collection "all systems" and see if you can find the computers (XP and server 2008) ? do you computer names from the colleciton ?

client is pushed successfully from server.You can check the ccmsetup.log and client.msi.log as well ?

take a look at ccm.log file from site server installation log files.it gives you ful info...

check the eventviwer log why it failed ,you will see some useful information which helps to resolve the issue.

You can do as you do for Physical machienes. Create a OS image using WIM file ,Distribute it to DP and create a TS ,apply to collection (either Unknwon computers or collection with imported CA). configure the Virtual PC to use the same network Card as server has and do PXE boot.

Did you check niall comments ? the package is 0 bytes

did you check if Webdav is installed correctly and configures as it says in solution. Check MP logs for Management point installation ,it says what prereq missed for installtion. take a look at this installation and configuration of Webdav http://www.windows-n...ws-server-2008/

failed due to client package can not be found .as said by Peter,check distmgr.log and ensure the package is avilable on DP(not on PXE DP).

take a look at this blog to identify the computers not sent their hinv info http://eskonr.com/2009/08/collection-report-for-hardware-inventory-not-reported-scanned-for-x-days-and-systems-that-doesnt-even-report-to-site/ and troubleshoting http://blogs.technet.com/b/sudheesn/archive/2010/05/31/troubleshooting-sccm-part-ii-hardware-inventory.aspx

if software/applicaiton is uninstalled from computers,it should be reported Via hardware inventory agent to site server not via Discovery methods and discovery method will not discover this information. check if the computer sent its hardware inventory or not by looking at inventoryagent.log from c:\windows\system32\ccm\logs