# Server 2016 Core + PsDscRunAsCredential

**URL:** <https://forums.powershell.org/t/server-2016-core-psdscrunascredential/8799>\
**Category:** DSC\
**Created:** [June 9, 2017, 12:39am UTC](https://forums.powershell.org/t/server-2016-core-psdscrunascredential/8799 "2017-06-09T00:39:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gareth-shipp](https://avatars.discourse-cdn.com/v4/letter/g/6bbea6/32.png) [@gareth-shipp](https://forums.powershell.org/u/gareth-shipp)\
**Post date:** [June 9, 2017, 12:39am UTC](https://forums.powershell.org/t/server-2016-core-psdscrunascredential/8799/1 "2017-06-09T00:39:38Z")

</div>

We’ve been running our DSC on Windows 2012 R2 GUI and Core for a while and it’s been working perfectly. Recently we decided to move to 2016 GUI and Core. Running a consistency check works perfectly fine on Windows 2016 GUI (1607 + May CU), however when running a consistency check on Windows 2016 Core, every resource using PsDscRunAsCredential gets an “The filename or extension is too long” error.

I thought maybe it was a certificate issue but I double checked our certificate settings against [https://msdn.microsoft.com/en-us/powershell/dsc/securemof](https://msdn.microsoft.com/en-us/powershell/dsc/securemof) and they have the correct settings.

```
VERBOSE: [S16AUMDC01TST01]: LCM: [Start Resource] [[cScheduleTask]PowershellHelpUpdateScheduledTask]
VERBOSE: [S16AUMDC01TST01]: LCM: [Start Test] [[cScheduleTask]PowershellHelpUpdateScheduledTask]
VERBOSE: [S16AUMDC01TST01]: LCM: [End Test] [[cScheduleTask]PowershellHelpUpdateScheduledTask] in 0.0470 seconds.
Invoke-CimMethod : The filename or extension is too long
At C:\Program Files\WindowsPowerShell\Modules\BVISMServerEnforcer\Functions\Public\Invoke-BVEnforcerCheck.ps1:20 char:5
+ Invoke-CimMethod -CimSession $ServerName -Name PerformRequiredCon ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : AuthenticationError: (:) [Invoke-CimMethod], CimException
    + FullyQualifiedErrorId : Win32Error:206,Microsoft.Management.Infrastructure.CimCmdlets.InvokeCimMethodCommand
    + PSComputerName : s16aumdc01tst01
```

Anyone have any ideas?

---

<div class="post-metadata">

**Author:** ![donj](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/donj/32/137_2.png) [@donj](https://forums.powershell.org/u/donj)\
**Post date:** [June 12, 2017, 7:26am UTC](https://forums.powershell.org/t/server-2016-core-psdscrunascredential/8799/2 "2017-06-12T07:26:02Z")

</div>

I’ve pinged a few folks on this.

---

<div class="post-metadata">

**Author:** ![gareth-shipp](https://avatars.discourse-cdn.com/v4/letter/g/6bbea6/32.png) [@gareth-shipp](https://forums.powershell.org/u/gareth-shipp)\
**Post date:** [June 12, 2017, 1:43pm UTC](https://forums.powershell.org/t/server-2016-core-psdscrunascredential/8799/3 "2017-06-12T13:43:19Z")

</div>

Thank you very much Don. I’ve discovered the issue exists on both Core and GUI. I’ve consolidated all the information on this post here [https://powershell.org/forums/topic/server-2016-the-filename-or-extension-is-too-long/](https://powershell.org/forums/topic/server-2016-the-filename-or-extension-is-too-long/).

If you can close this post that would be great.

---

<div class="post-metadata">

**Author:** ![dotnVo](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@dotnVo](https://forums.powershell.org/u/dotnVo)\
**Post date:** [May 16, 2024, 9:16pm UTC](https://forums.powershell.org/t/server-2016-core-psdscrunascredential/8799/4 "2024-05-16T21:16:40Z")

</div>

Closed on May 16, 2024, 9:16pm UTC


