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?
tamray_techAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
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

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
 
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.