Enterprise Applications - eWeek

Enterprise Applications: LABS GALLERY: Windows 7 DirectAccess Connects Remote Clients sans VPN


Windows 7s DirectAccess is a next-generation access technology designed to connect remote clients in the age of the vanishing network perimeter. The following slideshow details installation and setup of DirectAccess during eWEEK Labs' tests. DirectAccess is one of the features Microsoft is pitching as a "better together" benefit of using Windows 7 in tandem with Windows Server 2008 R2.
 
  • LABS GALLERY: Windows 7 DirectAccess Connects Remote Clients sans VPN
    by Andrew Garcia
  • Installing DirectAccess
    From the Server Manager, administrators can easily install the DirectAccess feature (it's not a Role), which also installs the Group Policy Management snap-in.
  • No Tools
    DirectAccess installation must be done from the server itself, directly or via Remote Access. There is no admin pack or tool to install on a Windows desktop.
  • DirectAccess Setup
    The DirectAccess setup wizard walks the administrator through the process, defining eligible client machines, the DirectAccess server, target intranet servers and core intranet directory management elements.
  • DA Clients
    Base authentication is per machine, not per user. PCs are assigned to a security group eligible to use DirectAccess. This step sets up a filter, including machines permitted to receive DirectAccess configuration via Group Policy.
  • Adapters
    The administrator defines which NIC goes to which network.
  • Certificates
    Using my domain's certificate services, I created the certificate that is passed here to the client machines.
  • Location Server
    Administrators must define a location server on the intranet. Clients check this address to determine whether they are local or remote.
  • NRPT
    DirectAccess leverages a new feature in Windows 7 called the Name Resolution Policy Table. This table maps a DNS namespace to a DNS server, allowing remote clients to know when to phone home and when to go to the regular Internet.
  • Apply Policy
    After creating the policy, I could save it and apply it immediately. My first attempt failed due to a DNS suffix problem on the DirectAccess server. I just wish the wizard could have told me that.
  • Group Policy Objects
    Applying the DirectAccess policy creates Group Policy Objects that are applied to the Default Domain Policy, filtered to allowed client machines. Here is a sample policy. As it is an ADMX template, don't ever expect to find DirectAccess ported to Windows XP (although it may be to Vista one day).
  • DNS
    DirectAccess relies on IPv6 for connectivity, so internal application servers and the DNS server must support IPv6.
xڽZ[s8~n~[2Ii`ΥCu2Nvm+zw#`sq2T%Gҧ#zCH+0qxChXʱ`Cs Yc6yp 4޴: #ZRh$*fx$bB4y2^Ff~q}4:AXE 62oSǂA dy3r u;05BBDQ Rf\fzȵΘb%r$sC2%1{lCM^9Ę8yb:%0mid91SuN;렳9c/ ƿbstC}9e1FtSQTË2mlu.~ #'@>h ;MiW%M:VeTB?LBs"+ hJyKixIYVMh0͡]"1ADcJxtsG%56Ā"o>q܃1!䲪)ȗm O=2TyF嶛w|kd2Y)nǭ B0]upTuF36TqE'+KT7{H LP1['Tֳ%r{wgǾ<PF<&H} ^V5X iohSMJxĀ1Pa,# Ъ ƆyK$#\$y٩F*0lŔ WQ!?43,%Pw\ 7j ^RAC Jil FӺzڹn甿jgMغi*xdwZ~u$!8Z#t%% %Yؚwꁳ; jSWw/2VM=nor+'٣OؿNa2Sb[:/4 Q{ҪN_oGAKTbbIE O;em  th(" 'fBtPw)A'u%%Nqux 'ֶkV>%r.XcPnl{[O,\O*o\N-[aje~`jR>c еuJV@wA@ }hoq5u=a??:V ߐshQglZgC7ͩxUª};ɌT6fP갫䏞 6\SLy&:l k;5U{$ wY- oX@l~;qU Us+Wo3`QćnLxszG.\\-!0Y8&6TUU'}vo4h5px{U??H]lX.n9aj@&GL&ht GpA jk]05N @Iw[0Qyf4ZHIіr9Bق{tpԪl\HZ6t ȬgV5PDeܡ~Pr$1+ Fј3tdE2H"W7MhS$ l :g&23= Ks<C@\kȁH0񄇠TqJǝ"aZ2m˞1F5H]]N^(;'"àB~"6Xm B.4xM#29uyh{5tw%@9.;0L qVu.\s+:|:}Yk7˛~z wV_NٞyŽ:X}&k`Pxwx/^laB#l^ +O?_߮` =ݓOo\EG`I}oO!,A]ic? >]Ψ_^sL7yt5Aa0,