SCCM 2012 R2 - Maintenance Windows + Installation deadline ASAP + Deadline Randomization

There are a ton of questions out there regarding MWs and deadlines etc, but I haven't found any yet with my specific question:
If I:
Use an ADR that sets the software available time and installation
deadline both to ASAP 
AND
put my machines into maintenance windows
AND
enabled deadline randomization (disabled by default in SP1 and R2)
Will the deadline randomization take place during the maintenance window?
I know the default setting for the randomization is 0-120 minutes so if I match that and make my MW 2 hours, can I expect all the machines in that MW to patch ONLY during the MW but at a random time during those 2 hrs?

I tried for a couple days and could not get any of my 3 test machines to patch during the maintenance window with deadline randomization enabled.
Yesterday I disabled it and over the night, 2 of my 3 machines patched during the MW.
It doesn't appear to like the proposed setup - I would have anticipated them patching during the MW but during a random time between 0-120 min from when the MW started

Similar Messages

  • SCCM 2012 R2 - Maintenance Windows - a few questions

    Let's say I configure a maintenance windows (MW) for the 2nd saturday of every month from 6p-10p and I have 100 servers in this maintenance window,
    are they all going to try and patch and reboot at the same time?
    (Assuming they are all online)
    This brings up concerns when trying to plan maintenance windows for our servers - especially when we are 80%+ virtualized. I can't find anything that states the sequence of events that happen when a machine goes to install patches based on a MW.
    Do they wait on a heartbeat? Do they typically kick off right at the front of the MW? Does SCCM spread the installs out?
    We currently use WSUS (working on migrating to SCCM) and in WSUS we have a ton of groups based on the hour so we spread out the machines being patched. I am trying to avoid having so many different options and times and instead just using MWs.
    Another issue we are going to run into is certain machines need to be patched/rebooted in a certain order and with others we just cant have them all down at the same time (e.g. domain controllers). I supposed I could create 2-3 phases per patch weekend to
    spread those machines out - is that the best option? (for instance; on the 2nd Saturday we have MW Phase 1 from 6p-8, MW Phase 2 from 8-10, and MW Phase 3 from 10-midnight)

    Let's say I configure a maintenance windows (MW) for the 2nd saturday of every month from 6p-10p and I have 100 servers in this maintenance window,
    are they all going to try and patch and reboot at the same time?
    (Assuming they are all online)
    This brings up concerns when trying to plan maintenance windows for our servers - especially when we are 80%+ virtualized. I can't find anything that states the sequence of events that happen when a machine goes to install patches based on a MW.
    Do they wait on a heartbeat? Do they typically kick off right at the front of the MW? Does SCCM spread the installs out?
    We currently use WSUS (working on migrating to SCCM) and in WSUS we have a ton of groups based on the hour so we spread out the machines being patched. I am trying to avoid having so many different options and times and instead just using MWs.
    Another issue we are going to run into is certain machines need to be patched/rebooted in a certain order and with others we just cant have them all down at the same time (e.g. domain controllers). I supposed I could create 2-3 phases per patch weekend to
    spread those machines out - is that the best option? (for instance; on the 2nd Saturday we have MW Phase 1 from 6p-8, MW Phase 2 from 8-10, and MW Phase 3 from 10-midnight)
    Hi,
    I often help customers with this scenario that you are facing. I'll try to answer your questions as clearly as possible.
    A) Yes, if you have 100 servers in one MW during 6p-10p, they will start at 6p if they have recieved the policy before that. What you can do is to activate the Deadline randomization that was introduced in ConfigMgr 2012 SP1. You can read more on that here
    http://technet.microsoft.com/en-us/library/gg682067.aspx
    B) ConfigMgr does not wait for a heartbeat or anything like that. You need to manage to logic to move your workload from hosts before you take them down for a reboot. VMM could help you with this IIRC. Or at least SCSM SMA and PowerShell. The sequence is
    basically that they install the patches, if a reboot is required, it will reboot at the end of the patches.
    C) Yes you need to create different MWs and place those servers in the MW order that they need to be rebooted. Be careful tough. If you have ServerA, ServerB and ServerC that need to reboot in that order. You place them in MWs in that order. You might end
    up getting patches to some or all of those servers from a Patch Tuesday but perhaps only ServerB will need a reboot so only ServerB will reboot and thus put you in a place you don't want to be. To solve this, create a re-running package/program deployment
    that reboots ALL servers that are sensitive each and EVERY MW.
    Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

  • SCCM 2012 complete maintenance

    Hi
    I am in need of SCCM 2012 complete maintenance task Manual as well as Scheduled maintenance task document. Moreover the
    link for SQL 2008 maintenance task document. If anybody is having the link for these please let me know it would be very helpful for me.I will be very thankful for this.
    Please let me know some link on below topics also.
    How to check Distribution Manager issues , Clean Configuration Manager inboxes on sites , Intermittent Proxy Management Point connection issues to SQL , Make site settings consistent between Primary sites
    Thanks in advance!!!!!!!!!!!!!!!!!
    Regards
    Gokulnath

    Hi,
    The following KB talks about Maintenance tasks default settings in SCCM 2012.
    Maintenance tasks default settings in System Center 2012 and System Center 2012 R2 Configuration Manager
    For SQL 2008 R2,
    Maintenance Tasks
    Best Regards,
    Joyce Li
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SCCM 2012 - Adding Operating System Installer (The specified path does not contain a valid operating system ..)

    I have encountered the dreaded "The specified path does not contain a valid operating system or you do not have permission to access it.  Specify a valid path" message that seems to be popular in many forums .... BUT, so far none of the "solutions"
    have fixed the problem (of I don't understand the fix)
    Configuration
    SCCM 2012 SP1 5.0.7804.1000
    WADK 8.100.26629.0  < Suggested Fix
    Server 2008 R2
    SCCM Administrator with UserID = SCCMAdmin 
    Steps / Fixes I have followed
    I have configured a administrative share
    \\caleb\sources$ to hold directories (such as Apps, Drivers, and OS) with the following NTFS Permissions
    EVERYONE has Read and Execute, List folder, Read permissions<o:p></o:p>
    SYSTEM has Full Control 
    <Suggested Fix
    SCCMManagers (our group that has all SCCMManagers) has Full Control<o:p></o:p>
    SCCMAdmin (the SCCM Admin account that we are using to import image) has Full Control<o:p></o:p>
    Local Administrators (the local machine administrator) has Full Control 
    <Suggested Fix
    <o:p></o:p>
    Another Fix is to explicitly grant all permissions to the SCCM Administrator
    <Suggested Fix
    >Administrative Users ...
    Properties of the SCCM Administrator (for us that is SCCMAdmin) has all the boxes checked<o:p></o:p>
    Another suggestion I was able to glean was to Specify the Network Access Account
    so I configured SCCMAdmin as the Network Access Account.
    Another potential fix is that the image ISO file that has been downloaded is corrupt.   So, I downloaded the Win 7 (and Win 8.1) ISO's from MSDN and did a Checksum check.
    I then mounted the ISO (on 2008R2 I use VirtualClone Drive) and copied the contents of the image to
    E:\Sources\OS\en_windows_7_professional_with_sp1_vl_build_x86_dvd_u_677896 for Windows 7 with SP1
    To double check,
    I computed the Hash on the Install.WIM located in the Sources directory and compared with
    the computed Has Tag for the Install.WIM on the ISO Image  ... and the Hash tag of the WIM's matched (extracted vs what is contained within the ISO)<o:p></o:p>
    I tried to load the images into SCCM 2012 using the "Operating System Installers" option
    UNC to installer
    \\caleb\sources$\OS\en_windows_7_professional_with_sp1_vl_build_x86_dvd_u_677896
    Then I receive the lovely message <o:p></o:p>
    "The specified path does not contain a valid operating system or you do not have permission to access it.  Specify a valid path"<o:p></o:p>
    <o:p> </o:p>
    From
    C:\Program Files (x86)\Microsoft Configuration
    Manager\AdminConsole\AdminUILog\SmsAdminUI.log<o:p></o:p>
    <o:p> </o:p>
    \r\nSystem.Management.ManagementException\r\nGeneric failure \r\n  
    at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus
    errorCode)
       at System.Management.ManagementObject.InvokeMethod(String
    methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
       at
    Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String
    methodClass, String methodName, Dictionary`2 methodParameters, Boolean
    traceParameters)\r\nManagementException details:
    instance of SMS_ExtendedStatus
     Description = "Failed to get the image property from the source WIM
    file due to error 80070002";
     ErrorCode = 2147942402;
     File ="e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspimagepackage.cpp";
     Line = 586;
     Operation = "ExecMethod";
     ParameterInfo = "SMS_OperatingSystemInstallPackage";
     ProviderName = "WinMgmt";
     StatusCode = 2147749889;
    \r\n<o:p></o:p>
    What am I missing ????  I assume something simple but, darn I'm stumped!!!

    Hi,
    Configuration Manager version
    Windows AIK or Windows ADK Version
    Windows PE versions for boot images customizable from the Configuration Manager console
    Supported Windows PE versions for boot images not customizable from the Configuration Manager console
    System Center 2012 Configuration Manager with no service pack
    Windows AIK for Windows 7
    Windows PE 3
    None
    System Center 2012 Configuration Manager with SP1
    Windows ADK for Windows 8
    Windows PE 4
    None
    System Center 2012 Configuration Manager with SP1 and cumulative update 2
    Windows ADK for Windows 8
    Windows PE 4
    Windows PE 3.11
    System Center 2012 Configuration Manager with SP1 and cumulative update 3
    Windows ADK for Windows 8
    Windows PE 4
    Windows PE 3.11 and Windows PE 5
    System Center 2012 R2 Configuration Manager
    Windows ADK for Windows 8.1
    Windows PE 5
    Windows PE 3.11
    Please try to install the Windows ADK for Windows 8.
    http://www.microsoft.com/en-us/download/details.aspx?id=30652
    For more information, please review the link below:
    http://technet.microsoft.com/en-us/library/gg682187.aspx
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Sccm 2012 https workgroup client installation error

    Hello everyone,
    i got a problem workgroup client installation with PKI.
    My SCCM 2012 SP1 hierarchy is:
    sccm1.izmir.local = Primary Site Server, FSP, MP, SUP
    sccm2.izmir.local = MP,DP (internet FQDN is sccmextmp2.izmir.com)
    sccm3.izmir.local = MP,DP, Enrollment Point, Enrollment Proxy Point
    sccm4.izmir.local = Reporting Service Point, Application Catalog Web Service Point and Applicaiton Catalog Web Site Point
    All MP's and DP's IIS configured with Certificate and client has got certificate too.
    i'm using this parameters for installing workgroup client with PKI:
    ccmsetup.exe /source:D:\Client /UsePKICert /NoCRLCheck CCMHOSTNAME=sccmextmp2.izmir.com SMSSIGNCERT=D:\Client\sccm1.cert SMSSITECODE=TCP FSP=sccm1.izmir.local CCMALWAYSINF=1 CCMFIRSTCERT=1
    and my error is in the ccmsetup.log:
    <![LOG[MSI: Action 11:56:36: SmsSetClientConfig. Applies the configuration placed by SmsSetClientConfigInit and configures client framework.]LOG]!><time="11:56:36.673-120" date="02-11-2013" component="ccmsetup" context=""
    type="0" thread="5604" file="msiutil.cpp:314">
    <![LOG[MSI: Setup failed due to unexpected circumstances
    The error code is 80070002]LOG]!><time="11:56:36.719-120" date="02-11-2013" component="ccmsetup" context="" type="3" thread="5604" file="msiutil.cpp:300">
    <![LOG[MSI: Action 11:56:36: Rollback. Rolling back action:]LOG]!><time="11:56:36.907-120" date="02-11-2013" component="ccmsetup" context="" type="0" thread="5604" file="msiutil.cpp:314">
    <![LOG[File C:\Windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
    Action: SmsSetClientConfig.
    ErrorMessages:
    Setup failed due to unexpected circumstances
    The error code is 80070002
    ]LOG]!><time="11:56:49.886-120" date="02-11-2013" component="ccmsetup" context="" type="3" thread="5604" file="msiutil.cpp:872">
    <![LOG[Next retry in 120 minute(s)...]LOG]!><time="11:56:49.948-120" date="02-11-2013" component="ccmsetup" context="" type="0" thread="5604" file="ccmsetup.cpp:8498">
    You got any idea?
    thanks..
    MCT

    Hi;
    yes i'm using last version of SP1 and applied that hotfix.
    By the way i fixed the problem but now i got anothers:) Now i have no errorst in ccmsetup.log. Client agent installed but in Configuration Manager Agent Client certificate:None and Connection Type: Unknown
    CertificateMaintenance.log
    MCT

  • SCCM 2012 SP1 Maintenance -- Random Environments Rebooting Early

    Background on my deployment process for SCCM 2012 SP1:  I run a Powershell script that sends out a package and configures settings exactly the same for the particular environment set. 
    The deployment script will call one or several environments at a time, as applicable. 
    It will take each environment, affix the settings, push the package to be deployed (based on OS) during the specified maintenance window, and repeat. It is a very consistent process.
    Last week, I deployed to A-CLOUD (name changed for simplicity purposes), among others. 
    A-CLOUD went through the same process as the others in the script (see end of paragraph), in which the appropriate settings were checked. 
    The environment was supposed to update and reboot on Saturday, July 12. 
    However, A-CLOUD (only) updated and bounced as soon as I sent out the package on Wednesday, July 9. 
    Also in the same deployment script was B-CLOUD, C-CLOUD, D-CLOUD, and E-CLOUD, which all updated and rebooted as planned on July 12.
    I received an alert that A-CLOUD was rebooted by Configuration Manager.  I checked the reboot logs in Task Scheduler to compare A-CLOUD with C-CLOUD days later to compare a faulty reboot with one that ran correctly
    (both of these environments are on the same site).  There was no difference in the log files. 
    This issue occurs at least one a month and I have only noticed ONE pattern, Server 2008R2 -- however, it is not always the same environment that will reboot early each month, same week, same day, etc.  It seems to be
    random.
    Any ideas?

    This is way too generic to be answered. What ConfigMgr object type are you deploying (package? application?)? How is the reboot initiated? How are the deployment settings etc.?
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM 2012 R2 and Windows 8.1

    Hi,
    I have installed SCCM 2012 R2. SCCM client deployed on 10 PCs and I can explore Hardware resources on all PCs except 1 PC which is 8.1
    so my question now does SCCM 2012 R2 supports 8.1?
    Thanks,
    Kareem Behery

    Hi,
    Yes, ConfigMgr 2012 R2 supports Windows 8.1. Check the Windows 8.1 computer to make sure that the SCCM client is operational and sends in Inventory to the Site server. Inventpryagent.log file on the computer is a good place to start.
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • Wifi profiles SCCM 2012 R2 and Windows Intune

    Hi All,
    A quick question regarding SCCM 2012 R2 and the new Wifi Profiles feature...
    Can anyone confirm if you need windows Intune combined with SCCM 2012 R2 to be able to deploy WIFI profiles to users devices i.e Windows 8.1, IOS and Android platforms?  Microsoft documentation is not clear on this subject.
    Any help would be much appreciated.
    Regards PowerShell90

    It not as straight forward as one would hope. I am running the latest version of SCCM 2012 R2 CU2 connected to my Windows Intune subscription. There are a lot of hickups. One is that the direct of management needs to be all or nothing. In other words you
    either need to use Windows Intune solely to manage your devices or SCCM 2012 R2 (via connector). If the later then you must do everything from in SCCM 2012 R2. You cannot hybrid manage your devices as this will screw things up.
    Android for some reason is left out on a lot of features. I would think that MS Devs would work hard on the market share that being Android, not iOS. Any way, accord to some official MS articles Android is supported, but others claim that not all features
    are, these being the important ones like Email and Wi-Fi Profiles. They simply do not work.
    I think MS is heading in the right direction but there is a lot of work that needs to be done before this is a competitive product. I could care less if connects to my SCCM 2012 R2 server or not. Here are few things that I sent o a MS Support Rep today that
    need to be address.
    1. Better response time when updating devices after enrollment (e.g. Name change).
    2. The ability to locked down uninstalling Windows Intune from device.<o:p></o:p>
    3. The ability to locked down certain features in the Windows Intune app on device (e.g. User can reset device with Windows Intune app, rename, etc...).<o:p></o:p>
    4. Ability to rename device in either Windows Intune Admin Portal and/or SCCM 2-12 R2.<o:p></o:p>

  • SCCM 2012 R2 and windows 7 folder redirection

    Hello gurus
    I want to ask a quick question. Does anyone know if I can do folder redirection, offline folders, roaming profiles and network drive on Windows 7 using SCCM 2012 R2?
    Thanks in advance. 
    Regards,

    The setting does not apply to Windows 7. I tested and DCMagent just thought it is Non-applicable.
    Juke Chou
    TechNet Community Support

  • SCCM 2012 SP1 Secondary Site installation Fails

    Hi.
    I have multiple secondary sites when i am  trying to install  new SCCM 2012 Secondary site server remotely but installation status shows a pending from last few days.
    1) SEC server have privilages on System managent container
    2) Primary site Server account and computer have local admin right on SEC server
    hman logs says the following error message
    Cannot get SQL Certificate from site xxx
    CheckParentSQLServerCertificate: Failed to get SQL certificate for site XXX
    1) Deleted the secondary site and reinstalled the site with different Site code but no luck
    2) Able to telnet 1433 and 4022 from both primary to secondary and vice versa
    3) SQL server Configuration Manager , TCP IP port was set to 1433.
    please let me know if any thing i am missing
    Thanks

    Hi Guys
    Exact same problem as described above:
    Been told to install SQL Express manually first, but even after that, we continued to get the same problem.
    The SQL Communication between the 2 sites doesn't seem to work.
    I noticed that the Primary's SQL Security Account doesn't get created on Primary DB, in the Database replication the link has not yet been created either.
    The "Exec spDrsSendSubscriptionInvalid 'Secondary 3 digit site code','Primary 3 digit site code','configuration data'" worked on 1 Secondary, but fails on all the rest.
    Uninstalling/Installing the Secondary doesn't work either.
    HMAN.LOG:
    Update site server active directory informtion into DB SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
    CheckSQLServiceRestart : SQL Service hasn't been restart since last time we check, skip it. SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
       Time to verify if the parent['PRI-SITECODE'] sql server certificate is still valid on site ['SEC-SITECODE'] sql server. SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
    Cannot get SQL Certificate from Site 'PRI-SITECODE'. SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
    CheckParentSQLServerCertificate: Failed to get SQL certificate for site PM2 SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
    Any ideas would be appreciated.

  • Microsoft Intune and SCCM 2012 R2 Integration - Windows 7 clients.

    Hi All,
    This is our scenario I am trying to find out more about Intune integration with SCCM 2012 R2 and what solution is best for us.
    We have a SCCM 2012 R2 instance up and running which services/monitors machines on our internal network. All of these machines are Windows 7 OS. We have laptops that travel frequently and need for these to report back to our SCCM server whilst connected
    via internet connections. Also we have multiple "off domain" machines (ie workgroup machines) which we also need to report back to the same SCCM server.
    I have read a lot about Intune integration with SCCM but it appears to be targetted at MDM not around PC management.
    What would be the best way for us to move forward?
    Thanks in advance.

    Just see my reply in the ConfigMgr forums. 
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM 2012, Intune and Windows OS Support

    I am just trying to confirm what I believe I am reading about Microsoft OS Support for Windows Intune when integrated with SCCM 2012 R2...
    What I believe to be the case:
    Windows RT, Windows RT 8.1, Windows 8.1 all have the ability to enroll via OMA-DM, thus can be managed by SCCM.
    Down-level OS's such as XP SP3, Vista, and Windows 7 require the Intune Client to be installed, thus can only be managed by a standalone Intune subscription?
    Can anyone confirm this?
    Thanks!

    More or less correct.
    Generally, even for Win 8.1 and WinRT, IBCM or DirectAccess are a better choice than OMA-DM as it can only enable management of a limited subset of features. Two important ones cannot be: software updates and endpoint protection.
    As you've seen (based on your other thread), you can still use the Intune subscription that is connected to your ConfigMgr site to manage devices with the Intune client installed. Effectively, there are two halves of the Intune subscription, the full client
    management half and MDM half which can be controlled by Intune or ConfigMgr. Just because the MDM half is controlled by ConfigMgr does not technically preclude you from still utilizing the full client management half. That's not at all saying you should do
    this though, but you certainly could.
    Jason | http://blog.configmgrftw.com

  • SCCM 2012: hotfixes via Windows updates?

    Hi,i
    Is this still the proper way to deploy hotfixes via Windows updates in SCCM 2012 R2 (the article is more then a year old, maybe SCCM has other built in features to do this)?
    http://blogs.technet.com/b/michaelgriswold/archive/2013/03/13/kb2775511-deployment-for-the-sccm-admin.aspx
    Please advise.
    J.
    Jan Hoedt

    Hi,
    As long as the hotfix is available in the Microsoft Update Catalog which not all hotfixes are, then it will work. It is not really supported to deploy it that way. Otherwise it is possible to deploy them using a package/program which is the way I normally
    does it.
    Here is an example of a script to use.
    http://ccmexec.com/2012/02/installing-multiple-windows-7-hotfixes-msu-with-sccm/
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • SCCM 2012 R2 Distribution Point Installs but does not send packet.

    I installed SCCM 2012 Primary Site on a server and need to create 18 Dps, could create 12 however I am having trouble creating the last 6, the link from headquarters to branch MPLS is a full 256 Kb, it creates the folders and DPs however the server can not
    send the first two packages that are Client Package Configuration Manager and Configuration Manager Client Upgrade package only 6 DPS the other 12 I got. 
    The computer account is in the Administrators group and Admin Domains; 
    Already checked the WMI with Wbemtest; 
    I uninstalled and installed the DP again; 
    Below is the log, changed the name to contoso by issues of customer privacy.
    Sleep 928 seconds...      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:00:07       2528 (0x09E0)
    Sleeping for 60 minutes before content cleanup task starts.      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:10:52              
    5772 (0x168C)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:12:13       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:40       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x14F4 (5364) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:40              
    2528 (0x09E0)
    Sleep 60 seconds...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:40       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.072 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    Retrying package LAA00003       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:41       5264 (0x1490)
    Thread Handle = 0000000000002330       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5264 (0x1490)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41              
    5264 (0x1490)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    DP thread with thread handle 0000000000002330 and thread ID 5264 ended.    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:41      
    5364 (0x14F4)
    Only retrying local DP update for package LAA00003, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    SourceVersion (1) of package LAA00003. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:41       5364 (0x14F4)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.684 2014 ISTR0="Configuration Manager Client Package"
    ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41                5364 (0x14F4)
    Failed to process package LAA00003 after 66 retries, will retry 34 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:41      
    5364 (0x14F4)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41      
    5364 (0x14F4)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:46       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x14D0 (5328) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47              
    2528 (0x09E0)
    Sleep 1824 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.300 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    Retrying package LAA00004       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:47       5736 (0x1668)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5736 (0x1668)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47              
    5736 (0x1668)
    Thread Handle = 0000000000002A50      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    DP thread with thread handle 0000000000002A50 and thread ID 5736 ended.   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:47      
    5328 (0x14D0)
    Only retrying local DP update for package LAA00004, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    SourceVersion (1) of package LAA00004. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:47       5328 (0x14D0)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.910 2014 ISTR0="Configuration Manager Client Upgrade Package"
    ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"             
    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:47       5328 (0x14D0)
    Failed to process package LAA00004 after 66 retries, will retry 34 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:47      
    5328 (0x14D0)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47      
    5328 (0x14D0)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:52       2528 (0x09E0)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:52       2528 (0x09E0)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:42:18       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x1394 (5012) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23              
    2528 (0x09E0)
    Sleep 60 seconds...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:23.524 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:23       5012 (0x1394)
    Retrying package LAA00003       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:23       5012 (0x1394)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:23       5112 (0x13F8)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:23       5112 (0x13F8)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23              
    5112 (0x13F8)
    Thread Handle = 0000000000001CF0      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    DP thread with thread handle 0000000000001CF0 and thread ID 5112 ended.   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:23      
    5012 (0x1394)
    Only retrying local DP update for package LAA00003, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:24       5012 (0x1394)
    StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:24       5012 (0x1394)
    SourceVersion (1) of package LAA00003. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:24       5012 (0x1394)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:24.068 2014 ISTR0="Configuration Manager Client Package"
    ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:24                5012 (0x1394)
    Failed to process package LAA00003 after 67 retries, will retry 33 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:24      
    5012 (0x1394)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:24      
    5012 (0x1394)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x176C (5996) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29              
    2528 (0x09E0)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:29.592 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:29       5996 (0x176C)
    Retrying package LAA00004       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:29       5996 (0x176C)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:29       4576 (0x11E0)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:29       4576 (0x11E0)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29              
    4576 (0x11E0)
    Thread Handle = 00000000000025F8       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    DP thread with thread handle 00000000000025F8 and thread ID 4576 ended.    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:29      
    5996 (0x176C)
    Only retrying local DP update for package LAA00004, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:30       5996 (0x176C)
    StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:30       5996 (0x176C)
    SourceVersion (1) of package LAA00004. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:30       5996 (0x176C)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:30.137 2014 ISTR0="Configuration Manager Client Upgrade Package"
    ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"             
    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:30       5996 (0x176C)
    Failed to process package LAA00004 after 67 retries, will retry 33 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:30      
    5996 (0x176C)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:30      
    5996 (0x176C)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:35       2528 (0x09E0)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:35       2528 (0x09E0)
    Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA.   SMS_DISTRIBUTION_MANAGER             14/08/2014
    00:59:32               4008 (0x0FA8)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       5292 (0x14AC)
    Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:32       4008 (0x0FA8)
    Processing status update for package LAA00003              SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32               
    4008 (0x0FA8)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       2528 (0x09E0)
    Sleep 1048 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       2528 (0x09E0)
    Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00003, Status 5            
    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       4008 (0x0FA8)
    Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA     SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:32               4008 (0x0FA8)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:37       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:37       2528 (0x09E0)
    Sleep 1043 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:37       2528 (0x09E0)
    Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA.  SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:39              
    4008 (0x0FA8)
    Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:39       4008 (0x0FA8)
    Processing status update for package LAA00004              SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:39               
    4008 (0x0FA8)
    Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00004, Status 5            
    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:39       4008 (0x0FA8)
    Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA    SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:39               4008 (0x0FA8)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:42       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:42       2528 (0x09E0)
    Sleep 1038 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:42       2528 (0x09E0)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:47       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:47       2528 (0x09E0)
    Sleep 1033 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:47       2528 (0x09E0)
    Sleeping for 60 minutes before content cleanup task starts.      SMS_DISTRIBUTION_MANAGER             14/08/2014 01:10:52              
    5772 (0x168C)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:28       5292 (0x14AC)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33       5292 (0x14AC)
    Found notification for package 'LAA00003'          SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33      
    2528 (0x09E0)
    Found notification for package 'LAA00004'          SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33      
    2528 (0x09E0)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x388 (904)      SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33              
    2528 (0x09E0)
    Starting package processing thread, thread ID = 0x1678 (5752) SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:34              
    2528 (0x09E0)
    Sleep 3600 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:34       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=904 GMTDATE=qui ago 14 04
    Lucas Simoes MCTS

    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              13/08/2014 23:57:10               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    13/08/2014 23:57:10       4004 (0x0FA4)
    Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:11       4004 (0x0FA4)
    Created sending thread (Thread ID = 0xBE8)     SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:11               
    4004 (0x0FA4)
    Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:11       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x3B4)     SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:11               
    4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:11               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:11       4004 (0x0FA4)
    Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:35       3048 (0x0BE8)
    Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:35       948 (0x03B4)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:36.046 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       3048 (0x0BE8)
    Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       3048 (0x0BE8)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:36.484 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       948 (0x03B4)
    Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       948 (0x03B4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:45       3048 (0x0BE8)
     PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:45 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:45       3048 (0x0BE8)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:45.880 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:45       3048 (0x0BE8)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:45      
    3048 (0x0BE8)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:45               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:45       4004 (0x0FA4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:52       948 (0x03B4)
     PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:52 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:52       948 (0x03B4)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:52.923 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:52       948 (0x03B4)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:52      
    948 (0x03B4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:52               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:52       4004 (0x0FA4)
    Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:37:52       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x1680)   SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:37:52               
    4004 (0x0FA4)
    Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:37:53       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x18A4)   SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:37:53               
    4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:37:53               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:37:53       4004 (0x0FA4)
    Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:16       5760 (0x1680)
    Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:17       6308 (0x18A4)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:20.098 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       6308 (0x18A4)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:20.111 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       5760 (0x1680)
    Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       6308 (0x18A4)
    Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       5760 (0x1680)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:43       6308 (0x18A4)
     PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:43 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:43       6308 (0x18A4)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:43.622 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:43       6308 (0x18A4)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:43      
    6308 (0x18A4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:43               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:43       4004 (0x0FA4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:50       5760 (0x1680)
     PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:50 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:50       5760 (0x1680)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:50.708 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:50       5760 (0x1680)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:50      
    5760 (0x1680)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:50               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:50       4004 (0x0FA4)
    Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:58:50       4004 (0x0FA4)
    Created sending thread (Thread ID = 0xF28)      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:58:50               
    4004 (0x0FA4)
    Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:58:50       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x11D0)   SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:58:50               
    4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:58:50               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:58:50       4004 (0x0FA4)
    Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:15       3880 (0x0F28)
    Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:15       4560 (0x11D0)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:16.990 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:16       3880 (0x0F28)
    Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:17       3880 (0x0F28)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:17.845 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:17       4560 (0x11D0)
    Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:17       4560 (0x11D0)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       3880 (0x0F28)
     Attempted max retry count. The job would be marked for deletion now.                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       3880 (0x0F28)
    Sent status to the distribution manager for pkg LAA00003, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27       3880 (0x0F28)
    STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.291 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       3880 (0x0F28)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.305 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27       3880 (0x0F28)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27      
    3880 (0x0F28)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       4004 (0x0FA4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4560 (0x11D0)
     Attempted max retry count. The job would be marked for deletion now.                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4560 (0x11D0)
    Sent status to the distribution manager for pkg LAA00004, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34       4560 (0x11D0)
    STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.335 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4560 (0x11D0)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.337 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34       4560 (0x11D0)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34      
    4560 (0x11D0)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 01:19:34               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 01:19:34       4004 (0x0FA4)
    No (more) send requests found to process.     
    SMS_PACKAGE_TRANSFER_MANAG
    Lucas Simoes Rezende MCP, MCTS , ITIL V3

  • Software Asset Management Solution Accelerator for SCCM 2012 (Contracts, Licenses, Userights, Installations and net usage

    Hello All
    With the given need from the market to manage license compliance proactively - the givven toolsets from MS SCCM 2012 should be capable of handling the given complexity. (reference 27 processes out of SAM ISO 19.770-1:2012
    Where can I find the solution accelerator, which guides us to help clients on two tipical use-cases
    a.) Client has SCCM 2012 - however not yet established the SAM componentes to it (Contracts, Use-rights and License-Comparizons)
    b.) Client has no SCCM yet and wants to start his journey with the Commercial scope right away.
    Any guidance highly appreciated

    SCCM alone isn't going to fit this need.
    You need a License Compliance Solution / Software Asset Management (SAM) solution which SCCM is not.
    The issue with those system, they fail of providing clean /usefull data.
    Usually the best approach is to collect the data with SCCM, normalize the data for that I used BDNA Normalize, then pull in the SAM.
    Like this:
    SCCM 2012 - Normalize - SAM
    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

Maybe you are looking for

  • Error "ssl_error_rx_unexpected_server_key_exch" Since Upgrading to 3.6.9

    Since the upgrade to 3.6.9 was released today, we are now getting the following error on one of our secure websites. Our SSL certificate has been in place since March and is generated by Thawte. This site works fine in Internet Explorer and worked fi

  • BB in Home sub forums? Need your feedback in Idea...

    Hi Guys Not sure if you have had a chance to check out the Ideas Bank yet?  An idea has been submitted suggesting that the BB in Home board should be split into smaller sub forums?  What do you think?  Is this a good idea?  What sub-forums should we

  • It says that my computer is supposedly too old for my iPod

    I recently bought the original iPod, but when I tried connecting it to my computer, it came up with a sign that says: The iPod "iPod" cannot be use becuse it requires MAC OS X 10.4.8 or over. Do I have to buy I whole new computer? I really hope not.

  • Invoice Verification (MIRO) allocation via Delivery note

    We are in 5.00 version In our system the same Delivery note number could be associated not only to different vendor, but even to the same vendor in different years. In the last case the system allocate ALL the Delivery notes. I try to use the F4 func

  • Contact Center Licence Invalid?

    Hi all, I am trying to load a CCX license and i get the attached error message. Could this be that the license in invalid or currupt? Please what could be the cause and how do I handle it?