Forum Discussion
Solved
Using intune to create application desktop shortcuts
I'm trying to use intune to push an application shortcut to the public desktop. I created an lnk file and saved it to a shared network drive. I then wrote a powershell script to copy that file to a...
- You should include the .lnl file in the Win32 app and use :
Copy-Item ".\FortiClientVPN.lnk" -Destination "c:\scut\FortiClientVPN.lnk"
Copy-Item ".\FortiClientVPN.lnk" -Destination "$env:Public\Desktop\FortiClientVPN.lnk"
But is there a reason for it to be on c:\scut and the Public Desktop? You created the shortcut on the Public Desktop based on the copied from S:\, but that drive is unavailable when installed as a System. I think adding the shortcut file to your package and copying it just to the public desktop is enough?
So your files are copied, or ...?
I didn't check your script, but Harm may found something, but the trigger for me is the Network share.
When you run this under System, your network share is probably not accessible and you should use the Run as User option. (also as Harm mentioned...)
The mapping is a problem; it's not accessible running it as a user, too, I guess, because it doesn't do any mapping.
Just run the script as system and include the .lnk file in the package.
Just run the script as system and include the .lnk file in the package.