ICA client not getting to access the Citrix XenApp 6.0 Server

ICA client not getting to access the Citrix XenApp 6.0 Server

 This is the problem in the registry if you see this type of error than check the following and than modify it
Error screen shot






soloution
Go to the registry edit from go to Mycomputer -C:\
To avoid this issue is to rename the file concurrent_state.xml located in C:\Program Files (x86)\Citrix\Licensing\LS\conf.

Installation Of Exchange server 2010

Introduction
Just got my hands on this latest new messaging product from Microsoft, and this has been one of the most anticipated products - Microsoft Exchange Server 2010 Beta (code named Exchange 14). You may can find the download link here, if you wish to test this out in your environment.
Design Diagram @MyLab

Below is the Exchange Server 2010 design in my Lab setup, all the servers are virtualized.

Prerequisites

Before installing Exchange Server 2010, here are the prerequisites to be installed in all the servers

1. Net Framework 3.5
2. Powershell 2.0 CTP 3
3. Windows Remote Management

The above three components must be installed regardless of which role you wish to install.
Step by Step
1. Prepare your forest and organization in Active Directory
First you need to do the Schema preparation. Since this is a fresh new setup in the lab, I will perform the preparation on domain controller

Run Setup from the directory where your Exchange 2010 installation files are located. Here is the cmdlets

Setup /PrepareSchema or Setup /ps

*If you are running the prep process on the computer which is member of the forest or domain, and the OS is Windows Server 2008, you need to install the following component before executing the prep.

ServerManagerCmd -i RSAT-ADDS

Below screen capture shows that its completed.

Next, you will need to prep the domain and organization. Here is the cmdlet

Setup /p /on:SG or Setup /PrepareAD /OrganizationName:SG (where SG is my organization name in the Lab)

Now we have done the initial preparation. The forest and domain are ready to have the first Exchange 2010 server installed.
2. Install first Exchange 2010 server
We will do that on server "Bugis" which will have Client Access Role, Transport Role and Mailbox Role. But we will eventually remove the Mailbox role and deploy DAG on server "Outram", "Redhill" and "Dover". There is a reason behind why I choose to have 3 mailbox servers to form a DAG. That will be discussed in my future articles soon.
There are additional components needed before Exchange installation.,
As my first Exchange server is a combination all the 3 roles mentione above, I used the following command (refer the below screen capture)

ServerManagerCmd -i Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Windows-Auth Web-Net-Ext Web-Digest-Auth Web-Dyn-Compression NET-HTTP-Activation Web-ISAPI-Ext RPC-over-HTTP-proxy RSAT-ADDS

Here is the break down of what you will need to install in role level.
Client Access Role

ServerManagerCmd -i Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Windows-Auth Web-Net-Ext Web-Digest-Auth Web-Dyn-Compression NET-HTTP-Activation Web-ISAPI-Ext RPC-over-HTTP-proxy RSAT-ADDS

Transport Role

ServerManagerCmd -i Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Windows-Auth Web-Net-Ext RSAT-ADDS

Mailbox Role

ServerManagerCmd -i Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Windows-Auth Web-Net-Ext RSAT-ADDS

*For Mailbox Role, you have to install another component call "MSFilter Pack"
After the installation, you are required to perform restart server.

There are some updates & fixes need to be applied in specific.

Client Access Role
KB951725, KB950888, KB952664, KB953290
Transport Role
KB951725, KB950888, KB952664
Mailbox Role
KB951725, KB950888, KB952664

Now we are truly ready for the installation. I will not talk about installation using UI, because I prefer using command line.
Execute the command as shown in the screen capture below.

Here are the definitions of the parameters

/m = /mode
/r = /role, /roles
H = Transport or you can use HT
C = Client Access or you can use CA
M = Mailbox or you can use MB

Just hit "Enter" and sit back enjoy your coffee or newspaper. :-)

Voila, you have now completed the installation and enjoy. (below are the two screenshots of new Exchange Management Console and OWA after installation)

Installation of Fedora Linux 14

Linux Logical Volume Manager, as the default disk partitioning scheme. The installer creates three logical volumes by default, besides the non-LVM /boot partition. The three logical volumes, for /home, /, and swap, are the minimum recommended for a desktop installation. The problem with the default installation is that all available disk space is allocated to the logical volumes, living none for future use when it might be needed to grow a partition, or create a new logical volume. This installation guide takes you through the process of editing each logical volume to free up disk space, space that is not needed for the system to run. At the end (of this tutorial), I will show an example of how to resize (grow) a logical volumes, a basic LVM management task.
When writing these tutorials, I always like to exclude those images that are not pertinent to the subject matter. And so the first image in this tutorial is taken from the step where disk management starts. The default option is to install to Basic Storage Devices, like you would find on a personal computer. The other option is for enterprise-grade installations. Click Next to continue.

Installation options

The Fedora installer offers several disk partitioning methods. The default is shown below, and would be ok if Fedora is the only OS you want on the disk. Just like the default, the other options are self-explanatory. Because the objective of this tutorial is to modify the default partitions, be sure to enable “Review and modify partitioning layout.” And to take advantage of Fedora’s one-click, full disk encryption scheme, enable “Encrypt system.” Next.

Disk partition methods

These are the default partitions and logical volumes created by the installer. We have two primary partitions, one of which is for /boot, and the other is the Physical Volume, that is, the primary partition initialized for use by LVM. If you enabled the encryption option as in this example, the Physical Volume will be encrypted. The test system, which was in a virtual environment, had a disk size of 100 GB, all of which the installer allocated to /boot and the three logical volumes. This is where we begin to modify the logical volumes to free up space, leaving just enough on the logical volumes to install the system.

You can see in this example that about 50% of the available disk space was allocated to lv_root, the root file system, and a similar percentage to lv_home. Since a default installation of Fedora 14 uses less than 2.5 GB of disk space, nothing will be adversely affected if you reduce the size of the logical volumes. To start editing the logical volumes, select each and click on the Edit button, or just double-click on the one you want to edit.

Default partitions

Note: the only entry that is not editable at this step is the physical volume. Try it and you will get the alert shown below.

Volume edit error message

Ok, if you selected any logical volume for editing, the following window will be opened. The first one being edited here is lv_root. The primary goal is to reduce the size, but we can also edit the name of the logical volume. I prefer the logical volume names to be without the lv_ prefix. So lv_root I would rename to just root, lv_home to home, and lv_swap to swap.
Knowing that a new installation of Fedora 14 can be installed on less than 2.5 GB of disk space, reducing the size of lv_root to any value above that should be fine. For this example, I have reduced it to 8 GB. 3 GB should be good too. The name of the logical volume will also be changed as suggested in the previous paragraph.







This is the edited logical volume. Notice the changes from the default. Click OK to close the window and return to the main window. Note that because the physical volume in this example has been enabled for encryption, it is not necessary to encrypt the logical volumes. Doing so would be overkill, but if you are that security conscious, go ahead. Depending on the situation, I would, but in this case, it is not necessary.

Edited /root logical volume

If lv_home is selected for editing, these are the defaults. As with lv_root, the primary item we want to edit is the size.

Default /home logical volume

This is the edited window. Again, notice the difference from the defaults.

Edited /home logical volume

For lv_swap, these are the defaults.

Default swap logical volume

And this is the edited version. For this logical volume, I edited just the name, leaving the size at the default of about 1 GB. Keep in mind that if you do not change the size of swap here, you can only resize it on a running system from the command line. System-config-lvm, the graphical management tool for LVM, does not allow resizing of the swap partition.

Edited swap logical volume

With all three logical volumes edited, this is the new partitioning window. Notice that we now have about 76 GB, roughly 75%, of disk space free. This can then be used to grow or create new logical volumes, if there is a need for it. Click Next to continue with the installation.

Edited partitions

If disk encryption option was enabled, you get this prompt. The passphrase requested here will be used to encrypted the disk.

Encryption passphrase

After the first stage of the installation process has ended, you will be asked to reboot to continue with the second stage of the installation. At the second stage, you will have to create a user, have the option to modify the default boot loader configuration, enable the Network Time Protocol, etc.
When the second stage has completed and you reboot the computer, the disk encryption passphrase will be needed to unlock the disk, that is, if disk encryption was enabled.

Unlock disk

To showcase one advantage, or benefit, of LVM, I will show how easy it is to grow (resize or extend) a logical volume, and I will use the logical volume for /home as an example. Fedora 14 comes with two graphical disk management utilities. One is the GNOME Disk Utility (Applications > System Tools > Disk Utility), and the other is system-config-lvm (System > Administration > Logical Volume Management). Disk Utility is unable to manage encrypted LVM, so the only (graphical) option available is system-config-lvm.

The image below is from the Logical View of system-config-lvm, and the logical volume in focus is for /home. To change the size of this or any other logical volume, just click on the Edit Properties button.

Logical volume view

This is the Edit Properties window. The original size of this logical volume is about 20 GB, and the volume group has about 75 GB of disk space free. To illustrate how easy it is to grow this logical volume, I am going to increase the size to 30 GB.

Original LV properties

This is the edited size. Click OK and you should see the new size reflected in the main window of system-config-lvm. A df -h or lvdisplay at a shell terminal will also show the new size. Note that with ext4 file system, the resizing is accomplished online, that is, you do not need to unmount the volume before editing the properties.
From the command line, resizing a logical volume is even easier. To accomplish this same task from the command line, all that is needed is this command: lvresize -L +10G /dev/vg_hu/home path-to-physcialvolume. You can use lvextend in place of lvresize and still get the same result.

Edited LV properties

In just the same manner that a logical volume can be extended, the size of the volume group can also be extended by adding another disk or disk partition to the volume group. That and other more involved tasks will be covered in a future article

Installation of Exchange server 2007

How to Setup Exchange Server 2007

Follow the steps below to correctly configure your Exchange Server 2007 email server for general use, and for use with IGetMail.  Note that for this document we are assuming you are installing Exchange 2007 on Windows Server 2008 64-Bit.

• Pre-Installation Checklist
  • Install Windows Server 2008 64-bit version
  • Configure your static IP address
  • Activate Auto Updates
  • Add role - Active Directory Services
  • Add role - Active Directory Lightweight Services
  • Add feature - Windows Process Activation Service
  • Add role - Web Server (IIS)
  • Add feature - PowerShell
  • Roles / Features NOT to install
• Installing Exchange Server 2007
• Allow Mail access to your Exchange Server
• Adding E-Mail Users

Pre-Installation Checklist
Make sure you have all of the following steps in place before you setup Exchange Server 2007 on Windows Server 2008 64-Bit.
For simplicity we are assuming you are setting up a small office where one machine will be used for both the Active Directory and the Exchange Server. This setup works just fine and reduces the number of machines to maintain. If you have a larger office you may want to consider separating the Active Directory machine and the Exchange 2007 Server. 
Install Windows Server 2008 64-bit version
Exchange 2007 is a 64-bit application and requires 64-bit versions of Windows Server 2003 or Windows Server 2008.  You should select a computer that is capable of running the 64-bit version of Windows Server 2003 or 2008.  For this example we will start with a clean installation of Windows Server 2008 64-bit version that has not had any roles installed.
After installing Windows Server 2008, we set the clock and the name of the server to be "EX2007".  At this point this server is configured to be a stand-alone computer with default settings.

Configure Your Static IP Address
The default installation of Windows 2008 sets your IP v4 and IP v6 addresses to use DHCP.  Since we will be configuring this computer to be a domain controller, you must change the IP address of the computer to be a static IP address.
To change your IP address, click on "View Network Connections" in the Server Manager screen. 
This will display the list of active network interfaces.

Double-click on your network adaptor to display the adaptors status.

Press the Properties button.

Highlight "Internet Protocol Version 4 (TCP/IPv4)" and press the Properties button.

Change the radio button to "Use the following IP address" and enter an IP address you want to use for this server.  In our example, we chose to assign this server the internal IP address "192.168.1.25".  We also have a firewall appliance that operates as a gateway at the IP address "192.168.1.1". 
NOTE: It is important to include this computer in the DNS list.  You should list the IP address of this computer as the first entry in the list of DNS servers.  In the "Alternate DNS server" field, enter the IP address of a DNS server provided by your ISP.
Press OK to save your changes.
Now you will need to modify the support for IP v6.  If your network uses IP v6, then you will need to select "Internet Protocol Version 6 (TCP/IPv6)" and press the Properties button.  Enter a static address.  If you are not using IP v6, you can leave the IP v6 set to the default setting of DHCP.
NOTE:  Exchange requires that IP V6 be enabled.  Even if you do not use IP V6 you must leave it enabled.  During the setup of Active Directory, the Active Directory Setup Wizard will check that both IP v4 and IP v6 have static addresses as long as the IP v4 address is static you can continue the installation.  DO NOT DISABLE IP V6 or else the Exchange Hub Transport Service will not start.
At this point you should have all IP addresses on this server configured as static IP addresses.  OR you have the IP v4 address configured as static and the IP v6 configured using DHCP.  Press OK to save your changes and close the network connection screen.
Activate Auto Update
The next step in making this server a domain controller is to activate auto update.  Active Directory will not install until this computer has auto updates active.  To activate auto updates click on the link "Configure Updates".   Then select the option to have Windows automatically install updates.   At this time Windows will download updates and will most likely need to reboot your computer.  Allow the updates to be applied and the computer to be restarted until all updates are applied before installing Active Directory.  You do not want to be in the middle of installing Active Directory when an auto update needs to reboot your computer.

Add role - Active Directory Services
The process of installing Active Directory consists of two steps, the first step is to install Active Directory and then you will need to configure your Active Directory.  Once this is complete your Windows Server will now be a domain controller.
Step 1 - Install Active Directory
At the Computer Management Screen press the "Add Roles" link.  At the Select Server Roles dialog check/tick the option "Active Directory Domain Services" and press Next.

Active Directory Domain Services will present information about the changes it will make to your server.  Review this information and press Next.

Now the installation will scan your configuration and inform you if there are any pre-requisites that you have not fulfilled.  If the Active Directory Installation presents an errors, correct these at this time and then repeat the installation.  Once the Setup program indicates that you have met all pre-requisite, then  press the Install button to start the installation process.

The setup program will now install Active Directory on your Server.

When the installation is complete you should see a message indicate "Installation Succeeded", press Close to return to the Server Management Screen.

Step 2 - Configure Active Directory
At the Server Management screen you should now see that you have 1 role installed.  The Active Directory Domain Services may indicate that it is installed but there are errors.  This is because the software is installed but not configured.

To configure Active Directory click on the line under Roles labeled "Active Directory Domain Services".  The Server Manage will show you a page about the status of the Active Directory Role.

Click on the link "Run the Active Directory Services Installation Wizard (dcpromo.exe)" and the Active Directory Domain Services Installation Wizard will appear, press Next.

The Installation Wizard will present information about the version of Active directory, press Next.

Since we are assuming this Exchange Server will be the first Domain Controller, we chose to create a new domain in a new forest.  Press Next.

Enter the name of your domain.  The domain name you enter here is the domain name that Exchange will associated with all of your email.  If you use a hosting company to host your Internet Domain, then you may want to enter the name of your Internet domain with ".local".  If you host your own Internet Domain then you would enter your domain name here.
In our example we are assuming that IGetMail.com is hosted at an Internet Hosting Company.  Since we do not host IGetMail.com on this Exchange Server, we will use IGetMail.local to indicate our internal domain for IGetMail. 
NOTE:  Once you enter your domain name it is very hard to change it in the future, so you should take great care when enter this name. 
Press Next once you have decided on the name of your internal domain, that will be your Active Directory Domain and the domain serviced by Exchange.

Next the Installation Wizard will ask you about compatibility.  If you plan to have domain controllers running various versions of Active Directory then you will want to chose a function level to include the lowest version of Windows that you are using for domain controllers.  Press Next.

Next you will be asked a similar question which is at the domain level instead of the forest level on the previous screen.  You should follow the same approach and include the function level to include the lowest version of Windows you plan to use for domain controllers.  Press Next.

The first Domain Controller needs to have a DNS server running locally.  The optimal location is to start out with having the installation wizard install the DNS server locally.  Also it will automatically make this computer a global catalog server.  Press Next.

You can specify where you want Active Directory to store its data.  If you only have on e drive in your Server then use the defaults.  If you have multiple drives, you can select which drive to use.  Press Next.

Should you need to restore Active Directory in the event of a hard drive failure you will need to boot your Server into a special mode called "Directory Restoration Mode".  Should you need to boot your computer into this special mode, you will need to use a special password just for this restoration.  You can define this password at this time.  NOTE:  This password is different than the administrator account and if you change the administrator password this password will not change.  So you will need to store this password forever in a safe place.  Press Next.

Now the Installation Wizard will summarize the configuration that it is about to create.  Press Next to start the process of configuring your new Domain Controller.

The Installation Wizard will show its progress as it configures your Server.   This will take a long time.

When the installation is complete, you will be shown a final screen.  Press Finish.

Then restart your computer.

After restarting your computer Windows should show you the Server Manager.  You should see on the Server Manager screen that you have Active Directory and DNS Server roles installed.  Also the process of installing Active Directory will add the features "Group Policy Management" and "Remote Server Administration Tools".