HP Color LaserJet 9500 HP Color LaserJet 9500n and 9500hdn - Software Technica - Page 270

Migration strategies, Strategy 1: Use Windows NT 4.0 drivers to support all clients

Page 270 highlights

Migration strategies What follows is the exploration of three different strategies for being able to support Point and Print in a mixed operating-system environment. The three strategies are not necessarily mutually exclusive but can in some cases be combined or partially used concurrently to ensure that all of the client computers are served with a supportable printer driver configuration. Formulating a solution based on these strategies involves examining the list of printers to be supported and the list of page description languages required for use on these printers along with other site-specific migration requirements, and drafting a plan by which all of the client computers can be served with a supported driver configuration. Strategy 1: Use Windows NT 4.0 drivers to support all clients In this approach we seek to avoid printer driver compatibility issues altogether by isolating the Windows NT 4.0, clients and servers, from newer operating systems, thus running a dual printing environment temporarily. This is accomplished by leaving existing Windows NT 4.0-based print servers in place to serve the existing legacy Windows NT 4.0 client base and deploying new Windows 2000 or .NET print servers to support the migrated client base running Windows 2000, Windows XP, or Windows Server 2003. As clients are migrated, they are reconnected to the new print queues hosted on the new Windows 2000 or Windows 2003 Server print servers. At the end of the migration when there are no more Windows NT 4.0 clients, the Windows NT 4.0 print servers can be retired. This approach ensures that the print servers and clients are always running the same correct printer drivers, thus avoiding any incompatibilities that may otherwise exist. Advantages of this approach include not having to do any additional work to the legacy NT 4.0 clients and servers and ending up with the proper version-3 drivers for all of the products at the end of the migration, and most importantly, all printer models and drivers can be supported using this approach. Strategy 2: Use Windows NT 4.0 drivers to support all clients Because Windows 2000, Windows XP, and Windows Server 2003 are capable of running Version-2 printer drivers, a simple approach might be to use Version-2 printer drivers to support all of the servers and clients. In this way version-2 and version-3 printer driver compatibility issues are avoided because only version-2 printer drivers are deployed in the solution. In fact, this is the recommendation Microsoft makes if driver incompatibility issues arise. In general, this is a safe recommendation to make for version-2 PS printer drivers which are based on Microsoft's PS driver core. However, caution is advised because, while HP's version-2 PCL drivers are compatible with Windows 2000, they are not all compatible with Windows XP or Windows 2003 Server. The HP version-2 PCL printer drivers should not be installed on Windows Server 2003 servers, nor should Windows XP clients connect to print queues hosted from Windows NT 4.0 print servers that have only version-2 PCL printer drivers installed. "Installed" means that the printer driver running the queue on .NET server should not be a version-2 PCL driver. It is acceptable to create a printer on .NET using a version-3 driver, and then add the compatible version-2 driver for NT clients, however, as described in Strategy 3. While this strategy has the advantage of simplicity, there are several disadvantages. Because of the restriction for version-2 PCL printer drivers described previously, not all printer products and page description languages can be supported. Another disadvantage of this strategy is the inherent risk associated with running version-2 printer drivers. Finally, at the end of the migration period when all of the clients and servers have been migrated to newer operating systems, the printer drivers being used are all version-2 Windows NT printer drivers; this would definitely lead to further work to upgrade all of the version-2 printer drivers to their version-3 counterparts. Also note that many older version-2 printer drivers cannot be used with this strategy because they are incompatible with Windows 2000, XP, and 2003, and are blocked from installation by those operating systems. Therefore, it is necessary to update existing version-2 printer drivers prior to deploying to migrated servers or clients. Strategy 3: Use a mix of version-2 and version-3 drivers to support all clients In this approach, all of the version-2 and version-3 printer drivers are installed on the print server that are necessary to support a mixed client base during the migration as is illustrated graphically in the following figure. As mentioned previously, these printer drivers must be compatible with one another in such a way that they store the driver configuration in a format that is common to both drivers. HP has compatible printer driver pairs available for most printers and page description languages, as described in the following tables. The information in the tables describes the printers and specific printer driver versions that can be installed together on a server in this manner. 268 Print server operating system migration Software Technical Reference ENWW

  • 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

Migration strategies
What follows is the exploration of three different strategies for being able to support Point and Print in a mixed
operating-system environment. The three strategies are not necessarily mutually exclusive but can in some cases be
combined or partially used concurrently to ensure that all of the client computers are served with a supportable printer
driver configuration. Formulating a solution based on these strategies involves examining the list of printers to be
supported and the list of page description languages required for use on these printers along with other site-specific
migration requirements, and drafting a plan by which all of the client computers can be served with a supported driver
configuration.
Strategy 1: Use Windows NT 4.0 drivers to support all clients
In this approach we seek to avoid printer driver compatibility issues altogether by isolating the Windows NT 4.0, clients
and servers, from newer operating systems, thus running a dual printing environment temporarily. This is
accomplished by leaving existing Windows NT 4.0-based print servers in place to serve the existing legacy Windows
NT 4.0 client base and deploying new Windows 2000 or .NET print servers to support the migrated client base running
Windows 2000, Windows XP, or Windows Server 2003. As clients are migrated, they are reconnected to the new print
queues hosted on the new Windows 2000 or Windows 2003 Server print servers. At the end of the migration when
there are no more Windows NT 4.0 clients, the Windows NT 4.0 print servers can be retired.
This approach ensures that the print servers and clients are always running the same correct printer drivers, thus
avoiding any incompatibilities that may otherwise exist.
Advantages of this approach include not having to do any additional work to the legacy NT 4.0 clients and servers and
ending up with the proper version-3 drivers for all of the products at the end of the migration, and most importantly, all
printer models and drivers can be supported using this approach.
Strategy 2: Use Windows NT 4.0 drivers to support all clients
Because Windows 2000, Windows XP, and Windows Server 2003 are capable of running Version-2 printer drivers, a
simple approach might be to use Version-2 printer drivers to support all of the servers and clients. In this way version-2
and version-3 printer driver compatibility issues are avoided because only version-2 printer drivers are deployed in the
solution. In fact, this is the recommendation Microsoft makes if driver incompatibility issues arise.
In general, this is a safe recommendation to make for version-2 PS printer drivers which are based on Microsoft’s PS
driver core. However, caution is advised because, while HP’s version-2 PCL drivers are compatible with Windows
2000, they are not all compatible with Windows XP or Windows 2003 Server. The HP version-2 PCL printer drivers
should not be installed on Windows Server 2003 servers, nor should Windows XP clients connect to print queues
hosted from Windows NT 4.0 print servers that have only version-2 PCL printer drivers installed. “Installed” means that
the printer driver running the queue on .NET server should not be a version-2 PCL driver. It is acceptable to create a
printer on .NET using a version-3 driver, and then add the compatible version-2 driver for NT clients, however, as
described in Strategy 3.
While this strategy has the advantage of simplicity, there are several disadvantages. Because of the restriction for
version-2 PCL printer drivers described previously, not all printer products and page description languages can be
supported. Another disadvantage of this strategy is the inherent risk associated with running version-2 printer drivers.
Finally, at the end of the migration period when all of the clients and servers have been migrated to newer operating
systems, the printer drivers being used are all version-2 Windows NT printer drivers; this would definitely lead to
further work to upgrade all of the version-2 printer drivers to their version-3 counterparts.
Also note that many older version-2 printer drivers cannot be used with this strategy because they are incompatible
with Windows 2000, XP, and 2003, and are blocked from installation by those operating systems. Therefore, it is
necessary to update existing version-2 printer drivers prior to deploying to migrated servers or clients.
Strategy 3: Use a mix of version-2 and version-3 drivers to support all clients
In this approach, all of the version-2 and version-3 printer drivers are installed on the print server that are necessary to
support a mixed client base during the migration as is illustrated graphically in the following figure. As mentioned
previously, these printer drivers must be compatible with one another in such a way that they store the driver
configuration in a format that is common to both drivers. HP has compatible printer driver pairs available for most
printers and page description languages, as described in the following tables. The information in the tables describes
the printers and specific printer driver versions that can be installed together on a server in this manner.
268
Print server operating system migration
Software Technical Reference ENWW