Bit late to the party . DA is great, I use it all the time, I set it up many
months ago with that 2nd link from MSDN, simples. 

 

I just read over Gerry's PDF and it is pretty well laid out, easy to follow,
very nice Gerry!

 

Robert

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Kent, Mark
Sent: 19 September 2014 13:51
To: [email protected]
Subject: RE: [mssms] RE: OT: DirectAccess

 

Thanks all for the input!

 

Mark Kent (MCP)

Sr. Desktop Systems Engineer

Computing & Technology Services - SUNY Buffalo State

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Atkinson, Matt
Sent: Wednesday, September 17, 2014 6:05 PM
To: [email protected] <mailto:[email protected]> 
Subject: RE: [mssms] RE: OT: DirectAccess

 

I used this guide to build a proof of concept at my last employer:

http://blogs.msdn.com/b/canberrapfe/archive/2012/07/12/simple-direct-access-
setup-with-windows-server-2012-rp.aspx

 

Followed the Windows 7 steps verbatim and it was a piece of cake. Everything
worked as advertised, the only thing I didn't get working was
monitoring/status of connected clients in the console. Windows Firewall was
disabled in the default domain policy (don't do this) which was why the
client worked but never showed in the console as active. Never worked past
that problem as the whole thing got shot down once we learned that we would
have to use something like OTP for 2 factor auth due to regulatory reasons.

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Gerry Hampson
Sent: Wednesday, September 17, 2014 1:23 PM
To: [email protected] <mailto:[email protected]> 
Subject: Re: [mssms] RE: OT: DirectAccess

 

Just a little more involved - requires PKI. Implement the solution and test
on Windows 8 first. Then add the Windows 7 piece.

 

-------- Original message --------

From: "Kent, Mark" 

Date:17/09/2014 21:06 (GMT+00:00) 

To: [email protected] <mailto:[email protected]>  

Subject: [mssms] RE: OT: DirectAccess 

 

Most of our clients are Windows 7, are they a headache to setup or just a
little more involved compared to Win8?

 

Mark Kent (MCP)

Sr. Desktop Systems Engineer

Computing & Technology Services - SUNY Buffalo State

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Gerry Hampson
Sent: Wednesday, September 17, 2014 4:01 PM
To: [email protected] <mailto:[email protected]> 
Subject: [mssms] RE: OT: DirectAccess

 

It's a fantastic technology and works pretty much out of the box for Windows
8. Windows 7 is a little more involved and requires certificates for the
second factor of authentication.

 

I have a guide to implementing DirectAccess here. It's reasonably
straightforward.

 

http://gallery.technet.microsoft.com/Implement-Direct-Access-a7c085b1

 

Gerry

 

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Kent, Mark
Sent: 17 September 2014 20:56
To: [email protected] <mailto:[email protected]> 
Subject: [mssms] OT: DirectAccess

 

For those that use this, has it been a good/bad experience?  Logistical
nightmare?  Is it a lot more involved to set up on Windows 7 clients as
compared to Windows 8 clients?  Appreciate any opinions, thanks!

 

Mark Kent (MCP)

Sr. Desktop Systems Engineer

Computing & Technology Services - SUNY Buffalo State

 

 

 

 

 

 

  _____  


This message is intended for the sole use of the addressee, and may contain
information that is privileged, confidential and exempt from disclosure
under applicable law. If you are not the addressee you are hereby notified
that you may not use, copy, disclose, or distribute to anyone the message or
any information contained in the message. If you have received this message
in error, please immediately advise the sender by reply email and delete
this message.

 

 



Reply via email to