Home
%3CLINGO-SUB%20id%3D%22lingo-sub-399073%22%20slang%3D%22en-US%22%3EWindows%20Server%20Essentials%202016%20%E2%80%93%20Update%20two%20on%20Remote%20Web%20Access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-399073%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20TechNet%20on%20Jun%2026%2C%202017%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20Hello%2C%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20An%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4019472%2Fwindows-10-update-kb4019472%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20update%20%3C%2FA%3E%20for%20the%20remote%20web%20access%20feature%20went%20live%20in%20May%20and%20so%20the%20workaround%20suggested%20%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fsbs%2F2017%2F04%2F17%2Fwindows-server-essentials-2016-update-on-remote-web-access%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20in%20this%20previous%20blog%20%3C%2FA%3E%20can%20be%20undone.%20Users%20will%20now%20be%20able%20to%20get%20to%20http%3A%2F%2Fservername%2Fremote%20or%20%3CA%20href%3D%22https%3A%2F%2Fservername.remotewebaccess.com%2Fremote%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fservername.remotewebaccess.com%2Fremote%3C%2FA%3E%20without%20errors%2C%20regardless%20of%20how%20long%20the%20server%20has%20been%20online.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Thanks%2C%20%3CBR%20%2F%3E%20Scott%20Johnson%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-399073%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TechNet%20on%20Jun%2026%2C%202017%20Hello%2CAn%20update%20for%20the%20remote%20web%20access%20feature%20went%20live%20in%20May%20and%20so%20the%20workaround%20suggested%20in%20this%20previous%20blog%20can%20be%20undone.%3C%2FLINGO-TEASER%3E
Microsoft
First published on TechNet on Jun 26, 2017
Hello,

An update for the remote web access feature went live in May and so the workaround suggested in this previous blog can be undone. Users will now be able to get to http://servername/remote or https://servername.remotewebaccess.com/remote without errors, regardless of how long the server has been online.

Thanks,
Scott Johnson