waingro

Here's the locations for all OSD logs: http://technet.microsoft.com/en-us/library/bb932135.aspx I also recommend the right-click tools for SCCM. It includes SMS Trace which is helpful in formatting and highlighting errors, making the scanning of log files much easier. I install it on my workstation and it gives you some wonderful functionality (if you don't already have it). http://myitforum.com/cs2/blogs/rhouchins/archive/2008/04/09/sccm-right-click-tools.aspx

I see nothing in that log, either. Boot images must have the drivers injected in order to interface with the hardware properly. It's similar to pressing F6 when installing XP to install 3rd party drivers. Whether or not the installation would run without injecting any drivers is dependent upon the hardware platform you are running and whether or not the drivers are already included in the boot image. If you enabled the command prompt during the TS you can look at the local log files - they should give you more information. I believe there's a listing of those log file locations somewhere on this site. I'll see if I can find them.

Select the boot image you are using in the SCCM console, select the Windows PE tab, and select the "Enable Command Support" check box. Refresh the DP and resend the TS. That'll give you a command prompt on the workstation that'll allow you to view the log files.

Are you using native mode?

If you use SCCM to manage updates it would then be beneficial. Other than preference I can't really see a reason not to install it - it's been very stable on my other servers.

The speed of downloads can be regulated through BITs settings. Maybe this article will help: http://technet.microsoft.com/en-us/library/cc720428(WS.10).aspx You also need to verify that your network is not congested and that the client has proper bandwidth to perform these operations. As for me and mine, I choose to run the advertisement directly from the server. This results in a much faster install time since the package is not downloaded to the client first. This approach also keeps from running into space issues on the client since the client cache is limited by default. HTH.

I was able to accomplish this in the manner described here http://sys-center.blogspot.com/2008/04/windows-firewall-exceptions-for-sccm.html using group policy. There are other exceptions that need to be made for other aspects, such as remote tools, etc, but this will allow the client to install.

How are you deploying the client? Is the client listed in ConfigMgr now?