MOSS 2007 Enterprise - InfoPath Dev
in

InfoPath Dev

MOSS 2007 Enterprise

Last post 10-10-2009 05:23 AM by warrtalon. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 10-09-2009 10:36 AM

    MOSS 2007 Enterprise

    We are finally moving from WSS 3.0 to MOSS and our implementation guys actually came to me to ask if there were any features that I wanted them to make sure that were 'turned on' during the implementation.  After I picked my jaw up - first i couldn't believe that we were finally making the move and second that they wanted my input - I started looking into it.  Does anyone here have any suggestions?  I know that it is a broad question, but if anyone has any feedback from their migration that may help out, I'd greatly appreciate it.

    Fishman
  • 10-10-2009 05:04 AM In reply to

    Just as an FYI, I would say that the question is not relevant to InfoPathDev unless your company is moving to MOSS Enterprise.  Do you know if it is going to be MOSS Enterprise or MOSS Standard? Enterprise includes Forms Services, which then allows you to do browser-enabled forms.  MOSS Standard does not, but at least you will have a Shared Service Provider (SSP) that will expose some nice web services for you to use in your rich client InfoPath forms. When install MOSS, I'm not it's a valid question to ask which features you would want to turn on.  For the farm, all of the "features" (these are actual things in MOSS that get activated/deactivated) are already activated at the web application level.  It then depends on the type of site collection you create, because each template has its own INSTALLED and ACTIVATED feature set. Even after you create a site, you can go activate all the extra features that weren't activated by default.

    So, in terms of things that you want to be toggled or configured (not features)and assuming you were asking the question in regards to InfoPath, I would recommend this:

    - If it's MOSS Enterprise, be sure they go to Central Admin > App Mgmt > Configure InfoPath Forms Services > Check all the checkboxes that the company will allow.  You need to look at them and decide on the one you want, or if they refuse to allow some, then you need to know it, becuse it could hamper your useof InfoPath

    - Ensure it gets architected properly with the web apps inside an SSP and that all users have Read rights on the Personal Features permission of Personalization Services Permissions

     

  • 10-10-2009 05:17 AM In reply to

    Hello Calyton.

    Thank you for the response.  It is MOSS Enterprise that we will be migrating to.  This is exactly the kind of response that I was looking for.  I have been struggling with WSS 3 for a couple of years now and every time I try to build a solution, I keep hearing how much easier it would be if we were on MOSS Enterprise.  Unfortunately, I do not know much about SharePoint and our SP guys think that IP is Black VooDoo Magic, so we often find ouselves speaking a different language.  Hopefully with your input we can get this thing done and make everyone's life a bit easier.  Thanks again for your feedback, it is greatly appreciated.

    Don F.

    Fishman
  • 10-10-2009 05:23 AM In reply to

    I don't know that anything is easier because of Enterprise unless you're talking about browser-enabled forms, and those are MUCH harder to deal with than rich client forms, but they give you more flexibility.  I have a lot of experience with browser forms, so I can help along the way.  Be sure you're familiar with each of my blog posts before you get started.

Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.