Monday, May 31, 2010

OWA Pictures still missing!!

So, After my previous fix, the OWA pictures started not-loading again.

I moved the contents of the most recent folder under the program files/microsoft/exchange/client access/owa directory to a safe place, for safe keeping, and issued a command to create a junction, with the same name as the directory that I just moved, linking it to the previous version.

to do this, I used the command line command: mklink /J

or something of the sort.

This effectively copied/pasted the contents of the previous version into the "current version"s directory.

OWA works again.

Of course, I checked to make sure the application settings were correct in IIS Manager first...

good luck to all those who many be experiencing this problem

Saturday, May 22, 2010

Google

With a new phone, powered by the operating system, made by google; and having used google for just about everything from directions, to mail, to organizing my day, to talking to friends... I just wanted to put out a thank you.

Thanks Google.

For winning over our hearts and minds by being more than just a good search engine.

Friday, May 21, 2010

Exchange OWA pictures missing!

After a recent update, automatically applied to my server as of the last time it was active; likely incomplete, my OWA's pictures stoppped working.

I finally resolved the problem.

You can go through and debug every little error, if you'd like, and I recommend it, a smooth OWA is a happy OWA, but what I found the problem was, was pictures that were missing.

The confusing part about OWA and Exchange's web presence (Client Access), is that it's all so intricate that it's hard to decode. Take a look at your %programfiles% folder, under Microsoft\Exchange Server\ClientAccess\Owa\

You'll see some base files and a series of folders, mine all started with 8.1.###.#

I have about five different versions of the OWA server installed. at least, that's what I'm gathering from the different version numbered folders. I would presume that the ASPX files in the root, dynamically load the newest OWA revision in the folder.

An easy and quick fix would be to revert back to an old OWA, just delete the newest (highest numbered) folder, and voila, it should work... My problem was that I was missing the pictures from owa and owa lite.

I since havn't gotten OWA premium working, but I suspect it might be a problem with my IE on this system, I have to do more investigating before I figure it out. Regardless, to fix a problem like the pictures, go into the 2nd newest folder (where I presume you had OWA access with everything working as expected) copy the themes folder, and paste it into your newest owa folder, combining it with the existing contents. There were css's in my existing folder, which I chose to keep, but I would assume that the damage would be negligible if one were to decide to "overwrite all" in this scenario.

if you've done this, or confirmed the folders have gif's and jpg's or whatever, in them, then you're dealing with a permissions issue. be sure to give the IIS user account (IUSR_ for IIS6 and IUSR for IIS7) read access to the theme folder, recursive. that should fix the problem of no pictures working, and should at least get OWA lite working.

getting a straight forward answer with all this has been difficult, but when I noticed the subfolders under themes, in the newest version of the owa directories, only contained one css file, and the older version numbers had many more files of varying types (mostly css, gif, etc), I decided to give it a go; and it worked!

Now, if I could only find that guide I had that explained how to use self-signed server certificates for Exchange ActiveSync...

I know it has to be done from the command line, since the GUI doesn't have the necessary options to create a self-signed cert for a dns entry that it does not technically inhabit. To explain, my server is located behind a NAT firewall, with port forwarding for port 443 (SSL). The servers address, according to the server is WIN-*random characters*.domain, where, to the rest of the internet (and any web-accessing Windows Mobile device) will see it as simply the domain name (no computer name). So, the server needs to issue a self-signed cert, that the public key is exportable to the device (for manual addition, RE: Trust), for the root domain.

I'll do the work for it later, when I have time, for now, OWA works, despite the certificate errors.

Tuesday, May 18, 2010

(sometimes not-so-) Smartphones

I started my journey with smartphones about a year back, I was an avid Windows Mobile user and I started with a very simple philosophy. This philosophy was based on the fact that I had, in the past, had experience with Windows Mobile as a platform for PDAs, and experience with the Dell Axim x51v, which was built by HTC.

So my philosophy was, combine HTC, with Windows Mobile (preferably something later than version 6), and you should come out a winner. I was wrong.

I ended up buying the HTC Touch Pro, from Telus Mobility, here in Canada. We don't have very good options for mobile networks here, and I don't want to get into the nuances of why Telus is superior over the other two of the big three (Bell, Telus, and Rogers). Needless to say, it took me a long time to arrive on Telus' door. Now that I'm here, I'm not leaving.

At first, I was really satisfied with the device, I even setup an exchange server for the purposes of sync-ing my contacts, calendar, etc. Though, I didn't have, at the time, a proper DNS or MX setup (nor did I know how at the time), so the system wouldn't RECEIVE any email, however, it worked for what I needed. I had to reset my phone a few times during the past year and the exchange server was instrumental for getting up and running quickly.

There are two major quirks with this phone, from this provider, that I can point to as a primary reason for me wanting to rid myself of it.

First, and primarily, is text messaging. Don't get me wrong, texting on the Touch Pro was a dream, however, the phone would wake up EVERY TIME a text was received. This means that the touch screen is active and there's a lot that can go wrong when you don't hear the text message alert tone and the phone is rattling around in your pocket for a few minutes. I had one instance where I "pocket dialed" someone more than half a dozen times (the same person!)...

I searched without luck to try and figure out how to fix the problem and eventually just lived with it until I got so fed up that I replaced the phone.

I know there are a lot of people who may yell and scream and jump up and down saying that there are apps for that, and ways to lock out the screen so that even if it comes on, it won't end up pocket dialing people. To them, I would say that I have yet to find a solution that isn't completely and totally irritating, every time you turn on your phone, that maintains the overall performance of the phone. There's a built-in screen lock, which requires a code to unlock, not convenient if you just want to quickly look to see who's sent you a text or email; there's also 3rd party applications like S2U2, which I actually tried for a time, but found the overall latency that it added to the phone was more costly than the convenience of having it.

Secondly, there was the phone. As a multimedia, email, texting device, as well as an organizer for contacts, and planning my day, The HTC Touch Pro was excellent in almost every regard, some areas a little less so, but overall, excellent. As a phone however, it just wasn't very good at all. Don't get me wrong, the overall experience, talking on the phone, etc, was adequate, and you could clearly understand the person on the other end and listen to what they had to say, additionally, they could hear you, etc.

That's not what I'm talking about.

After about 10-15 seconds on the phone, the display would turn off. The only way to re-activate it, is to hit the power button... with automated systems that have greetings longer than "hello", by the time you get the opportunity to make a selection, enter your parties extension, or enter your password (in the case of voice mail) the display is off. A minor gripe, I'll admit but still, every time. There's probably a way to change this, but at the time, I was so tired of fighting with the phone to get it to do what I wanted, that I just decided to live with it.

after that, the keypad wasn't always responsive. you could hit three or four keys before it would respond, but it would remember each button pressed on-screen, so you could, for the most part, punch in an extension even when it's not responding, and it would eventually send the tones. unfortunately, they register as very short taps, so the tones are also very short, which, with some systems, cause the numbers not to be recognized; this resulted in having to re-enter the same sequence, more slowly.

Additionally, the phone application, when ending a call, would completely lock up the phone for 10-15 seconds with no discernible reason. The system would spring back to life (all your taps would be recognized at once), and you'd end up back in business. Again, a minor gripe for sure, but should I really have to wait 15 seconds to suspend my phone after every call? This is wasting time in my life, and often I'm only waiting for it to respond long enough to exit from the phone application and shut off the phone so I can go and do something else.

Yesterday, I officially took the plunge; into financial termoil, and bought a new smart(er) phone. Since I'm always eager to try something new, I decided to give a go at an Android phone. I can, and have, used almost every other mobile operating system, and here's my general rundown:

Standard phones: with most 'regular' cellphones, an OS is an OS. the presentation and layout may vary, but the content is pretty much set. If you've seen one T9/"Predictive Text" input, you've generally seen them all. Buttons vary, eg. which button is the space bar and which one selects the next potential word, but beyond that, there isn't much variation. Even with that said, I prefer the OS you'll find on Samsung phones. It's fairly clean and responsive, without a lot of extras, which I like. I'm also a personal fan of Samsung. there isn't much that I'm not a fan of, other than Sony.

Apple and apple related products: I have a relative with an ipod touch, as well as several friends with the same affliction. There's others that I'm sure I know with iphones, but honestly, from what I've seen, other than the ability to call someone, and text, and the freedom to use a 3g network as opposed to being confined to within wifi range, there's not a lot of difference between the OSes. they're neat and organized with little variation. I don't like the interface myself, and with the lack of multitasking on the phone, I would rather not own one. Granted, on a small-format device like a cellphone, you're probably not going to be jumping between apps like you would on a Desktop, but still; knowing my MSN or gtalk is running in the background collecting messages for me, so that I'm available to friends and family for a large percentage of my day, is important to me, and I can't see that being feasible on one of these devices.

They're nice, I'll give them that. They have good hardware, and apple knows what they're doing when it comes to hardware. but the support is lacking.

Blackberries: You've seen one, you've seen them all. I guess that's good in a way. other than the fact that some don't have keyboards, and it's now all done on-screen, there isn't much variation here. A friend of mine bought a blackberry a week or more ago, and I finally got a chance to play with it the other day. I found myself thoroughly bored with the interface, almost searching for something to do on the phone. These are, very much, work devices. if you're not emailing, sending texts, talking on the phone, or using it for something else, likely related to that, you're probably not using it at all. Don't get me wrong, a blackberry has it's place, but if I wanted an overpriced, souped up Nokia 5190, I'd buy one.

Which brings me to my next point,

Symbian: I'm not sure why this deserves it's own catagory, but I'll roll with it. Symbian is a beefed up version of the same, recycled operating system that's been used on Nokia phones since they could program one in. I first experienced the early, almost "beta" version of symbian on the 5190, and again on the 6190, and again on the 7210. When a friend of mine literally destroyed his 7190 out of pure frustration, I decided to move in a different direction. I havn't kept up to date with development of this operating system; I don't think many have. To be honest, it's almost sad to see how much Nokia has fallen. Their phones are usually of fairly good build quality though, so if you're not in the smartphone market, Nokia's are usually solid devices.

As a smartphone though, I wouldn't choose a Nokia over a blackberry. just wouldn't happen.

Saving the best for last, Android.

Google keeps out pacing itself, and I hope this keeps up. Everytime I see some new, supposedly amazing google application or device or something, I remain skeptical; even if I sometimes get in on a beta (eg. google wave). I usually end up plesantly surprised, but I usually keep away from google's products until they've proven themselves in the market. I moved to Google Chrome as my primary browser and have slowly adopted most of google's online offerings through a multitude of gmail accounts. There are some products they've come up with, that are currently US only that I would be eager to try out, despite my skepticism (eg. Google Voice).

With all that being said, Android is a truly unique platform, in the sense that it supports and almost promotes free software distribution, while allowing for the potential of proprietary, 3rd party applications to be installed as well. As an operating system and as a standard, it's truly a beautiful product, regardless of the hardware.

Hardware helps though, and there's a lot to choose from with google's offerings. They've created an almost invincible alliance with HTC, who seemed to be, until recently, lost in a haze of making products for other people (eg, Dell Axims). Now, with HTC at their side, Google seems to be blazing forwards with a new momentum, taking over a vastly expanding market; cellphones. They aren't without competition, and I'd be lying if I said I knew a lot of people with Android phones. But interest remains high, and improvements to existing devices and releases of new ROMS is fairly common, to devices that will support the new features.

After looking over the options, I decided to get a Motorola Milestone from Telus. I chose this option for 3 reasons.

First, I decided on the Milestone, because of the keyboard. Being a long time cellphone keyboard lover (starting with a Nokia 6865? from Rogers), I've long since loved having a keyboard for texting on my cellphone. With the addition of MSN and gtalk, as well as Email and Web browsing, not to mention the social networking applications, etc; a keyboard makes sense.

Next, why the version from Telus? The price of a Milestone from expansys.ca is actually LESS than the base cost of the Milestone handset from Telus. However, Telus was offering me a discount on buying a phone by renewing my contract and agreeing to re-start my 3 years with them... I'm only a year into my contract and it looks like the Touch Pro won't make it 2 more, so I'm okay with that.

Finally, the Milestone is advertised as coming with an 8GB MicroSDHC card. This is for all the various applications and content you'll want to put on your device. This phone is a multimedia powerhouse, with a WXGA display, so 8GB is more like a minimum than anything. With that said, Telus was offering the Milestone with an included 16GB MicroSDHC card. I later discovered this is a Class 2 card, but the performance of my specific card seem to be more around Class 4-6, so I've been fortunate.

Overall, the purchase cost me less, I also ended up grabbing up a power adapter for my car, and an otter case for it, I still have yet to get a holster style case for it, which I've done with every phone I can remember (since the 7210). But this too will come with time.

Initial impressions are good. There's lots of free software in the Android market, and I'm overall pleased with the performance of 2.1. I'm somewhat disappointed at the video format compatibility, even with x264 encoded video, an mkv file will still not play natively on the phone. the x264 codec should be directly compatible with the h.264 decoder built into the phone, however, the media player will not demux the mkv file.

I have a lot of testing and discovery left to do with this phone, and I hope it's a plesant experience overall. So far, so good. And there's a built-in slide-unlocker... even though the phone will remain "off" when getting a text! woo. So far, all my gripes about the Touch Pro are gone, I wonder what other gripes I'll find.

If you're curious and want me to check something, just leave a comment, I'll be happy to try something out on the phone and get back to you. I'll be happy to answer any other questions that may be posted too :)

Saturday, May 15, 2010

Wifi

I know my blog doesn't reach very far yet, and most of the people who have seen it, and will be reading it currently, don't have an extensive technical knowlege, so with that in mind, I move forward.

My blogs will become more technically driven, worded and oriented as time goes on, but if you find that I'm explaining simple technical concepts here, that's because I expect most of my readers to be non-technical people.

I just saw a video on youtube about a man who boosted his wifi signal strength for less than $1, using an old box and some aluminum foil. I'd like to throw support behind the guy, and he's got the concept right, but the implementation is clearly done by someone without technical knowledge of how wireless functions.

for the purposes of this article we'll be talking about the most common wifi, which is 802.11g, 2.4ghz wireless.

Here's a brief rundown: In optimal conditions, a wireless router produces an alternating current through a wire, at 2.4 billion iterations per second, which produces an electromagnetic wave, which travels through space towards its intended target. this wave travels at light speed in a vacuum, but since we don't live in one, it's slowed down by air and whatnot. Regardless, at 2.4Ghz, and the distance that an electromagnetic wave can travel in one second, we can determine the wavelength. The wavelength is how long one hz, or one iteration of the wave occurs (meaning it goes up, comes down, and comes back to center). from all the math, we can determine that a 2.4ghz wave has a wavelength of aproximately 12.5cm (or 4.9something inches). all this aside, the 802.11 protocol has been designed with reflections and noise accounted for, so your computer isn't expecting a clean wifi signal to begin with. with this guy's reflector being... what? 2cm from his antennas, it causes a reflection that is out of phase.

brifely, phase is where in the wave you are, it's measured in degrees, starting at zero degrees from centre, going upwards to the highest level, at 90 degrees, returning to the zero line, at 180 degrees, and the lowest level at 270 degrees, then returning to zero again at 360 (or zero) degrees.

the out of phase signal is accounted for by the wifi card and it interprets it with the rest of the data on the wireless channel, but it makes for an uneven waveform (which actually damages the potential signal quality).

The intention is to put two waves, in phase, and by doing so, the two compliment each other and amplify each other. to do this, the reflector should be one-half wavelength away from the antennas on the opposite side of the antenna related to the desired target (aka behind it).

all this techobabble means that if you want to boost your signal better, you need to have the reflector exactly 6.25cm behind your antennas (for 2.4ghz). obviously, he's far under this, I doubt he's even 1/4 wavelength behind the antennas, which means he's probably giving two waves to the target that are 1/8th wavelength, or 45 degrees out of sync. albeit, it will still be more powerful than without the reflector, but move that reflector to 1/4 wavelength and you would actually have a negative impact on wireless performance.

Optimally, the reflector should be parabolic, or rounded, around the antennas, maintaining a constant distance from the signal origin.

I hope this explains some of the nuances of wifi technology and signal enhancing technologies. his idea is good and it's a very simple and effective way to increase signal strenth (if done right).

I hope you all enjoyed, good luck if you're trying this, and happy wifi-ing.

Wednesday, May 12, 2010

Trying to Untangle the Tubes

Hello Internet!

or as some of us like to call it, the tubes.

This is, of course, my very first posting here and I would like to start with a statement of intent. This, is my very own tech-blog. This will be where I talk about technical matters of grave importance to me, and give my opinions on a vast array of topics, from network security, system security, server setup, network topology, microtechnology, robotics, cell phones, operating systems, applications, and hardware... there's probably more, but you get the idea.

Currently, I'm working on embedding all of my current endeavours into a single unified webspace, and, if you're reading this significantly after I've posted it, it may already exist; you may have even been referred here from it. In either case, I welcome you to my thoughts.

Personally, I am interested in a wide array of technologies, including microsystems and robotic, though my experience in that field is limited. I have also taken some time to get to know various types of cellphones, and their associated embedded applications, and have recently begun branching out into smartphone technologies. I've been slowly reading up on the CCNA tests, and I've been making my way though self-study books. I've also been working through A+ certification books, mostly for fun, since I don't seem to be learning anything from them. With over 10 years in computers, this field is very natural to me, and never ceases to engage my mind with interest, intrigue, and curiosity.

Currently, I run several systems, including a few laptops for personal use, I sacrificed my desktop to use as a server, and maintain several servers, some for use by 3rd party organizations, some belonging to party organizations. I also have a number of electronics, routers, switches, as well as the usual banter for someone in the field (storage, flash drives, external drives, monitors, keyboards... even a PDA (Dell Axim x51v)).

All this aside, I hope you understand and learn something new.