Tech Forum - Windows Networking & Systems

Friday, September 7, 2012

Citrix 6.5 Installation

Citrix – XenApp 6.5 – Installation Guide for Administrators

In Citrix, Xenapp 6.5 on September 23, 2011 by vmhq blogger Tagged: Citrix, Xenapp, XenApp 6.5

Welcome to our XenApp 6.5 Installation Guide for Administrators

1.0 XENAPP 6.5 DEPLOYMENT

This post is a configuration guide for an administrator to assist in joining a 2008 R2 server to a XenApp 6.5 Citrix Farm.

1.1 FARM DESIGN – OVERVIEW

1.2 BASE BUILD

1.2.1 Server Resource Specifications

Server 2008 R2 Standard x64

4 Gigs Memory

2 Processors

60 Gig HDD

1.2.2 SECURITY GROUP ASSIGNMENT

Manage access to your citrix servers using Group Policies. Use Security Groups for your server objects. Once the server is joined to the domain – add the server object to the secuirty group in AD that reflects the environment it will service.

1.3 XENAPP PREREQUISITS

The XenApp Server Role
Manager deploys the following software (except as noted), if it is not already installed:

.NET Framework 3.5 SP1 (this is a prerequisite for the XenApp Server
Role Manager; it is deployed automatically when you choose to add the
XenApp server role from the Autorun menu)
Windows Server Remote Desktop Services role (if you do not have
this prerequisite installed, the Server Role Manager installs it and enables
the RDP client connection option; you will be asked to restart the server
and resume the installation when you log on again)
Windows Application Server role
Microsoft Visual C++ 2005 SP1 Redistributable (x64)
Microsoft Visual C++ 2008 SP1 Redistributable (x64)

1.4 INSTALLING XENAPP

Run "autorun.exe"
Click "Install XenApp Server
Click "OK" to install .Net 3.5 SP1
Click to Add Server Roles
Install Enterprise Edition
Accept the License Agreement
Select the XenApp Role and click "Next"
Remove Xenapp Management and Windows Desktop Experience Integration. Click Next
Review the prerequisites and click next, and install
Reboot Server as requested
Log back in, the Xenapp Server Role Manager will open again. Click on Add or remove server roles.

(Ignore the Reboot message – That won't go away no matter how many times you reboot )

Click on Add Server Roles and accept the License agreement
Add XenApp again and click Next
Remove Xenapp Management and Windows Desktop Experience Integration. Click Next
Review the prerequisites and click next, and install. Install can take up too 30 mins.
Click Finish

4.4.2 CONFIGURING XENAPP SERVER

Open the Citrix Xenapp Server Role Manager
Under Server Configuration Tasks, click on Specify Licensing
On the License Configuration screen, enter (Name of your Citrix License Server) as the License Server, or choose to Configure the license
server later using policy if you have specified the license server in your farm policies. Click Next.
Choose XenApp as the model in the the Licensing Model Screen and click apply
You will return to the XenApp Server Role Manager screen
Click on "Configure" under the Server Configuration Tasks
Click Add this server to an existing server farm
Choose Existing Microsoft SQL Server database and click next
Enter the name of your Database Server and the database name. Choose "SQL Server authentication using a login ID and password to access the database".
Test the connection and click next
On the Configure Shadowing screen leave the default of allow and click next
Under Specify Advanced Server Settings, configure the following:

(BE AWARE THERE IS 4 SETTINGS TO CONFIGURE ON THIS PAGE BEFORE CLICKING NEXT)

Data Collection
- § Enable Session-host mode if you want to limit the data collector to specific servers
- § Use a custom Zone name or accept the default
- XML Service
  - § Use a custom XML Service TCP/IP Port : 8080 if you choose not to integrate with IIS and you changed your XML service port
  - Receiver
    - § Leave Blank (You can configure this lately should you need to use it
    - Remote Desktop Users
      - § Only select "Add the Authenticated Users". Deselect the default option. Click Next. Click Apply
      - § Click Finish. Reboot the Server.

And All Done!

Wednesday, July 25, 2012

Job Description of Incident Manager

Job Description of Incident Managers

1. Understand the Incident and the diagnostic/resolution actions attempted already by the Service Desk and any other Technology Tracks
2. Use the designated or allotted communication bridge, monitoring facilities and on-call schedule from Technology tracks to facilitate immediate attention from all required parties
3. Authorize any IVR message updates for Service Desk
4. Work with all stakeholders to identify the workaround or resolution for the Incident
5. Set expectations of all stakeholders about the timelines and permissions required for the resolution
6. Send Periodic updates to the stakeholders (and if required, to the customers) through Service Desk, until the Incident is resolved
7. Initiate Emergency Changes if required, mobilize cross functional teams, External Vendors and obtain approvals for the mitigation actions from all stakeholders
8. Retain the Technical Observation Post (certain ad-hoc individuals who observe the service after the Incident is resolved) in order to insure that the resolution has actually resolved the Incident and that the Services have returned to their normal state
9. Open Problem Tickets as per Problem Management Policy and Procedures
10. Document in retrospect, the actions taken, learning and approvals in the service Management tools
11. Document the new knowledge learning and any other recommendations in a Critical Incident Report and submit the report to the audience in line with the Critical Incident Management procedures.
12. Periodically audit Incident records and coach the Incident Management staff to
13. insure that "ticket hops" are reduced to the minimum
14. avoid possible misuse of "Pending" status by resolving groups
15. enforce the use of available knowledgebase, Configuration Management Database and Known Error Database for quicker resolution of Incidents
16. Quality of updates being made into the Incident Records
17. Devise, measure, report, monitor and improve the internally designed KPIs to improve the efficiency of Incident Management process. Example: Ticket hops, Incidents per staff, Incidents resolved using KB

Regards

Mohamed Rafi
GSM :91-9791133997