Help putting a file in all users' "Startup" folder

[jgq85]

I am trying both FileInstall and FileCopy. I can get it to work if I pick a folder anywhere else that exists, but for some reason if I try to make the path "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp" or @StartupCommonDir, it doesn't create or copy the file there depending on what I try. 

The reason I need to put it here is because I can't run the exe i'm making in the user's context. My remote management tool will only run under the SYSTEM context. So I think this is the best way I can get it to the user's start up folder, as well as without triggering a UAC prompt. 

Anyone have advice? 

I've tried each of the following: 

• FileInstall("C:\ITScript.exe", "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp", 1)
• FileInstall("C:\ITScript.exe", @StartupCommonDir, 1)
• FileCopy("C:\ITScript.exe", "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp")
• FileCopy("C:\ITScript.exe", @StartupCommonDir)

 

 

Edited April 15, 2020 by jgq85

[1957classic]

I believe your source location is wrong but I know your destination is incomplete.
I think it should be...

FileInstall("ITScript.exe", @StartupCommonDir & "\ITScript.exe", 1)
Or
FileCopy("ITScript.exe", @StartupCommonDir & "\ITScript.exe", 1)

 

[seadoggie01]

Specifically, this isn't working because FileCopy and FileInstall expect either the full path to a file or a directory with a trailing backslash. If there isn't a trailing backslash, your directory looks like a file without an extension on the end. If you print any of the directory macros, you'll see that they don't contain a trailing backslash (a pet peeve of mine, but okay).

[jgq85]

14 hours ago, 1957classic said:

I believe your source location is wrong but I know your destination is incomplete.
I think it should be...

FileInstall("ITScript.exe", @StartupCommonDir & "\ITScript.exe", 1)
Or
FileCopy("ITScript.exe", @StartupCommonDir & "\ITScript.exe", 1)

 

Hi @1957classic,

Thanks for the reply. I'm compiling the script to exe so does that mean I have to specify the path to the ITScript.exe on the machine I'm compiling from? So that it merges into the exe on the target system? 

[Nine]

Once compiled, you cannot use any variables in the source path.  Read help file, it clearly states it.  So if the location of the source file varies, you will need to adjust  you script  But you could use a map drive or something similar so you don't have to edit the script for every computer.

[jgq85]

2 minutes ago, Nine said:

Once compiled, you cannot use any variables in the source path.  Read help file, it clearly states it.  So if the location of the source file varies, you will need to adjust  you script  But you could use a map drive or something similar so you don't have to edit the script for every computer.

On the help KB (https://www.autoitscript.com/autoit3/docs/functions/FileInstall.htm) the example is:

FileInstall("C:\Test.bmp", @ScriptDir & "\Test.bmp")

In my case isn't the Test.bmp my ITScript.exe ? Example uses C:\Test.bmp, not just "Test.bmp"

[Nine]

Let me explain :

1) c:\test.bmp   ==> is an absolute path (the file MUST be located inside c:\)

2) test.bmp ==> is a relative path to the script folder  (it means, that the file MUST be at the same place as the script)

3) m:\test.bmp ==>  where m: is a map drive that relates to any other computer/drive/network that contains the file you want.

I suggest you use the 3rd solution where you can apply the same script to any computer in your environment.

[rudi]

One more point: What you are trying to do is to create a lot of independent copies of the exact same EXE file.

 

Ooooghhh!

 

I'd like to mention, that you place in the @StartupCommonDir a LNK to "one-file-on-a-network-share" for all computers.

 

$WD="\\server\share\Path1\Path2"
$EXE="ITscript.EXE"
$LNK=@StartupCommonDir & "\" & StringTrimRight($EXE,3) & "LNK"
FileCreateShortcut($WD & "\" & $EXE,$LNK,$WD,"","Description what this EXE is doing")

Rudi