Consolidating print servers Chating with horny girl
If you don’t, then as of July 14th there will be no more updates, no savings, no compliance, and no safe haven.
If you’re like me, that doesn’t make you comfortable—so you have to review your options.
I know—just reading those words probably gives you a headache. As you likely know, Microsoft has announced that it will end its support of Windows Server 2003/R2 on July 14, 2015.
With that end-of-life (EOL) date upon us, it’s time to prepare and migrate to either Windows Server 2008/R2 or Windows Server 2012/R2.
There are a variety of applications and methods to assist with the transfer of many of these services, but printing remains a particular migration challenge for most organizations.
When it comes to migrating the print service to your new server, here are the steps you’ll need to go through: Currently, the most common method used when migrating print servers is to export then re-import the printers through the Print Management Console.
The first is the rip-and-replace, where you swap your old servers for the newer version. So let’s take a deeper look at your options and break down the steps involved in each, with specific emphasis on available print server migration paths.So you may be tempted to consolidate your print servers as well into a single, centralized print server.I could go on for paragraphs about options and issues that you’ll likely face (and, in fact, we have in this white paper), but I think you get the point. Data Center Consolidation Given the difficulties involved in replacing old hardware with new, now is a great time to consider a server consolidation initiative.With new technologies it is rather simple to move file services to the data center and allow users to access files over better WAN connections (which weren’t there back when the 2003 file server was put in place).Replacing Old Servers with New Hardware I’ve always found it funny that people refer to this option as the “rip-and-replace” option. Just rip out your old servers, plug in new ones, and you’re good to go—right? The problem with replacing your old Windows Server 2003 hardware with Windows Server 2012 is that you need to migrate everything from the 2003 hardware to the 2008/2012s.
Your 2003 servers potentially have file, print, DHCP, DNS or other services on them.