Video Screencast Help

SUM: how do I exclude Outlook .OST file?

Created: 11 Feb 2008 • Updated: 20 Sep 2010 | 7 comments
EC's picture
I'm using the 2.0.2 version of SUM (Symantec User Migration ver. 11.0.2.1573).  It appears to work pretty much the same as the prev. version in this regard.  I am capturing settings for Microsoft Outlook 2003. But, I don't want to capture the .ost file (the local copy of the data store).  We have our laptops set up to use a local .ost, syncing with the server.  But that file gets pretty big and we don't need to migrate it since it'll be re-created on the new computer.
 
I'm using a customized, manually edited template file (SCMMigrationOptions.xml), where I've put in two lines to exlude the .ost:
c:\*.ost
$Profile$\Local Settings\Application Data\Microsoft\Outlook\outlook.ost
 
I added the second line because the first didn't work, but outlook.ost is still being captured.  That's about 40mb that I don't need.
 
It looks like the application capture settings take precedence over the file exclude settings, just like the file exclude settings take precedence over the file include settings.
 
Is there any way for me to exclude the outlook.ost file?
 
Ernie Camacho
Discussion Filed Under:

Comments 7 CommentsJump to latest comment

xan_todd's picture

> Is there any way for me to exclude the outlook.ost file?

Not at this time. Although there are circumstances where it is desirable to include the ost, we are aware this is a concern. This has been scheduled for further investigation. I'll remind the people working in that area. This did not make it to the 2.0.2 release.

In the meantime I've provided a workaround which I hope is useful to you.

EC's picture
Ah, batch files!  It's been a while.
Xan, I found a couple of problems with your sample script:
1.  The file deletion doesn't work 'cause quotes are needed around the entire path.
2.  "All Users" becomes "All" in the deletion loop.  (two vars instead of just one)
I was able to fix the first, but not the second.  I'd need more time to remind myself how the For Do loop works.
 
Also, since I'm running the wizard stand-alone, I want to put this in a batch file that ends up by running the wizard.  To that end, I split your script into two batch files.  I'l list them here:
 
capturewizard.bat:
@echo off
:--capturewizard.bat  runs the SUM wizard after doing some prep work on the capture computer.
:
echo.
echo Make sure that you have exited all Microsoft Office applications,
echo as well as other applications whose settings you want migrated.
echo.
pause
:
Set UserRoot=C:\Documents and Settings
:
:--loop to delete any outlook.ost files found in user profiles under "documents and settings".
FOR /F %%p IN ('dir /b "%UserRoot%"') DO call delost.bat %%p
:
echo end of file deletion loop.  ready to run wizard.
pause
:--Run the wizard
sumwizard.exe
:--end of batch file--
 
delost.bat:
@echo off
if "%1"=="" exit
Set UserPath=%1
if %UserPath%==All set UserPath=All Users
Echo Path = %UserRoot%\%UserPath%
Del "%UserRoot%\%UserPath%\Local Settings\Application Data\Microsoft\Outlook\Outlook.ost"
:--end of batch file--
 
This assumes that only "all users" will have a space in the name.  I might also have capturewizard.bat run a reg file to make sure all unresolve shortcuts are restored.  BTW, from my reading of the readme with GSS 2.0.2, I take it that restoring unresolved shortcuts is the default, not needing a registry entry.  Is that correct?
 
Ernie



Message Edited by EC on 02-13-2008 04:23 PM

Message Edited by EC on 02-13-2008 04:27 PM

xan_todd's picture

> BTW, from my reading of the readme with GSS 2.0.2, I take it that restoring unresolved shortcuts is the default, not needing a registry entry.  Is that correct?

That is correct. Restoration of all shortcuts is now the default behaviour.

> I found a couple of problems with your sample script:

O.k. That's possible. The sample script certainly worked with the system I developed and tested it on, but yeah, there are probably lots of cases I did not cover.


Nimi Rose's picture
Hi Ernie,
 
I have a script which resets the path in registry  to ost files for all the outlook profiles. Run this before you do an user migration capture to exclude the ost from capturing.
 
 
Code:
const HKEY_CURRENT_USER = &H80000001strComputer = "." Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_strComputer & "\root\default:StdRegProv") strBinaryValueName = "001f6610"strGuidkey = "13dbb0c8aa05101a9bb000aa002fc45a"arrValues = Array(0,0,0,0,0,0,0,0)strKeyPath = "Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles"oReg.EnumKey HKEY_CURRENT_USER, strKeyPath, arrSubKeys For Each subkey In arrSubKeys strGuidKeyPath = strKeyPath + "\"+subkey oReg.EnumKey HKEY_CURRENT_USER, strGuidKeyPath, arrGuidSubKeys For Each guidsubkey In arrGuidSubKeys  If guidsubkey = strGuidkey Then   strFullKeyName=strGuidKeyPath+ "\" + guidsubkey   oReg.DeleteValue HKEY_CURRENT_USER,strFullKeyName,strBinaryValueName   oReg.SetBinaryValue HKEY_CURRENT_USER,strFullKeyName,strBinaryValueName,arrValues  End If NextNext


 

PS: Please take a backup copy of your registry before you try this. I have used this internally only & this seems to work.Mostly used on xp systems with outlook 2003.
 
Cheers,
Nimi
EC's picture
Xan, Nimi, thanks for the quick replies!
 
Ernie
xan_todd's picture
Hi Ernie,
 
Unfortunately, we were not able to complete work to include the ability, to exclude the ost file, in the GSS 2.5 release. We remain aware the inclusion of the ost is inconvenient (and sometimes inappropriate) in a number of ways, and look forward to addressing it in future.
 
In the meantime, I hope Nimi's script is continuing to work well for you.
 
Thanks,
Xan
 
 
 
Casper73's picture

Is the inability to exclude OST files still the case?