Thanks for the responses guys. We got what we needed through the Admin WebServices - it has a method that allows you to create Sites (CreateSite(...)). Once the site is created we can then use the client object model to assign the necessary permissions and make any other changes we need to the webs etc. Using the PowerShell scripts may have been a last resort, but realised that you needed to use the server object model which we want to avoid. We'll make a note of your suggestions Nathan.
Thanks again. Steve On 21 September 2011 10:20, Nathan Schultz <milish...@gmail.com> wrote: > Hi Steve, > > In regards to the Powershell question - I'm reading between the lines a bit > about your exact requirements. You do not have to use the Sharepoint 2010 > Management Shell. The only difference between Windows Powershell and the > Sharepoint 2010 Management Shell is the Sharepoint providers loaded by > default (Windows.Sharepoint.Powershell). > > The same can be achieved in normal Windows Powershell script by adding the > following to the top of your script: > > Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction > "SilentlyContinue" > > The error action is added in case the script IS run through the Sharepoint > 2010 Management Shell - it won't bomb out. > > Windows.Sharepoint.Powershell is installed with Sharepoint Foundation, but > what might be a sticking point to you is that AFAIK most of the Sharepoint > powershell commandlets will only work with locally installed Sharepoint > Farms (ie, I do not believe you can run them across the network). I'm not > sure why this is an issue - no administrator I know would let a dev even > walk within spitting distance of any server they maintain ;-) All the same, > you can create comprehensive Powershell installation / update / rollback > scripts for your Sharepoint Administrator to run in environments (eg, Prod) > where you typically won't have access. > > Regards, > > Nathan. > > > > On Tue, Sep 20, 2011 at 1:04 PM, Peter Arvoll <ozdot...@dotnetpete.com>wrote: > >> Hi Steve >> >> I have been looking into working with SharePoint sites today (via the web >> services) and I think that I read somewhere that the object model only works >> if you're running on the machine where SharePoint is hosted. >> >> Throwing the question to a wider audience, I have a client who wants to >> move from Exchange group calendars to SharePoint but it seems that to have >> to migrate across I need to add the meeting to the Calendar list (in order >> to display in calendar view) and then create (and link) a meeting workspace >> in order to manage attendees and attachments. >> >> Am I missing something? >> >> Thanks >> Peter >> >> >> On 20 September 2011 13:28, Stephen Liedig <slie...@gmail.com> wrote: >> >>> I think we sorted this. We are using the Admin web services to create the >>> site. We then plan to use the client object model to change the site >>> properties. This should give us what we need. >>> >>> Regards, >>> >>> Steve >>> >>> >>> On 20 September 2011 09:28, Stephen Liedig <slie...@gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> not sure if anyone can help me with this. We need to find a way to be >>>> able to create a SharePoint 2010 Site (Site Collection) only using the >>>> client object model. So far we've managed to create a SP Web, no problem, >>>> but because of the architectural requirements each of these needs a must be >>>> contained in its own Site. At this stage, we want to avoid having to deploy >>>> server side components to do this but realise we may need to change our >>>> approach if using the client object model is not possible. Also, is it >>>> possible to use PowerShell scripts outside of the SharePoint environment? >>>> Any help would be appreciated. >>>> >>>> Cheers, >>>> >>>> Steve >>>> >>>> PS. I know there is probably a SharePoint list but I'm not a member, I >>>> was hoping there a couple of SP experts on this list. >>>> >>>> >>> >> >
