![]() The script also outputs the admin credentials and the sites that were created:Ĭredentials: corp\spadmin Password: ********* Once the whole script has run (warning can take a couple of hours) you can RDP into the VMs … or, just navigate to the default Sharepoint site that is configured. ![]() Nice! I opted for the SingleVMs option … so 3x VMs in total.Īll those VMs sit on a Virtual Network that is also configured for you: I wont get into all the steps for how to set up and run the scripts as that is well documented:Īfter you run the scripts you end up with a fully configured SP Farm running in Azure. My CredSSP setup failed because the Windows Remote Management service wasn’t running. The PowerShell all runs on your client machine and uses the Azure PowerShell Cmdlets to remotely setup Azure etc… Getting your machine setup before you run the scripts is a little tricky as it uses CredSSP for delegation which requires some manual setup, but if you follow the Wiki word for word you should be fine ( here). So I did! and I have to say it totally rocks! I watched the session in the online recordings after the TechEd and it interested me enough to try it out. Highly Available – 9 Vms (DC x2, SQL x2, 1 Quorum VM, SP App servers x2, SP WFE x2). ![]() ![]() Single VMs – 3 VMs (DC, SQL and SharePoint).They let you build out two farm types right now: The “ SharePoint 2013 Automated Deployment Master Scripts” is a set of scripts that you can grab from GitHub that will automate end to end the process of creating, configuring and setting up SharePoint in Azure IaaS VMs. One of the things they talked about was a set of PowerShell scripts that they have built to fully automate this process. This was a really cool session that focused on building out SharePoint farms in Azure. At TechEd North America 2013 my good friend Paul Stubbs did a session with Michael Washam and Corey Sanders on: IaaS: Hosting a Microsoft SharePoint 2013 Farm on Windows Azure
0 Comments
Leave a Reply. |