Windows 2000 server with XP client logon script question

I have created a simple logon script to map some network drives.  I called the script startup.bat and placed it in the \winnt\sysvol\%domain%\scripts directory. (Where %domain% is the name of the company)

I then went into AD users and computers, opened the profile of a user and put \\server\sysvol\%domain%\scripts\startup.bat into the logon script box.

Why doesn't it run?
dkuhlmanAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Casca1Commented:
I couldn't begin to imagine why it doesn't run. However, I can tell you a good way to get it to run. Apply it through a group policy.
Open AD User and computers, right click your domain, and select properties.
In the properties screen, select the group policy tab, click edit, user, windows settings, scripts.
Double click logon scripts, click add, and then browse to your script location.
After you add it, close out to the AD User and computers, and then go to your users that you added the script to in their profile, and remove it.
It could be cached logons are causing your issue, jeez, I dunno.
But through GPO scripting, if it doesn't work, it's because your client used a cahced logon, which will happen when a Global Catalog server can't be contacted to validate the logon request.
0
P1iskenCommented:
It depends on if you are having the client Log in from across the network or on the local machine... I am guessing across the network, just your comments do not specify...

For a logon script to be ran, it has to be accessible by the client that needs to run it.. So if User A needs to be able to execute that logon script, it has to be shared to him with at least read access...

To test this, have the user logon to the workstation and then you can goto:
Start -> Run -> And type "\\servername\sharename\pathtologinscript" minus the quotes of course...

If that person can not access it, then it will not execute at logon. You also should be using the same path in the Client's properties that the user has to type to access it...

Good luck and let us know...
0
strangedesignCommented:
try just inserting
startup.bat
in the profile and not the full path
 \\server\sysvol\%domain%\scripts\startup.bat
0

Experts Exchange Solution brought to you by

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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.