Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Device ID duplicated on two machines RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote
    I have a Windows Vista machine which I imaged and duplicated on a different piece of hardware using Acronis True Image Workstation.  When I install Live Mesh on each (machine) device, Mesh appears to think it is the same device even though they each have a unique name on the domain and each was activated with unique product keys.  I see that mesh, at the time of install, creates a device authentication key which is stored in the registry [HKEY_CURRENT_USER\Software\Microsoft\Live Mesh\CurrentDeviceIDs] which is showing up identical on each machine.  I have uninstalled reinstalled etc, but they keep getting the same device ID.  How do I fix this?  Where is this ID derived from?

    Brad Sando
    • Edited by TriadX1 Saturday, September 27, 2008 3:30 PM
    Friday, September 26, 2008 2:59 AM

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote
    Disclaimer here ... if you're imaging machines without sysprep and moving the image across hardware ... you are in unsupported territory.

    That said ... the device ID is typically written to \appdata\roaming\Microsoft\IdentityCRL ... what you do with this information is up to you :)

    • Marked as answer by TriadX1 Wednesday, October 1, 2008 6:59 AM
    Wednesday, October 1, 2008 1:42 AM
    Answerer
  • Question
    Sign in to vote
    1
    Sign in to vote
    Hi Brad - the device ID that Live Mesh uses is actually for a logical device which means each NT user account gets its own ID.  This ID (certificate) is stored in the user profile.  So to ensure that the device ID is unique on a given physical machine and user account ... please verify that:

    1) The imaging solution you use does in fact sysprep the machine before imaging and wipe all user accounts from the system.
    2) You are not using roaming profiles for your domain users.  We have a known issue with roaming profiles where the device IDs actually roam with the profile.  We're working on a fix for this.

    Thanks,
    John
    Monday, September 29, 2008 5:04 PM
    Answerer

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    same issue here. please help.
    Monday, September 29, 2008 9:34 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Hi Brad - the device ID that Live Mesh uses is actually for a logical device which means each NT user account gets its own ID.  This ID (certificate) is stored in the user profile.  So to ensure that the device ID is unique on a given physical machine and user account ... please verify that:

    1) The imaging solution you use does in fact sysprep the machine before imaging and wipe all user accounts from the system.
    2) You are not using roaming profiles for your domain users.  We have a known issue with roaming profiles where the device IDs actually roam with the profile.  We're working on a fix for this.

    Thanks,
    John
    Monday, September 29, 2008 5:04 PM
    Answerer
  • Question
    Sign in to vote
    1
    Sign in to vote
    JohnMac_MSFT said:

    Hi Brad - the device ID that Live Mesh uses is actually for a logical device which means each NT user account gets its own ID.  This ID (certificate) is stored in the user profile.  So to ensure that the device ID is unique on a given physical machine and user account ... please verify that:

    1) The imaging solution you use does in fact sysprep the machine before imaging and wipe all user accounts from the system.
    2) You are not using roaming profiles for your domain users.  We have a known issue with roaming profiles where the device IDs actually roam with the profile.  We're working on a fix for this.

    Thanks,
    John

    The main reason I use imaging technology to duplicate to a second machine it so that I don't have to re-do all my personalization and configuration, which is stored in my user profile.  Sysprep wipes all this out. 

    Can you just be more specific as to what area of the user profile I need to wipe so that it is recreated when I load Live Mesh?

    Thanks for your help!

    Brad
    Brad Sando
    Tuesday, September 30, 2008 5:34 PM
  • Question
    Sign in to vote
    2
    Sign in to vote
    Disclaimer here ... if you're imaging machines without sysprep and moving the image across hardware ... you are in unsupported territory.

    That said ... the device ID is typically written to \appdata\roaming\Microsoft\IdentityCRL ... what you do with this information is up to you :)

    • Marked as answer by TriadX1 Wednesday, October 1, 2008 6:59 AM
    Wednesday, October 1, 2008 1:42 AM
    Answerer