In either case, it is always best to ensure that your Terminal Server is properly protected within the confines of a network firewall. With Terminal Server, a user can experience running a desktop over the internet with the Windows Remote Desktop Connection feature. They do not need to install any programs on their machine and none of the data streams across the internet. Only screen refreshes are sent over the Internet so it feels like you're running the application locally but it's all happening on the server.
Printing also occurs locally, so a user can run an application over Terminal Server and have it print reports on their local printer. Since multiple users are running your program on the same machine, your application needs to be multiuser friendly to avoid conflicts between users. Terminal Server is particularly powerful for database applications such as Microsoft Access since you don't need to worry about installing Microsoft Access on each user's machine, making sure the right version of Access is loaded, whether the latest front-end database application is deployed, and the need to send large amounts of data over the Internet for Access to process.
It's all being done on the Terminal Server machine with the local network bandwidth, and only the screen is refreshed as it changes. For multi-user and scalable support, your Microsoft Access application should be a split database design where each user has their own copy of the front-end database installed under their profile.
Our Total Access Startup program can also help with deployment for each user to ensure they have the latest copy of your front-end database. However, giving users a virtual desktop on your network can be too much power if you only want to let people run one application over the Internet.
With the release of Windows Server R2, many enhancements were made to the Terminal Server feature. In particular, a powerful feature called "RemoteApp" is now available see RemoteApp and Desktop Connection from Microsoft for more details. With RemoteApp, you can "lock down" the Windows desktop to limit users to a single Windows application.
Unlike a remote desktop environment, RemoteApp restricts the user from running other applications, browsing the network, etc. NET, etc. For example, you can use Terminal Server with RemoteApp to let your external contractors access your organization's Windows invoice submission application over the web without exposing any other programs or resources to them.
Below are the steps for setting up a Terminal Server on your network, then exposing a particular application with RemoteApp. The computer must be a 64 bit machine, with enough hardware and memory to support running the maximum number of simultaneous sessions you expect.
It's essentially the same as running multiple instances of your application on one machine. The computer also needs to be on your network and Internet to allow remote users to run it. In addition to the server license, you must have a license for the maximum number of simultaneous users of your RemoteApp sessions.
The CALS are limited by the number of users, not the number of applications you want to support and expose over the web. This lets them run the machine as if they were onsite. However, that can give the user too much power and rights to your network. RemoteApp lets you restrict users to a single program. When the user logs into their Terminal Server account, the program you specified automatically loads.
The user doesn't get to the desktop, can't load Windows Explorer, or any other programs while connected. When you install your application on the Terminal Server, you must have Admin rights to install your program, any ActiveX controls, etc.
Your user can then run the application. Upon closing the program, the Terminal Server session closes.
RemoteApp also supports batch command instructions if you need to initialize anything before the user starts. Below are the basic steps to configure RemoteApp to start a program:. While Terminal Server and RemoteApp offer an amazing way to deliver your application over the web, there are limitations and differences compared to a web solution:. RemoteApp is not a replacement for an Internet site that is publicly available and can support large numbers of simultaneous users.
Those are appropriately created with Visual Studio. NET, Java, or other platforms that scale for such environments. One of the benefits of using Microsoft Access is the support that is offers for linking or connecting to one or more data sources.
However, there is a limitation with the ability of RemoteApp to support User Path variables. For example, the following path does not work:. This is a limitation which Microsoft Access Administrators must deal with since a proper deployment of an Access application requires that each user opens their open local copy of the database. A solution to this limitation would be to use Total Access Startup. For Access applications, Total Access Startup addresses the following concerns of Access developers and administrators:.
You don't need to create special settings for each user. Total Access Startup lets you specify the version of your front-end database.
When that changes, the user's copy is updated automatically the next time they launch your program. Ensure that the database is opened within the version of Access which it is designed to support as specified by the database administrator within an INI file used by Total Access Startup. There's even support to downgrade below the preferred version, if desired. You can control this for each database regardless of having multiple instances of Access installed on the PC. For more information about Total Access Startup and the functionality is offers, we invite you visit the main page for Total Access Startup.
There is fully functional trial version of Total Access Startup available for download here. Terminal Server and RemoteApp are an excellent and cost effective option for extending existing Windows based applications to remote users. For existing applications where you only need to support a limited number of remote users, RemoteApp lets you leverage your existing investment in all your applications and get up and running immediately.
There's no need to make the investment in time and money to rewrite the application for the web in these situations. You also won't give up the nice features in Windows that aren't implemented so well on web solutions e. A Terminal Server and RemoteApp platform offers a convenient, safe, and secure method for your offsite employees, contractors, and selected external users to obtain controlled access to your internal applications and resources.
We have found this technology to be especially impressive with its ease of implementation, use, and customizability. There is a licensing grace period of Days during which no license server is required. Use the following information to learn about how client access licensing works in Remote Desktop Services and to deploy and manage your licenses:.
When you use the Per Device model, a temporary license is issued the first time a device connects to the RD Session Host. When you use the Per User model, licensing is not enforced and each user is granted a license to connect to an RD Session Host from any number of devices.
It's your responsibility to ensure that all of your users have a valid license and zero Over-Used CALs—otherwise, you're in violation of the Remote Desktop Services license terms. An example of where one would use the Per Device model would be in an environment where there are two or more shifts using the same computers to access the RD Session Host s.
If you want to use the Office template image that comes with RemoteApp, you must have an existing Office ProPlus plan. The same is true for any Office app that you publish using a custom template. You need to activate the apps with your own subscription. This is true for both trial and paid subscriptions. If you want to use the Office template image during the trial, and you don't already have a subscription , go to the Office page to sign up for a trial subscription.
See How do RemoteApp and Office work together? If, during the trial period, you don't want to get an Office trial subscription, use the Office Professional Plus template image that comes with RemoteApp.
This template image can only be used for 30 days and cannot be converted into a paid collection. That makes sense, right?
You can publish any app that you are legally entitled to share.
0コメント