Could you please tell me how many days can I use the trial version of Dashboard? Looks very useful for my SCCM infra. Also please let me know how to opt for dashboard after the trial period.First a huge thanks for all attending the webinar, as promised he are a list of the questions that we didn’t have time to answer during the webinar.
- Q: We already use Flexera for compliance. Is "Patching" included in it OR is it a separate module?
A: Patching is integrated in the standard CSI solution. You can either patch using WSUS or integrate with Configuration Manager - Q:We have had unexpected reboots when patching servers. We have a GP in place to disable automatic updates and the server is in a collection that has 2 maintenance windows (one for SU and one for All Deployments). Only a SU deployment is deployed to the (missing text)?
A: I’m guessing that the missing text is something like “collection”. I would look in the RebootCoordinator.log file on the local server and see what caused the restart. I have seen the same issue when running Configuration Manager 1606, but not with version 1610 - Q: Could you please tell me how many days can I use the trial version of Dashboard? Looks very useful for my SCCM infra. Also please let me know how to opt for dashboard after the trial period?
A: I take it, that we are talking about the Coretech System Center Dashboard, a trial can be requested here: http://coretech.global/downloads/sccm-dashboard/ the trial is valid for at least 2 weeks and can be extended if needed. - Q: Is task sequence the recommended way to deploy Feature updates you said you had more control then?
A: For now I would say Yes. A task sequence will offer you much more control compared to the build-in servicing feature. Just be aware that using a task sequence will increase the size of the content compared to the servicing module. - Q: Having those detailed task seq. logs for server baselining is great BUT how would you manage the sheer volume of logs if you had to patch 17,000 servers *monthly* ?
A: In the Enterprise we normally integrate ConfigMgr with a CMDB like Microsoft Service Manager or ServiceNow. That allows us to collect the information where it truly belongs – a CMDB – along with with all the server documentation. - Q: Adding on question 1, what are the advantages where you recommend the CSI agent rather than built in software inventory?
A: Using the CSI agent has a lighter impact on the amount of data being collected. - Q: The "Patching" item between reports and administration in the menu does not exist when we log on, what are missing?
A: In the CSI console, the “Patching” object is only visible when you install the IE plugin. There is a red link in the button of your browser whenever you have an older version or the IE plugin or no plugin at all. - Q: can CSI scan use SCCM inventory data? If it does how compliance status will get updated after installing the patch? do we have to wait till next inventory cycle finishes?
A: Yes, CSI can either use the CSI agent or software inventory data from Configuration Manager (*.exe, *.ocx, *.dll files). Compliance data are updated along with the software inventory scan process. - Q: We’re using WSUS since we don’t like ConfigMgr default reboot – we tried the Coretech shutdown tool – any plans to make more features available in the shutdown tool?
A: What features are you looking for? Also the Configuration Manager reboot has changed in latest version 1610, you can now choose to install updates during restart or shutdown. - Q: After I perform a clean of the software updates (remove all expired and superseded) some sites will have a very large scan, in the form of traffic back to the primary SUP well over 1GB. I have not been able to sort out why some of these clients are doing such a large (missing text).
A: I need to have more details to understand the scenario and answer the question – feel free to reach out to me using twitter @Agerlund - Q: Are there any good reason why a enterprise business should NOT choose LTSB?
A: Yes, it’s never been mend to be a version implemented on “traditional” devices. Only special devices where changes happens rarely and new features are NEVER required. - Q: I missed where you got the dashboard from? Is it free and where can I get it?
A: It’s a paid service that includes +25 customer reports, configuration items and the Azure dashboard interface. A trial can be requested here http://coretech.global/downloads/sccm-dashboard/ - Q: Do the systems not reporting compliance include systems that have not completed a scan due to client issues? Not just systems that have failed to apply updates.
A: If a client computer did not successfully scan for software updates compliance the state will be Unknown. clients that failed a deployment will be listed as “Failed” - Q: what can we do about the patches that insist on not installing on some clients? Like we installed a New time zone patch that published by Microsoft but some clients still don’t have it?
A: If the client is not requesting the patch, then you could install it as a package, it really depends on the patch. You can also create a configuration item with a patch check and force the installation. - Q: IS it worth using CSI in an agentless format? Can you talk a little bit about the Secunia/CSI agent footprint?
A: The footprint is not that big, but often customers do not like the fact that we are installing another service on the endpoints. For that reason I find it easier to run the client as a package.
