HP Indigo 3500 HP Color LaserJet 3500 Series Printer - Software Technical Refe - Page 211

Introduction of incompatible printer drivers through a silent driver upgrade

Page 211 highlights

PCL 6", but it is a version-2 driver and Windows 2000 prefers to use a version-3 printer driver when it is available. So in this case, because the print server at the remote site has a matching driver, which is version-3, the Windows 2000 client downloads this version-3 driver and now runs this printer driver. The connection to the remote print server silently upgraded the client computers printer driver to a version-3 driver. While still at the remote site, the client and server are both running the same printer driver and printing works as expected. However at Event #3, when the client returns to the home office and tries to print, problems occur because the printer driver being used on the client is not the same as that being used on the server and these two printer drivers are incompatible with each other. Figure 81: Introduction of incompatible printer drivers through a silent driver upgrade The example illustrated in the following figure is similar, except in this scenario the client first makes a connection to a Windows 2000 server with the version-3 "HP LaserJet 4000 Series PCL 6" printer driver. Initially, because client and server are both running the same printer driver, printing works as expected. However, in Event #2, the client makes a connection to a printer that also uses a "HP LaserJet 4000 Series PCL 6" printer driver. But the printer driver on this NT 4.0 server is a version-2 printer driver. Because the client already has a matching printer driver that is version-3, it just continues to use this printer driver. If these version-2 and -3 printer drivers are not compatible, then printing problems occur when trying to print to this second printer. Software Technical Reference ENWW Print server operating system migration 209

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226

PCL 6”, but it is a version-2 driver and Windows 2000 prefers to use a version-3 printer driver when it is available. So
in this case, because the print server at the remote site has a matching driver, which is version-3, the Windows 2000
client downloads this version-3 driver and now runs this printer driver.
The connection to the remote print server silently upgraded the client computers printer driver to a version-3 driver.
While still at the remote site, the client and server are both running the same printer driver and printing works as
expected. However at Event #3, when the client returns to the home office and tries to print, problems occur because
the printer driver being used on the client is not the same as that being used on the server and these two printer
drivers are incompatible with each other.
Figure 81: Introduction of incompatible printer drivers through a silent driver upgrade
The example illustrated in the following figure is similar, except in this scenario the client first makes a connection to a
Windows 2000 server with the version-3 “HP LaserJet 4000 Series PCL 6” printer driver. Initially, because client and
server are both running the same printer driver, printing works as expected. However, in Event #2, the client makes a
connection to a printer that also uses a “HP LaserJet 4000 Series PCL 6” printer driver. But the printer driver on this
NT 4.0 server is a version-2 printer driver. Because the client already has a matching printer driver that is version-3, it
just continues to use this printer driver. If these version-2 and -3 printer drivers are not compatible, then printing
problems occur when trying to print to this second printer.
Software Technical Reference ENWW
Print server operating system migration
209