Category Archives: Registry Hacks

Where is the Temporary Outlook folder?

An unusual issue developed yesterday. A user mentioned that they could not open a PDF file from Outlook. Other PDF files would open, but just not ones that were called ESale.PDF. The message in Outlook was “Can’t create file: ESale.PDF. Right click on the folder you want to create the file in, and then click Properties on the shortcut menu to check your permissions for the folder.”
 
A quick check indicated that since the user opened files by this name quite often, it was likely that the Outlook Temp folder had reached the maximum number of stored files with this name. Apparently, Outlook creates temp files in this folder called ESale.PDF, then ESale(2).PDF, ESale(3).PDF and so on until Esale(99).PDF. After that, the error occurs.
 
To find out where the Outlook Temp folder resides, one can look in the following registry entries, depending on the version of Outlook.
 
Outlook 97 – HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\Outlook\Security
Outlook 98 – HKEY_CURRENT_USER\Software\Microsoft\Office\8.5\Outlook\Security
Outlook 2000 – HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Outlook\Security
Outlook 2002/XP – HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security
Outlook 2003 – HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security
Outlook 2007 – HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Security
 
Copy and paste that location into Explorer, and you will then be able to view the contents of the folder and clear out un-needed files. This is also particularly useful for people who may have opened and attachment, made changes to the attachment, and inadvertently clicked Save and Exit. The file is then saved in this temporary folder, and hidden from the user.

How to increase the size of the Exchange 2003 mailbox store

This has cropped up a few times at different sites over the past few weeks, so I thought I would post it here for quick reference.
Exchange mailbox stores were shutting down on a daily basis. This was affecting iPhone, which apparently “wipe out” the data (i think the data becomes unavailable), when there is no connection to the Exchange server. To workaround this, switch of the “push” action for email collection on the iPhone. This will also significantly increase the battery life if you nromally receive a lot of emails.
 
To increase the size of the Exchange mailbox store from it’s default of 18GB, do the following.
 
For a mailbox store, go to the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Private-Mailbox Store GUID

For a public folder store, go to the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Public-Public Store GUID

Create a New DWORD Value, “Database Size Limit in Gb” and set it between 1 to 75 as required. The default is 18 (of course).

Restart the MS Exchange Information Store service.

Remove User Profile in Vista

**Note this also works for Windows 7**
If you need to delete a user profile in Vista to clear some issues, there is an added step.
1. Delete or rename the user profile in C:\Users. If you were logged in to this user, you may need to reboot your PC and log in using another administrator level account.
2. In the registry, go to HKLM\Software\Microsoft\Windows NT\Current Version\Pofiles List. Expand the key and search for the username. Delete the GUID key, which will normally contain a .BAK at the end.
If the second step is not done, you will end up logging on to the system with a temporary profile.

Vista networking issues with SBS2003

I have come across an issue which has come up regularly when using Vista workstations in a SBS2003 network. A network share cannot be accessed properly from the Vista PC. Files can be created, copied to, or deleted off the network share. However, when an attempt is made to rename the file, or edit and save the file, an error pops up similar to the following – “The file cannot be found” or “The network resource is no longer available”.
 
One way to fix this is to reset the Offline Folders database, which may be corrupted. To do this:
 
1. Open Regedit
2. Go to HKLM\SYSTEM\CurrentControlSet\Services\CSC\Parameters
3. Edit or add the DWORD value called FormatDatabase to 1
4. Restart the computer
 
Alternatively, disable Offline Files in the Control Panel and restart the PC.
 

Vista is unable to Rename/Move Files/Folders on a network drive

Upon installing a new PC on a SBS2008 domain, the following symptom showed up when trying to save, rename or move files and folders on the network drive.
 
“The “\\servername\sharedfolder” does not exist. The file may have been moved or deleted. Do you want to create it?”
 
I was able to create a new folder or file, but could not rename it. I could also delete the folder or file.
 
The problem appears to happen with new PCs, possibly caused by the way the vendor packaged the OS.
 
A resolution was to turn off Offline Files Synchronization from the control panel.
I also needed to create a DWORD value named FormatDatabase with a value of 1 in HKLM/system/currentcontrolset/services/csc/parameters.
Reboot, and problem solved.

More RWW woes with XP SP2 and SP3

Following on from my blog regarding RWW on SBS2008 (http://blog.powerbiz.net.au/fixes/remote-web-workplace-rww-is-not-working-after-xp-sp3-is-installed/) and the need to have XP SP3 or RDC 6.1 for XP SP2.
After applying the following, I had a client who still could not connect to RWW. An error message appeared.
 
“The wizard cannot configure Remote Desktop Connection settings. Make sure that the client version of Remote Desktop Protocol (RDP) 6.0 or later is installed on this computer”
 
But it was installed!!??? Check out http://www.fixmyrww.com/
 
Go to the Internet Explorer Add-Ons, and enable the Microsoft Terminal Services Client Control ActiveX control or the Microsoft RDP client Control ActiveX control.
If this is already enabled, or after this is enabled, you will also need to re-register the ActiveX control.
 
Run the following commandregsvr32 %systemroot%\system32\mstscax.dll
 

Microsoft Office Outlook cannot provide form scripting support

I installed Trend Micro Worry Free Business Security Advanced on a server and implemented the antispam features. Trend drops detected spam messages into a folder called Spam Folder in each user’s Outlook mailbox on the Exchange server.
 
When accessing this folder on a Terminal Server, the following error message appears.
 
“Microsoft Office Outlook cannot provide form scripting support. This feature is not available. For more information, contact your support administrator.”
 
The fix to this problem is detailed in KB302003 – http://support.microsoft.com/kb/302003
 
1. Copy Outlvbs.dll from a normal client PC (not a Terminal Server). The file needs to be placed in the Program Files\Microsoft Office\Office12 folder. For Ooulook 2003, put this file in the Office11 folder.
 
2. Enable VB Script support by running the following command on the Terminal Server – msiexec /i {Product GUID} ADDLOCAL=OutlookVBScript /qb
The Product GUID can be found in the HKLM\SOFTWARE\Microsoft\Office\12.0\Common\InstalledPackages. Look for the Microsoft Office package key that is installed.
 

How to Make Terminal Servers in Application Sharing Mode Appear in Remote Web Workplace

Here is a bit of a gem. Now we can turn off port 3389 and get users to use RWW from port 443 in SBS2008 instead.
 
Thanks to the Technet guys!
 

Administrators will see all servers and workstations that are shown in the SBS Console’s Computer tab. However, standard users will only see workstations that they have been granted access to. This means that Terminal Servers in the domain will NOT be shown to standard users. To allow non-administrators to see Terminal Servers present in the network, follow these steps:

  1. Log on to SBS 2008 as an Administrator
  2. Open Registry Editor by typing “regedit” in the Start menu. In the Registry Editor, navigate to “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer
  3. Create a sub-key “RemoteUserPortal” under the key “SmallBusinessServer“, if it does not already exist
  4. Under the “RemoteUserPortal” key, create a new a Multi-String Value with the name”TsServerNames” (without the quotes; note the capitalization)
  5. Edit the “TsServerNames” value, add your TS servers name into the value data (one server per line), and then click OK to save them
  6. After completing the steps above, the servers you added into the registry will show to all RWW users in their computer selection list.

clip_image002

clip_image004

Note: Once this change is completed, ALL users will be able to view the TS Server from RWW.

Missing SYSVOL and NETLOGON during migration

I have had a crazy week so far. One of the issues that has bugged me this week was missing SYSVOL and NETLOGON shares and missing domain data after a new domain controller was added to the domain during migrations.

I first ran into this problem 3 years ago, when I was performing one of my first Swing migrations. I had shut down a server too soon, and as a result, the replica sets were incorrecty synchronized. In that case, I didn’t know what hit me. After I swung the DC back to the target new server, the entire AD crashed. There was no recovery, and I had to restore the server to it’s original state. When I reworked the Swing Migration weeks later, this error did not occur. I made a note on my Swing Migration worksheet, and did not come across this issue again . . . until Monday.

In the first case, I was trying to salvage the AD for a SBS2000 server which had lost the RAID and was barely functional. Just enough to get started. I quickly fixed up a Win2003 server and joined it to domain with the purpose of giving some backup to the AD in preparation for a Swing Migration.

Everything went according to plan, and the AD appeared to have transfered across. I did one last check according to my notes, which I have compiled over the past 4 years, and hit a snag which I had not seen for about 3 years. The SYSVOL and NETLOGON shares were not present on the new DC. Looking further, C:\WINDOWS\SYSVOL\sysvol\domain.name was empty. It should have 2 very important folders – Policies and Scripts. Without this, the AD would crash if the main DC were no longer operational.

In this instance, time was short, and I had to let this one go. We had to rebuild a new domain and reset all the workstations and data.

Today, as I was preparing a new SBS2008 server for migration, I found the same situation. The SBS2008 installation had completed and this new server was fully operational. Being paranoid, I checked, and there was the problem again!

After some searching, I finally found an old Microsoft Knowledge Base article KB290762 (http://support.microsoft.com/kb/290762/) – Using the BurFlags registry key to reinitialize File Replication Service replica sets.

I ran the Authoritative FRS restore procedure using the D4 flag on the old server.

  1. Click Start, and then click Run.
  2. In the Open box, type cmd and then press ENTER.
  3. In the Command box, type net stop ntfrs.
  4. Click Start, and then click Run.
  5. In the Open box, type regedit and then press ENTER.
  6. Locate the following subkey in the registry:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
  7. In the right pane, double click BurFlags.
  8. In the Edit DWORD Value dialog box, type D4 and then click OK.
  9. Quit Registry Editor, and then switch to the Command box.
  10. In the Command box, type net start ntfrs.
  11. Quit the Command box.

Then I ran the nonauthoritative restore process using the D2 flag on the SBS2008 server.

  1. Click Start, and then click Run.
  2. In the Open box, type cmd and then press ENTER.
  3. In the Command box, type net stop ntfrs.
  4. Click Start, and then click Run.
  5. In the Open box, type regedit and then press ENTER.
  6. Locate the following subkey in the registry:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
  7. In the right pane, double-click BurFlags.
  8. In the Edit DWORD Value dialog box, type D2 and then click OK.
  9. Quit Registry Editor, and then switch to the Command box.
  10. In the Command box, type net start ntfrs.
  11. Quit the Command box.

Bingo, the folders were recreated, and the shares appeared! An answer to a 3 year old question.

Server on, no connections

In the past few months, I have had random situations where a server would restart, and following the restart, no one could connect in or the server would not connect out. Normally, a second reboot would fix the problem.

I have discovered that this is caused by the application of the MS08-037 patch. If the randomly assigned ports conflicted with the IPSEC service, this service would fail, causing the server to start in block mode where all network connectivity to the server is blocked. The proactive solution as documented by Microsoft in http://blogs.technet.com/sbs/archive/2008/07/17/some-services-may-fail-to-start-or-may-not-work-properly-after-installing-ms08-037-951746-and-951748.aspx is to modify a registry entry as follows.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ReservedPorts
Add the following port ranges and reboot.
3343-3343
1433-1434
1745-1745
1080-1080
1720-1720
1645-1646
1701-1701
1812-1813
2883-2883
4500-4500

There is more information on this problem along with other scenarios which I have not yet encountered.