Installing-SQL-Server-2012-32.gif' alt='Install Oracle Client Windows Server 2012' title='Install Oracle Client Windows Server 2012' />Installation of Oracle 11gR2 64bit client on Windows 7 is even trickier compared to Oracle 32bit client installation. In fact after some series of installations, I. Powershell script to install Remote System Administration Tools RSAT features on Windows Server 2012 R2. As a reminder, the WebUpd8 Oracle Java PPA doesnt include any Java binaries, just a script that automatically downloads and install Oracle Java 8. Install Oracle Client Windows Server 2012' title='Install Oracle Client Windows Server 2012' />Direct. Access in Windows Server 2. In Windows Server 2. R2, installing and configuring Direct. Access is painful. It requires a very complicated setup process that involves meeting public key infrastructure PKI requirements, getting server certificates, setting up a network location server, making sure the targets support IPv. Forefront Unified Access Gateway UAG. That has all changed. In Windows Server 2. Direct. Access is simple if youre using Windows 8 clients. Before I describe the vastly improved setup process, Ill take a step back and tell you what Direct. Access is and how it can help your organization. What Is Direct. Access In my first job as a VAXVMS systems administrator, I got to the office at 8 0. Those were the hours I interacted with the work systems including email, and I never accessed the systems outside the office. Today, the concept of 8 to 5 office hours has disappeared, and the line between work and personal life has blurred. IT administrators and end users alike need to be able to access company systems and data all the time, so they always need connectivity. Related Articles Direct. Access Improvements in Forefront Unified Access Gateway SP1Q. What technologies does Direct. Access useQ. Is it true that Direct. Access only works with IPv. Q If Im implementing Direct. Locator Light Font. Access in my organization, can I drop my VPN solution. There are two traditional approaches for managing access to corporate systems from outside the corporate network. Access over web based protocols, such as HTTP Secure HTTPS. For example, this type of access is used for accessing Microsoft Exchange mailboxes over Active. Sync, accessing Share. Point sites that are published in a secure fashion to the web, and even using remote desktop connections by means of the Remote Desktop Gateway, which encapsulates the RDP traffic in HTTPS. VPN tunnels through the Internet between a machine and the corporate network. With this approach, users manually initiate a connection to the corporate network. Using HTTPS is a great solution when its available. It has the advantage of typically just working and is available on many different types of devices. However, the HTTPS approach doesnt work for many types of services, such as line of business LOB applications. And sometimes organizations dont want to use it, even if its a viable option. For these situations, the traditional VPN approach can be used. But this approach also has challenges. The users must manually initiate the connection, which can be complex. The users are connected to the corporate network infrastructure only when theyre in a VPN session. As a result, if the users dont connect often, their computers cant be managed for activities such as patching, policy updates, and software updates. To provide another option, Microsoft introduced Direct. Access in Server 2. R2 and Windows 7 Enterprise and Ultimate editions. Direct. Access enables an always on connection from the client to the corporate network, without any user action. When users are accessing an Internet resource, their regular Internet connection is used. When users are accessing a corporate resource, the Direct. Access tunnel is used, giving them transparent corporate resource access from anywhere. To determine whether the target is a corporate resource, Direct. Access compares the targets DNS suffix against a Name Resolution Policy Table. This table basically contains rules that identify the DNS suffixes that must communicate through the corporate intranet to be reachable. Although Direct. Access looks similar to a VPN in terms of creating a tunnel between the computer and the corporate environment, theres an important difference. Behind the scenes, there are actually two tunnels used with Direct. Access. The first tunnel is the infrastructure tunnel, which is established when the machine is turned on. It allows key IT infrastructure systems to talk to the machine and perform management. After a user logs on, a second tunnel is created. This intranet tunnel allows the user to access the systems on the corporate network. Because theres no user action required, the user can access corporate resources seamlessly. Note that its possible to use only the infrastructure tunnel for management and not the intranet tunnel, in which case users wouldnt be able to access the corporate resources. As you can see, Direct. Access is great for users, but its even better for the IT department. With Direct. Access, all the communications traveling across the Internet are authenticated and encrypted using IPSec, which gives users a seamless but highly secure connection from their machines to the corporate network. In addition, because users computers are connected to the key IT infrastructure systems whenever the users turn on their computers, its easy to manage those computers. Tetris Worlds Pc here. Direct. Access is built on IPv. Although the industry is certainly moving toward using IPv. Internet, are primarily using IPv. As a result, Direct. Access leverages IPv. Direct. Access server and those clients using IPv. Internet. The common transition technologies being used are Teredo and IP over HTTPS IP HTTPS, both of which allow the tunneling of IPv. IPv. 4. Technically, the 6to. However, 6to. 4 doesnt work when the client is behind a Network Address Translation NAT device. Because most Internet based clients are behind a NAT device of some kind, 6to. Direct. Access is a fantastic technology, but its highly unlikely that youll be able to get rid of your VPN solution. For example, Direct. Access in Server 2. Windows 8 Enterprise and Windows 7 Enterprise machines. For all other devicese. Enterprise editions of Windows 8 and 7, mobile phones, non Windows devicesyoull still need to leverage a VPN. I recommend that when you can use Direct. Access, use it. For everything else, youll need to continue to use a VPN. If youre struggling to understand the difference between a VPN and Direct. Access, Ive heard this summary The VPN connects the user to the network, whereas Direct. Access extends the network to the computer and user. Direct. Access in Server 2. To deploy a usable Direct. Access implementation in Server 2. R2, you really need to use the Forefront UAG. It provides a simpler setup experience and enables support for IPv. Server 2. 01. 2 includes all of Forefront UAGs technologies related to Direct. Access, such as DNS for IPv. IPv. 4 DNS6. 4 and Network Address Translation for IPv. IPv. 4 NAT6. 4. As a result, Direct. Access will work in a Server 2. Forefront UAG. Server 2. Remote Access. Through this role, you can manage Direct. Access and VPNs including site to site VPNs as a unified service. Server 2. 01. 2 also introduces multi site support and geographical awareness, which means you can have multiple Direct. Access deployments single servers or arrays at different locations, and clients will use whichever site is closest based on response time. The response time is determined using an HTTP probe that tests connectivity to all the Direct. Access deployments identified in its policy. If a site fails, clients will use the remaining Direct. Access deployments. Multi site awareness is a Windows 8 native capability. However, if you really need this capability for Windows 7 clients, there are ways to make it work to a certain extent. There are some constraints. If you have only Windows 8 clients, the requirement for a PKI is removed in Server 2.