Logon script error silencing

Hello, I'm not the most experienced with logon scripts.  I would like our script to remove any mapped network drives with the letters p through z each time a user logs on.  However with the script as follows I end up flooding the majority of end users with a bunch of ERROR 2250's when the mapped network drive doesn't exist at logon.  Here's how I have it written:

net use p: /delete
net use q: /delete
net use r: /delete
net use s: /delete
net use t: /delete
net use u: /delete
net use v: /delete
net use w: /delete
net use x: /delete
net use y: /delete
net use z: /delete

How can I disable this bounce-back error reporting each time a drive is not found?
Thanks in advance
Who is Participating?

Improve company productivity with a Business Account.Sign Up

oBdAConnect With a Mentor Commented:

@echo off
for %%a in (p q r s t u v w x y z) do net use %%a: /delete >NUL 2>&1
Alternative, if you want to stay with a single line:
@for %%a in (p q r s t u v w x y z) do @net use %%a: /delete >NUL 2>&1

Open in new window

Simply send the errors into the NUL device (and you can do that in a loop, btw):

for %%a in (p q r s t u v w x y z) do net use %%a: /delete >NUL 2>&1

Open in new window

Todd MummertConnect With a Mentor Commented:

net use p: /delete 2>NUL

if there was output on stdout as well , you could use

net use p: /delete >NUL 2>&1

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

maingateincAuthor Commented:
Ok I see when I make these changes that I get a response that just says NUL instead of the 2250 ERROR.  Is there a way to disable the response at all?  Or a way to run that part of the script silently?  I tried @ECHO OFF at the top but it didn't work
Todd MummertCommented:

Can you attach your entire script?   Or create a smaller script that still exhibits the same problem and attach that.    What specific OS version?

maingateincAuthor Commented:
You bet; here it is (wouldnt let me attach as .bat, had to leave it a .txt)

Pushing this out through AD/sysvolume directory on Windows 2003 Server Standard to Windows XP Pro workstations
Runs just nice and quiet for me.
You might want to add the "@echo off" at the beginning, but other than that, there should be nothing displayed at all.
Does that happen as well when you run the script manually?
maingateincAuthor Commented:
Hmm yes whether I have it in the script or run it manually we get the following window that appears with a sleu of message lines
maingateincAuthor Commented:
Well @echo off wasn't working before, like I said, but with the new command string from above combined with @echo off it ran silently!  Thanks guys
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.

All Courses

From novice to tech pro — start learning today.