However, I recently upgraded to the latest version of IE7 PRO and noticed that IE7Pro offers bookmarks syncing as an online service. I decided to try it out and it seems to work just as seamlessly as zinkmo and it doesn’t place an icon in the taskbar notification area like zinkmo does.

So for now, I’ll be uninstalling Zinkmo and trying out the IE7PRO bookmarks synchronization for a while.

So if you’re stuck in a similar predicament with an IBM, Sony or some other manufacturer that refuses to live in the year 2007, then follow these steps-

1) Download and Install AutoHotKey

2) Edit the script and use the following Code-

#.::
Send, {VKFFSC120}
return

#/::
Send, {VKFFSC130}
return

#,::
Send, {VKFFSC12E}
return

3) Press Win+. to mute, Win+/ to vol-up and Win+, to vol-down

You can of course change the script to your liking or if you need help then post a comment

System Tray Icon

What I don’t like about the client side software is that it puts an icon in the System Tray. However, I have found that you can kill this icon using the registry without impacting any functionality. This way LogMeIn is completely transparent to the end user and you have the ability to remote control their computer whenever they are experiencing an issue. In order to remove the icon from the system tray, remove the following entry from the registry-

HKLM\Software\Microsoft\Windows\CurrentVersion\Run
Delete "LogMeIn GUI"

The next time you restart your computer, the system tray GUI will not run but the core LogMeIn processes will run, giving you complete access to their system.

Vista Update (10/10/2007): It seems that the system tray icon may give you some trouble on Vista machines. The simplest workaround right now is to simply rename the executable located here: C:\Program Files\LogMeIn\x86\LogMeInSystray.exe to something else. Change the executable in the x64 folder on 64-bit machines. If you find a better workaround, please post it in the comments.

Authentication

The other part that might be tricky is the fact that you need a local user account on the machine that you are going to support. Now I haven’t completely figured why this happens, but apparently depending upon the mood of the installer, you may be prompted by the installer to create a “Computer Access Code”. What this really means is that the installer has created a user account for you on that local box called “LogMeInRemoteUser” and has hidden this user account from showing up on the XP Welcome Screen or on the User Accounts management tool in the Control Panel.

I wasn’t too comfortable using “LogMeInRemoteUser” on some machines and a personal local account on other machines. Therefore, I chose to create personal accounts on ALL machines that I support and deleted the LogMeInRemoteUser account in an effort to maintain consistency. I will not be covering the steps to create a local user account.

First thing I wanted to do was to hide my personal account from the XP Welcome Screen and from the User Accounts management tool in Control Panel. To do this, add the following DWORD to the registry-

HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\SpecialAccounts\UserList
Add DWORD for "AccountName" and set value to 0 to hide it from the UI

My Personal Account’s username is “Pranav” so I just create a DWORD for “Pranav” and set it to 0 ni the location mentioned above.

If you were prompted to create a Computer Access Code during installation, then the installer created a local account called LogMeInRemoteUser and you’ll notice that there is a DWORD entry in the same location for that account. Simply delete this DWORD and you’ll now see this account in the User Accounts management tool in Control Panel. You can then go ahead and delete this account if you wish to do so.

Conclusion

I am loving the product so far – especially since it is FREE and EASY. I have also been able to make this experience completely transparent for the people that I support and that is a great plus point for me. Please share your suggestions/experiences in the comments below.

Upon further investigation I found out from the IIS logs on the target machine that all the exported .cab files were actually being transferred over successfully and IIS was returning back a status code of 200 for each transfer. However on the last CAB file upload, IIS returned a status code of 400 every time for some reason. After that, everything just died out and the source machine could not confirm that the transfer was complete.

Rob has a more detailed account of why SP2 broke Content Deployment but in short, the fix involved making changes to the registry since service pack 2 has issues with networking and I am being told that there is no way to roll-back from SP2.

However, if you want to make changes to how the alert email looks – perhaps to make the email look more like your corporate emails – you have to modify a file called alerttemplates.xml located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\XML. Combined-Knowledge has a great white-paper on how to do so.

However, I just wasted a bit of my time figuring out why my changes were not taking effect. It turns out that after making changes to your alert template, you must use the stsadm -o updatealerttemplates to update the alert template for the site collection you want. Then you MUST re-subscribe yourself to receive the alert by clicking “Actions > Alert Me“

It appears that the site creates a separate alert template for each user. Seems inefficient if it is true – can someone confirm this?

I also remember Vista setting up personal settings upon login as is customary for new profiles when users first login. I thought this was pretty strange since my profile already existed on the computer. However even though it appeared that Vista was creating me a new profile, all my settings and files were untouched.

Anyways, I reboot the computer just like the warning/error message told me to and now things seem fine. Very Wierd.