First thing we need to do, is install the application, but we can’t just double click on the installer and run through the installation like we normally would, instead we have to put the XenApp server into terminal services install mode, then we can launch the installer. Once finished, we need to exit the terminal server install mode and publish the application.
Terminal Server Install Mode:
To begin the installation, we can do this in two ways:
We can now begin the installation. Notice how when we use the first option “Install Application on Remote Desktop…” we get a window that prompts us for the installer. Well that’s all we have to do, once we point to the installer, the actual installation process is identical to what it would be if we were installing the application on a regular computer.
Publishing The Application:
Publishing the application is also, quite simple, the idea is to tell the XenApp server where the application is installed. XenApp server then publishes that application to the farm.
Let’s begin by navigate to the applications within AppCenter, right click on the application and click on Publish Applications
Click Next
Fill in the application Display name and description and click Next
Here is where we need to chose the type of application we’re looking to publish. We have three choices:
Streamed/Streamed to client means that the application will be downloaded to the client workstation and opened on the client. This would be a good option for users that use laptops and tend to be offline (not connected to the network) but still require access to these applications
In our example, we’ll select the default application type and click Next
Here is where we need to chose the location of the application and the working directory. It’s important to make note as to where we install the application on the server because we’ll need to point to the application when we’re publishing in XenApp. Also, it is very important when we have more than one XenApp server, that we install the application in the same location on both servers. For example, if we install Adobe reader in E:AdobeReader 11.0 on Server 1, then on Server 2, we’d need to install Adobe reader in the same location
Now, we’re going chose the servers where we want these applications to run
Next, we have to specify the users or groups to whom we want to give access to
The next section, gives us a couple of options. Generally speaking, this section allows us to manage the application shortcuts by defining where we want the application to be displayed on the users desktop or web interface. We can create folders and add the application to those folders. When the user connects with the Online plugin or through the web interface, they’ll see their applications in the folders or locations that we define here. This is something interesting that we can keep in mind when publishing the applications. In our case, we’ll keep the defaults and click Next
Now we can click on Finish, and our application will be published
I want to make a quick note and say that we also have some advanced options that we can configure for the application before we Finish publishing to the XenApp server. These advanced application configurations include:
Terminal Server Install Mode:
To begin the installation, we can do this in two ways:
- In control panel click on Install application on Remote Desktop…
- Within command prompt, place the server into install mode
We can now begin the installation. Notice how when we use the first option “Install Application on Remote Desktop…” we get a window that prompts us for the installer. Well that’s all we have to do, once we point to the installer, the actual installation process is identical to what it would be if we were installing the application on a regular computer.Publishing The Application:
Publishing the application is also, quite simple, the idea is to tell the XenApp server where the application is installed. XenApp server then publishes that application to the farm.
Let’s begin by navigate to the applications within AppCenter, right click on the application and click on Publish Applications
Click Next
Fill in the application Display name and description and click Next
Here is where we need to chose the type of application we’re looking to publish. We have three choices:- Server desktop – XenApp Server console
- Content – Web pages and Links
- Application – Applications we installed on the XenApp server
- Accessed from a server – Default option, application is launched on the server
- Streamed if possible, otherwise accessed from a server – Application is streamed to the client, if not possible, the application will be launched on the server
- Streamed to client – Streamed to the client
Streamed/Streamed to client means that the application will be downloaded to the client workstation and opened on the client. This would be a good option for users that use laptops and tend to be offline (not connected to the network) but still require access to these applications
In our example, we’ll select the default application type and click Next
Here is where we need to chose the location of the application and the working directory. It’s important to make note as to where we install the application on the server because we’ll need to point to the application when we’re publishing in XenApp. Also, it is very important when we have more than one XenApp server, that we install the application in the same location on both servers. For example, if we install Adobe reader in E:AdobeReader 11.0 on Server 1, then on Server 2, we’d need to install Adobe reader in the same location
Now, we’re going chose the servers where we want these applications to run
Next, we have to specify the users or groups to whom we want to give access to
The next section, gives us a couple of options. Generally speaking, this section allows us to manage the application shortcuts by defining where we want the application to be displayed on the users desktop or web interface. We can create folders and add the application to those folders. When the user connects with the Online plugin or through the web interface, they’ll see their applications in the folders or locations that we define here. This is something interesting that we can keep in mind when publishing the applications. In our case, we’ll keep the defaults and click Next
Now we can click on Finish, and our application will be published
- Access Control – We can create filters and limit as to who can access the applications
- Content Redirection – The ability to open files that are local to the user but with application that is remote on the XenApp server or wise versa
- Limits – Limit the number of instances and concurrent connections that are allowed to open the application
- Client Options – Audio, connection encryption and printing options for the applications
- Appearance – Resolution, colors, etc
No comments:
Post a Comment