Eswar Koneti

From SCCM server,right click on computer,resource explorer,under hardware --->work station status you will see when was it reported to.

can you check on the spotted computer,when was it reported its last hardware inventory to SCCM site server ?

Nope,there is not but you can use the site maintanance tasks (like delete aged Discovery Task will only delete resources that have not been updated by any discovery method for the designated period) for the computers that are removed from AD. Refer this thread http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/e52b568f-2da5-45a6-a9d5-c33592937871/

Any other programs are running on this client ? Or is this only pakcage having issue ? For me it seesms to be some access issue to connect.

Did you refer SCCM super flows document on Software update http://eskonr.com/2010/09/system-center-configuration-manager-2007sccm-superflows/ Particularly,take a look at Software Updates Synchronization SuperFlow(WSUS and SCCM server) and Configuring Software Updates SuperFlow(how the settings are applied to Client and process explained well)

Are you able to connect to remote computer admin$ share from SCCM server ? If Yes,try if wmi is working or not on remote computer.

Instead of deplying the applications to user based(what happens if one use using loggin to multiple computers),I would prefer ,to deploy to their assigned computers based on AD security group. Here is automatic way of doing application Deployment . http://www.windows-n...ctions-in-sccm/

By default authenticated users (domain users) can only add 10 machines to the domain. see http://blogs.technet.../18/403817.aspx for instructions on how to change. This is controlled by the "Add workstations to domain" right, which can be found in the security policy under "Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\". Typically, this would be changed by the sysadmin when the domain is created in order to restrict this right to a specific group, usually "DOMAIN\Administrators. for more info http://technet.microsoft.com/en-us/library/cc780195%28WS.10%29.aspx

Check,the permissions for domain joining account ? does it have proper rights ? For troubleshooting domain join issues, can you check the C:\Windows\Debug\Netsetup.log file on the client ?

Ah.Okay ,should this be the case in SMS environment as well ? http://technet.microsoft.com/en-us/library/cc180360.aspx there is change in NAA Account functionality from SMS to SCCM .

There is no maintenance taks that will remove duplicate records in the database. You should however always configure the Delete Inactive and Delete Obosolete clients. For Duplicate records you will need to identify them and delete them. Check this post for more information http://support.microsoft.com/kb/837374 You wil also find a query to locate duplicate records in the post.

From the execmgr.log,it says,error 2--->The system cannot find the file specified and Script for Package:IDS00128, Program: Per-system unattended failed with exit code 1619-->This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Clients will always connect to DP to install packages and not from host server(I mean source Location) and client uses Network access account to get connect to DP for packages. So you will have to make the package avilable on DP,set NAAccount with correct password with required advertisement options(run from DP or download and run)

If Microsoft DHCP is installed on the same physical computer as Windows Deployment Services, the WDS configuration wizard does the following (if you configure Windows Deployment Services by using WDSUTIL, you have to manually make these changes): Adds DHCP option tag 60, with the PXE client setting selected, to all DHCP scopes (as a DHCP global option). This is necessary so that a booting PXE client can be notified that there is a listening PXE server on the network. Selects the Do Not Listen on port 67 option. This is necessary so that booting clients can find the DHCP server on the network. [*]If you are running Windows Deployment Services and a non-Microsoft DHCP server on the same computer, in addition to configuring the server to not listen on port 67, you must use your DHCP tools to add Option 60 to their DHCP scopes.[*]If DHCP is installed on a server that is located in a different sub-net, then you must do one of the following: Recommended: configure your IP Helper tables. All DHCP broadcasts on UDP port 67 by client computers should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server. Also, all traffic to UDP port 4011 from the client computers to the Windows Deployment Services PXE server should be routed appropriately (these requests direct traffic to the server, not broadcasts). Add DHCP options 66 and 67. For more information, see the PXE Boot chapter at http://go.microsoft.com/fwlink/?LinkId=88439

How did you set the package to run ? is it run from DP or download from DP before run ? can you check the version for the package and on the client if any mismatch or something ? Try updating the package on the DP (look at locationservices.log which DP is it contacting ) and see if that works? Have ever changed the password for Network Access Account ?

Have you tried with creating package and program with command line REG IMPORT filename.reg ?

can you provide the full path for the file 1.dll after /XF ? something like /XF C:\eskonr\test.txt OR /XF C:\eskonr\test\test.txt

SCCM Uses the functionality of WDS in PXE Boot mode and the procedure is same . Take a look at this post how to disable F12 http://www.windows-noob.com/forums/index.php?/topic/2720-no-f12/

what does execmgr.log and CAS.Log says ?

take a look at peter's blog post http://www.petervanderwoude.nl/post/ConfigMgr-2007-Updating-a-Windows-7-Image-with-the-latest-Software-Updates-e28093-A-less-conventional-but-very-effective-way.aspx

Probably,you can check that by looking at execmgr.log from ccm logs ?

The error 0x80070057 means basically A Network Adapter Hardware not found. What does smsts.log says ? what is the full error message thay you get on the screen along with failed to run task sequence ?

Go to your Group Policy Management Console (gpmc.msc) and edit the GPO and locate computer configuration--->policies--->adinistrative Templates-->windows Components-->Internet Explorer-->Delete Browsing History. set the settings as per the requirement. Done!

> 1. After deploying patches and while monitoring deployment status, SCCM Console is very slow :Console performance is not affected because of patch deployment.there could be many reasons why it is slow.What is the RAM that you used and can u check task manager for the performance of the processes,etc > 2. How to find the systems having WMI issues? : Take a look at this http://blogs.technet...mi-testing.aspx how to check but not Via SCCM. > 3. Patch management best practices : For best practice,look at MS technet and how to set up ,http://www.windows-noob.com/forums/index.php?/topic/624-configuring-software-update-point-within-sccm/ > 4. Is there any way patch management for Linux Systems through SCCM , :Yes, I think so, If You integrate VAS(Quest Tool) http://www.quest.com...ation-services/ or some other extentions tool > 5. What is the maximum size of package should be. (Software or Updates package) :Not 100% sure about package size but you can include max of 500 patches in a Deployment package as i know.Rad it from MS http://technet.microsoft.com/en-ca/library/bb693754.aspx (Selective Download)

Take a look at thsi post to get an idea how this work in this scnenario http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/588b8679-c51d-442c-afeb-ba460c46e429/

SCCM\SMSPIXIEIMAGES$ comes only,when you have WDS feature correctly installed (<Drive Installation>:\Remoteinstall\SMSimages) and configured and PXE role is enabled. check,if there are any issues in installing PXE Role from log PXESetup.log. You have Lot of guides avilable here on How to Set up SCCM http://www.windows-n...cm-2007-guides/