Make sure you have enabled the policy for Print Driver Isolation on all print drivers. I was reading this thread when I checked on my post and saw your link to a similar situation: Tuesday, March 29, 5: Once I enabled that service and started it, the printers from the source server that had both 32bit and 64bit drivers would import on the destination server, when the import was run again. Windows Server Network Infrastructure, Configuration. On the source server, before the export, correct?

Uploader: Mirn
Date Added: 28 September 2010
File Size: 54.92 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 2634
Price: Free* [*Free Regsitration Required]

I’m trying to come up with a start-to-finish plan on this.

46C IBM Lenovo ServRAID M Server mm Flash ZZ Power Module Cable | eBay

But, as I continue to test and troubleshoot this – for example after I’ve enabled a GPO for “override print driver execution I was reading this thread when I checked on my post and saw your link to a similar situation:. When installing cross platform drivers, the language monitor file for the non native chipset are not copied to system Out of printers, not one migrated.


Here is the list of drivers from one of the x32 servers.

Security Microsoft Certified Systems Engineer: Sign in to vote. I’ll have a read.

46C9793 IBM Lenovo ServRAID M5200 Server 925mm Flash ZZ Power Module Cable

Reading homework, tell your boss It’s required by me. Is that a trouble shooting step to get around the fact that existing x64 printers are not being installed on the R2 server?

Using the command line option will give more specific errors for most failures. For the HP Universal driver, you should install the 64bit driver on the destination server before the restore to get the package aware install of the driver.

When I ran the file it required that I install a printer – I chose a local printer, LPT1 even though there is no printer. Sunday, J5200 27, I’ll look up the code tomorrow at work and post it. Windows Server General Forum. When I do the import on the R2 machine, as I mentioned in another post, I do get ports, drivers and forms. By continuing to browse this site, you agree to this use.

And what is a “language monitor”? Office Office Exchange Server. The printer driver is unknown.


To continue using , please upgrade your browser.

There is not AMD64 directory on there. Windows Server Network Infrastructure, Configuration. I have event ID’s 31, 33 and Well, I have some printers on the source server that already have the x64 driver installed, and they match exactly the drivers on the destination server. I called Microsoft and opened a case.

I haven’t done a count to see if all came over. Marked as answer by JohnB Tuesday, March 29, Monday, March 28, Use print management to create the list from mmc. Friday, March 25, 2: As I see you have got driver problems. The restore process will continue, skipping this queue.

Tuesday, March 29, The source servers are x32 and the destination is x How did I end up with none?