SfB Online: Next generation provisioning is not enabled for your tenant.

While trying to add a Holiday to one of our Auto Attendants I was greeted with a “useless” error message, so in hopes of getting a better picture of what was going on, I opened up my powershell console and connected with our Tenant

$session = new-CsOnlineSession
import-PSSession $session
Export-CsAutoAttendantHolidays
cmdlet Export-CsAutoAttendantHolidays at command pipeline position 1
Supply values for the following parameters:
Identity: <snip>
Next generation provisioning is not enabled for your tenant. Please contact support to enroll.
    + CategoryInfo          : NotSpecified: (:) [Export-CsAutoAttendantHolidays], OnlineCmdletException
    + FullyQualifiedErrorId : FeatureIsNotEnabledForTenant,Microsoft.Rtc.Management.Hosted.OAA.V2.ExportCsAaHolidaysCmdlet
    + PSComputerName        : admin0e.online.lync.com
Continue reading

Enterprise Management Scheduled Tasks do not match documentation

When we started our journey towards 100% Intune managed, AAD joined devices one of our frustrations was that, after a device was joined to our AAD, we had to play a waiting game before we could verify that all deployment & configuration settings were actually applied to the device.

You can either wait for the MDM client to trigger it’s scheduled check-in, use the device’s GUI to force a manual sync, or trigger one from the Intune management portal.

For Windows 10 devices, the documented schedule for check-ins is as follows:

  • Windows 10 PCs enrolled as devices: Every eight hours.

If the device has just enrolled, the check-in frequency is more frequent, as follows:

  • Windows PCs enrolled as devices: Every three minutes for 30 minutes, and then every eight hours.

Continue reading

Enforcing Computername using Intune Powershell

When performing a ‘Fresh Start’ or ‘Factory Reset’ on an Intune managed device, the computername is reset to the default ‘DESKTOP-<random>’ name.

Our requirement however, was that every machine has a specific computername.

Since Intune offers the possibility of deploying Powershell scripts, I’ve written one that checks the device’s serial number and renames the computer if the serial is known.

Continue reading

Deploying the ‘Upgrade Readiness Deployment Script’ via InTune

Microsoft has released the “Upgrade Readiness Deployment Script” (URDS), including a method for deployment with SCCM.

Upgrade Readiness is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud based services for managing your on-premises and cloud environments. For more information about OMS, see Operations Management Suite overview.

Unfortunately, they do not provide instructions how to deploy the script using Azure InTune, the MDM solution we use.

Luckily, with the use of Advanced Installer (AI) and a short PowerShell script, I have been able to deploy via InTune 🙂

Continue reading

Unable to enable PIN usage in Windows 10 Enterprise

While comparing the domain join experience when joining an Azure Active Directory domain to the experience when joining a ‘regular’ on-premise domain, I noticed the AAD joined machine prompted me to setup a PIN for login purposes.

Of course, I wanted to check if this was also possible on my on-premise joined machine, but -alas- all options related to this ( Settings -> Accounts -> Sign-in options) were greyed out….

Luckily, a quick google search later, I found this technet thread explaining that all that was needed to re-enable this was a simple registry entry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System]
"AllowDomainPINLogon"=dword:00000001

Unable to add Campaign Members to a Campaign

Problem

One of our users was unable to add new members to a campaign because the ‘Campaign Membership Status’ pulldown menu was empty.

Possible solution

  1. Go to Setup | Customize | Campaigns | Campaign Members, and look at the ‘Status’ field, make sure there are values listed.
  2. Click ‘Advanced Setup’ on the relevant Campaign, and make sure there are values in the Member Status Values Related list.

On a side note, if you find yourself adding the same additional Statuses to Campaigns over and over, check out AAkonsult’s “Campaign Status Defaulting” app on the AppExchange, it will make your life easier!

My first encounter with a Bug

While implementing Order processing in our sandbox, I ran into the scenario where a test user is able to create an Order for a certain account, can select the relevant Price Book and sees all the Products from that (standard) Price Book.

Unfortunately, after selecting the Products to add to the Order, and clicking “Select”, the user gets the generic “Insufficient Privileges” error message.

Continue reading

Welcome

This is a blog by a ‘Rookie’ Salesforce Admin/Developer.

The purpose of this blog is to share insights and as a log for things I run into in day-to-day operations that I want to keep track of.

Hopefully, it will also be of use to other SFDC Admins 🙂