Search the Community
Showing results for tags 'cmtrace'.
Found 2 results
Hello, I am trying to deploy CMTrace as part of the TS (SCCM 2012 SP1, no MDT integration) and also set it as default log viewer. This is my powershell script: $RelativePath = (split-path $SCRIPT:MyInvocation.MyCommand.Path -parent)+"\" Copy-Item -Path $RelativePath"CMTrace.exe" -Destination "c:\temp\" -Force xcopy "c:\temp\CMtrace.exe" "c:\windows\System32" /y xcopy "c:\temp\CMtrace.exe" "c:\windows\SYSWOW64" /y $CMtraceKey = "HKCU:\SOFTWARE\Microsoft\Trace32" Set-ItemProperty -Path $CMtraceKey -Name "Register File Types" -Value 00000000 $Parameters = "assoc .log=logfile" cmd.exe /c $Parameters The xcopy commands do not work for some reason, and smsts log doesn't show me anything. Can somebody advise on why the copy commands do not work and how can I apply the HKCU key properly ? Thanks
Deploying CMTrace as an Application
narcoticmind posted a question in Deploy software, applications and driversJust 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...