An alternative to the startup folder is scheduled tasks. You can schedule a task to run on startup. For a GUI, run taskschd. To manage scheduled tasks from the command prompt, use schtasks. This program will allow you to create, delete, and run scheduled tasks.
Putting things here in this location is fine and not uncommon. Another common location where people place their scripts in the netlogon folder. I tend to prefer this because you can use better folder and script names. Just re-read your question. I think what you want to do is assign login scripts via Group Policy if I understand your question correctly. Also make sure that the Group Policy is being applied to your workstations as well. Sign up to join this community. The best answers are voted up and rise to the top.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Having trouble getting startup scripts to work in Server Ask Question. Asked 11 years, 9 months ago. Active 11 years, 9 months ago. This topic describes how to install and use scripts on a domain controller. If you want information about script use for the local computer, see Working with startup, shutdown, logon, and logoff scripts using the Local Group Policy Editor.
You can use Windows PowerShell scripts, or author scripts in any other language supported by the client computer. You must be a member of the Domain Administrators security group to configure scripts on a domain controller. Right-click the Group Policy Object you want to edit, and then click Edit. In Script Name , type the path of the script, or click Browse to search for the script file in the Netlogon shared folder on the domain controller.
In Script Parameters , type any parameters that you want, exactly as you would type them on the command line. Has anyone else here experienced this and if so, did you fix it? Can you check with the guys who have access to modifying the GPOs and see if they made any changes recently?
I can see some of the things they did via gpedit. I searched my archived e-mail for issues like this and one guy in the company said he just rejoined the machines to the domain and the problem went away.
It may solve the problem but that's not a solution for me. I've seen weird stuff like this when file and printer sharing has been disabled on a domain controller. Perhaps something in the users startup script is failing, and not timing out, or is hung?
0コメント