RE: Login Scrips in a Mixed World

From: Mike Pisano (mpisano_at_ConcordiaFreight.com)
Date: 04/01/04 

Date: Thu, 1 Apr 2004 08:55:59 -0800

Abraham,

Thanks for the reply,

A few Unclear issues:

If I "Create an Organization Unit for the Windows XP
workstations in the remote office, and move these
computers to that OU."

Does it Matter if these computers are NT4, and their local
server is a NT4 BDC; Can I create I OU for a NT4 Server or
only 2000\2003?

Also it's the uses login Script, not computers. For Each
BDC (Remote Office) thier are scripts for depatrments ie
(Sales\Customer Service\Operations...).

If the XP Workstations will Detect and use the GC over the
local BDC and cache the credentials, what about the Login
Script if the GC is unavalable? Does the Workstation cache
the last login script?

Thanks Again,

Mike Pisano

>-----Original Message-----
>Hi Mike,
>
>Thank you for posting here.
>
>Based on your description, I understand that the login
scripts can't run on
>the Windows XP workstations in a remote site. If I have
misunderstood your
>concerns, please let me know.
>
>Because the Windows XP workstations connect to the PDC
via WAN and Windows
>XP does not wait for the network to be fully initialized
at startup and
>logon. Therefore, to guarantee the login scripts can run
on the Windows XP
>workstations, please follow the next steps:
>1. Create an Organization Unit for the Windows XP
workstations in the
>remote office, and move these computers to that OU.
>2. Create a Group Policy Object for the OU.
>3. Enable the "always wait for the network at computer
startup and logon"
>(Computer Configuration\Administrative
Templates\System\Logon) police.
>
> After those have been down, if the problem persists, on
one of the Windows
>XP workstations, run "gpresult /v>1.txt" at command
prompt, send me an
>email with the file at v-abrahc@microsoft.com.
>
>The answer to your questions is below:
>1. Windows XP Professional workstations don't use the way
as the NT 4.0
>used to run login script.
>2. If their local server is NT, the Windows XP will
attempt to connect to
>Windows Server 2003 Domain Controllers via WAN link to
perform the
>authentication and execute policies settings.
>3. Windows XP Professional workstations can not get the
script polices from
>the NT 4.0 Domain Controllers. Therefore they will get
script polices from
>the Windows Server 2003 Domain Controllers via WAN link.
>4. If the Windows Server 2003 Domain Controller is
unavailable, by default,
>the users are logged on using cached credentials.
>5. To optimize performance, you should install a Domain
Controller and a
>Global Catalog at each remote office.
>6. It is impossible for Windows XP to join the NT domain.
>
>If you have any questions or concerns regarding this
issue, please do not
>hesitate to let me know.
>
>Thanks & regards,
>
>Abraham Cheng [MSFT], MCSE 2000
>Microsoft Online Partner Support
>
>Get Secure! - www.microsoft.com/security
>
>=====================================================
>When responding to posts, please "Reply to Group" via
your newsreader so
>that others may learn and benefit from your issue.
>=====================================================
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>
>--------------------
>>Content-Class: urn:content-classes:message
>>From: "Mike Pisano" <Mpisano@ConcordiaFreight.com>
>>Sender: "Mike Pisano" <Mpisano@ConcordiaFreight.com>
>>Subject: Login Scrips in a Mixed World
>>Date: Wed, 31 Mar 2004 12:43:50 -0800
>>Lines: 48
>>Message-ID: <1672501c41760$dfa9e850$a301280a@phx.gbl>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>>Thread-Index: AcQXYN+nqzFP6riSQlOitkZy4MUVww==
>>Newsgroups: microsoft.public.windows.group_policy
>>Path: cpmsftngxa06.phx.gbl
>>Xref: cpmsftngxa06.phx.gbl
microsoft.public.windows.group_policy:5962
>>NNTP-Posting-Host: tk2msftngxa11.phx.gbl 10.40.1.163
>>X-Tomcat-NG: microsoft.public.windows.group_policy
>>
>>Login Scrips in a Mixed World
>>
>>Hi All,
>>
>>I have a pure NT4 Server\Workstation Wan we build back
in
>>1999 that's been running great. We have a PDC and BDC in
>>NY and remote BDC at each satellite offices to support
the
>>local clusters of NT4 workstations for
>>File\Print\Autho\WINS...
>>
>>We are trying to introduce XP workstations into the mix,
>>so we upgraded the NT4 PDC to 2003 server and build the
>>beginning of an AD tree. So far all the existing BDC
are
>>syncing great with the 2003 server.
>>
>>When we install XP workstation at a remote site, it does
>>find the PDC(2003 AD server) and is able to add the new
XP
>>workstation to the Domain, but the login scripts will
not
>>run when the user logs in?
>>
>>It seems back it the 2000 days MS changed the way login
>>scripts work. We're use to the NT4 method of Netlogon
>>Share.
>>
>>Issues \ Questions:
>>1) Is their a way to have a XP prof Workstation use the
>>older NT4 method?
>>
>>2) If you must use the newer Policy and SYSVOL method,
>>what happens if their local server is NT; No Sysvol
Share?
>>
>>3) Do the workstation go back across the WAN for the
>>script?
>>
>>4) If so, what happens if the 2003 server is unavailable?
>>
>>5) Am I suppose to have a local DC or GC at the remote
>>offices is order for this to work correctly?
>>
>>6) Is their a way to join the Domain and Not the AD Tree
>>so the XP work like NT until theirs a local DC
>>
>>Sorry for any cross posts
>>
>>Thanks In advance,
>>
>>Mike Pisano
>>
>>
>
>.
>

Relevant Pages

  • Re: Change local administrator password for all PCs in the domain
    ... > I have about 200 workstations in my Windows 2000 domain. ... you could setup a custom script or Group Policy (in ... no workgroup machines. ...
    (microsoft.public.windows.server.scripting)
  • RE: Login Scrips in a Mixed World
    ... Because the Windows XP workstations connect to the PDC via WAN and Windows ... to guarantee the login scripts can run on the Windows XP ... remote office, and move these computers to that OU. ...
    (microsoft.public.windows.group_policy)
  • Re: GPO uninstall script
    ... GPO = Government Printing Office ... I have a Windows 2003 domain and few workstations joined to the domain. ... Now I want to use a script - that must be executed within GPO Default ...
    (microsoft.public.scripting.wsh)
  • Re: Limiting Ability to Join Domain
    ... Microsoft MVP - Windows NT Server ... They can add maximum 10 workstations ... > Authenticated Users group by default. ... >> Microsoft MVP - Windows NT Server ...
    (microsoft.public.windows.server.setup)
  • RE: Workstations unable to use the shared fax
    ... > Thank you for posting to the SBS Newsgroup. ... > I understand that your Windows XP Home clients cannot send fax. ... > Please understand that SBS 2003 Shared Fax requires the client workstations ...
    (microsoft.public.windows.server.sbs)