The 32-bit version of Exchange 2007 cano be used in a non-production environment only. As such, there is no need to license the product by entering a product key. Doing so will only result in the error "Invalid product key".
A side effect of this limitation is that you can also not enter a product key for a valid 64-bit server from a 32-bit installation such as the management tools on a 32-bit OS. I have a PowerShell script that configures a server, depending on the roles that are installed. However, the first thing it does for all servers is apply the product key. This fails because I am running my configuration script from a 32-bit management installation.
I consider this a bug. The only solution is to run the Set-ExchangeServer command with the -ProductKey parameter on a 64-bit installation of the management tools.
MercyMe goes to a lot of places for touring, but they don’t seem to hit Portland very often. Two of the three times I have gone to see them has been in the metro area, with the other being up in Washington for a county fair. Perhaps this is because Oregon, based on some metric, is the most unchurched state in the country. I like to think that we may have fewer regular Sunday service attendees per capita, but that we make up for it by having a much higher percentage of those who actually have a personal relationship with Jesus.
This time, Jen and I will be traveling four hours and 270 miles to the booming metropolis of Central Point, where they will be performing with Casting Crowns on July 27. The drive will be worth it since we have seats in Row 2 (!!), which will be the best seats we have ever had seeing them.
I look forward to seeing them since they are my favorite CCM band, along with Chris Tomlin. And I look forward to Bart’s new Hymned album, which he has already recorded and I assume will come out later this year. If you are a poor, lost soul who hasn’t had the opportunity to listen to MercyMe, go to their website to hear them, or visit their blog to see how even grown men can be childish at heart.
For the second time since I have owned it, the starter string on my Ryobi multi-attachment trimmer broke. Must be poor design causing too much friction and slowing wearing down the nylon until it frays and breaks.
One of the difficult parts to remove, if you haven’t done it before, is the clutch drum. To do so, you need to remove spark plug and insert a screw driver into the combustion chamber to keep the piston from moving. Then use a Torx 15 driver and insert it into the whole in the front of the drum. Turn the driver counter-clockwise while holding the engine/chassis still to remove the screw holding the drum in place.
After you remove the springs holding the clutch together, loosen the clutch with a wrench and remove it. Then you can remove the gray plastic cover that houses the starter string, pulley, and spring. When you remove the pulley retaining parts, you can lift out the pulley. You need to be careful when doing so because the spring will uncoil all over the place if you don’t reign it in while lifting the pulley out.
I slowly let the spring uncoil so I can work with the pulley. Now you can replace the broken string. The frustrating part for me at this point was keeping the spring in place while trying to attache the pulley. After several failed attempts, I figured out a better way. I was trying to mount the pulley with the string wound around it, which means that the spring has to be uncoiled a bit. But this leads to the spring not wanting to remain flat when the pulley is being mounted on the shaft. The better thing to do is to unwind the the starter string so it is fully extended. You can then wind the spring as tight as it will go around the pulley (less one or two revolutions).
Even though the spring has more potential energy at this point, there is enough friction between each revolution of the spring that it makes it less prone to want to jump off the pulley. I found it much easier to mount the pulley when the spring is wound tighter around it.
I hope this trick will help you if you need to replace the starter string on your Ryobi trimmer.
The Faria ROM I have been using for awhile started having issues recently. I was having to soft reset more often (sometimes a couple of times per day), and I couldn’t turn on WiFi anymore. Memory would start at about 21MB and slowly work its way down, though a lot of that is probably due to the applications installed.
So I figured it was time to either reflash with the Faria ROM or use another. I settled on another, discussed here at XDA Developers. This is a 6.1 ROM, which is nice because of some of the improvements, such as native threaded SMS. I also have more memory after a reset: about 24MB versus 21MB with Faria. Usage feels much snappier, too. I thought that it might simply be because OMAPClock is included, but when I checked it I was still running at 180MHz. So if it feels snappy now, I can’t wait to try it at 252MHz, which is what I normally run at.
If certain MAPI limits are reached when working with sessions, items, attachments, etc., Exchange will deny further access to that user to that object type. When this happens event ID 9646 is logged in the Application log. The description of the event contains a mailbox GUID that is causing the issue, but the GUID alone does nothing to indicate what user/mailbox is affected.
Microsoft KB 899663 instructs how to manually transpose GUID into a format that can be used in an LDAP filter so that you can search for a match. Why do all this by hand when a script can do it for you? I took an existing script I had that already does the transposition and added an AD search to return the matching dn. The dn is passed to a name translation function that converts the dn to the NT4 format (domain\username) and displays the match with username and display name.
In addition to the VBScript file, I have also included a compiled version that uses SAPIEN Script Host as the engine. This is a self-contained, runs-in-memory-only, no-DOS-box-comes-up engine from PrimalScript. Running the compiled version is nice since you don’t have to ensure that CScript is the default host and no DOS box appears while the script is running.
The zip file with both versions is available here .
I tried mapping the location of the OCS presentation, metadata, and address book shares using DFS paths, only to get an error in the Create Pool Wizard. The example in the wizard does show \\server\share, but I couldn’t imagine that it would be so archaic as to require hard-coded, specific servers in the UNC path.
The deployment guide doesn’t explicitly state that you can or cannot use DFS. It does say that the wizard validates the path by attempting to set permissions, but it doesn’t say if it is trying to set share or NTFS permissions. If it is trying to set share permissions, that isn’t going to work with DFS. To top it off, there are no log files created during this test, so you can’t tell exactly what it is trying to do.
I resorted to calling Microsoft so I could ask them, and the confirmed that you have to go old-school and use \\server\share mapping. I expressed my dismay at such an antiquated requirement and that it goes against best practices of hard-coding server names. The engineer said that the product group has had several requests from customers to enable support for DFS, so I can only hope it will come in a service pack.
My favorite CCM band released a new album a couple weeks ago. I preordered it from MusicChristian and it arrived on the day of release. I eagerly popped it into the CD player, and like "Coming Up To Breathe", my first reaction based on Track 1 was that this isn’t the band I know and love. "Goodbye Ordinary" is heavier, for them, in electric guitar than I prefer, not to say that I dislike the song altogether. "Time Has Come" starts with a sound that, if I didn’t know to whom I was listening, I would think it is Chris Tomlin. Not until "I Know" does MercyMe’s traditional sound come through. I like "God With Us" (except the end with the strings), "Sanctified," "You Reign," and "Grace Tells Another Story." "Alright" is a feel-good track with an "Ooh ooh" ditty. I really like the false ending that segues into a tag that is repeated. They have done this on several tracks in the past, and there is just something about when they do that that I really like. Maybe it is to help burn the tag lyrics into your head or practice harmonizing with them. (If the former, it is "Count up your joy when the world comes crashing / Hold your head up and keep on dancing.") "My Heart Will Fly" continues their sound, but my favorite track is "Finally Home." Bart Millard has such a beautiful voice that you can just focus on his lyrics and singing. Aside from the electric guitar with its distortion coming through, this is a simple acoustic song, more about telling its story than the music (reminds me of "MawMaw’s Song"). I really like the one-voice melody that Bart sings, which progresses into a two-, then three-/ four-, and maybe even five-voice polyphony.
After listening to the album a number of times, I really enjoy it, and I am glad that I don’t judge it based on my first impression of the first track. This was the same with "Coming Up To Breathe," where repeated listening is what endeared the album to me. Hopefully for their tour they will choose to stop by Portland. Their album tours have not led them this way recently, though they have been to Puyallup for the WWC Fair and to Tualatin with Audio Adrenaline. I have seen them perform three times, so I look forward to the next time.
This video has been sitting in my temp directory since July, 2005. I figured some day I would get to it, and since I am cleaning my temp directory, that day is today. The video is a clip from an HBO comedy performance where the comedian mimes actions to Natalie Imbruglia’s "Torn." He does it with amazingly smooth transitions from each action to the next, not to mention how he choose to mime certain words.
HollowMen Video
After Microsoft bought Lookout, by far the best Outlook indexer, they incorporated its functionality into Windows Desktop Search. WDS is a horrible app, in my opinion. Microsoft chose to intentionally disallow Lookout as an add-in in Outlook 2007. I have tried other indexers that work with Outlook, but none could compare to the efficient and fast Lookout. I settled on Nelson Email Organizer (NEO), which is a standalone application. It does do some nice things, but it just isn’t the same.
A successor to Lookout has found: Lookeen. Like Lookout, it is a COM add-in just for indexing your mailbox (not a bloated app that also indexes your mailbox). It is very fast, and offers a nice feature that Lookout never did: it display results in a tabbed window, so you can view results by their item type (messages, appointments, contacts, files, etc.). Lookeen is in beta right now, but you can download it and give it a try. I haven’t tried any complex searches, but my early results are very positive.
There is a limitation in the use of automatic formatting to control how a message is displayed in a folder’s message list. I had been trying to use automatic formatting to change the color of messages in a particular folder if they contain a certain word in the body. I have a rule that moves some daily reports I receive into the folder, and rather than open each report if nothing has changed in the results of the report since it last ran, I wanted to have messages that contain a word that is in them when they have been updated to display differently. This way I can simply delete the reports with unchanged data, but still open them if I want to (which is why I am not using a rule to delete them upon arrival).
However, the automatic formatting was not being applied to messages that contained the keyword. I tried several different ways within the conditions editor of applying the formatting, all with the same results. I decided to open a case with Microsoft since we have loads of Premier incidents available to use. I had to work through several engineers until I finally got to the Outlook development team who had to look at the source code to determine why it wasn’t working.
That is when they discovered the culprit: a limitation that is by design. When using automatic formatting, only the first 256 characters of the message body will be searched. This is for performance reasons. I couldn’t understand why this would be the case since rules will search all of a message body. Then I realized why and it does make sense: Automatic formatting is part of the view for a folder. Views are calculated and applied each time you switch to that folder, so displaying the font face/color/size and bold/italics of each message in the folder list is dynamically applied each time you switch to the folder. The default automatic formatting rules for a folder include unread, overdue, and expired messages, plus group headers, etc. There is definitely a performance risk if Outlook had to search the entire message body of every message in a folder to determine how it should be displayed. To mitigate this, message body searches are limited to 256 characters when part of automatic formatting.
Rules aren’t subject to this limitation because they are one-time processes. Rules are applied only when a message arrives or is sent (or when you manually run one). So the workaround for my issue is to use a rule to search the body for a keyword, assign a category to it if there is a match, and then move it to the folder. I then use automatic formatting to change how a message is displayed if the category is the one I assigned. I have to create a rule for each keyword I am looking for (since I am also looking for reports that have errors), which isn’t as efficient as defining multiple automatic formatting rules, but it is an acceptable workaround since the results are the same.
Comments (0) 
Themocracy