W
Wayne2019
Hi,
I had a problem when I configured Windows Server Essentials Experience role on Windows Server 2016 Standard (running as virtual machines). If I click Configure button of the post-deployment configuration wizard, the fail message jumped up immediately every time like below,
"Please restart the server, and then run the configuration wizard again. If the issue still exists please refer to the help link for more troubleshooting steps."
There are two windows server 2016 standard VMs in my environment which exist in different network segment and both need to install essentials experience role. Because it stuck at very beginning (0%) every time, I think there are two possible reasons: (1) the service WseMgmtSvc is down; (2) or log on account problem.
1. When I installed this role on the Domain Controller, it worked successfully only if I added the ServerAdmin$ account into the Policy: "Log on as a service" under the Default Domain Controller Policy; < I use the account Administrator to login to this OS >
2. The second windows 2016 is used as a member in this domain (no AD installed, and still use the same domain user account "Administrator" to login). But at this time, when I run the post-deployment configuration wizard after installation, the above failed message will be given. Then I found that windows created a new service account ServerAdmin1$ on the Active Directory. If I add this new service account to the "Log on as a service" policy on the DC, it cannot work at this time!
Can someone help explain this for me or give me some advice to solve this problem?
Thanks in advance!
Continue reading...
I had a problem when I configured Windows Server Essentials Experience role on Windows Server 2016 Standard (running as virtual machines). If I click Configure button of the post-deployment configuration wizard, the fail message jumped up immediately every time like below,
"Please restart the server, and then run the configuration wizard again. If the issue still exists please refer to the help link for more troubleshooting steps."
There are two windows server 2016 standard VMs in my environment which exist in different network segment and both need to install essentials experience role. Because it stuck at very beginning (0%) every time, I think there are two possible reasons: (1) the service WseMgmtSvc is down; (2) or log on account problem.
1. When I installed this role on the Domain Controller, it worked successfully only if I added the ServerAdmin$ account into the Policy: "Log on as a service" under the Default Domain Controller Policy; < I use the account Administrator to login to this OS >
2. The second windows 2016 is used as a member in this domain (no AD installed, and still use the same domain user account "Administrator" to login). But at this time, when I run the post-deployment configuration wizard after installation, the above failed message will be given. Then I found that windows created a new service account ServerAdmin1$ on the Active Directory. If I add this new service account to the "Log on as a service" policy on the DC, it cannot work at this time!
Can someone help explain this for me or give me some advice to solve this problem?
Thanks in advance!
Continue reading...