Archive

Archive for the ‘SCCM / SMS’ Category

Modifying SCCM collections from the command line

February 8th, 2012 No comments

Automating SCCM OSD collection removal and addition.

I  created a little command line app that allows modification of SCCM collections from the command line  SCCMd – it requires various licensed MS components, but these should all be present on your SCCM server.

Usage: ScCmd.exe [/h:<hostname>] [/u:<username>] [/p:<password>] [/i] [/d] [/a:<CollectionName>] [/r:<CollectionName>] [/rd] [/c:<SccmclientName>
] [/m:<MacAddress>] [/f] [/q:<MacAddress or ClientName>]

/h SCCM HostName <required>
/u UserName <Defaults to current user>
/p Password <Only required when specifying user>
/i Import client to SCCM <MacAddress and HostName required> (use -f if Overwrite required)
/d Delete client from SCCM <ClientName or macAddress required>
/a Add Client to Collection <ClientName and CollectionName required>
/r Remove direct rule client from a Collection <Clientname and CollectionName required>
/rd Remove all direct Collection rules <clientName required>
/f Force Overwrite of existing records when importing new clients
/c Sccm Client Name
/m MacAddress
/q Query SCCM for client record – returns client details

I use this to manage the removal from collection (and addition to new collections) by monitoring events on my build jobs.

So by settings up an Eventlog monitor to execute a bacth file like the following:

@ECHO OFF
if “%1″==”” goto :NOARGS

REM Check if server is in one of my deployment collections
c:\Windows\sccmcmd.exe /h:mysccmserver /q:%1 > %temp%\%1.txt
findstr /C:”Windows Server 2008 R2″  %temp%\%1.txt >nul&&(GOTO POSTBUILD)||(GOTO 2K3)

:2K3
findstr /C:”Windows Server 2003 R2 x64″  %temp%\%1.txt >nul&&(GOTO POSTBUILD)||(GOTO FLUSH)

:FLUSH
REM Remove from all collections
c:\Windows\SCCMCmd.exe /h:mysccmserver /rd /c:%1
GOTO END

:POSTBUILD
REM Schedule PostBuild Job by adding the server to the Postbuild collection
c:\Windows\SCCMCmd.exe /h:mysccmserver /rd /c:%1
c:\Windows\SCCMCmd.exe /h:mysccmserver /a:”R2 PostConfig – LIVE – R2.CMD” /c:%1
GOTO END

:NOARGS
ECHO “No Arguments”
GOTO END

:END

The Server gets removed from all collections after a successful build, then added to the ‘PostBuild’ collection – which of course launches all of my PostBuild scripts.

This means I am able to manage which collections my server is in at the end of my build process.

Categories: SCCM / SMS Tags:

ADSI from WinPE

September 21st, 2011 No comments

Johan Arwidmark  over at http://www.deployvista.com/Home/tabid/36/EntryID/127/language/sv-SE/Default.aspx has an ADSI plugin for Windows PE, (the download link below has x86 and x64 support.)

 

He has recently replaced his site with http://www.deploymentresearch.com – but I am unable to find the link on this site (hence the link to the old site below)

This is very useful for those who want to hit the AD from deployment HTAs etc when creating server builds and so on

He has even created very simple batch files for creating the updated boot wims (though I assume of course that you all have relatively custom wims as is, so may want to pick through the batch file and substitute your own boot wim as a source)

Download link:
http://www.deployvista.com/Repository/tabid/71/EntryId/61/DMXModule/396/Download/attachment/language/en-US/Default.aspx

 

Categories: SCCM / SMS, Toolbox Tags:

“Safety settings on this machine prohibit accessing a data source on another domain.” – solution

September 21st, 2011 No comments

I have been building a new HTA fronted deploy ISO for multiple domains (in combination with SCCM as used on a client site) and kept coming across the error message:

“Safety settings on this machine prohibit accessing a data source on another domain.”
Stupidly, I initially assumed that this had something to do with the HTA being run from a WinPE environent – well this is partially true – but the fix applies to machines that are in workgroups / domains and even running WinPE.

It is a simple secuity tweak by Microsoft to prevent access across domains (thgouh of course when running WinPE you are not a domain member)

The fix is simple   – you simply need a regkey to define the policy setting.

the key is as follows:

head to :

 

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3

 

and create a REG_DWORD key 1406 and set it to 0

Of course if you need it for all users / default user – set it at those hives.

Simple

 

 

Categories: SCCM / SMS Tags:

Troubleshooting SCCM

September 1st, 2011 No comments

Straight from – http://w ww.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Systems_Management_Server/A_1259-SCCM-OSD-Basic-troubleshooting.html

Duplicated here as information keeps disappearing from all my bookmarks -then I am unable to find it . .

 

All Credit to the guys  at expertsexchange

SCCM OSD Basic troubleshooting

SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispersed nature of the blog posts that deal with some of these issues. This article will help SCCM OSD newbies with some of these issues.

Integrating SCCM and MDT 2008
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:

  • Templated task sequences we can import into SCCM
  • Additional TS Variables for use in our task sequences
  • Additional options and flexibility around computer backup, USMT etc.

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.

Setting yourself up
In order to have any chance at troubleshooting SCCM OSD issues, you need to do the following:

1
Install trace32.exe which is part of the SMS 2003 Toolkit 2
(download from Here)
2
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
3
Be familiar with your OS setup log files (e.g. WindowsXP has setupapi.log, netsetup.log etc.)

Log files
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:

  • WindowsPE, before HDD format:
    x:\windows\temp\smstslog\smsts.log
  • WindowsPE, after HDD format:
    x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
  • Full version windows, before SCCM agent installed:
    c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
  • Full version windows, after SCCM agent installed:
    c:\windows\system32\ccm\logs\Smstslog\smsts.log
  • Full version x64 windows, after SCCM agent installed:
    c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
  • After Task Sequence has finished running
    c:\windows\system32\ccm\logs\smsts.log
  • After Task Sequence has finished running(x64)
    c:\windows\sysWOW64\ccm\logs\smsts.log

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.

PXE boot issues
In order to resolve PXE boot issues, there are two main log files we are interested in:

  • Pxecontrol.log — which is located in the installation logs directory (eg C:\Program Files (x86)\Microsoft Configuration Manager\Logs\pxecontrol.log)
  • Smspxe.log — which is located in MP logs directory (eg C:\Program Files (x86)\SMS_CCM\Logs\smspxe.log)

If this is the first time you’ve setup a PXE service point, I recommend you check pxecontrol.log, there should be lines similar to the following:

1:
2:
3:
4:
5:
6:
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)>

If you see otherwise, then, WDS or the PXE service point is not correctly installed.  Without going into too much detail in this area, as a catch-all fix:

  • Uninstall the pxe service point
  • Uninstall WDS
  • Reboot
  • Install WDS, but DO NOT configure
  • Install the pxe service point
  • Re-check the pxecontrol.log

Another very common error is to see the following when trying to PXE boot:

1:
2:
PXE-T01: The specified file was not found
PXE-E3B:TFTP error -- File not found

This error is caused because you are missing files from your \remoteinstall\smsboot\x86

or x64 directory and is generally caused by one of two things:

1
The x64 boot image has not been added to the PXE service point.
“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 populated with files, and your good to go.

2
Even after you update your PXE DP, the files still don’t show up.
This is a common issue.  When updating the DP, the WIM file is mounted (under C:\windows\temp), all your modifications injected (such as drivers, custom backgrounds etc) and then packed back up into the boot wim pushed to the DP.  At the same time, the boot ROM files were interested in are extracted to C:\Windows\temp\Pxebootfiles before being copied to \remoteinstall\smsboot\x86or x64.Sometimes the C:\Windows\temp\Pxebootfiles directory has something funky happen to it and doesn’t clean itself up correctly.  So the difficult fix is — Delete the directory and re-distribute the package. (The directory is hidden, so make sure you set the option in Explorer so you can see it).  You can also have a look at pxecontrol.log to see the extraction process and/or the error occurring.

On some computers you might PXE boot, proceed to see a screen which indicates that the PC is talking with SCCM, followed by a line which indicates a boot ROM called abortpxe has been used.  This indicates one of two things:

1
This computer has already been built via PXE.
If you want to run this advertisement again, you must go into the console, right click on the computer record and select clear pxe advertisement
2
There is no advertisement for this machines mac address or SMSBIOS GUID in the database.
This can be confirmed by viewing the smspxe.log.  In this case, you should ensure that
a. The computer record has the correct MAC address
b. The computer record is in a collection which has the task sequence advertised to it
c. The task sequence advertisement is available to PXE boot (a property of the advert)

Software Update issues on reference build
While creating the reference build, the target machine must not be a member of a domain (and therefore must only be in a workgroup).  Because of this, the machine cannot use AD to lookup SCCM server location details and software updates will fail (after a 20 minute wait).

To work around this, in your reference build TS, navigate to the step setup windows and configmgr, and in the installation properties add

1:
SMSSLP=<fqdnOfSCCMServer> SMSMP=<fqdnOfSCCMServer>

This will allow the client to locate the software update point and download the appropriate updates. (Note: this assumes you have installed the Server Locator Point role on your server).

In the case that there are a large number of updates to be downloaded, you may also find that this task fails. This is caused by an issue documented in this TechNet blog entry about error 0x80244010.  Due to this issue, I recommend you create a number of software update tasks (I use 3), each with continue on error checked.  This will get around this issue, but will not cause any significant delay even if this issue does not occur.

Drivers
The deployment guys have a fantastic blog post on how to handle drivers in this TechNet Driver Management blog entry.

Boot image drivers
SCCM boot images are customised windows PE 2.x images used to boot the computer and contact the SCCM server. There are a couple of basic rules when working with boot images:

1
SCCM boot images only require network and local disk access (as they need to grab data from the SCCM server and apply it to the local disk) so these are the only drivers that ever need to be added to a boot image. (adding additional drivers will only bloat the image, slowing down your installs).
2
SCCM boot images are based on Windows PE 2.x, which is based on Vista.
You must add Vista drivers to your boot images only.  Even if you’re deploying on XP, it doesn’t matter, the boot environment is completely separate to your final OS.

The way I find out if I need to add additional boot wim drivers is to simply boot any new machines into a OSD TS, boot, press F8 to get a command prompt, then run

1:
ipconfig

If there is no ip address (we don’t have NIC drivers and they need to be added), then run

1:
diskpart | list disk

If there are no disks listed, then we need to add mass storage drivers to the boot WIM.

Windows XP 07B stop issues
If you’re building Windows XP or 2003, these operating systems do not allow dynamic injection of mass-storage drivers. So, you have a few options:

  • Move to Windows 7 — which after 6 months of betas/RCs and now running RTM – I’m willing to say is brilliant.  …or…
  • Change the disk controller mode from AHCI or RAID to IDE in the BIOS (quick, but not recommended for a long term solution).  …or…
  • Use the appropriate AHCI mass storage drivers:
    a. Import the drivers into SCCM, using categories etc. (see the deployment guys blog post on
    best practices for this)
    b.  Add a task to the task sequence: Apply driver package
    c.  Select the appropriate driver package
    d.  Check the box: Select the mass storage driver within the package.…..
    e.  Select the appropriate driver.
    f.  Add a condition via a TS variable <model> or WMI Query (again, covered in the deployment guys post)

Task Sequence Variables
Task sequence variables are really what give task sequences a bucketload of power, as you can have one TS which accounts for all the variations in your environment.

One of the most common questions we get is:
How do I know what TS Variables are available?
Well, there is a list in this article:  Operating System Deployment Task Sequence Variables, or you could read the documentation (Toolkit Reference.doc from the MDT 2008 documentation), or search through the script which gathers the variables (ZTIGather.vbs), or dump them all out using another useful script from the deployment guys (See Logging All the Configuration Manager Task Sequence Variables).

The advantage of dumping them all is that the output actually has meaning, so you can see what variable has what value — as opposed to just looking at a bunch of variables that might not mean much to you without values assigned to them.

In addition to the built in variables, you can add custom variables to computer objects or to entire collections.

SCCM Client Version
If you are using SCCM 2007 SP1, there is a hotfix, KB955955 available here, which you should apply, as it removes a delay between tasks, which, for long task sequences can significantly reduce build time.  The article also includes instructions on how to implement the hotfix during your bare-metal builds.

Categories: SCCM / SMS, VMWare Tags:

SCCM OSD Port requirements for private networks

February 18th, 2011 No comments

We’ve been considering building servers using SCCM in remote offices (Brussels, New York etc)
For now, it will be a limited number of servers, so we do not want to duplicate the SCCM infrastructure, but this will mean that we need to open some ports for this to run. Read more…

Categories: SCCM / SMS Tags:

SCCM error Codes – Troubleshooting SCCM OSD

January 25th, 2011 No comments

I found this list somewhere . . and have had it sitting on a notepad doc for some while – figure I may as well post it somewhere useful?

Error Code Description
CCM_ERRORCODE(0x 80040200) NAMENOTFOUND
2147746304
Name not found
CCM_ERRORCODE(0x 80040201) BADNAMEFORMAT
2147746305
Incorrect name format
CCM_ERRORCODE(0x 80040202) SERVICESHUTDOWN
2147746306
Service is shutting down
CCM_ERRORCODE(0x 80040203) DATAEMPTY
2147746307
No data supplied
CCM_ERRORCODE(0x 80040204) DATATOOLARGE
2147746308
Data too large
CCM_ERRORCODE(0x 80040205) INVALIDPATH
2147746309
Invalid path
CCM_ERRORCODE(0x 80040206) INVALIDFILE
2147746310
Invalid file
CCM_ERRORCODE(0x 80040207) PARSE
2147746311
Parsing error
CCM_ERRORCODE(0x 80040208) INVALIDCOMMAND
2147746312
Invalid command
CCM_ERRORCODE(0x 80040209) DATATYPEMISMATCH
2147746313
Data type mismatch
CCM_ERRORCODE(0x 80040210)
INVALIDTRANSLATOR
2147746320
Invalid Translator
CCM_ERRORCODE(0x 80040211) INVALIDADDRESS
2147746321
Invalid Address
CCM_ERRORCODE(0x 80040212) CONTEXTCLOSED
2147746322
Context is closed
CCM_ERRORCODE(0x 80040213) TIMEOUT
2147746323
Timeout occurred
CCM_ERRORCODE(0x 80040214) INVALIDNAMELEN
2147746324
Invalid name length
CCM_ERRORCODE(0x 80040215) ITEMNOTFOUND
2147746325
Item not found
CCM_ERRORCODE(0x 80040216)
INVALIDSERVICEPARAM
2147746326
Invalid service parameter. The WMI file could be corrupt or there was a manual change to a site control file.
CCM_ERRORCODE(0x 80040217) DATACORRUPT
2147746327
Data is corrupt
CCM_ERRORCODE(0x 80040218) INVALIDSERVICESETTING
2147746328
Invalid service settings
CCM_ERRORCODE(0x 80040219) GLOBALSERVICENOTSET
2147746329
Global service not set
CCM_ERRORCODE(0x 80040220) INVALIDTYPE
2147746336
Invalid type
CCM_ERRORCODE(0x 80040221) INVALIDUSER
2147746337
Invalid user. An operation for a user that is not logged on is in process or the user account is invalid.
CCM_ERRORCODE(0x 80040222)
CANCELLED
2147746338
Operation cancelled
CCM_ERRORCODE(0x 80040223) VERSIONMISMATCH
2147746339
Version mismatch
CCM_ERRORCODE(0x 80040224) INVALIDMESSAGE
2147746340
Invalid message
CCM_ERRORCODE(0x 80040225)
INVALIDADDRESSTYPE
2147746341
Invalid address type
CCM_ERRORCODE(0x 80040226) INVALIDPROTOCOL
2147746342
Invalid protocol
CCM_ERRORCODE(0x 80040227) DISABLED
2147746343
Functionality disabled
CCM_ERRORCODE(0x 80040228) INVALIDENDPOINT
2147746344
Invalid endpoint
CCM_ERRORCODE(0x 80040229) GETCREDENTIALS
2147746345
Failed to get credentials
CCM_ERRORCODE(0x 80040230) LOGONUSER
2147746352
Error logging on as given credentials
CCM_ERRORCODE(0x 80040231) TRANSIENT
2147746353
Transient error that could indicate a network problem.
CCM_ERRORCODE(0x 80040232) MESSAGENOTSIGNED
2147746354
Message not signed
CCM_E_MESSAGENOTTRUSTED(0X 0x80040233)
2147746355
Message not trusted
CCM_ERRORCODE(0x 80040234) INTERNALENDPOINT
2147746356
Internal endpoint cannot receive a remote message
CCM_ERRORCODE(0x 80040235) PARSE_SYNTAX
2147746357
Syntax error occurred while parsing
CCM_ERRORCODE(0x 80040236) LOWMEMORY
2147746358
Low memory.
CCM_ERRORCODE(0x 80040237) REPLYMODE_INCOMPATIBLE
2147746359
Reply mode incompatible
CCM_ERRORCODE(0x 80040238) PUBLIC_KEY_NOT_FOUND
2147746360
Public key not found
CCM_ERRORCODE(0x 80040239) CLIENT_ID_NOT_FOUND
2147746361
Client ID not found
CCM_ERRORCODE(0x 80040240) INSUFFICIENTDISKSPACE
2147746368
Insufficient disk space
CCM_ERRORCODE(0x 80040241) DATABASE_CONNECT_FAILED
2147746369
Failed to connect to database
CCM_ERRORCODE(0x 80040242) STORED_PROCEDURE_FAILED
2147746370
Stored procedure failed
CCM_ERRORCODE(0x 80040243) PUBLIC_KEY_MISMATCH
2147746371
Public key mismatch
CCM_E_BAD_HTTP_STATUS_CODE (0x 8004027E)
2147746430
Client communication from the management point failed.
CCM_E_EMPTY_CERT_STORE (0x 80040280)
2147746432
A valid certificate was not found in the certificate store.
CCM_E_NO_CERT_MATCHING_CRITERIA (0x 80040281)
2147746433
No valid certificate could be found using the specified certificate selection.
CCM_E_TOO_MANY_CERTS (0x 080040282)
2147746434
More than one valid certificate was located
CCM_E_MISSING_PRIVATEKEY (0x 080040283)
2147746435
The selected certificate does not have a corresponding private key, which is required for successful communication.
CCM_E_MISSING_SUBJECT_NAME (0x 080040284)
2147746436
The selected certificate does not have a Subject Name defined.
CCM_E_UNKNOWN_SEARCH_CRITERIA (0x 080040285)
2147746436
The certificate selection criteria syntax is invalid.
CCM_E_INVALID_SMS_AUTHORITY (0x 080040286)
2147746437
The certificate does not successfully chain to a trusted root certification authority.
CCM_E_MISSING_SITE_SIGNING_CERT (0x 080040287)
2147746438
Cannot locate the required Configuration Manager site server signing certificate for this site.
HandleRemoteSyncSend failed (0x80040309).
2147746569
The ‘trust failed’. This happens when the client doesn’t trust data from the management point.
CForwarder_Sync::Send failed (0x80040309).
2147746569
The ‘trust failed’. This happens when the client doesn’t trust data from the management point.
CForwarder_Base::Send failed (0x80040309).
2147746569
The ‘trust failed’ This happens when the client doesn’t trust data from the management point.
CCM_E_LOCATION_MPREFRESH
CCM_ERRORCODE(0x80040300)
2147746560
Client trying to refresh management point and it is empty.
CCM_E_LOCATION_NOAD
CCM_ERRORCODE(0x80040301)
2147746561
Client is configured to only read Active Directory Domain Services and couldn’t find the requested location (site assignment, management point) data.
CCM_E_LOCATION_NOTASSIGNED
CCM_ERRORCODE(0x80040302)
2147746562
Client is trying to do something that requires being assigned to a site and it is not assigned. Only called from NAP when trying to refresh the management point.
CCM_E_LOCATION_INTERNALERROR
CCM_ERRORCODE(0x80040303)
2147746563
Internal error
CCM_E_LOCATION_BADSERVERCERT
CCM_ERRORCODE(0x80040304)
2147746564
Management point certification is corrupt from client’s perspective, which could be due to network corruption or an attacker.
CCM_E_LOCATION_BADCLIENTCERT
CCM_ERRORCODE(0x80040305)
2147746565
Client certification is corrupt from site system’s perspective, which could be due to network corruption or an attacker.
CCM_E_LOCATION_MPUNREACHABLE
CCM_ERRORCODE(0x80040306)
2147746566
Client failed to connect to management point to make a location services request (MPLIST or MPKEYINFORMATION).
CCM_E_LOCATION_PROXYMPREFRESH
CCM_ERRORCODE(0x80040307)
2147746567
Client is trying to refresh proxy management point and it’s empty. May only be called from NAP when trying to refresh the proxy management point.
CCM_E_LOCATION_LOCALMPREFRESH
CCM_ERRORCODE(0x80040308)
2147746568
Client is trying to refresh local management point and it’s empty. Only called from NAP when trying to refresh proxy management point.
CCM_E_LOCATION_MESSAGEFAILED
CCM_ERRORCODE(0x80040309)
2147746569
In most cases this indicates that the in band server authorization failed on a client, usually because the trusted root key does not match the management point certificate.

Desired Configuration Management Custom Error Codes

Error Code Description
0x80040752
E_DCM_DOTNETMISSING
Microsoft .NET Framework 2.0 or later not installed
0x80040756 E_DCM_SDM_REPORTING_FAILED
2147747670
Client failed to report state or status.
0x80040763 E_DCM_CI_INTERNAL_FAILURE
2147747683
WMI corruption or heap corruption
0x80040764
E_DCM_SDM_INTERNAL_FAILURE
WMI corruption, memory corruption, disk corruption
0x80040765
E_DCM_SDM_CLRHOST_LAUNCH_FAILURE
Problem with client installation or.NET Framework 2.0 installation

Inventory Custom Error Codes

Error Code Description
0x80040900 A valid WMI instance inventoried could not be added to the report. The __Path property may be undefined.

Mobile Device Management Custom Error Codes

Error Code Description
-2147220846
FFFFFFFF80040292
Unable to compute message signature for in-band authentication.
-2147220843
FFFFFFFF80040295
Unable to find a valid client authentication certificate for registration.
11520 Mobile device client deployment action failed. Failed to establish ActiveSync or Mobile Device Center connection to the mobile device.
11521 Mobile device client deployment action failed. Invalid client settings file.
11522 Mobile device client deployment action failed. Error determining running directory for DmClientXfer.exe
11523 Mobile device client deployment action failed. Required ActiveSync libraries missing.
11524 Mobile device client deployment action failed. Could not determine processor type of attached mobile device.
11525 Mobile device client deployment action failed. Could not determine base operating system version of attached mobile device.
11526 Mobile device client deployment action failed. Error determining client version for the attached mobile device.
11527 Mobile device client deployment action failed. Error creating client settings .ini file.
11528 Mobile device client deployment action failed. Failed to copy files to the attached mobile device.
11529 Mobile device client deployment action failed. Failed executing the mobile device client installer program on attached mobile device.
11530 Mobile device client deployment action may have failed. Failed reading status information from the mobile device.
11540 Mobile device client deployment action failed. Error determining running directory for the mobile device client installer program.
11541 Mobile device client deployment action failed. Error executing the pre-install command line.
11542 Mobile device client deployment action failed. Error executing the post-install command line.
11550 Mobile device client installation or upgrade failed. Error during removal of the previous client.
11551 Mobile device client installation or upgrade failed. Invalid client settings file.
11552 Mobile device client installation or upgrade failed. Error installing client CAB file.
11553 Mobile device client installation or upgrade failed. Error starting client service.
11554 Mobile device client installation or upgrade failed. Error updating client settings.
11555 Device Client Deployment failed with unknown error.
11560 Mobile device client verification or repair failed. Error during removal of previous client.
11561 Mobile device client verification or repair failed. Invalid client settings file.
11562 Mobile device client verification or repair failed. Error installing client CAB file.
11563 Mobile device client verification or repair failed. Error starting client service.
11564 Mobile device client verification or repair failed. Error updating client settings.
11565 Mobile device client verification or repair failed. Error restoring required files.
11566 Mobile device client privileged certificate installation failed.
11567 Encountered unknown error installing the device client.
11568 Mobile device client setup failed to launch during install.
11570 Mobile device client removal failed. Error using unload.exe to uninstall the existing client.
11571 Mobile device client install/upgrade failed. Error enforcing new client. Mobile device rolled back to old client (if existed before).
11572 Mobile device client rollback failed during unsuccessful upgrade. Error enforcing old client.
11573 Mobile device client failed to perform post cab install actions. Device client installation failed.

Operating System Deployment Custom Error Codes

Error Code Description
0x80040001 Could not get the client GUID
0x80040101 Network access account is not set
0x80040102 No content location returned for the given package
0x80040103 Could not access package content in the DP
0x80040104 Could not find reference program policy
0x80040105 Could not find CCM_ClientAgentConfig raw policy
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) An invalid image capture path has been specified.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) An invalid image file name extension has been specified.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,3) An invalid image file name extension has been specified.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,4) Image capture path is too long
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,5) An invalid image file name extension has been specified.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) Timeout waiting for PNP to finish initialization.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) Task sequence failed in Windows PE
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) An invalid network adapter index has been specified
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) Sysprep is not installed
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) Sysprep is invalid
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,3) Invalid System Partition
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,4) Machine is joined to a domain
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,5) Machine is domain controller
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) A default management point has not been assigned for this site.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) Certificates for the default management point are not available.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,3) Package
Unknown macro: {0}
is not available on the specified distribution points.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,4) Invalid password for media certificate
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,5) The media certificate does not have an associated private key
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,6) The certification authority’s certificate has not been set for this site.

Remote Tools Custom Error Codes

Error Code Description
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) Another remote control session is already in progress. Remote Control does not support multiple concurrent remote control sessions.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) Level of access allowed is set to “No Access” in the Remote Tools client agent General tab on the site server or in the Remote Control control panel applet.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,3) Remote Control Agent was not properly installed on the client.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,4) No interactive session found on the client.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,5) Remote computer screen is locked.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,6) Failed to create the RDP session.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,8) Remote Tools is disabled.
MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,9) Failed to launch the Remote Control Agent process.

Software Distribution Custom Error Codes

Error Code Description
E_FAIL_EXECUTION_PENDING 0x80008001 The program cannot be run now from the client UI because :
A restart is in progress.
or
Software Distribution is paused because of a task sequence running
or
Another program is currently running
NOTE: This error code is only returned to the UI and is not present in status messages.
E_FAIL_DUPLICATE_REQUEST 0x80008002 The program cannot be run again from the client UI because it is already pending, an optional (initiated from the UI) run request already exists for it.
NOTE: This error code is only returned to the UI and is not present in status messages.
E_SWDIST_POLICY_NOT_FOUND 0x80002004 The software distribution policy was not found.
E_FAIL_PROGRAM_DISABLED 0x80008004 The program cannot run because it is currently disabled.
E_FAIL_INVALID_POLICY 0x80008005 This error code can be returned on the client if policy cannot be found or the policy is not valid to run or cancel the requested program.
NOTE: This error code is currently not sent in status messages.
E_FAIL_INVALID_PROGRAM 0x80008006 The requested program is not currently pending.
This error code can be returned on the client if the user attempts to continue or cancel the program that is not currently pending. It can also be returned to the task sequence manager (TSM) when TSM requests download locations for packages that are not referenced by the currently running task sequence.
NOTE: This error code is not raised in status messages by Software distribution, but could be raised by task sequence.
E_FAIL_SET_CACHEDCONTENTINUSE 0x80008008 Unable to set the CachedContentInUse flag. Failed to indicate the client cache is currently in use.
E_FAIL_WMI_ERROR 0x80008009 Failed to read data from WMI. The program could not continue because a system restart is in progress or there is already a run request for this program that requires a reboot.
E_FAIL_REQUEST_NOT_FOUND 0x80008011 Used for Task Sequence. Failed to reconnect to Task Sequence job because a request cannot be found with the given job ID.
NOTE: Not sent in status message by Software Distribution, but may be used by task sequence.
E_FAIL_ACTIVE_REQUEST_NOT_FOUND 0x80008012 There is no program currently running.
This error code is returned to task sequence when there is no run request that is currently running, but task sequence tries to get the currently running request.
E_FAIL_DEPENDENCY_NOT_RUN 0x80008013 This program cannot run because it depends on another program that has not run successfully before. This error code is returned to task sequence manager when a task sequence Install Software Action step cannot be run because the step has a child program which has not been run before.
E_FAIL_USER_REQUIRED
0x80008014
This error code is returned to task sequence manager when an “Install Software” step cannot be run because the software distribution program in this step is targeted to a user, requires user input or is set to run in user context
E_FAIL_SWD_NOT_PAUSED
0x80008015
Failed to notify caller that software distribution is paused because the paused state or paused cookie do not match.
E_FAIL_INVALID_HASH
0x80008017
The content hash string or hash versions are empty or incorrect in the software distribution policy or the hash verification failed.
E_FAIL_CANNOT_RUN_ON_INTERNET 0x80008018 The program cannot run at this time because the client is on the internet.
E_FAIL_EXECUTION_NONFATAL 0x80008100 A non fatal error has been encountered while attempting to run the program. The program execution will be retried if the retry count has not been exceeded.
E_FAIL_BAD_ENVIRONMENT_NONFATAL 0x80008103 A non fatal error occurred while preparing to run the program, for example when creating the program execution environment, making a network connection, impersonating the user, determining the file association information, or when attempting to launch the program. This program execution will be retried if the retry count has not been exceeded.
E_FAIL_PROGRAM_NOT_MONITORED 0x80008105 An error was encountered while getting the process information for the launched program and the program execution will not be monitored.
E_FAIL_BAD_ENVIRONMENT_FATAL 0x8000910A A fatal error occurred while preparing to run the program, for example when creating the program execution environment, making a network connection, impersonating the user, determining the file association information, or when attempting to launch the program. This program execution will not be retried.
E_FAIL_EXECUTION_FATAL
0x80009101
A fatal error has been encountered while attempting to run the program. The program execution will not be retried.
E_FAIL_INVALID_PROGRAM_OBJECT 0x80009102 An error occurred while creating the execution context.
This is error code indicates that an error was encountered while creating the internal execution context object. This is most likely not due to configuration errors, but could be because of low memory conditions, COM failures or other external errors.
E_FAIL_INVALID_CMDLINE 0x80009104 The command line for this program is invalid.
E_FAIL_NO_CONTENT 0x80009106 Failed to verify the executable file is valid or to construct the associated command line.
E_FAIL_NO_SOURCE 0x80008107 Failed to access all the provided program locations. This program may retry if the maximum retry count has not been reached.
E_INVALID_CONTENT_REQUEST_HANDLE 0x80008200 This is an internal error. No content request found with the given handle.
E_NO_SPACE_IN_CACHE 0x80008201 The content download cannot be performed because there is not enough available space in cache or the disk is full.
E_CACHE_TOO_SMALL 0x80008202 The content download cannot be performed because the total size of the client cache is smaller than the size of the requested content.
E_CACHE_IN_USE 0x80008203 The client cache is currently in use by a running program or by a download in progress.
E_NO_DP_FOUND 0x80008204 NOTE: this error code is sent at least in status message 10051.
No distribution points were found for the requested content.
E_FAIL_LOCATION_REQUEST 0x80008210 Failed to get content locations.
E_FAIL_JOB_PENDING 0x80008250 The computer restart cannot be initiated because a software installation job is in progress.
E_FAIL_INACCESSIBLE_SOURCE 0x80009108 Failed to access all the provided program locations. This program will not retry.
E_FAIL_INVALID_MSI 0x80009109 Failed to verify that the given file is a valid installation package.

Software Updates Custom Error Codes

Error Code Description
E_UPDDEPLOY_APPLY_NOT_REQUIRED
CCM_ERRORCODE(0x80040708)
2147747592
Software Updates Install not required.
E_MONITOR_RESUME_FAILURE
CCM_ERRORCODE(0x80040709)
2147747593
Failed to resume the monitoring of the process.
E_INVALID_CMDLINE
CCM_ERRORCODE(0x8004070A)
2147747594
Invalid command line
E_CREATEPROCESS_FAILURE
CCM_ERRORCODE(0x8004070B)
2147747595
Failed to create process
E_EXECUTION_TIMEOUT
CCM_ERRORCODE(0x8004070C)
2147747596
Software update execution timeout
E_UPDATE_FAILED_RESULT
CCM_ERRORCODE(0x8004070D)
2147747597
Software update failed when attempted
E_EMPTY_COMMANDLINE
CCM_ERRORCODE(0x8004070E)
2147747598
Empty command line specified
E_INVALID_INSTALLER_PATH
CCM_ERRORCODE(0x8004070F)
2147747599
Invalid updates installer path
E_COMPARE_CREATION_TIMES
CCM_ERRORCODE(0x80040710)
2147747600
Failed to compare process creation time.
E_DEPLOYMENT_NOT_ACTIVE
CCM_ERRORCODE(0x80040711)
2147747601
Software updates deployment not active yet for example, start time is in future
E_UPDDEPLOY_REBOOT_REQUIRED
CCM_ERRORCODE(0x80040712)
2147747602
A system restart is required to complete the installation.
E_NO_DETECT_RESULT
CCM_ERRORCODE(0x80040713)
2147747603
Software updates detection results not received yet.
E_UPDATES_USERINSTALL_RESTART_PENDING
CCM_ERRORCODE(0x80040714)
2147747604
User based install not allowed as system restart is pending.
E_USERINSTALL_NO_UPDATES
CCM_ERRORCODE(0x80040715)
2147747605
No applicable updates specified in user install request.
E_NOINTERFACE
FFFFFFFF80004002
-2147467262
No such interface supported
[DCOM belly up] CAgent::CreateJob failed
FFFFFFFF8007000E
-2147024882
Not enough storage is available to complete this operation.
ERROR_TIMEOUT
FFFFFFFF800705B4
-2147023436
This operation returned because the timeout period expired.
[Scan fails on x64vista] OnSearchComplete
0x80240032[WU]
-2145124302
Failed to end search job [SMS] WU client failed Searching for update with error.
WU_E_PT_WINHTTP_NAME_NOT_RESOLVED Same as –
ERROR_WINHTTP_NAME_NOT_RESOLVED FFFFFFFF8024402C
-2145107924
The proxy server or target server name cannot be resolved.
FFFFFFFF80040692
-2147219822
Group Policy conflict
FFFFFFFF80040693
-2147219821
Low WUA version
WU_E_PT_HTTP_STATUS_BAD_GATEWAY
FF80244021
-2145107935
Same as HTTP status 502. The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
-939523070
ERROR_OBJECT_ALREADY_EXISTS
FFFFFFFFC8000402
Object already exists
[SA fail if SWD not working] createInstance failed for UpdateServiceManager FFFFFFFF80040154
-2147221164
Class not registered
FFFFFFFF800705B4
-2147023436
This operation returned because the timeout period expired.
ERROR_INTERNET_TIMEOUT
FFFFFFFF80072EE2
-2147012894
Internet timeout
ERROR_WINHTTP_CANNOT_CONNECT or ERROR_INTERNET_CANNOT_CONNECT
FFFFFFFF80072EFD
-2147012867
Internet cannot connect
E_INVALIDSTATE_AFTER_APPLY
FFFFFFFF80040668
-2147219864
Software update still detected as actionable after apply.
E_EXECUTION_TIMEOUT
FFFFFFFF8004070C
-2147219700
Software update execution timeout
WU_E_PT_WINHTTP_NAME_NOT_RESOLVED – same as ERROR_WINHTTP_NAME_NOT_RESOLVED
FFFFFFFF8024402C
-2145107924
The proxy server or target server name cannot be resolved.
ERROR_PATH_NOT_FOUND
FFFFFFFF80070003
-2147024893
The system cannot find the path specified.
ERROR_FILE_EXISTS
FFFFFFFF80070050
-2147024816
The file exists
ERROR_ACCESS_DENIED or E_ACCESS_DENIED
FFFFFFFF80070005
-2147024891
Access denied
WU_E_PT_WINHTTP_NAME_NOT_RESOLVED Same as ERROR_WINHTTP_NAME_NOT_RESOLVED
FFFFFFFF8024402C
-2145107924
The proxy server or target server name cannot be resolved.
ERROR_INAVILD_ENVIROMENT
FFFFFFFF8004070D
-2147219699
Software update failed when attempted.
Install Errors
-Last Install Error
FF8024402C WU_E_PT_WINHTTP_NAME_NOT_RESOLVED – same as ERROR_WINHTTP_NAME_NOT_RESOLVED
2145107924
The proxy server or target server name cannot be resolved.
Last Install Error
FF8007066F
ERROR_PATCH_NOT_APPLIED
-2147023249
Can sometimes happen when Windows Installer configuration for an installed application is out of sequence for example, Windows Installer thinks it has more patches applied than is really the case (this sometimes used to happen with roaming profiles).
Last Install Error
FF8007064
ERROR_INSTALL_FAILURE
-2147023293
Generic failure code from Windows Installer installs.
Last Install Error
FF8007F0F4
STATUS_PREREQUISITE_FAILED
-2146963212
Generated by update.exe. People seem to be getting this when they try to install a Service Pack while on battery power.
Last Install Error
FF8007F0F5
WU_E_DM_INCORRECTFILEHASH
-2146963211
The WU Agent’s metadata store and the policy received by ccmexec could be out of sync.
Last Install Error
FF8007F0F6
ERROR INVALID PARAMETER
-2146963212
Failed to start the installation of updates because update is not found
Scan Failures
Last Scan Error
FF80244021
WU_E_PT_HTTP_STATUS_BAD_GATEWAY
-2145107935
Possible network connectivity issues
Last Scan Error
FF8024001D
WU_E_INVALID_UPDATE
-2145124323
An update contains invalid metadata.
Last Scan Error
FF80004002
E_NOINTERFACE
-2147467262
No such interface supported
Last Scan Error
FFC8000402
RECORD TOO BIG
-939523070
This seems to be a recoverable error, and possibly due to many Scan Service Packages left around when the 2003 ITMU was used. This is NOT the case.
FF8024400A
WU_E_PT_SOAPCLIENT_PARSE
1097366519818
Needs update
Last Scan Error
WU_E_SERVICE_STOP
FF8024001E
-2145124322
Operation did not complete because the service or system was being shut down.
Last Scan Error
FF8024400D
WU_E_PT_SOAP_CLIENT
-2145107955
SOAP client found the message was malformed.
Last Scan Error
FFC800042D
RefreshServerUpdateInfo
-939523027
WSUS unable to update software distribution folder. Scans fail.
Last Scan Error
FF80244022
WU_E_PT_HTTP_STATUS_SERVICE_UNAVAIL
-2145107934
HTTP status 503. The service is temporarily overloaded.
Last Scan Error
FF80240032
WU_E_INVALID_CRITERIA
-2145124302
The search criteria string was invalid.
Last Scan Error
FF80240013
WU_E_DUPLICATE_ITEM
-2145124333
Failed to add file to the FileLocationList.
Last Scan Error
FF8007041D
ERROR SERVICE REQUEST TIMEOUT
-2147023843
The service did not respond to the start or control request in a timely fashion.
E_FAIL_POLICY_NOT_FOUND
CCM_ERRORCODE(0x80040600)
2147747328
Scan Tool Policy not found
E_LOCATION_TIMEOUT
CCM_ERRORCODE(0x80040602)
2147747330
Out of cache space
E_SCANTOOL_POLICY_REMOVED
CCM_ERRORCODE(0x80040603)
2147747331
The ScanTool Policy has been removed so cannot complete Scan Operation.
E_SCANTOOL_NOTFOUND_INJOBQUEUE
CCM_ERRORCODE(0x80040604)
2147747332
The ScanTool was not found in the job queue.
E_FAIL_SCAN_TOOL_REMOVED
CCM_ERRORCODE(0x80040605)
2147747333
Scan Tool has been Removed
E_FAIL_OFFLINE_SCAN_HISTORY_NOT_FOUND
CCM_ERRORCODE(0x80040606)
2147747334
Scan Tool Policy not found
E_CONTENT_NOT_FOUND
CCM_ERRORCODE(0x80040607)
2147747335
Out of cache space
E_INVALID_INSTANCE_TYPE
CCM_ERRORCODE(0x80040608)
2147747336
Out of cache space
E_NO_SPACE_IN_CACHE
0x80008201
2147516929
Out of cache space
E_CACHE_TOO_SMALL
0x80008202
2147516930
Cache size is smaller than requested content’s size.
Deployments Agent Specific Errors
E_UPDDEPLOY_APPLY_NOT_ALLOWED CCM_ERRORCODE(0x80040700)
2147747584
Install not allowed
E_UPDDEPLOY_DOWNLOAD_NOT_ALLOWED CCM_ERRORCODE(0x80040701)
2147747585
Download not allowed
E_ASSIGNMENT_POLICY_NOT_FOUND
CCM_ERRORCODE(0x80040702)
2147747586
Assignment policy not available
E_ANOTHER_JOB_IN_PROGRESS
CCM_ERRORCODE(0x80040703)
2147747587
Only one job is allowed at a time
E_HARDREBOOT_PENDING
CCM_ERRORCODE(0x80040704)
2147747588
Only one job is allowed at a time.
2147747589
E_PAUSE_STATE_REQUIRED
CCM_ERRORCODE(0x80040705)
Pause state required
2147747590
E_NO_ACTIVE_JOB
CCM_ERRORCODE(0x80040706)
No active job exists (while reconnect called).
2147747591
E_JOB_ID_MISMATCH
CCM_ERRORCODE(0x80040707)
Job Id mismatch (while reconnect called).
Categories: SCCM / SMS Tags: , ,

Building a custom Windows PE Image

January 25th, 2011 No comments

The first step in creating a customized Windows® PE 3.0 image is to modify the base Windows PE image (winpe.wim) by using the Deployment Image Servicing and Management (DISM) tool. DISM extracts the files to a local directory and enables you to add and remove packages (optional components and language packs). In addition, you can add out-of-box drivers. DISM provides the same mounting and unmounting operations as ImageX.

The general process for creating a custom Windows PE image includes:
1. Mount the base image by using the DISM tool to a local directory share. For example,

Dism /Mount-Wim /WimFile:C:\winpe_x86\winpe.wim /index:1 /MountDir:C:\winpe_x86\mount

2. Using the Dism command with the /Get-Package option to see which packages are installed. For example,

Dism /image:C:\winpe_x86\mount /Get-Packages

3. Add packages, and language packs as appropriate by using the Dism command with the /Add-Package option. For example, to add the HTA package you must add both the language neutral package along with the language specific package. For example:

Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\<version>\Tools\PETools\x86\WinPE_FPs\WinPE-HTA.cab"
Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\<version>\Tools\PETools\x86\WinPE_FPs\en-us\WinPE-HTA_en-us.cab"

Where <version> can be the OEM Preinstallation Kit (OPK) or the Automated Installation Kit (AIK).
4. Add drivers as appropriate by using the Dism command with the /Add-Driver option. For example:

Dism /image:C:\winpe_x86\mount /Add-Driver /driver:C:\test\drivers\mydriver.inf

5. Add any additional custom files or tools that you intend to include in the image within the \mount directory. For example, you can include ImageX within your image,

copy "C:\Program Files\<version>\Tools\x86\imagex.exe" C:\winpe_x86\mount\Windows\System32\

Where <version> can be Windows OPK or Windows AIK.
6. Commit the changes using the Dism command with the /Unmount-Wim /Commit option. For example,

Dism /Unmount-Wim /MountDir:C:\winpe_x86\mount /Commit

7. Copy your custom image into \ISO\sources folder and rename to boot.wim. For example,

copy c:\winpe_x86\winpe.wim c:\winpe_x86\ISO\sources\boot.wim
Categories: SCCM / SMS Tags: , ,

SCCM Log file locations

January 25th, 2011 No comments

Operating System Deployment Log Files

The following table provides information about the log files and their default locations that are created when using Configuration Manager 2007 operating system deployment.

Log File Name Description
CCMSetup.log Provides information about client-based operating system actions.
Log file location:
%Windir%\System32\Ccmsetup
CreateTSMedia.log Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.
Log file location:
<ConfigMgrInstallationPath>\AdminUI\AdminUILog
Dism.log Provides information about drivers installed during operating system deployment.
Configuration Manager 2007 SP2 installs drivers by using the Deployment Image Servicing and Management (DISM) tool in Windows Automated Installation (AIK) 2.0.
Log file location:
%Temp%\SMSTSLOG\Dism.log
DriverCatalog.log Provides information about device drivers that have been imported into the driver catalog.
Log file location:
<ConfigMgrInstallationPath>\Logs
MP_ClientIDManager.log Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.
Log file location:
<ConfigMgrInstallationPath>\SMS_CCM\Logs
MP_DriverManager.log Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.
Log file location:
<ConfigMgrInstallationPath>\SMS_CCM\Logs
MP_Location.log Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.
Log file location:
<ConfigMgrInstallationPath>\SMS_CCM\Logs
PkgMgr.log Provides information about drivers installed during operating system deployment.
Configuration Manager 2007 SP1 installs drivers by using the Package Manager tool.
Log file location:
%Temp%\SMSTSLOG\Pkgmgr.log
Pxecontrol.log Provides information about the PXE Control Manager.
Log file location:
<ConfigMgrInstallationPath>\Logs
PXEMsi.log Provides information about the PXE service point and is generated when the PXE service point site server has been created.
Log file location:
<ConfigMgrInstallationPath>\Logs
PXESetup.log Provides information about the PXE service point and is generated when the PXE service point site server has been created.
Log file location:
<ConfigMgrInstallationPath>\Logs
Setupact.log, Setupapi.log, Setuperr.log Provides information about Windows Sysprep and Setup logs.
Log file location:
%Windir%
SmpIsapi.log Provides information about the state migration point Configuration Manager 2007 client request responses.
Log file location:
<InstallationPath>\SMS_CCM\Logs
Smpmgr.log Provides information about the results of state migration point health checks and configuration changes.
Log file location:
<ConfigMgrInstallationPath>\Logs
SmpMSI.log Provides information about the state migration point and is generated when the state migration point site server has been created.
Log file location:
<ConfigMgrInstallationPath>\Logs
Smsprov.log Provides information about the SMS Provider.
Log file location:
<ConfigMgrInstallationPath>\Logs
Smspxe.log Provides information about the Configuration Manager 2007 PXE service point.
Log file location:
<ConfigMgrInstallationPath>\Sms_ccm\Logs
SMSSMPSetup.log Provides information about the state migration point and is generated when the state migration point site server has been created.
Log file location:
<ConfigMgrInstallationPath>\Logs
Smsts.log General location for all operating system deployment and task sequence log events.
Log file location:

  • If task sequence completes when running in the full operating system with an Configuration Manager 2007 client installed on the computer: <ConfigMgrInstallationPath>\Logs
  • If a task sequence is completed when running in the full operating system with no Configuration Manager 2007 client installed on the computer: %temp%\SMSTSLOG
  • If a task sequence is completed when running in Windows PE: <largest fixed partition>\SMSTSLOG
Note
<ConfigMgrInstallationPath> is %Windir%\System32\Ccm\Logs for most Configuration Manager 2007 clients and <ConfigMgrInstallationPath>\SMS_CCM for the Configuration Manager 2007 site server.
TaskSequenceProvider.log Provides information about task sequences when they are imported, exported, or edited.
Log file location:
<ConfigMgrInstallationPath>\Logs
USMT Log loadstate.log Provides information about the User State Migration Tool (USMT) regarding the restoring of user state data.
Log file location:
%Windir%\System32\Ccm\Logs
USMT Log scanstate.log Provides information about the User State Migration Tool (USMT) regarding the capture of user state data.
Log file location:
%Windir%\System32\Ccm\Logs
Categories: SCCM / SMS Tags: , ,