2008년 5월 10일 토요일 오후 11:16I'm having a great time with Live Mesh; the MOE may solve several problems for the deployment of a new application we're developing.
One issue to date is that I'm having trouble adding my computer to the mesh; although the enable remote access box is ticked during the install process, there is subsequently an error message stating that not all updates could be installed. I think it is some kind of Vista security setting problem (running SP1) and I have been having problems with remote access.
Got any ideas?
2008년 5월 11일 일요일 오전 6:10I am having the same type of problem. No error code but just an inability to access my Vista Premium machine remotely however, it is syncing my folders.
In my Mesh circle there is a exclamation point on this particular machine. I too checked the remote access box during installation and my firewall (Windows' own) is configured correctly but I cannot connect. It states "Check the Live Mesh notifier on the device to see if Live Mesh remote desktop enhancements need to be installed." However, there is nothing on the notifier that offers any suggestions or instructions regarding these "enhancements". I do not have this problem on my XP machine.
Not sure where to go from here???
Any help is appreciated, thanks
2008년 5월 11일 일요일 오후 2:38OK, I found another thread regarding this issue. I initially used an elevation of privileges instead of being logged in as an admin. I removed the device from my Mesh, uninstalled and then reinstalled as an admin. That fixed the problem. However, I now have another.
The "send + ctl +alt + del" button does not force a log in prompt to appear. My screen remains black. The connection is active as I can see the mouse moving around on the other machine but if I were actually doing this remotely I could not see my desktop. I am testing this with both machines on my desk.
I made certain both video card drivers were current. I will try to test this tomorrow from work with another machine to see if it yields the same results.
Again, no problem accessing the XP machine remotely through Vista but unable to do the opposite.
Any thoughts or suggestions?
2008년 5월 12일 월요일 오후 3:51
As Kevin indicates above, when installing the Live Mesh Remote Desktop Enhancements in Vista, you must be logged in under an admin account. Live Mesh currently does not support over-the-shoulder elevation of privileges during install. If you initially installed from a Standard user account, please remove your Vista machine from your devices (go to the Devices tab on www.mesh.com, select the device you want to remove, then choose Options and click Remove device from Live Mesh), uninstall the Live Mesh software, then try installing again while logged into an admin account.
I hope that helps,
- 편집됨 Ben [Live Mesh] 2008년 5월 12일 월요일 오후 6:29 spacing
2008년 5월 12일 월요일 오후 4:02Hi Kevin,
We have a known issue with Live Mesh Remote Desktop that could produce the behavior you're seeing. Would you mind collecting your logs (from the target machine, the one that you were trying to connect remotely to) and submitting them to the team?
To submit a bug with your logs:
Please go to http://connect.microsoft.com/. Sign in and then select Live Mesh Tech Preview on Your Dashboard. Click Feedback and follow the instructions for collecting your logs and then submit a bug.
To get your logs:
1. Click Start.
2. Select All Programs and look for the Live Mesh folder.
3. Click Collect Live Mesh Logs.
4. Your logs will be bundled together in a cab file now located on your desktop.
Attach your LiveMeshLogs.cab file located on your desktop to your bug.
Note: you will have to submit a bug first, then edit it to attach your logs.If you do not have access to the Live Mesh Connect site, you can email your logs to email@example.com. Please provide as much information about your issue as you can in that email.
2008년 5월 12일 월요일 오후 6:13Kevin,
I'm OK now... my user account (Nicholas Bedworth) is setup to have administrator privileges. However, I was using the over shoulder elevation approach, and as you pointed out, this doesn't seem to work reliably. Right now, a colleague is going to add one of his machines to or mesh, and then we'll start experimenting with remote access.
2008년 5월 13일 화요일 오전 1:00Hey Ben,
I followed your instructions and I have tried multiple times to generate the log file. DOS pops up on the screen and it shows the file as being prepared but nothing shows up on the desktop.
I also dug around in the Mesh Program folder and there is a subfolder there named "Logs" but it is empty.
I don't understand why I would have problems generating the .cab file. I even did a search for LiveMeshLogs.cab from the start menu which yielded no results. I have my folders set to show all files although I doubt this would be a hidden file anyway.
Any suggestions? I would like to submit this bug so it can hopefully be resolved. The machine I really want to access remotely is the one I currently cannot. I have a home server which also makes this possible but I don't want to punch holes in my firewall and until UPnP is more secure, it is disabled on my router.
2008년 5월 13일 화요일 오전 1:20답변자Hi Kevin,
There are known issues with the log collection script, where it fails if you have a space in your NT username, if you've redirected your Desktop, or if it's a 64 bit machine. Are any of these true?
In the meantime, you can zip up the following files on the machine you are trying to remote to (if they exist) and attach them to the bug in Connect:
- "%USERPROFILE%\Local Settings\Application Data\Microsoft\Live Mesh\Bin\WlcMsTsc.*.log"
- "%LOCALAPPDATA%\Microsoft\Live Mesh\Bin\WlcMsTsc.*.log"
- "%PROGRAMFILES%\Live Mesh\Remote Desktop\*.log"
- "%PROGRAMFILES%\Internet Explorer\IExplore.*.log"
- "%USERPROFILE%\Local Settings\Application Data\Microsoft\Live Mesh\Setup\Servicing*.log"
- "%LOCALAPPDATA%\Microsoft\Live Mesh\Setup\Servicing*.log"
Sorry for the trouble!
Richard Chung [ Live Mesh ]
2008년 5월 13일 화요일 오전 2:04Hey Richard,
Yes, I have a space in my user name.
I will collect the files you specified and will submit them to Connect.
Thank you for the explanation.