Excel crashing due to igc32.dll

One of our users recently reported that Excel was consistently not starting up, a quick repair and a full repair did not solve the issue.

Digging into the event viewer provided the following error:

Faulting application name: EXCEL.EXE, version: 16.0.13127.20296, time stamp: 0x5f47452f
Faulting module name: igc32.dll, version: 27.20.100.8189, time stamp: 0x5eb1b776
Exception code: 0xc0000409
Fault offset: 0x009374b6
Faulting process ID: 0x27d0
Faulting application start time: 0x01d681b4baefa07b
Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\EXCEL.EXE
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igc32.dll
Report ID: d0e8befa-809f-4691-a6ac-e995a0365b18
Faulting package full name: 
Faulting package-relative application ID: 

Pasting the error message in Google did not yield any usable results, hence this post 🙂

Googling on the purpose of IGC32.dll showed that it is part of the Intel Video drivers.

A short term workaround for this error is going to Device Manager -> Display Adapters and uninstalling the current device driver (do not reboot afterwards).

I’ll be testing if reinstalling the same driver version will cause the issue to re-occur, or if the dll was simply corrupted, but the user obviously has work to do first 😛

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

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

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 🙂