Halp Install network Application in Windows 7

Coqui

Piccolo Pete
Oct 14, 2004
35,593
4,667
673
45
Columbus, OH
Marklar
₥3,593
Trying to run a setup for an application which resides on our network. The application will be running off the network as well.

When I try to install it in Windows 7, the drive mappings don't show up when you modify the location. (leaving it at default just says they aren't there)

I've already tried running the application in compatability mode, as an administrator, copying the setup files locally, and enabling file/print/media sharing. What am I missing?
 

JAXvillain

Curly_Sue
Oct 13, 2004
68,732
1,999
923
Marklar
₥0
if the app is running off the network you can't just drop a shortcut to the exe on the desktop?
 

fly

omg
Oct 1, 2004
76,197
26,090
1,323
Marklar
₥64,238
Steam
mattressfish
Last edited:

Coqui

Piccolo Pete
Oct 14, 2004
35,593
4,667
673
45
Columbus, OH
Marklar
₥3,593
Very simple doing this then running as administrator allowed it to work:

1) Open up the command prompt *in administrator mode*
2) Type net use driveletter: \\servername\share
 

Coqui

Piccolo Pete
Oct 14, 2004
35,593
4,667
673
45
Columbus, OH
Marklar
₥3,593
Wait, so you didn't use a mapped network drive from the beginning?

Drives were already mapped through a script. I verified they were there. I attempted to run as an administrator (my account and it didn't work) I right clicked and ran as administrator (which technically should have still been using my account since I hadn't generated a default admin account yet)

So I had to manually map after automatically mapping the drive just to get it to work. I would not have been able to double click on setup had the drive not been mapped.

EDIT: This is my first time ever really touching Windows 7, so you'll have to forgive me if things that are obvious to most technicians haven't come to me yet.
 

Josh

Biff Clurton
Oct 9, 2006
7,752
4,054
523
East bumfuck.
Marklar
₥6,678
Ah I see. Strange the installer didn't recognize the mapped drives via a script (probably a GPO I assume). 2003 server or 2008? I've heard of some quirkyness with 2003 Server and Win7 clients. R2 is supposed to be better than original 2003 when it comes to Win7.

Most of my clients have XP computers and haven't jumped to 7. :|
 

Coqui

Piccolo Pete
Oct 14, 2004
35,593
4,667
673
45
Columbus, OH
Marklar
₥3,593
Ah I see. Strange the installer didn't recognize the mapped drives via a script (probably a GPO I assume). 2003 server or 2008? I've heard of some quirkyness with 2003 Server and Win7 clients. R2 is supposed to be better than original 2003 when it comes to Win7.

Most of my clients have XP computers and haven't jumped to 7. :|

08. Although this apparently has been an issue since Vista (another OS I have never touched)
 

fly

omg
Oct 1, 2004
76,197
26,090
1,323
Marklar
₥64,238
Steam
mattressfish
Ah I see. Strange the installer didn't recognize the mapped drives via a script (probably a GPO I assume). 2003 server or 2008? I've heard of some quirkyness with 2003 Server and Win7 clients. R2 is supposed to be better than original 2003 when it comes to Win7.

Most of my clients have XP computers and haven't jumped to 7. :|

No, it didn't recognize the drives because the install was run as 'administrator' but the drives weren't mapped as admin...
 

JAXvillain

Curly_Sue
Oct 13, 2004
68,732
1,999
923
Marklar
₥0
Of course now I'm trying to figure out how to run login scripts on users who don't have admin access when UAC is enabled.

script a group that has admin access specifically for the purpose of running things in the present/future and add it to all new jobs.
 

Josh

Biff Clurton
Oct 9, 2006
7,752
4,054
523
East bumfuck.
Marklar
₥6,678
To work around this issue, I have created a new version of Launchapp.wsf (attached below). I took the existing version of Launchapp.wsf and combined it with code from John Howard’s blog (http://blogs.technet.com/jhoward/archive/2008/11/19/how-to-detect-uac-elevation-from-vbscript.aspx). If this version of Launchapp.wsf detects it is running elevated, it deletes/creates the scheduled task as the original did. If it is not running elevated, it simply launches the app or script passed on the command line directly.

So you're running this modified version and not the original launchapp.wsf?
 

Coqui

Piccolo Pete
Oct 14, 2004
35,593
4,667
673
45
Columbus, OH
Marklar
₥3,593
To work around this issue, I have created a new version of Launchapp.wsf (attached below). I took the existing version of Launchapp.wsf and combined it with code from John Howard’s blog (http://blogs.technet.com/jhoward/archive/2008/11/19/how-to-detect-uac-elevation-from-vbscript.aspx). If this version of Launchapp.wsf detects it is running elevated, it deletes/creates the scheduled task as the original did. If it is not running elevated, it simply launches the app or script passed on the command line directly.

So you're running this modified version and not the original launchapp.wsf?

Yes. We thought that was the problem initially. It worked for a bit, but then stopped working sometime over the weekend.