I'm using a new Dell laptop with the latest Windows 10 to remote into a laptop at the office and I'm running into a wall trying to get Microsoft Activesync or Mobile Device Manager to communicate with this new laptop. I'm told by the IT people that Microsoft isn't supporting these any longer but I don't have the full scoop on why they won't communicate. Anyone run into this and have any solutions? I'm using Access running on a TSC3 and Windows 10 does not want to acknowledge and communicate with the TSC3. The older version of Windows 10 running in the office works just fine, but having to go into the office to upload and download survey data sort of defeats the purpose. My head hurts after dealing with IT people all week. Any help would appreciated. TIA
Your IT is correct. Microsoft is no longer supporting the windows mobile devices. There is a work around, it something that is changed in the computers registry, although that may no longer work. Each time windows updates, you need to redo the fix. Depending on your level of IT it may not be worth it.
My work around is to jump drive the job folder from the TSC to my computer. Easy.
Look for a Trimble support file named WMDCRegistryUpdate?ÿ ?ÿit repairs registry entries to allow the TSC to communicate with windows.
Use a geek whistle like Jon suggested.?ÿ Make sure you do a soft power off on your DC before removing the jump drive.?ÿ I've had a few that got corrupted, and then had to be reformatted, before I figured out the problem.
USB flash memory, but in my mind only those that hang on a lanyard like a referee's whistle.
Thanks for the direction guys. Geek whistle. I don't know if I'll call one anything else from here out. Cheers
?ÿI got this from the local trimble service tech when having connection issues with a TCU after a windows update. As I recall, following suggestions worked.
I beam my coordinate files via bluetooth to my laptop.
I still use my own video:
?ÿ
and the accompanying cheat sheets:
?ÿ http://igage.com/v/bin/WMDC_Win10_CreatorsEdition_Fix_RevB.pdf
?ÿ http://igage.com/v/bin/WMDC_RNDIS_007.pdf
for our customers. Seems that once you get it working, you need to do it again every year or so.
The advantage of manually entering the registry commands and then doing the 'Services' trick is that we can do them without rebooting the computer which disconnects our remote screen share.
I am pretty sure it still works because I used it twice last week.
GEEK WHISTLE?
OMG
?ÿ
JA, PLS, SoCal
Trimble Man coined that name?ÿ
Can't tell you when or where I heard it called that for the first time because it has been so long ago.
@mark-silver Wow, this worked on my Windows 10 installation! Thank you! The obscure nonsense that lurks in Microsoft Windows is mind-boggling.
I had been using a Windows 8 virtual machine for running Windows Mobile Device Center.
I think that video has more views than any other video I have ever done. And I was not wearing a tie and I did not shave that Saturday morning. Look like a bum. Dang-it.
Glad it worked for both of you. Like I said, we use it a couple of times every week.
This whole Windows Mobile Device Center (can I say b*lls**t) thing is just too much. It is why we are pushing the Carlson RT4 so hard now.
?ÿ
M
