I have been look for a way to report deployment status, without using Monitoring | Deployment in the console. The trick was to monitor SMSPROV.LOG while I activated the monitoring | deployment in the console. After some digging around in the log, I found the select statement below. I have modified it a bit and added some comments. select all SMS_DeploymentSummary . ApplicationName , SMS_DeploymentSummary . AssignmentID , SMS_DeploymentSummary . CI_ID , SMS_DeploymentSummary . CollectionID , SMS_DeploymentSummary . CollectionName , SMS_DeploymentSummary . CreationTime , SMS_DeploymentSummary . DeploymentID , SMS_DeploymentSummary . DeploymentIntent , SMS_DeploymentSummary . DeploymentTime , SMS_DeploymentSummary . DesiredConfigType , SMS_DeploymentSummary . EnforcementDeadline , SMS_DeploymentSummary . FeatureType , SMS_DeploymentSummary . ModelName , SMS_DeploymentSummary . ModificationTime , SMS_DeploymentSummary . NumberErrors , SMS_Deployme
Download an appx application locally to be used in SCCM CB I got some inspiration to this blogpost from: http://woshub.com/how-to-download-appx-installation-file-for-any-windows-store-app/ Here is an easy way to download an appx from Microsoft store. This can be used to add an appx application in SCCM CB and the distribute it to devices. Why all this hazzle, when you can get the app from the store? Quite simple: our company policy don't allow app update over the Internet Requirement: The application must be installed, to be able to copy the download link. Next: Search for the application and chose share. (Sorry for the danish. Lommeregner = Calculator) In the share dialog box, select copy link Browse to this URL: https://store.rg-adguard.net/ and paste the URL into the textbox Find lines with the version number you would like to download and place them all in the same folder. Also download the files for x86 & x64 or an easier way...
Playing around with TFTPWindowsSize can result in faster pxeboot process over a slow line. One of my colleagues has optimized the pxeboot process by adjusting the TFTPWindowsSize. In our case the load of the pxe wim vent down from 20 min to 2 min. The default value i 1, and the test ended with 16. it migth be required with some test in your environment to find the "right" value for you. The change did not impact the pxe process on VMWare. PS/ Do not change the TFTPBlocksize, this will break the pxe process! Next step will bo to implement BranchCache, to get additional performance improvements
Comments
Post a Comment