Re: Running Login Scripts on XP using NT 4.0 Netlogon

From: Roger Abell (mvpNOSpam_at_asu.edu)
Date: 03/19/04


Date: Thu, 18 Mar 2004 18:45:01 -0700

The scripts are working at least far enough into them to
get the drive mapped. So, you should find out why/where
it (evidently) errors out and stops running. There are a
number of DOSish things that were OK for Win9x that
do not fly with XP. Have you tried running the script
in a cmd windows to see how it goes ?

Printers are an issue. There is a policy to allow the accounts
that you specify to install printer drivers. However, this policy
introduces a significant security vulnerability. Once a driver is
installed, the other accounts should be able to set up their default
printer without having to install the driver again, and if you use
a print server this will be more simple.

-- 
Roger Abell
Microsoft MVP (Windows Server System: Security)
MCSE (W2k3,W2k,Nt4)  MCDBA
"Ed D." <ed@mv.k12.wa.us> wrote in message
news:ffb901c40d2b$e51b1a50$a101280a@phx.gbl...
> I work in an Educational Lab environment that is a bit
> antiquated. We are running NT 4.0 Server and using Win 98
> clients. We are currently upgrading to XP on the client
> side. We have run into 2 issues. First, the login scripts
> will now only map their Home Share. The rest of the script
> does not execute. The scripts worked fine in the past with
> the Win 98 clients.
>
> The second is the labs has rotating users, they will sit
> at random systems and use their accounts. We have
> installed networked printers under user Administrator but,
> when a student logins in the printers are gone. The
> students had Power User rights only and I need to keep
> them that way. We also have their Globe Group set on the
> systems. I know this is wordy but, has anyone dealt with
> this issue. Any help would be great.
>
> Thanks


Relevant Pages

  • Re: Resolve Printer long names mapping by FQDN name
    ... Make sure that your machines use only domain internal DNS servers. ... script to map network printers during clients login to network. ... My scripts looks like this: ...
    (microsoft.public.windows.server.active_directory)
  • Re: pushprinterconnection.exe
    ... You said you used a startup script right? ... Since startup scripts (versus ... In the Group Policy Object Editor: ... Logged on as administrator and didn't get the assigned printers. ...
    (microsoft.public.windows.group_policy)
  • Re: pushprinterconnection.exe
    ... setting in group policy (not startup scripts): ... In the Group Policy Object Editor: ... Logged on as administrator and didn't get the assigned printers. ... Does GPO deployment work under that scenario? ...
    (microsoft.public.windows.group_policy)
  • Re: PLEASE EVALUATE THIS SCRIPT INSTEAD Re: Please evaluate logon script
    ... The scripts are at work, I'll copy and send them tomorrow ... our network is up 99%. ... drives and printers. ... so I can display the default and all printers available to ...
    (microsoft.public.scripting.vbscript)
  • Re: Mapping a drive
    ... thanks for the idea on the printers. ... Jim ... > connection is made to the right share. ... > I also connect to printers in CMD scripts using the following command ...
    (microsoft.public.windows.group_policy)