locked
[Forum FAQ] Introduction and FAQ for the Windows Server Essentials Experience role RRS feed

All replies

  • Frequently Asked Questions


    Q1:
     Do we need to setup Active Directory before install the Windows Server Essentials Experience role?

    Answer: No, we don’t.


    1. Environment with Activity Directory domain already exists

    You can install the Windows Server Essentials Experience role in an environment with Activity Directory domain already exists. The server does not have to be a domain controller.

    Please note: When we enable the Windows Server Essentials Experience role on a member server, we need to type user name and password as Figure 2. Please make sure that the user account is the member of the Enterprise Admin group, Domain Admin group and Local Admin group on the target server (Figure 3).

    Figure 2: Type user name and password

    Figure 3: Check privilege

    2. Environment without pre-existing Active Directory domain

    When install the Windows Server Essentials Experience role on a Windows Server 2012 R2 Standard/Datacenter, it will create an Active Directory domain. This server (with Windows Server Essentials Experience role installed) will become the domain controller and hold all the FSMO roles.

    Please note:The Windows Server Essentials Experience role can only be deployed into a single domain. Also, a read-only domain controller cannot exist in this domain.

    More information:

    Deploying Windows Server 2012 R2 Standard/Datacenter with Windows Server Essentials Experience role in an Existing Active Directory Environment

    Deploying Windows Server 2012 R2 Essentials in an Existing Active Directory Environment


    Q2: Can we remove the Windows Server Essentials Experience role?

    Answer: Yes, we can. However, we need to note the following.


    1. Please use Clean up Windows Server Essentials wizard to clean up firstly. Then use Remove Roles and Features Wizard to remove the Windows Server Essentials Experience role. Otherwise, the following error may occur (Figure 4).

    Validation Results

    The validation process found problems on the server from which you want to remove features. The selected features cannot be removed from the selected server. Click OK to select different features.

    Your server has been configured with Windows Server Essentials. Please run the clean up task prior to removing Windows Server Essentials.

    Figure 4:  Error when you remove the feature

    2. If you want to install the role again, you may also need to remove Certification Authority. Otherwise, when you add the Windows Server Essentials Experience role via Add Roles and Features Wizard successfully, you will not be able to complete Post-deployment Configuration task (Configure Windows Server Essentials) (Figure 5).

    Configure Windows Server Essentials

    Pre-requisites verification

    The following issues have been identified. You need to resolve the issues before continuing. You can click Retry after Resolving the issues. Please see the help to resolve the issues.

    Issue detected

    Certification Authority has been installed on this server

    Figure 5: Error when you configure Windows Server Essentials

    Please note:when remove Certification Authority, please remove Certification Authority Web Enrollment firstly. Then remove Certification Authority (Figure 6).

    Figure 6: Remove Authority Web Enrollment firstly


    Q3: What can we do if the Post-Deployment Configuration task fails?


    If you configure “Log on as service” group policy setting in the domain environment, and then start Post-deployment Configuration task (Configure Windows Server Essentials). You may encounter the following issue (Figure 7).

    Configuration encountered some issues

    Please Click Retry. If the issue still exists, please refer to the help link for more troubleshooting steps.

    Figure 7: Configuration encountered some issues


    Answer: Please refer to the solution/workaround below.


    1. Open Event Viewer, there will be some Event 7041 related errors (Figure 8).

    Event ID: 7041

    Source: Service Control Manager

    Level: Error

    The WseMgmtSvc service was unable to log on as domain.com\account& with currently configured password due to the following error:

    Logon failure: the user has not been granted the requested logon type at this computer.

    Figure 8: Event ID: 7041; Source: Service Control Manager

    To resolve the issue:

    1) If the “Log on a service” setting is not required in your domain, you can set it to Not Defined. After that, you may able to complete Post-deployment Configuration task (Configure Windows Server Essentials).

    2) If the “Log on a service” setting is required, logon DC as Administrator, configure and add contoso.com\ServerAdmin$. Then click Check Names (Figure 9).

    Figure 9: Log on as a service

    After adding, we can complete Post-deployment Configuration task successfully.

    Cause: While the Post-Deployment Configuration task is running, the Windows Server Essentials Management Service is configured to use the ServerAdmin$ account to log on as a service and perform the task. After the Essentials Configurations are complete, the service is configured to use the Local System account. Similarly, the Windows Server Essentials Media Streaming Service is configured to use the MediaAdmin$ account.

    For more details, we can refer to the KB article below.

    The Post-Deployment Configuration task may fail after you install the Windows Server Essentials Experience role on Windows Server 2012 R2

    2. If you do not have the pre-existing Activity Directory domain, when install Windows Server Essentials Experience role on a Windows Server 2012 R2, the server will become a Domain Controller. However, when you start Post-deployment Configuration task (Configure Windows Server Essentials), you may also encounter the same issue as above.

    Meanwhile, you cannot add ServerAdmin$ or MediaAdmin$ into “Log on as a service”. Error occurred as Figure 10. And if you set “Log on a service” setting as Not Defined, you still cannot complete the Post-deployment Configuration task.

    Figure 10: Cannot add ServerAdmin$ or MediaAdmin$

    Then, you can try the following as a workaround.

    1. Use Clean up Windows Server Essentials wizard to clean up.
    2. Use Remove Roles and Features Wizard to remove the Windows ServerEssentials Experience role.
    3. Use Remove Roles and Features Wizard to remove Certification Authority Web Enrollment firstly. Then remove Certification Authority.
    4. Then use Remove Roles and Features Wizard to add the Windows Server Essentials Experience role again.
    5. Now, you will be able to add ServerAdmin$ or MediaAdmin$ into “Log on as a service”. And complete Post-deployment Configuration task (Configure Windows Server Essentials).

    If you still encounter issues with Windows Server Essentials Experience role, please check Event Log and collect detailed error message. Then post in our Windows Server 2012 Essentials forum. It may help us to understand your problem clearly and then provide better assistances.


    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    • Edited by ForumFAQ Monday, March 31, 2014 1:45 PM Edit
    Monday, March 31, 2014 1:42 PM
  • Which Clean Up wizard is referenced in this article?  I can only find the WSUS Clean Up Wizard. Not sure that is the correct one....

    Thank you in advance for your assistance!

    -Wayne

    Thursday, October 16, 2014 10:16 PM
  • Hi Wayne,

    Before going further, would you please let me confirm whether there has a Windows Server 2012 R2 Standard (or Datacenter) with Windows Server Essentials Experience role installed?

    Based on your description, I understand that you want to uninstall the Windows Server Essentials Experience role.

    à Which Clean Up wizard is referenced in this article?

    I guess that you mean the Clean up Windows Server Essentials wizard which come from this description:

    Please use Clean up Windows Server Essentials wizard to clean up firstly. Then use Remove Roles and Features Wizard to remove the Windows Server Essentials Experience role.

    When want to uninstall Windows Server Essentials Experience role, please un-check the role in Remove Roles and Feature Wizard. Then you will be able to find the result as below picture shows.

    When click “Run Windows Server Esssentials Clean up”, the “Clena up Windows Server Essentials” panel will apprear as below picture shows.

    By the way, if has some updates of this issue, I suggest that you should separate the question to a new thread. It will be a better option that help us to go further analyze.

    Hope this helps.

    Best regards,

    Justin Gu

    • Edited by Justin Gu Friday, October 17, 2014 5:49 AM
    Friday, October 17, 2014 5:15 AM