http://www.gradwell.com/support/kb/article.php?id=159

I wrote a powershell script to test the system and it worked well, but I didn’t really have a practical use for dialing from the command line.  Yesterday I was by chance reading about Extending the Internet Explorer Context Menu.

I decided to put together a quick bit of code that would allow me to initiate calls directly from Internet Explorer to my Gradwell extension, and it works really well!  I ditched the original Powershell version in favour of javascript because it made the solution much neater.

To make this work for you need to setup an authentication token for your extension on the Gradwell VoIP control panel first. Make a note of your extention and authentication token.

Download this HTML File (right click - Save Target as) and store it locally somewhere on your machine.  Open the file for editing and modify with your own extension number and authentication token:

Now we just need to create the internet explorer context menu, create the following registry key:

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\MenuExt\&Gradwell Call]
@=REG_SZ:”C:\some\path\to\View\DialGradwell.htm”
Contexts=REG_DWORD:10

You will need to change “c:\some\path\to” to the actual folder where you saved “DialGradwell.htm”.

Open Internet Explorer again and highlight some text or a link and right click and you should now have the option to call the number directly from your browser:

If you have done everything right, simply click on the “Gradwell Call” context menu option and your phone should start ringing right away.  Answer the call and you’ll hear the ringing of the destination number right away.

I might see about doing the same thing for Chrome and Firefox.

Your message did not reach some or all of the intended recipients.

Subject: FW: Offer

Sent: 20/09/2011 10:33

The following recipient(s) cannot be reached:

‘user@domain.com’ on 20/09/2011 10:33
None of your e-mail accounts could send to this recipient.

This problem is caused when the email address has been pasted into to the to: field with the mailto: portion still intact.

Go into the sent items and open the email that failed to transmit and then choose “resend this message” and then double click on the email address you will probably see something like this:

As in the picture the “E-mail type:” is set to MAILTO. Clicking on the Internet type button will reset it back to SMTP and should be able to send the message.

Sometimes the incorrect address can also get cached into your NK2 file, so you will need to remove it from your autocomplete cache to make sure that you don’t get the problem again.

So, I have rewritten the script in Powershell and it should now work on any system which has Powershell installed.  The new script is easier to read and includes support for SMTP over SSL, making the use of a Gmail account for sending the alerts very straightforward.

The whole process is very similar to the previous script, so if you used that one, this will be immediatly familiar.

Installation:

After you have downloaded the Zip file extract it to a folder on your server, e.g “C:\Script”

You will then need to edit the variables at the top of the script to make them appropriate for your environment:

If you do not specify an SMTPServer, it will default to localhost.  If you do not specify an SMTPPort it will default to port 25.

If you intend to use the script with a gmail account set:

$SMTPServer = “smtp.gmail.com”
$SMTPUser = Your gmail account name (without the @gmail.com part).
$SMTPPassword = Your gmail account password
$SMTPPort = 587
$EnableSSL = true

Test Email is functional

Now that you have the script installed open up a powershell prompt and run the script with the “testemail” parameter e.g:

c:\script\dellalerts.ps1 testemail

If everything is working properly you should receive a test alert in your inbox.

Setup Alerts from OpenManage

Once the email function has been tested you can go ahead and setup the script to run from open manage, simply run the script again with the “setup” parameter, and you should see something like this:

Testing

There are a few easy ways to test the script in practice with a real alert generated by OpenManage:

• Pop the side off the server casing, this will generate a chassis intrusion alert.
• If you have a dual powersupply system you can pull the power to one of the supplies and the server should report the power loss.

The problem with these methods is that you have to be in the same place as the server.  So I prefer to trigger a tempreture alert like this:

Just set the warning threshold to be a couple of degrees lower than your current reading.  Warning: If you have a thermal shutdown action configured, this could trigger that process off and shutdown your server.  Once you have received your test emails, set the tempreture wanrings back to default values.

Please let me know of any issues you have with the script and I will work on them as soon as possible.  I have installed this updated version on a number of systems and it is working well.

The download includes both the new version and the older VBScript version.

This Dynamic Distribution Group was created with the Exchange Management Shell. You can use the Exchange Managment Shell to modify the filter.

And all of the controls are disabled.

To update the recipient container from the Exchange Management Shell run:

Set-DynamicDistributionGroup -Identity DistributionGroupName -RecipientContainer ‘containername/ouname’

A common problem with Direct PDF printing is that it is not possible to include any printer control commands such as tray calls within the PDF and lots of people have been asking how to do this – I checked with HP Technical support and was told it is not possible.

It is possible however to setup a print job with PJL commands and include the PDF documents within that job. The key being to set the printer language/personality to PDF and then using the UEL (Universal Exit Language) command to issue more control commands. After a bit of trial and error I found that this is actually quite straightforward, and thought I would post the code as I was not able to find any working examples:


ESC%-12345X@PJL
@PJL JOB NAME = "paultest2.pdf" DISPLAY = "Printing & Stapling paultest2.pdf"
@PJL SET OUTBIN=OPTIONALOUTBIN1
@PJL SET PROCESSINGTYPE="STAPLING"
@PJL SET PROCESSINGOPTION="LEFT_1PT_ANGLED"
@PJL SET MEDIASOURCE = TRAY3
@PJL ENTER LANGUAGE = PDF


After setting up the job with the above, you can then add the PDF code. After the PDF you either need to end the job or specify more further printing control. In my example I am printing another PDF document right away within the same job but from a different tray, like so:


ESC%-12345X@PJL
@PJL SET MEDIASOURCE = TRAY4
@PJL ENTER LANGUAGE = PDF


Then follow this with more PDF data and then end the job like this:


ESC%-12345X@PJL
@PJL RESET
@PJL EOJ NAME = "paultest2.pdf"
ESC%-12345X


In this example the two PDFs are also being stapled together and the status display on the printer is also updated to show what document is being printed.

All of the above was tested using a HP Laserjet P4015N with a 500-Sheet Stapler/Stacker(CB522A). Although it contains no references to PDF printing, the best reference I have found is this document from HP:

http://h20000.www2.hp.com/bc/docs/support/SupportManual/bpl13208/bpl13208.pdf

In production I am doing all of the PJL wrapping via a korn shell script which I’ve tested from IBM AIX, Ubuntu and Sco Openserver 5.0.7.

A visitor to the blog called Steve has kindly posted some code on that post which enables the same functionality in Linux and I think it is worthy of its own post.

Before attempting to use the script you will need to download this perl script called sendEmail and that you have unix2dos installed.

The script accepts two arguments, which are setup or show.

“setup” will set the alerts action to the value of $alert_script which should be the full path to the script itself.
“show” will print the current alert settings for the system to the screen.

The code of the script is as follows, or you can download from here:

A good way to test the script is to temporarily set the “Temperature Maximum” to something low like 12 to trigger an alert.

Unfortunately all of my Linux machines are virtual machines so I cannot test or modify this script, so if anyone wants to give me SSH access to a server running OMSA, be my guest.

Again, big thanks to Steve for posting this and I am sure it will be useful to lots of people. This has also inspired me to make some improvements to my original Windows version.

Annoyingly clnpack.exe does not give any error messages at all if the syntax of the commad is not perfect and you get nowhere.  In the end I discovered that I could only make clnpack.exe work by using 8.3 file paths instead of long path names.

An example of a working command line:


C:\PROGRA~1\TRENDM~1\OfficeScan\PCCSRV\Admin\Utility\ClientPackager\clnpack.exe /i /o NT /s C:\PROGRA~1\TRENDM~1\OfficeScan\PCCSRV /d d:\shared~1\software\trend32.exe

You can see 8.3 format filenames by going into a command prompt and using:

dir /x

Now that I have this command working I can integrate it with a batch file which will upload it to our web server.

The function of the script is to perform scheduled reboots of Draytek routers.  Optionally is it possible to reboot the router only if a specified IP address does not respond to a ping request.  This is useful to test if a VPN connection is functioning, and only reboot the router if there is no response.

Early Draytek firmwares had a tendancy to lose VPN connectivity and a reboot is the only way to restore the connection.

First of you need to install the Toolsack Baseline components for this script to work:

http://www.toolsack.com/download/

The script needs to be supplied with parameters, so a typical command line would look like this:

cscript reboot.vbs 86.11.93.131 routerpassword

and a conditional command line would look like this:

cscript reboot.vbs 86.11.93.131 routerpassword 192.168.1.254

The 3rd argument will be tested for a ping response, if none is received then a reboot will be executed.

Here is the code, save it as reboot.vbs:

set args=wscript.arguments

If wscript.arguments.count=2 then
   IP=args.item(0)
   Password=args.item(1)
   call reboot(IP,Password)
elseif wscript.arguments.count=3 then
   IP=args.item(0)
   Password=args.item(1)
   TestIP=args.item(2)
   if ping(TestIP)=False then
      call reboot(IP,Password)
   end if
else
   wscript.echo "Invalid number of arguments specified"
   wscript.echo "Please specify router IP address & password and optional test IP"
end if

sub reboot(IP, Password)
   set s = CreateObject("Toolsack.Socket")
   s.Connect IP, 23
       s.Write Password & vbCrLf
   s.write "sys reboot" & vbcrlf
   s.write "quit" & vbcrlf
end sub

Function Ping(strHost)

    dim objPing, objRetStatus

    set objPing = GetObject("winmgmts:{impersonationLevel=impersonate}").ExecQuery _
      ("select * from Win32_PingStatus where address = '" & strHost & "'")

    for each objRetStatus in objPing
        if IsNull(objRetStatus.StatusCode) or objRetStatus.StatusCode<>0 then
       Ping = False
        else
            Ping = True
        end if
    next
End Function 

Visiting the backup URL manually ( http://localhost/backup/default.aspx ) enabled me to see the backup reports as normal.  Had a quick look in the code of default.htm which is the page that the “Manage Small Business Server Backup” console loads and saw that it is really just a javascript redirect.

Turns out that this server had scripting disabled for the intranet zone and therefore the page redirection was never happening.

Once scripting was enabled again the backup console started working as expected.  Couldn’t find mention of anyone else having this problem so thought I would post.

I am always forgetting the syntax for the New-ExchangeCertificate cmdlet when I need to do a new certificate request so I decided to write a little bit of javascript to build up the command automatically. Its much easier to copy and paste it from here than work with in it the Exchange 2007 Command Shell.

So just fill in the fields below and the command will be built automatically in the box below. Then just copy into command shell. If required, seperate the “Subject Alternative Names” with commas.

CSR Command:

I am thinking of duplicating this code and writing another post which will generate the commands for the import of the newly generated certificate.