2 PCs recognized by Mesh as same Device
-
2009年10月4日 17:24Hello folks,
I have two similar PCs (make, model, user account) and I am unable to get them both added to Live Mesh. I have tried every permutation of removing all devices, restarting, reinstalling that I can think of. After I remove the devices from the web interface, uninstall, reboot, reinstall, and reboot, I can log in on both systems (Win 7 Business RTM, different license numbers) and get them both to the screen where you choose their names (which are different on the system and that's recognized by Live Mesh) and all appears fine. But, whichever one I add first ends up begin recognized as both. The first one to log in is the one you can actually access, but both machines (plus another non-issue PC) show the single device. If I disconnect one, the referenced device seems to switch over to the other PC.
Basically, both PCs are being given the same device ID, I think, and that isn't cleared on uninstall (or the hash algorithm doesn't use enough unique features to separate these systems). Is there a way to test this hypothesis? Is there a registry key that isn't cleared or a config file hiding somewhere that I can delete (tried all the obvious ones in program files and appdata)?
I also have Live Sync installed, and it has no such issues.
Thanks much,
Brandon
すべての返信
-
2009年10月5日 0:33モデレータAre the two PCs cloned by any chance? Meaning that Windows was installed on the 1st PC and an image created and restored to the second PC?
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator -
2009年10月12日 6:17
Are the two PCs cloned by any chance? Meaning that Windows was installed on the 1st PC and an image created and restored to the second PC?
Yes, they are. I renamed them and didn't have Live Mesh or Live Sync on before cloning, and installed them afterward. Both also have different valid and activated Win7x64 Business serial numbers. Could this have caused the problem? I know there is some type of unique user ID that is set when an account is created, which can cause some wonkiness. (I had an issue a while ago in XP where accounts with the same name on two different PCs had permissions problems that prevented one from accessing an HDD that was used by the other.)
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator
-
2009年10月12日 11:27モデレータYes, cloning is the source of the problem. I don't know what Live Mesh uses to identify the PC, but suspect that it is created as part of the OS installation as a machine identifier. When you clone the PC, this identifier travels to the clone and renaming or activating with a serial doesn't change that.
There may be a solution, but I'm not aware of what that might be. I recommend submitting a bug report with logs from both machines and details of what was done to clone the PC.
How to Submit Bugs and Live Mesh Logs
Note that you probably won't get a response to the bug report, though. It will be transferred to the internal system to be assigned to the appropriate development group.
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator- 回答としてマーク Stephen BootsMVP, Moderator 2009年10月12日 11:28
- 回答としてマークされていない neuroking 2009年10月21日 19:06
-
2009年10月17日 4:49I went back and used the sysprep utility on the original PC, as instructed in the MS documentation, which means that now these should effectively be two different machines, with different SIDs. I uninstalled Live Mesh before the cloning (which may have not been a complete uninstall as my more recent thread points out), reinstalled Live Mesh, and still no go. After another quasi/broken uninstall I reinstalled, uninstalled, and then manually disabled the LM remote desktop service and deleted the program folder. Then reinstalled. On both machines. Restarted between each step. No problems with any other programs except LM.
And that'll do it for me. It was a nice service when it worked, but now it has become a nasty time drain. I probably wasted as much time troubleshooting this as I saved by cloning the damn system. Ah well. Back to Live Sync, Dropbox and VNC. -
2009年10月19日 21:11I am having the same issue. I cloned a Win7x64 machine, uninstalling LM first and then sysprep'ing the source. Once up on the new machine, using the same account that was present on the source machine, I installed LM. It asked for a device name and connected to my mesh, etc. Problem is I can't see that device on any other PC in my mesh, nor on the web site.
-
2009年10月22日 18:43所有者I haven't seen cloning issues occuring before. I'll see what we can do to track down what's going sideways with this here.
-
2009年11月26日 19:54Hi,
I have exactly the same issue:
sysprepped a PC
installed the image to two more computers
Live Mesh (and Home Server!) think it's the same machine
Would be nice to see a patch.
Andreas -
2009年11月26日 22:46Regarding cloning and SID duplication, it is worth reading Mark Russinovich's article on this.
http://blogs.technet.com/markrussinovich/archive/2009/11/03/3291024.aspx
It would be interesting to hear something from someone inside the Mesh team on where Mesh stands in this regard.
Trevor -
2009年11月27日 14:26
I would have suggested running new SID to see if it corrects the issue
-
2009年12月19日 4:29Hi,
apart from the fact that new sid fails effectively when used together with Win7 (NTFS file permissions get screwed up) it doesn't help with Mesh. I tried newsid w/o, w admin rights and within safe mode, as well as within normal mode. (4 times in total). Then I also tried to sysprep the devices. This resulted in new sids, however the Mesh error won't be solved solved either. I contacted Microsoft customer support, they told me this scenario is not supported, as WIM installations are for enterprise users, whereas Live Mesh is a consumer product. However I created a bug report at connect and hopefully will get an answer soon. -
2010年1月11日 2:36所有者 We're definitely aware of the issue. Mesh is indeed listed as a consumer product and not an enterprise solution based product so some enterprise solutions (cloning being one of them) aren't supported as well as they should be.
I know this is something that is trying to be fixed, but unfortunately I don't have any timeframe on when it will be.
-Ken- 回答としてマーク kensm [msft]Microsoft Contingent Staff, Owner 2010年1月11日 2:36
-
2010年1月11日 23:53Hi - Same problem here.
I don't want a fix - I just want to know from the Mesh team how Mesh identifies the machine - then I can make sure that "thing" is different on each of my cloned machines. If its not the SID, and its not the machine name, what is used? Where can we change it?
Surely someone on the Mesh team will be able to come up with a work around quickly... no need to release a patch...
Help please? -
2011年3月7日 6:14
Hello,
Well reading through this thread I see this issue I have has been around a long time. Several new versions of Mesh and I am wondering if the Mesh team is any further in resolving it????? Oh by the way, consumer pc cloners image as well. Now it affects them. Maybe a little more priority would be nice.
Again as a gentleman in this post requested just how do you uniquely identify the PC.
Vern
-
2011年3月7日 13:41モデレータ
Hello,
Well reading through this thread I see this issue I have has been around a long time. Several new versions of Mesh and I am wondering if the Mesh team is any further in resolving it????? Oh by the way, consumer pc cloners image as well. Now it affects them. Maybe a little more priority would be nice.
Again as a gentleman in this post requested just how do you uniquely identify the PC.
Vern
This thread is over a year old. Live Mesh Beta will cease functioning at the end of March, 2011.For discussion of the new Windows Live Mesh (formerly Sync), (as well as the released Live Sync version) go here:
http://windowslivehelp.com/forums.aspx?productid=24
-steve
~ Microsoft MVP Windows Live ~ Windows Live OneCare| Live Mesh|MS Security Essentials Forums Moderator ~
