ExcludedFileTypesFromConversion settings reverted to default
Hi,
I'm experiencing the following issue on a brand new client deployment
ExcludedFileTypesFromConversion are reverting to default. I'm aware that this is normal behaviour if I remove ANY of the default values, as per the technote below
http://www.symantec.com/business/support/index?page=content&id=HOWTO58201
"When you remove some file types using ExcludedFileTypesFromConversion, they are automatically replaced upon restarting the storage service"
However, I'm not removing any of the default values, but ADDING some, namely
.ZIP.PDF.7z.M4A.BAK.COM.RAR.
so the whole registry key looks like
.ABS.AIF.AIFC.AIFF.ASC.ASF.ASX.AU.AVI.BIN.BMP.BP.C2D.CBT.CCD.CD.CDI.CHM.CIF.CUR.DAT.DAO.
DVS.DWI.ENC.ENT.EVT.FCD.FDM.FP.GCD.GI.GIF.GTS.HLP.ICO.IMG.ISO.JFI.JFIF.JIF.JPE.JPEG.JPG.JTF
.JP2.JPX.JPF.MJ2.M1V.M2V.M3U.MDF.MDS.MID.MKV.MMM.MOD.MODV.MOO.MOOV.MOV.MP2.MP3.MP4.
MPA.MPE.MPEG.MPEGA.MPEGV.MPG.MPM.MPP.MPV.MSO.NRG.OLE.PAB.PDI.PF.PGP.PJPEG.PLS.PNG
.POI.PST.PUB.PXI.QT.QTM.QTW.RA.RAM.RAW.RM.RMI.RMJ.RMX.RP.RV.SND.SNP.SWA.SWF.TAO.TIF.TIFF.
VDO.VIV.VSF.WAV.WMA.WMV.Z01.Z02.Z03.Z04.Z05.Z06.Z07.Z08.Z09.Z10.ZIP.PDF.7z.M4A.BAK.COM.RAR.
Storage Services is restarted after applying the values, however, and for some reason, it reverts back to default
.ABS.AIF.AIFC.AIFF.ASC.ASF.ASX.AU.AVI.BIN.BMP.BP.C2D.CBT.CCD.CD.CDI.CHM.CIF.CUR.DAT.DAO.
DVS.DWI.ENC.ENT.EVT.FCD.FDM.FP.GCD.GI.GIF.GTS.HLP.ICO.IMG.ISO.JFI.JFIF.JIF.JPE.JPEG.JPG.JTF
.JP2.JPX.JPF.MJ2.M1V.M2V.M3U.MDF.MDS.MID.MKV.MMM.MOD.MODV.MOO.MOOV.MOV.MP2.MP3.MP4.
MPA.MPE.MPEG.MPEGA.MPEGV.MPG.MPM.MPP.MPV.MSO.NRG.OLE.PAB.PDI.PF.PGP.PJPEG.PLS.PNG
.POI.PST.PUB.PXI.QT.QTM.QTW.RA.RAM.RAW.RM.RMI.RMJ.RMX.RP.RV.SND.SNP.SWA.SWF.TAO.TIF.TIFF.
VDO.VIV.VSF.WAV.WMA.WMV.Z01.Z02.Z03.Z04.Z05.Z06.Z07.Z08.Z09.Z10.
No services are being restarted that might cause the return to default settings. Also, we have been unable to pinpoint when the value is being changed back. This is the ONLY registry setting being affected.
Any help would be greatly appreciated.
Hi all,
I am said backline engineer and you got to the same ballpark so good work there .
This is actually resident in any version of EV but just happens to be hit earlier in EV 10.0.4. due to additional extensions being added to the list in that version. I have just published the technical article which outlines the issue fuller and the workaround I gave Andres along with the fact that we will be addressing this in a future version of the product.
http://www.symantec.com/docs/TECH214026
Regards.....Paul.