Jump to content


Leaderboard

Popular Content

Showing content with the highest reputation since 10/29/2021 in all areas

  1. Use the application substitution rule, first do the uninstallation of the old version parameters or scripts, in the installation will first uninstall the old version before installing the new version
    1 point
  2. 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
    1 point
  3. ok first things first, the SMSTSPostAction variable is for use in operating system deployment task sequences to do an action after the task sequence has completed, are you planning on installing SEP as part of a task sequence ? if so use an Install Application step instead of Install Package if that's easier, or even run PowerShell script... but first, if you really want to install the app just using a powershell script then test the script on a virtual machine standalone, outside of a task sequence
    1 point
  4. Need help, I´ve followed your manual and I got error 0xffffffff on run command step. I don´t have timeout selected. Is there anything else what I can check? Thank you. @already solved by adding proper path to powershell.exe file in Win10. Thx
    1 point
  5. I imported some VHD's from Microsoft Virtual PC to Hyper V, and I noticed that one of my VM's had a problem, I couldn't add a second network card to it (I could add it in settings, but it would never appear as a new device on the VM or in the VM's device manager), so I checked out the device manager, there was a device with a yellow exclamation mark on it called VMBus. Double clicking on that showed me the following error After some googling I found this post and the advice in there was spot on, I had already installed my Intergration Services Setup disk and rebooted, but my problem remained, the VMBus was now called Virtual Machine Bus but still no network, so I ran MSCONFIG, clicked on boot, then clicked on the advanced tab and put a checkmark in Detect HAL, I clicked ok and reboot, some windows drivers were redetected and lo and behold my problem disappeared ! cheers ! anyweb
    1 point
×
×
  • Create New...