have Trouble deploying Citrix Receiver for users? Unlike most rely on Citrix Citrix Receiver is on client devices rather than centralized servers, which are only administrators. I found this blog article as a step-by-step instructions for administrators who Citrix Receiver on client devices with little interaction with the user want to customize and deploy.
Below is a high-level overview of the steps used in this blog to configure a custom recipient installation package:
- Adjusting receiver. This section describes how to configure receiver with specific settings, including settings of ADM templates.
- Deploy receiver. This section describes how to use Smart Install Maker to create a custom Receiver application. This section also shows how to implement receiver through storefront and Web interface
. Note: For the purposes of this blog the installation files to C are stored: Receiver on a Windows operating system. In addition, recipients can be manually uninstalled; However manual uninstalls of receiver may leave some legacy registry keys on a user's computer. It is a publicly available utility that receiver cleanup utility that legacy registry key removed. Uninstall any legacy version of the receiver before a customized version of the receiver to a user's device to install.
1 Adjust Receiver
How many versions of Citrix Receiver are available, an administrator must first determine which version to implement provision of receivers and what functions. The Citrix eDocs provides information on the beneficiaries versions and CTX135933 provides methods for deploying Citrix Receiver.
1.1 Download receiver
| step | Description |
| download receiver. | from a Windows operating system, download the corresponding receiver version. |
| Save receiver. | Save receiver to C: Receiver and the file on CitrixReceiver |
1.2 adjust receiver
[1945013umbenennen]step
Description [determine
receiver settings.
determine requirements for recipients. create
batch file with receiver settings.
create a batch file with receiver installation parameters command line. Save the file on C: Receiver and file name as Steps.bat . Below is an example batch file command:
CitrixReceiver.exe / silent / includeSSON ENABLEPRELAUNCH = true
Note: may be some features Receiver command line parameters to use when installing the receiver by. However, other features that are not used on the command line parameters, and instead an ADM template required can. If a setting can not be configured using command line parameters, go to step 1.3 implemented. Otherwise, continue 1.4.
1.3 Configuring ADM Template Settings
| step | Description |
| import ADM template. | Import ADM template for Group Policy and configure the settings Note: .. an example of how to import an ADM template in CTX113004 be found |
| determine registry changes. | After confirming that the policy of the ADM templates work on a test PC, open the test PC registry. The ADM template policy should be in HKEY_LOCAL_MACHINE SOFTWARE Policies Citrix ICA Client . Export the key to C: Receiver . For example, a registry key for a single sign-on would change be renamed sso.reg. |
1.4 Edit Steps.bat
| step | Description |
| confirm files in C: receiver | to . C: Receiver and confirm the existence of files of sections 1.2 and 1.3. If the exact steps from this blog to use the following files would be available:
Note: the administrator places the files on C: receiver . However, the Receiver script push files to another drive on the client devices. This blog is assumed that the receiver script pushes files to . C: temp |
| Adding files to Steps.bat . | Besides Receiver Installation Steps.bat will import registry settings. Update Steps.bat contain other files in C: Receiver In order to fulfill these tasks. Below is an example .: ECHO ECHO |
| Save Steps.bat. | Save steps. bat . |
2 Deploying Receiver
with the steps to install a batch file providing correct receiver requires a custom application winding tool. This blog uses Smart Install Maker to create a custom application that executed the Steps.bat file and load the files contained in C: Receiver user C: temp drive. The custom application can be automatically inserted through storefront or web interface.
2.1 Creating custom recipient application
| step | Description |
| download Smart Install Maker. | Download and install Smart Maker install. Then start Smart Install Maker. |
| Update installer Tab. | Under the installer tab , select the General tab to change the text in Save: to the location and the name of the custom executable. In this example, the custom executable named custom.exe is and the file will be stored in C: Receiver . Note: [1945006DieseEinstellungen] can be customized by the administrator to create custom business settings such as company name, company website and installer included name. The Save to: option specifies where the final executable is written; in this case . C: / receiver as the path and custom.exe as executable name |
| selected Update files Tab . | Under the files, click tab at the bottom right of the page. appears after the Add Item window, add files to the source . Add |
| files. | Add all the files from C: Receiver |
| Change target directory | change the text target as .. target directory: to C: temp . Then turn off the Uninstall checkbox and select OK . Note: This process will copy the files down to the user C: / Temp directory. The directory location can be customized by the administrator. |
| Update dialogue Tab. | Under the dialogue tab, select the Silent Installation checkbox and enter . C: temp for the target path Note: This option will remove prompts from message is shown during the installation, so that the final executable file can be used without any user intervention , |
| Update commands Tab. | Under the commands tab, add the Steps.bat file. Select After unpacking under divisions: and select Wait until the application is terminated checkbox. Then select OK . Once the files have been copied previously indicated in the list below, the custom installer will start the Steps.bat file in Section 1.4 creates custom installation of the receiver to process. |
| update the Uninstaller Tab. | Under the Uninstaller tab, select the General tab. Disable the Let uninstalled the product checkbox be . Note: allow the product to create a uninstalledwill an uninstaller option that is available through the available Add / Remove Programs menu in the user's device for easy removal. create |
| custom executable. | Under the project tab, select Build Installer to create a .exe file |
| , the custom executable View custom executable | , the custom executable in C available: .. receiver , as at the beginning of this section indicated. |
| Test custom executable. | of a test PC, run custom.exe . custom.exe is first download the receiver and the other files on the user . C: temp drive and then run the Steps.bat script |
2.2 Deploying custom recipient through storefront
Note: 2.2 Some of the changes in portion can not be undone. See available at Citrix eDocs .: Ask Citrix Receiver installation files on the server
| step | Description |
| Copy receiver storefront. | on the storefront server to C: Program Files Citrix Receiver Storefront Receiver client . Create a folder named Windows , copy the custom recipients file (ie custom.exe ) with Windows folder. Note: If using the web interface, go to section 2.3 |
| Run PowerShell script | start .. PowerShell , enter & "C: program Files Citrix receiver storefront scripts UpdateWindowsReceiverLocation.ps1" -ClientLocation "Windows custom. exe " and press Enter . Note: PowerShell can not allow scripts to run on the storefront server. In order to continue running scripts in PowerShell, run Set-ExecutionPolicy unrestricted . |
| Edit web.config file. | under C: storeName Inetput wwwroot Citrix Web , edit web.config. Locate upgradeAtLogin = "false" and change upgradeAtLogin = "true" before you save the file. |
2.3 Deploy custom recipients via the web interface
| step | Description |
| Copy receiver to the web interface. | on the Web Interface server to % Program Files% Citrix Web Interface 5.4.0 Clients . Create a folder named Windows and in the Windows folder, create another folder named Receiver . Then copy the custom recipients file (ie custom.exe ) with the Receiver folder. |
| Set Folder Permissions The following permissions | in Windows folder Receiver folder and custom.exe , add .: administrators - Full Control authenticated users - read and Execute, read NETWORK SERVICE - read and Run, read |
| Select client Deployment . | from the Web Interface Management console, right-click the Web Interface site and select client deployment . |
| Enable Client Detection . | under General , select Client Detection . Select the Perform client detection at logon and offer upgrades for customer checkbox. Then select OK . |
| Edit WebInterface.conf file. | under C: Inetput wwwroot Citrix Site-Name Conf , edit WebInterface.conf. Locate # ClientICAWin32 = filename: CitrixOnlinePluginWeb.exe ... and switch ClientICAWin32 = filename :. Custom.exe ... before saving the file |
In addition, I would like the following Citrix Consultants thank for their contributions: Pablo Legorreta and Eric Jurasinski
Thank you ,.
Steven Krueger
Citrix Consulting
0 Komentar