Generic Services are pretty simple to setup. You need to make sure the relevant service is installed on all nodes in the cluster. If the service needs some resource (such as disk) that is in a cluster group, then it will need to be in that group; otherwise, you can stick it in whatever group you want. The generic services I have had to setup in the past are simply installed on the C: drive, and no dependencies are really necessary. Set the service to manual on all nodes, and then add it into cluster administrator.
Bill Mayo -----Original Message----- From: Ziots, Edward [mailto:[email protected]] Sent: Wednesday, July 28, 2010 2:43 PM To: NT System Admin Issues Subject: Clustering a NON_cluster aware service? Got another one of those screw ball requests, DBA put a non-cluster aware service on one node of the SQL Server Cluster, and didn't tell us about it, now he wants it to be a cluster aware service with its own Group, drive, ect etc. I haven't had to do a Generic Service before and with everything going on, my google-fu is failing me, and M$ doesn't have jack$hit that I can find on a step by step procedure to install this POS as a generic service. I was thinking from what I remember, I can either use the MSDTC group or Quorum or SQL group on the cluster for the generic service, and I think I need the drive letter the service is installed on, as a dependency accordingly. OR do you need to install the application to the same drive on both nodes and then make it a clustered service? Z Edward E. Ziots CISSP, Network +, Security + Network Engineer Lifespan Organization Email:[email protected] Cell:401-639-3505 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
