It's a bad idea, but..if the policy got corresponding registry value, then...
Take the two Registry.pol file under :\Windows\System32\GroupPolicy\ ref
The Group Policy Object Editor stores registry-based configuration settings in two Registry.pol files, stored in folders under the :\Windows\System32\GroupPolicy\ folder. One file contains computer settings and the other file contains user settings. The Group Policy Object Editor saves the settings to these files on exit, and imports the settings on startup.
Better idea to manage your computer;
Create a GPO that target that computer and make it apply to other computers you want.
By copying the .pol file you fall like it was on older system like NT4 with poledit to make policies.. It's a way back to a nightmare for many tech that lived that period IMO, but welcome to the boat if you use that method I guess.
error saying that there was no mapping between the account names and security id.Correct. Windows 101: user accounts on different computers are not the same, even if the username is the same. That is why Active Directory was created, to have a central store of user accounts that would be recognized on all computers. Active Directory also has Group Policy, which is convenient for transparently replicating Group Policy to computers.