Creating a Development VM - Part 2: Preparing Windows
This document details how to install and test an SDL Tridion Content Manager 2013 install on Windows 2012 with a SQL Server database.
Creating a Development VM - Part 2
Prepare your Windows 2012 server
In this step we'll take you through preparing your Windows 2012 server for a clean Tridion installation.
Change password policy
Simplify development by changing the password policy (using "Group Policy Editor").
- From your keyboard's Start button, go to Administrative Tools > Local Security Policy.
- Disable "Password Must meet complexity requirements."
Rename your server
Name your machine something you are likely to remember.
Tridion System Account
In a normal Tridion environment, the Tridion System Account must be a Domain account. If this is just a local development or test machine, you may want to create this account as a local account instead. In either case, ensure that this account is added to the local "Administrators" group.
- Go to Tools > Computer Management > Local Users and Groups > Users.
- Create a New User.
- Name the user MTSUser
- Type in "Administrators" and press Check Names then OK.
- Note: your old computer name may show in the Select Groups pop-up until the next reboot.
- MTSUser's properties should now show it belongs to Administrators.
Install available Microsoft Updates
From Configure this local Server, select the Never link under Last Installed Updates.
If prompted to Turn on
, optionally turn it on.
In the Server Manager dashboard, select option 2 Add Roles.
At the Installation Type option select "Role-based or feature-based installation" and then select next.
Select your server from the server pool and then select next.
- Select Application Server and Web Server (IIS) roles.
- Click Next
You have now configured the required Windows 2012 Server Roles for an SDL Tridion 2013 Content Manager Server.
Next section: Setting up the database
Move on to the next chapter in this tutorial:
Preparing the database