Avatar of isaackhazi
isaackhazi
 asked on

how to cluster two servers and an iSCSI NAS drive to create a cloud server?

i have two servers running windows server 2008 r2 enterprise with 2 NIC cards on both, and i have an iSCSI NAS storage drive (RAID1) with 2 gigabit ports.
my objective is to create a cloud server (running windows server 2008 - any version) which will share resources from both servers and use the iSCSI storage drive as its hard disk. the idea is that when one server is unavailable, the cloud server will switch to the other other for resources and vice verca.

the idea in my head is that both the servers will use NIC1 to connect to domain network, and NIC2 from both the servers will be directly connected to the 2 gigabit ports on the NAS storage drive.

so, how do i set this cloud server up with the intention described above? i cannot find any articles or tutorials on how to accomplish this anywhere on the net. or maybe i'm using the wrong keywords. what exactly do you call this setup in the first place?

your help is much appreciated.

thanks
Windows Server 2008VirtualizationStorage

Avatar of undefined
Last Comment
isaackhazi

8/22/2022 - Mon
Imal Upalakshitha

isaackhazi

ASKER
i've seen tutorials to set up application server, but i'm looking to set up a whole cloud operating system using the NAS storage and  physical resources from both the servers. can you confirm if the links you've provided for the virtual lab cover my objective?
charles_lawrence

are you referring to a cloud computing or just windows 2008 cluster service with iscsi nas storage?
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
isaackhazi

ASKER
i've made a diagram using painbrush (please forgive me for my lack of artistic talent) to illustrate what i'm hoping to achieve.
cloud.jpg
isaackhazi

ASKER
and eventually, I want this cloud operating system to be able to access and join the domain network which both the servers are directly connected to.
isaackhazi

ASKER
@charles_lawrence,

honestly, i'm not sure what this setup is called.... what does the above diagram tell u?
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
kevinhsieh

This is not a 'cloud' setup. From what I can tell, you are trying to put together a standard high availability cluster for a Windows Server virtual machine. The VM can run on any of the physical nodes in the cluster. The VM can be non-disruptively moved from one node to another in a planned fashion, or it can fail over (reboot) on a different node if the host it is running on should crash. To get started, install Hyper-V and the Windows Clustering service on each physical server. Then provision some storage on your iSCSI SAN and connect each host to it. Run the Cluster wizard to create your cluster. You can then create a VM on the cluster.
isaackhazi

ASKER
exactly!! that was what i had planned to do as well. install hyper-v on both servers, create clusters and then install the VM on the clusters. but I couldnt find any documentation on installing the VM after that.

can you guide me through the whole thing or point me to some online tutorial on how to go through with this? I've never used hyper-v before.

I've setup one of the servers with ms server 2008 r2 enterprise. the other i'm currently setting up with the same operating system. and will install hyper-v on both of them. now will the servers detect the NAS without static ip configuration? should they be of different subnet from the domain network?
charles_lawrence

Why do you need HyperV on the server, you can install Windows OS directly on the server without installing VMs on it.

is this a test environment? if yes, then even in a laptop computer you can test this. mine is Core2 Duo with 4 gb mem/ win7 x64 bit OS but it is working.

I created 4 OSes:
Win2k8 AD
Win2k3 for iSCSI software- http://www.kernsafe.com/download.aspx
Win2k8 Node1 (2 nics)/ 1 private (Heartbeat)/ 1 Public (LAN)
Win2k8 Node2 (2 nics)/ 1 private (Heartbeat)/ 1 Public (LAN)

You need atleast 5 Static IPs
2 for each node + 1 for Cluster IP

Plus ofcourse if you are planing to install exchange or sql apps then you need additional IPs.

This is the good document for Windows 2008 + KernSafe iscsi storage server
http://www.kernsafe.com/tech/iStorage-Server/iStorage-Server-iSCSI-SAN-for-Windows-Clustering.pdf

I hope this help.




This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
kevinhsieh

Hyper-V: Using Hyper-V and Failover Clustering
http://technet.microsoft.com/en-us/library/cc732181(WS.10).aspx

Applies To: Windows Server 2008, Windows Server 2008 R2

This guide walks you through the steps required to set up Hyper-V™ and the Failover Clustering feature to use these two technologies together.

isaackhazi

ASKER
@charles lawrence,

this is a test environment. i have two old poweredge servers we no longer use for any particular service. so i've installed server 2008 r2 enterprise on both the servers. given them static addresses. dont i have to install hyper V on both of them now inorder to make this cloud OS or whatever it is called?

also, i dont understand why u created 4 OSes. Dont we need just three? i mean 2 server 2008 on the 2 servers and the cloud server 2008? why do u have the 2003 server and where do i install it?

thanks. sorry for the delay. long weekend here.
isaackhazi

ASKER
@kevinhsieh..

thanks for the technet article link... i'm going through it right now.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
charles_lawrence

This is NOT a cloud computing. This is just a Failover Cluster FEATURE of Windows 2008 Server.

"also, i dont understand why u created 4 OSes. Dont we need just three? i mean 2 server 2008 on the 2 servers and the cloud server 2008? why do u have the 2003 server and where do i install it?"

You are asking:
 i dont understand why u created 4 OSes. Dont we need just three?

This is SETUP 1 of the attached Diagram:
Win2k8 AD - For your Active Directory
Win2k3 for iSCSI software- http://www.kernsafe.com/download.aspx--> This will be your iSCSI NAS target (Member server)
Win2k8 Node1 (2 nics)/ 1 private (Heartbeat)/ 1 Public (LAN)
Win2k8 Node2 (2 nics)/ 1 private (Heartbeat)/ 1 Public (LAN)

why do u have the 2003 server and where do i install it?
iSCSI software is a small piece software that you will install in any machine in your network that can play the role of iSCSI Target Server. You may want to try to install it in your AD (Setup 2 of Diagram).

This is the requirement for kernsafe iscsi storage: http://www.kernsafe.com/product/istorage-server/requirements.aspx

Diagram.JPG
kevinhsieh

You can also use the free Microsoft iSCSI Target 3.3 Software on Windows 2008 R2 to create your SAN.

http://www.microsoft.com/download/en/details.aspx?id=19867
isaackhazi

ASKER
@charles,

i'm slightly confused now. If both the nics of the iSCSI NAS are connected to the 2nd NICs of the 2 node servers, then how will the iSCSI Target server find it? Secondly, why do we have to install the iSCSI target software on a server other than the node servers?

also, as per kevin's comment above, can I use the microsoft iSCSI Target? coz the iSCSI NAS i have is a Cisco NAS : http://www.cisco.com/en/US/products/ps10853/index.html
will the kernsafe software work for the NAS i'm using?

i'm already in an AD environment and all Domain controllers we have are on server 2008, no server 2003 here.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
charles_lawrence

:) im sorry i didnt label the switch in between servers.

"why do we have to install the iSCSI target software on a server other than the node servers?"
kernsafe developed a very nice software like iSCSI target software.. it is just like NAS storage box.. the installation is straight forward.. just create partitions in your server (iscsi target server) then enable it in iscsi software. just refer on the link that i gave to you. read and read
http://www.kernsafe.com/tech/iStorage-Server/iStorage-Server-iSCSI-SAN-for-Windows-Clustering.pdf

No problem. if you dont like 2003 you can install the iscsi software in windows 2008 server as well..
isaackhazi

ASKER
ok... i get it now... i'll read the kernsafe manual and try it out that way...

but since i bought the cisco NAS anyway, cant I use it somehow as the NAS storage box for the VM?
andyalder

Don't you already have an iSCSI target? "i have an iSCSI NAS storage drive (RAID1) with 2 gigabit ports."
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
isaackhazi

ASKER
i have a iSCSI NAS with 2 gigabit port as I'd shown in my diagram

I have a question now. I installed Hyper-V on both the servers. However, I cannot install Failover clustering feature on one of the servers. The other one, I opened server manager, add features, I selected Failover clustering and it installed fine and later I was able to create a cluster as well. But on the second server, after installed Hyper-V and restarting, I open server manager, add features, Failover Clustering feature is not even listed there. Why is this happening on the second server when I followed the same steps I used on the first serveR?
isaackhazi

ASKER
also, on the second server where I cannot find the failover clustering feature, there are lots of error logs under Hyper-V role. most of them shows this:
"Failed to register service principal name."

i copied the complete log file here:


Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          8/18/2011 2:38:55 AM
Event ID:      14050
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      xxxxcluster2.xxxx.local
Description:
Failed to register service principal name.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
    <EventID>14050</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2011-08-18T09:38:55.770514600Z" />
    <EventRecordID>52</EventRecordID>
    <Correlation />
    <Execution ProcessID="1292" ThreadID="1780" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>prtrcluster2.PRTR.local</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
    </VmlEventLog>
  </UserData>
</Event>
andyalder

#First thing to check is DNS settings on the server that's giving those errors, e.g. what happens when you do ipconfig /registerDNS? Can you resolve host with forward and reverse lookups?
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
isaackhazi

ASKER
dns is fine i guess.... its on static ip, but it can find other servers and pcs on the domain, connect to the internet etc.

upon issuing the command ipconfig /registerdns, it shows this:

C:\>ipconfig /registerDNS

Windows IP Configuration

Registration of the DNS resource records for all adapters of this computer has b
een initiated. Any errors will be reported in the Event Viewer in 15 minutes.
charles_lawrence

Hi isaackhazi, i cant understand why you still pushing to install Hyper-V in each server  since you can install Windows 2008 OS in each node directly.

With regards on your situation right now, please plan your settings/ configuration/ connection PROPERLY on each server in your network before implementing it.

before you install any features/ application be sure you can access your AD/ DNS. In cluster environment, be sure you can ping each other IPs- private (heartbeat) - public (LAN), AD/DNS, your domain user account to be use in cluster, permission, iSCSI target server IP, theres a number of prerequisite in building a cluster be aware of it and do it properly before you install a cluster to eliminate any problem during your actual implementation.
isaackhazi

ASKER
i installed server 2008 OS on each node servers already... and correctly me if i'm wrong, but I was under the impression that I need hyper-v role installed on these two servers and then create a cluster on both the servers to install the VM failover server on both nodes?
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
isaackhazi

ASKER
i'll tell u the settings on both the servers:

xxxxcluster1
joined domain
NIC1: static IP: 192.168.0.241 (same subnet as all other servers and PCs on domain)
can access internet, connect to other servers and pcs on network
able to install hyper-v role and then failover clustering feature (from server manager)

xxxxcluster
joined domain
NIC1: static IP: 192.168.0.243 (same subnet as all other servers and PCs on domain)
can access internet, connect to other servers and pcs on network
able to install hyper-v role, but cannot find failover clustering feature under "Add features" section (from server manager)


i've not set the heartbeat network on NIC2 on both servers yet as I'm unclear what subnet should be on, eg: do I have to give IP address 192.168.0.242 or 192.168.1.242 or some other subnet
isaackhazi

ASKER
the second server's name is xxxxcluster2
ASKER CERTIFIED SOLUTION
charles_lawrence

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
isaackhazi

ASKER
charles, in the above picture you've uploaded, where is the NAS? In the picture I'd initially upload in the beginning of this webpage, you can see that I have a NAS with 2 gigabit ports which i specifically bought to use in this project. where does that go in?

you seem to have replaced the NAS with an actual server running windows server 2003/2008 and using it as an iSCSI target.
Your help has saved me hundreds of hours of internet surfing.
fblack61
andyalder

Charles' NAS is the server at the top. His happens to be running Windows plus iSCSI target but it could be anything you liked. It isn't highly available which defeats the purpose of having redundant servers in front of it somewhat.
isaackhazi

ASKER
i've picked up a cheap NAS... as this is for testing purposes... from Cisco... NSS 322... with 2 Hard-disk bays on RAID1... and two gigabit ports each of them connected to the second NICs for the two servers i have. now how do i go about setting up with virtual OS which can switch between each node while one of them is down or unavailable? thats what i'm looking for.
andyalder

It goes at the top of Charles' diagram in place of the Windows 2008/iSCSI server.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
isaackhazi

ASKER
yes... okay, i get that much... now do i have to install the iSCSI target software on any of the servers?

also, why am i unable to install failover clustering feature on one of the servers as i'd posted previously?
isaackhazi

ASKER
Since i cant find the option to install "failover clustering" feature through Server Manager > Add Features, i tried installing by running the following command line:

dism /online /Enable-Feature /Featurename:FailoverCluster-FullServer

but it did not work, gave me this error:

Error: 0x800f080c

Feature name FailoverCluster-FullServer is unknown.
A Windows feature name was not recognized.
Use the /Get-Features option to find the name of the feature in the image and tr
y the command again.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

this is the log entry pertaining to this action from the dism.log file:


2011-08-24 12:05:50, Info                  DISM   PID=3068 Scratch directory set to 'C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\'. - CDISMManager::put_ScratchDir
2011-08-24 12:05:50, Info                  DISM   PID=3068 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Manager: PID=3068 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM.EXE:
2011-08-24 12:05:50, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2011-08-24 12:05:50, Info                  DISM   DISM.EXE:
2011-08-24 12:05:50, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=2
2011-08-24 12:05:50, Info                  DISM   DISM.EXE: Executing command line: dism  /online /Enable-Feature /Featurename:FailoverCluster-FullServer
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=3068 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Manager: PID=3068 Successfully loaded the ImageSession at "C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337" - CDISMManager::LoadImageSession
2011-08-24 12:05:50, Info                  DISM   DISM Image Session: PID=2232 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Loading Provider from location C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Connecting to the provider located at C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:50, Info                  DISM   DISM OS Provider: PID=2232 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2011-08-24 12:05:50, Info                  DISM   DISM OS Provider: PID=2232 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Loading Provider from location C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Connecting to the provider located at C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Getting Provider OSServices - CDISMProviderStore::GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Loading Provider from location C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Warning               DISM   DISM Provider Store: PID=2232 Failed to Load the provider: C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Manager: PID=3068 Image session successfully loaded from the temporary location: C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337 - CDISMManager::CreateImageSession
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Getting Provider OSServices - CDISMProviderStore::GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2011-08-24 12:05:50, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_SUCCESS
2011-08-24 12:05:50, Info                  DISM   DISM.EXE: Target image information: OS Version=6.1.7601.17592, Image architecture=amd64
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Loading Provider from location C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Connecting to the provider located at C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:50, Info                  DISM   DISM Provider Store: PID=2232 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:50, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2011-08-24 12:05:50, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_SUCCESS
2011-08-24 12:05:50, Info                  DISM   DISM Package Manager: PID=2232 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2011-08-24 12:05:50, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2011-08-24 12:05:50, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_SUCCESS
2011-08-24 12:05:51, Info                  DISM   DISM Package Manager: PID=2232 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2011-08-24 12:05:51, Info                  DISM   DISM Package Manager: PID=2232 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Loading Provider from location C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Connecting to the provider located at C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Loading Provider from location C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Connecting to the provider located at C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Loading Provider from location C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Connecting to the provider located at C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:51, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2011-08-24 12:05:51, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe" : got STATUS_SUCCESS
2011-08-24 12:05:51, Info                  DISM   DISM OS Provider: PID=2232 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2011-08-24 12:05:51, Info                  DISM   DISM Driver Manager: PID=2232 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Loading Provider from location C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Connecting to the provider located at C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Loading Provider from location C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Connecting to the provider located at C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Loading Provider from location C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Connecting to the provider located at C:\Users\ADMINI~1.PRT\AppData\Local\Temp\2\7CD4D4A3-8345-4443-B0DA-F9EDBA84E337\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2011-08-24 12:05:51, Info                  DISM   DISM Transmog Provider: PID=2232 Current image session is [ONLINE] - CTransmogManager::GetMode
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2011-08-24 12:05:51, Info                  DISM   DISM Package Manager: PID=2232 Processing the top level command token(enable-feature). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2011-08-24 12:05:51, Info                  DISM   DISM Package Manager: PID=2232 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2011-08-24 12:05:51, Info                  DISM   DISM Package Manager: PID=2232 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2011-08-24 12:05:51, Info                  DISM   DISM Package Manager: PID=2232 Encountered the option "featurename" with value "FailoverCluster-FullServer" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
2011-08-24 12:05:51, Info                  DISM   DISM Package Manager: PID=2232 Encountered an unknown option "featurename" with value "FailoverCluster-FullServer" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
2011-08-24 12:05:51, Error                 DISM   DISM Package Manager: PID=2232 Failed to get the Update through CBS. - CDISMPackage::Internal_OpenFeature(hr:0x800f080c)
2011-08-24 12:05:51, Error                 DISM   DISM Package Manager: PID=2232 Failed to get the underlying CBS Feature - CDISMPackage::OpenFeature(hr:0x800f080c)
2011-08-24 12:05:51, Error                 DISM   DISM Package Manager: PID=2232 Feature name FailoverCluster-FullServer is unknown. - CPackageManagerCLIHandler::Private_GetFeaturesFromCommandLine(hr:0x800f080c)
2011-08-24 12:05:51, Error                 DISM   DISM Package Manager: PID=2232 Unknown features were specified on the command-line. - CPackageManagerCLIHandler::Private_GetFeaturesFromCommandLine(hr:0x800f080c)
2011-08-24 12:05:51, Error                 DISM   DISM Package Manager: PID=2232 Failed to get the Feature List from the command line. - CPackageManagerCLIHandler::Private_ProcessFeatureChange(hr:0x800f080c)
2011-08-24 12:05:51, Error                 DISM   DISM Package Manager: PID=2232 Failed while processing command enable-feature. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f080c)
2011-08-24 12:05:51, Info                  DISM   DISM Package Manager: PID=2232 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2011-08-24 12:05:51, Info                  DISM   DISM Image Session: PID=2232 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Package Manager: PID=2232 Finalizing CBS core. - CDISMPackageManager::Finalize
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=2232 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2011-08-24 12:05:51, Info                  DISM   DISM.EXE:
2011-08-24 12:05:51, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2011-08-24 12:05:51, Info                  DISM   DISM.EXE:
2011-08-24 12:05:51, Info                  DISM   DISM Image Session: PID=3068 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=3068 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=3068 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2011-08-24 12:05:51, Info                  DISM   DISM Provider Store: PID=3068 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
isaackhazi

ASKER
sorry guys.... dont bother reading the above logs... i finally figured out why i was facing this issue...

turns out, i had installed server 2008 r2 standard on the second server by mistake... i'm installing enterprise now... will let you know how it turns out..
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck