Bill, I just found your message while catching up on email.
That folder holds Windows' "side-by-side" executables. Those are used by Windows for downward compatibility with older applications. So excluding them won't affect *Windows*, but whatever old application you're running that is using them will probably fail to start. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 03/29/2005 08:10:36 AM: > I have a client with a Windows2003 server with Exchange 2003 on it. > Lately he started seeing errors in his nightly non-Exchange > backups relating to a file in the C:\Windows\WinSxS folder. I've > search the archives and came up dry. No hits on IBM either. I > Google search brought up some information on package assemblies. > > > > Would it be safe to EXCLUDE.DIR the C:\WINDOWS\WINSXS directory? The > error(s) the client is getting are: > > > > 03/28/2005 03:32:13 ANS1228E Sending of object > '\\hbgexchits1\c$\WINDOWS\WinSxS\Policies\x86_policy.5.2.Microsoft. > Windows.SystemCompatible_6595b64144ccf1df_x-ww_92C6FB91\5.2.0.0.p > olicy' failed > > 03/28/2005 03:32:13 ANS4023E Error processing > '\\hbgexchits1\c$\WINDOWS\WinSxS\Policies\x86_policy.5.2.Microsoft. > Windows.SystemCompatible_6595b64144ccf1df_x-ww_92C6FB91\5.2.0.0.p > olicy': file input/output error > > 03/28/2005 03:32:44 ANS1512E Scheduled event 'BD70330' failed. > Return code = 12. > > > > > > And the backup schedule indicates failed. > > > > Bill Boyer > > "Growing old is mandatory, growing up is optional" - ??
