All in the same consistent way.įor more information about installing PnP PowerShell, please refer to the documentation. from a Windows machine, Mac, Linux based device, Azure Function, Azure Runbook or even a Raspberry Pi. PnP PowerShell runs on any device on any platform. No need to download different PowerShell Modules, which all work in a slightly different way, requiring different ways of connecting and authenticating. The advantage is that you will have a consistent way to work with a broad range of Microsoft products from a single connection. Update-TypeData -TypeName System.Io.PnP PowerShell is a “swiss army knife” type of PowerShell Module providing over 650 cmdlets that work with Microsoft products such as SharePoint Online, Microsoft Teams, Microsoft Project, Security & Compliance, Azure Active Directory, and more. The following is an example you can copy and paste that exposes the goods as a new property called FileVersionUpdated on all FileInfo objects (in the current session): It is just hidden by default.ĭepending on your scripting preferences as a scripty scripter-you can use this freshly revealed truth in several ways. My colleague Artem Pronichkin showed me that VersionInfo contains the information we want.
If you’d like to see this default behavior in PowerShell changed, vote along at. The example above is from Windows Server 2012 R2. Eagle-eyed friends of mine found that on Windows Server 2008 R2 machines with SP1 + additional patches installed PowerShell will show pre-SP1 versions numbers on various DLLs. You can try this on various machines and OSes and get fun weird results. What the what? This image shows that for the very same file PowerShell and file properties (Explorer) can report different version numbers. Unfortunately the default presentation of file version info in PowerShell is… sub-optimal.
I focus on enterprise Windows optimization and security for Microsoft Services. First published on TechNet on Dec 07, 2014
0 kommentar(er)
