Solved Outlook 2010 Command-Line Switches & options

[zapp22]

Friends I have a situation similar to or exactly same as described in this long ugly chronicle, apparently a flaw in Outlook 2010 which MS doesn't or didn't ack
Complete Outlook 2010 Lock-Up when accessing archive pst files

What I specifically am asking help with is a command-line-based way of setting Outlook 2010 on the client notebook to a state from which I can run maintenance routines. The symptomatic problem is that since end of February Outlook 2010 cannot operate because it hangs upon attempting to load/refresh the default profile, which is the oft-repeated situation described in the technet thread above.

Is there a command line switch/option that would disable the loading of the default profile and simply startup the outlook app without setting off any updates/refreshes/fetches ??? I was thinking of the /restore switch but I do not think that would provide a static state - what it would do is attempt a rollback to a stable state but the odds are that it would fail. Maybe someone knows better than i.

/safe failed. It simply apparently set app to a safe mode but immediately went into load-profile mode, thus ... wash/rinse/repeat.

thanks for any help or links or guidance.

z

 

[Golden]

Hi Zapp,

I've had a quick look, but this is beyond my limited Outlook skills.

Have you consulted this:

Command-line switches for Outlook 2010 - Outlook - Office.com

I'm wondering if the /restore is what you are after?

Regards,
Golden

 

[zapp22]

sorry to be so slow.
I hate to say this, and realize how it sounds, but the problem either self-corrected or some one of the feeble steps altered the condition - at any rate it began working right. which is irritating since I finally landed on a fix after consulting with one of my smarter buds... seems that Exchange 2007 has some transport issues that are aggravated with Outlook 2010 clients networking remotely, in this case vpn. 2010 installs on the client default to non-cached mode. this user has a big, ill-maintained [non-maintained] Outlook db. so pretty easy for snafus to happen when first loading the profile with unpredictable network linkage.

supposedly the fix [for anyone searching this] is twofold:
- rename the .ost file to off it
- reopen outlook and let it rebuild
- when on the local LAN, change to cached mode if you have the disk space for it [we do in this case]

I still plan to do the latter but the client is traveling right now.

thank you Golden