Подобная тема уже пару раз поднималась на форуме. 1, 2
Предложенный вариант добавления принтера посредством создания IP-порта и прямой печати в обход \\ИмяСервера - такой вариант не очень красивый.
Хочу поделиться ссылкой на исчерпывающее решение.
вот с сайта микрософт тичнет:
[more=Вопрос]Using WAIK/Deployment Workbench, we have successfully deployed Windows 7 Pro with applications to a set of dell Optiplex 745s. There are no errors during or after the deployment. However, after logging into the workstation, I am unable to print or add network printers.
Our printers are located in //powervault/<printer name>. //powervault is a windows 2008 R2 server with X64 and x32 drivers. I currently have windows XP, vista, 7 (64 and 32 bit) clients all printing fine. In the past, I've used a .bat file to deploy printers. There are a total of 6 printers from various manufacturers.
So far I have tried:
- Browsing to //powervault and double clicking on printers. This results in error 0x00000709 (Double check the printer name and make sure that the printer is connected to the network)
- deploying printers using a GPO (no error, but they do not appear on the client)
- adding printers by creating an IP port and directly printing (bypass //powervault) This works, but is unacceptable as //powervault runs print accounting software to bill our clients.
There isn't much information on the 0x00000709 error that makes sense. I only get this error on computers that have been deployed and not a hand-installed OS.
Does anyone have any ideas for further troubleshooting? Thanks in advance.[/more]
[more=Ответ]Hi,
Based on my research, this error code means ERROR_INVALID_PRINTER_NAME. To resolve this kind of issue, you need to take the following steps:
1. Searched for any PendingUpgrades or PostSPUpgradeKey in the Print Hive and removed the same.
2. Windows 7 will try to communicate to the print server via the Asynchronous RPC protocol, to disallow the use of the Asyncronous RPC protocol on the client, configure the following registry value:
Path: HKLM\Software\Policies\Microsoft\Windows NT\Printers\EnabledProtocols
Type: DWORD
Data: 6
3. Created the following Key.
reg add HKLM\SYSTEM\CurrentControlSet\Control\Print /v DnsOnWire /t REG_DWORD /d 1
Reference:
Error message when you try to connect to a printer by using an alias (CNAME) resource record: "Windows couldn't connect to the printer"
http://support.microsoft.com/kb/979602
4. Also created the following keys.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters Value Name: DisableStrictNameChecking Data Type: REG_DWORD Value: 1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parametersValue Name: Optional Names Data Type: REG_MULTI_SZ Value:
Server name : WOODS
IP : 10.205.2.214
5. Then change the value of "Previous name" in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows X64\Drivers\Version-3
"Previous Names"=hex(7):00,00
Reference:
Error message when you try to install a network printer on a Windows Vista-based computer: "Windows cannot connect to the printer Operation could not be completed (error 0x0000000d)"
http://support.microsoft.com/kb/947236/en-us
6. Also created a value in the HOST file for the Print Server at C:\Windows\System32\drivers\etc
7. Set the Point and Print restriction policy in Computer Configuration in Windows 7.
Policy for Windows 7 Clients:
============================
Computer Configuration | Administrative Templates | Printers | Point and Print
Restrictions.
Disabled the policy.
Also set the other policy as well.
Policy :
============================
Computer Configuration | Administrative Templates | System | Driver Installation
and used the policy "Allow Non-Administrators to install drivers for these device setup classes".
Also in that Policy we have to specify the class (GUID) of the driver.
Found the Class of printers : {4D36E979-E325-11CE-BFC1-08002BE10318}
8. Finally deleted the whole print hive. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print
Merged the Print hive from a fresh working Windows 7 64 Bit machine.
Restarted the spooler.
[/more]
Предложенный вариант добавления принтера посредством создания IP-порта и прямой печати в обход \\ИмяСервера - такой вариант не очень красивый.
Хочу поделиться ссылкой на исчерпывающее решение.
вот с сайта микрософт тичнет:
[more=Вопрос]Using WAIK/Deployment Workbench, we have successfully deployed Windows 7 Pro with applications to a set of dell Optiplex 745s. There are no errors during or after the deployment. However, after logging into the workstation, I am unable to print or add network printers.
Our printers are located in //powervault/<printer name>. //powervault is a windows 2008 R2 server with X64 and x32 drivers. I currently have windows XP, vista, 7 (64 and 32 bit) clients all printing fine. In the past, I've used a .bat file to deploy printers. There are a total of 6 printers from various manufacturers.
So far I have tried:
- Browsing to //powervault and double clicking on printers. This results in error 0x00000709 (Double check the printer name and make sure that the printer is connected to the network)
- deploying printers using a GPO (no error, but they do not appear on the client)
- adding printers by creating an IP port and directly printing (bypass //powervault) This works, but is unacceptable as //powervault runs print accounting software to bill our clients.
There isn't much information on the 0x00000709 error that makes sense. I only get this error on computers that have been deployed and not a hand-installed OS.
Does anyone have any ideas for further troubleshooting? Thanks in advance.[/more]
[more=Ответ]Hi,
Based on my research, this error code means ERROR_INVALID_PRINTER_NAME. To resolve this kind of issue, you need to take the following steps:
1. Searched for any PendingUpgrades or PostSPUpgradeKey in the Print Hive and removed the same.
2. Windows 7 will try to communicate to the print server via the Asynchronous RPC protocol, to disallow the use of the Asyncronous RPC protocol on the client, configure the following registry value:
Path: HKLM\Software\Policies\Microsoft\Windows NT\Printers\EnabledProtocols
Type: DWORD
Data: 6
3. Created the following Key.
reg add HKLM\SYSTEM\CurrentControlSet\Control\Print /v DnsOnWire /t REG_DWORD /d 1
Reference:
Error message when you try to connect to a printer by using an alias (CNAME) resource record: "Windows couldn't connect to the printer"
http://support.microsoft.com/kb/979602
4. Also created the following keys.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters Value Name: DisableStrictNameChecking Data Type: REG_DWORD Value: 1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parametersValue Name: Optional Names Data Type: REG_MULTI_SZ Value:
Server name : WOODS
IP : 10.205.2.214
5. Then change the value of "Previous name" in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows X64\Drivers\Version-3
"Previous Names"=hex(7):00,00
Reference:
Error message when you try to install a network printer on a Windows Vista-based computer: "Windows cannot connect to the printer Operation could not be completed (error 0x0000000d)"
http://support.microsoft.com/kb/947236/en-us
6. Also created a value in the HOST file for the Print Server at C:\Windows\System32\drivers\etc
7. Set the Point and Print restriction policy in Computer Configuration in Windows 7.
Policy for Windows 7 Clients:
============================
Computer Configuration | Administrative Templates | Printers | Point and Print
Restrictions.
Disabled the policy.
Also set the other policy as well.
Policy :
============================
Computer Configuration | Administrative Templates | System | Driver Installation
and used the policy "Allow Non-Administrators to install drivers for these device setup classes".
Also in that Policy we have to specify the class (GUID) of the driver.
Found the Class of printers : {4D36E979-E325-11CE-BFC1-08002BE10318}
8. Finally deleted the whole print hive. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print
Merged the Print hive from a fresh working Windows 7 64 Bit machine.
Restarted the spooler.
[/more]
