HP 9500n HP Color LaserJet 9500n and 9500hdn - Software Technical Reference - Page 267

Point and Print in a mixed operating system environment, Mixed driver-version compatibility

Page 267 highlights

Point and Print in a mixed operating system environment When using Point and Print, the print queue configuration is stored on, and managed from, the print server. Client computers get the print queue configuration and the printer driver from the print server. Changes to the printer driver on the server, or its configuration, are automatically replicated to the client. In a homogenous operating system environment (all of the clients and servers are running the same operating system), the printer driver that is vended from the server to the clients in a Point and Print environment is the same printer driver that is running and controlling the print queue configuration on the server. In this case, there is no doubt that the client computer can correctly interpret the print queue configuration and printing behaves as expected. However, in a mixed operating system environment that typically occurs during an operating system migration, there are situations in which client computers could be running a different version of the printer driver than the one that is running on the print server. In order for this situation to work correctly, the printer driver that is running on the client must be capable of correctly interpreting the configuration that was created by the printer driver running on the print server. (Microsoft refers to the data structure in which this configuration is stored as the DEVMODE, but for the purposes of this section, we refer to this as the print queue configuration.) The following figure illustrates a situation involving a Windows NT 4.0 print server that is supporting a mixed client base of Windows NT 4.0 and Windows 2000, XP, or 2003 clients. Because the server is running Windows NT 4.0, it is running a version-2 driver and the print queue configuration is created by this driver. A version-3 driver has been added to this server for vending to Windows 2000, XP, or 2003 clients (Microsoft documents a special procedure to accomplish this which is discussed later). When Windows NT 4.0 clients make a connection to this shared printer on the Windows NT 4.0 print server, it is vended the same version-2 printer driver that is running on the print server. Because this is the same printer driver that created the print queue configuration, there is no problem reading this configuration and all of the print jobs functions as expected. However, when a Windows 2000, Windows XP, or Windows Server 2003 client makes a connection to this shared printer on the Windows NT 4.0 print server, it is vended the added version-3 printer driver. In this illustration, the version-3 printer driver is not written to be able to correctly interpret the data structure which stores the print queue configuration and this does have an impact on printing functionality because the version-3 printer driver on the Windows 2000, Windows XP, or Windows Server 2003 client does not "see" all of the installed options as they are configured in the version-2 printer driver on the print server. Figure 99: Mixed driver-version compatibility Software Technical Reference ENWW Print server operating system migration 265

  • 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
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286

Point and Print in a mixed operating system environment
When using Point and Print, the print queue configuration is stored on, and managed from, the print server. Client
computers get the print queue configuration and the printer driver from the print server. Changes to the printer driver
on the server, or its configuration, are automatically replicated to the client.
In a homogenous operating system environment (all of the clients and servers are running the same operating
system), the printer driver that is vended from the server to the clients in a Point and Print environment is the same
printer driver that is running and controlling the print queue configuration on the server. In this case, there is no doubt
that the client computer can correctly interpret the print queue configuration and printing behaves as expected.
However, in a mixed operating system environment that typically occurs during an operating system migration, there
are situations in which client computers could be running a different version of the printer driver than the one that is
running on the print server. In order for this situation to work correctly, the printer driver that is running on the client
must be capable of correctly interpreting the configuration that was created by the printer driver running on the print
server. (Microsoft refers to the data structure in which this configuration is stored as the DEVMODE, but for the
purposes of this section, we refer to this as the print queue configuration.)
The following figure illustrates a situation involving a Windows NT 4.0 print server that is supporting a mixed client
base of Windows NT 4.0 and Windows 2000, XP, or 2003 clients. Because the server is running Windows NT 4.0, it is
running a version-2 driver and the print queue configuration is created by this driver. A version-3 driver has been
added to this server for vending to Windows 2000, XP, or 2003 clients (Microsoft documents a special procedure to
accomplish this which is discussed later).
When Windows NT 4.0 clients make a connection to this shared printer on the Windows NT 4.0 print server, it is
vended the same version-2 printer driver that is running on the print server. Because this is the same printer driver that
created the print queue configuration, there is no problem reading this configuration and all of the print jobs functions
as expected. However, when a Windows 2000, Windows XP, or Windows Server 2003 client makes a connection to
this shared printer on the Windows NT 4.0 print server, it is vended the added version-3 printer driver. In this
illustration, the version-3 printer driver is not written to be able to correctly interpret the data structure which stores the
print queue configuration and this does have an impact on printing functionality because the version-3 printer driver on
the Windows 2000, Windows XP, or Windows Server 2003 client does not “see” all of the installed options as they are
configured in the version-2 printer driver on the print server.
Figure 99: Mixed driver-version compatibility
Software Technical Reference ENWW
Print server operating system migration
265