Ever wondered when running a Software Inventory you dont get the info back you wanted ??

ok so imagine you have a piece of software installed on X amount of clients out there, you need to know what clients have this installed software and the software inventory is not reporting back what you would expect. i.e you know there is clients showing in add remove programs as having the software but your query is not reporting them back.

 

the reason for this because the software inventory does not include the add the remove programs, this is collated and reported back via the hardware inventory.

 

you can check the classes that hardware inventory reports back via resource explorer.

See below:-

Complete list of log files for SCCM 2007

Client Log Files

* CAS – Content Access Service. Maintains the local package cache.
* Ccmexec.log – Records activities of the client and the SMS Agent Host service.
* CertificateMaintenance.log – Maintains certificates for Active Directory directory service and management points.
* ClientIDManagerStartup.log – Creates and maintains the client GUID.
* ClientLocation.log – Site assignment tasks.
* ContentTransferManager.log – Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.
* DataTransferService.log – Records all BITS communication for policy or package access.
* Execmgr.log – Records advertisements that run.
* FileBITS.log – Records all SMB package access tasks.
* Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) – Windows Management Instrumentation (WMI) provider for software inventory and file collection.
* InventoryAgent.log – Creates discovery data records (DDRs) and hardware and software inventory records.
* LocationServices.log – Finds management points and distribution points.
* Mifprovider.log – The WMI provider for .MIF files.
* Mtrmgr.log – Monitors all software metering processes.
* PolicyAgent.log – Requests policies by using the Data Transfer service.
* PolicyAgentProvider.log – Records policy changes.
* PolicyEvaluator.log – Records new policy settings.
* Remctrl.log – Logs when the remote control component (WUSER32) starts.
* Scheduler.log – Records schedule tasks for all client operations.
* Smscliui.log – Records usage of the Systems Management tool in Control Panel.
* StatusAgent.log – Logs status messages that are created by the client components.
* SWMTRReportGen.log – Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

Server Log Files

* Ccm.log – Client Configuration Manager tasks.
* Cidm.log – Records changes to the client settings by the Client Install Data Manager (CIDM).
* Colleval.log – Logs when collections are created, changed, and deleted by the Collection Evaluator.
* Compsumm.log – Records Component Status Summarizer tasks.
* Cscnfsvc.log – Records Courier Sender confirmation service tasks.
* Dataldr.log – Processes Management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.
* Ddm.log – Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager.
* Despool.log – Records incoming site-to-site communication transfers.
* Distmgr.log – Records package creation, compression, delta replication, and information updates.
* Hman.log – Records site configuration changes, and publishes site information in Active Directory Domain Services.
* Inboxast.log – Records files that are moved from the management point to the corresponding SMS\INBOXES folder.
* Inboxmgr.log – Records file maintenance.
* Invproc.log – Records the processing of delta MIF files for the Dataloader component from client inventory files.
* Mpcontrol.log – Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.
* Mpfdm.log – Management point component that moves client files to the corresponding SMS\INBOXES folder.
* MPMSI.log – Management point .msi installation log.
* MPSetup.log – Records the management point installation wrapper process.
* Ntsvrdis.log – Configuration Manager 2007 server discovery.
* Offermgr.log – Records advertisement updates.
* Offersum.log – Records summarization of advertisement status messages.
* Policypv.log – Records updates to the client policies to reflect changes to client settings or advertisements.
* Replmgr.log – Records the replication of files between the site server components and the Scheduler component.
* Rsetup.log – Reporting point setup log.
* Sched.log – Records site-to-site job and package replication.
* Sender.log – Records files that are sent to other child and parent sites.
* Sinvproc.log – Records client software inventory data processing to the site database in Microsoft SQL Server.
* Sitecomp.log – Records maintenance of the installed site components.
* Sitectrl.log – Records site setting changes to the Sitectrl.ct0 file.
* Sitestat.log – Records the monitoring process of all site systems.
* Smsdbmon.log – Records database changes.
* Smsexec.log – Records processing of all site server component threads.
* Smsprov.log – Records WMI provider access to the site database.
* SMSReportingInstall.log – Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.
* SMSSHVSetup.log – Records the success or failure (with failure reason) of installing the System Health Validator point.
* Srvacct.log – Records the maintenance of accounts when the site uses standard security.
* Statmgr.log – Writes all status messages to the database.
* Swmproc.log – Processes metering files and maintains settings.

Admin Console Log Files

* RepairWizard.log – Records errors, warnings, and information about the process of running the Repair Wizard.
* ResourceExplorer.log – Records errors, warnings, and information about running the Resource Explorer.
* SMSAdminUI.log – Records the local Configuration Manager 2007 console tasks when you connect to Configuration Manager 2007 sites.

Management Point Log Files

* MP_Ddr.log – Records the conversion of XML.ddr records from clients, and copies them to the site server.
* MP_GetAuth.log – Records the status of the site management points.
* MP_GetPolicy.log – Records policy information.
* MP_Hinv.log – Converts XML hardware inventory records from clients and copies the files to the site server.
* MP_Location.log – Records location manager tasks.
* MP_Policy.log – Records policy communication.
* MP_Relay.log – Copies files that are collected from the client.
* MP_Retry.log – Records the hardware inventory retry processes.
* MP_Sinv.log – Converts XML hardware inventory records from clients and copies them to the site server.
* MP_Status.log – Converts XML.svf status message files from clients and copies them to the site server.

Mobile Device Management Log Files

* DmClientHealth.log – Records the GUIDs of all the mobile device clients that are communicating with the Device Management Point.
* DmClientRegistration.log – Records registration requests from and responses to the mobile device client in Native mode.
* DmpDatastore.log – Records all the site database connections and queries made by the Device Management Point.
* DmpDiscovery.log – Records all the discovery data from the mobile device clients on the Device Management Point.
* DmpFileCollection.log – Records mobile device file collection data from mobile device clients on the Device Management Point.
* DmpHardware.log – Records hardware inventory data from mobile device clients on the Device Management Point.
* DmpIsapi.log – Records mobile device communication data from device clients on the Device Management Point.
* dmpMSI.log – Records the MSI data for Device Management Point setup.
* DMPSetup.log – Records the mobile device management setup process.
* DmpSoftware.log – Records mobile device software distribution data from mobile device clients on the Device Management Point.
* DmpStatus.log – Records mobile device status messages data from mobile device clients on the Device Management Point.
* FspIsapi.log – Records Fallback Status Point communication data from mobile device clients and client computers on the Fallback Status Point.

Mobile Device Client Log Files

* DmCertEnroll.log – Records certificate enrollment data on mobile device clients.
* DMCertResp.htm (in \temp) – Records HTML response from the certificate server when the mobile device Enroller program requests a client authentication certificate on mobile device clients.
* DmClientSetup.log – Records client setup data on mobile device clients.
* DmClientXfer.log – Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.
* DmCommonInstaller.log – Records client transfer file installation for setting up mobile device client transfer files on client computers.
* DmInstaller.log – Records whether DMInstaller correctly calls DmClientSetup and whether DmClientSetup exits with success or failure on mobile device clients.
* DmInvExtension.log – Records Inventory Extension file installation for setting up Inventory Extension files on client computers.
* DmSvc.log – Records mobile device management service data on mobile device clients.

Operating System Deployment Log Files

* CCMSetup.log – Provides information about client-based operating system actions.
* 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.
* DriverCatalog.log – Provides information about device drivers that have been imported into the driver catalog.
* 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.
* 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.
* 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.
* Pxecontrol.log – Provides information about the PXE Control Manager.
* PXEMsi.log – Provides information about the PXE service point and is generated when the PXE service point site server has been created.
* PXESetup.log – Provides information about the PXE service point and is generated when the PXE service point site server has been created.
* Setupact.log Setupapi.log Setuperr.log Provide information about Windows Sysprep and setup logs.
* SmpIsapi.log – Provides information about the state migration point Configuration Manager 2007 client request responses.
* Smpmgr.log – Provides information about the results of state migration point health checks and configuration changes.
* SmpMSI.log – Provides information about the state migration point and is generated when the state migration point site server has been created.
* Smsprov.log – Provides information about the SMS provider.
* Smspxe.log – Provides information about the Configuration Manager 2007 PXE service point.
* SMSSMPSetup.log – Provides information about the state migration point and is generated when the state migration point site server has been created.
* Smsts.log – General location for all operating system deployment and task sequence log events.
* TaskSequenceProvider.log – Provides information about task sequences when they are imported, exported, or edited.
* USMT Log loadstate.log – Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.
* USMT Log scanstate.log – Provides information about the USMT regarding the capture of user state data.

Network Access Protection Log Files

* Ccmcca.log – Logs the processing of compliance evaluation based on Configuration Manager NAP policy processing and contains the processing of remediation for each software update required for compliance.
* CIAgent.log – Tracks the process of remediation and compliance. However, the software updates log file, *Updateshandler.log – provides more informative details on installing the software updates required for compliance.
* locationservices.log – Used by other Configuration Manager features (for example, information about the client’s assigned site) but also contains information specific to Network Access Protection when the client is in remediation. It records the names of the required remediation servers (management point, software update point, and distribution points that host content required for compliance), which are also sent in the client statement of health.
* SDMAgent.log – Shared with the Configuration Manager feature desired configuration management and contains the tracking process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance.
* SMSSha.log – The main log file for the Configuration Manager Network Access Protection client and contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.

System Health Validator Point Log Files

* Ccmperf.log -Contains information about the initialization of the System Health Validator point performance counters.
* SmsSHV.log – The main log file for the System Health Validator point; logs the basic operations of the System Health Validator service, such as the initialization progress.
* SmsSHVADCacheClient.log – Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.
* SmsSHVCacheStore.log – Contains information about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.
* SmsSHVRegistrySettings.log – Records any dynamic changes to the System Health Validator component configuration while the service is running.
* SmsSHVQuarValidator.log – Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL

Desired Configuration Management Log Files

* ciagent.log – Provides information about downloading, storing, and accessing assigned configuration baselines.
* dcmagent.log – Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes.
* discovery.log – Provides detailed information about the Service Modeling Language (SML) processes.
* sdmagent.log – Provides information about downloading, storing, and accessing configuration item content.
* sdmdiscagent.log – Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items.

Wake On LAN Log Files

* Wolmgr.log – Contains information about wake-up procedures such as when to wake up advertisements or deployments that are configured for Wake On LAN.
* WolCmgr.log – Contains information about which clients need to be sent wake-up packets, the number of wake-up packets sent, and the number of wake-up packets retried.

Software Updates Site Server Log Files

* ciamgr.log – Provides information about the addition, deletion, and modification of software update configuration items.
* distmgr.log – Provides information about the replication of software update deployment packages.
* objreplmgr.log – Provides information about the replication of software updates notification files from a parent to child sites.
* PatchDownloader.log – Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server.
* replmgr.log – Provides information about the process for replicating files between sites.
* smsdbmon.log – Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.
* SUPSetup – Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.
* WCM.log – Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.
* WSUSCtrl.log – Provides information about the configuration, database connectivity, and health of the WSUS server for the site.
* wsyncmgr.log -Provides information about the software updates synchronization process.

WSUS Server Log Files

* Change.log – Provides information about the WSUS server database information that has changed.
* SoftwareDistribution.log – Provides information about the software updates that are synchronized from the configured update source to the WSUS server database.

Software Updates Client Computer Log Files

* CAS.log – Provides information about the process of downloading software updates to the local cache and cache management.
* CIAgent.log – Provides information about processing configuration items, including software updates.
* LocationServices.log – Provides information about the location of the WSUS server when a scan is initiated on the client.
* PatchDownloader.log – Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
* PolicyAgent.log – Provides information about the process for downloading, compiling, and deleting policies on client computers.
* PolicyEvaluator – Provides information about the process for evaluating policies on client computers, including policies from software updates.
* RebootCoordinator.log – Provides information about the process for coordinating system restarts on client computers after software update installations.
* ScanAgent.log – Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
* ScanWrapper – Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.
* SdmAgent.log – Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.
* ServiceWindowManager.log – Provides information about the process for evaluating configured maintenance windows.
* smscliUI.log – Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.
* SmsWusHandler – Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.
* StateMessage.log – Provides information about when software updates state messages are created and sent to the management point.
* UpdatesDeployment.log – Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
* UpdatesHandler.log – Provides information about software update compliance scanning and about the download and installation of software updates on the client.
* UpdatesStore.log – Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.
* WUAHandler.log – Provides information about when the Windows Update Agent on the client searches for software updates.
* WUSSyncXML.log – Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

Windows Update Agent Log File

* WindowsUpdate.log – Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.

SCCM 2012 servers up and running

Started setting up a new SCCM 2012 infrastructure before christmas and its looking good, all working like it should.

 

more info to follow.

 

happy new year everyone.

Retired or dead distribution point issues

OK imagine this or in my case this really happened, we had major issues with a DP in our SCCM server farm. without going into to much depth the DP in question was retired, i removed the roles and cleared it from the systems, low and behold though the packages was still showing the DP as and was trying to install a fresh copy. you manage the DP’s and its not list as being active but the packages still think it is.

i created this script out of multiple scripts i found around the net to try and remove the retired DP a after many hours editing and re-writing i got this to work, so here it is feel free to use as this proved really help full.

DPclean

remember to download the above and rename to DPClean.vbs

MBAM up and running, great edition to our enterprise setup.

the console up and running……

Key Concepts of User Centric Application Delivery in Configuration Manager 2012: Part 1

Check out Bill Anderson’s blog post, Principal Program Manager Lead for System Center Configuration Manager, where he kicks off a two part blog series that touches on the five key conceptual changes in ConfigMgr 2012 that will fundamentally change the way that you think about delivering applications in the future.

http://blogs.technet.com/b/server-cloud/archive/2011/11/01/key-concepts-of-user-centric-application-delivery-in-configuration-manager-2012-part-1.aspx

MSI Error Codes

we have been repackaging software within our organisation and creating MSI installers via admin studio, the main issue we came across was understanding MSI error codes within the logs files

So ive put this up today to help with this headache.

Enjoy

Error code	Value	Description
ERROR_SUCCESS	0	The action completed successfully.
ERROR_INVALID_DATA	13	The data is invalid.
ERROR_INVALID_PARAMETER	87	One of the parameters was invalid.
ERROR_CALL_NOT_IMPLEMENTED	120	This value is returned when a custom action attempts to call a function that cannot be called from custom actions. The function returns the value ERROR_CALL_NOT_IMPLEMENTED. Available beginning with Windows Installer version 3.0.
ERROR_APPHELP_BLOCK	1259	If Windows Installer determines a product may be incompatible with the current operating system, it displays a dialog box informing the user and asking whether to try to install anyway. This error code is returned if the user chooses not to try the installation.
ERROR_INSTALL_SERVICE_FAILURE	1601	The Windows Installer service could not be accessed. Contact your support personnel to verify that the Windows Installer service is properly registered.
ERROR_INSTALL_USEREXIT	1602	The user cancels installation.
ERROR_INSTALL_FAILURE	1603	A fatal error occurred during installation.
ERROR_INSTALL_SUSPEND	1604	Installation suspended, incomplete.
ERROR_UNKNOWN_PRODUCT	1605	This action is only valid for products that are currently installed.
ERROR_UNKNOWN_FEATURE	1606	The feature identifier is not registered.
ERROR_UNKNOWN_COMPONENT	1607	The component identifier is not registered.
ERROR_UNKNOWN_PROPERTY	1608	This is an unknown property.
ERROR_INVALID_HANDLE_STATE	1609	The handle is in an invalid state.
ERROR_BAD_CONFIGURATION	1610	The configuration data for this product is corrupt. Contact your support personnel.
ERROR_INDEX_ABSENT	1611	The component qualifier not present.
ERROR_INSTALL_SOURCE_ABSENT	1612	The installation source for this product is not available. Verify that the source exists and that you can access it.
ERROR_INSTALL_PACKAGE_VERSION	1613	This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.
ERROR_PRODUCT_UNINSTALLED	1614	The product is uninstalled.
ERROR_BAD_QUERY_SYNTAX	1615	The SQL query syntax is invalid or unsupported.
ERROR_INVALID_FIELD	1616	The record field does not exist.
ERROR_INSTALL_ALREADY_RUNNING	1618	Another installation is already in progress. Complete that installation before proceeding with this install.For information about the mutex, see _MSIExecute Mutex.
ERROR_INSTALL_PACKAGE_OPEN_FAILED	1619	This installation package could not be opened. Verify that the package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer package.
ERROR_INSTALL_PACKAGE_INVALID	1620	This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
ERROR_INSTALL_UI_FAILURE	1621	There was an error starting the Windows Installer service user interface. Contact your support personnel.
ERROR_INSTALL_LOG_FAILURE	1622	There was an error opening installation log file. Verify that the specified log file location exists and is writable.
ERROR_INSTALL_LANGUAGE_UNSUPPORTED	1623	This language of this installation package is not supported by your system.
ERROR_INSTALL_TRANSFORM_FAILURE	1624	There was an error applying transforms. Verify that the specified transform paths are valid.
ERROR_INSTALL_PACKAGE_REJECTED	1625	This installation is forbidden by system policy. Contact your system administrator.
ERROR_FUNCTION_NOT_CALLED	1626	The function could not be executed.
ERROR_FUNCTION_FAILED	1627	The function failed during execution.
ERROR_INVALID_TABLE	1628	An invalid or unknown table was specified.
ERROR_DATATYPE_MISMATCH	1629	The data supplied is the wrong type.
ERROR_UNSUPPORTED_TYPE	1630	Data of this type is not supported.
ERROR_CREATE_FAILED	1631	The Windows Installer service failed to start. Contact your support personnel.
ERROR_INSTALL_TEMP_UNWRITABLE	1632	The Temp folder is either full or inaccessible. Verify that the Temp folder exists and that you can write to it.
ERROR_INSTALL_PLATFORM_UNSUPPORTED	1633	This installation package is not supported on this platform. Contact your application vendor.
ERROR_INSTALL_NOTUSED	1634	Component is not used on this machine.
ERROR_PATCH_PACKAGE_OPEN_FAILED	1635	This patch package could not be opened. Verify that the patch package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer patch package.
ERROR_PATCH_PACKAGE_INVALID	1636	This patch package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer patch package.
ERROR_PATCH_PACKAGE_UNSUPPORTED	1637	This patch package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.
ERROR_PRODUCT_VERSION	1638	Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs in Control Panel.
ERROR_INVALID_COMMAND_LINE	1639	Invalid command line argument. Consult the Windows Installer SDK for detailed command-line help.
ERROR_INSTALL_REMOTE_DISALLOWED	1640	The current user is not permitted to perform installations from a client session of a server running the Terminal Server role service.
ERROR_SUCCESS_REBOOT_INITIATED	1641	The installer has initiated a restart. This message is indicative of a success.
ERROR_PATCH_TARGET_NOT_FOUND	1642	The installer cannot install the upgrade patch because the program being upgraded may be missing or the upgrade patch updates a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.
ERROR_PATCH_PACKAGE_REJECTED	1643	The patch package is not permitted by system policy.
ERROR_INSTALL_TRANSFORM_REJECTED	1644	One or more customizations are not permitted by system policy.
ERROR_INSTALL_REMOTE_PROHIBITED	1645	Windows Installer does not permit installation from a Remote Desktop Connection.
ERROR_PATCH_REMOVAL_UNSUPPORTED	1646	The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
ERROR_UNKNOWN_PATCH	1647	The patch is not applied to this product. Available beginning with Windows Installer version 3.0.
ERROR_PATCH_NO_SEQUENCE	1648	No valid sequence could be found for the set of patches. Available beginning with Windows Installer version 3.0.
ERROR_PATCH_REMOVAL_DISALLOWED	1649	Patch removal was disallowed by policy. Available beginning with Windows Installer version 3.0.
ERROR_INVALID_PATCH_XML	1650	The XML patch data is invalid. Available beginning with Windows Installer version 3.0.
ERROR_PATCH_MANAGED_ADVERTISED_PRODUCT	1651	Administrative user failed to apply patch for a per-user managed or a per-machine application that is in advertise state. Available beginning with Windows Installer version 3.0.
ERROR_INSTALL_SERVICE_SAFEBOOT	1652	Windows Installer is not accessible when the computer is in Safe Mode. Exit Safe Mode and try again or try using System Restore to return your computer to a previous state. Available beginning with Windows Installer version 4.0.
ERROR_ROLLBACK_DISABLED	1653	Could not perform a multiple-package transaction because rollback has been disabled. Multiple-Package Installations cannot run if rollback is disabled. Available beginning with Windows Installer version 4.5.
ERROR_SUCCESS_REBOOT_REQUIRED	3010	A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run

Duplicate Records when you use Unknown Computer Support along with AD Delta Discovery

I’ve run into this scenario a couple of times after enabling Delta Discovery and have
got into the habit of doing a manual sweep for duplicate records, or extending
the Delta Discovery period, but that kind of defeats much of the reason for it.

http://blogs.technet.com/b/configmgrteam/archive/2011/08/17/known-issue-and-workaround-duplicate-records-when-you-use-unknown-computer-support-with-active-directory-delta-discovery.aspx

Basically, if you have Delta Discovery enabled and then image a new device
using unknown computer support SCCM creates a record for the new device, but
then if Delta Discovery runs before the Task Sequence installs the Client Agent
and after the OS has been joined to the domain, 2 records will be created
within SCCM.  The problems start though when SCCM can’t link/merge the two
together and won’t age either of the out of the database either.

Two choices are then left for you.

1. Manually
   sweep for duplicate records and delete the one that shows no client
   installed.
2. Setup a
   status filter rule that will run a script to automatically delete the
   record.

Thanks to
the TechNet article posted by Minfang Lv, this is now relatively simple to do,
with the scripts and instructions supplied.

As always, test before putting straight into production.

Microsoft Lync 2010 award

Just received this award from microsoft for contribution towards the lync development.

SMS_Site_SQL_Backup Error Unable to Communicate with remote SQL component

Had some issues today with the SMS_Site_SQL_ Backup error and unable to communicate

Thought i would share this out great find by a poster called Gorilla :-

http://www.windows-noob.com/forums/index.php?/topic/816-sms-site-sql-backup-error/

For posterity, I wanted to contribute something wacky I’ve resolved with Microsoft’s help.

Server 2008
SCCM 2007 SP1
Remote SQL 2005 DB

Text book install on pristine hardware. Was getting errors and had several working against me. This KB explained one:

http://support.microsoft.com/kb/957879

However the Hot Fix did NOT work. Updated DLL. Same problem Turns out that the Install.MAP file was not correct and an important bootstrap file wasn’t called. Once I updated Install.MAP and bounced the Site Component Manager, the sun came out, birds sang, and all was right in the universe. This was not intuitive, was not posted anywhere, and the support rep said that the documentation was internal. Not sure how or why this one hit me, but in case anyone else runs into this here’s the line:

In the ConfigMgr root (C:\Program Files\Microsoft Configuration Manager folder is a file called Install.MAP. Open this and find the section SMS_SITE_SQL_BACKUP under the BEGIN_COMPONENT_FILELIST section. There should be an entry:

FILE <smssqlbkup.exe><1><766496>

This tells SCCM the name of the executable, a bit flag for installed <1> or uninstalled <0>, and a 6 digit code for the file. The remote SQL Server needs the srvboot.exe file to well…bootstrap the component remotely. But it wasn’t in my Component list. I added the following line after the previous one:

FILE <srvboot.exe><0><219904>

Bounce the component manager and enjoy life. Though maybe few others will see this, I find it hard to believe anyone else in this environment wouldn’t have the same problem. They did agree this was Hot Fix support and did not levy a support incident. Hope that helps some poor frustrated soul somewhere.