...building hybrid clouds that can support any device from anywhere
Hey Readers, so you’ve taken a look at the initial post and are ready for some more information I suppose. Well if you haven’t seen the previous post, before we dive in, make sure you review on where we started in Part 1 where you can get an idea of the high level goals, some information on the technology we are using, and a really cool video!
Application Management-Example-Deploying a Service to Your Private Cloud (Part 1)
As promised I am going to start with the basics on what is required to support this solution.
Yeah I know – obvious? Well, if you are curious about this private cloud stuff you are definitely in the right place. Look around and get some information here. The Deployment Track is loaded with information on how to setup a private cloud. This is Step 1 (or step 0 if you prefer) so go do that and come back (I’ll wait) .
So once you have your private cloud up and ready, to get started we need the basic essentials which you can go download from the TechNet Gallery content page here.
This download (ServiceTemplateForSharePoint2013_content.zip) contains the following artifacts:
Download and extract these files to a local system drive. Review the Service Template for SharePoint 2013 User Guide.docx to get started. Make sure you pay attention to the environmental requirements section of the document before moving forward.
Now that you’ve had time to review the document and got those files located somewhere they can be accessed, we can get started moving through the steps for setup and configuration. The graphic that follows is a good summary of what’s ahead of us and I’ll likely refer to it often through the series.
This specific service template leverages 11 individual user accounts. Now I’ve provided a script (located within the sp_Create_User.zip) that can be used to create these accounts in Active Directory, but of course it doesn’t do everything .
Remember what I said, it doesn’t do everything! This script takes as parameters (OUPath and InputFile) and has defaults defined that you can update as well. This script will take the user names listed in the input file and create them in the OU specified with the password you fill in at the prompt when executed. This script requires that the ActiveDirectory PowerShell module be available on the system you are running this script from. For more information and details, refer to the documentation provided in the content download (I’m going to say this a lot).
Put them together and you get something like this
If all goes well, it will look a lot like this
This is simply a list of user accounts to be created in Active Directory. All of these accounts (with the exception of the highlighted account) are referenced within an XML that is called by the autospinstaller script. These accounts are expected to exist at time of install. The !installer account could be replaced by any domain account that is a local administrator on the virtual machines (by default) as they are deployed for the installation of your SharePoint farm. If you choose to leverage your own admin account, refer to the documentation as it goes into detail on where each of these accounts are used and how to update the dependencies accordingly.
SharePoint 2013 Server Enterprise edition, SQL Server 2012 SP1, and the AutoSPInstaller script source are all assumed to be located on a network share for this service template. We’ll get into the details of how these files are leveraged later but a couple of reasons that the AutoSPInstaller and SharePoint content is on a network share is:
Here are the quick and dirty steps for share creation
Next, we need to download and stage the required artifacts. What are the required artifacts you ask?
Well they break out like this:
The content had within it a directory called “apps$”.
To properly stage the download content “apps$” folder
SQL Server 2012 SP1 media is accessed during the service template customization of SQL. This media must be located on a share that is accessible by the SQL install account. See the documentation for more details.
To download and stage SQL Server 2012 SP1
The service template for SharePoint 2013 Enterprise takes advantage of a robust scripted solution for the installation of SharePoint. This community script is located on CodePlex at AutoSPInstaller, and it must be downloaded and placed on a secure network share.
To download and stage AutoSPInstaller
The SharePoint Server 2013 Enterprise source files are called directly by the AutoSPInstaller script to install and finalize SharePoint.
To download and stage SharePoint Server 2013 Enterprise
OK! I think that is enough for today . We covered some basics, setup the accounts for SharePoint, created a share and staged the files we need to get us going in the next steps. We’ll pick up next on creating your VHDs to support the service template.
Make sure to check out the next post in the series here: Application Management-Example-Deploying a Service to Your Private Cloud (Part 3)
Till next time – Happy Automating!