« Spring Church IT Roundtable - Mark Your Calendar | Main | Spam volume on the rise globally! »

November 20, 2006

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Jason,

I can't wait to give it try myself. I had the 2.0 up and running for awhile, testing it for our intranet, but I felt it was lacking. Then I read about the changes in 3.0 and had been looking forward to it. I didn't know it was out of beta until your post.

Any modules you find useful, yet?

Enjoy and I hope it works out!

I have absolutely no idea what you are talking about. I clicked on to "DUSTIN" and also had no idea what he was talking about.
But apparently it's pretty awesome, helpful, and will be valuable in these next few months.

You rock, even though I have no idea what you are talking about.

Can you play Pong on it?

I've looked at WSS off and on for quite some time. As you go about enabling your "several hundred" volunteers, I'd love to hear about your thougts on the following topics:

1) Which version of SQL server are you using? How did you license it? Per CPU? Per User?

2) Do you need Win 2k3 CALs for each named user in your "Volunteer" OU?

3) How are you doing backup for WSS?

4) Do you consider anti-virus solutions for WSS necessary?

5) What tools do you use to customize WSS?

6) Did you give church email addresses to the volunteers?

Bryan - Jason will have a better followup with some links on licensing. There are a couple of gotchas. Here are my thoughts on 3 - 5

3. The new version of WSS includes a recycle bin. The amount of time an object is retained in the recycle bin is configurable from both an end user standpoint and a sharepoint admin standpoint. Sharepoint also includes the stsadmin utility which can be used to backup the full site collection. Now with all of that fun marketing stuff out of the way the best solution is a combination of the Microsoft tools and 3rd party solutions. Veritas and CommVault both provide good backup solutions for Sharepoint but will cost you where the Microsoft solutions are free. Look for more options with the next release of Microsoft Data Protection Manager now in beta.


4. Within Sharepoint you can prevent certain file extensions from being uploaded and this may be acceptable today but I think your best bet is to check out the new upcoming ForeFront Security for Sharepoint. I would suspect 3rd party guys will also participate in this arena.


5. Jason will have to answer this for what he plans to use but Sharepoint Designer (aka the new Frontpage) is the Microsoft Answer to customization. You can also use the .Net development suite to do customizations. Note Microsoft does not support making direct changes to sharepoint SQL tables, views, etc.

Bryan ... here's a couple answers for ya

1) We're using our existing SQL2000 server. We already had per processor licensing ... but yes, you either have to do that or get 1 SQL cal per sharepoint user.

2) Anyone you put in AD needs a server cal. However, it appears you can purchase a one time connector license ($600) that sounds like it covers an unlimited number of "external" users. We're still trying to decifer the licensing, but that's certainly the way we read it.

3) We're still investigating the best way to back it up ... but we're leaning towards the veritas sharepoint module.

4) Good question. Given all our other antivirus layers I guess at this point I'm going to not add another AV layer ... but it's certainly worth pondering some more.

5) I'm guessing we'll use the new sharepoint designer ... very little $

6) No, volunteers will not be getting gcc email accounts.

It's still a work in progress, but I'll post more once we get a good test site developed.

The comments to this entry are closed.

My Photo

Disclaimer

  • Jason Powell is the Information Technology Director at Granger Community Church. The views and opinions expressed here are not necessarily those of GCC ...
    or are they? Hmm???

Your email address:


Powered by FeedBlitz

Twitter Updates

    follow me on Twitter