I recognize this could be a odd mix, yet if you ever need to mount VMWare vCenter 4.0 and also MS SQL consisting of Coverage Solution on the very same maker (Home windows Web server 2008 64 Bit), this is exactly how it’s done. Be advised, VMWare will at some point not assistance this setup, yet I had no problems keeping that approximately this factor.
VMWare vCenter calls for a SQL data source (SQL 2005 or SQL 2008 at the moment of this composing). While you can utilize a remote data source we had the require for a regional setup in addition to we required SQL Web server Coverage solution set up. After setting up the Home windows Running System we did a complete mount of SQL Web server 2005 consisting of SP3. We did attempt this with SQL 2008 previously, yet SQL 2008 is not utilizing IIS to handle the Coverage Solutions which made it extremely hard to handle the 2 applictions and also their ports that they utilize (tip: overlapping ports are 80 and also 443).
After you set up SQL 2005, you can mount vSphere vCenter 4. Throughout the setup you can alter the ports that vCenter makes use of, nonetheless this doesn’t work. SQL Record Solutions demands port 443 for inner interaction. I had transformed the port in vCenter to 444 when utilizing SQL 2008, yet obviously vCenter overlooks that port establishing and also still locks port 443 later on one – production Coverage Solutions kaput. So, mount vCenter with the default ports.
Currently enter into IIS (tip: SQL 2005 calls for that you mount ALL IIS products in Web server 2008) and also alter the port for the coverage solutions to port 81. There’s no have to touch port 443 to obtain MS SQL Coverage Solutions to work. Currently open the Record Solutions Setup device and also choose the Internet Solution Identification tab. Establish the appPool to “Traditional.NET” for the Record Web server and also the Record Supervisor.
MS SQL Coverage solutions must work simply great as lengthy as you define the new port in the URL when accessing the records.
Why did SQL 2008 not help me? SQL 2008 Record Solutions does utilize HTTPS traffic a lot more compared to SQL 2005 does. Since VMWare vcenter locks that port (also if you inform it not to), SQL 2008 Coverage Solutions will not operate correctly.