Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 3752 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Active Directory Sync pulling old computer names?

wjohnson2k1

Hey guys, we currently are running Sophos Endpoint 9.7 Sync'ed up with Active directory. Right before we did the upgrade from 9.5 this issue started popping up.  We are currently in the midst of replacing older computers, during the replacement old computers are renamed to (computername_temp) while we process and finish setting up a replacement, we then name the replacement (computername) and put the temp in the outgoing pile. Well about 1/5 times Sophos will not delete the (computername_temp) and no matter what we do it continues to show up in the enterprise console and the new computer (computername) will not show up or install. 

Does that make sense? Any ideas what could be causing this? 

Things I've tried-

Deleting Sync with AD and recreating

Checked AD to ensure computername_temp no longer exists

Manually insall on new (computername) works fine.

Thanks!

-Wayne  

:14943


This thread was automatically locked due to age.
Parents
  • 0

    Thanks for the reply! It sounds like you reproduced our exact problem. Althought sometimes it seems that even after waiting a day or two the "stub" entry will still stick, and not allow for deployment of the new computer. I think that deleting this entry from the database would solve that, but do I manually need to log into the database to accomplish this task? Deleting from the enterprise console simply doesn't work, once it does and AD scan its added right back in even though the "stub" compy doesn't exist in AD. 

    :14991
Reply
  • 0

    Thanks for the reply! It sounds like you reproduced our exact problem. Althought sometimes it seems that even after waiting a day or two the "stub" entry will still stick, and not allow for deployment of the new computer. I think that deleting this entry from the database would solve that, but do I manually need to log into the database to accomplish this task? Deleting from the enterprise console simply doesn't work, once it does and AD scan its added right back in even though the "stub" compy doesn't exist in AD. 

    :14991
Children
No Data