SqlMonitoring Tool

 

The SqlMonitoring tool makes it possible to monitor SQL 2000, 2005, 2008 environments and send alerts to a central database (SQL 2008). A client can be used to view the alerts en perform actions on them. This tool is a good alternative if you do not have the budget or infrastructure for tools like SCOM.

SqlMonitoring Tool – Home

Txt Gateways for Sending Txt Messages from an Email Client

You can send a txt message to anyone who can receive txt messages on their phone or smartphone using your favorite email client – you just need to know the remote phone number along with the provider gateway information.

Here’s a few:

Verizon: 10digitphonenumber@vtext.com
AT&T: 10digitphonenumber@txt.att.net
Sprint: 10digitphonenumber@messaging.sprintpcs.com
T-Mobile: 10digitphonenumber@tmomail.net
Nextel: 10digitphonenumber@messaging.nextel.com
Cingular: 10digitphonenumber@cingularme.com
Virgin Mobile: 10digitphonenumber@vmobl.com
Alltel: 10digitphonenumber@
message.alltel.com
CellularOne: 10digitphonenumber@mobile.celloneusa.com
Omnipoint: 10digitphonenumber@omnipointpcs.com
Qwest: 10digitphonenumber@qwestmp.com

Exchange Message Store not mounting – one fix…

I saw an issue recently where an update to the server’s AV caused the Exchange Information Store service not to start.  It was first identified when the server was rebooted for some other reason, and the service would not start automatically.  There were strange errors like: 0(0x0), which really didn’t tell me much.  After a bit of sleuthing I found that the VirusScan portion of Exchange was causing the service to actually time-out when starting.  Renaming the VirusScan key solved the problem to allow email to start flowing again.  If you’re out of options trying to figure out why a store will not mount and the service will not start, give this fix a shot.  It could get you back up and running.

To do this, find this key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\VirusScan

Rename, “VirusScan” to something different like “NotVirusScan” or something so that Exchange doesn’t see the key when the Information Store service is started.

Silverlight 3.x – the download – and installation methods…

The Silverlight 3.x installation seems to be hijacking computers this week, showing up in update windows at the most inopportune times.  And, if you cancel the install, there’s no easy way to get the installation to start up again.

So…I finally found the actual download link to download Silverlight 3.x to your local computer for distributing in a more corporate, more civilized manner.

Click this link and the download will start:

http://www.microsoft.com/silverlight/handlers/getsilverlight.ashx

To install silently, use:  silverlight.exe /q

NOTE: This upgrades the previously installed version without needing to uninstall it first.

You can also grab the .msi file from the silverlight.exe by running:  silverlight.exe /extract

Once extracted, you’ll find a silverlight.7z file.  This is a WinZip compatible (or other zipping app) file from which you can extract the silverlight.msp and other files.  For the .msi installation, though, you only need to retain the .msp and .msi files, i.e., you can discard the rest.

If you choose to go the .msi installation method, uninstall Silverlight 2.0 FIRST by running:

start /w msiexec.exe /X{89F4137D-6C26-4A84-BDB8-2E5A4BB71E00} /qn

Then, run the Silverlight 3.0 installation by running:

start /w msiexec /i silverlight.msi /update Silverlight.msp
ALLUSERS=2 /qn /LiV %temp%\Silverlight3.log

 

Extra Stuff:

Silverlight 3.0 .exe silent uninstall:  silverlight /qu

Silverlight 3.0 .msi silent uninstall:  start /w msiexec.exe /X{89F4137D-6C26-4A84-BDB8-2E5A4BB71E00} /qn

AMT / ConfigMgr SQL Query: Mismatched Hostnames « Trevor Sullivan’s Tech Room

 

In IT environments where device naming standards may be course, or where users can freely rename their systems at will, you may experience problems managing these clients’ AMT firmwares. Since, in order to maintain proper AMT functionality, the OS and AMT hostnames must match, an IT administrator or engineer would likely be interested in finding out which machines do not meet this criteria.

With that in mind, I’ve written a simple SQL query, that can be run against your Configuration Manager database, to determine what devices have mismatching OS and AMT hostnames. I’ve pasted the text below, but if you want a more nicely formatted version, please see this link at PasteBin.

Get the script:

AMT / ConfigMgr SQL Query: Mismatched Hostnames « Trevor Sullivan’s Tech Room