jigzs Posted September 2, 2010 Report post Posted September 2, 2010 Guys, Thanks for the excellent installation guide on vnext. Can you also provide how to configure software catalog service point. I am getting heaps of errors. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted September 11, 2010 Report post Posted September 11, 2010 i'm putting something together, coming shortly, what errors are you seeing Quote Share this post Link to post Share on other sites More sharing options...
asim Posted September 17, 2010 Report post Posted September 17, 2010 I have setup SCCM v.Next and the software catalog service but i cant seem to get the applications in the web portal, how do i deploy an application so that it is visible in the software catalog? Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted September 17, 2010 Report post Posted September 17, 2010 By deploying it to a User Collection. Quote Share this post Link to post Share on other sites More sharing options...
asim Posted September 18, 2010 Report post Posted September 18, 2010 I Figured that out just after posting the question by trying what you suggested peter, thanks for replying Quote Share this post Link to post Share on other sites More sharing options...
marlonc1980 Posted August 21, 2012 Report post Posted August 21, 2012 Friends'm having this problem when installing on the client and observe the state of SCCM 2012 reports this error "error in webservice critical point and the other web service point", I'm starting to install the first client, the WCF was not active; and turn it on and went back to install, the IIS is well, if anyone can help me. the others are fine Quote Share this post Link to post Share on other sites More sharing options...
marlonc1980 Posted August 21, 2012 Report post Posted August 21, 2012 Error Detail NAP 8/21/2012 11:18:07 AM nombreservidor.dominio.COM SMS_PORTALWEB_CONTROL_MANAGER 4951 Site Component Manager failed to install this component, because the Microsoft Installer File for this component (portlweb.msi) could not install. Refer to the SMSPortalWebSetup.log, the PortlWebMSI.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information. HELP Quote Share this post Link to post Share on other sites More sharing options...
marlonc1980 Posted August 21, 2012 Report post Posted August 21, 2012 Site Component Manager failed to install this component, because the Microsoft Installer File for this component (portlweb.msi) could not install. Quote Share this post Link to post Share on other sites More sharing options...
marlonc1980 Posted August 21, 2012 Report post Posted August 21, 2012 Information Milestone NAP 8/21/2012 1:19:00 PM server.dominio.COM SMS_PORTALWEB_CONTROL_MANAGER 4610 Component Status Summarizer set the status of component "SMS_PORTALWEB_CONTROL_MANAGER" running on computer "server.dominio.COM" to Warning. Possible cause: The component is experiencing a problem. Solution: Diagnose and fix the problem by: 1. Examine the status messages that the component reports. 2. Correcting the problem. 3. Instructing Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the Configuration Manager Console. When the counts are reset, Component Status Summarizer will change the status of the component to OK. This might take some time if site "NAP" is a child site. 4. Deleting any unwanted status messages from the site database, if necessary. 5. Monitor the component occasionally to verify the problem does not reoccur. Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component. Solution: Increase the Component Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the Configuration Manager Console. Possible cause: The component is "flooding" the status system by rapidly reporting the same message repeatedly. Solution: Diagnose and control the flood of status messages by: 1. Verifying that the component is actually flooding the status system. View the status messages reported by the component, and verify that the same message is continually reported every several minutes or seconds. 2. Noting the Message ID of the flooded status message. 3. Creating a Status Filter Rule for site "NAP" that instructs Status Manager to discard the flooded status message when component "SMS_PORTALWEB_CONTROL_MANAGER" on computer "server.dominio.COM" reports it. 4. Verifying that your sites' databases were not filled up by the flooded status messag Quote Share this post Link to post Share on other sites More sharing options...
