Outlook blocks EXE and MDB file attachments (and others)

1. Close Outlook
   Open the Registry Editor
   
2. Office XP/2002 : HKEY_CURRENT_USER\ Software\ Microsoft\ Office\ 10.0\ Outlook\ Security
   Office 2003: HKEY_CURRENT_USER\ Software\ Microsoft\ Office\ 11.0\ Outlook\ Security
   
3. Create a new string value by selecting New and then String Value from the Edit menu.
   
4. Name the new value Level1Remove.
   
5. Double-click the new Level1Remove to edit it, and enter the filename extensions you'd like to stop Outlook from blocking. Extensions should be typed in lower case, without the dots (.), and separated by semicolons (;). For example, type
   exe;mdb;vbs to allow .exe, .mdb, and .vbs attachments, respectfully.
   
6. Click Ok and then close the Registry Editor when you're done.
   
7. The next time you restart Outlook, you'll now be able to open previously-blocked attachments.

10 Minute Mail

Need a temporary email to sign-up, validate, subscribe, enroll, register etc? Try 10 Minute Mail

• You click on an link and get a temporary e-mail address.
• Any e-mails sent to that address will show up automatically on the web page. You can read them, click on links, and even reply to them.
• The e-mail address will expire after 10 minutes.a temporary e-mail address.
• Any e-mails sent to that address will show up automatically on the web page.
• You can read them, click on links, and even reply to them.
• The e-mail address will expire after 10 minutes.

Enable the Built-in Administrator Account in Vista

The built-in administrator account is disabled by default in Vista. To enable it, open an command shell and type:

net user administrator/active:yes

See also http://technet2.microsoft.com/WindowsVista/en/library/9fe3a3eb-01ec-47d4-abac-227bd6d8490f1033.mspx?mfr=true

Launch Elevated Command Prompt in Vista

To add the Open Command Window Here (Administrator) option to the context menu for file system folders, use the following REG file:

[HKEY_CLASSES_ROOT\Directory\shell\runas]@="Open Command Window Here (Administrator)"

[HKEY_CLASSES_ROOT\Directory\shell\runas\command]@="cmd.exe /s /k pushd \"%V\""

To add the entry to Computer (My Computer) context menu, use the following REG file:

[HKEY_CLASSES_ROOT\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\runas]@="Open Command Prompt (Administrator)"

[HKEY_CLASSES_ROOT\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\runas\command]@="cmd.exe"


Copy the above contents to Notepad, and save the file with .REG extension. Then right-click the REG file and choose Merge.

Remove all temporary internet files

With admin rights in C:\Documents and settings:
del *].* /s

Sandboxie, nýtt tól í baráttunni við Internet óværu

Kerfisstjórinn rakst á þetta skemmtilega tól um daginn. Það heitir Sandboxie og gerir mönnum kleyft að keyra forrit af vefnum án þess að þau séu að skrifa gögn á harða diskinn. Í staðinn er öllum skriftilraunum beint í Sandboxie. Með þessu er hægt að koma í veg fyrir að vírusar, auglýsinga- og njósnaforrit komi sér fyrir á tölvunni.

Algengir MMC-ar úr Start - Run

Computer Management - compmgmt.msc
Device Manager - devmgmt.msc
Disk Management - diskmgmt.msc
Event Viewer - eventvwr.msc
Group Policy - gpedit.msc
Local Security Settings - secpol.msc
Local Users and Groups - lusrmgr.msc
Services - services.msc

----------------- 0 -----------------

Certificates - certmgr.msc
Component Services - comexp.msc
Disk Defragmenter - dfrg.msc
Indexing Service- ciadv.msc
Removable Storage - ntmsmgr.msc
Removable Storage Operator Requests - ntmsoprq.msc
Performance - perfmon.msc
Resultant Set of Policy - rsop.msc
Shared Folders - fsmgmt.msc
Windows Management Infrastructure (WMI) - wmimgmt.msc

Vista and Sysprep

Vesen með Vista og Sysprep? Hér er lausnin:

"The few systems administrators who are already deploying Windows Vista are brave; they're the ones taking the arrows, running into problems the rest of us haven't seen yet.
One such intermittent problem occurs when an admin uses the Sysprep utility to prepare a Windows Vista system (typically for cloning). The error message that comes up simply reads: A fatal error occurred while trying to sysprep the machine.

Open up the Setupact.log file generated by Sysprep, and you'll find a bit more information: 0x80070020 / ERROR_SHARING_VIOLATION. This message is generated by the Microsoft Distributed Transaction Coordinator (MSDTC), a Windows component that shows up in nearly every Vista installation out there.

Microsoft's take on this is that the problem is more the fault of Windows Vista than Sysprep. Why? Here's my guess: When the MSDTC tries to reset its log, it discovers it can't do this because Sysprep has locked the log for exclusive access. Hence the error, and Sysprep itself aborts as well. Essentially, the two programs interfere with each other's operation. The problem appears to affect all SKUs of Vista.

There is a solution, but today it's only available as a free hotfix from Microsoft's Product Support Services. Call them and refer to Knowledge Base article 930193. The solution involves patching two files: Msdtcprx.dll (to version 2001.12.6930.20502) and Xolehlp.dll (2001.12.6930.20502). Both 32-bit and 64-bit editions of the fix are available as needed.

Note: A vaguely similar error sometimes occurs when you run the sysprep -reseal command in Windows Vista, which logs the following error in Setuperr.log: Failed to delete reg value SystemIndexNormalization under reg key. A hotfix is available, but, again, only from Product Support Services. Refer to Knowledge Base article 929913.

Note: If you're not experiencing these problems with Sysprep and Vista, the hotfix isn't required. For now, this fix is only for people who are actually experiencing the issue. A fully regression-tested fix for everyone to use will show up in Service Pack 1 for Vista, which, by all accounts, will be out in the second half of 2007."

About the author: Serdar Yegulalp is editor of the Windows Insight, (formerly the Windows Power Users Newsletter), a blog site devoted to hints, tips, tricks and news for users and administrators of Windows NT, Windows 2000, Windows XP, Windows Server 2003 and Vista. He has more than 12 years of Windows experience under his belt, and contributes regularly to SearchWinComputing.com and SearchSQLServer.com

RyanVM's Windows XP Post-SP2 Update Pack

RyanVM's Windows XP Post-SP2 Update Pack er pakki til að setja upp XP SP2 með öllum hotfixum, sbr:

This pack is designed to bring a Windows XP CD with SP2 integrated fully up to date with all of the latest hotfixes released by Microsoft since SP2's release. It accomplishes this task via direct integration, where files on the CD are directly overwritten by the updated files. This method has numerous advantages over other integration techniques:

1. Since the files are being directly overwritten on the CD, there is no period of vulnerability between when the files are copied to the hard drive and the hotfixes are run. This guarantees maximum stability and security.
2. All necessary registry entries needed by Windows Update, QFECheck, and Microsoft Baseline Security Analyzer are imported during Windows setup, meaning that the integration is transparent to Windows.
3. Security Catalogs necessary for Windows File Protection to recognize the updated files as digitally signed are installed, once again ensuring maximum transparency to Windows.
4. Since the updated files are being directly overwritten on the CD, this pack has the minimum possible amount of overhead associated with integrating hotfixes in comparison to other methods - both in space used on the CD and in Windows installation time.
5. This pack works regardless of whether or not the Windows installation is unattended.

How to Activate the Telnet client in Windows Vista

In Windows Vista, the Telnet client isn’t as readily available as in previous versions. Like a lot of old functionality, they’ve hidden the fact that it’s there. To re-enable your old friend, navigate to Control Panel, then Programs and Features, and then click Turn Windows features on or off. Look for the Telnet Client and re-enable it.