When troubleshooting client installation issues the log files on the client machine and the site server usually provide you with a clue as to what the issue is. It may at times seem cryptic but generally the logs will provide you with a direction to take when troubleshooting client installation issues.
It is important to note here that in order to install a client the resource needs to be discovered and assigned to the site. This is initiated by adding site boundaries and enabling and executing a network discovery to locate potential client resources before they can be installed.
On the potential client resource the machine must obviously have sufficient free disk space and have network connectivity in the domain and meet the minimum client requirements for SMS or ConfigMgr. For example a ConfigMgr SP 1 client machine must have at least the following at a minimum:
Windows 2000 Professional SP 4 Operating system or later.
350 MB Free disk space.
233-MHz Processor.
128 MB RAM.
Additionally the client must have File and Print Sharing enabled and you must be able to access to the ADMIN$ share on the machine and remote WMI access must be enabled. In most cases the firewall or the firewall restrictions are preventing WMI access and access to the site server files necessary to initiate and complete the client installation. You can configure the firewall to allow the necessary access or you can temporarily disable the firewall on the client to see if the installation will function as expected.
The site server and your domain infrastructure may also be preventing client Installation as well. On the site server make sure that you have an admin account for the Client Push Installation specified that has administrator rights on the client machines and try and determine that there are no name resolution issues in the domain.
No Comments