Ente

I finally had some time to take a deeper look at this and here are the errors I see when attempting to install the Reporting Point on just one of the SQL Nodes: Error Milestone XXX 10/28/2013 12:05:06 PM SQLNODE02.DOMAIN.LOCAL SMS_SRS_REPORTING_POINT 7403 The report server service is not running on Reporting Service Point server "SQLNODE02.DOMAIN.LOCAL"; start the service to enable reporting. This is strange because I can verify that the service is running on the SQL node. Here's some of the other log entries I see: Information Milestone XXX 10/28/2013 12:05:11 PM sqlnode02.DOMAIN.local SMS_SITE_SYSTEM_STATUS_SUMMARIZER 4721 Site System Status Summarizer detected that the availability of the "Reporting services point" role on server "\\sqlnode02.DOMAIN.local" has changed to Failed. Possible cause: This Configuration Manager Server Role is unable to function. Solution: Verify that no security or configuration problems exist and that all related components are running. Information Milestone XXX 10/28/2013 12:05:10 PM SQLNODE02.DOMAIN.LOCAL SMS_SITE_SYSTEM_STATUS_SUMMARIZER 4709 Site System Status Summarizer detected that the storage object "\\SQLNODE02.DOMAIN.LOCAL\M$\SMS" on site system "\\SQLNODE02.DOMAIN.LOCAL" has 335762524 KB of free storage space, which is above the Free Space Thresholds for this storage object. Site System Status Summarizer will now set the status of the storage object to OK in the Site System Status summary in the Configuration Manager Console. Information Milestone XXX 10/28/2013 12:05:10 PM SQLNODE02.DOMAIN.LOCAL SMS_SITE_SYSTEM_STATUS_SUMMARIZER 4702 Site System Status Summarizer successfully accessed storage object "\\SQLNODE02.DOMAIN.LOCAL\M$\SMS" on site system "\\SQLNODE02.DOMAIN.LOCAL". Possible cause: The storage object had been inaccessible since "10/28/2013 12:00:00 PM". Solution: If the storage object has sufficient free storage space, Site System Status Summarizer will now restore the status of the storage object to OK in the Site System Status summary in the Configuration Manager Console. Information Milestone XXX 10/28/2013 12:05:10 PM sqlnode02.DOMAIN.local SMS_SITE_SYSTEM_STATUS_SUMMARIZER 4709 Site System Status Summarizer detected that the storage object "\\SQLNODE02.DOMAIN.LOCAL\M$\SMS" on site system "\\sqlnode02.DOMAIN.local" has 335819200 KB of free storage space, which is above the Free Space Thresholds for this storage object. Site System Status Summarizer will now set the status of the storage object to OK in the Site System Status summary in the Configuration Manager Console.

I installed the RP's on each node and I was attempting to create a report from within the SCCM Admin Console.

I added the RP to both SQL nodes and I'm still receiving the same SSL/TLS error. I'm not very experienced with SQL, but I'm assuming this could have something to do with Certificates? I have my SCCM environment working in native mode with a PKI.

Not to get into a best practices argument, but isn't it usually best to keep the database running on a separate server from client management products? I'm thinking from a disaster recovery point of view. I've been burned in the past by running them on the same box.

I'm trying to get reporting services working and currently when I attempt to create a report I get the following error: "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel." Reporting was an after-thought when I built this 2012 environment as its not vital to our infrastructure, but now we need to make use of it. We have a Windows 2008 R2 cluster with 2 nodes and each runs SQL 2008. I initially put the Reporting Services Point on the name of the cluster itself, but I'm not sure where exactly the Reporting Role should be place. Should it be on each SQL node or the Primary Site server itself? We just run a standalone Primary Site connected to a 2 node SQL cluster.

While Microsoft gathered and combed through logs I made a fresh VM workstation from scratch to capture the operating system after customizing it and now my Task Sequences no longer fail at the "ConfigMgr Setup". I do not understand what the hiccup was with the VM I used to use as its been working for the past 2 years as a custom base image of Windows 7. Each year I would just spin up the VM again and make my changes, then capture it with a disk. What really irks me even more is that the logs point me in completely different directions from the cause of the issue. I kept investigating a MP refresh error in the ClientIDManagerStartup.log.

I have a ticket open with Microsoft for this issue.

Once it hangs at the SCCM Task Sequence screen I have to power off the device, turn it back on, then it continues with "Setup is preparing your computer for first use". Then I'll log into Windows and the client is install, but sometimes with very few options under the Actions tab. I even changed my Site properties to allow HTTP or HTTPS, but it OSD's still hang.

I should also add that smsts.log contains a long repetitive log start with the following: <![LOG[Succeeded loading resource DLL 'C:\Windows\CCM\1033\TSRES.DLL']LOG]!><time="12:53:05.163+300" date="08-27-2013" component="TSManager" context="" type="1" thread="2128" file="util.cpp:963"> <![LOG[Failed to create an instance of COM progress UI object. Error code 0x80070015]LOG]!><time="12:53:05.163+300" date="08-27-2013" component="TSManager" context="" type="2" thread="2128" file="clientui.cpp:265"> <![LOG[Failed to set log directory. Some execution history may be lost. The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="13:20:28.702+300" date="08-27-2013" component="OSDSetupHook" context="" type="3" thread="980" file="osdsetuphook.cpp:192"> <![LOG[Executing task sequence]LOG]!><time="13:20:28.797+300" date="08-27-2013" component="OSDSetupHook" context="" type="1" thread="980" file="osdsetuphook.cpp:279"> <![LOG[Task Sequence environment not found.]LOG]!><time="13:20:28.797+300" date="08-27-2013" component="OSDSetupHook" context="" type="1" thread="980" file="basesetuphook.cpp:1420"> <![LOG[Attempting to get active request.]LOG]!><time="13:20:28.797+300" date="08-27-2013" component="OSDSetupHook" context="" type="1" thread="980" file="basesetuphook.cpp:48"> <![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="13:20:29.062+300" date="08-27-2013" component="OSDSetupHook" context="" type="1" thread="980" file="basesetuphook.cpp:57"> <![LOG[Waiting for ccmexec process to start.]LOG]!><time="13:20:29.062+300" date="08-27-2013" component="OSDSetupHook" context="" type="1" thread="980" file="basesetuphook.cpp:58"> <![LOG[Failed to create instance if Software Execution Request Managerr. 0x80070005]LOG]!><time="13:20:34.070+300" date="08-27-2013" component="OSDSetupHook" context="" type="1" thread="980" file="basesetuphook.cpp:57"> This will repeat itself until, what looks like, I manually power off the device and turn it back on.

I migrated from SCCM 2007 to 2012 just fine and can push out the client (with PKI) without issues, but I cannot seem to reimage/refresh a device as it hangs forever after installing drivers. After the client reboots out of WinPE and starts the step "Setup Windows and ConfigMgr" everything comes to a halt. I checked the ClientIDManagerStartup.log file and see some of the following entries: <![LOG[RegTask: Failed to get certificate. Error: 0x87d00215]LOG]!><time="13:22:52.641+300" date="08-27-2013" component="ClientIDManagerStartup" context="" type="3" thread="2936" file="regtask.cpp:640"> <![LOG[Begin searching client certificates based on Certificate Issuers]LOG]!><time="13:22:53.687+300" date="08-27-2013" component="ClientIDManagerStartup" context="" type="1" thread="2936" file="ccmcert.cpp:3833"> <![LOG[Certificate Issuer 1 [CN=CA; DC=DOMAIN; DC=local]]LOG]!><time="13:22:53.687+300" date="08-27-2013" component="ClientIDManagerStartup" context="" type="1" thread="2936" file="ccmcert.cpp:3849"> <![LOG[Certificate Issuer 2 [CN=CA; DC=DOMAIN; DC=local]]LOG]!><time="13:22:53.687+300" date="08-27-2013" component="ClientIDManagerStartup" context="" type="1" thread="2936" file="ccmcert.cpp:3849"> <![LOG[Finding certificate by issuer chain returned error 80092004]LOG]!><time="13:22:53.687+300" date="08-27-2013" component="ClientIDManagerStartup" context="" type="2" thread="2936" file="ccmcert.cpp:3958"> <![LOG[Completed searching client certificates based on Certificate Issuers]LOG]!><time="13:22:53.687+300" date="08-27-2013" component="ClientIDManagerStartup" context="" type="1" thread="2936" file="ccmcert.cpp:3992"> <![LOG[Unable to find any Certificate based on Certificate Issuers]LOG]!><time="13:22:53.687+300" date="08-27-2013" component="ClientIDManagerStartup" context="" type="2" thread="2936" file="ccmcert.cpp:4069"> Would this be preventing the task sequence from continuing or should I be looking somewhere else?

I can see my clients switching to the old site "BPS": Attempting to query AD for assigned site code ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) Executing query (&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=177229899)(MSSMSRangedIPHigh>=177229899)))) ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) Executing query (&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=10.144.80.0)(mSSMSRoamingBoundaries=RJAC))) ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) This client might be within the boundaries of more than one site - AD SiteCode search matched 2 entries ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) The client will be assigned to the first valid site ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) LSGetAssignedSiteFromAD : Trying to Assign to the Site <BPS> ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) The MP name retrieved is 'OLDSERVER.DOMAIN.LOCAL' with version '6487l' and capabilities '<Capabilities SchemaVersion="1.0"> </Capabilities>' ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) Retrieving client operational settings from AD. ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) ClientOperationalSettings search filter is '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=BPS))' ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) Command line: "C:\Windows\SoftwareDistribution\Download\Install\ccmsetup.exe" ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) CCMHTTPPORT: 80 ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) CCMHTTPSPORT: 443 ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) CCMHTTPSSTATE: 0 ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) CCMHTTPSCERTNAME: ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) FSP: OLDSERVER.DOMAIN.LOCAL ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) CCMFIRSTCERT: 0 ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) Config file: ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) Retry time: 10 minute(s) ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) MSI log file: ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) MSI properties: SMSSITECODE=BPS SMSCACHESIZE=12000 CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="OLDSERVER.DOMAIN.LOCAL" CCMFIRSTCERT="0" ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) Source List: ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) MPs: ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) OLDSERVER.DOMAIN.LOCAL ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC) Updated security on object C:\Windows\ccmsetup\. ccmsetup 7/30/2013 8:17:06 AM 4604 (0x11FC)

Curses. I was telling both the 2007 and 2012 Sites to push the Client. Was this a cause for devices swapping between the PKI then to None as the certificate? I turned off the Client Push on the 2007 server, but what else will I need to do? I suspect that my devices that was "broke" will have permanent issues.

Sorry for digging this up, but can you go into what you did to resolve this? I renewed our CA and am curious if its causing issues in my environment.

Ok I removed the Management Point and readded it to my Primary Site server. I also enabled Client Push again. Waiting to see if this resolves anything, but I was looking at the ccmsetup.log file on a client listed as "None" and "Unknown" and it appeared that it was trying to install the client off my old 2007 site. At the end of the log there were entries stating that the client from the old site server was too old and rolledback. Looks like my clients are very confused as to where to talk, but I have a computer near me that is working just fine. PKI and Intranet.

Those logs look fairly clean. I see some entries from June 12th, but nothing after that. <06/12/13 11:10:16> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=63 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 <06/12/13 11:10:38> mp.msi exited with return code: 1603 <06/12/13 11:10:38> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError <06/12/13 11:10:38> Fatal MSI Error - mp.msi could not be installed. <06/12/13 11:10:38> ~RoleSetup(). MSI (s) (14:AC) [11:21:12:769]: Product: ConfigMgr Management Point -- Installation operation completed successfully. MSI (s) (14:AC) [11:21:12:769]: Windows Installer installed the product. Product Name: ConfigMgr Management Point. Product Version: 5.00.7804.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. Under System Management I have an entry for the Management Point: SMS-MP-CODE-SERVERFQDN I think part of the problem is that now my clients no longer list the PKI within the SCCM client. They used to display "PKI" under Client Certificate in the General tab, but now they display "None". Connection type is also "Unknown".