Re: Win2000 Pro will not process logon script

Paul:

Thanks for your hlep.
I will let you know what I find out.

Myrt

"Paul Bergson [MVP-DS]" wrote:

Group Processing bypassed -or- can't find domain controller

Look in all logs, but the Application Log would be the most likely place

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Myrt in MT" <MyrtinMT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DA232CC0-B844-4806-B694-D3627591435F@xxxxxxxxxxxxxxxx
I found the link, Thank you.

I am not at work today I wil l have to check the logs Monday. What kind of
messages would I expect to see if the link speed was a factor? Would the
messages be on the client log or the dc log?

"Paul Bergson [MVP-DS]" wrote:

The link I included will provide additional details. Was there any
messages
in the log files?

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.

"Myrt in MT" <MyrtinMT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6489FDD1-126C-4129-8396-19FE9F2CC2E6@xxxxxxxxxxxxxxxx
here is no firewall between the machines that do not run the script and
others that do. In one section that all connect thru the same switch,
the
newer machines run the script and some of the older ones do not.

I am not familar with the "slow link" policy. Where can I find out more
about that? Would there be a differnce in the slow link process between
XP
machines and 2000 machines?

"Paul Bergson [MVP-DS]" wrote:

What kind of messages are you getting in the Event Logs (Check
Application
Log for sure)? Are these machines at a location where slow link
policy
could be setting in? Slow link is where a machine pings the dc and
determines its repsonse time, if it is too slow it will bypass running
the
logon script. It could also be at a location where icmp traffic
(Ping)
is
being blocked because of a firewall is in between the two. So even
though
there is a good connection someone started the firewall and so the
machine
assumes a slow link and it won't run.

http://support.microsoft.com/default.aspx/kb/227260

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.

"Myrt in MT" <MyrtinMT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E0DA0A01-3BBC-48E6-ABD6-DC41516D5292@xxxxxxxxxxxxxxxx
I work as an asst SA for a small hospital. I have been there about 3
months.

The present SA does not use group policy to help administer the
Win2003
domain. I was asked to devise a way to place a url shortcut on all
desktops
in the domain. I put together a script, tested it and deployed it. I
deployed
the script using a "Desktop" group policy that ran after the default
domain
policy and a password policy. The script is supposed to run whenever
a
domain
user logs onto a Win2000 or WinXP machine.

The results of the deployment are mixed. The script is successful on
the
XP
machines and some Win2000 machines but does not run on several older
Win2000
platforms. I can log onto a computer that is not running the script
and
the
script will not run for me. But it runs fine on other newer machines
when
I
log on. This leads me to believe that there is something about the
older
Win2000 machines that is preventing the script from running using
group
policy logon script. When I run the script manually on the offending
machines, it runs fine.

We have a Win2003 domain what was migrated from an NT domain. The
migration
of user names into active directly had goofy results. Some users
have
their
names reversed, some are not listed in the GAL except by logon name.

I need some hints I can look at to figure out why some of my Win2000
machines are not running my script.












.

Relevant Pages

  • Re: Win2000 Pro will not process logon script
    ... Are these machines at a location where slow link policy ... The present SA does not use group policy to help administer the Win2003 ... I put together a script, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2000 Pro will not process logon script
    ... newer machines run the script and some of the older ones do not. ... I am not familar with the "slow link" policy. ... Would there be a differnce in the slow link process between XP ...
    (microsoft.public.windows.server.active_directory)
  • Re: Use Group Policy to assign computer startup scripts for 2007 Office deployment
    ... The Office 2007 pro install takes nearly 40 minutes, ... I just edited the local machine policy to run this script on ... Simplify Group Policy Troubleshooting with the NEW GPExpert ... machines under it. ...
    (microsoft.public.windows.group_policy)
  • Re: Win2000 Pro will not process logon script
    ... newer machines run the script and some of the older ones do not. ... I am not familar with the "slow link" policy. ... Would there be a differnce in the slow link process between XP ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2000 Pro will not process logon script
    ... newer machines run the script and some of the older ones do not. ... I am not familar with the "slow link" policy. ... Would there be a differnce in the slow link process between XP ...
    (microsoft.public.windows.server.active_directory)