Author Posts

May 11, 2016 at 1:32 am

Hi,

I have installed PackageManagement (x64, msi) on couple of 2012 R2 servers.
Some of them has the Find-PacketProvider cmdlet and some don't. I haven't figured out why there is difference.

The only thing that has struct me is the CLR version – but has that really something to do with it?
The server 2012 R2 that has the Find-PacketProvider cmdlet:

PS C:\Windows\system32> $PSVersionTable

Name Value
---- -----
PSVersion 4.0
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.42000
BuildVersion 6.3.9600.17400
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion 2.2

The server 2012 R2 that does not have the Find-PacketProvider cmdlet:

PS C:\Windows\system32> $PSVersionTable

Name Value
---- -----
PSVersion 4.0
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.34209
BuildVersion 6.3.9600.17400
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion 2.2

Best regards
Stig

May 11, 2016 at 2:03 am

Good news, I guess. Upgraded the failing server to .NET 4.6.1 and still no Find-PacketProvider – so .NET is not the issue.. 🙂

But then what is..

May 11, 2016 at 2:14 am

Seems Find-PackageProvider has been removed. The servers with the cmdlet are a bit older than the ones missing the cmdlet. I can easily install providers without the Find cmdlet.

Case closed