Need help with MDT - Remote Command

Comments

4 comments

  • Stephen Valdinger

    Should work without Central Server. You will certainly need to change the ServicePort before Invoke-Command will work to kick off pdqdeploy.exe. What error are you getting after you set the service port and start the service? 

    I'd recommend reaching out to support directly by emailing support@pdq.com so they can help you sort that error out. Once that is working, the Invoke-Command you've got should do the trick.

    0
    Comment actions Permalink
  • Trav A. Tonsfeldt

    I use two Run Command Lines within my Task Sequence to deploy packages with an baseline packages. This installs psexec onto the machine and then uses psexec to call the server to deploy the package

     

    xcopy "File path" /E "C:\Windows\System32" /s /i
    SETX /M PATH "%PATH%C:\Windows\System32\PSTools"

    for /f "skip=1 delims={}, " %%A in ('wmic nicconfig get ipaddress') do for /f "tokens=1" %%B in ("%%~A") do set "IP=%%~B"

    psexec \\server -u username -p password -h -accepteula "C:\Program Files (x86)\Admin Arsenal\PDQ Deploy\pdqdeploy.exe" Deploy -Package "Baseline" -Targets %ip%

    0
    Comment actions Permalink
  • Charles Hucks

    We took a different approach.  Instead of using psexec or Invoke-Command, we use a scheduled task that fires when a particular event is logged to the Windows event log of the PDQ server.  The scheduled task just runs the same pdqdeploy command line options but we found this method to be more reliable.  An added bonus is that we have a history of the events in the event log.

     

    0
    Comment actions Permalink
  • Patrick Morphy

    I used MDT applications to launch PDQ push requests: https://support.pdq.com/hc/en-us/community/posts/115001838131-How-to-use-MDT-Applications-for-PDQ-push-requests 

    0
    Comment actions Permalink

Please sign in to leave a comment.