2k server logon script being strange

2k workstations

I put some stuff in our login bat to do some logging, innocuous stuff like:

echo %logonserver% >> \\server\logs$\logon\%computername%.txt

trouble is in the log files, the results are echoed twice for no apparent reason. I never had any trouble like this when i did this sort of thing on NT.

any ideas?
LVL 3
browolfAsked:
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.

PanadminCommented:
Could the login script be running twice, as a result of group policy and being defined on the user account?
0
browolfAuthor Commented:
that's a thought, because all our accounts were originally NT ones and had the login script on the user account. when we migrated we naturally put it in the group policy as well. will check tomorrow.
0
browolfAuthor Commented:
our older accounts do have  the login script in the user profile as well as  the group policy. Atm we have the logon scripts visible but we only see one dos window.  the order we have the login scripts is
printerscript using rundll then logon script.  this is what we see when we log on.

if the login script was running twice i'd be expecting to see 2 dos windows.

however i've just experimented with making a copy of the logon script and altering one of the loglines and then changing the user profile script on our test user account to point to this one instead. and it does indeed run invisibly.

bugger. i wonder if this has some bearing on why some logons can be quite slow. 2-3mins.

 
0
PanadminCommented:
Are the logged lines still duplicated with only one login script running? If they are, there's probably some other location where the code is running twice. Does your batch file call any other batch files, or vice versa?

I agree, running the script twice will increase the logon time.
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
browolfAuthor Commented:
it's fixed now. perhaps i didnt make it quite clear.
0
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
Windows 2000

From novice to tech pro — start learning today.

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.