narcoticmind Posted September 25, 2012 Report post Posted September 25, 2012 Just tested this thing and I'm kind of thrilled.. so I wanted to deploy cmtrace as an CM12 application, I did it with the quick-and-dirty method. So, I created a new application, and for the deployment type I checked script and the actual install program was as follows xcopy.exe ".\*.*" "%windir%\system32" /D /E /C /I /Q /H /R /Y /S And the uninstall program was as follows del.exe %windir%\system32\cmtrace.exe Detection method was of course checking the presence of cmtrace in %windir%\system32. The niceness about this is, that now I can simply run cmtrace on any computer in the network and I was thinking that the new app-model is way better than the old package deployment, what do you guys think? Has anyone else thought about deploying software like this? I know it would be better to handle it by doing a script that installs the cmtrace to %programfiles% and so on... Quote Share this post Link to post Share on other sites More sharing options...
0 ramlan Posted July 4, 2014 Report post Posted July 4, 2014 Sorry kubie for delayed response. Instead of using MSI - check this link - I tried and the installed worked out fine. http://myitforum.com/myitforumwp/2014/06/19/using-configmgr-2012-application-model-to-install-cmtrace-file-version/ Quote Share this post Link to post Share on other sites More sharing options...
0 tr3mblay Posted February 21, 2019 Report post Posted February 21, 2019 Old post i ran into while looking at deploying CMTrace. I completed the deployment using PowerShell scripts, with the addition of copying a link to the Public Desktop. CMTrace_Install.ps1 # Path to store the .ico and .exe $AppPath = 'C:\Windows\System32' # Path of the Public Desktop for shortcut $AppShortcut = "C:\Users\Public\Desktop" # Copy the .ico, .exe, and .lnk. Copy-Item .\CMTrace.lnk -Destination $AppShortcut Copy-Item .\CMTrace.ico -Destination $AppPath Copy-Item .\CMTrace.exe -Destination $AppPath CMTrace_UnInstall.ps1 # Path to store the .ico and .exe $AppPath = 'C:\Windows\System32' # Path of the Public Desktop shortcut $AppShortcut = 'C:\Users\Public\Desktop' # Remove the .ico, .exe, and .lnk Remove-Item $AppShortcut\CMTrace.lnk Remove-Item $AppPath\CMTrace.exe Remove-Item $AppPath\CMTrace.ico Quote Share this post Link to post Share on other sites More sharing options...
0 GarthMJ Posted February 21, 2019 Report post Posted February 21, 2019 FYI, in CMCB CMtrace is now installed as part of the client install. But I know you example it can use used with any application like it. Quote Share this post Link to post Share on other sites More sharing options...
Just tested this thing and I'm kind of thrilled.. so I wanted to deploy cmtrace as an CM12 application,
I did it with the quick-and-dirty method.
So, I created a new application, and for the deployment type I checked script and the actual install program was as follows
xcopy.exe ".\*.*" "%windir%\system32" /D /E /C /I /Q /H /R /Y /S
And the uninstall program was as follows
del.exe %windir%\system32\cmtrace.exe
Detection method was of course checking the presence of cmtrace in %windir%\system32.
The niceness about this is, that now I can simply run cmtrace on any computer in the network and
I was thinking that the new app-model is way better than the old package deployment, what do you guys think?
Has anyone else thought about deploying software like this? I know it would be better to handle it by doing
a script that installs the cmtrace to %programfiles% and so on...
Share this post
Link to post
Share on other sites