Create Virtual SAN Using Microsoft iSCSI Software Target

This is one of the perfect free tool from Microsoft which was really useful for me to create an SAN virtually for my testing purposes. You can use this for any kind of requirement which are related to SAN Spaces.

Here my requirement was to use this SAN for a windows Cluster as SAN space is an mandatory for it.

clip_image001

Note – This is for testing environments and NOT to be Used in Production.

Download and Install the application first. Download from here

Tool located under administrative tools as below once you installed .

clip_image002

Configure Target

Target is – the central location which holding the main configuration and storage for Virtual SAN.

Lets get create a New …….

Right click on iSCSI Targets , create new Target

Click next to continue

clip_image003

Provide a Name for your New Target and Next to continue.

clip_image004

Here to define IQN Identifiers. This is used to add your identifiers (Other Nodes which will use this Target).you will need to guess this by referring to below syntax as we haven’t setup our client yet

So will come back t this to verify once we configured our client.

The syntax for IQN is – iqn.1991-05.com.microsoft:machinename.domainname.com

Here I gave my client’s IQN as I have already setup it.

Click next to proceed and click finish to complete.

clip_image005

Now we need to create Virtual disks for this Target. Get in to Create Virtual Disk wizard to do it.

clip_image006

Give a Name to New Disk and define the path as you wish.it will create a virtual disk in particular location.

clip_image007

Size of the virtual disk to be defined in MB.

clip_image008

Give a description for better identification while you work in Console.

clip_image009

Click finish to complete the disk creation.

clip_image010

Direct to Properties of the New Target. You can see here all the settings you given.

clip_image011

all the initiators you added are shown here. Also you can add more initiators if your other hosts need to use this Target (V-SAN)

clip_image012

Virtual disks are shows here in this tab

clip_image013

More Details on the disks are discoverable in root.

clip_image014

Configure Clients (Initiators) via ISCSI Initiator

This can be setup in most operating systems, tool is available in Windows 7 /Server 2008 by default so you don’t need to install this.

For Other Operating Systems = From the download earlier – get the following file for installation

iscsitargetClient_public.msi

Each and every clients should be configured for accessing the Target we created.

Find iSCSI Initiator at administrative tools and get in to the interface shown below.

clip_image015

Click Yes for the verification massage box as you get it once launching this tool for the first time.

Copy Initiator’s Name of the client by Direct to Configuration tab. Initiator Name is the Unique Name for particular client which we need to include in Initiators list in our ‘Target’.

clip_image016

Go back to Target’s Properties and insert this name in to Initiators list.

Click Add to insert

clip_image017

Paste Name Here which you copied from client and click OK.

clip_image018

Go Back to the Client and direct to ‘Discover’ Tab and click Discover Portal.

Give the IP/DNS Name of the ‘Target’, This is the place to connect to Target from clients.

clip_image019

clip_image020

Here will appear you Portal.

clip_image021

Then next is to connect to our Target. Go to Targets tab and it should appear yours as inactive bby default.

clip_image022

Click Connect to continue and click OK to connect

clip_image023

Now status becomes connected as it was success.

clip_image024

Click ‘Auto configure’ in Volumes and Devices tab. What ever the disks are created in your Target should appear here once it’s success.

clip_image025

Also disks are can be viewed via ‘Devices’ in Targets tab as shown below.

clip_image026

Map Disks to clients

Now we can map disks to each clients as required.

Get in to the disk management utility, it will appear in initialization wizard to disks, check for each disk as required and click ‘OK’ get mapped.

clip_image027

That’s all for configuring Client and our new disks are Ready to Rock and Roll……….. !!!!!!

Now You can create volumes as required.

clip_image028

Advertisement

Create Virtual SAN Using Microsoft iSCSI Software Target

This is one of the perfect free tool from Microsoft which was really useful for me to create an SAN virtually for my testing purposes. You can use this for any kind of requirement which are related to SAN Spaces.

Here my requirement was to use this SAN for a windows Cluster as SAN space is an mandatory for it.

clip_image001

Note – This is for testing environments and NOT to be Used in Production.

Download and Install the application first. Download from here

Tool located under administrative tools as below once you installed .

clip_image002

Configure Target

Target is – the central location which holding the main configuration and storage for Virtual SAN.

Lets get create a New …….

Right click on iSCSI Targets , create new Target

Click next to continue

clip_image003

Provide a Name for your New Target and Next to continue.

clip_image004

Here to define IQN Identifiers. This is used to add your identifiers (Other Nodes which will use this Target).you will need to guess this by referring to below syntax as we haven’t setup our client yet

So will come back t this to verify once we configured our client.

The syntax for IQN is – iqn.1991-05.com.microsoft:machinename.domainname.com

Here I gave my client’s IQN as I have already setup it.

Click next to proceed and click finish to complete.

clip_image005

Now we need to create Virtual disks for this Target. Get in to Create Virtual Disk wizard to do it.

clip_image006

Give a Name to New Disk and define the path as you wish.it will create a virtual disk in particular location.

clip_image007

Size of the virtual disk to be defined in MB.

clip_image008

Give a description for better identification while you work in Console.

clip_image009

Click finish to complete the disk creation.

clip_image010

Direct to Properties of the New Target. You can see here all the settings you given.

clip_image011

all the initiators you added are shown here. Also you can add more initiators if your other hosts need to use this Target (V-SAN)

clip_image012

Virtual disks are shows here in this tab

clip_image013

More Details on the disks are discoverable in root.

clip_image014

Configure Clients (Initiators) via ISCSI Initiator

This can be setup in most operating systems, tool is available in Windows 7 /Server 2008 by default so you don’t need to install this.

For Other Operating Systems = From the download earlier – get the following file for installation

iscsitargetClient_public.msi

Each and every clients should be configured for accessing the Target we created.

Find iSCSI Initiator at administrative tools and get in to the interface shown below.

clip_image015

Click Yes for the verification massage box as you get it once launching this tool for the first time.

Copy Initiator’s Name of the client by Direct to Configuration tab. Initiator Name is the Unique Name for particular client which we need to include in Initiators list in our ‘Target’.

clip_image016

Go back to Target’s Properties and insert this name in to Initiators list.

Click Add to insert

clip_image017

Paste Name Here which you copied from client and click OK.

clip_image018

Go Back to the Client and direct to ‘Discover’ Tab and click Discover Portal.

Give the IP/DNS Name of the ‘Target’, This is the place to connect to Target from clients.

clip_image019

clip_image020

Here will appear you Portal.

clip_image021

Then next is to connect to our Target. Go to Targets tab and it should appear yours as inactive bby default.

clip_image022

Click Connect to continue and click OK to connect

clip_image023

Now status becomes connected as it was success.

clip_image024

Click ‘Auto configure’ in Volumes and Devices tab. What ever the disks are created in your Target should appear here once it’s success.

clip_image025

Also disks are can be viewed via ‘Devices’ in Targets tab as shown below.

clip_image026

Map Disks to clients

Now we can map disks to each clients as required.

Get in to the disk management utility, it will appear in initialization wizard to disks, check for each disk as required and click ‘OK’ get mapped.

clip_image027

That’s all for configuring Client and our new disks are Ready to Rock and Roll……….. !!!!!!

Now You can create volumes as required.

clip_image028

Connect Client Machine to a New(DR) Server–KOFAX CAPTURE SERVER 9.0

Manual Failover configuration – KOFAX CAPTURE 9.0 Client (Purpose – In Case of any failure on existing Kofax application Server, Each and Every Client can be failover manually to a New Server which is already Kofax Installed) ——————————————————————————————————————————————

This is for describe configuration for Kofax application Failover configuration on client/workstation from

Current Server (Production Application Server) to another (DR Server).

I have connected my client to Application Server 1 and Kofax application is up and Running.

What I wanted to do is – Connect client/Workstation to new server which installed as DR (Independent of DB, CaptureSV Folder from production) in totally separate environment using separate Database and CaptureSV Location.

It’s an easy configuration via AcDeployUtil command line tool which is provided by Kofax. Follow these steps to start.

Tool is located at C:\Program Files (x86)\Kofax\CaptureSS\ServLib\Bin, copy this path to clip board

Get in to the Tool using below command.

Cd C:\Program Files (x86)\Kofax\CaptureSS\ServLib\Bin

It will direct in to the tool, then type AcDeployUtil/ServerPath(Parameter):Z:\(UNC/Mapped Name for CaptureSV Folder )

[Here I given mapped folder drive letter as I used by mapping to client]

Eg –

clip_image001

That’s all….!!

And it will appear “Workstation disk image deployment complete once it is successful”.

Open Kofax from client and now it should Work via new server.

Install Kofax Capture 9.0 Server-Client Step by Step

 

Step By Step Kofax Capture Server 9.0 Installation

You will get the following screen once you insert your media, click on “Install Kofax Capture to begin the Installation”.

clip_image001

Click ok to Welcome screen

clip_image002

We have to agree with the license agreement

clip_image003

Select Installation type , here I am going to setup an server.

clip_image004

This location for Installation folder, leave it with C drive default if you are not using another drive/partition for the applications and click next.

clip_image005

Server files Folder contains – Workstation Setup, Batch classes, Batch, and Image file Information. So here im using UNC path of my clustered File server Share Folder as below.

\\KFXCLSTRDFS\KFXFileShareSpace (You need to Map this drive on each Client Workstations once you complete this process).

Click next to proceed.

clip_image006

Database Configuration is the next Option we should define. “Standard” will install with SQL Server Express edition

Here I already have an SQL Server configured on another server clustered it self, I am selecting SQL Server.

Click Next to proceed.

clip_image007

Site Name (Local Machine’s Host Name) and Site ID (Starts from 1) will automatically Pick up. Either you can customize but its better to leave as default for easy identification in the future.

clip_image008

Station ID will pick automatically using your Local machine’s hostname, but it has removed “-” to separate station ID from the Site Name. So I will leave this default also.

clip_image009

Select Manual as login, this may require once it reboot.

clip_image010

Click Next to Start Installation.

clip_image011

Click Ok to System file Update

clip_image012

Setup will take Several minutes.

clip_image013

clip_image014

clip_image015

clip_image016

clip_image017

Provide your Licensing details if you have purchased the product,

Click “Manual” if you have got an temporary license for a short time period.

Hardware key will detect automatically if you have pugged it to the local machine.

I will cancel this as I haven’t got any license at the moment.

clip_image018

Let It Proceed

clip_image019

Database configuration Utility Will appear as below. Provide your Instance Name, Database name

Also the Credentials, Check “Store Batches in SQL Server” And apply.

Here in my Setup I am using an Clustered database Access point (KFXSQLSERVERCLR1).

clip_image020

Click Yes for the verification massage .

clip_image021

I got this error because of windows firewall on DB Server and Kofax Server. Turn off windows firewall for the moment or

Open required ports for Kofax to proceed.

clip_image022

This massage appears once connection is success with the Database Server. Click OK to the massage.

clip_image023

Give a moment for the installation.

clip_image024

We done here with the Server Installation. Click finish

clip_image025

Check on Programs, it will contain all the module as you seeing below.

clip_image026

———————————————————————————————————————————————————–

Install Client Node.

First Step is to Map share folder which we located Client components at the server installation.

Go to My computer and click ‘Map Network drive on Menu. Get the folder mapped to the client Host as figured below.

clip_image027

clip_image028

Folder will Explored automatically once you mapped.

clip_image029

Browse “WrkInst” Folder and run the setup from there.

clip_image030

I have ignored basic steps like license agreement and etc. .

Select the Destination folder for the installation and click next.

clip_image031

Here also it picks up Hostname of the local machine as ID. So leave if for default and click next.

clip_image032

Select Manual Login

clip_image033

Click Next to proceed with the installation.

clip_image034

Click Ok to system file update.

clip_image035

Be Patient Until Installation take you for the next step.

clip_image036

clip_image037

clip_image038

clip_image039

Here We done !

clip_image040

It has been installed required components on the client, so try it Via Administration Module.

All the batches and settings should load as it is which you configured on the Server.

clip_image041