Your bar is two lines on this screen now. Tap the pin again to undo, or choose in Settings.
Your products All productsPCS Remote help
Usually because a computer was cloned: a disk or virtual
machine was copied, or sysprep wasn't run (or wasn't
run properly) before the image was made. The copies share one
Windows identity, so PCS Remote gives them all the same number.
It's a Windows imaging issue, not a fault in PCS Remote. In our own test, another popular remote tool showed the same address on both copies.
Please read this whole page, including the box at the bottom, before running any of these.
The quick option, for a lab or virtual machine. On that copy, open PowerShell as administrator, run this, then restart the computer:
Set-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Cryptography' MachineGuid ([guid]::NewGuid().ToString())
It comes back as a new machine with a new PCS Remote number. In PCS Remote IT, add it again as a new tile.
After the restart it may fail to connect. If it does, delete the old key file in an administrator PowerShell, then restart again:
Get-ChildItem 'C:\ProgramData\Microsoft\Crypto\Keys' -Force | Where-Object { $_.Name -like '8f9d3fae6be3d585d06231d46d4dfa5e_*' -and $_.Name -notlike "*$((Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Cryptography').MachineGuid)" } | Remove-Item -Force
The best way to avoid this. Run sysprep /generalize
before you capture or clone the image, and every PC made from it
gets an identity of its own, including its own Windows SID, which
matters on a domain.
Please don't press “Generate new ID” in PCS Remote. It moves every copy that shares the identity to the new number, so the copies still collide.
And please don't press “Reset security pin” to get past the warning. That tells PCS Remote IT to accept whichever machine holds the number right now, including the wrong one. Fix the copy's identity instead.