Absolutely

Have a network of about 25 workstations and today I added 5 workstations.
None of these new workstations will run the logon scripts. I can manually
map drives without a problem. I can browse out to the NETLOGON folder and
run the script without a problem. I can logon to any of the other existing
workstations as the same users I'm logging onto the new workstations as and
the script runs without issue. The machines joined the domain without a
problem. This is baffling the hell out of me.

Absolutely

BTW... there is only one DC.

"Absolutely" <abs@spam.never> wrote in message
news:OWbHsZVYIHA.4448@TK2MSFTNGP03.phx.gbl...
> Have a network of about 25 workstations and today I added 5 workstations.
> None of these new workstations will run the logon scripts. I can manually
> map drives without a problem. I can browse out to the NETLOGON folder and
> run the script without a problem. I can logon to any of the other
> existing workstations as the same users I'm logging onto the new
> workstations as and the script runs without issue. The machines joined
> the domain without a problem. This is baffling the hell out of me.
>
>

Pegasus \(MVP\)

"Absolutely" <abs@spam.never> wrote in message
news:uo0DFiVYIHA.3652@TK2MSFTNGP02.phx.gbl...
> BTW... there is only one DC.
>
> "Absolutely" <abs@spam.never> wrote in message
> news:OWbHsZVYIHA.4448@TK2MSFTNGP03.phx.gbl...
>> Have a network of about 25 workstations and today I added 5 workstations.
>> None of these new workstations will run the logon scripts. I can
>> manually map drives without a problem. I can browse out to the NETLOGON
>> folder and run the script without a problem. I can logon to any of the
>> other existing workstations as the same users I'm logging onto the new
>> workstations as and the script runs without issue. The machines joined
>> the domain without a problem. This is baffling the hell out of me.
>>
>>

How do you know that the logon script does not run? Modify
it by adding the line below to the very top, test it and post it here.
What can you see in c:\test.txt?

@echo off
echo %date% %time% %UserName% >> c:\test.txt

Absolutely

It wasn't running. I'm an idiot. Drugs after surgery are messing up my
thinking. I went back after I'd given it a rest and found that I was
specifying the script in the profile box, which explains another weird event
I was witnessing. I must have looked at that a hundred times and 4 hours
later it was as plain as day what I had done. Guess I know now why they say
I shouldn't play with dangerous stuff while taking these things.





"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
news:%23$0RKlZYIHA.4880@TK2MSFTNGP03.phx.gbl...
>
> "Absolutely" <abs@spam.never> wrote in message
> news:uo0DFiVYIHA.3652@TK2MSFTNGP02.phx.gbl...
>> BTW... there is only one DC.
>>
>> "Absolutely" <abs@spam.never> wrote in message
>> news:OWbHsZVYIHA.4448@TK2MSFTNGP03.phx.gbl...
>>> Have a network of about 25 workstations and today I added 5
>>> workstations. None of these new workstations will run the logon scripts.
>>> I can manually map drives without a problem. I can browse out to the
>>> NETLOGON folder and run the script without a problem. I can logon to
>>> any of the other existing workstations as the same users I'm logging
>>> onto the new workstations as and the script runs without issue. The
>>> machines joined the domain without a problem. This is baffling the hell
>>> out of me.
>>>
>>>
>
> How do you know that the logon script does not run? Modify
> it by adding the line below to the very top, test it and post it here.
> What can you see in c:\test.txt?
>
> @echo off
> echo %date% %time% %UserName% >> c:\test.txt
>

Pegasus \(MVP\)

Thanks for the feedback. Mind you, I'm still puzzled.
You reported that the logon script does not run for five
new ***workstations***, and then you fixed the problem
in the ***accounts*** profile. Perhaps you added not
only some workstations but some accounts too . . .


"Absolutely" <abs@spam.never> wrote in message
news:ub6FRNaYIHA.3556@TK2MSFTNGP02.phx.gbl...
> It wasn't running. I'm an idiot. Drugs after surgery are messing up my
> thinking. I went back after I'd given it a rest and found that I was
> specifying the script in the profile box, which explains another weird
> event I was witnessing. I must have looked at that a hundred times and 4
> hours later it was as plain as day what I had done. Guess I know now why
> they say I shouldn't play with dangerous stuff while taking these things.
>
>
>
>
>
>
> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
> news:%23$0RKlZYIHA.4880@TK2MSFTNGP03.phx.gbl...
>>
>> "Absolutely" <abs@spam.never> wrote in message
>> news:uo0DFiVYIHA.3652@TK2MSFTNGP02.phx.gbl...
>>> BTW... there is only one DC.
>>>
>>> "Absolutely" <abs@spam.never> wrote in message
>>> news:OWbHsZVYIHA.4448@TK2MSFTNGP03.phx.gbl...
>>>> Have a network of about 25 workstations and today I added 5
>>>> workstations. None of these new workstations will run the logon
>>>> scripts. I can manually map drives without a problem. I can browse out
>>>> to the NETLOGON folder and run the script without a problem. I can
>>>> logon to any of the other existing workstations as the same users I'm
>>>> logging onto the new workstations as and the script runs without issue.
>>>> The machines joined the domain without a problem. This is baffling the
>>>> hell out of me.
>>>>
>>>>
>>
>> How do you know that the logon script does not run? Modify
>> it by adding the line below to the very top, test it and post it here.
>> What can you see in c:\test.txt?
>>
>> @echo off
>> echo %date% %time% %UserName% >> c:\test.txt
>>
>
>

Absolutely

Yea, accounts too. Sorry.


"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
news:OhcRvEbYIHA.6140@TK2MSFTNGP02.phx.gbl...
> Thanks for the feedback. Mind you, I'm still puzzled.
> You reported that the logon script does not run for five
> new ***workstations***, and then you fixed the problem
> in the ***accounts*** profile. Perhaps you added not
> only some workstations but some accounts too . . .
>
>
> "Absolutely" <abs@spam.never> wrote in message
> news:ub6FRNaYIHA.3556@TK2MSFTNGP02.phx.gbl...
>> It wasn't running. I'm an idiot. Drugs after surgery are messing up my
>> thinking. I went back after I'd given it a rest and found that I was
>> specifying the script in the profile box, which explains another weird
>> event I was witnessing. I must have looked at that a hundred times and 4
>> hours later it was as plain as day what I had done. Guess I know now why
>> they say I shouldn't play with dangerous stuff while taking these things.
>>
>>
>>
>>
>>
>>
>> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
>> news:%23$0RKlZYIHA.4880@TK2MSFTNGP03.phx.gbl...
>>>
>>> "Absolutely" <abs@spam.never> wrote in message
>>> news:uo0DFiVYIHA.3652@TK2MSFTNGP02.phx.gbl...
>>>> BTW... there is only one DC.
>>>>
>>>> "Absolutely" <abs@spam.never> wrote in message
>>>> news:OWbHsZVYIHA.4448@TK2MSFTNGP03.phx.gbl...
>>>>> Have a network of about 25 workstations and today I added 5
>>>>> workstations. None of these new workstations will run the logon
>>>>> scripts. I can manually map drives without a problem. I can browse
>>>>> out to the NETLOGON folder and run the script without a problem. I
>>>>> can logon to any of the other existing workstations as the same users
>>>>> I'm logging onto the new workstations as and the script runs without
>>>>> issue. The machines joined the domain without a problem. This is
>>>>> baffling the hell out of me.
>>>>>
>>>>>
>>>
>>> How do you know that the logon script does not run? Modify
>>> it by adding the line below to the very top, test it and post it here.
>>> What can you see in c:\test.txt?
>>>
>>> @echo off
>>> echo %date% %time% %UserName% >> c:\test.txt
>>>
>>
>>
>
>