I was under the impression that like the current version of Forefront if you did not have one of the System Center products it would install a cut down version that only dealt with Forefront. From what I saw on my installation the reason for SQL WAS the MOM package. I just hope that Sterling will work with SCE. I have that up and running now. I would not mind doing a re-install when Streling is released IF it works well together. The down side is that Sterling is supposed to go Gold about the time for our renewal. Man I would really hate to be one of the first to roll that package.
Jon On Fri, May 1, 2009 at 9:55 AM, Joseph L. Casale <[email protected]>wrote: > Yeah, > > I read some more last night. The component that manages non server clients > needs SQL 2005. The console that could only manage server components can use > SQL2000+ and Express. > > > > What’s worse is the Beta for the next version needs SQL and SCOM from what > I read. > > > > Lame… > > jlc > > > > *From:* Jon Harris [mailto:[email protected]] > *Sent:* Friday, May 01, 2009 6:50 AM > *To:* NT System Admin Issues > *Subject:* Re: Forefront > > > > Try and install a working version without the full SQL. > > > > Jon > > On Thu, Apr 30, 2009 at 4:52 PM, Joseph L. Casale < > [email protected]> wrote: > > >I was just not happen that our resellar did not make the SQL > requirement clear up front. > > > > I am just reading the installation Guide and it suggests: > > “SQL Server 2005 Standard Edition (and above), SQL Server 2005 Express > Edition, or SQL Server 2000” > > > > You have more than 2000 users? I saw somewhere that 2000 users was the > limit I think for Express… > > That would make this cheap? $100.00 per console, and $13.00 per client. > > > > jlc > > > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
