The free Idera PowerShellPlus remains my go to PowerShell editor for the unique combination of features it has...

Desktop management systems frequently add or update software using a user profile other than the actual user of the system.  This creates a classic problem in discerning which user profile(s) represent the active user(s) of the machine.  Several variants of this oneliner show a couple methods for identifying one or more "active", "recent" or "owning" users of the machine locally or remotely.  This article layer's up useful code that also demonstrates: selecting files by age, sorting one array with another, showing hidden files, selecting the most recent file and other techniques.

With the May 2014 release of the Office 365 Pro Plus Click To Run, Microsoft introduced the ability to install less than the entire Office suite.  Prior to this, enterprises installing Office 365 Pro Plus using *Click To Run* (NOT Windows Installer / MSI) could only install the entire suite - just like when 365 Click To Run is pull installed from the Microsoft Office 365 portal.  Awesome move Microsoft!  Many companies are planning to push only Lync 2013 Click To Run and follow up with the full Office Suite later or perhaps will need to add OneDrive at some point.  This raises an interesting question... How do you tell what 365 sub-products are already installed?

It is never ceases to amaze me how many application compatibility issues I diagnose that come down to challenges running 32-bit software on 64-bit Windows!  Flexera is sounding the same drum beat as the primary application compatibility concern when migrating off of Server 2003 and I have to say I agree.

Even if you followed the Microsoft playbook exactly when doing App-V 4.6 on SCCM 2007, when you migrate to SCCM 2012 you may be in for some pain.  The App-V shortcuts installed by SCCM link to a special launcher that is part of the SCCM clinet.  In the case of 2007, this is probably linked to "c:\windows\syswow64\ccm\vapplauncher.exe".  These links end up breaking when the SCCM 2007 client is removed while upgrading to the 2012 client.  The following PowerShell Oneliner screams through (yes it is quick) the Win32_Shortcut WMI name space to find all shortcuts to this file and updates them very quickly!

With Office 2013 Microsoft created a new deployment and installation mechanism known as "Click To Run (CTR)".  This is the method used to deploy office from the web in a near instant fashion and it includes a type of "Runtime App-V" under the covers.  The same mechanism is used to deploy the Click To Run edition in corporations. Up until now you could only install the entire suite of Office applications when using Click To Run (MSI based installs have always retained full selective product install capabilities).

In many languages combining or unisecting arrays is part of the standard operators or they have special operators to do this.  PowerShell does not have special operators and it has taken me a very long time to figure out how to make it do this!

I have been working on a project to deploy Office 365 to the enterprise for over 6 months now.  Office 365 SP1 is a significant boost to the ability to deploy an on-premise source approach to Office 365...