Skip to main content

Restricting the use of consumer accounts on domain joined PC's

If you have domain joined PCs that can be managed via group policy and you use G Suite, then you might want to restrict the use of consumer accounts on your machines. If a user can use a private account, they can do a range of things that can potentially bypass content filtering and other policies you have set in the management console in G Suite.

The best way to prevent this is at the network level - see the Google help page here. This means that all devices on your network will be prevented from using consumer accounts. Many firewalls and content filter providers (e.g. Securly) have this as a setting now. However, if you are not able to use this approach, or want to set it on specific users only, then the lastest Group Policy Templates have policies to enable it.

There are two policies for this. One to block signin to Chrome from non domain accounts and the other to block non domain login to things like GMail.

Restrict who can sign into Chrome:


Restrict who can sign into G Suite tools such as GMail. Just be aware that this does not stop them using a private account to authenticate with some services - but it does effectively block the use of G Suite tools with private accounts. 


You can see the documentation for these settings (and all other ones) here. To get the latest policy settings, you do need to periodically download and update your template files on your domain controller. So if you don't have one or both of these settings, download and apply the latest admx files. 



Popular posts from this blog

Delete a specific email using GAM

If a user send an inappropriate email to a loads of people or get stung by some sort of email exploit you can quickly delete the email from all of the recipients using a GAM command.
Step 1 - get the email header Go into Google Vault and search for the offending user or someone known to have got the message.
Click show details and grab the email ID. This will be a long string of characters followed by @mail.gmail.com
Step 2 - find out who has the email Go into Google Vault and find the original message sent by the offending user. Look at the details to see who got it. Copy the list and dump it into a spreadsheet. Clean up to just a list of emails with a column header 'mail'. Save as a csv file.
Step 3 - delete messages with GAM Put your CSV file in your GAM folder - this e.g. assumes its called mail.csv
Run:
gam csv mail.csv gam user ~mail delete messages query rfc822msgid:MESSAGEIDHERE doit

The alternative nuke option is:
gam all users delete messages query rfc822msgid:MESSAGEI…

How to push bookmarks to users in Chrome via the management console

With the release of Chrome and ChomeOS 37 an update to the management console has arrived that allows you to push bookmarks to users.

Under Device Management > Chrome > User Settings > User Experience you will now find the option to add managed bookmarks.


In the example above, the bookmarks are applied to the sub-OU of 'students' - so all our students will get these bookmarks. Simply add your url and the bookmark name, click the + and save. These will appear in a folder called 'yourdomain bookmarks' - see below:



Be aware that to get these bookmarks applied on a Windows/OS-X device the user must be signed into Chrome. Update: if you install the latest group policy template you can push the bookmarks via policy on PCs - details are given here.
Video Guide:

ClearOS 7.1 as a Windows Domain Controller

I've been a long time user of ClearOS for gateway, DNS,DHCP, backup and a variety of other services. It is a Linux distro that is backed up with a marketplace of great apps that can be easily managed via a web config (although you can drop into cli whenever you want more control). The new samba directory app allows ClearOS to behave as a full on Windows Domain controller and file server without the cost of Windows Server.

So this is a demo from installation to a working DC and files server. Its about 40 mins for the full job - so skip though bits - gives you an example of what you can do. Please note the the Samba Directory App is currently in beta - but I've not spotted any bugs in a my test setup yet.