Re: Clients not updated with new MSSecure data...
From: Adam Welker [MSFT] (adamwel_at_online.microsoft.com)
Date: 07/20/04
- Next message: Chris: "Re: Clients not updated with new MSSecure data..."
- Previous message: Adam Welker [MSFT]: "Re: Clients not updated with new MSSecure data..."
- In reply to: Chris: "Re: Clients not updated with new MSSecure data..."
- Next in thread: Chris: "Re: Clients not updated with new MSSecure data..."
- Reply: Chris: "Re: Clients not updated with new MSSecure data..."
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 20 Jul 2004 12:55:19 -0700
You'll note on 7/13 a file was downloaded which is different than the one in
the existing package source. (The hash calculations on the downloaded file
in temp doesn't match the one in the package source.)
After this a copy operation was done on 7/13 to move the file from temp to
the package source. I don't see the package update occuring, so I'm
assuming you may have the /unattend switch on the sync program command line.
If true this would mean you either need to manually update the package or
have it update on a periodic schedule.
After that I'd say within 6 hours you should have inventory from everyone
whose online.
-- Adam Welker This posting is provided "AS IS" with no warranties, and confers no rights. "Chris" <Chris@discussions.microsoft.com> wrote in message news:CFC18884-1DB6-4771-AB0C-4B69843118DC@microsoft.com... > Here are two copies of the SecuritySyncXml.log. One from last night and one from the actualy most recent time it downloaded & updated the mssecure file. > > 07/19/2004: > > Initialized log file - SyncXML started at 7/19/2004 2:00:05 PM 1/1/1601 12:00:00 AM 3764264 (0x397028) > Sync task started with command-line = /s /unattend /site VITEAST-DBS1 /code A01 /target \\VITEAST-DBS1\D$\SMS\SecurityPatch\PkgSource /package A0100002 1/1/1601 12:00:00 AM 3764264 (0x397028) > User Account: NONE 1/1/1601 12:00:00 AM 3764264 (0x397028) > User Profile: C:\Documents and Settings\forecaster 1/1/1601 12:00:00 AM 3764264 (0x397028) > Command line specified package to update on DPs as A0100002 1/1/1601 12:00:00 AM 3764264 (0x397028) > Command line specified folder to update as \\VITEAST-DBS1\D$\SMS\SecurityPatch\PkgSource. 1/1/1601 12:00:00 AM 3764264 (0x397028) > Command line specified site code: A01. 1/1/1601 12:00:00 AM 3764264 (0x397028) > Command line specified site server: VITEAST-DBS1. 1/1/1601 12:00:00 AM 3764264 (0x397028) > Command line enable UNATTEND 1/1/1601 12:00:00 AM 3764264 (0x397028) > Specified folder is local, changing it to: D:\SMS\SECURITYPATCH\PKGSOURCE 1/1/1601 12:00:00 AM 3764264 (0x397028) > Download completed - http://go.microsoft.com/fwlink/?LinkId=23190 1/1/1601 12:00:00 AM 3764264 (0x397028) > Download completed successfully. 1/1/1601 12:00:00 AM 3764264 (0x397028) > Trying to calculate hash on C:\WINNT\TEMP\mssecure.cab. Software Updates Scan Helper 7/19/2004 2:00:10 PM 3024 (0x0BD0) > Trying to calculate hash on D:\SMS\SECURITYPATCH\PKGSOURCE\1033\mssecure.cab. Software Updates Scan Helper 7/19/2004 2:00:10 PM 3024 (0x0BD0) > C:\WINNT\TEMP\mssecure.cab and D:\SMS\SECURITYPATCH\PKGSOURCE\1033\mssecure.cab were found to be same. Software Updates Scan Helper 7/19/2004 2:00:10 PM 3024 (0x0BD0) > Distribution points will not be updated. 1/1/1601 12:00:00 AM 3024 (0x0BD0) > > > 07/13/2004: > > Initialized log file - SyncXML started at 7/13/2004 5:15:10 PM 1/1/1601 12:00:00 AM 948 (0x03B4) > Sync task started with command-line = /s /unattend /site VITEAST-DBS1 /code A01 /target \\VITEAST-DBS1\D$\SMS\SecurityPatch\PkgSource /package A0100002 1/1/1601 12:00:00 AM 3764264 (0x397028) > User Account: NONE 1/1/1601 12:00:00 AM 3764264 (0x397028) > User Profile: C:\Documents and Settings\forecaster 1/1/1601 12:00:00 AM 3764264 (0x397028) > Command line specified package to update on DPs as A0100002 1/1/1601 12:00:00 AM 3764264 (0x397028) > Command line specified folder to update as \\VITEAST-DBS1\D$\SMS\SecurityPatch\PkgSource. 1/1/1601 12:00:00 AM 3764264 (0x397028) > Command line specified site code: A01. 1/1/1601 12:00:00 AM 3764264 (0x397028) > Command line specified site server: VITEAST-DBS1. 1/1/1601 12:00:00 AM 3764264 (0x397028) > Command line enable UNATTEND 1/1/1601 12:00:00 AM 3764264 (0x397028) > Specified folder is local, changing it to: D:\SMS\SECURITYPATCH\PKGSOURCE 1/1/1601 12:00:00 AM 3764264 (0x397028) > Download completed - http://go.microsoft.com/fwlink/?LinkId=23190 1/1/1601 12:00:00 AM 3764264 (0x397028) > Download completed successfully. 1/1/1601 12:00:00 AM 3764264 (0x397028) > Trying to calculate hash on C:\WINNT\TEMP\mssecure.cab. Software Updates Scan Helper 7/13/2004 5:15:18 PM 3636 (0x0E34) > Trying to calculate hash on D:\SMS\SECURITYPATCH\PKGSOURCE\1033\mssecure.cab. Software Updates Scan Helper 7/13/2004 5:15:18 PM 3636 (0x0E34) > C:\WINNT\TEMP\mssecure.cab and D:\SMS\SECURITYPATCH\PKGSOURCE\1033\mssecure.cab were found to be different. Software Updates Scan Helper 7/13/2004 5:15:18 PM 3636 (0x0E34) > Copied C:\WINNT\TEMP\mssecure.cab to D:\SMS\SECURITYPATCH\PKGSOURCE\1033\mssecure.cab. Software Updates Scan Helper 7/13/2004 5:15:18 PM 3636 (0x0E34) > > > "Adam Welker [MSFT]" wrote: > > > Please check and post as appropriate your securitysyncxml.log. > > > > -- > > Adam Welker > > This posting is provided "AS IS" with no warranties, and confers no rights. > > > > > >
- Next message: Chris: "Re: Clients not updated with new MSSecure data..."
- Previous message: Adam Welker [MSFT]: "Re: Clients not updated with new MSSecure data..."
- In reply to: Chris: "Re: Clients not updated with new MSSecure data..."
- Next in thread: Chris: "Re: Clients not updated with new MSSecure data..."
- Reply: Chris: "Re: Clients not updated with new MSSecure data..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading