Was just setting up XP on a machine I inherited, just messing around with it. This was the first time I've had an XP machine fail to install the connector software. I had fully updated XP (pro SP3) prior to trying to connect.
Of course the myserver/connect wants to install framework 4.0, and it appeared to be doing that. moved on and entered my server password, wake for backup, no to participate and the very next thing was the connector encountered an error and had to close. So this is where it didn't install on the XP machine, but had added the XP machine to the dash board.
I didn't think too much of it at the time, but I noticed the update icon in the sys tray and a notice of three 4.0 .net updates failed. I restarted the XP machine and it then installed those updates.
I kept getting the same error in the same spot, did a little research and found a post from someone that said they swapped the smsvchost.exe.config file from the 3.0 .net framework, to the 4.0 .net framework folder. At this time, I didn't have 3.0 installed, so I did a little more research. I found that NET.tcp sharing was supposed to be enabled, but when I viewed my services, I had no NET.tcp sharing service listed. Under optional updates, there were 3 more updates for .net 4.0, so I installed those thinking maybe they'd correct an issue. It didn't.
Then I messed up. Instead of simply uninstalling .net 4.0 and reinstalling it, I installed 3.5. After installing 3.5, this loaded NET.tcp sharing in to the services.msc. When I checked it's properties, it was coming from .net 3.5. I started this service, and the connector installed without further issue as well, I performed a backup of that client.
I guess that's fine and all, but now I feel I have unnecessary files installed. I believe installing 3.5 also installed 2.0 and 3.0 (at least they are all there under add/remove). 3.5 is listed as an SP1.
I'm guessing here, but I believe my original problem was that the connector was installing 4.0, windows update saw that and wanted to install the high priority updates that follow the initial 4.0 install and fowled up the initial 4.0 installation since I had no service listing at all for any NETtcp. No sharing or listener.
Just posting this in case someone else is searching for connector issues. I'd never had an issue with an XP machine before, but I couldn't say if those XP machines already had .net 4.0 installed or had it installed during connector setup.