Psychology Technology

http://blogs.msdn.com/joelo/archive/2007/06/27/file-name-length-size-and-invalid-character-restrictions-and-recommendations.aspx

Accessibility Options
 access.cpl

Add/Remove Programs
 appwiz.cpl

Add Hardware Wizard
 hdwwiz.cpl

Automatic Updates
 wuaucpl.cpl
 
Bluetooth Properties
 bthprops.cpl
 
Display Properties
 desk.cpl
 
Firewall Properties
 firewall.cpl
 
Game Controllers
 joy.cpl
 
Internet Options
 inetcpl.cpl

iSCSI Initiator
 iscsicpl.cpl
 
Java Control Panel
 jpicpl32.cpl
  
Licensing Mode
 liccpa.cpl
 
Mouse Properties
 main.cpl
 
Network Connections
 ncpa.cpl

Network Setup Wizard
 netsetup.cpl
 
ODBC Properties
 odbccp32.cpl
 
Power Options
 powercfg.cpl
 
Regional and Language Options
 intl.cpl
 
Sound and Audio Devices
 mmsys.cpl

Stored Passwords
 keymgr.cpl

System Properties
 sysdm.cpl
 
Telephone and Modem Properties
 telephon.cpl

Time and Date Settings
 timedate.cpl
 
User Accounts nusrmgr.cpl
 
Windows Security Center
 wscui.cpl

Wireless Link
 irprops.cpl

Recently I moved an installation of Neevia’s Document Convertor Pro to a new machine, as well as moving from version 4.9.9 to 5.2.2

Everything eventually migrated without much issue, though the main stumbling block (as it always does) proved to be antivirus software getting in the way of normal operation.  Once the antivirus realtime scanning was reduced in scope, all the document parsers to convert to pdf seemed well.

One small mistep was that one of the folders I set up for monitoring was not keeping the orientation of pages.  There were several documents where the first page was portrait, and the remaining were landscape.  This was easily overcome by going in to the folder settings, and making the AutoRotate Pages option set to ‘Page-by-Page’ instead of default.  While there is probably some performance overhead to this, it is needed for some environments.

Also, the support Neevia provide is fantastic!

During the course of my work today, troubleshooting a particularly sluggish application, I was investigating whether some DCOM errors in the Event Log had any impact on things.  One thing I have always found frustrating when doing this research, is that Microsoft will sometimes refer to their MS-05-051 Security Bulletin nomenclature, instead of the KB article that gets referred to when that bulletin in applied.

Moaning aside, I give a script below that will display if a particular KB is installed on a machine.

Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* |
 where-object {$_.DisplayName -like “*KB963707*”} |
   Format-Table DisplayName, Publisher

The above will display an entry if the string matches, so you could get more than one result, or none at all.  If you want to pull back all KB’s installed, just modify the query like so:

HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* |
 where-object {$_.DisplayName -like “*KB*”} |
   Format-Table DisplayName, Publisher

Sometimes it just is not convenient to pull back for particular events.  In the previous post I find I would much prefer the approach to have been having an exclusion list, rather than inclusion list of eventIDs to monitor.

While I work on that, I want to share the script I use to do this job, for a quick sneak peak at event logs across the network.  You can easily glean from the other scripts to have this read in a list of computers if you want, but I tend to use this while troubleshooting a single machine.  Then I’ll run multiple tabs in the powershell GUI for each computer.

## http://blog.getbusinessconfident.com
## PowerShell script to list the eventlogs on another computer
##
##The below is useful mostly for ad-hoc diagnostics or reviewing for a particular problem and whether it has recurred

$Log = “Application”
$Computer =”computerHostName”
$ID = “12345
$Type = “Error”

##The above are your standard Event Viewer attributes, to choose the system log, replace the word Application
##To view Warnings or Information, replace the word Error
$Objlog = New-Object system.diagnostics.eventLog($Log, $Computer)
#$Objlog = $Objlog | Where-object { $_.EntryType -like $Type }
#$Objlog.entries | select -last 5000

$result = $Objlog.entries | where { $_.EntryType -like “[$Type]*” } | select -last 20 | out-string
## On the above, you can amend the ‘select -last 20 to whichever number of entries you would like to pull back

write-host $result