Share via

Does printbrm.exe exist on Windows Server Core 2022?

Anonymous
2023-10-09T16:08:01+00:00

I’m trying to migrate a print server from Server 2012r2 to Server 2022 Core. I’ve installed the Print Server and Migration features but the printbrm tool doesn’t seem to exist in C:\Windows\System32\Spool\Tools.

Am I missing something? Has it moved to a different folder?

Windows Server Print, fax, and scan

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-10-09T20:53:47+00:00

    Isn't it "printbrmUi.exe" in system 32?

    0 comments
  2. Anonymous
    2023-10-09T20:58:16+00:00

    Printbrmui.exe is also not there… this is why I’m wondering if it has been moved to a different location or am I missing something…

    0 comments
  3. Anonymous
    2023-10-09T21:15:29+00:00

    I did not use it personally, no 2022.

    But it should be there. It will need admin rights though.

    And I don't see any documentation stating otherwise.

    There is an article about using it, not sure if any in there helps.

    Migrate print servers to Windows Server 2019 / 2022 – 4sysops

    0 comments
  4. Anonymous
    2023-10-09T21:18:57+00:00

    Your location is right so where is it?

    Printbrm | LOLBAS (lolbas-project.github.io)

    0 comments
  5. Anonymous
    2023-10-09T23:04:16+00:00

    Just to add that I’ve just installed Server 2022 with the Desktop Experience and it’s there so why is it not there on Core… Microsoft advocate using the Core variant as a print server but it would appear you can only create a new print server and not migrate an existing one into or away from it…

    I must be missing something… a feature other than the Print Server or Migration ones… or maybe it’s a Capability that needs adding? Or a FoD?

    0 comments