Stop the Exchange account getting set as default in Outlook

By default in a Microsoft Small Business Server environment, every time a user logs into their client PC a script is run which (among other things) changes their Outlook profile, setting their default account to the Exchange server.

This can be a major pain for users who have a POP account(s) setup as default in their Outlook profile. It means that each time they login they must go into Tools | Accounts and set their POP account to be default.

There is thankfully a fairly straightforward fix…

Open REGEDIT on the client computer (Start | Run | regedit) and navigate to HKEY Local Machine\Software\Microsoft\SmallBusinessServer\ClientSetup.
Create a DWORD entry here named “NoTransportOrder” and give this a value of “1”.
The transport order will not be changed next time the user logs in.

In my opinion it’s way better to have your clients setup to use Exchange and have Exchange send and receive email for them. Having clients collecting POP is messy. But in the real world we don’t often get to do things by the book.

This fix draws from content found at http://sbs.seandaniel.com and http://www.slipstick.com

Comments

Anonymous said…

This worked on two of the computers we're having this problem with but on a third computer...there is no smallbusinessSever under the HKEY Local Machine\Sofware\Microsoft so I don't know where to go from here for that last machine!

Thanks!

15 June 2010 at 20:23

steve said…

Has the third computer been joined to the server's domain?

26 July 2010 at 17:19

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted. Very often the fix is to run SCANPST.EXE on the offending PST/OST file. However, every time I go to do this I forget where the two executable files are. Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more... but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box: \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in: UPDATE tbSingletonData SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

Unable to Extend Volume because the Windows Recovery Partition is in the way

I had to increase the space allocated to a customer's WSUS server VM that had run out of capacity and was keeling over. So I powered off the VM, added the extra capacity to the virtual hard disk, powered it back on, and went into Disk Management to extend the C: drive partition. However, I discovered that because the Windows Recovery Partition was in between the C: partition and the new unallocated space (similar to the image below which I've copied from Woshub.com ), I was unable to do an "Extend Volume" job. The solution was to move the recovery partition. This involves disabling it, deleting it, extending your partition as required, and then re-creating the recovery partition and enabling it. Here are the steps involved: Disable existing recovery partition: You will need to disable the existing Windows recovery partition. To do this, run this command from an admin command line/PowerShell: reagentc /disable If you get the error message "REAGENTC.EXE: Operati...

Artifact Weblog

Search This Blog