Troubleshooting Client Deployment Issues when using Windows Small Business Server 2011 Essentials, Windows Home Server 2011 and Windows Storage Server 2008 R2 Essentials
Add this info to the file in the following format: 127.0.0.1 localhost ::1 localhost [yourserverIPaddress] [yourservername] Note: Do not start the entries with a # symbol as shown in the examples in the hosts file.
127.0.0.1 localhost
::1 localhost
[yourserverIPaddress] [yourservername]
Note: Do not start the entries with a # symbol as shown in the examples in the hosts file.
Applies to
Windows Home Server 2011 and Windows Storage Server 2008 R2 Essentials, while client has Media Center feature enabled. Symptoms
Open the ClientCore.msi.log under %programdata%\Microsoft\Windows Server\Logs on the client and search for the following logs:
Error 1722. There is problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SetupMcConnector, location: C:\Program Files\Windows Server\Bin\esSetup.exe.
Cause
Media Center add-in installation failed during client connector installation. Solution
First, as a genearal trouble shooting step, try to install the client connector again. If it still fail, please follow the below steps to resolve this issue.
Note these steps will allow the client connector to skip the installation of Media Center Add-in. This add-in intergates the build in shared folder into media center, without the the add-in, you will not be able to access media files on server's shared folder from Media Center Console, or record/archive TV to the server share. However, there will be no impact to Media Center features or the Server Shared Folder features.
On the client computers, run regedit to open the registry key, (note: if the client is a 64bit client, make sure you run the regedit 32bit version, which could be found under %systemroot%\syswow64\regedit.exe)
Windows Home Server 2011, Windows Small Business Server 2011 Essentials and Windows Storage Server 2008 R2 Essentials Symptoms
The following log files located on the client computer at %programdata%/Microsoft/Windows Server/Logs include the records noted:
Product: Windows Server Connector -- Error 1920. Service 'Windows Server Client Computer Backup Provider Service' (WSS_ComputerBackupProviderSvc) failed to start. Verify that you have sufficient privileges to start system services.
Service "WSS_ComputerBackupProviderSvc" failed to start: Unhandled exception in OnStart: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException: The task image is corrupt or has been tampered with. (Exception from HRESULT: 0x80041321)
Task Scheduler could not complete the task because the task image is corrupt.
Solution
For information that may help you resolve this issue, see the related posting in the Windows Client TechCenter (http://social.technet.microsoft.com/Forums/en/itprovistadesktopui/thread/d24a6af9-4c42-4507-9562-fdf466c9d707).
Windows Small Business Server 2011 Essentials
The Windows Server Connector was uninstalled from a client computer that is still joined to the domain of a different server.
This behavior is by design. Uninstalling the server Connector does not unjoin a client computer from the network domain.
To resolve this issue, manually unjoin the client computer from the network, and then visit http://<servername>/connect to automatically reinstall the connector and join the network domain.
Windows Home Server 2011, Windows Small Business Server 2011 and Windows Storage Server 2008 R2 Essentials
Symptoms
After restarting the computer multiple times, the message continues to appear.
A previous software installation on the client computer has left the computer in a restart pending mode, and restarting the computer does not clear the status.
You may be able to resolve the issue by performing the following steps:
You can also use this resource and script to find any files if your registry key is empty: http://msmvps.com/blogs/bradley/archive/2011/09/26/cannot-connect-the-computer-to-the-server-the-computer-has-a-restart-pending.aspx
Windows Home Server 2011, Windows Small Business Server 2011 Essentials and Windows Storage Server 2008 R2 Essentials
You cannot open the Dashboard from Launchpad on the client computer.
You will experience this problem in the following scenario:
At this point, the more recent version of the Windows Server Connector installed on client computers is not compatible with the older version that is installed on the server.
As a best practice, you should install the most recent updates on the server. To install the most recent updates from Microsoft:
If you do not want to install the most recent updates, you must uninstall the Windows Server Connector update on the client computer. To uninstall the update on the client computer:
The update installation process on client computers may run continuously for an extended period and does not finish.
An unknown error caused the connector update installation to fail on the client computer.
You may be able to resolve this issue by perform the following steps:
Windows Home Server 2011, Windows Small Business Server 2011 Essentials and Windows Storage Server 2008 R2 Essentials Client is Windows XP SP3
During client connector installation, you will get an error message says "The Connector has encountered an unexpected error" and on your XP client NetTCPPortSharing service is in starting status but not successfully started.
In some situations, NetTCPPortSharing service fail to start on XP client with .NET 4.0 installed. That may caused by several reasons including
Note if your C drive is a dynamic disk, convert the dynamic disk to basic disk or upgrade XP to Windows 7 will also resolve it, however, keep in mind coverting from dynamic disk to basic disk will erase all data on that disk.
It happens if you joined this client to Windows Small Business Server 2011 Essentials before and uninstalled the connector software but not leave the Server domain. When you try installing the client connector to connect to the same server with different user credential, you will get this error.
For domain joined client, changing the AD content requires network administrator permission.
Please use the account has network administrator permission to deploy the connector.
[3012] 120427.090332.6261: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:NetworkError ErrorCode:-1
BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus ---> System.ServiceModel.Security.SecurityNegotiationException: Could not establish trust relationship for the SSL/TLS secure channel with authority 'aurorajuyao:65500'. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
Windows Home Server 2011, Windows Small Business Server 2011 Essentials and Windows Storage Server 2008 R2 Essentials, Mac Clients
Apr 12 18:37:31 RysMac.local WSL[1015] <Error>: /Users/xcbusr/macbuild/Request/9AA878B8-1898-4BEA-8BA9-0B5091CFCEE7/MacUtils/RegistrationManager.m:383 Registration failed
Windows Home Server 2011, Windows Small Business Server 2011 Essentials and Windows Storage Server 2008 R2 Essentials Client does not have .NET 4.0 installed and has Anti-virus software install like Kaspersky. Symptoms
NetworkUtil::_WinInetDownloadFile (http://[FE80:0000:0000:0000:90D2:61F9:FF62:3294]:80/Connect/default.aspx?Get=dotNetFx45_Full_x86_x64.exe, C:\Windows\Temp\Client Deployment Files\dotNetFx40_Full_x86_x64.exe) _CopyInetDataToFile - InternetReadFile returns 12002 _CopyInetDataToFile (., C:\Windows\Temp\Client Deployment Files\dotNetFx45_Full_x86_x64.exe, 300000, 500000000) failed with hr = 0x80072ee2 _WinInetDownloadFile returns 0x80072ee2. NetworkUtil::DownloadFile(http://[FE80:0000:0000:0000:90D2:61F9:FF62:3294]:80, Connect/default.aspx?Get=dotNetFx40_Full_x86_x64.exe, C:\Windows\Temp\Client Deployment Files\dotNetFx45_Full_x86_x64.exe) failed with hr = 0x80072ee2.
This issue will be solved when you try install the client connector again, there is no any function break.