Conversation history not saving in Outlook 2010

May 20, 2013August 31, 2015 Josh Reichardt 1 Comment

Recently I ran into an issue with a Lync environment (2010) where Lync conversations were not being saved to the “Conversation History” folder in Outlook (2010). Luckily there is a quick way to fix this issue, through Exchange. From the reading that I have done it seems like the most common reason this occurs is when a user in your Exchange environment reaches or surpasses 1,000 combined folders and sub folders in their mailbox. The easiest way to check if a user has reached this threshold is to use the Exchange Management Shell to quickly take a look at their total combined mailbox folders using the following command.

(Get-MailboxFolderStatistics “user”).Count

Easy enough, often times this is enough to determine the cause. But I have taken this command one step further and wrapped it into a little script that will go through your Exchange environment and record all users that have reached this threshold and place their display name as well as the number of folders/subfolders into a csv file for an easier to reference. Here is the logic of the script.

$mailboxes = Get-Mailbox
$overlimit = @()

ForEach ($mailbox in $mailboxes) {

$mbxmember = New-Object PSObject
$folders = (Get-MailboxFolderStatistics $mailbox).Count
$mbxmember | Add-Member -MemberType NoteProperty -Name "Display Name" -Value $mailbox.DisplayName
$mbxmember | Add-Member -MemberType NoteProperty –Name “Folder Count” –Value $folders

	If ($folders -gt 1000) {
		$overlimit += $mbxmember
	}
}

$overlimit

That logic right there is very basic but will iterate over all mailboxes in the Exchange environment, grab those with over 1,000 folders/sub folders, place them into an array and output the array. This will take a while depending on the size of your environment, so feel free to let it run in the background. It is not a super intensive process, it just takes forever. To get this into a CSV file use the following Powershell command, I have this script name Get-Folders.ps1 in this example.

.\Get-Folders.ps1 | Export-CSV users.csv

That should be it. Not everybody will need this obviously but I found that it came in handy.

Evo 4G Customization Goodness

May 13, 2013August 31, 2015 Josh Reichardt 13 Comments

Since my initial rooting and unlocking project last weekend I haven’t been able to stop thinking about the shiny new ROM I have installed and how awesome it is. So now that I have the taste for flashing custom ROM’s, I wanted to see what else was out there. I did some digging and learned (to my happy surprise) that the Evo 4G, or the “OG” as community members refer to it as, is still alive and well, with a very talented community and very active user base. Especially for a device that is nearly 3 years old.

If you missed my original ROM flashing post you can view it here. That should get you up speed.

Custom ROM’s can be confusing and maybe a bit intimidating at first but once you start to wrap your head around the concept then things get much easier. If you have any questions let me know and I will do my best to help explain things as best I can (from my own understanding of how it all works at this point). I am certainly new to this as well but am quickly beginning to understand the power and draw behind custom ROM’s, especially for tinkerers and people that are interested in DIY tech projects, there is really a whole world out there to go explore for this type of stuff. I would take a look at XDA Developers forum for a good place to get started on many of these topics.

I am working on putting together a list of the latest and greatest ROM’s that I have stumbled across since my initial flash using the MazWoz Jelly Bean ROM last week. I will also try to offer some perspective and comparisons between these custom ROM’s to help you choose which one will suit your needs and will work best in your use case. All of the ROM’s that I have been testing are currently all 4.2.x (Jelly Bean) and are all fantastic, so if you are having trouble picking one out I would advise that you just pick one. More than likely it will be a good fit. The only difference between many of these are small subtleties such as specific themes, customization options, look and feel and a few packaged apps here and there. So for example, Slim Bean offers a UI “pie controls” that aren’t built in to some of the other ROM’s. But for the most part many of these ROM’s are using a lot of the same “stuff” in the background. There are probably more out there but I will just be covering the most popular and most active ROM’s that I cam across, so let’s go ahead get started.

MazWoz – http://forum.xda-developers.com/showthread.php?t=1947452

This is a great ROM and the first custom ROM that I tried. Nearly everything is working currently, it is certainly stable enough for every day use IMO. It did a hot reboot on me once and the camera was a little bit on the glitchy side, there were some strange GUI effect glitches every now and WiMax is broken (which won’t get a fix it doesn’t look like but who cares) but otherwise worked flawlessly, it is very snappy and responsive, it provides a buttery smooth experience. I would highly recommend giving this ROM a shot since it is both stable and smooth. It isn’t quite there 100% on all the new Jelly Bean features but it is getting there and is under active development by its creator and maintainer. The latest release was about a month ago so hopefully there will be an update to provide some of these niceties in the near future.

Slim Bean – http://forum.xda-developers.com/showthread.php?t=2217412

Currently testing this ROM out. So far so good, it is fast and everything I’ve tried seems to be working correctly. This ROM is designed to be light weight and snappy, so only basic themes, look and feel and apps although I will say that after booting initially it felt a very tiny bit slower than the MazWoz ROM but this slowdown was still very tolerable. I suspect there may have been issues since it was trying to sync up and download things in the background, because everything has been working much more smoothly after the everything is in sync. The camera works slightly more fluidly than the MazWoz camera and there do not appear to be any other noticibly odd glicthy behaviors with the GUI. Other initial findings were that there is no WiMax (again expected) and no front camera. This ROM is very smooth and there is support for facial recognition and unlock which is pretty slick. There are some other cool features baked in such that other ROM’s do not offer such as “The Real Dark Slim (TRDS)” which is basically a customization engine for this particular ROM as well as Slim PIE and a few other unique customizations for this ROM which allow for a more fine tuned experience.

Cyanogenmod 10.1 – http://forum.xda-developers.com/showthread.php?t=2244061

This is the defacto for custom ROM’s currently, it easily has the largest user and developer base and its latest version has been ported over to the Evo 4G. This is pretty much the most complete package as far as custom 4.2.x ROM’s go. It has basically every standard feature that comes along with this version of Android as well as a ton of tweaks and improvement, including pie controls and speed/optimization improvements and other nice goodies. There is no official release for this build because this current port literally just happened not more than a few weeks ago but I’m sure the word will spread quickly. So far I have liked this release for the most part, there are some issues though, such as a little big of glitchiness as with the other releases I have tried, the swype style keyboard doesn’t work all the time, the launcher (trebuchet) crashed ones, no front camera, some of the camera options aren’t perfect either and there is no WiMax support. These are really just small gripes though and outside of that it is snappy and also probably the smoothest ROM I’ve tried so far. It has some slick features built in including a custom launcher, file manager and media player, as well as some additional themes and widgets built in which are a really nice touch. The CyanogenMod is an all around good experience and with all of the little additions and bells and whistles built in has been my favorite ROM so far.

AOKP – http://forum.xda-developers.com/showthread.php?t=2257194

This is one of the newer projects out there but it is gathering steam and the community as well as developers have really worked hard to make this ROM very nice. The features of this ROM are on par (some may even say better) than Cyanognmod and this ROM certainly delivers so very nice customization options as well as a stable and fast platform. I have only recently tried this ROM out myself yet so I can’t report on all of the issues that it has other than the standard issues that all of these ROM’s suffer from. No front camera, no WiMax, some weird camera issues, etc. Nothing out of the ordinary. I have really liked the quickness of this ROM so far, I’d say it is on par or better than Slim Bean and offers a really nice experience overall and the ability for a lot of customization. I would definitely recommend trying this ROM out. The only caveat for getting this ROM to work correctly is that you need to partition your SD card prior to flashing, otherwise you will suffer from boot loops which caught me originally. Other than that, it is pretty straight forward to flash and use.

Evervolv – http://forum.xda-developers.com/showthread.php?t=2172323

This one is worth a mention as well but seems to be losing some of its previous favor amongst the community as of late (at least as far as I can tell, I could be totally wrong about this though). It seems like a lot of ROM’s are built using much of Evervolv’s code but the project itself isn’t quite as popular as it was at one time. I haven’t tried this ROM out for myself yet, I just found that it was worth a mention because of its support for the Evo 4 G. I might come back and update this post if I ever switch and try this ROM out, but I just can’t get away from Cyanogenmod right now.

Hack your Evo 4G into a High End Smart Phone

May 6, 2013August 31, 2015 Josh Reichardt 5 Comments

I was in desperate need of a phone upgrade recently and ran across a nice little deal on an old Evo 4G (not to be confused with the Evo 4G LTE) on craigslist this past weekend, which to my surprise turned into a nice little phone hacking project. Luckily for me the phone I got was basically in mint condition as it belonged to an older gentlemen who I imagine didn’t get a lot of mileage out of it. On top of that, it was layered in protective casings.

Sometimes buying phones on craigslist can be scary and turn into a crap shoot but in my own experience I’ve found them to work out more often than not. The two pieces of advice I can offer when buying a used phone on craigslist are to have the seller send you the ESN number prior to meeting so you can check to make sure it is active (there are many online ESN checkers out there). The other, simple advice is to look at the phone when you meet and make sure you can turn it on and off and that it can hold a charge.

I also want to take a moment and tell everybody about the provider I use, which is Ting. Why? Because they are awesome and super easy to use. Ting offers a very competitive price and doesn’t require contracts, which I believe are important things to consider when selecting a provider. Anyway, I could probably write an entire post about how awesome Ting is and why you should use their service but I will forego the details for now. I just wanted to mention that you can activate your phone entirely on your own in like 5 minutes, which helped me out a lot with this project. There are detailed instructions on their site about activating new/used phones and porting over numbers, it is easy and Ting even encourages its users to root and unlock their phones. Long story short, Ting is awesome, it made this project much easier and you should give them a try.

Once you do all the running around and finally get your phone it is time to actually get down to the fun stuff. I learned that rooting the Evo 4G was a bit tricky since it had all of the newest firmware and protection from HTC. I have had less issues with rooting some other HTC devices in the past, but I don’t know how that effects the steps if the software and firmware change. In all reality the additional steps are just a technicality I would say and aren’t too much of a hindrance. So in the following details I will outline the process of getting your phone from the basic locked version of HTC Android to a fully unlocked phone with the capability of running custom ROMS, namely the MazWoz ROM which is currently the Jelly Bean ROM that I am using for the Evo 4G.

The first step is to get root. This is essential because without it you will not be able to get S-OFF and be able to flash custom ROM’s. Rather than go into great detail and post all of the steps here I will instead point you in the right direction on how to get started yourself. There are a ton of guides out there already on how to do this and there would really be no point to add another to that collection of guides, since there are some really good ones out there that have all the links and resources. I found this one and this one to be the most relevant and helpful. The first one is especially nice because it offers some video guidance as well as written. Basically when I got stuck with one of the guides I would just switch back and forth and reference the other. I feel that they both definitely compliment each other very well.

The second step is to obtain S-OFF. Use the links mentioned previously for obtaining root to obtain S-OFF as well, after you root your phone. This step was very confusing to me at first so I thought I would clarify the process to make things easier for readers to understand. Once you have root on your phone you can The major issue I ran across with this step was when I reached the step for copying over the flashimage and mtd-eng.img files. To get this step to work I had to be in Fastboot mode to gain read/write access to the sdcard. Other than that, everything else worked great. I should also note that for S-OFF I chose to use to use revolutionary.exe following the instructions from the first site. I think the steps for flashing S-OFF using the unrevoked method from the second link would work fine, maybe even preferably, I just never tested this myself.

The third step is to flash the custom ROM, along with the other apps and fixes that turn your phone in the Jelly Bean device. Jelly Bean brings with it a number of features and improvements that make for a much better, much smoother smart phone experience. It is really leaps and bounds above the stock version of Android OS that is shipped by default on the Evo 4G and the experience is often referred to as “buttery smooth” because it is so nice. Here is the link for getting the MazWoz Supersonic ROM. I used the B4 release, which is the most current as of this writing as well as the link to Gapps and the GPS fix. As of the B4 release the WiMax wasn’t working and the video is a little glitchy and the front camera isn’t working but other than that, this ROM is a fully functioning 4.2.1 Jelly Bean image. The WiMax isn’t important to me as I don’t have access to it where I live and the video isn’t really a big issue for me either since I don’t shoot a lot of video.

The positives of using this custom ROM immensely outweigh the negatives in my opinion. So all in all, hacking an almost 3 year old phone in about 3 hours time into a usable Jelly Bean device that typically sells for upwards of $300 for the bargain $80 price tag seems like a steal to me, the experience is nearly flawless. Granted there are a few caveats and you need to be willing to follow the steps for the upgrade but in my opinion this is still a great deal. You get to a) revive an old piece of hardware that is beginning to show its age, b) save a shitload of money on the cost of a new phone and c) get to tinker with your phone, which to me was the best part out of this project. Here is a link to some other devices that have been quickly faded in popularity that can potentially be updated and given new life. My hop is that this post will inspire you or at least give you some ideas to go and check what’s out there and maybe even help breathe some new life into some of your otherwise antiquated and dying android devices.

Fix the “Can’t create highly Available VM” error in VMM

May 3, 2013August 31, 2015 Josh Reichardt 7 Comments

I was doing some lab testing with Virtual Machine Manager (VMM) for my Hyper-V environment the other day when I ran across this issue. It was happening because I was attempting to save my disk image to a CSV location and I couldn’t figure out why it was blowing up.

It turns out that the answer is really simple actually but is annoying to fix. So here is what the error looks like in VMM. “Cannot create or update a non highly available virtual machine because the path cluster storage volume is a clustered resource error”. Surprisingly Google didn’t turn up much for how to fix this so I thought I would make a note of it in case others happen to run across this.

The fix is simple enough, I just wish VMM was smart enough to know when you select a CSV to use for storage. When you go through the VM creation process and you get to the hardware selection tab, choose the “Make this virtual machine highly available” check box.

If you happen to be building a lot of identical (or near identical) VM’s I reccomend checking out Profiles through VMM, in this case a specific hardware profile for desktop VM’s. Creating profiles simplifies the build and creation process and you don’t need to worry about picking all the right defaults without having your VM creation blow up.

Automatic Load Balancing Fails for New Exchange Mailboxes

April 26, 2013August 31, 2015 Josh Reichardt 9 Comments

I had a strange issue come up recently where mail administrators were unable to allow Exchange to pick which mailbox database to place users into (I’m not quite sure what this feature is called so we’re going with automatic load balancing) when they were creating new user mailbox profiles. This feature essentially picks a database at random as a way to balance and spread out mailboxes among databases. Makes, sense to me. Anyway, I’m thinking we may have installed an update that changed the behavior because this feature had apparently been working up until we installed Rollup 5-v2. So it appears that this update had broken this automatic mailbox load balancing functionality, although I’m not 100% sure. I just wanted to mention it in case some of you are looking for clues as to why this is happening.

So here is what the error looks like when allowing Exchange to choose which database to use when a new user is initially created.

Error: Load balancing failed to find a valid mailbox database.

Hmm, okay. That is weird. You can check to see if the database is set to be allowed with this command.

get-mailboxdatabase | ft name,isexcludedfromprovisioning

In my case, all of my mailbox databases came back true, so they are unable to be used for automatically selecting a database when the user created. To fix this, go ahead and run the following.

get-mailboxdatabase | set-mailboxdatabase -isexcludedfromprovisioning $false

Now go ahead and run the first command again and you should see that all the mailboxes are now marked as false, meaning they are now included in the provisioning process.

Now you should be able to go through and create without selecing a specific mailbox. My best guess is that the update must have set this flag to exclude these databases from provisioning but is weird and is worth mentioning because it happened to cause some seemingly unexplained issues for us.