Is it a confirmed bug? If not, it needs to be on Uservoice, not Connect. Daniel Ratliff
From: [email protected] [mailto:[email protected]] On Behalf Of Mote, Todd Sent: Wednesday, June 7, 2017 2:34 PM To: [email protected]; [email protected] Subject: [mssms] Anybody have a workaround for this? How to create a Computer record in AD and SCCM that will merge into ONE record in a supported way in Current Branch https://social.technet.microsoft.com/Forums/en-US/a9832bf4-d3aa-4272-a1a4-5978093c94a8/how-to-create-a-computer-record-in-ad-and-sccm-that-will-merge-into-one-record-in-a-supported-way-in?forum=ConfigMgrPowerShell I know there is a Connect item open for this, and it's "Active", but does anybody have any clever workarounds? I create an object with the powershell cmdlet, Import-CMComputerInformation, then place that into a maintenance window collection all at provision time and I'm finding that the Manual Machine Entry is where I put it post deployment, but the client registers and then that merges with the AD sys discovery object, and the manual machine entry never merges. I'm left with two objects with the same name, same MAC and same netbios name and they won't merge. Any ideas? Todd The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
