SCCM Discovery/Client Installation Problems

[guest]

I recently configured SCCM 2007 SP2 on a Windows Server 2008 R2 Hyper-V server. Along with SCCM, in this domain, are an Active Directory DC Hyper-V server as well as another Hyper-V server running 2008 R2. The issue I am having is I can't seem to find a way to push the SCCM Client to the other two servers. I know the connection exists because all of the domain systems can ping each other. I know that the permissions are right because all of the systems can access each other. I've set the permissions in Active Directory so that all three Computer objects have Domain and Local administrator permissions.

Then, after I went through all of these steps, I tried to just install the SCCM client manually from the SCCM disk onto the Active Directory Server and the second Server 2008 R2 server. The client would not install. I extended the schema using the utility on the SCCM disk to extend the Active Directory schema for SCCM.

I'm very new to SCCM and have never used SMS or any other type of zero-touch deployment service.

What steps am I missing to ensure that SCCM can "discover" the other two systems (or ANY other system other than itself) so that the client can be pushed from SCCM or so that I can manually install the client to facilitate SCCM's discovery of the other two machines?

[guest]

I was able to obtain a partial resolution:

Problem Cause:

Windows Server 2008 blocks a BITS download of the required Swimage Conductor files when they have been advertised to the client.

Remediation Steps:

1.The requestFiltering section on BITS-enabled distribution point server must be modified Open the applicationHost.config file located in the %windir%\System32\inetsrv\config\ directory on the BITS-enabled distribution point site system.
2.Search for the <requestFiltering> section.
3.Determine the file extensions that you will have in the packages on that distribution point. For each file extension that you require, change allowed to true.
- Change the line <add fileExtension=".vb" allowed="false" /> to <add fileExtension=".vb" allowed="true" />.
- Change the line <add fileExtension=".config" allowed="false" /> to <add fileExtension=".config" allowed="true" />.
- Allow only the file extensions required for your packages.
4.Save and close the applicationHost.config file.
Reference:
http://technet.microsoft.com/en-us/libr ... 31377.aspx



Once I changed the "allowed" from "false" to "true," the Windows 7 test machine was easily able to obtain the packages I was trying to send from SCCM. Now I need to do more work to determine what is holding up the rest of my Hyper-V machines from being discovered by the SCCM test Hyper-V machine that I have in my configuration and see if, once they are discovered, if the software packs I have been trying to send will properly launch.