Technology Log

Greetings everyone! If you are following in my footsteps of exposing the App Catalog web services. Here are a few tibbits that could help you keep your services exposed. Create a CI and use the following in the detection method. $registryPath = "HKLM:\Software\Microsoft\SMS\PORTALWEB" $registryName = "PortalPath" $key = Get-ItemProperty -Path $registryPath -Name $registryName $FilePath = $key.PortalPath+"\default.aspx" $ConfigFile = $key.PortalPath+"\web.config" $WebConfig1 = [System.IO.File]::ReadAllText($ConfigFile) $WSDLVisble = $WebConfig1.Contains("<!--<remove name=""Documentation"" />-->") -or $WebConfig1.Contains("<!--<remove name=""Documentation""/>-->") -or (!($WebConfig1.Contains("<remove name=""Documentation"" />"))) Remediation (if you choose to be so brave). $registryPath = "HKLM:\Software\Micr...

A while back I was tasked with finding a way to script an application deployment that was user based. So basically find a way to do what the native CM 2012 application catalog did without using the catalog web interface. The result ended up being write a powershell that is created on the client machine and called by and hta script downloaded from the "other" store interface. Its not very pretty but it met their requirements. I started my road using very useful information from the CM Team Blog https://blogs.technet.microsoft.com/configmgrteam/2012/09/19/extending-the-application-catalog-in-system-center-2012-configuration-manager/  their blog is an excellent source to help you get your catalog setup so that you can utilize the functions that I'll be using in my examples. From trial/error and debug log reading here is the basic flow of the application catalog interactions and how it works with the client. 1. Get 'AppID' of the application you want to install ...