Re: Script in GPO
- From: "Paul Bergson" <pbergson@xxxxxxxxxxxxxxxxx>
- Date: Fri, 28 Apr 2006 07:58:32 -0500
It is in the registry
--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
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.
"Not a happy bunny" <Bunny@xxxxxxxxxxxx> wrote in message
news:DF8BD11B-12DE-4C78-9F17-FD2869BB5C01@xxxxxxxxxxxxxxxx
A printer was the issue. Not the server.
I could have changed the share name back to the old one but worried that
if
I changed the script back to match it, we would then have the same issue
where the system would continue to look for the new share regardless that
the
script had been changed back.
90% of the user that have now logged on are not get the error message
flash.
As the script was working correctly, what would have cause the system to
still attempt to find the previous printer? Reg key? Ini file?
Where else would a user's printer mapping be stored.
Thanks for the assistance.
"Paul Bergson" wrote:
Go to the new print server and alias the name to the old server. Enter
the
old server name in DNS. This way your new print server will handle old
and
new names the only requirement is the share name is going to have to be
the
same.
http://support.microsoft.com/kb/281308/en-us
--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
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.
"Not a happy bunny" <Bunny@xxxxxxxxxxxx> wrote in message
news:3E448237-A0BC-419C-AB75-EA062B159CF3@xxxxxxxxxxxxxxxx
Part of the logon script attached to a GPO, is for mapping a LPT port.
The printer that it maps to is dead, so I changed the script to point
another newly installed printer.
The problem is that when user logs on, the system still attempts to
find
the
old printer and flash's up a connection error message stating that the
printer cannot be found. Ticking the "do not reconnect in the future"
option
and hitting "No" to continue the connection.. Gets you in ok. And the
correct
printer has been mapped.
The next day when users attempt to logon, the same message comes up.
What can still be telling the system to try the old mapping?
Thanks
.
- References:
- Re: Script in GPO
- From: Paul Bergson
- Re: Script in GPO
- Prev by Date: Re: Can i lock keyboard and mouse after userlogin for a timeperiod?
- Next by Date: Re: Second domain controller
- Previous by thread: Re: Script in GPO
- Next by thread: Windows Server 2K/2K3 DFS setup and interoperability
- Index(es):
Relevant Pages
|
