Tuesday, November 20, 2012

Make changes on Citrix Web interface to allow password change through Access Gateway

Make changes on Citrix Web interface to allow password change through Access Gateway


Step 1

Log in to the Web interface Servers
Create a folder as Backup_Webconfig in C drive.
Copy the file webinterface.conf from C:\Inetpub\wwwroot\Citrix\XenApp\External\Conf to C:\Backup_Webconfig
Ensure backup is successful.

Step 2
Please go to
Line#25 AllowUserPasswordChange=Never
Line#238 PNAChangePasswordMethod=Direct-Only

Note - Line#238 - If it is commented remove the comment.
               
Change to
AllowUserPasswordChange=Expired-Only
PNAChangePasswordMethod=Proxy

Step 3

Save the configuration.
Valid the site 

Monday, September 10, 2012

Citrix - Important Basic Citrix Commands.

Change user
Changes the setting for .ini file mapping.
Syntax
change user {/execute | /install | /query}
Top of page
Parameters
/execute : Enables .ini file mapping to the home directory. This is the default setting.
/install : Disables .ini file mapping to the home directory. All .ini files are read and written to the system directory. You must disable .ini file mapping when installing applications on a terminal server.
/query : Displays the current setting for .ini file mapping.
/? : Displays help at the command prompt.
Top of page
Remarks
Use change user /install before installing an application to create .ini files for the application in the system directory. These files are used as master copies for user-specific .ini files. After installing the application, use change user /execute to revert to standard .ini file mapping.
The first time you run the application, it searches the home directory for its .ini files. If the .ini files are not found in the home directory, but are found in the system directory, Terminal Services copies the .ini files to the home directory, ensuring that each user has a unique copy of the application .ini files. Any new .ini files are created in the home directory.
Each user should have a unique copy of the .ini files for an application. This prevents instances where different users might have incompatible application configurations (for example, different default directories or screen resolutions).
When the system is in install mode (change user /install), several things occur. All registry entries that are created are shadowed under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\TerminalServer\Install. Keys added to HKEY_CURRENT_USER are copied under the \SOFTWARE key, and keys added to HKEY_LOCAL_MACHINE are copied under \MACHINE. If the application queries the Windows directory using system calls, such as GetWindowsDirectory, the Terminal server returns the systemroot directory. If any .ini file entries are added using system calls, such as WritePrivateProfileString, they are added to the .ini files under the systemroot directory.
When the system returns to execution mode (change user /execute), and the application tries to read a registry entry under HKEY_CURRENT_USER that does not exist, Terminal Services checks to see whether a copy of the key exists under the \TerminalServer\Install key. If it does, the keys are copied to the appropriate location under HKEY_CURRENT_USER. If the application tries to read from an .ini file that does not exist, Terminal Services searches for that .ini file under the system root. If the .ini file is in the system root, it is copied to the \Windows subdirectory of the user's home directory. If the application queries the Windows directory, the Terminal server returns the \Windows subdirectory of the user's home directory.
When you log on, Terminal Services checks whether its system .ini files are newer than the .ini files on your computer. If the system version is newer, your .ini file is either replaced or merged with the newer version. This depends on whether or not the INISYNC bit, 0x40, is set for this .ini file. Your previous version of the .ini file is renamed as Inifile.ctx. If the system registry values under the \TerminalServer\Install key are newer than your version under HKEY_CURRENT_USER, then your version of the keys is deleted and replaced with the new keys from under \TerminalServer\Install.


Issue:
Remove Server entries in Citrix 4.5 once the server is uninstalled and still showing in Farm configuration.
Solution:
dscheck /full servers /deletecomsrv ServerName
dscheck /full servers /deletemf ServerPath ServerName

Issue:
Important Basic Citrix Commands.
Solution:
acrcfg                                      Configure auto-reconnect settings.
altaddr                                      Specify server alternate IP address.
app                                           Run application execution shell.
Auditlog                                    Generate server logon/logoff reports.
change client                            Change client device mapping.
chfarm                                      Change the server farm membership of the server, create an additional farm, and configure a replacement data store.
ctxkeytool                                 Generate farm key for IMA encryption.
ctxxmlss                                  Change the Citrix XML Service port number.
dscheck                                   Validate the integrity of the server farm data store.
dsmaint                                    Maintain the server farm’s data store.
enablelb                                    Enable load balancing for servers that fail health monitoring tests.
icaport                                      Configure TCP/IP port number used by the ICA protocol on the server.
imaport                                     Change IMA ports.
migratetosqlexpress                 Migrate the server farm’s data store from a Microsoft Access database to a SQL Server Express database.
query                                       View information about server farms, processes, ICA sessions, & users.
twconfig                                   Configure ICA display settings.


Friday, August 31, 2012

How to install Rollup Pack 7 on Xenapp 6.5 Farm


How to install Rollup Pack 7 on Xenapp 6.5 Citrix Farm

Implementation Steps

·         Ensure that there are no existing connections on any servers
·         Ensure that the Independent Management Service is running
·         Create a folder called source and copy PSE450W2K3R07.msp
·          Proceed installation with Server(Server name)
·         Double click PSE450W2K3R07.msp located on C:\Source\
·         Reboot the server.
Post Implementation
Ø  After a deployment, ensure that all servers in the farm are updated to the same hotfix rollup pack level.
Ø  All services are running
Ø  Check Server accepts ICA connection by launching test application

Saturday, August 4, 2012

How to ensure users have the desired regional settings


Scenario
Regional settings such as currency, date/time format, and numbers are user profile-based.
In a Terminal Server/Citrix environment, users from different regions may want to retain their client-side regional settings when logging on to the server.
To set up the correct regional settings, log on to the Citrix server, select Start > Control Panel > Regional Settings. Set the correct setting and log off so the setting is written to the user’s profile.

Method 1
This method sets the users’ regional options at logon by script:

1. Create global groups based upon the users’ desired regional setting.
2. Create a test user for each global group.
3. Log on to the Citrix server with that test user and make appropriate changes within the regional options.
4. Export the registry key HKEY_CURRENT_USER\Control Panel\International.
5. Create a script (How to use Regini.exe to modify HKEY_CURRENT_USER) and call it Usrlogon.cmd.
6. When users log on to the Citrix server, they will inherit the regional settings based upon their group membership.

Friday, August 3, 2012

Citrix Xenapp 6.5 Installation step by step procedure

1. Document Scope:

This document describes the procedure to perform an initial setup of Citrix XenApp 6.5 on a Windows Server 2008 R2.
To support a globally centralized service desk it is necessary to follow this basis document’s procedures. This provides a similar Citrix environment worldwide with differences in view regional based configurations only, but nearly the same behaviour.
2. System Requirements
•    Ensure that a new database for the new XenApp 6.5 farm is available on the SQL server hosting Citrix datastores in your environment
•   Install XenApp 6.5 on the first server in the farm and perform the initial configuration.
•   Install XenApp 6.5 on member servers and perform additional configuration as necessary.

3. XenApp 6.5 installation
XenApp 6.5 Wizard based installation:-
To installing XenApp it is recommended to use the Wizard-Based Server Role Manager.On the installation media, double-click autorun.exe. The Citrix XenApp installation menu launches. Select Install XenApp Server. 
The Server Role Manager launches and checks if any roles are already installed

Select “Add server roles”. The server roles manager pops up with an edition menu. Select “Enterpris Edition” and continue.
 Confirm the License agreement. Tag “I accept.....” and click “Next”
 Choose common role XenApp  and continue with “Next”.
Do not choose any subcomponents click “Next”
The XenApp installer is checking for pre-requisites as shows a list of the missing on you system.

Confirm and continue.

The next screen displays all parts of the installation that will be performed.
Click “Install” to proceed.



The progress and finally the status of the installation will be confirmed with the next info.
Confirm with the “Finish” button. The installation is done. Now it’s time to perform a basic configuration.

Specify Licensing:- Click “Specify Licensing” within the server configuration tasks.
Enter the License server for your environment and check if the mentioned server is accessible.
Click the “Test Connection” button and the configuration will be confirmed with the popup window below.
Select license model “XenApp” and apply the settings.
Licensing is preconfigured now.
Create a new farm
The XenApp Server role manager has one configuration left. Click configure to continue. 
Create a new farm if this is the first server. The server will be automatically setup in controller mode.
Define the name of the farm which should appear in your configuration and set the account you are logged in as the first Citrix administrator account.

Here we need to provide the SQL database instance hosting the Citrix datastores, the database name and the database service account.  (Datastore details will provide once we have those information)


Enter the data and click next.

Enter the credentials of the service account configured for accessing your database  on the SQL server instance.  

The credentials below are an example:-

Perform a connection test.

A valid configuration will be confirmed like shown below.
Click ok to leave the datastore configuration.
Configure advanced settings

Keep the default settings for shadowing and confirm with the “Next” button.

Specify Data Collection settings. The fist server must be a Controller and therefore this setting cannot be changed. Use a custom zone name. Provide a speaking name for your zone as it is needed in a twin data center configuration to spread the farm of 2 DC’s.
Keep in mind that 2 controllers must be configured per DC.
Do not configure the Citrix Receiver settings on the XenApp Server. Leave it empty and continue.
Deselect “Add Anonymous Users” and “Add the list of users from the Users group” and select only “Add the Authenticated Users” as shown below. Click “Next” to confirm.



The screen below gives you an overview of what has been configured with the previous steps.
Click “Apply” button to proceed this settings .

After the configuration has been applied you will be informed like the next screen. All successful part will be shown green flagged.
The XenApp Server Role Manager displays the status of your installation.
Reboot the server and you are done.


Confirm to perform a reboot.
Congratulations! Your server has passed  installation and configuration successfully.
Uncheck “Do not show this windows at logon” .


Installation complete!!  















Monday, June 18, 2012

Take full control of devices, apps and data


From chaos to control.
Learn how to eliminate mobile and cloud chaos with an enterprise app store.
IT departments are grappling with a chaotic environment marked by exploding device heterogeneity, app proliferation and data fragmentation, all while trying to keep people productive. It’s easy to see how IT is losing control over devices, data and users. Now, with Citrix Unified Storefront you can build a secure enterprise app store and turn chaos into control:
Simplify IT with a single point of control over all apps, data, devices and users
Protect apps and data with context-aware security controls that deliver content based on role, device, location and network
Empower users with a single point of secure access from any device to all apps and data whether virtual, web, SaaS or mobile
Boost productivity with a personalised, self-service enterprise app store that seamlessly follows users from device to device
Unified Storefront delivers an enterprise app store and a more secure and agile business in just four easy steps.Learn More.