Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1408
  • Last Modified:

Usrlogon.cmd does not run at login on 2003 server

I just added a new 2003 server to our terminal server farm. As I understand it, usrlogon.cmd is supposed to automatically run when users connect via RPC. It does run for all users on our other servers, but doesn't seem to be running for the new one. How can I force it to run as the others do?
0
tamray_tech
Asked:
tamray_tech
1 Solution
 
delyan_valchevCommented:
If usrlogon.cmd is configured as logon script through GPO, you should check if the GPO has any security settings, preventing it to be applied on your new server. If the script is locally executed it should be configured to run from the same place as on the old servers (All users Startup, registry HKLM/Software/Microsoft/Windows/Current Version/Run)
Hope it helps!
0
 
tamray_techAuthor Commented:
The script was actually running, but erring out. The reg file was there by default, so I did not need to make changes there. The fix was to copy the cmd file and common application script folder to the new server, overwriting what was there. This answer was correct, according to the question
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now