Here’s a stupid script I made to export PHP IPAM to an Excel XLS, then email it to someone.
Edit the ipamexport.sh file to specify the URL and desired email recipient.
Edit the mailer.py file to specify your SMTP server and sender address.
Pop it in a crontab for scheduled exports.
You can review the source in my GitHub.
Screw paying for CDs on eBay.
Here’s a link to the D22 Service Manual covering models from ’97 to early ’08.
Click read more to get the link.
Had this error occur in my Hyper-V lab after playing with WinRM GPOs. After removing the GPO because SCVMM is a finicky pain – I was still receiving this error when attempting to create a new VM:
An internal error has occurred trying to contact the lab-hyperv1.lab.int server: : .
WinRM: URL: [http://lab-hyperv1.lab.int:5985], Verb: [INVOKE], Method: [CreateDirectory], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/FileInformation]
Invalid Signature (0x80090006)
Check that WS-Management service is installed and running on server lab-hyperv1.lab.int. For more information use the command "winrm helpmsg hresult". If lab-hyperv1.lab.int is a host/library/update server or a PXE server role then ensure that VMM agent is installed and running. Refer to http://support.microsoft.com/kb/2742275 for more details.
Here’s how to fix this:
- Remove the affected Hyper-V hosts from SCVMM
- Open Certificate Management (Computer) and make sure you don’t see certificates for the Hyper-V hosts in the ‘Trusted People’ store
- Re-add the Hyper-V hosts
You should now be able to create new VMs.
Back in the day, when mIRC and NoNameScript were my friends, I used to have a CTCP trigger set up that gave people DCC leeching from me the ability to resume transfers if they disconnected for some reason, amongst other things.
Now that I’m all Mac, I’ve been using Colloquy, and haven’t started looking at scripting for it – that is, until today.
Austnet are now blocking all DCC by default, and the only way to allow someone to send you a file is to issue the user command /dccallow +User <timeout> – adding them to a temporary Allow list. This, of course, only works if your nick is registered and you have identified with /nickop.
Place this script in your ~/Library/Application Support/Colloquy/Plugins directory, then issue a /reload plugins in Colloquy if it’s already open. People can then use /ctcp <Your Username> DCCALLOW to allow themselves DCC access to your username for 300 seconds. Additionally, if you want to auto-accept DCC requests from strangers, you’ll need to modify your Colloquy settings to allow it.