Techies--

I know that SSIS hasn't been designed for clustered environments. In our 2008 R2 environments, we resolved the issue by deploying dtsx and dtsConfig files to a mutual share.  This is our first deployment to a clustered 2012 environment.  I don't want to lose the native reporting features and project parameter environments available in 2012. How do I approach this?

I would suggest reading this:

http://blogs.msdn.com/b/mattm/archive/2012/09/19/ssis-with-alwayson.aspx

Tom,

Are you thinking always on would be an alternative to a cluster setup? Unfortunately, the server configuration as it exists (clustered) is what I have to work with. I don't really need SSIS to failover as I would other more failover friendly/assigned resource--I just need it to get installed to the SSIS integration catalog.  

For those following this thread:

Don't make it any harder than need be. Follow the instructions under 

SSIS MSDN Clustering Instructions - 2012 and up

• Marked as answer by ditallop 12 hours 48 minutes ago

For those following this thread:

Don't make it any harder than need be. Follow the instructions under 

SSIS MSDN Clustering Instructions - 2012 and up

• Marked as answer by ditallop Friday, September 11, 2015 6:16 PM