Re: Script in GPO
- From: "Paul Bergson" <pbergson@xxxxxxxxxxxxxxxxx>
- Date: Thu, 27 Apr 2006 12:54:35 -0500
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
.
- Prev by Date: Monitoring AD
- Next by Date: Windows Server 2K/2K3 DFS setup and interoperability
- Previous by thread: Monitoring AD
- Next by thread: Re: Script in GPO
- Index(es):
Relevant Pages
|
