This is how I add subdomains (so basically new schools) to out G suite setup. I've got these steps documented on a scruffy set of notes that I've now got in Keep - so time to document them - for myself as much as anyone else!
Steps in order (roughly)
Steps in order (roughly)
- Add the new domain
- Verify the new domain
- Add MX records to hosting
- Add SPF record for Google to hosting
- Turn on email authentication
- Add DMARC record to hosting
- Setup custom Directory and restrict students OU to this.
- Create an admin quarantine for the domain.
- Configure SPAM setting for the domain.
- Turn on and off services as appropriate.
- Map a blank Google Site to the naked domain - if required.
- Setup some basic groups - allstaff, allusers (for directory) and students with appropriate permissions.
- Deploy custom wallpapers.
So the steps in a bit of detail:
Add the new domain & Verify ownership
Click on Domains in the admin console:
Add/remove domains followed by "add a domain"
At this point make sure you select the second option.
You will then be prompted to verify ownership. In most cases, this means adding TXT record to wherever you host your DNS.
Click "Verify" and you should get a nice green tick.
Add MX records
Next to your new domain in your list of domains, there will be a prompt to add MX record. Click on this and the MX records you need to add will be shown. Add these to your web hosting.
SPF/DKIM and DMARC
I did a blog post about these a while back that explains how to set these up. You can find it here.
Setup a custom Directory
We have about 16 organisations as part of out overall G Suite setup, so it's important that individual member organisations can have access to a directory that just has their users if they wish. To do this, create a group called email@example.com. Make sure you lock this group down so people cannot join or post to it - it's purely for the directory.
You can use a scheduled GAM task to sync the membership of this group to the OU for this organisation (you need to make a sub-OU structure for the new organisation!).
gam update group firstname.lastname@example.org sync member ou_and_children "OU path in here"
So put this in a batch file and run as a scheduled Windows task. I have a file with many commands like this for different organisations within our setup.
Once you have the group, you can create the custom directory - Apps > G Suite > Directory in the management console:
Select Visibility settings for the OU you want to apply this to. Click "Users in a custom directory" and CREATE NEW.
Give the Directory a name and then search for you alluser groups and select it and click CREATE.
Save the setting. Note - custom directories taker anything up to a week to start working - so don't expect it to be instant.
Create an admin quarantine for the domain & Configure SPAM setting for the domain.
I've covered this in my blog post here. The one thing I've changed since writing that is that I never bypass internal senders in the SPAM settings. Internal accounts can be compromised as well!
Turn on and off services as appropriate.
What I turn on and off is normally down to the joining school. However, my basic ones I always do:
- Turn off G+ unless specifically asked for and for any OU with <13-year-olds in it.
- Turn off YouTube for any OU with <13-year-olds in it.
- Turn on restricted mode YouTube for students and allow staff OU's to approve videos.
- Restrict sharing in Drive to within the domain only.
- Turn off Blogger for student OUs (unless requested).
Map a blank Google Site to the naked domain - if required.
Why pay for a website? Just use a Google Site - its way easier. I create a blank site with a user on the new domain (this is important!). Then in the admin console Apps > G Suite > Sites > Web Address Mapping and click on ADD A NEW WEB ADDRESS
So pick "new Sites", select your new domain, your site name and in the web address - just put www.
You will then be directed to add a CNAME record to your web-hosting. Remember to add a redirect to https://www.yoursitename.com for https://yoursitename.com
Setup basic groups
I always setup a few basic groups like email@example.com etc. Just make sure the permissions are set appropriately on the groups. Auto-populate them with a scheduled GAM command as shown in red earlier on.
Wallpapers and other Chrome settings
I generally set up custom wallpapers for both devices and users and put in a few managed bookmarks to get them started.