No announcement yet.

Trying to make shortcuts on desk

  • Filter
  • Time
  • Show
Clear All
new posts

  • Trying to make shortcuts on desk


    Not sure where to post this so sorry if in wrong place

    Thank you for reading my post. I am brand new to scripting so my apologies if this is rather basic – But everyone starts somewhere.

    We are running Windows 7 desktop on a 2003 Enterprise domain.
    I need to copy some short cuts files (eod8 extension) to the start menu under “All Programs” in a folder called “EOD”. The users must be able to save and open the shortcuts (so using the All Users folder did not work since a standard user can’t save to that location) So I am copying the files to the local user profile.

    My Script
     set Installpath=%~dp0
     mkdir "C:\Users\%username%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\EOD"
     echo "No" | xcopy  "%Installpath%*.eod8" "C:\Users\%username%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\EOD"  /d
     Timeout /T 1 
    When I run the script locally it works – When I deploy through SCCM It fails
    “Unable to find the file *.eod8” – What I have noticed is that If I go to C:\Windows\ccmcache\XX
    And edit then close the script file (no change has been made) it works through the Software Center

    From my limited knowledge I think my issue could be with the location\path of my script

    Thanks for your advice
    Last edited by Rems; 13th November 2014, 20:50. Reason: added [code] tags around the code

  • #2
    Re: Trying to make shortcuts on desk

    The install path is set to the directory that the script is run from. Where does SCCM drop the script? My guess is that the install path is OK but you should check that just to make sure.

    Also, if SCCM is running the script under the system account it won't work since it's using the %username% variable. The script needs to be run in the user context. This would be my best guess as to what the issue is. I'm not very familiar with SCCM. Can you get it to run in the logged on user's context? If not then I would use group policy and configure this as a logon script.

    Network Consultant/Engineer
    Baltimore - Washington area and beyond