SQL for 3 server topology
- Hello.
I'm trying to deploy FFCS in 3 server topology. We have a server with SQL Ent. installed, and another one with WSUS, so I think the 3 server topology is the best choice.
The reporting database server role require SQL Std./Ent. - that's ok. But the Management, collection and reporting server role require one more SQL Std./Ent.
My company is an MS Golden Partner, so we have limited licenses for SQL server. If you buy the FFCS, you get the licence for SQL Ent. included to the FFCS license, but in the case of MS Golden Partner internal use rights it is not the same. Golden Partner should use the licence for SQL Ent. granted for internal use.
And it may be OK for all-in-one topology, but looks bad for 3 and more server topology.
All SQL licenses for internal use are utilised. Do anybody know how to solve this problem without payments. The installation of the FFCS on the server with SQL Ent. thet i'm going to use for the reporting database server role is restricted.
Best regards
Answers
Hi,
Thank you for your update.
“Error: Could not access this address: http://scom/ReportServer”
This information indicate that the server failed to connect SCOM. Yes , you can use SCOM 2007 to monitor FCS v1 servers. But it is no supported methods to interface FCS v1 data to SCOM.
Regards,
Nick Gu - MSFT- Marked As Answer byNick Gu - MSFTMSFT, ModeratorTuesday, November 03, 2009 1:35 AM
All Replies
Hi,
Thank you for your post.
I think you would probably be better talking to either your local MS sales rep or whomever you normally deal with for licensing.
Thank you for your understanding.
Regards,
Nick Gu - MSFT- I have an idea.
May be I can solve my problem If i use this kind of topology:
1 server: Reporting+Reporting database+Collection database server (SQL Std./Ent. required)
2 server: Collection+Management server (SQL Std./Ent. not required)
3 server: Distribution server (SQL Std./Ent. not required)
This kind of installation was not described in Deployment guide.
Is this scheme functional? Hi,
Yes, you can deploy FCS with this topology. And you should pay attention to the network ports and protocols that are used for communicating between Client Security servers. For more information, please refer to this link: http://technet.microsoft.com/en-us/library/bb404251.aspx
Regards,
Nick Gu - MSFT- Proposed As Answer byNick Gu - MSFTMSFT, ModeratorFriday, October 30, 2009 2:59 AM
- Hello, thank you for reply.
I started to install FCS in my topology.
The first step is installation of Reporting+Reporting database+Collection database server to the server wich have an SQL Ent. SP3 and SCOM.
(I found thet FCS can coexist with SCOM: http://social.technet.microsoft.com/Forums/en-US/Forefrontclientsetup/thread/fe03848e-9c08-40b8-9fa7-302c4e86b560)
And I have got an issue during verifications. All points OK except one:
[10/28/2009 3:13:58 PM] Verification(Verifying URLs for reports)
Error: Could not access this address: http://scom/ReportServer
Details: The remote server returned an error: (500) Internal Server Error.
The permittions for this URL were correctly specified, and i can open this url by browser under account specified as DAS.
All prerequisites looks good, what is the problem?
Best regards Hi,
Thank you for your update.
“Error: Could not access this address: http://scom/ReportServer”
This information indicate that the server failed to connect SCOM. Yes , you can use SCOM 2007 to monitor FCS v1 servers. But it is no supported methods to interface FCS v1 data to SCOM.
Regards,
Nick Gu - MSFT- Marked As Answer byNick Gu - MSFTMSFT, ModeratorTuesday, November 03, 2009 1:35 AM
