Recently I started using Mantra to develop my Meteor apps. As with any other framework You’ll find a lot of answers to common questions in a related forum or any other resource. However I couldn’t get a good answer on how to implement routing logic properly. The Mantra specs also don’t tell much about how to approach it. So here’s my solution.
Based on my last Active Directory backup script I’ve developed a similar script to backup all group policies.
What it does:
- Create a daily full snapshot of all group policy objects
- Keep a daily, weekly and monthly snapshot
- Notify me if something failed (requires PowerShell PowerUp)
Since SharePoint 2013 only supports claim based authentication I discovered that updates in SharePoint Active Directory groups do not take effect immediately.
Thanks to Ryan McIntyre there’s a simple fix for that issue.
By adjusting the lifetime of the claims token you can shorten the time it takes to update the Active Directory group changes.
The SharePoint term store service is one of the most important parts of a SharePoint installation. It’s the best place to store an manage global metadata for your companies documents.
It’s not that hard to design a term set in Excel and import it afterwards with the built-in term store import wizard.
However there’s no tool or wizard that allows you to get a term set out of the term store.
It’s only possible with my PowerShell function (which is as always part of my PowerShell PowerUp project)
As in on of my last post I’ve showed you my approach to manage distribution groups in the hierarchical structure of an ActiveDirectory installation. In the mean time I’ve adapted a similiar approach for the security groups.
Here is an example of the structure: Read More
The goal of this project is a simple Windows 7 Kiosk installation with nothing else as the newest version of internet explorer installed. A user should not be allowed to do something than can malfunction the system or even elevating the user privileges. I want to show you in this post which GroupPolicies I’ve used and what configurations I made to set up this type of installation.
First I want to commit my principles for working with ActiveDirectory and Group Policies:
- If not needed a GroupPolicy shouldn’t contain any registry keys.
- Group Policies instructions are much easier to read.
- Only AMDX templates are allowed, this means no AMD templates or anything else.
- AMDX won’t in contrast to AMD templates becopied to the client, they stay in the SYSVOL Policy Definition folder on the domain controller.
- The Group Policy objects should be reusable.
- Configuring the minimum.