Running Windows Server Essentials 2012 R2 and received critical error that Pre-Defined Folders are missing.  Look in Dashboard shows several folders missing such as Company & Users as well as a couple I created.  Client Computers, File History and Folder Redirect are present and correct.  Look at D:\ServerFolders and the missing Folders are present with data. 

When I attempt to recreate the folder, I receive an error "Make sure the DFS service is running and try again".

DFS Service is running.

Any ideas how to restore the missing folders in the Dashboard?

Hi,

I am looking to redirect all folders, company, client backups, file history, etc to a Nas on my network.  I believe there is a GPO i can edit to do it but I dont know where to look to make that change.

Any help would be great - I am aware this isnt recommended.

Thanks,
Rich

I am currently running Windows Server 2012 R2 Essentials. It's a small box and there is not much room for expansion. I also have a Synology DS1815+ on the network which handled all of the network storage on the network so far. 

I can't seem to figure out how I can add a network share from the DS1815+ to the Server Folders or Shared Folders on server box. If i go to the Dashboard under storage and server folders to add a share it refuses. 

I also tried to add the network share to DFS which works but it still won't let me add it to the Server Folders. 

I am a little puzzled as to why Server Folders and Shares require a drive letter.

p.s. 

The DS1815+ does a fine job but people got sometimes confused to where their stuff is actually saved so I wanted to re-share the folders on the windows server to have it at least logically appear in one location. 

Another reason is Windows Server Essentials Media Pack. I installed it and tested it and it works fine; however, again I am limited on space on the server so I would like to be able add the network shares to the Server Folders so i can include them in the media library.

You can either be part of the problem or be part of the solution.

I'm setting up a network server for our office. 6 computers running windows 10 pro have connected to the server without issue. 

One computer, however, won't. I'd first installed a trial of Windows 10 Enterprise and the connection worked fine. After reinstalling windows 10 Home, and then Upgrading to 10 Pro, the connector wizard has an unknown error at the end of the process and then the only option is to close.

Running the connector utility does no good. Other than to sometimes say that the computer is already connected.

Is there a link to an article on how to manually configure the Shared server folder?

Hi

I have Created Step by Step Video on How to install Anywhere Access (Remote Web Access) on Windows Server 2012 Essentials and want to share

http://www.youtube.com/watch?v=aXBiV3pQrLg

Thanks

I'm trying to get a connection from a Windows 10 client to my Server Essentials 2012 R2 server. When I try to connect I receive the error message: "The revocation function was unable to check revocation because the revocation server was offline."

How can I fix this?

Thanks

Hi, so while it has certainly been a rocky road, windows 10 is working fine on all the desktops in the office. WIN!

whats NOT WORKING is anyone that has a laptop and wants to work remotely.

right now no laptop that connects with the WSE Connector and has it 'green' can see or access any of the files stored on the server that are part of 'Shared Folders'. this is crippling our company right now and is making me think of rolling everyone back to windows 7!

please help. nothing has changed in the router or access setup topology. remote desktop works fine and thats what everyone is having to use right now, but its painful and now how it should be.

Windows 10 is not an upgrade right now, its a big step backwards!

I am unable to connect my desktop PC which is running Windows 10 to Windows Server 2012 Essentials R2.

I downloaded and ran the latest patch for the Connecter Wizard -- several times actually. It gives me the sign on page, and after signing on "thinks" for a long time, then gives me a message that says "Cannot connect this computer to the network","The server is not available. Try connecting this computer again.".  I tried signing on both with my administrator ID and my desktop ID, with the same results.

Windows Server is running on an HP ProLiant MicroServer.  I have other systems running Windows 7 and Windows 8 connected in OK.

My desktop, back before I upgraded it from Windows 7 to Windows 10, had successfully been connected to another server running Windows Server 2003, using the same router, etc.  My desktop is able to access all other network resources like stand-alone hard drives, printers, other PC's, etc. with no problems.

I have tried rebooting everything as well, with the same results.

Any suggestions?

Thanks

After reinstalling Anywhere Access in Windows Server 2012 R2 Essentials seems to be working better than it did... but... when logging into cisco dpc3939b router, the IP keeps changing from reserved IP 10.1.10.2 to 10.1.10.194 after server boots up and starts doing its thing???

It is set static on the server (router is handling DHCP, not server).

If i check right after server starts, shows proper static .2 IP in the router setup, but give it a few minutes, shows .194 ip again in router?

Is WS12ER2 making the router change to .194? Is the remote Anywhere Access making this change? Once this happens, i cannot select the .194 and change to .2 reserved in the router?

Thank you. 
Tim

EDIT:

When installing Anywhere Access, I let it set up the router itself using UPnP and was successful... It seemed to work even though in the router Poert forwarding wasn't even enabled?  I saw the dimmed entries added for port 80 and 443.  But now port 443 is GONE????  what the?  Does UPnP allow the server to change things when it wants or needs to?

I didn't remove the port 443?  only port 80 is left??? 

After installing Anywhere Access in Windows Server 2012 Essentials R2, I cannot use Anywhere Access using the setup domain name in the wizard such as remote.mydomain.com?

If I enter the public ip address, for example, 72.2.34.5 it works.

Before I set up Anywhere Access, I created a A record pointing to this public address...pinged and that worked...so not sure what I am doing wrong?  Is the wizard supposed to already create that A record etc and just make this remote.mydomain.com just work?

Also if I enter the public ip address while on the lan, it takes me to the router webpage.  Shouldn't it also work on the LAN as if it was accessed via public ip?

Thank you, Tim.

I have a new Server 2012 Essentials and am stuck on setting up client PCs. They are all giving the same error in the ClientDeploy.log:

[5388] 160220.210257.5998: ClientSetup: Start of ClientDeploy
[5388] 160220.210257.7958: General: Initializing...C:\Windows\Temp\Client Deployment Files\ClientDeploy.exe
[5388] 160220.210257.8148: ClientSetup: Loading Wizard Data
[5388] 160220.210257.8839: ClientSetup: Current DeploymentStatus=Running
[5388] 160220.210258.3439: ClientSetup: Showing the Client Deployment Wizard
[5388] 160220.210258.5209: ClientSetup: Adding Server Info data in the Product Registry
[5388] 160220.210258.5459: ClientSetup: Set the Deployment Sync Event
[5456] 160220.210304.1895: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred
[5456] 160220.210304.1985: ClientSetup: Entering ConnectorWizardForm.RunTasks
[5456] 160220.210304.1995: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask
[5456] 160220.210304.2045: ClientSetup: Entering InstallRootCertTask.Run
[5456] 160220.210304.2085: ClientSetup: Install root cert to local trusted store
[5456] 160220.210304.2175: ClientSetup: Exiting InstallRootCertTask.Run
[5456] 160220.210304.2175: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success
[5456] 160220.210304.2175: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot
[5456] 160220.210304.2175: ClientSetup: Exting ConnectorWizardForm.RunTasks
[5456] 160220.210304.2175: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred
[5456] 160220.210304.2185: ClientSetup: Entering ConnectorWizardForm.RunTasks
[5456] 160220.210304.2195: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask
[5456] 160220.210304.2275: ClientSetup: Entering SetupVpnAndDATask.Run
[5456] 160220.210304.2455: ClientSetup: Exting SetupVpnAndDATask.Run
[5456] 160220.210304.2455: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Success
[5456] 160220.210304.2455: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot
[5456] 160220.210304.2455: ClientSetup: Exting ConnectorWizardForm.RunTasks
[5456] 160220.210304.2455: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
[5456] 160220.210304.2465: ClientSetup: Entering ConnectorWizardForm.RunTasks
[5456] 160220.210304.2475: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
[5456] 160220.210304.2535: ClientSetup: Entering ValidateUserTask.Run
[5456] 160220.210304.2535: ClientSetup: Validating User
[5456] 160220.210304.2535: ClientSetup: Call MachineIdentityManager.GetMachineStatus
[5456] 160220.210305.4086: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:ProviderNotAvailable ErrorCode:-1
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)
[5456] 160220.210305.4096: ClientSetup: Exiting ValidateUserTask.Run
[5456] 160220.210305.4096: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed
[5456] 160220.210305.4096: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
[5456] 160220.210305.4096: ClientSetup: Exting ConnectorWizardForm.RunTasks
[5388] 160220.210305.4176: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed
[5388] 160220.210307.2308: ClientSetup: Back from the Client Deployment Wizard
[5388] 160220.210307.2378: ClientSetup: Saving Wizard Data
[5388] 160220.210307.2458: ClientSetup: End of ClientDeploy: ErrorCode=1603

Any help is greatly appreciated.  Thank you.

VFRider

Dear All,

We have installed a Windows Server 2012 Essentials and would like to synchronise local file shares with our OneDrive for Business account. The "OneDrive for Business sync Client" works just fine, however, only when one logs onto the Essentials server or when installed on a client PC. We require a tool which runs as a service on the Essentials server and syncs local shares with our OneDrive for Business account. Any ideas?

Many thanks for your help.

Regards, Oliver

I haven't touched my server in a long time besides applying updates and Plex.  For some reason, the last two weeks the dashboard has been crashing / will not stay open. 

Anyone know why this may be occurring?

We have a 2012 essentials which has been shutting down every 30 days due to licensing. It is not breaking any of the licensing it is a stand alone server doing files & AD for 8 people.

I believe the issue is specifically with an error the licensing service gets: "Not enough storage is available to process this command."

There is heaps of storage on both drives really stuck as to what is causing this. Event log below.

Log Name:      Microsoft-Windows-Server Infrastructure Licensing/Operational

Source:        Microsoft-Windows-Server Infrastructure Licensing

Date:          11/02/2016 3:21:51 PM

Event ID:      50

Task Category: None

Level:         Error

Keywords:     

User:          SYSTEM

Computer:      ####

Description:

Root domain check did not pass because error 0x80070008 occurred in function f1980 [JQOH].

Not enough storage is available to process this command.

Make sure that the domain that this computer is joined is reachable. This server will automatically shut down if the issue cannot be corrected.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Server Infrastructure Licensing" Guid="{D459C229-4A00-4424-9F63-7325E5AAFA21}" />

    <EventID>50</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2016-02-11T04:21:51.163640900Z" />

    <EventRecordID>32051</EventRecordID>

    <Correlation />

    <Execution ProcessID="3052" ThreadID="6636" />

    <Channel>Microsoft-Windows-Server Infrastructure Licensing/Operational</Channel>

    <Computer>#####</Computer>

    <Security UserID="S-1-5-18" />

  </System>

  <UserData>

    <LicensingEvent xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://schemas.microsoft.com/win/2004/08/events/WindowsServerSolutions/LicensingComplianceService/1.0">

      <ErrorCode>0x80070008</ErrorCode>

      <Function>f1980 [JQOH]</Function>

      <Message>Not enough storage is available to process this command.

</Message>

    </LicensingEvent>

  </UserData>

</Event>

Hi,

I have a problem with a new  Windows Server 2012 Essentials R2 install. I am having problems with RWA/Anywhere access.

Here is some useful info

Windows Server Essentials 2012 R2 is at IP 192.168.1.3

Router is a sonicwall TZ100W GW= 192.168.1.1

Customer Portal PC is in a DMZ  192.168..10.9

I am making up a domain name to protect customer.  www.clubexample.com

We have a GoDaddy SSL Cert for remote.clubexample.com

Here is Problem:

There is an existing use of HTTPS port  443 box for a customer portal pc. With old setup. So all traffic for https port 443 is forwarded to Customer Portal PC @ 192.168.10.9.

So in the sonicwall have setup rule that all traffic for port 446 be sent to port 443 on the Windows Server Essentials R2 @ 192.168.1.3.

This  done with a link for remote user like this.

https:/remote.clubexample.com:446/remote

We get to RWA login and are able to login.  We get the launch pad for Devices/Shared Folders/Links.

Everything works right except Devices when we click on pc to access. We get:

Window: Remote Desktop Connection

Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address requested and the certificate subject name do not match. Contact your network administrator for assistance.

View certificate shows a  a GoDaddy Certificate issued to:

members.clubexample.com

I assume this is the customer portal in DMZ?

Side Note:

If customer portal is disabled and port 443 is sent to normal location at WSE it works fine.

Any ideas?

Thanks

Dexter  Southerland  

Server Error in '/imageright.web.client' Application.

An existing connection was forcibly closed by the remote host

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[SocketException (0x2746): An existing connection was forcibly closed by the remote host]
   System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult) +147

[IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.]
   System.Net.TlsStream.EndWrite(IAsyncResult asyncResult) +8277683
   System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar) +213

[WebException: The underlying connection was closed: An unexpected error occurred on a send.]
   System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context) +3365149
   System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar) +155

[HttpRequestException: An error occurred while sending the request.]
   System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +144
   System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +84
   System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() +49
   ImageRight.Web.Client.Services.<Validate>d__0.MoveNext() +672
   System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +144
   System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +84
   ImageRight.Web.Client.Services.<Authenticate>d__0.MoveNext() +333
   System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +144
   System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +84
   ImageRight.Web.Client.Controllers.<LogIn>d__4.MoveNext() +481
   System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +144
   System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +84
   System.Web.Mvc.Async.TaskAsyncActionDescriptor.EndExecute(IAsyncResult asyncResult) +143
   System.Web.Mvc.Async.<>c__DisplayClass37.<BeginInvokeAsynchronousActionMethod>b__36(IAsyncResult asyncResult) +23
   System.Web.Mvc.Async.AsyncInvocationWithFilters.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3d() +112
   System.Web.Mvc.Async.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f() +452
   System.Web.Mvc.Async.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f() +452
   System.Web.Mvc.Async.<>c__DisplayClass33.<BeginInvokeActionMethodWithFilters>b__32(IAsyncResult asyncResult) +15
   System.Web.Mvc.Async.<>c__DisplayClass2b.<BeginInvokeAction>b__1c() +37
   System.Web.Mvc.Async.<>c__DisplayClass21.<BeginInvokeAction>b__1e(IAsyncResult asyncResult) +241
   System.Web.Mvc.Controller.<BeginExecuteCore>b__1d(IAsyncResult asyncResult, ExecuteCoreState innerState) +29
   System.Web.Mvc.Async.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult) +111
   System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) +53
   System.Web.Mvc.Async.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult) +19
   System.Web.Mvc.MvcHandler.<BeginProcessRequest>b__5(IAsyncResult asyncResult, ProcessRequestState innerState) +51
   System.Web.Mvc.Async.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult) +111
   System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +282

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34274

The standard VPN config (through the AnyWhere Access wizard on the Essentials R2 Server) is to use split tunnel VPN. Our clients can connect using the wizard generated VPN connection fine. Local resources can be accessed and internet traffic is routed through the users local internet connection.

We understand the pros and cons of split and single tunnel VPN. When checking the box on clients "use default gateway on remote network" to effectively force internet traffic down the VPN tunnel clients loose internet access and fall into a limited connectivity state.

Question: We have installed the RRAS manager on the Essentials R2 server so we can see the settings which are normally hidden in Essentials to prevent tampering. What changes do we need to make to facilitate "use default gateway on remote network" so clients can browse the internet with this option checked?? Gut feel is this is a routing table issue but this area is not my bag. IP of router: 192.168.16.1. IP of server: 192.168.16.2. Default RRAS config is to use DHCP to assign VPN addresses rather than a static pool. Maybe something to do with this? DHCP is dished out by the Essentials R2 Server and not our router.

I have a client that I did a SBS 2008 migration to Server 2012 R2 and installed the "Server Essentials Experience" role.

For the most part everything has been fantastic! Although I just recently discover something that I need to address.

I have been configuring manually the VPN connections for users to connect to the company, however I just recently found out that Server Essentials actually auto-configured a VPN connection on client machines.

Normally this would be great, however the auto-configured VPN connection doesn't enable the "Use default gateway on remote network", and I need this setting enabled as the company is protected by a enterprise grade firewall that does active scanning on web traffic and a whole bunch of other stuff.

Is there a way to modify the provisioning of the auto-configured VPN connections to check the checkbox and enable "Use default gateway on remote network", or do I need to manually tick this box on each remote user?

Thanks in advance!

The new Client Connector for Windows 10 overwrites saved user credentials on non-domain joined computers, breaking the user experience. This is different than the behavior on Windows 8.1.

Normally when one logs into the Connector on a non-domain joined PC, a credential is created with session persistence, and is deleted when the session ends.  However, if a user-supplied credential existed in Windows Credential Manager prior to Windows 10, the Connector would skip creating its own session credential and simply log the user in seamlessly.

One assumes this is the correct behavior, as Windows has always allowed users to persist saved credentials for server shares. And as the 2012 R2 Connector does not have its own mechanism for saving passwords, this provided an effective work-around to provide a seamless experience on non-domain joined computers.

The new Windows 10 Connector, however, always overwrites user-supplied credentials with its own session-level credential anytime a user logs into it. This seems like unintended behavior, as it breaks the seamless user experience, since the next time the user logs into their computer they will no longer have access to remote shares.  In fact, the only way to protect a user-supplied credential to access the server is to prohibit users from logging into the Connector altogether.

I would like to understand if this was an intended change or merely a bug?  As it is, it is a rather large regression from the behavior in Windows 8.1. Thanks for listening.