RunAs not opening shortcut

[ipgenie]

I'm trying to allow users to access files on a server without authenticating. The RunAs command looks like it should work, but nothing ever opens up. I added a MsgBox to confirm that it wasn't getting stuck somehow and it runs fine, but does not open the shortcut. Does anyone have any ideas on what I'm doing wrong?

; Username, domain and password.

$sUserName = "XXXXX"

$sPassword = "XXXXX"

$sDomain = "XXXXX.local"

; Run command

RunAs($sUserName, $sDomain, $sPassword, 0, @ComSpec & " /c " & "\\server\utility\shortcut.lnk", "\\server\PMW220\App", @SW_HIDE)

; Confirmation test message.

MsgBox(0, "Done", "Done.")

[sleepydvdr]

Run can only run executables, not links. Change it to point to the executable.

[ipgenie]

Thanks sleepydvdr.

I did try using a .exe with the same name in the same folder like this:

RunAs($sUserName, $sDomain, $sPassword, 0, @ComSpec & " /c " & "\\server\utility\shortcut.exe", "\\server\PMW220\App", @SW_HIDE)

This is a compiled script that opens the shortcut and it works, but doesn't open when I try to run it with RunAs.

[sleepydvdr]

I've used a trick I have used before that makes accessing network shares easier: DriveMapAdd. Then change the location of the executable to the drive letter you mapped it to. If you don't want to keep it mapped all the time, you can un-map it when the program is closed.

[BrewManNH]

Hopefully the username and password in your script isn't an admin password because that's going to present a security risk for the server you're accessing.

[ipgenie]

Any domain user has access to that share so no admin needed.

I have two domains and am slowly moving everything from the old to the new.

I'll probably have to map a network drive in order for it to work properly.

[Jos]

Thanks sleepydvdr.

I did try using a .exe with the same name in the same folder like this:

RunAs($sUserName, $sDomain, $sPassword, 0, @ComSpec & " /c " & "\\server\utility\shortcut.exe", "\\server\PMW220\App", @SW_HIDE)

This is a compiled script that opens the shortcut and it works, but doesn't open when I try to run it with RunAs.

What happens when you do a runas on the cmd prompt and start CMD under these credentials and then try to run the script as indicated?

Jos