Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, April 10, 2015 5:49 PM
Hello SCCM community,
I'm trying this route to see if I am able to find a solution to a problem I am having. Our Windows 7 x64 "golden" image was starting to take quite some time to get deployed on workstations because of the quantity of Software Updates getting pushed out at the end of the process.
We decided to kick in our bi-yearly process of rebuilding the Build and Capture task sequence to include all the latest software updates up to the month of March. The B&C process itself worked flawlessly.
Since I wanted to test the whole thing before rolling it out into production, I copied my production "Deploy Windows 7" task sequence on a Test TS that I deployed on a Test Collection. I edited my TS and changed the "Apply Operating System" step to have the update WIM file I just created.
Here's the problem we encounter when attempting to deploy this TS: not every time, but, quite frequently, the Task Sequence will seem to go idle on the first Package with a Program that gets invoked by the Task Sequence. In my case, since I'm testing using a Virtual Machine, this first Package is usually the VMWare Tools. The same TS deployed on a physical machine, such as an HP laptop will do the same, except on the Fingerprint Reader which is the first package to get called.
I have seen a few posts online that seem to resemble my issue, such as:
http://sccm-etc.blogspot.ca/2013/12/task-sequence-stops-randomly.html
https://social.technet.microsoft.com/Forums/en-US/54a01410-ebe5-4bba-8f62-01415a6dac7a/tasksequence-stops-randomly?forum=configmanagerosd#70507abc-714c-4e3a-8558-f8000f226113They all seem to exhibit similar symptoms to mine, but none of the solutions proposed work for me.
- Single Primary Site with DP Role installed, 2012 R2 CU4
- Task Sequence Client Installation also installs the CU4 client
- Had the problem before I upgraded to CU4 (Previously was on CU3)
- I tried the VBS proposed in the 3 link I posted
- The problem is not because the application is waiting for use input because all these applications work with our "older" golden image
- I tried adding a 5 minutes sleep + Reboot right after the Setup Windows and Configuration Manager, also tried a Reboot + Sleep, both cases, no change
- I tried replacing the "driver specific model" step in WinPE by an AutoApply Drivers, same thing.
- I tried recapturing my golden image, waiting 24 hours, adding it to SCCM, waiting another 24 hours, distributing it to my DP, still, no change
All I see in my SMSTS.log is an infinite loop of "Waiting for job status notification...".
I currently have a case opened with Microsoft, but, so far, nothing concrete. I'm hoping someone has seen this and has something good for me!
All replies (19)
Thursday, April 30, 2015 11:36 AM ✅Answered
Hi Daniel,
I'm still working on it. I had a partial workaround found Microsoft: remove the application of the CU in my Setup Windows and ConfigMgr step. I honestly don't like that solution as it makes no sense to me.
I was just about ready to accept it. But since we were now in the month of april, I han't rolled out my image into production yet, so I told myself, might as well recapture the image with the April 2015 patches since we now know how to get it to work.
Bad idea. Same issue once again.
What's even worse is that I don't even seem to be able to run a full Build and Capture from beginning to end without the process failing during software updates.
- I tried adding the installation of .net framework 4.5.2 via Application instead of Software updates. Doesn't complete.
- I tried using Scheduled Updates on the DEFAULT Windows 7 wim file in order to alleviate the quantity of patches to install. Doesn't change anything, it still install 198 updates in the first pass of patches. Why?!?!
- I tried adding multiple passes of Install Software Updates + Scans + Waits. Doesn't change anything.
I'm seriously out of ideas.
I attached the SMSTS.log, if ever it can enlighten someone...
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_f3201fb1-80ac-4e3e-917c-e945c37d340e failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_b3e027f0-b4a9-41d9-97c9-2642e10fda9d failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_d6408a2e-b6d4-4212-978e-6f5894036e56 failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_f3201fb1-80ac-4e3e-917c-e945c37d340e failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_b3e027f0-b4a9-41d9-97c9-2642e10fda9d failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_d6408a2e-b6d4-4212-978e-6f5894036e56 failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_f3201fb1-80ac-4e3e-917c-e945c37d340e failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_b3e027f0-b4a9-41d9-97c9-2642e10fda9d failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_d6408a2e-b6d4-4212-978e-6f5894036e56 failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_f3201fb1-80ac-4e3e-917c-e945c37d340e failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_b3e027f0-b4a9-41d9-97c9-2642e10fda9d failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_d6408a2e-b6d4-4212-978e-6f5894036e56 failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_f3201fb1-80ac-4e3e-917c-e945c37d340e failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_b3e027f0-b4a9-41d9-97c9-2642e10fda9d failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_d6408a2e-b6d4-4212-978e-6f5894036e56 failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:48 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_f3201fb1-80ac-4e3e-917c-e945c37d340e failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:49 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_b3e027f0-b4a9-41d9-97c9-2642e10fda9d failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:49 4900 (0x1324)
NotifyComplete received InstallSWUpdates 2015-04-29 17:23:49 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_d6408a2e-b6d4-4212-978e-6f5894036e56 failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:49 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_f3201fb1-80ac-4e3e-917c-e945c37d340e failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:49 4900 (0x1324)
Update with CIID Site_251DFA33-D04D-45D0-9F59-24423C97FE7F/SUM_b3e027f0-b4a9-41d9-97c9-2642e10fda9d failed with hr = 0x80240017 InstallSWUpdates 2015-04-29 17:23:49 4900 (0x1324)
Received job completion notification from Updates Deployment Agent InstallSWUpdate 2015-04-29 17:23:49 616 (0x0268)
Reboot Required InstallSWUpdate 2015-04-29 17:23:49 616 (0x0268)
Setting TSEnv variable SMSTSRebootRequested=HD InstallSWUpdate 2015-04-29 17:23:49 616 (0x0268)
Setting TSEnv variable SMSTSRetryRequested=TRUE InstallSWUpdate 2015-04-29 17:23:49 616 (0x0268)
Installation is not yet complete, action needs to be re-run after reboot InstallSWUpdate 2015-04-29 17:23:49 616 (0x0268)
Setting TSEnv variable SMSTSInstallUpdateJobGUID= InstallSWUpdate 2015-04-29 17:23:49 616 (0x0268)
Process completed with exit code 0 TSManager 2015-04-29 17:23:49 1904 (0x0770)
!! TSManager 2015-04-29 17:23:49 1904 (0x0770)
Successfully completed the action (Install Software Updates) with the exit win32 code 0 TSManager 2015-04-29 17:23:49 1904 (0x0770)
MP server http://MYSERVER.fqdn.com. Ports 80,443. CRL=false. TSManager 2015-04-29 17:23:49 1904 (0x0770)
Setting authenticator TSManager 2015-04-29 17:23:49 1904 (0x0770)
Set authenticator in transport TSManager 2015-04-29 17:23:49 1904 (0x0770)
Sending StatusMessage TSManager 2015-04-29 17:23:49 1904 (0x0770)
Setting message signatures. TSManager 2015-04-29 17:23:49 1904 (0x0770)
Setting the authenticator. TSManager 2015-04-29 17:23:49 1904 (0x0770)
CLibSMSMessageWinHttpTransport::Send: URL: MYSERVER.fqdn.com:80 CCM_POST /ccm_system/request TSManager 2015-04-29 17:23:49 1904 (0x0770)
Request was successful. TSManager 2015-04-29 17:23:49 1904 (0x0770)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 2015-04-29 17:23:49 1904 (0x0770)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 2015-04-29 17:23:49 1904 (0x0770)
Clear local default environment TSManager 2015-04-29 17:23:49 1904 (0x0770)
The action (Install Software Updates) requested a retry TSManager 2015-04-29 17:23:49 1904 (0x0770)
Reboot to local harddisk TSManager 2015-04-29 17:23:49 1904 (0x0770)
_OSDGinaIsConfigured variable set to TRUE TSManager 2015-04-29 17:23:49 1904 (0x0770)
_SMSTSServiceStartType variable set to TSManager 2015-04-29 17:23:49 1904 (0x0770)
Command line for extension .exe is "%1" %* TSManager 2015-04-29 17:23:49 1904 (0x0770)
Set command line: "bcdedit.exe" TSManager 2015-04-29 17:23:49 1904 (0x0770)
Executing command line: "bcdedit.exe" TSManager 2015-04-29 17:23:49 1904 (0x0770)
Process completed with exit code 0 TSManager 2015-04-29 17:23:49 1904 (0x0770)
Calling RebootSystem() TSManager 2015-04-29 17:23:49 1904 (0x0770)
OSD type of task sequence. ignore the service window setting TSManager 2015-04-29 17:23:49 1904 (0x0770)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 2015-04-29 17:23:49 1904 (0x0770)
Path variable _SMSTSBootStagePath converted from C:\_SMSTaskSequence\WinPE to 7D60A1030000100000000000:\_SMSTaskSequence\WinPE TSManager 2015-04-29 17:23:49 1904 (0x0770)
Updated security on object C:\_SMSTaskSequence. TSManager 2015-04-29 17:23:49 1904 (0x0770)
Set a global environment variable _SMSTSNextInstructionPointer=38 TSManager 2015-04-29 17:23:49 1904 (0x0770)
Set a TS execution environment variable _SMSTSNextInstructionPointer=38 TSManager 2015-04-29 17:23:49 1904 (0x0770)
Set a global environment variable _SMSTSInstructionStackString=0 35 TSManager 2015-04-29 17:23:49 1904 (0x0770)
Set a TS execution environment variable _SMSTSInstructionStackString=0 35 TSManager 2015-04-29 17:23:49 1904 (0x0770)
Save the current environment block TSManager 2015-04-29 17:23:49 1904 (0x0770)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 2015-04-29 17:23:49 1904 (0x0770)
==============================[ OSDSetupHook.exe ]============================== OSDSetupHook 2015-04-29 17:24:50 784 (0x0310)
Executing task sequence OSDSetupHook 2015-04-29 17:24:50 784 (0x0310)
Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat". OSDSetupHook 2015-04-29 17:24:50 784 (0x0310)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} OSDSetupHook 2015-04-29 17:24:50 784 (0x0310)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} OSDSetupHook 2015-04-29 17:24:50 784 (0x0310)
Debug shell is enabled OSDSetupHook 2015-04-29 17:24:52 784 (0x0310)
Successfully enabled debug command shell support. OSDSetupHook 2015-04-29 17:24:52 784 (0x0310)
Configuring local administrator account OSDSetupHook 2015-04-29 17:24:52 784 (0x0310)
Re-assign all drive letters... OSDSetupHook 2015-04-29 17:24:52 784 (0x0310)
The drive information which has no drive letter can not be found. No need to re-assign driver letters. OSDSetupHook 2015-04-29 17:24:52 784 (0x0310)
Installing SMS client OSDSetupHook 2015-04-29 17:24:52 784 (0x0310)
Client already installed. OSDSetupHook 2015-04-29 17:24:52 784 (0x0310)
Moving logs to SMS client directory OSDSetupHook 2015-04-29 17:24:52 784 (0x0310)
Sunday, April 12, 2015 5:24 AM
This happens if any application installation is not responding during installation. I have seen with antivirus in my case as it tries to go for update.
Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"
Monday, April 13, 2015 7:20 AM
Hi,
Is the client on a slow link? This would cause content transfer issue.
You may prioritize MP-Client http traffic.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, April 13, 2015 11:51 AM
It makes sense, however, I'm not sure this could be my case.
If so, how do we explain that an older version of the WIM works fine (as is the case with our production task sequence) but doesn't with a more recent one?
Monday, April 13, 2015 11:52 AM
No. Not the case.
Client is in a fast boundary within our main office where the DP is.
Wednesday, April 15, 2015 6:49 PM
Ok.
I might have made some progress with the help of the Microsoft engineer on my case.
My Setup Windows and Configuration Manager step previously had the following parameters:
SMSCACHESIZE=20000 CCMINSTALLDIR=C:\Windows\CCM SMSMP=FQDN.Primary.Site FSP=FQDN.Primary.Site
PATCH="%_SMSTSMDataPath%\OSD\XYZ000D2\hotfix\KB3026739\Client\x64\configmgr2012ac-r2-kb3026739-x64.msp"
This is the MSP for CU4.
Apparently, the CU4 installation causes the client service to restart, and in turn, not able to reconnect to the TS.
The case is still opened, so I don't know yet WHY this happens. But as soon as I remove Patch=... everything works smoothly.
Now... I could be wrong but... Isn't applying the CU this way one of the numerous supported methods that should work???
Wednesday, April 15, 2015 7:26 PM
From my understanding, use of a variable like that in the patch parameter can be unreliable. One better option is to use a C:\SMSTaskSequence based path, which will work during OSD every time. Here's a post about this.
If you have integrate your SCCM installation with MDT, the best solution I've seen is using a deployment guys script, details here.
The downside to option one, is that value you supply using PATCH is used later if the client wants to fix itself and needs to obtain the msp file. Obviously once a task sequence finishes successfully that C:\SMSTaskSequence won't be valid. Option 2 doesn't have this problem :).
Hope that makes sense!
Tuesday, April 28, 2015 9:47 AM
Hi,
Since you have case opened with Microsoft support, did you figure this out?
Can you share the solution which may also help the others in this forum?
Thank you.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, May 1, 2015 2:53 PM
Just spent a good two hours with Microsoft Premier on the phone.
Here's what we are attempting now:
http://www.danielclasson.com/how-to-force-an-sccm-2012-client-out-of-provisioing-mode-during-osd/
I'll report back Monday with the results :)
Tuesday, May 12, 2015 12:02 PM
No go.
This actually made my Task Sequence worse! The build and capture was failing on the Software Updates step because of errors saying that server couldn't find the WSUS server, it was overwritten by an higher authority/domain controller/GPO.
I did see that message in the past, but that was when my machine was joined to the domain.
In this case, this machine was not in the domain yet as I was building it. Guess what? I disabled the two reg keys, and voilà, the Build and Capture was succesfully attempting to patch again.
Since my TS is more or less comprised of the following steps:
- Install Windows
- Inject Windows 7 Language Pack offline
- Inject IE10 offline
- Install Framework 4.5.2
- Install Visual c++ redist 2005, 2008, 2010, 2011
- Install Office 2010
- Install Software Updates
- Scan, Pause, Install Software Updates
- Scan, Pause, Install Software Updates - Scan, Pause, Install Software Updates
So... That wasn't working. I'll try this:
- Install Windows
- Install Software Updates - Inject Windows 7 Language Pack offline
- Inject IE10 offline
- Install Software Updates - Install Framework 4.5.2
- Install Visual c++ redist 2005, 2008, 2010, 2011
- Install Office 2010
- Install Software Updates
- Scan, Pause, Install Software Updates
- Scan, Pause, Install Software Updates
- Scan, Pause, Install Software Updates
Maybe the fact that I'll break down the quantity of patches will work. Who knows.
Wednesday, May 13, 2015 1:32 AM
Yeah the number of updates in Win7 + Office + .NET, etc can be too much for a B&C.
The only difference we have from your list above is we do the scan and pause before every Install Software Updates step.
Daniel Ratliff | http://www.PotentEngineer.com | @PotentEngineer
Wednesday, May 13, 2015 11:39 AM
Well, yesterday it completed successfully twice. Which is definite progress!
During the whole troubleshooting steps I had resorted to disabling the capture portion in the TS and putting it in a different TS, that way I could let the client patch itself out of the TS and afterwards, when completed, I could run the capture.
This morning I just re-enabled the Capture in the TS, so I'm just now starting a full B&C. Let's hope my luck keeps on holding.
Two things I'd like to have the community's opinion on while I wait for the TS to run...
1) Daniel, how long did you set your pauses? 30 seconds? The reason why I am asking is because there is still something I find odd. Right before the capture runs, I have put 3 passes of Install Software Updates. Yesterday, the test that ran while I was still at the office, the machine only actually installed patches on the last pass. The first two passes scanned, paused and installed no updates. I found it odd that it only installed at the last pass. Maybe my pauses are too short?
2) While on my call with Microsoft, the engineer did propose an idea that I had never thought about. If my "golden" image is good and no softwares need to be changed or updated, would it be a good idea to create some kind of delta B&C TS that would have the following steps:
- Install Windows (by using your current golden image instead of the default Windows 7 wim)
- Scan, Pause, Install Software Updates
- Capture
This seemed like a good idea actually. I was planning on trying it with the May 2015 patches as we will be downloading them today. Any thoughts on this?
Have a nice one guys, I'll report back as soon as my TS completes!
Thursday, May 14, 2015 12:44 AM
Our pause is set to 180 seconds. We do a scan, then pause.
We use our 'gold' image to create a handful of other images. It helps to not have to reload everything in each B&C but I am not sure how this will help installing too many software updates.
Daniel Ratliff | http://www.PotentEngineer.com | @PotentEngineer
Friday, May 15, 2015 12:11 PM
Thanks Daniel,
I'll try that as soon as I can.
While working on the B&C, I ran into a new issue which I describe in depth here: https://social.technet.microsoft.com/Forums/en-US/d0f7f746-cef1-445c-99cc-511da480a16f/geteula-text-failed-hr80240033?forum=configmanagersecurity
As soon as I'm done, I'll update this post.
Tuesday, May 19, 2015 1:30 PM
Ok issue resolved.
And of course, since I was away from the office for 3 days, I completely forgot to change my pause to 180 seconds before I restarted my B&C.
Oh well, what's one more attempt in the grand scheme of things?
Last Friday, I was able to run a big part of my Build & Capture. As far as I can tell from the logs, it does seem like my 3 passes at patching worked, but I don't seem to see anything in my SMSTS.log for Preparing Configuration Manager Client. But after the failing for whatever reason, I'm back at a default Windows login screen. But nothing pops up in my software center, so it seems as though it failed during that step. But... That step is quite generic no? I mean... What are the chances of something bugging out in that particular step?
Monday, May 25, 2015 2:01 PM
Coincidentally, I had some issues with patches installing during my B&C last week. I moved things around, double checked all my steps, and found one issue.
The VM I run my B&C on is pretty slow, so I started checking the logs and found the software update scan I wait 180 seconds for was taking a whopping 11 minutes!! The 3 minutes I had before just wasnt long enough for the scan to complete. I bumped it to 900 seconds, and the built went through the very next time.
You may want to look into how long your Software Update Scan is taking instead of setting an arbitrary number.
Daniel Ratliff | http://www.PotentEngineer.com | @PotentEngineer
Tuesday, May 26, 2015 2:10 PM
Hi Daniel,
I'm curious, which log precisely were you able to see the scan duration?
In my case, I think bumping the time to 180 up from the original 30 definately helped. I was now able to do 2 full captures without issue. I still did have a failure one of the attempts, but it's definately better. But, I like your theory. Maybe even 180 seconds is too short.
I'll check my logs also once you point me in the right direction!
Tuesday, May 26, 2015 7:23 PM
You want C:\windows\ccm\logs\ScanAgent.log. Something like below...
Message received: '<?xml version='1.0' ?> <UpdateSourceMessage MessageType='ScanByUpdateSource'>
<ForceScan>TRUE</ForceScan>
<UpdateSourceIDs>
<ID>{46A0176C-FDEE-46E6-915B-872BC0DC013E} </ID>
</UpdateSourceIDs>
</UpdateSourceMessage>'
ScanAgent 5/26/2015 3:21:52 PM 11652 (0x2D84)
*****ScanByUpdateSource request received with ForceReScan=2, ScanOptions=0x0000000a, WSUSLocationTimeout = 604800 ScanAgent 5/26/2015 3:21:52 PM 11652 (0x2D84)
Sources are current and valid. TTLs are also valid. ScanAgent 5/26/2015 3:21:53 PM 11652 (0x2D84)
*****WSUSLocationUpdate received for location request guid={E6B2F6F2-3F91-44DC-8159-3A9AA257E231} ScanAgent 5/26/2015 3:21:53 PM 8076 (0x1F8C)
ScanJob({A9268A7C-8052-4E38-A183-147364DA5055}): - - - - - -Locations requested for ScanJobID={A9268A7C-8052-4E38-A183-147364DA5055} (LocationRequestID={E6B2F6F2-3F91-44DC-8159-3A9AA257E231}), will process the scan request once locations are available. ScanAgent 5/26/2015 3:21:53 PM 11652 (0x2D84)
Sources are current and valid. TTLs are also valid. ScanAgent 5/26/2015 3:21:53 PM 11652 (0x2D84)
ScanJob({A9268A7C-8052-4E38-A183-147364DA5055}): Performing Full Scan. ScanAgent 5/26/2015 3:21:53 PM 11652 (0x2D84)
ScanJob({A9268A7C-8052-4E38-A183-147364DA5055}): Scan Succeeded, Resetting Source to Current and TTLs to Valid ScanAgent 5/26/2015 3:22:40 PM 8076 (0x1F8C)
ScanJob({A9268A7C-8052-4E38-A183-147364DA5055}): CScanJob::OnScanComplete - Scan completed successfully, ScanType=1 ScanAgent 5/26/2015 3:22:40 PM 8076 (0x1F8C)
ScanJob({A9268A7C-8052-4E38-A183-147364DA5055}): CScanJobManager::OnScanComplete -ScanJob is completed. ScanAgent 5/26/2015 3:22:40 PM 8076 (0x1F8C)
ScanJob({A9268A7C-8052-4E38-A183-147364DA5055}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients... ScanAgent 5/26/2015 3:22:40 PM 8076 (0x1F8C)
- - Calling back to client on Scan request complete... ScanAgent 5/26/2015 3:22:40 PM 11652 (0x2D84)
CScanAgent::ScanComplete- Scan completion received. ScanAgent 5/26/2015 3:22:40 PM 11652 (0x2D84)
Daniel Ratliff | http://www.PotentEngineer.com | @PotentEngineer
Wednesday, May 27, 2015 6:38 PM
Ok ok.
Let me have a look. Altough, your excerpt doesn't seem too awful. I see less than a minute.
Unless you posted a random excerpt and not the actual long scan you mentionned. Which would make sense.