Command Lines

sysdm.cpl - System Properties
powercfg.cpl
inetcpl.cpl
ncpa.cpl
wscui.cpl - Action Center
desk.cpl -  screen res
smscfgrc.cpl - SCCM 2012 Client Configuration Manager Properties

normally this is C:\Windows\CCM\smscfgrc.cpl     depending on where the client is installed.

dsa.msc     AD user computer admin (server tools)
gpmc.msc  Group policy editor/viewer


check the uptime from Statistics since ....  :
net statistics workstation

Windows 10/11

start the settings applet from command line

start ms-settings:

WSUS database reindexing

Windows Server Update Services
http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx


Download and install to the WSUS 3.0 server in the following order

Microsoft® ODBC Driver 11 for SQL Server

Microsoft® Command Line Utilities 11 for SQL Server

Obtain the wsusmaintenance.sql script here and run as directed.
https://gallery.technet.microsoft.com/scriptcenter/6f8cde49-5c52-4abd-9820-f1d270ddea61

Disable MSI Uninstall

This is an unusual requirement but if there is a situation that justifies disabling the uninstall the following settings provide for it.

Set the standard action LaunchCondition in the InstallExcuteSequence table to have a condition of  REMOVE~="ALL"

Set an entry in the LaunchCondition table

Not Installed      Uninstall Disabled


If an uninstall is started the Condition of the LaunchCondition standard action in the InstallExecuteSequence table evaluates to TRUE

The LaunchCondition of Not Installed evaluates to FALSE and prevents the uninstall from continuing.

If /qb is used "Uninstall Disabled" is displayed to the user.  /qn is fully silent. The uninstall Exit code will be 1603.

App-V 5 Launch Failure - may be due to a network failure

The application failed to launch.
This may be due to a network failure
Error code: 0x4C408B0C-80070002


The first response to this message would probably be a considering of weather it was actually a network failure.  Generally this message would appear if the App-V package was unavailable.

However, this can occur if the package has managed to arrive in some partial or corrupted way.  The following powershell commands can resolve this problem and re enable the application to launch correctly

Run as admin:
remove-appvclientpackage -name <PackageName>

Run as user:
get-appvclientpackage -name <PackageName>

this should verify that the package has been removed.

sync-appvpublishingserver 1

to refresh the available App-V packages on the client

get-appvclientpackage -name <PackageName>

to verify the the application is available again.

mount-appvclientpackage -name <PackageName>

to fully pull down the package prior to launching.

Autodesk products needing VC ++

The SCCM deployment fails to install one of the prerequisite VC runtimes.  Installed normally the complete process works correctly.

Where an SCCM deployed installation has occurred.  AutoCAD LT 2015 will fail to launch and generate an error message referring to MSVCP110.dll

To resolve this issue run the installation of the missing Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.61030.

It is in the source media location .\Img\3rdParty\x64\VCRedist\2012UPD4\vcredist_x64.exe

It can be located in the SCCM cache

C:\Windows\ccmcache\XX\Img\3rdParty\x64\VCRedist\2012UPD4\vcredist_x64.exe

Where XX is the SCCM assigned folder name.  The cache location can be found by searching the cache for acadlt.msi

DWG TrueView 2015 also requires this prerequisite and gives a launch error referring to VCOMP110.dll

Avery Wizard 5.0

Avery Wizard 5.0 is free label creation software which can be downloaded from
http://www.avery.co.uk/avery/en_gb/Templates-%26-Software/Software/Avery-Wizard-for-Microsoft-Office.htm

There are no shortcuts and instead the installer creates an addin to Office applications which links into the Avery Wizard software.  In Word an Avery Tab appears.

Initially it did not look suitable for App-V 5.0 because there was no shortcut entry points available (Word installed locally) and providing shortcuts where none are normally needed was seen as an unecessary change to the user experience.

However when the installer was analysed to create a machine installation delivered from SCCM the vendor's MSI had multiple issues (custom actions did not function as intended).  Clearly it was only designed to be installed and used by a users whose account was an administrator.  When installed by such a user it performed satisfactorily.

Installing using ALLUSERS=1 using an admin account left a normal user account with a 30+ second wait to launch Word.

Although a transform with preset property values (see below) could be used to enable a machine installation under the system account, any machines installed would suffer 30+ seconds launch delays for Word.

With more time available it may be possible to create a properly working local installation for SCCM delivery however given the issues, it was decided to revert back to App-V.  Unfortunately this also suffered extended launch times for Word when an App-V shortcut to Word was created, but this only had to be endured when Avery was actually needed.  The remainder of the time the local install of Word launching time would remain reasonable.

Transform items enabling a System Account install.
WORDSTARTUPFOLDER       C:\Program Files (x86)\Microsoft Office\Office14\STARTUP
IDP_WORD_VERSION_INSTALLED     14
IDP_EXCEL_VERSION_INSTALLED     14
HKCU(orLM)\Software\Avery\Avery Assistant\5.0\AutoUpdate\AutoUpdateEnable    DWORD 0
HKCU(orLM)\Software\Avery\Avery Assistant\5.0\AutoUpdate\InitialRun                  DWORD 1

Windows Media Center has stopped working

Windows 7 x64
Windows Media Center

Problem
When you attempt to start Windows Media Center (WMC) it immediately crashes and a dialog remains with "Windows Media Center has stopped working.

Solution
WMC uses a database file during launch.  If this gets corrupted it can cause the launch failure.

Delete/rename C:\ProgramData\Microsoft\ehome\*.db

Restart WMC.