<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Windows Server 2003 | TekCookie</title>
	<atom:link href="https://tekcookie.com/category/windows-server-2003/feed/" rel="self" type="application/rss+xml" />
	<link>https://tekcookie.com</link>
	<description>Everything about IT</description>
	<lastBuildDate>Sun, 13 Jun 2021 13:38:38 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://i0.wp.com/tekcookie.com/wp-content/uploads/2021/06/cropped-TekCookie-211.png?fit=32%2C17&#038;ssl=1</url>
	<title>Windows Server 2003 | TekCookie</title>
	<link>https://tekcookie.com</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">174510684</site>	<item>
		<title>Printer Server migration &#8211; 2003 to 2016</title>
		<link>https://tekcookie.com/printer-server-migration-2003-to-2016/</link>
					<comments>https://tekcookie.com/printer-server-migration-2003-to-2016/#comments</comments>
		
		<dc:creator><![CDATA[jeffythampi]]></dc:creator>
		<pubDate>Thu, 21 Nov 2019 13:19:59 +0000</pubDate>
				<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[Print Server Migration]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Windows Server 2003]]></category>
		<category><![CDATA[Windows Server 2016]]></category>
		<category><![CDATA[Printer Server migration]]></category>
		<category><![CDATA[Printer Server migration from Windows 2003 to Windows 2016]]></category>
		<guid isPermaLink="false">https://adminscripter.wordpress.com/?p=213</guid>

					<description><![CDATA[Printer Server migration from Windows 2003 to Windows 2016 Recently, I was assigned with a printer server migration project from Windows Server 2003 to Windows Server 2016. The difficult thing was that, I couldn&#8217;t find any article which explains about the migration from 32-bit architecture to 64-bit architecture. May be I am not that good [&#8230;]]]></description>
										<content:encoded><![CDATA[
<h1 class="has-text-align-left wp-block-heading">Printer Server migration from Windows 2003 to Windows 2016</h1>



<p>Recently, I was assigned with a printer server migration project from Windows Server 2003 to Windows Server 2016.</p>



<p>The difficult thing was that, I couldn&#8217;t find any article which explains about the migration from 32-bit architecture to 64-bit architecture. May be I am not that good in googling.</p>



<p>My task was to migrate 100+ printers from windows server 2003 to windows server 2016 with all configurations.</p>



<p>First thought which came to my mind was to export all printers settings (Printer name, driver name, model, printer port name, printer port IP, printer share name etc.) to a text file using the inbuilt vb scripts in windows and then format it to a CSV file.<br>With the CSV file as source, PowerShell can be used to add printers to the new server using <em><strong>Add-PrinterPort</strong></em> and <strong><em>Add-Printer</em></strong> command-lets. I was able to migrate the printers to new server with the Name, share name, port, comments, location etc. But I was stuck at paper size. I was not able to set custom size(Height and Width) for the label printers.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p>Here the only change was &#8211; the driver name was different for existing printers in windows server 2003 and the new package for windows server 2016. So I had to change the printer driver name in PowerShell accordingly</p></blockquote>



<p>After some thought process, I thought of printer migration tools. But there was some difficulty, it was for backup and restore of printers within windows server 2003.<br>Then I tried with Print Management tool in windows 2016, connected the print management mmc to windows  server 2003, exported the printer&#8217;s and &#8230; import failed.</p>



<p>Then I used PrintBrm.exe to export the printer&#8217;s and import failed again. 🙁</p>



<p>The issue was with the driver &#8220;<em>name</em>&#8221; as mentioned above.</p>



<ul class="wp-block-list"><li>Windows 2003 : Driver name &#8211; <strong>Zebra GK420t</strong></li><li>Windows 2016 : Driver name &#8211; <strong>ZDesigner GK420t </strong></li></ul>



<hr class="wp-block-separator"/>



<h3 class="wp-block-heading">Below are the steps which I followed to migrate the printers from Windows Server 2003 to Windows Server 2016</h3>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p><strong>Step-1</strong></p><cite>Add new driver to windows server 2003</cite></blockquote>



<p>Added the latest driver to windows 2003 to match the driver name. In the list of printer drivers, the new name was available.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p><strong>Step-2</strong></p><cite>Change existing printer driver to newly installed driver</cite></blockquote>



<p>For ease of login, both old and new servers local administrator id and password is set to same.<br>From windows server 2016, Following PowerShell script was run to change the drivers in Windows 2003.</p>



<pre class="wp-block-code"><code lang="powershell" class="language-powershell line-numbers">$Windows2003Name = "PRNSVR2003"
#Fetch all printers having driver name starting with Z, i.e. Zebra
$printers = Get-printer -ComputerName $Windows2003Name | where {$_.DriverName -like "Z*"} 
foreach($prns in $printers) 
{	#iterating through each printer and changing the driver name to new drivers
   if($prns.DriverName -like "Zebra  GK420t*")
   {
        #$prns.Name
        Set-Printer -ComputerName $Windows2003Name -Name $prns.Name -DriverName "ZDesigner GK420t"
   }
   elseif($prns.DriverName -like "Zebra  TLP2844-Z*")
   {
        #$prns.Name
        Set-Printer -ComputerName $Windows2003Name -Name $prns.Name -DriverName "ZDesigner TLP 2844-Z"
   }
}</code></pre>



<p>While the script is running, we can see the driver getting changed in the windows 2003 server printer console</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p><strong>Step-3</strong></p><cite>Backup printers from old server</cite></blockquote>



<p>From Windows 2016, run printer migration tool &#8211; PrintBrm.exe<br>Open command prompt and run the following </p>



<pre class="wp-block-code"><code lang="bash" class="language-bash line-numbers">cd %WinDir%\System32\Spool\Tools
printbrm.exe -s \\PRNSVR2003 -b -f Win2003Printer.printerExport</code></pre>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p><strong>Step-4</strong></p><cite>Restore printers to new server</cite></blockquote>



<p>Double click the above created file to import the printers with all settings.</p>



<p>That&#8217;s it! All your printers are in the new server.</p>



<div style="height:70px" aria-hidden="true" class="wp-block-spacer"></div>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p>Thank you for reading my post. Hope it is helpful to you.</p></blockquote>



<p></p>
]]></content:encoded>
					
					<wfw:commentRss>https://tekcookie.com/printer-server-migration-2003-to-2016/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">213</post-id>	</item>
	</channel>
</rss>
