*.dannyg

I faced some tough issues trying to install Windows Live Essentials.  Even more so it feels good to blog as I haven’t written an entry in over a month.  I have a lot of good stuff coming in the next few days.  I got an error when executing the wlsetup-web.exe available from the live.com site.  You can also use the offline installer which is available here.

So the error I was getting said Bad Image, something along the lines that c:\windows\system32\wer.dll (Windows Error Reporting), had some kind of issue.  This is related to a corrupt DLL. 

I needed to ensure that the “Windows Modules Installer” service was started.  Then I opened up a command prompt as administrator and ran the following cmd.

sfc /scannow

This took a few minutes to run.  Then I was able to launch the installer.  However the installer informed me that I had to uninstaller Windows Live Mesh Beta (2009).  This was rather difficult.  I ran the uninstall several times, but the Live Essentials installer was still complaining that it was installed.  I wound up searching through the entire registry for any key called “Live Mesh” and deleted them.

After this, I was able to successfully install.  A quick reboot and here I am writing this blog entry in Windows Live Writer 2011.

Ever wanted to know where your Outlook signature files go in Windows Vista or 7?

C:\Users\<USERNAME>\AppData\Roaming\Microsoft\Signatures

Enjoy!

Requires that you install the ODBC logging module.  This is done via the server manager.  You need to the “ODBC Logging” Role Service for IIS.

There is no 64-bit runnable client for Windows (including Vista and Windows 7).  After much frustration, today I finally found a workable solution.

1.) Install Windows XP Mode which is available for free from Microsoft’s website.  http://www.microsoft.com/windows/virtual-pc/download.aspx.  This will only work for Windows 7.  You might be able to install VMWare w/Unity Mode to do the same.

2.) Once you have the whole thing set up, fire up the virtual machine and install the CheckPoint VPN-1 SecureClient.  This will publish it to the Start Menu on Windows 7.

3.) You need to turn off NAT in order to get this to work, so under Tools, select the currently connected Network Adapter.

4.) Now you can run the application seamlessly in Windows 7, the virtual machine will run hidden.

5.) If you need to remote desktop, you’ll need to hack the registry in order to all the Remote Desktop application (which by default is not enabled) to be published.

6.)

Original Post: http://social.technet.microsoft.com/Forums/en-US/w7itprovirt/thread/42e03393-749b-466b-997c-35276ab89730

1. Open regedit in the VM
2. navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtual Machine\VPCVAppExcludeList a the Name of the program in question
3. Delete the value that you don't want (say Name: mstsc.exe Type: REG_SZ Data: C:\WINDOWS\System32\mstsc.exe)
4. Restart the virtual machine

7.) Now you should be able to use the VM’s RDP application to remote to any system that you’ve connected to via the VPN

Pretty tricky, the title says it all

cscript %systemdrive%\inetpub\adminiscripts\adsutil.vbs set w3svc/AspScriptErrorSentToBrowser true      (to allow error message send to client)

On a x64 OS (I run Windows 7 RC x64)

cscript C:\Windows\winsxs\amd64_microsoft-windows-iis-legacyscripts_31bf3856ad364e35_6.1.7100.0_none_4b5800ce84aa413c\adsutil.vbs set w3svc/AspScriptErrorSentToBrowser true