Posted on

Merging/Joining Get-aduser, Get-mailbox, and Get-mailboxstatistics

The other day, I was asked to provide an extract of all mailboxes in my exchange environment, along with attributes only available in other PS commands.

The below script provides the list (Get-Mailbox)along with a the sizes (Get-MailboxStatistics) and users’s associated dept(Get-User).

Hope it helps you.

Get-Mailbox -resultsize unlimited | sort-object | Select-Object DisplayName,PrimarySmtpAddress,@{n=”Size(KB)”;e = {$MBXstat = Get-MailboxStatistics $_.name; $MBXstat.totalItemsize}}, @{n=”ItemAcount”;e = {$MBXstat = Get-MailboxStatistics $_.name; $MBXstat.itemcount}},@{n=”Dept”;e={(get-aduser $_.name -properties department).department}} | export-csv mailboxout.csv

Posted on

iOS bug sends iPhones into endless crash

https://www.youtube.com/watch?v=PmgI0LaFYLA

 

There’s a bug in Apple’s iOS 8 that allows nearby attackers to send apps—and in some cases the iPhone or iPad they run on—into an endless reboot cycle that temporarily renders the devices useless, according to researchers who demonstrated the attack Tuesday.The exploit uses a standard Wi-Fi network that generates a specially designed secure sockets layer (SSL) certificate to exploit the bug, according to the researchers, who work for Israel-based Skycure. The encrypted communication causes whatever apps happen to be connected to the booby-trapped Wi-Fi network to crash. The vulnerability was introduced in version 8 of the Apple mobile operating system.

Read on, source: iOS bug sends iPhones into endless crash cycle when exposed to rogue Wi-Fi | Ars Technica

Posted on

Simpana 8.0 and Linux Clients – 19:599

Recent experience with Simpana is that jobs are submitted to for backup yet fail instantly after the job is started with error 19:599. Not much to go by and not much in Google either; nor the forums.

This issue seems to happen after the upgrade of Ubuntu based client to OS and security patches to 14.04.

Re-installing, reboot of the client and connectivity tests (ping, dns resolution, telnet client 8400+8402 to CV, and Media box; then all the way back again) do not resolve the issue.

After enough days of reading longs, the /etc/hosts file was found to be bad in that erroneous entries as such were present:

127.0.1.1 Localhost

One would expect the CV agent to be bound to an IP address, however along the way you will be fooled by the simple fact that the machine is about to answer to pings, had the required ports open, dns also matches its IP address, and firewalls have been disabled for testing purposes, so, from a network point of view; all is well. Change this and you will be in business.

Resolution is as follows:

  • Change the /etc/hosts entry with your favorite txt editor hosts to the actual IP of the client:
    • Original – 127.0.1.1 Localhost
    • New – x.x.x.x fqdn
  • Restart of the Simpana services from terminal using sudo simpana restart 
  • Check that your services are running with sudo simpana list

You will now find out that restarting the job with allow for a successful backup.

Posted on

Migrate Your WordPress to Turnkey-WordPress

So, today I had decided to try out TurnKey linux to run my wordpress instead of the traditional ubuntu + all the manual components to a simple, out of the box solution that could be run as a virtual machine with a readily prepped linux environment.

Getting the machine going is a breeze, a quick tutorial may be found here:

About 5 minutes – pretty straight forward to setup.

Seeing this blogpost is going to be hindsight for me and informative for you, I would also recommend using VMWare Workstation for the snapshots, I took one once I had a clean VM with all the patches and such.

If you have only been needing a clean install, you can stop reading here but if your are upgrading, the following steps will save you a bit of googling.

First of all you will need to export your original posts which can be found from your tools > export of your original worpress.org site.

Next up, we will assume you have already gotten your site up and running if you followed the guide above because you will need to re-import it into your new site. This you will do after logging into your new wp-admin. Below are a few considerations which should be tackled in the following order:

  1. Login – and create yourself a new user – this user will be used to take ownership of your posts in your NEW blog.
  2. When importing, WP will ask you to download a the WordPress importer; do it!
  3. Once imported you will need to alter your wp-config.php, please also note the location and how I modified it.
    Turnkey offers a nice/lazy way of editing your config files. This can be found at https://wp-ip-address:12321 then navigate to your Tools then File manager.
    Modify the following few fields withing the php file. wp-config
  4. Ok, we are halfway there. Now to change two fields into on your database, logon to your php myadmin using https://wp-ip-address:12321, select your wordpress database from your drag-down box. and open your wp_options table. Here you will need to change two fields; home AND site url to incorporate reflect your new site.
    siteurl
  5. Probably the most important issue I have faced is getting the <a href> of the pictures pointing towards the external facing site and not the internal ip address of the server. to address that, a little hunting around gave me the following SQL query I ran on the website instead of doing it manually.
    You can tun the following update by clicking on SQL on your MyPHP:
    UPDATE wp_posts set post_content=REPLACE(post_content, ‘192.168.2.225/’, ‘www.georgeene.com/’)

And – Voila and welcome to your new wordpress block running on next to no resources and is FAST given the apace + debian back-end.