Integrating SCCM and MDT 2008[/b]
For our deployments, we always install MDT 2008 on our SCCM server and select Configure ConfigMgr Integration from the MDT area on the start menu. This gives us:
For beginners, the template task sequences are a very quick way to get up and running while being guided through the process, while for more advanced users the additional functionality comes in handy when your task sequences become more complex.
[b]Setting yourself up[/b]
In order to have any chance at troubleshooting SCCM OSD issues, you need to do the following:
Install trace32.exe which is part of the SMS 2003 Toolkit 2
(download from Here)
Enable command line support within your boot images:
a. Go to the properties of your boot image(s) (right click and choose Properties)
b. Go to the Windows PE tab and tick the Enable command support (testing only) option.
c. When prompted, click on Yes to update your distribution points.
d. From within your boot image (Windows PE) environment, you can now press F8 to
open up a command window — very useful for troubleshooting
Be familiar with your OS setup log files (e.g. WindowsXP has setupapi.log, netsetup.log etc.)[b]Log files[/b]
The root of all Task Sequence troubleshooting is called smsts.log — and this log is always the first step to troubleshooting any TS issue — if you have an issue, look in here first!
Unfortunately, the smsts.log can be stored in one of 7 locations, depending on the stage of the build and the architecture of the OS:
x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\S
Information is also logged as SCCM client events, which can be viewed by running the SCCM report:
Last 1000 messages for a specific computer (Errors, warnings and information)
As a general rule, the SMSTS.log provides more detail, however the SCCM client events are easier to read, and, for simple issues, can lead you to the root cause very quickly.
[b]PXE boot issues[/b]
In order to resolve PXE boot issues, there are two main log files we are interested in:
address to server list 192.168.00.117 $$<SMS_PXE_SERVICE_POINT><Fri Jul 31 07:54:45.248 2009 Cen. Australia Standard Time><thread=772 (0x304)> adding address to server list 127.00.00.01 $$<SMS_PXE_SERVICE_POINT><Fri Jul 31 07:54:45.250 2009 Cen. Australia Standard Time><thread=772 (0x304)> Sending availiability packet to: 192.168.0.117~ $$<SMS_PXE_SERVICE_POINT><Fri Jul 31 07:54:45.252 2009 Cen. Australia Standard Time><thread=772 (0x304)> Sent 274 bytes to 192.168.000.117:4011~ $$<SMS_PXE_SERVICE_POINT><Fri Jul 31 07:54:45.253 2009 Cen. Australia Standard Time><thread=772 (0x304)> PXE test request succeeded.~ $$<SMS_PXE_SERVICE_POINT><Fri Jul 31 07:54:45.355 2009 Cen. Australia Standard Time><thread=772 (0x304)> Successfully performed availability check against local computer.~ $$<SMS_PXE_SERVICE_POINT><Fri Jul 31 07:54:45.357 2009 Cen. Australia Standard Time><thread=772 (0x304)>
Another very common error is to see the following when trying to PXE boot:
PXE-T01: The specified file was not found PXE-E3B:TFTP error -- File not found
“But I’m only deploying an x86 boot image and OS,” I hear you say. It doesn’t matter. If the machine is x64 architecture (which all today’s new machines are), the boot ROM requested will be x64. This in no way effects your ability to use an x86 boot image; this boot ROM process is completely independent.The solution is to add the x64 image to your PXE DP and update. You will then see the directory \remoteinstall\smsboot\x64
Bron: klik hier