The 9th Dutch PowerShell User Group meeting, almost exactly four years after our very first meeting. First of all I would like to thank everyone involved, speakers, IPsoft and our attendees for making this event into a success. We announced this event just 6 days before it was actually held and we were at full capacity within two days. A great show of community involvement which was definitely present during the evening.
During the event we had the following three speakers and sessions:
The event was hosted and generously sponsored by IPsoft and the following photos will give you an impression of the event:
Five countries, five MVPs
We have also created a separate repository on the DuPSUG GitHub account which has all available presentations:
9TH DUPSUG MEETING
During the evening Thierry Cailleau once provided us with live reports of the content being presented including notes and links in our Slack channel, dupsug.slack.com. Feel free to join us there to catch up on the details of the evening.
We hope to see you again in the next year as we have many more events planned in 2017!
A common problem on laptops or mobile workstations is that the initial PowerShell Remoting configuration will fail because the system is connected to a public network. The advice is to change the network from public to private, unfortunately this is not always possible because of WiFi connections.
There is a work around available for this, by running the following code:
Enable-PSRemoting -SkipNetworkProfileCheck -Force
By including the -SkipNetworkProfileCheck the cmdlet with omit the network check and PowerShell remoting correctly regardless of the fact that the system might be connected to a public network.
When setting up PowerShell Remoting using winrm quickconfig the following error might occur:
PS C:\WINDOWS\system32> winrm quickconfig quests on this machine.
The following changes must be made:
Start the WinRM service.
Set the WinRM service type to delayed auto start.
Make these changes [y/n]? y
WinRM has been updated to receive requests.
WinRM service type changed successfully.
WinRM service started.
Message = WinRM firewall exception will not work since one of the network connection types on this machi
ne is set to Public. Change the network connection type to either Domain or Private and try again.
Error number: -2144108183 0x80338169
WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Chang
e the network connection type to either Domain or Private and try again.
Or when using Enable-PSRemoting without skip network check this error will appear:
PS C:\WINDOWS\system32> Enable-PSRemoting -force
Set-WSManQuickConfig : <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859113"
Machine="localhost"><f:Message><f:ProviderFault provider="Config provider"
Code="2150859113" Machine="computername"><f:Message>WinRM firewall exception will not work since one of the network
connection types on this machine is set to Public. Change the network connection type to either Domain or Private and
try again. </f:Message></f:WSManFault></f:ProviderFault></f:Message></f:WSManFault>
At line:69 char:17
+ Set-WSManQuickConfig -force
+ CategoryInfo : InvalidOperation: (:) [Set-WSManQuickConfig], InvalidOperationException
+ FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.SetWSManQuickConfigCommand