none
Sharepoint 2013 in Workgroup w/ PowerView Reports

    Question

  • Is it possible to install Sharepoint 2013 in a wokgroup instead of joining it to a domain. What I would like to accomplish is to have Sharepoint 2013 in a workgroup and be able to publish PowerView reports via Excel 2013 to the PowerPivot Gallery I would also like to give access to these reports. Is the above possible in a workgroup or is this scenario only doable in a domain enviroment.

    Thanks..

    samedi 19 janvier 2013 02:37

Réponses

  • It is technically possible, although you have to put in a lot of effort to achieve this. You will need to pull off permissions as well, and you will face many scenarios that fail due to authentication problems. But with enough time on your hands you could technically do it.

    In production, however, this is not a supported scenario: http://support.microsoft.com/kb/2764086/en-us?wa=wsignin1.0

    You must install SP2013 on domain-joined machines if you want the deployment to be usable. That said, your identities can come from a lot of other places.

    If you are just doing POC's, make use of SP2013 trial versions.

    HTH!


    Independant SharePoint Consultant. Feel free to contact me. Blog: http://www.sharepoint.bg/radi Twitter: @RadiAtanassov

    • Marqué comme réponse Gdelgado_MM mardi 29 janvier 2013 18:43
    dimanche 20 janvier 2013 16:49
  • For your scenario it would be cheaper (and supported!) to do this in Office 365. No matter how much effort you spend on doing sharepoint in a non-domain environment on premise it's going to be a bad experience. People will always get prompted for credentials, you are spending a lot of money, as well as on hardware and licensing. Not to mention support. Just use Office 365 so much easier and supportable for your scenario.

    My CodePlex - My Blog - My Twitter

    • Marqué comme réponse Gdelgado_MM mardi 29 janvier 2013 18:43
    dimanche 20 janvier 2013 20:30

Toutes les réponses

  • It is technically possible, although you have to put in a lot of effort to achieve this. You will need to pull off permissions as well, and you will face many scenarios that fail due to authentication problems. But with enough time on your hands you could technically do it.

    In production, however, this is not a supported scenario: http://support.microsoft.com/kb/2764086/en-us?wa=wsignin1.0

    You must install SP2013 on domain-joined machines if you want the deployment to be usable. That said, your identities can come from a lot of other places.

    If you are just doing POC's, make use of SP2013 trial versions.

    HTH!


    Independant SharePoint Consultant. Feel free to contact me. Blog: http://www.sharepoint.bg/radi Twitter: @RadiAtanassov

    • Marqué comme réponse Gdelgado_MM mardi 29 janvier 2013 18:43
    dimanche 20 janvier 2013 16:49
  • For your scenario it would be cheaper (and supported!) to do this in Office 365. No matter how much effort you spend on doing sharepoint in a non-domain environment on premise it's going to be a bad experience. People will always get prompted for credentials, you are spending a lot of money, as well as on hardware and licensing. Not to mention support. Just use Office 365 so much easier and supportable for your scenario.

    My CodePlex - My Blog - My Twitter

    • Marqué comme réponse Gdelgado_MM mardi 29 janvier 2013 18:43
    dimanche 20 janvier 2013 20:30
  • Thank you for the answers now with this information it will be easier going forward with a solution.

    Thanks..

    mardi 29 janvier 2013 18:43