herrando

Is this in a task sequence environment? I've got some running in mine, I always just use a "run command line" and then enter: cmd /c c:\support\runme.cmd I found that if I didn't use cmd /c the dosbox would remain open in the background and eventually halt the task sequence. If dealing with flat files like this, you could also try creating a self extractor in Winrar and set the "run after extraction" to the extracted location of your cmd file.

Strange problem. I used to use SCCM Asset intelligence reporting - specifically the "Software 06A - Search for installed software" report ID 268 to find the software IDs for all versions of a particular application that was installed. For example, I would type %Chrome% into this report and run it on the SMS00001 collection to see every version of Chrome that was installed on the estate. I would then use this product ID in a batch file to remove all previous versions before installing the latest one. This helped me keep the software version in my estate consistent. Until recently, the reports have always had all fields populated and been very useful, but now for some reason, the software IDS are not being discovered. Software inventories are still being performed on the clients at regular intervals and there has been no changes. I also noticed that Asset Intelligence seems to have many apps sitting "pending online identification" for a few months now, despite saying it's "enabled and connected to online service". I don't see Chrome on the pending list, but I didn't think software guid discovery would depend on asset intelligence sync. Any ideas? Andrew

Well just a quick update, I had a specialist contractor come to look at this and he was also unable to resolve/identify the issue. It just looked like everything should have been working fine. Clients were getting the correct MP information and retrieving their policies fine. I've now taken the somewhat drastic step of building another secondary site at the same location and all is working fine there. I will be decomissioning this secondary site, the only assumption I can make is that there was something fundamentally broken on the site, despite all tests passing using MPTtroubleshooter and the CMRAP coming back with no issues the site did not function as expected.

Hi I have a problem I am hoping someone can assist with. A new secondary site was deployed recently and has been working absolutely fine. We could image PCs at the secondary site and they would appear in configmgr console with the correct primary site code within 25-35 minutes of them being deployed. This seems to have stopped happing recently. Any new PCS being built instead either don't appear in the configmgr console, or appear only when Active Directory system discovery is ran, when this happens the client are assigned to the secondary sitecode instead of the primary, and can receive no advertisements as a result of this. Here is the generic Info: All sites running SCCM 2007 SP2 R3 SQL database on separate server cluster AD schema extended Mixed mode operation. I have been though quite a few things to try and resolve this issue to no avail. Checked boundaries were correct - Initially I was using AD sites and services, I noticed that there were some issues with this so I have replaced this with the IP address ranges of the site instead. Verified no overlapping boundaries are present. Manually went though the boundaries and could find no overlaps, I also found a script that checked this and nothing was found. Check the health of the management point - Checked using MPTroubleshooter from ConfigMgr 2007 Toolkit V2, on the primary site all checks came up clear, but the secondary came up with a warning that the secondary site wasn't administrator on the SQL server - I run SQL in a separate cluster, I have now added the secondary site to the administrator group here and re-ran the test to find that it all comes back green now. running http://sbpssccm01/sms_mp/.sms_aut?mplist shows the primary and all secondary sites fine. running http://sbpssccm01/sms_mp/.sms_aut?mpcert shows the certificate Ensured that the secondary site is set to publish the site in active directory domain services, and also tried setting to publish in DNS. Checked System Management container in AD and verified that the secondary site is present and is being updated, the secondary site computer account has permissions to "this object and all descendant objects" On the Task sequence for my OSD I have specified additional installation properties MP=SBPSSCCM01.mydomain.net FSP=SBPSSCCM01.mydomain.net SLP=SBPSSCCM01.mydomain.net - my SBPSSCCM01 server runs in mixed mode and I have the FSP and SLP role installed on the same server. Using these settings my client is being installed, assigned to the correct site and appearing in SCCM correctly at all other secondary sites. On the client side I have verified that the client installs successfully, I have verified using Smsclient centre that the site is allocated to the correct MP and PMP. Sometimes the clients don't seem to automatically download a policy, I have to go onto the machine and trigger the machine policy retrieval and evaluation cycle. After this the machine gets it's policy fine. I run Discovery Data collection cycle, as I understand it, heartbeat discovery is the only thing that causes the configmanager console to update from client=no to client=yes and also renew the sitecode. This seems to run fine. Heartbeat discovery is set to run every hour on my secondary and primary site, I set the "clear client install flag" to only run once every 7 days. If I manually install the client over the top of the existing one pushed down via the TS with the MP hardcoded, or MP set to auto, the client will appear and work fine pointed at the correct site code (the primary). It seems that after a day or two the client reverts back to the secondary site, or is marked as client=no, yet you can still remote tools onto these machines and see the configmr client is still installed, and still seems be assigned correctly. Using Client Push results in the same issues. I have attached some logs when seem to have a few blips in them, but upon looking up the errors it seems to be normal operation. Open to any and all ideas... including crazy ones! - edit - uploaded some log files from the wrong client, reuploaded them. CAS.log CcmExec.log ClientIDManagerStartup.log ClientLocation.log DataTransferService.log execmgr.log LocationServices.log StatusAgent.log

I've bitten the bullet and uninstalled bits and the mangement point. Reinstalled bits and tested, the IIS errors stopped. I then reinstalled the management point and now all is working again.

Hi First post here for me, but I've been reading solutions on here for a good while now and find this forum to be an invaluable resource. Keep up the good work! Now my issue, I'm hoping someone call assist with this - becuase it's driving me around the twist now... We had SCCM 2007 R3 working all fine and well up until this morning. The only thing that we couldn't get working was asset intelligence synchronisation with Microsoft online catalog - it reported bad certificate. It was decided to remedy this by installing SCCM2007-SP2-KB2483225-ENU.msi. Immediatly after installing this patch we had several information warnings in SCCM saying that "SMS site component manager detected that this componant should be reinstalled on the system, error 1071 After this it looked like it reinstalled some of these sucessfully, but then this warning apears: "SMS Site Component Manager could not stop the SMS_EXECUTIVE service on site system \\SCCMA01. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. If this problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information." " SMS Site Component Manager failed to reinstall this component on this site system. Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the reinstallation in 60 minutes. To force SMS Site Component Manager to immediately retry the reinstallation, stop and restart SMS Site Component Manager using the SMS Service Manager. " Eventually it appears - without doing anything that the reinstall is sucessful. pretty much all the other roles get reinstalled at this point sucessfully but then this error appears: "MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory. Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. " " SMS Site Component Manager failed to reinstall this component on this site system. Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the reinstallation in 60 minutes. To force SMS Site Component Manager to immediately retry the reinstallation, stop and restart SMS Site Component Manager using the SMS Service Manager. " MS Site Component Manager failed to install this component, because the Microsoft Installer File for this component (MP.msi) could not install. Refer to the MPSetup.log, the MPMSI.log, as well as the SMS documentation and the Microsoft Knowledge Base for further information. " I checked my MPSetup.log and MPMSI.log and they contain the following: <09-05-2012 21:13:51> ==================================================================== <09-05-2012 21:13:51> SMSMP Setup Started.... <09-05-2012 21:13:51> Parameters: D:\PROGRA~1\MICROS~1\bin\i386\ROLESE~1.EXE /install /siteserver:SCCMA01 SMSMP <09-05-2012 21:13:51> Installing Pre Reqs for SMSMP <09-05-2012 21:13:51> ======== Installing Pre Reqs for Role SMSMP ======== <09-05-2012 21:13:51> Found 1 Pre Reqs for Role SMSMP <09-05-2012 21:13:51> Pre Req MSXML60 found. <09-05-2012 21:13:51> No versions of MSXML60 are installed. Would install new MSXML60. <09-05-2012 21:13:51> Enabling MSI logging. msxml6_x64.msi will log to D:\Program Files (x86)\Microsoft Configuration Manager\logs\msxml6_x64MSI.log <09-05-2012 21:13:51> Installing D:\Program Files (x86)\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi <09-05-2012 21:13:54> msxml6_x64.msi exited with return code: 1618 <09-05-2012 21:13:54> Backing up D:\Program Files (x86)\Microsoft Configuration Manager\logs\msxml6_x64MSI.log to D:\Program Files (x86)\Microsoft Configuration Manager\logs\msxml6_x64MSI.log.LastError <09-05-2012 21:13:54> ======== Completed Installion of Pre Reqs for Role SMSMP ======== <09-05-2012 21:13:54> Installing the SMSMP <09-05-2012 21:13:54> Passed OS version check. <09-05-2012 21:13:54> IIS Service is installed. <09-05-2012 21:13:54> checking WebDAV configuraitons <09-05-2012 21:13:55> WebDAV is configured <09-05-2012 21:13:55> SMSMP already installed (Product Code: {B391E30E-C8BD-41FC-8B8C-540C4365DBE0}). Upgrading/Reinstalling SMSMP <09-05-2012 21:13:55> New SMSMP is the same product code. This is a minor upgrade. <09-05-2012 21:13:55> Enabling MSI logging. mp.msi will log to D:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log <09-05-2012 21:13:55> Installing D:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\mp.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\Program Files (x86)\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files (x86)\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 <09-05-2012 21:13:58> mp.msi exited with return code: 1618 <09-05-2012 21:13:58> Backing up D:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log.LastError <09-05-2012 21:13:58> mp.msi could not be installed. The return code was 1618 MPMSI.LOG === Verbose logging started: 05/09/2012 21:13:55 Build type: SHIP UNICODE 5.00.7601.00 Calling process: D:\PROGRA~1\MICROS~1\bin\i386\ROLESE~1.EXE === MSI © (54:98) [21:13:55:100]: Resetting cached policy values MSI © (54:98) [21:13:55:100]: Machine policy value 'Debug' is 0 MSI © (54:98) [21:13:55:100]: ******* RunEngine: ******* Product: D:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\mp.msi ******* Action: ******* CommandLine: ********** MSI © (54:98) [21:13:55:100]: Client-side and UI is none or basic: Running entire install on the server. MSI © (54:98) [21:13:58:111]: Failed to grab execution mutex. System error 258. MSI © (54:98) [21:13:58:111]: Cloaking enabled. MSI © (54:98) [21:13:58:111]: Attempting to enable all disabled privileges before calling Install on Server MSI © (54:98) [21:13:58:111]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI © (54:98) [21:13:58:111]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI © (54:98) [21:13:58:111]: MainEngineThread is returning 1618 === Verbose logging stopped: 05/09/2012 21:13:58 === MSI (s) (B4:D0) [21:18:29:726]: User policy value 'DisableRollback' is 0 MSI (s) (B4:D0) [21:18:29:726]: Machine policy value 'DisableRollback' is 0 MSI (s) (B4:D0) [21:18:29:726]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (B4:D0) [21:18:29:726]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (B4:D0) [21:18:29:726]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (B4:D0) [21:18:29:726]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (s) (B4:D0) [21:18:29:726]: Restoring environment variables MSI (s) (B4:D0) [21:18:29:726]: Destroying RemoteAPI object. MSI (s) (B4:E4) [21:18:29:726]: Custom Action Manager thread ending. I did notice that initially before checking this that Webdav did not appear to be running (mapped drive to the localhost) I then checked IIS settings and there were several errors present- Webdav seemed to be configured correctly but upon checking the webdav schema file it was set as follwing: <element name="properties"> <attribute name="allowAnonymousPropfind" type="bool" defaultValue="false" /> <attribute name="allowInfinitePropfindDepth" type="bool" defaultValue="false" /> <attribute name="allowCustomProperties" type="bool" defaultValue="true" /> <collection addElement="add" removeElement="remove" clearElement="clear" allowUnrecognizedAttributes="true"> <attribute name="xmlNamespace" type="string" isUniqueKey="true" required="true" validationType="nonEmptyString" /> <attribute name="propertyStore" type="string" required="true" validationType="nonEmptyString" /> </collection> </element> I have changed it back to : <element name="properties"> <attribute name="allowAnonymousPropfind" type="bool" defaultValue="true" /> <attribute name="allowInfinitePropfindDepth" type="bool" defaultValue="true" /> <attribute name="allowCustomProperties" type="bool" defaultValue="false" /> <collection addElement="add" removeElement="remove" clearElement="clear" allowUnrecognizedAttributes="true"> <attribute name="xmlNamespace" type="string" isUniqueKey="true" required="true" validationType="nonEmptyString" /> <attribute name="propertyStore" type="string" required="true" validationType="nonEmptyString" /> </collection> </element> and restarted the componant services, and now webdav is working again - but still the MP wont reinstall. IIS logs keep throwing this error continually : Log Name: System Source: Microsoft-Windows-WAS Date: 05/09/2012 21:06:32 Event ID: 5009 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: SCCMA01.ourdomain.net Description: The description for Event ID 5009 from source Microsoft-Windows-WAS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: CCM Server Framework Pool 1376 fffffffe Event Xml: <Event xmlns="http://schemas.micro...08/events/event"> <System> <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" /> <EventID Qualifiers="32768">5009</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-09-05T20:06:32.000000000Z" /> <EventRecordID>801029</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>SCCMA01.ourdomain.net</Computer> <Security /> </System> <EventData> <Data Name="AppPoolID">CCM Server Framework Pool</Data> <Data Name="ProcessID">1376</Data> <Data Name="ExitCode">fffffffe</Data> </EventData> </Event> And I can see BITS errors too: Log Name: Application Source: BITS Server Extensions Date: 05/09/2012 10:10:39 Event ID: 9 Task Category: None Level: Error Keywords: User: SYSTEM Computer: SCCMA01.ourdomain.net Description: Enabling BITS uploads for the virtual directory failed with error 0x800CC801. The error occurred while creating the directory IIS://LocalHost/W3SVC/1/Root/CCM_Incoming Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="BITS Server Extensions" Guid="{38398B57-93F3-4C42-AC26-DB3F5998745B}" /> <EventID>9</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2012-09-05T09:10:39.473139100Z" /> <EventRecordID>37814</EventRecordID> <Correlation /> <Execution ProcessID="6096" ThreadID="8584" /> <Channel>Application</Channel> <Computer>SCCMA01.ourdomain.net</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="name">IIS://LocalHost/W3SVC/1/Root/CCM_Incoming</Data> <Data Name="hr">2148321281</Data> <Data Name="vdir"> </Data> </EventData> </Event> Its seems there is way too much going on here to try and start troubleshooting this.... Should I uninstall this KB? or will this cause more harm? i'm really struggling wiht this one to explain to my boss why this is on it's knees given it should have been a pretty straight forward update... Any help will be greatly appreciated.