Hi,

I'm a little confused about your title of the thread. You mean the connector installation could start but hangs without any responding, right?

At first, please make sure that you could open the webpage on the Windows 8 client just like the figure below:

From your description, it seems that you tried to install the software on the server via Remote Desktop.

Regards,

James

The symptom sounds exactly the same as the one I'm experiencing.  I posted under the Windows 8 forum since I suspected after reading the log file that it was a problem ultimately caused by upgrading from regular Windows 8 (Core) to Pro using the pro pack.  Take a look at my posting here:

http://social.technet.microsoft.com/Forums/en-US/w8itproinstall/thread/cf2af721-a589-4ca6-b3f6-1588f4badb57

It would be interesting to know whether the error(s) in your ClientDeploy.log file are the same or different than mine.

Perhaps someone else out there will reply with a definitive answer to the location of ClientDeploy.log.  I'm currently at work, and the problem machine is at home.  Compounding that, I just reverted the system back to its original state, so my ClientDeploy.log probably isn't there any more.  To find it, I went to the Desktop, launched File Explorer, highlighted the C: drive, then in the search box typed ClientDeploy.  A lot of results came up, one of them being the log file.

I've read in another article that you may find ClientDeploy.log in c:\ProgramData\Microsoft\Windows Server\Logs, but I can't confirm that.  The ProgramData folder is hidden, so you'd need to check "Hidden items" from the View menu in File Explorer to see it.

I am actually running Windows 7 Ultimate SP1 and get the same type of error. 

Here is what I did to be in that situation.

On my original setup, when the setup process asked me to migrate my data and settings, I panicked and cancel the install until I read some more on the process.  I wanted to make sure not to loose any info despite my backup etc.

I have taken the system back to original state and deleted the machine from the server, left the domain etc and tried it a couple of times.  Always stuck at the same point.

I assume that there are probably registry keys that are left behind and are causing this crash repeatedly.  I am searching the web but not a lot of success so far...arghhh bleeding edge :-(

I have two windows 7 ultimate systems that we ran into the same problem with the computer being logged into user _clientsetup_$. Was on phone with dell techs all day to no avail. Would greatly appreciate an answer.

I had this issue when I tried to allow the system to migrate my local users to the domain user profiles. The Connector would crash then stay logged in as you described.

Here's what I suggest. Use Windows Easy Transfer to backup your local user profiles to the local hard drive. Run the Connector but only add the domain users you want, don't migrate files and settings. Once the Connector software is finished, login as a domain user and run Windows Easy Transfer again to import the files and settings you just transferred. Make sure that you click "Advanced Options" at the bottom right and map the local profile to the appropriate domain profile, aka "domain\username".

Hope this

The problem I've experienced with connecting Win 7 Ultimate is different from the one described by the OP in this thread.  Here's a snippet from the ClientDeploy.log on my Win 7 Ultimate (from folder c:\Program Data\Microsoft\Windows Server\Logs):

6036] 121028.124428.3475: ClientSetup: NetJoinDomain( , MYDOMAIN.local, , MYDOMAIN.local\Me, *, NetSetupJoinDomain, NetSetupAcctCreate, NetSetupAcctDelete, NetSetupDomainJoinIfJoined, NetSetupDeferSpnSet)
[6036] 121028.124451.7943: ClientSetup: nativeNetJoinDomain returned ErrCode=2699
[6036] 121028.124451.8879: ClientSetup: JoinDomain failed: System.ComponentModel.Win32Exception (0x80004005): Unknown error (0xa8b)
   at Microsoft.WindowsServerSolutions.ClientSetup.NativeMethods.NativeMethodRetryWrapper(NativeMethodInvoker nmi, UInt32 numTries, TimeSpan timeToWaitBetweenRetries, String descriptionForLog, UInt32[] retryableErrorCodes)
   at Microsoft.WindowsServerSolutions.ClientSetup.NativeMethods.NetJoinDomain(String server, String domain, String destinationOuPath, String user, SecureString password, JoinDomainOptions joinOptions)
   at Microsoft.WindowsServerSolutions.ClientSetup.ComputerMgmt.JoinDomain(String domainName, String domainUserName, SecureString domainUserPass, String machineAccountOU)
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.JoinDomainTask.Run(WizData data)
[6036] 121028.124452.1219: ClientSetup: Set CD Fail reason 7 for SQM in ClientDeployment.exe
[6036] 121028.124452.1219: ClientSetup: Exiting JoinDomainTask.Run

I've confirmed that the folder where ClientDeploy.log gets written is c:\ProgramData\Microsoft\Windows Server\Logs.  Regarding the problem that I'm having connecting a Windows 8 Pro ("moved up" from Windows 8) machine, here are the relevant lines:

[3876] 121107.194235.2285: ClientSetup: LookupAccountSid (computerName = [], sid = [S-1-5-32-544])
[3876] 121107.194235.2285: ClientSetup: NetLocalGroupAddMember (server = [], groupName = [Administrators], sidMember = [S-1-5-21-452769647-1665919795-2316062235-1116])
[3876] 121107.194235.3067: ClientSetup: LookupAccountSid (computerName = [], sid = [S-1-5-32-555])
[3876] 121107.194235.4318: 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)

As I have stated elsewhere, for this particular problem, I strongly suspect a bug in the Pro Pack.  The local group [S-1-5-32-555], which is "Remote Desktop Users", isn't present on my machine, but should be, and the connector is assuming that it should be.  It is present on another Windows 8 Pro system that I have that was Pro out of the box.

We need log files please. 

http://titlerequired.com/2011/09/27/troubleshooting-client-connector-install-sbs2011-essentials-2/ and http://social.technet.microsoft.com/wiki/contents/articles/3887.connectcomputer-troubleshooting.aspx

Can you post these up to a skydrive location and link them here please?

Here's a link to the ClientDeploy.log from my Windows 8 machine, which was originally Windows 8 but moved up to Pro via the Pro Pack prior to attempting to connect it to the server:

https://skydrive.live.com/redir?resid=44D346876078177A!173&authkey=!ADLanZOjfQcxEd0

I'll post a link to other log files as soon as I get access to them.  Thanks in advance for any insight you can lend.

Edit:

Here's the corresponding ComputerConnector.log:

https://skydrive.live.com/redir?resid=44D346876078177A!174&authkey=!AJ3UI5joDEUMDbM

And the CSetup.log:

https://skydrive.live.com/redir?resid=44D346876078177A!175&authkey=!AJen4ZElO54mrk4

[3876] 121107.194235.3067: ClientSetup: LookupAccountSid (computerName =
[], sid = [S-1-5-32-555])

[3876] 121107.194235.4318: ClientSetup: !!!FATAL!!! Unhandled Exception:
System.ComponentModel.Win32Exception (0x80004005): No mapping between
account names and security IDs was done

Hang loose while we figure out what's going on here.

Yep.  Since [S-1-5-32-555] is built-in group "Remote Desktop Users", and that group seems to be missing on my computer, I'm wondering if this connector problem is related to another problem I discuss in this thread:

http://social.technet.microsoft.com/Forums/en-US/w8itprogeneral/thread/22daddac-4c98-4089-b31f-40e2e783c682

"We are investigating the root cause now. But we do have a work around
for this issue. Because it happened on a page which only appears after
domain join. So if you choose to skip domain join then you may by pass
this issue."

Joining a computer without domain joining

So, you have a work laptop, or a nicely running non-domain based home network.  But alas, you have no home server options anymore...  You are left with the option of installing a Windows Server 2012 Essentials machine (which whilst expensive, really is a great home server option).    The problem is, you don't want the machines in your home in a domain, you want them to remain totally independant for many a reason.
Here is a nugget of information that you will love then.    When you run the Connect computer wizard (http://nameofserver/connect) you can avoid the domain join bit by simply running this command in an elevated command prompt beforehand:
reg add "HKLM\SOFTWARE\Microsoft\Windows Server\ClientDeployment" /v SkipDomainJoin /t REG_DWORD /d 1
....then, run the wizard and you will get all the good backup and home features without the domain join.

(taken from Full article...

Thanks!  Very helpful!  So far so good with implementing this workaround.

I first manually took the computer out of the domain (back to just WORKGROUP) & rebooted, signed in as my local admin account, deleted the leftover _clientsetup_$ account and profile, and deleted the folder that had been created under c:\Windows\Temp for the previous client deployment, just in case.  I then added the registry key above and re-ran the connector.  I found that I had to use the server (domain) administrator account to connect, rather than my standard user, which makes sense.  I got a warning/info dialog because I hadn't deleted the computer out of the server's dashboard, which was still there from the previous attempt, but I pressed forward and it seemed to work fine.  It did warn me that I'd need to manually set up backups, but as far as I can tell they're set up now.

After all of that, I manually (re)-joined the domain, and was able to sign in using my domain account.  Again, so far, so good!  I'll report back if I have further feedback to share.

Here are my log files.

http://files.lvthunder.com/CSetup.log

http://files.lvthunder.com/Computerconnector.log

http://files.lvthunder.com/ClientDeploy.log

please use "computer management" "%windir%\system32\compmgmt.msc /s"  To check if "Remote Desktop users" group is missing in "System Tools"->"Local Users and Groups"->"Groups"

Or start 'cmd.exe'  type 'net localgroup' 

[4816] 121029.103841.0354: ClientSetup: Call MachineIdentityManager.GetMachineStatus
[4816] 121029.103846.5163: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:InvalidUser ErrorCode:1326
BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus
   at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)
[4816] 121029.103846.5163: ClientSetup: Exiting ValidateUserTask.Run

You have a different error. What user are you using to run this wiz?

For my Windows 8 Pro computer ("moved up" from regular Windows 8 64-bit using the Pro Pack), the "Remote Desktop Users" group is definitely missing.  I posted a screen shot of the Computer Management -> Local Users and Groups -> Groups over here: http://social.technet.microsoft.com/Forums/en-US/w8itprogeneral/thread/22daddac-4c98-4089-b31f-40e2e783c682 .  Look at the first post.

I also have run the "net localgroup" command, and here is the output:

Aliases for \\MYPC

-------------------------------------------------------------------------------
*Administrators
*Distributed COM Users
*Event Log Readers
*Guests
*IIS_IUSRS
*Performance Log Users
*Performance Monitor Users
*Remote Management Users
*Users
*WinRMRemoteWMIUsers__
The command completed successfully.

[4816] 121029.103841.0354: ClientSetup: Call MachineIdentityManager.GetMachineStatus
[4816] 121029.103846.5163: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:InvalidUser ErrorCode:1326
BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus
   at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)
[4816] 121029.103846.5163: ClientSetup: Exiting ValidateUserTask.Run

You have a different error. What user are you using to run this wiz?

http://files.lvthunder.com/ClientDeploy.log 

In this log, do have same errors ,it's above what you posted here. And I hope lvthunder could list "net localgroup" of the pc.

[4080] 121028.141553.5308: ClientSetup: LookupAccountSid (computerName = [], sid = [S-1-5-32-555])
[4080] 121028.141553.8431: 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)

Hi, lvthunder

It will be great if you could confirm:

1. Do you have the remote desktop group listed on your machine? You can use command line: "net localgroup" to list all the groups.

2. Did you upgrade Windows 8 to pro too?

T

Tell me exactly how you went from Win8 plain to Win8 pro.  What exact steps (where you bought/got the upgrade code etc etc)

Any fix yet?  I have a similar if not identical problem.

Below are logs for a successful connect and an unsuccessful connect.  The differences begin with the IP address. Both addresses should point to the server (based upon ipconfig). RDP does not work to the IPv6 address.

  Good: [4808] 121122.190424.3450: ClientSetup: Got Server Ip=[192.168.0.163]  (IPv4)

Bad:  [4928] 121202.124509.9930: ClientSetup: Got Server Ip=[fe80::d411:81b2:9600:42a9] (IPv6)

Bad Computer:

Good Computer:

What's the good computer/what's the bad computer?

Any win8 upgraded to pro in the mix?

Any fix yet?  I have a similar if not identical problem.

Below are logs for a successful connect and an unsuccessful connect.  The differences begin with the IP address. Both addresses should point to the server (based upon ipconfig). RDP does not work to the IPv6 address.

  Good: [4808] 121122.190424.3450: ClientSetup: Got Server Ip=[192.168.0.163]  (IPv4)

Bad:  [4928] 121202.124509.9930: ClientSetup: Got Server Ip=[fe80::d411:81b2:9600:42a9] (IPv6)

Bad Computer:

[4928] 121202.124509.9930: ClientSetup: Configure DNS settings on local NIC
[4928] 121202.124509.9930: ClientSetup: Got Server Ip=[fe80::d411:81b2:9600:42a9]
[4928] 121202.124517.1630: ClientSetup: NetGetJoinInformation (server = [], ...)
[4928] 121202.124517.1630: ClientSetup: Running Join Domain
[4928] 121202.124517.1630: ClientSetup: Disconnect any share to the server.
[4928] 121202.124517.1730: ClientSetup: NetUseEnum (UncServerName = [] )
[4928] 121202.124517.1730: ClientSetup: NetUseEnum (UncServerName = [] )
[4928] 121202.124517.1730: ClientSetup: Trying to clear dns cache.
[4928] 121202.124517.3530: ClientSetup: Calling SetPrimaryDnsSuffix.
[4928] 121202.124517.3530: ClientSetup: SetPrimaryDnsSuffix (DOMAIN.local)
[4928] 121202.124517.3530: ClientSetup: SetComputerNameEx (DOMAIN.local)
[4928] 121202.124517.8030: ClientSetup: Update tcpip Domain parameter with DOMAIN.local
[4928] 121202.124517.8030: ClientSetup: Calling join domain [DOMAIN.local] with domain user [DOMAIN.local\Vered] credential.
[4928] 121202.124517.8330: ClientSetup: Joining local machine to domain DOMAIN.local
[4928] 121202.124517.8330: ClientSetup: NetJoinDomain( , DOMAIN.local, , DOMAIN.local\Vered, *, NetSetupJoinDomain, NetSetupAcctCreate, NetSetupAcctDelete, NetSetupDomainJoinIfJoined, NetSetupDeferSpnSet)
[4928] 121202.124541.3431: ClientSetup: nativeNetJoinDomain returned ErrCode=2699
[4928] 121202.124541.5431: ClientSetup: JoinDomain failed: System.ComponentModel.Win32Exception (0x80004005): Unknown error (0xa8b)
   at Microsoft.WindowsServerSolutions.ClientSetup.NativeMethods.NativeMethodRetryWrapper(NativeMethodInvoker nmi, UInt32 numTries, TimeSpan timeToWaitBetweenRetries, String descriptionForLog, UInt32[] retryableErrorCodes)
   at Microsoft.WindowsServerSolutions.ClientSetup.NativeMethods.NetJoinDomain(String server, String domain, String destinationOuPath, String user, SecureString password, JoinDomainOptions joinOptions)
   at Microsoft.WindowsServerSolutions.ClientSetup.ComputerMgmt.JoinDomain(String domainName, String domainUserName, SecureString domainUserPass, String machineAccountOU)
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.JoinDomainTask.Run(WizData data)
[4928] 121202.124542.2331: ClientSetup: Set CD Fail reason 7 for SQM in ClientDeployment.exe
[4928] 121202.124542.2331: ClientSetup: Exiting JoinDomainTask.Run

Good Computer:

[4808] 121122.190424.3450: ClientSetup: Configure DNS settings on local NIC
[4808] 121122.190424.3450: ClientSetup: Got Server Ip=[192.168.0.163]
[4808] 121122.190440.3071: ClientSetup: NetGetJoinInformation (server = [], ...)
[4808] 121122.190440.3371: ClientSetup: Running Join Domain
[4808] 121122.190440.3371: ClientSetup: Disconnect any share to the server.
[4808] 121122.190440.3671: ClientSetup: NetUseEnum (UncServerName = [] )
[4808] 121122.190440.4071: ClientSetup: NetUseEnum (UncServerName = [] )
[4808] 121122.190440.4071: ClientSetup: Trying to clear dns cache.
[4808] 121122.190440.5371: ClientSetup: Calling SetPrimaryDnsSuffix.
[4808] 121122.190440.5371: ClientSetup: SetPrimaryDnsSuffix (DOMAIN.local)
[4808] 121122.190440.5371: ClientSetup: SetComputerNameEx (DOMAIN.local)
[4808] 121122.190440.8271: ClientSetup: Update tcpip Domain parameter with DOMAIN.local
[4808] 121122.190440.8271: ClientSetup: Calling join domain [DOMAIN.local] with domain user [DOMAIN.local\Vered] credential.
[4808] 121122.190440.8371: ClientSetup: Joining local machine to domain DOMAIN.local
[4808] 121122.190440.8371: ClientSetup: NetJoinDomain( , DOMAIN.local, , DOMAIN.local\Vered, *, NetSetupJoinDomain, NetSetupAcctCreate, NetSetupAcctDelete, NetSetupDomainJoinIfJoined, NetSetupDeferSpnSet)
[4808] 121122.190448.3481: ClientSetup: nativeNetJoinDomain returned ErrCode=0
[4808] 121122.190448.3481: ClientSetup: Exiting JoinDomainTas

This isn't "fixing" folks and we're not getting to the root of the problem.  This also causes issues with RWW.

It's not a fix, it's a workaround.

Let's get to the bottom and not assume that your root cause is the same as these other root causes whereby they were upgrades from Win8.

RWW is remote web access and it makes it more complicated to support RWW.

Can you run the essentials log file tool, zip up the log files and park them on a skydrive and link the url here please?

http://www.microsoft.com/en-us/download/details.aspx?id=34821

Try this.  Let me know if it works.

http://sdrv.ms/VWb2ms

Here's the link.

http://sdrv.ms/SOYE8y

For reference, the "Good" computer here is DarthVader.  Install was smooth.  Win7 Pro 64-bit

"Bad Computer" is "Basement".  Pretty much same OS as "good computer.  I had t use my workaround.

Susan,  you are the best!

Thanks from a certified "newbie."

Susan,

I need your help again.  I had a string of unsuccessful backups.  I hoped that removing a computer and reconnecting it will solve the problem.  Now the computer won't reconnect to this client.

I receive the same message as others "Server not available...blah, blah, blah.

Here is my client deploy log.  I put into a Word file to highlight the first instance of the error in red.

Please let me know if you have any ideas.  thx.  Walter

http://sdrv.ms/XPEpYE

Hi all,

I have the same problem as the original poster, except for I upgraded via Pro Pack I purchased online through the add features wizard.  I also dont have a Remote Desktop Users group on this system either

Looks more like a bug in the Windows 8 upgrade pack implementation than in the Windows Server 2012 connect wizard to me.

Andrew.

I am in the same boat... I have a new Asus Windows 8 Core laptop, I then purchased the Pro Upgrade Pack and attempted to run the connector software downloaded from my server.  After first reboot, the program crashes and leaves me logged in as _clientsetup_$. 

The Computer successfully joins the domain, but the "Essential" software is not installed. No launch pad, no dashboard, means no backups being taken.

Current work around is not acceptable.

Email me at susan-at-msmvps.com

Let's get an official support case opened up to get this to the right eyeballs.

1603 normally is .net barfage.

Either install .net 4.5 and ensure all updates are installed or pull it off the system and try again.

Christopher

What brand of computer?

And would you be willing to make a disk2vhd backup and ship it to someone at Microsoft?

Yo folks?  I need help here.  I need to know the specs on these systems?  What brand of computer?

Can you email me directly at susan-at-msmvps.com please?

=============================================

Win8 (plain not pro)

use Propack to upgrade to the Pro version

Ends up that the RDP user group role is not there

It causes the Essentials wizard to barf

When you dig into the details you can tell it's missing a group but it gives a cryptic missing SID

Correlating to SIDs you figure out it's the Remote Desktop users group

**Still in investigation**

Please feel free to post a me too to be alerted to updates to this issue.  I proposed as an "answer" just so this would be seen if you hit this in googling.

The items you should look for are the following lines in the client logs:

As I have stated elsewhere, for this particular problem, I strongly suspect a bug in the Pro Pack.  The local group [S-1-5-32-555], which is "Remote Desktop Users", isn't present on my machine, but should be, and the connector is assuming that it should be.  It is present on another Windows 8 Pro system that I have that was Pro out of the box."

======================================================

I to have just hit this with a brand new Dell laptop with OEM Win8 Pro.  I did not "upgrade" from Win8 to Pro, it was Pro out of the box.  the "Remote Desktop Users" security group is missing, causing the Essentials connector/join process to fail.

Seems to me this is either a base OS BUG or an OEM BUG.

Kevin

I have this problem now too, with a brand new Acer Aspire S7. I used the pro-pack to upgrade from standard to pro. I also had installed WHS 2011 client previously, then deleted it. I "refreshed" the PC with media I had from another computer, but don't see the "remote desktop" user group. I have successfully installed other clients that were installed with Window 8 Pro directly, as opposed to the upgrade path taken with the S7. Rollup 1 is installed on the server. I can get through the domain join, client restart, about 10 minutes of "getting ready" messages, and then when it gets to the dialog box asking if I want to install just for me, or for all users, regardless of what I select, when I press "next" I immediately get the error message "Client Deployment Wizard stops working"

It's pretty tough to fathom how MS can let this problem hang around so long! Where's the fix?

First off can you dig out the log file and confirm that you are truly missing the remote desktop group on that PC just to confirm that we truly do have exactly the same issue?  I want to make sure it is exact.

Let me give you a bit of a understanding of how getting fixes out of Microsoft works.  First off this isn't an Essentials problem, this is a core Windows problem.  So first I have to track down the right people to contact.  Then we have to get them to repro the problem.  Given that this is a problem with OEM images, this isn't easy.  It took finding a person willing to send them log files.  And lately we JUST got them an image of an OEM laptop so they can investigate further.  So we're at the point now where the have repro'd it but they are still investigating the root cause.

I don't mean this to be an excuse, but just so that you understand a bit better that it takes time to convince Microsoft it's a problem when not many people hit the issue.  Squeaky wheels get grease (unfortunately) and repros can be hard when they don't the exact code causing the issue (I'm serious about this sometimes the left hand doesn't know what the right hand is doing).

Some have said that doing a refresh of the operating system puts the right bits on the box.

Bottom line it's still being worked on, we just don't have a magic bullet yet.

See if a refresh will fix, if it does not, the only option I have at this time is to reinstall.  There is something in the OEM builds and the Propack that fails to lay down the remote desktop users group.  I am kicking up a thread with people again to see if there's been any action but given that they haven't emailed me, I doubt it.  I apologize that I don't have anything better to tell you, I'm being flat out honest with you.

I do thank you for reminding me once again to email people and ask the status.

Hi,

Thanks for reporting this issue and providing all the information here.  I would like to give you a update on this issue.

The root cause is that after the upgrade from Windows 8 to Windows 8 pro, the "Remote Desktop user group" is missing on the win8Pro.  It will cause the client deployment process failed.

1) we are now working closely with windows team. the fix is on the way.  So far the schedule to release this fix is in July. It will be available via WU.  More details about the fix will be provided later when we have it.

2) We are also working on the Windows 8.1 to make sure this issue is correctly addressed.

Please let me know whether you have further questions about this issue.

Regards,
Guang

Windows Server Essentials Team.

Add me to the list of users affected by this undocumented feature in Win ProPack upgrade from 8 core. Just as identified in above user posts, Groups are missing and connector fails to completely join system to domain (Server 2012 essentials). Same error log as SID's do not exist. I have ran 2 full 8 pro install without incident and 2 win 7 core to 8 Pro upgrades without incident. It is clearly related to how the Propack is broken OOB, and fails to write the appropriate registries.

What are we expected to do? Wait till next month so we can complete the install and join? Use the band aids listed above that really does not address the issue? I want this machine to be part of the domain.

I have over 20 hours lost in trying to resolve this as well as 3 complete reinstalls. Not happy at all.

Short of waiting you can

a. rebuild the pc (not good)

b. use this kb to not join the domain now but at least get yourself connected

How to deploy a client computer in a
      Windows Server 2012 Essentials network without joining the domain:
     

      http://support.microsoft.com/kb/2752321

I'm sorry this has taken so long, but at least there is light at the end of a long tunnel.

I have a similar problem to the original poster. I will need to verify if the Win8 machine was upgraded. The machine was working, joined with the network and had what was considered to be an annoying popup, aka the Essentials Dashboard. The backups worked, all was good. The the connector was uninstalled from the client. The client was still a member of the domain and had access to server storage, but then the backup issue was found. Tried installing the connector again but got an error the client was a member of another domain. Manually removed the client from the domain and reran the setup at http://server/connect which appeared to work until the process died with the system logged in as  _clientsetup_$. The client is connected to the domain again, and server access is working as expected but the connector did not install and the system shows as offline. Tried twice with same results.

The odd part for me is it was working and I have client backups from before the connector was uninstalled.

I am somewhat concerned as the rest of the clients on the server were reported to be connected via the control panel, advanced system options to join the domain. I am wondering if they can be upgraded to use the client. Previous admin didn't understand/appreciate the benefits of the connector for client backup management.

Short of waiting you can

a. rebuild the pc (not good)

b. use this kb to not join the domain now but at least get yourself connected

How to deploy a client computer in a
      Windows Server 2012 Essentials network without joining the domain:
     

      http://support.microsoft.com/kb/2752321

I'm sorry this has taken so long, but at least there is light at the end of a long tunnel.

After a few more hours of fighting with this I gave up and submitted to the "Work Around". As other posters (jesman & WDGrossman) have suggested, I had to manually join the domain and manually set the back-ups, but the installation of the connector and dashboard did finally take albeit really broke with the work-around. I have not had a chance to confirm if the back-ups are taking place but should know in the next 48 hours. I suspect that as mentioned above, the back-ups, RWW and probably a slew of other features we paid for are or will not function properly.

My tone probably displays this sediment, but I am highly disappointed that it has been 8 months and there is still no Official fix. This is why I hate adopting newly deployed OS's and Server Software. Your users get to suffer and lab-test. This fix is painfully too slow to release...

Does anyone really know if the Official WU will break any of what we have done to achieve the work around or will it just correct anything that was missed by using the workaround? More directly, will this workaround cause issues when the Fix is released?

Also, Susan... thanks for your efforts in helping the community. I am not bashing your work, just Microsoft in their lack of response to a known broken product.

If the machine was previously joined with connect, you have a different issue.  I would recommend starting a brand new thread and posting the log files. 

I have this same problem after "upgrading" to windows pro using propack.  Disappointed that there isn't a better solution than "wait 'till July sometime".

HI Guang,

The last post on this was nearly a month ago where you said "So far the schedule to release this fix is in July".  Since Monday is July, and I have not been able to have any microsoft support person even acknowledge that there is problem, and the propack continues to be sold knowing that it is brokent, can we get some sort of update on when it will be fixed?   Early July?  Patch Tuesday?, August?.   Some sort of update would be appreciated as Microsoft seems to be hiding its head in the sand on this one.

Cheers 

Hi Guang,

I fully concur with notalbuk. This problem has been going on for far too long while Microsoft continues to sell a defective product upgrade.  I'm still waiting to recoup my investments in Windows 8 pro upgrades I purchased.

It is concerning enough that a major component was left out of an upgrade package but more concerning is the amount of time it has taken to fix this issue.

Keeping customers in the loop is one way to mitigate the frustration so an update would be most appreciated!