Compute A has 4 duplicate entries in console and in each entry IP address is different.
And all are responding to custom action and reporting with latest date. How to identify the right one and Which single entry to keep and other to remove, how to identify.
If you have multiple computers with the same name, and both are responding to actions, those aren’t duplicates; those are multiple computers with the same name.
You might try displaying the “ID” column so you can tell them apart.
If those are responding to actions separate and each have different IPs, IDs, ect then you may wanna rename them. If they end up having the same ID, serial, ect then you can clean those up with the besadmin tool.
You can use this to rename domain joined windows 10 PCs. Just make sure that ps1 file gets deleted at the end. Use at your own risk
<?xml version="1.0" encoding="UTF-8"?>
<BES xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="BES.xsd">
<Task>
<Title>Rename PC (Win10)</Title>
<Description><![CDATA[<P><B>Please Enter your Domain Username and Password. This will be used for changing the name and re-adding it back to the Domain </P></B>
<P>Username: <INPUT id=username name=username> </P>
<P>Password: <INPUT id=pw type=password name=pw> </P><script>
document.body.ontakeaction = function() {
var User = document.getElementById( "username" ).value;
var Pass = document.getElementById( "pw" ).value;
TakeSecureFixletAction( Relevance('id of current fixlet'), Relevance('id of current bes site'), "Action1", {}, { username: User, pw: Pass } );
return false;
}
</script> ]]></Description>
<Relevance>true</Relevance>
<Category></Category>
<Source>Internal</Source>
<SourceID></SourceID>
<SourceReleaseDate>2020-04-24</SourceReleaseDate>
<SourceSeverity></SourceSeverity>
<CVENames></CVENames>
<SANSID></SANSID>
<MIMEField>
<Name>x-fixlet-modification-time</Name>
<Value>Mon, 04 May 2020 20:05:42 +0000</Value>
</MIMEField>
<Domain>BESC</Domain>
<DefaultAction ID="Action1">
<Description>
<PreLink>Click </PreLink>
<Link>here</Link>
<PostLink> to deploy this action.</PostLink>
</Description>
<ActionScript MIMEType="application/x-Fixlet-Windows-Shell">action uses wow64 redirection {not x64 of operating system}
action parameter query "PCName" with description "Please enter the New PC Name" with default value "New PC Name"
delete __createfile
createfile until END_OF_FILE
$bfuser = '{parameter "username" of action}'
$bfpass = '{parameter "pw" of action}'
$password = $bfpass | ConvertTo-SecureString -AsPlainText -Force
$Credential = New-Object System.Management.Automation.PsCredential -ArgumentList $bfuser, $Password
Rename-Computer -NewName "{parameter "PCName"}" -DomainCredential $Credential -Force
END_OF_FILE
delete powershell.ps1
move __createfile powershell.ps1
waithidden { pathname of file ((it as string) of value "Path" of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell" of native registry) } -ExecutionPolicy Bypass -File powershell.ps1
delete powershell.ps1</ActionScript>
</DefaultAction>
</Task>
</BES>