Archive for the ‘Windows Server Essentials’ Category

Procedures for joining workgroup PCs to remote Server Essentials domain

First step with new computer setup: Create Local user on workstation – skip the OOBE, do not use Hotmail account to create user, instead select limited or no internet and then create local user account – say pcadmin.  Set password and continue on till you get to the desktop.

Connecting PC to the Essentials Server:

  1. Go to to download the connector tool to the workstation PC1
  2. Run connector software – what this does is install the certificate and the VPN connection to site which connects to the foo.local domain.
  3. The connector then joins the domain or at least once you’re connected, you can open: sysdm.cpl and join the domain manually.
  4. After joining the domain manually, DO NOT REBOOT.  The reason is because you want to cache the new user1 credentials onto the workstation before rebooting and “losing” the remote connection.  So you do two things 1) add user1 to local administrators group and 2) logon with user1 to workstation before you reboot – yes it will work.
    1. Open elevated cmd prompt.
    2. Type:  net localgroup administrators foo\user1 /add   – this adds user1 to Administrators group on PC1
    3. Type: runas /user:foo\user1 cmd.exe  <enter key>  – then type in password for user1
    4. This opens CMD prompt under user1 credentials which thereby creates user1 profile.
  5. Now you’re still connected to the VPN network so you can switch user and logon to PC1 with user1 creds
  6. Click start, then go to admin account and choose switch user.
  7. At logon prompt type foo\user1 with password – this will finish with user profile creation and cache password.  Also, best once at desktop to lock workstation and unlock again with password.
  8. Then reboot computer
  9. Try logging on with user1 to foo domain.
  10. If it fails, then go back to local Admin account on PC1 and reconnect the remotewebaccess VPN
  11. Then switch user again and proceed to setup rest of items – like outlook, files etc.

    Remotewebaccess VPN disconnects (Error 829)

    Client told me he couldn’t access the vpn to the office.  Would connect and disconnect and or any connection would only last a few seconds before disconnecting. Event log errors include Error 829.

    At first I thought it could be the server needed a reboot. Nope, wasn’t it.

    Looked at the RWA certificates on the server and did notice that the one that was being used expired today. Hmmm. So I checked IIS and looked at the Bindings for the Default Website – but the server had already bound the new RWA certificate to it. Still clients couldn’t connect.

    Looking further at the client event logs this is example of one of error messages:

    CoId={3AE1BD1D-CF91-4B7B-A93F-7A59705A1EF5}: The user WIN10TEST\username dialed a connection named which has terminated. The reason code returned on termination is 829. All this means is a disconnected session. Great no help there.

    Searched the web and found this bit of information:

    The RWA certificate set in IIS is also used by Routing and Remote Access Server Configuration – not for authentication but for maintaining secure TLS connection. So even though the IIS cert was updated, RRAS console doesn’t upgrade it automatically :(.

    Solution: Go to Routing and Remote Access snap-in, right-click on the properties of your router (MACHINE-NAME (local) properties in the tree-view to the left) select the Security Tab; you will be warned that there’s no TLS certificate selected (the previous has expired in my case) and select the certificate that has the next year’s expiration date – can select and then view them prior to saving. This will force a RRAS service restart. Thereafter clients can connect and remain connected :).

    Windows Server 20xx Essentials cannot connect to O365.

    I found this cheat to reset the connection between the Essentials Server Dashboard and O365.

    First check the log to find out why it’s failing.  Log file is found here:

    C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-EmailProviderServiceConfig.log

    If log looks something like the below, then follow steps to fix:

    BecWebServiceAdapter: Connect to BECWS failed due to known exception : System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused


    To fix:

    Open Regedit and navigate to the following key:

    HKEY_Local_Machine\Software\Microsoft\Windows Server\Productivity\O365Integration\Settings

    Delete the BecEndPointAddress key.

    Close Regedit and re-open the Essentials Dashboard.  Re-attempt to integrate with O365 and this time it should work.

    Reference Link:;