Windows 10: Win 10 whs 2011 2753 cannot uninstall connector no launchpad

Hi Everyone,
This problem is on the last of eight machines I am upgrading.
On all the others after installation the WHS connector did not work. I uninstalled it, restarted, reinstalled it and everything was Hunky Dory. Not this time!

The connector would not uninstall - error 2753.
I then uninstalled it manually, deleting the appropriate registry key but could not reinstall so undeleted the key.
Found a beautiful Microsoft Fix here:
https://support.microsoft.com/en-gb/..._and_uninstall
NOT APPLICABLE TO WIN 10.
Have run chkdsk /r - no change.
CAN run dashboard.
Part of the issue is that some of the Windows server local services such as client backup and health service are marked to start automatically BUT DO NOT. They can be started manually and then Launchpad can be opened from ALL APPS but it should start automatically. I have just tried disabling and re-enabling it in System Configuration/Startup/Task Manager.
There is a myriad of posts on related issues on the web with convoluted suggestions for solution; I am looking for a simple one!
Thanks for your help.
Mike.

UPDATE..

...one step forward. After the restart the green Launchpad sign in box appeared (it has before) I signed in then got the: the server appears to be offline message and then by magic the white sign in boxes disappeared leaving the four usual options: backup, remote web access, shared folders and dashboard. This is further than I have got so far BUT on pressing backup, it does not connect and just notice the white flag at bottom left of green Launchpad box is flashing indicating server offline so nut much progress at all if any.

:)

 

Win10, v1607 Update: WHS 2011 Launchpad does not work

Thanks for the reply Syed. I followed your link but could not find a WHS forum on TechNet (only 'General', in business server). However, I did find a link to social.microsoft and posted in their

WHS 2011 forum.

This forum stuff is very confussing - I miss the old MS forums so much.

Anyway, thanks for the reply.

Cheers,

Chris

P.S. The answer was to exit Launchpad, leave it, and re-boot. Launchpad loaded on boot and signed me automatically, as it should. (Exiting Launchpad but not re-booting the laptop did not work.) However, there is no 'Mark as Answer' option for this post...

 

WHS2011 Launchpad Blank

The WHS 2011 Launchpad opens. Ir will not sign on automatically as it does in Win 7. Manual sign in is required by entering Username and Password. The Launchpad then changes to its usual green backgrounf but without any text other that LAUNCHPAD at the
top in white. So there are no links to click to access Shared Folders or Dashboard, for example.

 

Have now set client backup and health service to delayed start rather than automatic which does start them both after about three minutes of startup. The server can now see the client and may backup automatically or not, we shall see. Actually it does not matter too much as this is my main machine so I could do a manual backup at any time. But that is not the point is it?! it was set to automatic at start so should do as instructed. I have checked the logon, recovery and dependency tabs on these settings and they match the adjacent computer which is performing perfectly normally. Any suggestions folks?

Mike.

 

Hi,

I also had some minor issues with WHS2011 after my upgrade.

However, I think you should remove your "computer" from WHS console on the server first, uninstall WHS connector on the client. Reboot client, then install again.

Thing is, I experienced a lot of issues with backup becuase it was backing up drives and folders not being there after the upgrade.

Worth a try at least.

After I did it, all my clients are being backed up perfectly by the WHS 2011 server.

 

Thanks for your suggestion. I may have to go there but am avoiding it at present as, since I cannot uninstall the WHS connector on the client now, there is no guarantee I will be able to do so even if I remove it from the server or am I wrong?

 

When you install WHS connector it creates a reg key with some token data with the server -> client. And hence often the installer gives issues.

But if you delete or add new drives to the "client" marked in WHS Console on the server, it should be set again when installing.

You will be able to remove server sided client all the time, with no client interaction. So should not be a problem.

But why cant you uninstall the connector? it might not give the error this time, its not the most stable installer but worth a try.
Also you can download the installer manually 32/64 BIT versions if you dont want the one on the server.

 

Thanks for your further information.
I have tried to uninstall the connector five times with the same result and the same error given: 2753.
I will try to download the installer from the web but expect to be told I cannot use it until the old one is uninstalled.
At least currently I can access the server for backups but am still concerned if I am not careful I will be locked out. If I knew what was wrong I could copy a key from another machine or my last Win 7 backup before upgrading.

On a further note I have now entered my login credentials into launchpad and to it to remember me. The server offline flag is lit but it is online and I can access it BUT I still get the server offline dialogue box popping up offering me the option to login offline or not!

 

Mike,

Did you solve your issues with WHS2011?

 

Thanks for asking.

Have not tried your suggestion of removing client from the server side yet.

Have more pressing problem of client cleanup backup not running for two years. have deleted all backups and am now rerunning to save space. Hopefully then the server will have room to backup. All in all, very unreliable and bugridden.

Very best wishes,

Mike.

 

Well, today decided to reinstall WHS 2011 as sick and tired of backup cleanup not working and status of client backups shown as unknown. Thus removed the computer in question from the server in the hope the connector software could be uninstalled - NO DICE! Also no installer fixit for Win 10 yet so completely stuffed.

Any ideas folks please?

 

Have just had another look at problems connecting to WHS 2011 and just noted that non ascii characters can cause problems.
Now, this computer is called STUDY2 and am wondering if the 2 may have become superscript in the win 10 upgrade?
Furthermore, have read that with Win 7 you could do an in place reinstall using the Win 7 disk and selecting "UPGRADE" thus keeping everything and hopefully sorting errors. Is this possible with nWin 10?
Best wishes,
Mike.

 

There is a NASTY bug unfortunately in the WIN10 Anniversary Upgrade that has broken the WHS 2011 server connector software on the WIN10 client. Once uninstalled, you can not even do a reinstall of the server connector on a WIN10 client.

See https://social.microsoft.com/Forums/...&prof=required

WHS2011 is not the only victim, see “Windows 10 Feature Upgrade breaks client server connector for Window Server 2012 R2 Essentials, Windows Server 2012 Essentials and Windows Small Business Server 2011 Essentials” at https://blogs.technet.microsoft.com/...11-essentials/

 

I have done 2 Wino1 0 1607 installs now, both OK With Windows Home Server 2011 Launchpad.

1) Clean install of Win 10 Anni update, installed Launchpad from Server = OK and no issues
2) Upgraded Win 10 Anni on SONY VAIO Laptop = OK and no issues

Both are doing backups, both are showing al icons and I can browse etc...

I have NOT tested to uninstall, and re-install just for the sake of it.

 

FYI, the Event Viewer report is--
Product: Windows Home Server 2011 Connector - Update 'Hotfix for Microsoft Windows (KB2781278)' could not be installed. Error code 1603. Additional information is available in the log file C:\ProgramData\Microsoft\Windows Server\Logs\ClientCore.msi.log.
The log contains this -

Running Task with Id=ClientDeploy.InstallSoftware
[17132] 160812.064307.6120: ClientSetup: Entering InstallSoftwareTask.Run
[17132] 160812.064307.6120: ClientSetup: Install package C:\Windows\Temp\Client Deployment Files\ClientCore.msi
[17132] 160812.064307.6160: ClientSetup: Running MSI: C:\Windows\Temp\Client Deployment Files\ClientCore.msi SOFTWARE_NAME="Windows Home Server 2011" ADMIN_USERNAME="Administrator" ADMIN_PASSWORD=******* PATCH="C:\Windows\Temp\Client Deployment Files\KB2781278-amd64.msp" REBOOT=ReallySuppress
[17132] 160812.064352.7887: ClientSetup: Running MSI threw an exception:Microsoft.Deployment.WindowsInstaller.InstallerException: Fatal error during installation.
at Microsoft.Deployment.WindowsInstaller.Installer.CheckInstallResult(UInt32 ret)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RunMsi(String msiPathOrProductCode, String logFilePath, Dictionary`2 msiProperties, Boolean install, ProgressChangedEventHandler progressHandler)
[17132] 160812.064352.7887: ClientSetup: RunMsi returned error: RetCode=1603
[17132] 160812.064352.7887: ClientSetup: Failed to install C:\Windows\Temp\Client Deployment Files\ClientCore.msi
[17132] 160812.064352.7887: ClientSetup: Exting InstallSoftwareTask.Run
[17132] 160812.064352.7887: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has TaskStatus=Failed

KB27812278 has been installed on WHS2011 to deal with a UEFI based client computer. This client computer has the older version BIOS and therefore that hotfix is unnecessary.