Skip to main content
Question

Network Account and local Account Name Not Synced After Account Merge

  • March 21, 2025
  • 4 replies
  • 30 views

Forum|alt.badge.img+5

We enrolled a device and, during the assistance migration, used a Time Machine backup from a non-enrolled machine. Using the Jamf login configuration profile, we allowed the merge of the network account with the local account. After merging, the local account name appears in the "Users and Groups" section and in the terminal, but the password of the network account is required.

What steps can we take to ensure that after the merge, the local account adopts the network account name? In our standard routine, we use a synced network account and local account.

4 replies

Valcovish
Forum|alt.badge.img+6
  • Contributor
  • March 21, 2025

Hey @tahir,

It sounds like the local account isn’t fully syncing with the network account after the merge. A few things to check:

1. Confirm Account Linking

Run this in Terminal:

dscl . -read /Users/<local_account>

If the GeneratedUID doesn’t match the network account, they aren’t properly linked.

2. Force an Update

Try running:

sudo jamf policy -event updateAccount

This may push the sync.

3. Manually Rename the Local Account

If the local name isn’t updating, rename it:

sudo mv /Users/<old_local_name> /Users/<network_name>
sudo dscl . -change /Users/<old_local_name> RecordName <old_local_name> <network_name>

4. Fix Login Issues

If you’re getting password prompts, resetting the Keychain might help:

rm -rf ~/Library/Keychains/*

Hope this helps! Let me know if you need more details.


Forum|alt.badge.img+5
  • Author
  • Contributor
  • March 21, 2025

Hey @tahir,

It sounds like the local account isn’t fully syncing with the network account after the merge. A few things to check:

1. Confirm Account Linking

Run this in Terminal:

dscl . -read /Users/<local_account>

If the GeneratedUID doesn’t match the network account, they aren’t properly linked.

2. Force an Update

Try running:

sudo jamf policy -event updateAccount

This may push the sync.

3. Manually Rename the Local Account

If the local name isn’t updating, rename it:

sudo mv /Users/<old_local_name> /Users/<network_name>
sudo dscl . -change /Users/<old_local_name> RecordName <old_local_name> <network_name>

4. Fix Login Issues

If you’re getting password prompts, resetting the Keychain might help:

rm -rf ~/Library/Keychains/*

Hope this helps! Let me know if you need more details.


Actually its added network account as an Alias to local account 

Realname : Test

Recordname : test jamf.test


Forum|alt.badge.img+5
  • Author
  • Contributor
  • March 21, 2025

Hey @tahir,

It sounds like the local account isn’t fully syncing with the network account after the merge. A few things to check:

1. Confirm Account Linking

Run this in Terminal:

dscl . -read /Users/<local_account>

If the GeneratedUID doesn’t match the network account, they aren’t properly linked.

2. Force an Update

Try running:

sudo jamf policy -event updateAccount

This may push the sync.

3. Manually Rename the Local Account

If the local name isn’t updating, rename it:

sudo mv /Users/<old_local_name> /Users/<network_name>
sudo dscl . -change /Users/<old_local_name> RecordName <old_local_name> <network_name>

4. Fix Login Issues

If you’re getting password prompts, resetting the Keychain might help:

rm -rf ~/Library/Keychains/*

Hope this helps! Let me know if you need more details.


Upon Running this command with admin account "operation not permitted"

sudo mv /Users/<old_local_name> /Users/<network_name>

 


BGhilardi
Forum|alt.badge.img+7
  • Jamf Heroes
  • March 24, 2025

In our environment, we had to catch up on computers that were using unsynchronized local accounts and that were adhering to naming rules.
So, we first renamed the account names and home folders using the following procedure: https://support.apple.com/en-us/102547