Hi Team,
while troubleshooting Workfolders issues on Windows Server 2016 we noticed that the result of get-SyncUserstatus and also the users properties in server manager differs from what we see in the web for Windows 2012 R2.
It seems in Windows 2012 R2 get-SyncUserstatus will list some more details, like LastAttemtedSyny, LastSuccesfulSync etc.
see
https://blogs.technet.microsoft.com/filecab/2013/10/15/monitoring-windows-server-2012-r2-work-folders-deployments/
There are no such details in Windows 2016 Server.
One of our current problems is, that user getting just getting "Problem while connecting to server" (sorry had to translate from German)
and in
while troubleshooting Workfolders issues on Windows Server 2016 we noticed that the result of get-SyncUserstatus and also the users properties in server manager differs from what we see in the web for Windows 2012 R2.
It seems in Windows 2012 R2 get-SyncUserstatus will list some more details, like LastAttemtedSyny, LastSuccesfulSync etc.
see
https://blogs.technet.microsoft.com/filecab/2013/10/15/monitoring-windows-server-2012-r2-work-folders-deployments/
There are no such details in Windows 2016 Server.
One of our current problems is, that user getting just getting "Problem while connecting to server" (sorry had to translate from German)
and in
Microsoft-Windows-WorkFolders/Operational
Event ID 2100 "Error while connecting to server" error: (0x80072ee2)
That's basically means a timeout.
It seems to be temporally problem and occurs also when the machine is connected via LAN very well to the server.
the server log syncshare//Operational logs nothing at this time.
Is there another log on the server where we can see if the request arrived the server or not, such the w3svc log.
Thanks
Eckhard
Eckhard