One of the key features of Provisior is to provide insight in user access rights. This used to be quite simple as most access rights where formed by Active Directory security groups for access to network shares, shared mailboxes, distribution lists and software applications. One of the primary use cases
Today I learned a nice little trick one of our MSP partners uses in their PowerShell scripts. Provisior lets you define PowerShell parameters on a global level, so you can reuse them in different PowerShell templates you define. To do this, you link the parameters to the template and define
By default Provisior will send emails to users in name of the actor. For instance, if a user requests access to a shared mailbox, and his/her department manager needs to approve this, the manager will receive an email in name of the user requesting. This is convenient, because the receiver
In September 2018 we released a version of Provisior in which we introduced a nice new feature: The ability to bind the output of a Powershell script as the source for a (multi-value) field in our dynamic Forms (link in Dutch only). This opened a whole new world for our
While setting up Provisior at a new customer we ran into an error while testing the on-boarding of a new user. The mailbox could not be enabled in the local Exchange 2013 server. The error Exchange returned was: Load balancing failed to find a valid mailbox database. Fortunately Google helped
The other day I was sitting with a Provisior customer to discuss some topics and he wanted to show me something. As an example he started a request for himself and needed to scroll pretty far through the employee list and I hear him say “This is a bit frustrating
What better moment than introducing the Provisior Tech Blog on System Administrator Appreciation Day! This day, also known as Sysadmin Day, SysAdminDay, or Sysmas, is an annual event to show appreciation for the work of sysadmins and other IT workers. It is celebrated on the last Friday in July. Provisior,