Freigeben über


Remote Connection to WinPE during SCCM deployments - creating shortcuts with Ticket numbers and IP on a file share

Update - I've found a bug and fixed it. Now you can call this script from PE in OS Refresh scenario as well.

The well known name in Deployment world, Johan Arwidmark wrote an excelent article on adding remote control to MDT/SCCM Boot images.

https://www.deploymentresearch.com/Blog/tabid/62/EntryId/36/Software-Assurance-Pays-Off-Remote-Connection-to-WinPE-during-MDT-SCCM-deployments.aspx

Here is what he's saying:

"If you want to automate the connection to the client (for example provide a readymade link), you can create a script that reads the info from inv32.xml and creates a shortcut on the deployment server. Dart Remote Connection Viewer supports command line parameters for TicketNumber, IP Address and Port."

So I took some time to implement excactly that!

So, there is already some logic in MDT 2012 B2 for that, I just took his script, added a few parameters (like UNC share, user name, domain and a password to connect) and making it available for you :) Follow all his recommendations, but use files unattend.xml and StartRemoteRecovery.wsf   from attachment to this article.

Don't forget to modify unattend.xml replacing *** with your data. 

StartRemoteRecovery.zip

Comments

  • Anonymous
    January 16, 2012
    HiIm been trying out your script and everything seems to work, but i got a little problem.The ticket in the shortcut that is made is different from the remote connection on the end user.Have you had this problem yourself or have anyone else reportet this back to you?
  • Anonymous
    July 24, 2013
    Hey, this worked great!  I'm trying to change the link names from the IP Address to the Serial Number, but everything I've done, it just makes the shortcut name blank.  Ideas on how to make the shortcut name the Serial number instead?
  • Anonymous
    July 25, 2013
    Not sure what changed, but for some reason the script is no longer reporting the correct ticket number, and the shortcut it creates does not work because the ticket number is wrong.  I started over from scratch with the scripts, but still can't get it to work.
  • Anonymous
    October 02, 2014
    If i dont have SCCM integration,can I use this feature?