Solve : find file and copy?

1.	Solve : find file and copy?
Answer» yes but it will do next time.Quote from: Blisk on November 18, 2015, 12:16:38 PM yes but it will do next time. If you used my example it would work for new users as well. Quote from: Squashman on November 18, 2015, 07:27:19 PM If you used my example it would work for new users as well. Thank you I will CHECK your script again. When script must start when PC start or when user log in?Quote from: Blisk on November 19, 2015, 12:32:25 AM Thank you I will check your script again. When script must start when PC start or when user log in? As I said my previous post. Local computer policy. Which you could also implement at the domain level for the computer object but just as easy to do it once as a local policy on the computer. Or, you put the script in the startup folder. That is how we do it where I work. Quote from: Squashman on November 05, 2015, 08:55:12 AM Well if know how to do it for a domain then I would assume you know what Group Policy editor is. You can SET a group policy on that computer for a logon script. User Configuration\Windows Settings\Scripts (Logon/Logoff) ALTERNATIVELY any programs you put in this folder will startup when any user logs in. This is how we do it where I work. C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup Both these methods have been available since Windows 2000, which is as far back as I can remember. Might have been in Windows NT but only used it briefly. Another alternative: Since this is a configuration file, I'll assume that it's needed by some program INSTALLED on the computer. Rather than launching the program directly, create a batch file which will first check if the configuration file is in the proper place ("%UserProfile%\AppData\Local\Microsoft"), copy it if not, then launch the real program. Or do all three: check all users when the computer is first turned on, check each user when they log on to the computer, and check again when they try to launch the program needing the info. The last two are the easiest to code because you can get the current user with the %UserProfile% environment variable, and only check their configuration file, not everyone elses. Plus, you can use the policy editor to ensure the script is always run on those conditions (I think? I'm not as familiar with the policy editor these days..)

Answer»

yes but it will do next time.Quote from: Blisk on November 18, 2015, 12:16:38 PM

yes but it will do next time.

If you used my example it would work for new users as well. Quote from: Squashman on November 18, 2015, 07:27:19 PM

If you used my example it would work for new users as well.

Thank you I will CHECK your script again.
When script must start when PC start or when user log in?Quote from: Blisk on November 19, 2015, 12:32:25 AM

Thank you I will check your script again.
When script must start when PC start or when user log in?

As I said my previous post. Local computer policy. Which you could also implement at the domain level for the computer object but just as easy to do it once as a local policy on the computer.
Or, you put the script in the startup folder. That is how we do it where I work.
Quote from: Squashman on November 05, 2015, 08:55:12 AM

Well if know how to do it for a domain then I would assume you know what Group Policy editor is.
You can SET a group policy on that computer for a logon script.
User Configuration\Windows Settings\Scripts (Logon/Logoff)

ALTERNATIVELY any programs you put in this folder will startup when any user logs in. This is how we do it where I work.
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup

Both these methods have been available since Windows 2000, which is as far back as I can remember. Might have been in Windows NT but only used it briefly.

Another alternative: Since this is a configuration file, I'll assume that it's needed by some program INSTALLED on the computer. Rather than launching the program directly, create a batch file which will first check if the configuration file is in the proper place ("%UserProfile%\AppData\Local\Microsoft"), copy it if not, then launch the real program. Or do all three: check all users when the computer is first turned on, check each user when they log on to the computer, and check again when they try to launch the program needing the info. The last two are the easiest to code because you can get the current user with the %UserProfile% environment variable, and only check their configuration file, not everyone elses. Plus, you can use the policy editor to ensure the script is always run on those conditions (I think? I'm not as familiar with the policy editor these days..)

Solve : find file and copy?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment