1. Microsoft Access On Mac
2. Microsoft Direct Access Client For Mac Pro

Jan 12, 2010 DirectAccess, Microsoft's pairing of Windows 7 and Windows Server 2008 R2 for connect-anywhere access, is possibly the best thing Redmond has produced in a long time. Unfortunately for many, it. Dec 21, 2012 Operating Systems that can be DirectAccess client computers: Windows 7 Ultimate Windows 7 Enterprise Server 2008 R2 Windows 8 Enterprise Server 2012. I also have a number of customers running it on Mac:) Not to be misleading - what they are actually doing is running bootcamp or one of the other virtualization technologies on a Mac, basically using Mac hardware to run a Windows 7 instance.

DirectAccess, also known as Unified Remote Access, is a VPN-like technology that provides intranet connectivity to client computers when they are connected to the Internet. Unlike many traditional VPN connections, which must be initiated and terminated by explicit user action, DirectAccess connections are designed to connect automatically as soon as the computer connects to the Internet. DirectAccess was introduced in Windows Server 2008 R2, providing this service to Windows 7 and Windows 8 'Enterprise' edition clients. In 2010, Microsoft Forefront Unified Access Gateway (UAG) was released, which simplifies^[1] the deployment of DirectAccess for Windows 2008 R2, and includes additional components that make it easier to integrate without the need to deploy IPv6 on the network, and with a dedicated user interface for the configuration and monitoring. Some requirements and limitations that were part of the design of DirectAccess with Windows Server 2008 R2 and UAG have been changed (see requirements below). While DirectAccess is based on Microsoft technology, third-party solutions exist for accessing internal UNIX and Linux servers through DirectAccess. With Windows Server 2012, DirectAccess is fully integrated into the operating system, providing a user interface to configure and native IPv6 and IPv4 support.^[2]

Technology[edit]

DirectAccess establishes IPsec tunnels from the client to the DirectAccess server, and uses IPv6 to reach intranet resources or other DirectAccess clients. This technology encapsulates the IPv6 traffic over IPv4 to be able to reach the intranet over the Internet, which still (mostly) relies on IPv4 traffic. All traffic to the intranet is encrypted using IPsec and encapsulated in IPv4 packets, which means that in most cases, no configuration of firewalls or proxies should be required.^[3] A DirectAccess client can use one of several tunneling technologies, depending on the configuration of the network the client is connected to. The client can use 6to4, Teredo tunneling, or IP-HTTPS, provided the server is configured correctly to be able to use them. For example, a client that is connected to the Internet directly will use 6to4, but if it is inside a NATed network, it will use Teredo instead. In addition, Windows Server 2012 provides two backward compatibility services DNS64 and NAT64, which allows DirectAccess clients to communicate with servers inside the corporate network even if those servers are only capable of IPv4 networking. Due to the globally routable nature of IPv6, computers on the corporate network can also initiate a connection to DirectAccess clients, which allows them to remotely manage (Manage Out) these clients at any time.^[4]

Benefits[edit]

DirectAccess can be deployed for multiple sites. It allows for a secure encrypted VPN. This is controlled through Group Policies which allows the administrator to maintain a secure network.

Requirements[edit]

DirectAccess With Windows Server 2008 R2 or UAG requires:

• One or more DirectAccess servers running Windows Server 2008 R2 with two network adapters: one that is connected directly to the Internet, and a second that is connected to the intranet.
• On the DirectAccess server, at least two consecutive, public IPv4 addresses assigned to the network adapter that is connected to the Internet.
• DirectAccess clients running Windows 7 'Ultimate' or 'Enterprise' editions or Windows 8 'Enterprise' edition clients
• At least one domain controller and Domain Name System (DNS) server running Windows Server 2008 SP2 or Windows Server 2008 R2.
• Public key infrastructure (PKI) to issue computer certificates.

DirectAccess With Windows Server 2012 requires:

• One or more DirectAccess servers running Windows Server 2012 with one or more network adapters.
• At least one domain controller and Domain Name System (DNS) server running Windows Server 2008 SP2 or Windows Server 2008 R2.
• DirectAccess clients running Windows 7 'Ultimate' or 'Enterprise' editions or Windows 8 'Enterprise' edition clients
• A Public Key Infrastructure is not required for Windows 8 Clients.^[5]

Smart card certificates, and health certificates for Network Access Protection may be used along with PKI.

References[edit]

1. ^'Got DirectAccess? Get UAG!'. Archived from the original on 2009-07-21. Retrieved 2017-03-23.
2. ^'What's New in DirectAccess in Windows Server'. technet.microsoft.com. Retrieved 2017-03-23.
3. ^'DirectAccess: Microsoft's Newest VPN Solution - Part 1: Overview of Current Remote Access Solutions - TechGenix'. www.windowsecurity.com. Retrieved 2017-03-23.
4. ^'Configuring Manage Out to DirectAccess Clients PACKT Books'. www.packtpub.com. Retrieved 2017-03-23.
5. ^'What's New in DirectAccess in Windows Server'. technet.microsoft.com. Retrieved 2017-03-23.

External links[edit]

• MS-IPHTTPS on MSDN: includes PDF with specification.

Home > Articles > Home & Office Computing > Microsoft Windows Desktop

1. Installing Windows Home Server Connector on the Client Computers

In This Chapter

• Installing Windows Home Server Connector on the Client Computers
• Rediscovering the Windows Home Server
• Adding a Windows 98 Client to the Network
• Using a Mac on Your Windows Home Server Network
• Using a Linux Client on Your Windows Home Server Network
• Connecting Other Devices to the Windows Home Server Network

A network consisting of just a single Windows Home Server box isn't much of a 'network' at all, it goes without saying. To make things interesting, you need to add one or more devices to the network. By 'devices,' I mean other computers, first and foremost. As you'll see, Windows Vista and XP machines can participate in the full extent of the Windows Home Server experience by accessing the Windows Home Server shares, streaming media, and getting backed up nightly. However, that doesn't mean these are the only computers you can insert into your network. Older Windows boxes, Macs, and Linux machines can also get in on the action by accessing the Windows Home Server shared folders. In some cases, with the right software installed, you can connect remotely to the network from these machines.

By 'devices,' I also mean noncomputer equipment, including Xbox consoles, Zune media players, and other media devices such as network media players and digital picture frames. This chapter gives you the details on connecting these other devices to your Windows Home Server network.

Installing Windows Home Server Connector on the Client Computers

Your key to the riches of Windows Home Server from a client computer's point of view is a program called Windows Home Server Connector, which does the following:

• Locates the Windows Home Server on the network
• Registers your computer with Windows Home Server
• Configures Windows Home Server to automatically back up your computer every night
• Installs the Backup Now component that enables you to back up your computer manually at any time
• Installs the client version of the Restore Wizard, which enables you to restore backed up files and folders
• Adds a desktop shortcut for the Windows Home Server shared folders
• Installs the Home Server Tray application, a notification area icon that tells you the current network status and gives you access to Windows Home Server features
• Installs the client version of the Windows Home Server Console

Supported Operating Systems

The good news is that it's the Connector program that lets your client machine get in on the complete Windows Home Server experience. The bad news is that the Connector software only works on clients running newer versions of Windows:

• Windows Vista Home Basic
• Windows Vista Home Premium
• Windows Vista Business
• Windows Vista Enterprise
• Windows Vista Ultimate
• Windows Vista Home N (European Union only)
• Windows Vista Business N (European Union only)
• Windows XP Home with Service Pack 2
• Windows XP Professional with Service Pack 2
• Windows XP Media Center Edition 2005 with Service Pack 2 and Rollup 2
• Windows XP Media Center Edition 2005 with Service Pack 2
• Windows XP Media Center Edition 2004 with Service Pack 2
• Windows XP Tablet Edition with Service Pack 2

Note that Microsoft has posted no other system requirements for Windows Home Server Connector. In other words, if your system is capable of running any of the preceding operating systems and can make a wired or wireless connection to your network, you can install and run Windows Home Server Connector.

Preparing to Install Windows Home Server Connector

Before installing Windows Home Server connector, you should make sure that your client is ready for the installation and for joining the Windows Home Server network. Here's a checklist:

• Set up a wired or wireless connection to your network.
• Make sure the client's computer name is unique on the network.
• Make sure the client's workgroup name is the same as the workgroup name used by Windows Home Server.
• Make sure you can see the Windows Home Server on your network. (In Windows Vista, select Start, Network; in Windows XP, select Start, My Network Places, and then either click the View Workgroup Computers link or select Entire Network, Microsoft Windows Network, and then click your workgroup.)
• On the client, set up the user account you want to use with Windows Home Server (if you don't want to use an existing account).
• On Windows Home Server, set up a user account with the same username and password as the client user account.

Running the Windows Home Server Connector Setup Program on Windows Vista

Microsoft Access On Mac

With your Windows Vista client PC ready, here are the steps to follow to install the Windows Home Server Connector:

Microsoft Direct Access Client For Mac Pro

1. Insert the Windows Home Server Connector CD.
2. If you see the AutoPlay window, click the Run setup.exe link. Otherwise, use Windows Explorer to open the CD and double-click SETUP.EXE.
3. Enter your User Account Control credentials to authorize the installation.
4. In the initial Windows Home Server Connector dialog box, click Next.
5. Accept the license agreement and click Next. The Windows Home Server Connector installation begins. When the install is complete, you're prompted for the Windows Home Server password, as shown in Figure 5.1.

   Figure 5.1 When the Windows Home Server Connector software is installed, you need to log on to Windows Home Server.

6. Type the Windows Home Server password. If you're not sure of the correct password, click Password Hint to display the hint text that was entered during the Windows Home Server install.
7. Click Next. Windows Home Server Connector joins your computer to the network and configures Windows Home Server to back up your computer nightly.
8. Click Next to complete the Windows Home Server Connector installation.
9. Click Finish. Windows Home Server Connector adds a shortcut to the server shares on your desktop. Note that this shortcut appears on the desktop for all users of the computer.
10. The Home Server Tray application icon appears in the notification area. If your client user account password doesn't match your server user account password, the icon displays a message letting you know. Synchronize the passwords as described in Chapter 4, 'Setting Up and Working with User Accounts.'

Running the Windows Home Server Connector Setup Program on Windows XP

Installing Windows Home Server Connector on Windows XP is similar to installing it on Vista, but the two are different enough that the XP process deserves a separate set of steps. Follow these steps to install the Windows Home Server Connector on a Windows XP client:

Microsoft office 365 mac 2019 download torrent. MacBook Pro (15-inch, 2016 - 2019). MacBook Air (11-inch, Early 2015).

1. Log on to Windows XP with an Administrator-level account. Administrator rights are required to install the Connector software. If you don't want to use this Administrator-level account with Windows Home Server, that's okay. After Windows Home Server Connector is installed, you can log off and then log back on using the account you want to use with Windows Home Server.
2. Insert the Windows Home Server Connector CD.
3. The Setup program should start automatically. If not, use Windows Explorer to open the CD and double-click SETUP.EXE.
4. Depending on the configuration of your XP machine, Windows Home Server Connector may install Microsoft .NET Framework 2.0. If so, follow the onscreen instructions to install the framework.
5. In the initial Windows Home Server Connector dialog box, click Next.
6. Accept the license agreement and click Next. The Windows Home Server Connector installation begins. When the install is complete, you're prompted for the Windows Home Server password.
7. Type the Windows Home Server password. If you're not sure of the correct password, click Password Hint to display the hint text that was entered during the Windows Home Server install.
8. Click Next. Windows Home Server Connector joins your computer to the network and configures Windows Home Server to back up your computer nightly.
9. Click Next to complete the Windows Home Server Connector installation.
10. Click Finish. Windows Home Server Connector adds a shortcut to the server shares on your desktop. Note that this shortcut appears on the desktop for all users of the computer.
11. The Home Server Tray application icon appears in the notification area. If your client user account password doesn't match your server user account password, the icon displays a message letting you know. Synchronize the passwords as described in Chapter 4.
12. If the Administrator-level account you're using for the installation doesn't have a corresponding account in Windows Home Server, you see a dialog box similar to the one shown in Figure 5.2. Click Close.

    Figure 5.2 You see this dialog box if the current client user account doesn't have a corresponding user account on Windows Home Server.

13. If you are using the current Administrator-level user account only for installing Windows Home Server Connector, log off the account and then log back on using the account you want to use with Windows Home Server.

Related Resources

• Book $27.99

• eBook (Watermarked) $31.99

• eBook (Watermarked) $31.99