Sharing a program over the network.

slipd · 11 Jun 2012 at 15:18

Hi guys,

I've installed a new program (exam prep) on a server and I'd like my users to be able to access it; I know it isn't as simple as just creating a shortcut to it and putting it on my users desktop (I know becasue I've tried

), that just gives me a missing '.ink' error. Is there a way of changing the path of the shortcut so that users are able to access this software or will I have to go around to every machine and install it locally - which I was hoping to avoid :rolleyes:

Any ideas?

NealR · 11 Jun 2012 at 15:20

From the machine that has the files on, make that whole directory shared on the network. Then on the other machine, create a new shortcut with the location of: \\MACHINENAME\SHARENAME\EXECUTABLE.exe ?

needforspeed · 11 Jun 2012 at 16:04

What server is it? I think you can install using Group Policy with a .msi file?

slipd · 11 Jun 2012 at 16:06

needforspeed said:
What server is it? I think you can install using Group Policy with a .msi file?

Its a brand new 2008 server. The program I'm installing installs from an .exe - does that matter?

Cheers.

needforspeed · 11 Jun 2012 at 16:13

I think you should have posted on the Servers and Enterprise Solutions section? You could try what NealR suggested?

ChrisD. · 12 Jun 2012 at 09:09

It needs to be installed locally.

You could push the program onto the client machines using something like SCCM or similar (I'm unfamiliar with the latest name/version).

Either that or if you have a TS server license, allow the users to RDP onto the server and set their RDP file so that they can only open the program.

bignev72 · 12 Jun 2012 at 11:44

sam.wheale said:
Its a brand new 2008 server. The program I'm installing installs from an .exe - does that matter?

Cheers.

You can't install an .exe via Group Policy. You might be able to convert the exe into a .msi though. Google "convert exe to msi" and you will find some free limited programs.

Alternatively you could write a logon script to run the exe. However this would be messy as it would prompt each login for install.