We set up a Windows Server 2012 R2 server to be migrated from a Windows Server 2008. The migration process moved over Active Directory, DNS, and other objects successfully, however, running the "Configure Windows Server Essentials" wizard will fail with an unknown error. After some digging through the logs, we demoted the new server and re-ran the setup which completed successfully and we were able to enter the Dashboard to continue the setup process.

Getting the workstations to connect through the connect wizard gives us an error stating that either the trust relationship, or the time is off-sync with the server. The time is not off-sync.

So, thinking it was most likely the Windows Server Essentials Experience Role, I removed it and re-added it only to be back where I started with the Configuration wizard throwing errors because it doesn't like being on a domain controller.

Under C:\ProgramData\Microsoft\Windows Server\Logs I was able to find these errors being thrown:

[3332] 141115.210552.3357: DeploymentService: No answer file found. Keep waiting.
[3340] 141115.210557.3514: DeploymentService: No answer file found. Keep waiting.
[3436] 141115.210602.3556: DeploymentService: No answer file found. Keep waiting.

In a KB article it mentioned adding the ServerAdmin$ and MediaAdmin$ accounts to the "Log on as service" default domain controller policy, which has been done, but when we expand "Policies" we're met with this error:

"Resource '$(string.VerMgmtAuditModeEnable)' referenced in attribute displayName could not be found. File C:\Windows\PolicyDefinitions\inetres.admx, line 1495, column 249"

We're able to click "OK" to go past it and edit the policies, but I'm not exactly sure if this error is associated with the mayhem of the configuration wizard.

This server lives in a 5 - 7 workstation and the only roles that are installed at the moment are: Active Directory Domain Services, DNS, DHCP, Windows Deployment Services and Windows Server Essentials Experience.

With these errors we cannot open the dashboard, when we demoted the Windows 2012 server then ran the config it succeeded, but the workstations would not connect to the server using the http://server/connect wizard method, thus not showing up in the devices tab, thus not being about to set up remote access properly.

• Moved by Justin GuMicrosoft contingent staff, Moderator Monday, November 24, 2014 6:37 AM From Windows Server 2012 Setup forum

Hi,

Before going further, would you please let me confirm something more?

Based on your description, did you mean that this Windows Server R2 Standard which will install Windows Server Essentials Experience role was in an Existing Active Directory Environment? Did you mean that it will fail to configure Windows Server Essentials Experience role when this Windows Server 2012 R2 is a DC? And if demote the server, you will configure the Essentials role successfully?

On current situation, please refer to following article and check if can install and configure Windows Server Essentials Experience role via PowerShell successfully.

[Forum FAQ] How to install and configure Windows Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely

By the way, please open Event Viewer and check if find relevant events.

If anything I misunderstand or any update, please dont hesitate to let me know.

Hope this helps.

Best regards,

Justin Gu

Justin, thank you for your reply. Your breakdown is exactly what's going on.

Windows Application and System logs tell me nothing of what's going on in the wizards.

I gave your powershell command a shot, and received this error (Sorry, would love to attach images but the forum isn't letting me):

Start-WssconfigrationService : While trying to resolve a cross-store reference, the target principal could not be found in the domain indicated by the principal's SID.

At line:1 char:1

+ CategoryInfo   : notspecified: (:) [start-wssconfigurationservice], PrincipalOperationException

+ FullyQualifiedErrorId  : System.DirectoryServices.AccountManagement.PrinicipalOperationException,Microsoft.WindowsServerSolutions.Setup.Commands.InvokeEssentialsConfigureServiceCommand

We are still having this issue and without resolving it, remote web access will not function. Does anyone have any suggestions on what to do next?

If it was me, I would backup my data and start with a fresh install.  With less than 10 users/time spent ....Just sayin :)

Reinstalling windows isn't an option. Like I said previously, everything seems to work properly BESIDES the configuration wizard, which refuses to work.

Did you migrate from SBS 2008 or full 2008? Did the domain have any trusts or sub domains etc?

Full 2008, not SBS. And no, no subdomains or trusts. Just a basic domain with 7 - 8 computers and about 6 users running DNS, DHCP, Routing and remote access, etc etc.

Since this thread, that server has been demoted and turned off. The 2012 server now runs all the services. I also double checked active directory to make sure that the proper server is registered as the domain controller, and it is. With no other domain controller present anywhere in the list.

Does anyone have any suggestions on this matter? I'm at a loss right now.

Hi,

I would ran the GUI configuration then re-check the logs on C:\ProgramData\Microsoft\Windows Server\Logs for any possible clue.

The error received from the PowerShell attempt seems to be related to the underlying System.DirectoryServices.AccountManagement , maybe the credentials are not belonging to the required groups:

From the [Forum FAQ] :

"

After that, please install Windows Server Essentials Experience role as original description. After installation completed, please use the following command to configure Windows Server Essentials:

Start-WssConfigurationService Credential <Your Credential>

Note: The type of Your Credential should be as: Domain-Name\Domain-User-Account. You must be a member of the Enterprise Admin group and Domain Admin group in Active Directory when using the command above to configure Windows Server Essentials. (Figure 5)

"

Marian

Like I said above, when I try the GUI Wizard it runs for about 2 seconds then fails. The logs are almost entirely populated with this error:

[3332] 141115.210552.3357: DeploymentService: No answer file found. Keep waiting.
[3340] 141115.210557.3514: DeploymentService: No answer file found. Keep waiting.
[3436] 141115.210602.3556: DeploymentService: No answer file found. Keep waiting.

For the powershell command, the command I'm entering is correct. Correct domain, correct username, correct password, and the user account I'm using is apart of all the typical admin groups (Enterprise, domain, etc etc)

I am having the same problem.  Any updates?

Is there anyone out there that can help with this issue?

This issue is still happening and I'm not sure what the issue is. If there is anyone who can assist on this issue, please let me know. We would like to use the features that are SUPPOSED to work with windows server 2012.

We are still experiencing this issue with the server installation. Reinstalling windows will NOT be a viable option for them.

So is there anyone available to help me with this issue, or is it going to be ignored?

I am afraid your box is in too bad a shape for volunteers. I would suggest you look at other support options for a quicker resolution.

http://support.microsoft.com/gp/support-options-for-business/en-us

There is a link from there for partner forums which may offer more in depth support or a paid option as well.

What part of the Wizard does it crash at?

Do you get to enter your company info?

Domain Admin info?

I start the wizard, it shows me a progress bar for about 5 seconds then tells me an error occurred. When checking the logs that correspond with that wizard, this message repeats a few dozen times:

[3332] 141115.210552.3357: DeploymentService: No answer file found. Keep waiting.
[3340] 141115.210557.3514: DeploymentService: No answer file found. Keep waiting.
[3436] 141115.210602.3556: DeploymentService: No answer file found. Keep waiting.

I'm not able to input any information in the wizard, I haven't even gotten past the first 5 seconds of it initializing before it fails.

OK,

Just re-reading your original post.

So you had done a migration, then enabled the experience role, which failed. Demoted the server (ie removing the domain, assuming the old DC was gone by then) this would have broken the domain trust, because the clients were no longer able to contact their DC. I am speculating here of course, but simply adding the essentials role with the same domain name, does not repair the domain trust - you would have to rejoin those clients to the domain - which you may have been trying to do with the connect software - but did you first drop them out to a workgroup?

In any case none of that explains the current issues getting the role configured.

Ill have to try and set this up in my lab!