Cunningham's IMPACT software

[arthur231283]

Does any one have any instructions on how to install Cunningham's IMPACT cashless catering software on a workstation?

 

Every time it has been installed before the bursar has called the Cunningham's helpdesk and they have used logmein123 to remotely install it. Which is fine but if I need to quickly install it on more workstations or re-install it I don't want to have to call them every time.

 

Thanks in advance

[kmount]

Hi there,

 

from memory...

 

Map a drive to the impactserver\impact

 

Copy the impact folder from C:\ on the server to c:\ on the workstation, install Biostation from the bioupdate folder under impact and then there's a config file where you have to define the path (with the drive you mapped) to where it lives and it worked fine.

 

I used to use this for the bursar to set up the free school meals etc over the summer before folks came back.

 

(It doesn't use fingerprinting or anything on this host .... you'd need more info for that to work!)

[arthur231283]

Thanks for the reply.

 

I can get the software to work but it only works after I manually authenticate with the share.

 

I have to open the share input the username and password for the localadmin account on the impact server then I can login.

 

Is there a way of automatically authenticating with the share so I wont have to get the user to do it.

 

Thanks

[kmount]

You can map the drive specifying those credentials in a logon script.

[mjs_mjs]

You can map the drive specifying those credentials in a logon script.

 

have tried a vbs script;

Set objNetwork = WScript.CreateObject("WScript.Network")
strLocalDrive = "y:"
strRemoteShare = "\\10.218.166.61\Impact"
strPer = "FALSE"
strUsr = "Localadmin"
strPas = "password"
objNetwork.MapNetworkDrive strLocalDrive, strRemoteShare, strPer, strUsr, strPas
mDrive = "y:"
Set oShell = CreateObject("Shell.Application")
oShell.NameSpace(mDrive).Self.Name = "Impact"

 

replacing the password appropriatly to no effect, and also a batch script

net use y: \\10.218.166.61\Impact password/user:Loacladmin

 

nither of the two worked.

[kmount]

net use y: \\10.218.166.61\Impact /USER:NAMEOFMACHINE\administrator "password"

 

Worked fine here.

[p858snake]

net use y: \\10.218.166.61\Impact /USER:NAMEOFMACHINE\administrator "password"

 

Worked fine here.

It might be better to set up a domain user that has no rights execpt for what is needed to access the folders in case students and such get access to the script.

[mjs_mjs]

It might be better to set up a domain user that has no rights execpt for what is needed to access the folders in case students and such get access to the script.

 

good point - hadn't thought of that, question is, will the software work that way - the machine does not auth against our network.

[p858snake]

good point - hadn't thought of that, question is, will the software work that way - the machine does not auth against our network.

You should be able to use domain information against a remote machine that is in it if yours isn't (depending how locked down the network is).