LogMeIn OS X - 32 bit only

For several weeks I was frustrated that LogMeIn didn't work on my iMac i5 running 10.6.2. I couldn't find any explanation. I made do with the almost inert Java applet or used my MacBook (10.5) to maintain my mother's Mini.

Turns out LogMeIn is not fully compatible with Snow Leopard. It only works if Safari runs in 32 bit mode.

It did work for me in 32 bit mode, but it was flaky. I switched to Firefox which is still 32 bit (the 64 bit version is in beta I think). It worked there.

Obviously LogMeIn.com isn't exactly dying to please OS X customers. This should have shown up in blazing red letters for every OS X user who logs in to the service. Practically speaking, LogMeIn is not compatible with any of Apple's newer machines.

I don't mind them not having a fix, I do mind the time I wasted trying to make their product work.

Anyone know a better (please, no VNC) remote control solution? I don't mind paying! (Yes, I know about Apple's remote control solution. It's almost as crummy as iChat.)

Mobile Me back to my Mac for remote maintenance – a complete fail

I’ve had some luck so far with MobileMe, but this time I ran into a complete fail. It wasn’t completely unexpected.

I’ve been using LogMeIn to do remote maintenance of my mother’s Mac Mini, often using my old XP machine. It connects at the machine level; I can log out of her account and connect to the admin account in one session. Today performance using the Firefox plugin was excellent.

MobileMe’s Back to My Mac works very differently. It connects at the account level, and it’s designed as it’s named – to connect between two OS X machine-user-accounts that share the same MobileMe name. In other words, to connect to one’s own account – at the machine level, not the account level.

I had to setup an account on one of my machines with the same MobileMe user name as my mother. Then I could try the connection. As promised it did show her machine in my Shared device Finder display, but when I tried to connect I got a “connection failed” message. I assume my mother’s cable modem/router configuration is not supported.

Even if it had worked though I wouldn’t have been able to switch to her Administrator account, B2MM is an account level connection only.

OS X remote maintenance is certainly unimpressive. I’m even more impressed now with LogMeIn. This MobileMe feature failed.

See: The MobileMe Massacre begins

Video Chat for elder parents over OS X: Google Video/Gmail, Google Notifier, Firefox and LogMeIn

This is a bit complex to describe fully, but I hope these hints will be of use.

Briefly, I wanted to be able to establish a video chat connection to my elderly parents. Since we both use OS X and both have at least one Intel machine I considered iChat and Google Video Chat. I didn’t consider Skype or Yahoo because that would introduce new account issues and because, as best I can tell, Google has the best technology and no worse reliability than Skype or Yahoo.

I was unimpressed with iChat; it needs to be shot (see also). That left Google Video Chat, but it has a hellacious user interface. In fact, it has the lowest usability of just about any app I routinely use. Not well suited for my 80% blind and very arthritic mother. (I’m sure that will change when Google integrates GVC with Google Voice, but really Google needs all those usability people who’ve recently quite in disgust.)

At the same time I was exploring remote maintenance options and finally settled on LogMeIn Free.

This is the combination of technologies I’ve now cobbled together:

• Gmail/Google Video Chat: My mother’s email is managed via a Google account, even though she reads it using OS X Mail (IMAP). So she had an account.
• Google Notifier: In theory this keeps my mother logged in to Gmail so she doesn’t have to know her username and password. In practice I’m not sure this works; these day’s I might try FF with local caching instead.
• Logitech QuickCam Pro
• Firefox: For better or worse this is what my mother is accustomed to
• LogMeIn Free.
• I created a deskbar shortcut with is simple a Gmail desktop shortcut with the iChat icon pasted into it. So it looks like a Chat app.

Here’s how it works

1. I initiate the call from my Macbook using Firefox
2. I use LogMeIn to take control of my mother’s machine using Safari. Then I “answer” my own call (not hard).
3. I resize the window for my mother then drop the remote control connection.

Restarting a remote machine: XP and Windows 2003

How do you restart a remote machine, like an XP controlled by remote desktop or a Windows 2003 server running terminal services? At least with Windows 2003 server you see a grayed out button when you try to shutdown or restart from a remote desktop session.

In Windows NT and 2000 you could install the “remote shutdown tool” on your remote machine but Microsoft pulled it, perhaps because they had a rather serious security problem related to remote shutdown in XP SP1.

I couldn’t find much Microsoft documentation on how this works for XP, but it’s still supported. Just fire up the command line and type “shutdown –i”. In theory you need admin privileges on the remote machine for this to work (the SP1 bug allowed non-admin users to do remote restarts with another tool).

I can confirm this works on Windows 2003 server, though there is a known bug that can affect some machines.

Restart or shut down remotely and document the reason explains how to do it. You have to know the machine name of the remote machine and you have to have admin privileges on the remote machine associated with your network name. Oddly enough the documentation there uses / for an option delimiter, but if you type “shutdown” the directions use hyphens.

From a command prompt “shutdown –i” gives you a handy GUI (you can tediously browse the network for the machine), or just type this command line (where N4591Fred is not my real machine name) …

shutdown -r -m \\N4591Fred –t 0 -c "bug fixes"

The command line example above will shutdown with no warning, but it still takes a few minutes to shutdown, restart, etc.

Update: I’ve been told that if you’re connected to a remote server you can run the “shutdown.exe” command from the remote machine command line. I haven’t tried that yet.

Copilot vs. LogMeIn for supporting your parent's Mac

I hope this is what I asked for some time ago -- a version of Copilot that will let me control my mother's machine whenever I want, without her having to do anything or even know about it ...

Copilot OneClick for Macintosh - Joel on Software

... The new Copilot OneClick feature lets you preinstall the software on all the computers you connect to frequently, so every time your dad calls up needing help with the accounting software running his Ponzi scheme, you just click one link and you’re logged onto his computer.

As usual, it works through all kinds of firewalls, proxies, and NATs without any configuration, it’s protected by 128-bit SSL, and there’s never anything to configure.

Today, the Copilot team released the Macintosh version of the OneClick feature, so all the Copilot goodness is available on Windows or Mac, or both (you can control Windows computers from Macs and vice versa). And it’s cheap, by which I mean, inexpensive—I don’t mean that you can just buy it two drinks and take it back to your apartment and expect to be taking a bubble bath with it—most people get the $19.95 unlimited plan; it’s even free on weekends when we have lots of unused bandwidth.

Copilot uses VNC, so it's very slow. Nowhere near as useful as Citrix or Windows Remote Desktop. Alas, for OS X VNC is about as good as it gets. It's enough for troubleshooting if you're patient and if the screen sizes are reasonably similar.

Update 1/8/09: See also - Computer support for persons with special needs.

Update 4/25/09: As advised in a comment on this post, I ended up using the free LogMeIn instead. I installed the LogMeIn client on my mother's dual core Mac Mini running 10.4. I then installed the (theoretically optional but actually essential) controller client on my MacBook running 10.5. It's quite slow, but I'm able to control her computer with no action required on her part other than turning on the machine. Copilot wasn't price competitive, and it required my mother to do too much. With LogMeIn she has only to turn on the computer.

Update 6/7/10: LogMeIn stopped working. When I upgraded the Safari plugin on my MacBook running 10.5 it crashed Safari. There's still no 64bit support for Safari on OS X 10.6. I think LogMeIn has given up; I uninstalled them. I reviewed CoPilot again, but there prices for what I want have gone up a lot. I don't have any working solution at this time.

iPhone tips: reboot after updates and Starbucks access

Via Gruber, I learn that AT&T hotspots (including Starbucks) have finally launched their long promised iPhone access service with a tedious connection process:

Accessing AT&T Wi-Fi | Wireless from AT&T, formerly Cingular

1. Select 'attwifi' from the list of available networks
2. Enter your 10-digit mobile number and check the box to agree to the Acceptable Use Policy. Tap 'continue'
3. You will receive a text message from AT&T with a secure link to the AT&T Wi-Fi hotspot. You will not be charged for the text message. The SMS link will only be valid for 24 hours at the location it was requested. Another request must be submitted when using another hotspot location.
4. Open the text message and tap on the link for 24-hour access to the AT&T Wi-Fi hotspot

It's of greater interest to iTouch users and users without 3G access.

On an unrelated topic I've come across vendor recommendations to reboot the iPhone after every app update - esp. for users with several App Store products. Based on personal experience I think that's excellent advice.

MobileMe - Remote system control would make it useful

Apple's MobileMe is monumentally uninteresting -- less useful than .Mac.

Actually, it's worse than that. It's inferior to Google Apps, but since MobileMe is an Apple revenue stream they're incented to discourage Google Apps.

This is unfortunate, because if Apple made some modest changes to OS X 10.5 and MobileMe I'd buy a family package of both.

I want a remote system control option built into MobileMe. In particular I want to have full control of my mother's Mac Mini at all times -- without requiring her to do anything. (See also.)

Apple has all the pieces for this to work; even their toy VNC based remote control would be suffice.

[I first drafted this for .Mac in 2005. Found it while doing some cleanup; it's still true today.]

Screen Sharing in Leopard is a toy feature

When Leopard came out, I was very excited about the screen sharing feature. I thought I'd buy the OS in Jan 2008 for that feature alone, but there were so many bugs I waited until Sept 2008 to update my main machine.

During that long wait there was great excitement about how useful Screen Sharing in Leopard 10.5 was.

Cough.

Actually, there was total silence. A very suspicious total silence.

Which made it easier for me to wait until 10.5 was halfway decent; I knew my original expectations wouldn't be met.

Today, with both the MacBook and iMac running 10.5, I launched my long delayed test. It took about five minutes to make the call.

I'll keep it short. Leopard's VNC-based screen sharing is a toy compared to Citrix or Microsoft Remote Desktop.

Yes, it's marginally better than the worthless VNC tools I've previously used on OS X, but only someone who'd never used Citrix or Remote Desktop could think this imagine this VNC based solution was in any way comparable.

It is suitable only for use with iChat to do remote debugging, or with 'back to your desktop' to retrieve little fragments of data.

Typing lag is intolerable. The "scaling" is bitmap, not vector. There's no automatic vector resolution matches to the current display (which Microsoft has done for about 10 years).

The remote window is hemmed by the usual OS X chrome, so the usable screen space is very small. Keystrokes are not adequately captured; for example, I can't run LaunchBar on the remote display as the the local app captures my keystrokes.

Apple once marketed screen sharing as the #4 feature in Leopard, a few steps behind Time Machine (which has so far been of no use to me). Clearly Leopard was not about providing new features to users -- it was really about moving the development platform along.

OS X 10.5 was originally supposed to have a scalable Quartz-based UI with (screen) resolution independence. I can imagine that there was a screen sharing solution that went with that scalable UI, and that it was a serious Citrix/RDP competitor. Apple pulled the scalable UI before 10.5 was released; given how troubled 10.5 was, we know they made the right decision. Maybe, after the scalable UI was lost, Apple jammed this VNC solution in to fill the hole.

I'm sure I'll find a few uses for it, but nothing like what I was hoping for.

Update 9/27/08: BTW, you can only connect to the current user session. If it were possible to connect to a background session I'd have given screen sharing some points. It's obvious by the lack of objection to Apple's marketing that this is one of those capabilities that the vast majority of users really don't need or want!

Remote desktop control market improving

There's not much I envy from the Windows world, but Microsoft's (was it a Citrix offshoot) superb remote desktop protocol is on the list.

It was a work of genius. I don't have OS X 10.5, but I suspect the VNC dervied remote control features there are a pale shade of terminal services.

So, yes, I'm jealous. On the other hand, the good news is the remote desktop marketplace is expanding. Maybe news like this will convince Apple it's time to build a XP quality remote control solution for OS X.

In the news recently:

• WebEx PCNow: Costs $13/month, no per-use cost
  
• CoPilot is now free on weekends

I'd like to try out PCNow, but I didn't see any hint of a trial version.

Jing: free screen video capture for Windows and Mac

iShowU is a great low price OS X screen recording tool. I don't know of any high quality low cost tools for XP though. Until Jon Udell pointed me to TechSmith's Jing Project.

Free for now, which is a bit odd since TechSmith sells Camtasia -- which is very much not free.

Update 12/31/07: Jon Udell mentions Microsoft's SharedView.

Update 1/7/08: Udell also mentions Windows Media Encoder will do screen cast recording. Also I see the business plan for Jing -- it's tied to a media sharing service. That makes more sense! It won't work for corporate use then, and TechSmith sells Camtasia to corporations. SharedView is similarly tied to Microsoft Live. Windows Media Encoder screencasting looks like it's SilverLight based though I'm still following up.

No breakthroughs so far!

Bruce Eckel likes CrossLoop for XP screen sharing

XP is supposed to have built-in screen sharing controls, but I guess they don't work too well. Here's an important vote for CrossLoop:

Pairing Over the Web: "My brother recently turned me on to CrossLoop, which is the simplest and most responsive one we've tried, and allows both users to easily type into the document. Kudos to the CrossLoop creators; this really is a big improvement."

The first thing I'll do after buying 10.5.3 is describe what I think of Leopard's screen sharing. The lack of discussion on OS X blogs is probably meaningful.

Microsoft updates Remote Desktop Connection Client for Mac

I thought they'd semi-officially abandoned this client. Apparently not: Remote Desktop Connection Client for Mac 2.0 (Beta) - The Unofficial Apple Weblog (TUAW). Great news, I'll be using it.

Remote control for OS X: Suddenly, coming out of the woodwork ...

What the heck?! I've been ranting about the crummy remote control solutions [1] for OS X desktops for years -- to no avail (of course, I'm not delusional you know). All of sudden, they're popping up all over. Desktop Transporter is more interesting that most because it's now been acquired by DevonTechnologies, a very well regarded OS X vendor. It's not a straight VNC port [1] so I'll probably take a look at it. I doubt anyone but Apple is going to really be able to make this work the way I want [3], so I probably have to wait to see how bad 10.5 will be -- but I'll give is a try.

Some info on Desktop Transporter: Version Tracker: 3.8 stars

BTW, in the course of looking at DT I came across this extensive Macintouch topic thread. Alas, if only Macintouch would implement feeds for their topic page. There's only one mention of DT, but they mention some I'm familiar with. See also:

• Gordon's Tech TidBITS reviews OS X remote control software
• Gordon's Tech Leopard It does include remote control software
• Gordon's Tech The Apple AirTunes vision -- not really ready for primetime
• Gordon's Tech Remote control of a Tiger desktop
• Gordon's Tech Apple Remote Desktop (ARD) client service is now installed by default in 10.4
• Gordon's Tech Apple Remote Desktop 2 w- VNC

Update 7/28/07: No luck. I installed DT on two machines. It seemed to connect, but then simply hung with a black screen preview and a persistent "connecting" message. One machine is on 10.4.9, the other on 10.4.10. Local network, all Apple equipment. The only funny thing is I use WDS (an airport extreme and an airport express). The app complained NAT sharing was not enabled, though that should only be needed for remote access and the two machines showed a green internal connection. Enabling NAT on the Airport Extreme made no difference. I don't have time to futz with it, so this one is a flop.

--

[1] I know about VNC ports. I'm sure DT is really a VNC based solution, but it sounds like the developer worked to make it a better fit for Apple's oddball VNC implementation. It will be interesting to see how it handles multiple monitor and fast user switching for example.

[2] I know about Timbuktu as well. It was great once, but nothing I've heard about them recently makes me think they've kept up with the OS X world. Last time I looked they didn't have the confidence to offer a trial version. I suspect they just couldn't get deep enough into the OS to be efficient after classic died.

[3] It would have to be deeply integrated with Apple's mixed vector/raster display technology, which means only they can write it.

TSclientX: replace Microsoft's Remote Desktop Client with one made for OS X

I use Microsoft's Remote Desktop Client to control XP machines at home and work and to connect to Windows Terminal Servers (Win 2003). The terminal services interactions in particular are awesome, there's nothing comparable in the OS X world. It's my top complaint about OS X -- that Apple has never even tried to match Microsoft's six-plus year old remote control technology. 

Microsoft's Remote Desktop Client works very, very well under XP. They even made a client for OS X, but they stopped updating it a while ago. It's increasingly flaky, though I use it with some success even under 10.4.10 on a MacTel. I doubt, however, that it will work at all under 10.5 (BTW, I don't expect 10.5 until the spring of 2008 -- projects that big don't slip by only a few months, if it ships in October 2007 it will be dangerous).

So I'm very interested in TSclientX - An alternative RDP Client for Mac OS X. Runs native on Intel. Alas, it requires X11 ..

TSclientX is a Windows Terminal Services client for Mac OS X.  It appears to be a regular Mac OS application but is in fact an assembly of free software working in concert to provide similar (better?)  functionality to the official Remote Desktop Connection from Microsoft. Additionally, there is a nice tidy VNC Viewer built right in as well.

What makes TSclientX interesting compared to other Mac RDP Clients?

- SeamlessRDP is brought to you by Cendio's SeamlessRDP component.   It was originally introduced in rdesktop 1.5 and just simply rocks...

- Stability and speed on Intel Macs (and PowerPC Macs for that matter)   has been found by many to be superior compared to the official  Mac RDP client.

The most interesting ingredients are:

rdesktop 1.5 - http://www.rdesktop.org
An open source client for Windows NT Terminal Server and Windows 2000/2003 Terminal Services

tsclient 0.148  - http://www.gnomepro.com/tsclient A frontend for rdesktop and other remote desktop tools

VNC Viewer 4.1.2 - http://realvnc.com Virtual Network Computing

libao 0.86 - http://www.xiph.org/ao A cross platform audio library with CoreAudio support.

The GUI uses an optimized GTK+ build, specifically compiled for TSclientX.  Like most Unix-derived software on the Mac, Apple's X11 is required...

OS X Leopard: All is forgiven

Ok, so an out-of-cycle release of Safari is impressive, and a Windows version is astounding. Integrated GGears-style iPhone development -- perfect and wonderful. New Finder - at last, long needed. 64 bit - fine. A viewer architecture -- very good if it lets us finally view PowerPoint files [1] on OS X. Spotlight with Boolean operators? Duh, yes. Remote file access and/or synchronization via .mac - nice.

All more than sufficient to make me very happy to fork over $130 to Apple and some larger amount for family .Mac services. Heck, one or two of 'em would suffice. I wasn't expecting Jobs to address my longstanding whine anyway. I shed a few tears and turned to my work.

Then Andrew burst into my office and ripped the keyboard from my hands. His eagle eyes had spotted a small button in the Finder demo that nobody had commented on, a button that led him to this fragment on Apple's new Leopard page:

Apple - Mac OS X Leopard - Features - Finder

... With shared computers automatically displayed in the sidebar, it’s far easier to find or access files on any computer in your house, whether Mac or PC. All it takes is a click. But here’s where things get really interesting. By clicking on a connected Mac, you can see and control that computer (if authorized, of course) as if you were sitting in front of it. You can even search all the computers in the house to find what you're looking for...

So the very biggest "one more thing" is so big it didn't even merit a mention. This is what will allow Apple to sell the next, much more ambitious, version of Apple TV.

I'm a happy man today.

[1] Listening to the video there's no PPT support - just word and excel. Shame. Maybe later.

Atwood: why we don't miss Microsoft Streets and Trips

There are some applications that don't exist for OS X. One of the biggest omissions is quality speech recognition, but another is maps. There's nothing on the map like Microsoft Streets and Trips, even though S&T has been getting slower and buggier over the past two to three years.

I used to miss that application, though I became accustomed to its absence. Google Maps, and Google Earth, eased my pain -- except when I was on an airplane.

Now Jeff Atwood tells me I don't need to miss Microsoft Streets and Trips any more. His head-to-head real world testing demonstrates Google Maps is substantially faster and more usable than MS&T. Not merely comparable, but absolutely better. Also free, and it runs just fine on Camino/Firefox (Safari? What's that?).

I actually don't care that much (yet) about speech recognition on my desktop, so if Jobs today introduces OS X remote control functionality even 80% as good as Windows' ancient terminal services/RDP functionality the day of the PC will have truly passed.

TidBITS reviews OS X remote control software

One of the things that keeps me from being a complete Mac head is Microsoft's remote desktop protocol vs. OS X's ... ummm... uhhhh.

It's pathetic. OS X does have some hooks for a raster based unix remote screen control application, but it's stone age compared to Microsoft's iron age RDP. My best explanation for the absence of useful remote desktop control is that OS X users simply aren't interested. Once again I am reminded that a Vulcan's life is a lonely one...

Supposedly 10.5 includes some iChat remote control for remote maintenance. In the meantime we have CoPilot (works, but very slow -- useful only for remote support) and a variety of costly products that may or may not work. Now TidBITS reports one more option: LogMeIn for OS X is in beta. This product works quite well for Windows, so if the beta news isn't too bad I might give it a try.

SpyMe: another remote control app for OS X

SpyMe2 is presumably another VNC based remote control app, though the main page doesn't mention VNC. We're still waiting for something like Windows terminal services (RDP).

I might try it. Inexpensive.

Copilot 2.0 supports Macs - at last, at last, at last

For me, this is bigger than anything announced at MacWorld. Yeah, the iPhone is nice — but that’s months away. There’s nothing else that was announced that I want or need. Copilot is another story …

Copilot 2.0 supports Macs - The Unofficial Apple Weblog (TUAW)

…. Enter Copilot, the Fog Creek online 'assistive service' that allows you to connect to a remote computer using a small app and a website. Copilot 2.0 now supports OS X 10.2, and later, as well as both Safari and Firefox. No configuration is required, and the pricing structure is very interesting. 5 bucks will get you 24 hours of unlimited access, and if you find yourself using Copilot more than that there are subscription plans available that should suit your needs.

You can read more about Copilot at this post on Joel On Software, and to get a glimpse into the Mac dev side of things check out this post on Red Sweater blog. ...

Hallelujah. I wrote to the Copilot folks months ago and they said they were going to look seriously at a Mac version, but, honestly, I didn’t believe it. In the meantime I’ve was very jealous of some colleagues who showed me the free version of LogMeIn – XP only. I watched grinding my teeth in frustration at Apple’s determination not to deliver any kind of affordable remote maintenance solution (rumored, supposedly, for the next OS). Joel’s post on the product is, as usual, funny and informative. Five bucks for 24 hours use.

I’m going to ask my mother to put it in place on her Mac, so I can do support whenever it’s needed.

Now if Apple would only deliver the thin client solution that I’ve been whining about for at least 3 years … Alas, I think Jobs is allergic to it.

Update 1/26/07: I've been testing with two machines at home. It's painfully slow; it's running a variant of TightVNC and it's about as slow as VNC. It's nowhere near as responsive as Microsoft's Remote Desktop Protocol or the free logmein.com active-X service. It works though, I was able to do some basic work. An average window took 5 to 10 seconds to open, typing was slow but not as bad as window work.

There are definite rough edges:

1. Each time the service is used, both "host" (recipient) and "client" (helper, controller) must download and install a new local copy of the Helper and Host widgets.
2. They used .zip for transfer, which increases the risk of Stuffit seizing control. They should have used a compressed .dmg file.
   
3. When downloading with Firefox or Safari the requestor must download the zip, find it, unzip, then run the app. That's about 3 steps too many. When they're done they must find and discard the zip and the Copilot host widget.
4. It's slow, slow, slow. (Maybe the server is straining under the press of the new release?)
   

If there were other options I'd not bother, but this is a class of one. With some finagling it will likely work ...

Update 1/29/07: I sent a support email on this. The reply? They're changing from zip to .dmg.

Windows Home Server: At last, I say something nice about Microsoft

Paul Thurrott's SuperSite for Windows: Windows Home Server has the summary. I’ve been waiting a long time for this — but I was hoping (against hope) that it would come from Apple.

This is where we need to go; a home computing appliance with integrated backup and integrated secure remote access.

Microsoft is providing WHS users with a free Internet address via Windows Live. This address will give you a remote interface into your entire home network, not just WHS. You will be able to access any shared folders remotely, or even control individual PCs remotely.

All is not lost however ...

Mac user? You can access the WHS shared folders as you would any other Windows share, and that means your backup program--like Apple's Backup--can use a share as a save location as well. "We're a great back-end store for Time Machine," Headrick told me, alluding to the new backup feature Apple recently announced for Mac OS X Leopard.

Detente perhaps?

The missing piece is remote application executing using Microsoft’s very robust windows terminal services. That omission may be related to cost (CPU and memory demands on the server) or support and licensing concerns.

Very good, very impressive, and it’s about time. I’d very much like to see something comparable from Apple, but maybe they’d decided to surrender this to Microsoft. That would not bode well for Apple Computer Inc.