locked
Can't connect Windows 8 Pro (upgraded from Core) to Server 2012 Essentials RRS feed

  • Question

  • I'm running the evaluation version of Windows Server 2012 Essentials (Build 9200) and am trying to connect a client machine using thehttp://servername/connect URL.  This client machine is a brand-new computer that was Windows 8 Core x64 out of the box, but has been upgraded to Pro via the Pro Pack.  The machine joins the domain fine and reboots, then when ClientDeploy.exe continues, it crashes after I click "Next".  I'm wondering if it's because the client computer is missing some built-in groups (such as Remote Desktop Users, which I have bolded below) that the Pro version should have but didn't get added during the upgrade.  Checking the list of local groups, it's definitely not in there.  Here is an excerpt from the ClientDeploy.log file:

    [3472] 121101.145208.2387: ClientSetup: Start of ClientDeploy
    [3472] 121101.145208.3168: General: Initializing...C:\Windows\Temp\Client Deployment Files\ClientDeploy.exe
    [3472] 121101.145208.3324: General: Show floating language bar
    [3472] 121101.145208.3324: ClientSetup: Loading Wizard Data
    [3472] 121101.145208.3793: ClientSetup: Current DeploymentStatus=Running
    [3472] 121101.145208.6292: ClientSetup: OpenDNS Environment has been detected.
    [3472] 121101.145208.6292: ServerDiscovery:HostsFileUpdater: Ignore IPv6 link-local address: MYSERVER fe80::e91b:a811:5008:c075%12
    [3472] 121101.145208.6292: ClientSetup: Set OpenDNS environment state
    [3472] 121101.145208.6292: ClientSetup: Showing the Client Deployment Wizard
    [3472] 121101.145208.7541: ClientSetup: Set the Deployment Sync Event
    [3472] 121101.145210.6004: ClientSetup: Enter m_wizardPageSetupForMyselfOrOthers_PageValidating
    [3472] 121101.145210.6161: ClientSetup: LookupAccountSid (computerName = [], sid = [S-1-5-32-544])
    [3472] 121101.145210.6161: ClientSetup: NetLocalGroupAddMember (server = [], groupName = [Administrators], sidMember = [S-1-5-21-452769647-1665919795-2316062235-1116])
    [3472] 121101.145210.6317: ClientSetup: LookupAccountSid (computerName = [], sid = [S-1-5-32-555])
    [3472] 121101.145210.6317: ClientSetup: !!!FATAL!!! Unhandled Exception: System.ComponentModel.Win32Exception (0x80004005): No mapping between account names and security IDs was done
       at Microsoft.WindowsServerSolutions.ClientSetup.NativeMethods.LookupAccountSid(String computerName, SecurityIdentifier sid)
       at Microsoft.WindowsServerSolutions.ClientSetup.ComputerMgmt.GroupAddUser(SecurityIdentifier groupSid, SecurityIdentifier memberSid)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.m_wizardPageSetupForMyselfOrOthers_PageValidating(Object sender, ValidatingEventArgs e)
       at Microsoft.WindowsServerSolutions.Wizards.WizardForm.PageValidate()
       at Microsoft.WindowsServerSolutions.Wizards.WizardForm.NextButtonClicked()
       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ButtonBase.WndProc(Message& m)
       at System.Windows.Forms.Button.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
       at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Program.Main()

    Anyone seen this before and/or know a solution?  Many thanks in advance.

    Friday, November 2, 2012 4:28 PM

Answers

All replies

  • Hi,

    The error message you are getting indicates that Analysis Server received the script containing a username that it cannot resolve. Basically somewhere in one of your security roles you have a member that is no longer part of the domain. Or it might be you are trying to use local user and machine name has changed or you are deploying to different machine.  here are some informaiton for your referecne.

    http://social.technet.microsoft.com/wiki/contents/articles/3941.sbs-2011-troubleshooting-client-deployment-en-us.aspx


    Best regards, Jason Mei Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, November 7, 2012 7:43 AM
  • Thanks for the info!  I'll take some time and carefully read over the information in the Wiki.  I'll reply again later with further feedback and questions.

    My Windows Server 2012 Essentials has only two users, the administrator account (ServerAdmin) and the standard user (Me).  I would have used "Administrator" for the administrator account, but it wouldn't allow that name when I set up the server initially.  My Windows 8 Pro ("moved up" from Windows 8) has one user: "Me".  At least, I haven't set up any more users other than that one, which was added during the initial Windows 8 setup before moving up to Pro.

    Based on the ClientDeploy.log above, it looks like it successfully looks up the local [Administrators] group (SID [S-1-5-32-544]) and successfully adds the "Me" account (SID ending in -1116) to that group.  It looks like it blows up when it tries to get the name for SID [S-1-5-32-555], which is the well-known SID for local group "Remote Desktop Users".  Coincidentally, I noticed that in looking at the Computer Management console, the Windows 8 Pro computer ("moved up" from Windows 8) doesn't have that local group for some reason.  A second Windows 8 Pro computer that I have, which was Windows 8 Pro out of the box, does have that group.  Thus, at this point, I'm still suspecting a bug in the process that "moves up" Windows 8 to Windows 8 Pro.  While it may or may not be related to this specific problem, why would the "Remote Desktop Users" local group (as well as several others that should be present in Pro) be missing?

    Wednesday, November 7, 2012 3:23 PM
  • Hi,

    I know the error just occurs behind S-1-5-32-555,but it doesn't indicate this issue seems related to remote desktop user local group. As i mentioned, this error seems you are trying to use local user.


    Best regards, Jason Mei Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, November 8, 2012 8:44 AM
    • Proposed as answer by Jason Mei Monday, November 12, 2012 6:35 AM
    • Marked as answer by Niki Han Thursday, November 15, 2012 6:16 AM
    Friday, November 9, 2012 2:34 PM
  • Thanks for your sharing.

    Best regards, Jason Mei Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Monday, November 12, 2012 6:35 AM