ConsoleOne on Windows 7 GW client 802 TopDown Rebuild issue

Does anyone seen this issue before? Recently (3 months ago) we have migrated to GW 8. We are using Windows 7 64 bit and consoleOne 1.3.6h.
We have done topdown rebuild on all Domains and PO's. While logged in to ConsoleOne >Tools>Groupwise System Operations> Pending transactions. It does shows me 3-5 domains in "Modify" operations.
We checked the DB and rebuild agian and it shows same. Can't add or change password for the objects in consoleone too.
Any help would be greatly appreciated.

It seems no one installed such configuration and never had any issue. Please let me know what to do in case if you resolve this in future...:-)

Similar Messages

  • OBIEE 11.1.1.7 SSO for Windows Native Clients Error 401-UnAuthorized issue.

    I configured OBIEE to work with AD authenticator and AD authentication works fine. My AD users can login with their credential. I am having issues with Kerberos authentication. My keytab looks fine and kinit is successful too and do not have any duplicate SPNs. After configuring Kerberos, "I am getting error 401 Unauthorized" .
    I have an AD user bisystem which I generated SPN and key tab looks fine. My other AD users belong to AD group "Technical".
    What should be the principal-name in weblogic.xml?
    I have put <principal-name>bisytem</principal-name>
                     <principal-name>Technical</principal-name> in weblogic.xml

    from bi_server.out:
    default etypes for default_tkt_enctypes: 17 23 3 1 23.
    Pre-Authenticaton: find key for etype = 3
    AS-REQ: Add PA_ENC_TIMESTAMP now
    >>> EType: sun.security.krb5.internal.crypto.DesCbcMd5EType
    >>> KrbAsReq calling createMessage
    >>> KrbAsReq in createMessage
    >>> KrbKdcReq send: xxxx  timeout=30000, number of retries =3, #bytes=270
    >>> KDCCommunication: kdc=xxxx #bytes=270
    >>>DEBUG: TCPClient reading 106 bytes
    >>> KrbKdcReq send: #bytes read=106
    >>> KrbKdcReq send: #bytes read=106
    >>> KdcAccessibility: remove xxxxx
    >>> KDCRep: init() encoding tag is 126 req type is 11
    >>>KRBError:
             sTime is Wed Apr 15 13:32:41 EDT 2015 1429119161000
             suSec is 553936
             error code is 14
             error Message is KDC has no support for encryption type
             realm is xxxx
             sname is krbtgt/xxxxx
             msgType is 30
                    [Krb5LoginModule] authentication failed
    KDC has no support for encryption type (14)
    Any insight???

  • Windows 7 client won't connect with 802.1x security

    Having issues connecting a windows 7 dell laptop with cisco unified wireless infrastructure.  Currently running 4 4402 WLCs and 1 wism.  The client in question is trying to connect to an AP that sits on one of the controllers on the wism.  WLC code running is 6.0.199.  If I configure the windows 7 client to an ssid with wpa2 with preshared key it works with no issue.  It's really problematic with 802.1x, wondering if there is addition settings on the adapter in win 7 that I'm missing or have overlooked.
    Thank you in advance for any suggestions to a solution to my problem
    Regards,
    izzy

    Windows is going to want to use the credentials that you login to the machine.  SO if you logged is as "administrator" but you need to authenticated as domain\John.Smith  you need to manipulate the credentials.
    If you are logging in to the machine with valid domain credentiasl though, it becomes a bit more difficult.
    So, is this the only type of machine having an issue?  What is the driver version and chipset type?
    you can run debug client < cliet ma address > and watch what is happening from the controllers persepctive. You can also see what username is being sent to the AAA server.
    Cheers,
    Steve
    If  this helps you and/or answers  your question please mark the question as "answered" and/or rate it, so  other users can easily find it.

  • ConsoleOne and Windows 7

    With the rapid oncoming inevitability of Windows 7 and having completely skipped Vista as a viable Enterprise OS I've been doing a bit of testing.
    I have had Windows 7 x64 Build 7232 running as my primary OS for a bit over a week now and I have to say that it's quite an accomplished presentation. Using the Novell Client 2 for Windows Vista/2008 I have managed to set up my desktop in a thoroughly usable manner with a fully working GroupWise 8 client, properly mapping drives (after an initial odd process of having to re-enter my Tree and Context a couple of times it now goes in an maps all drives seamlessly), and up until yesterday when I allowed my machine to sleep overnight a fully working ConsoleOne.
    It appears that the Novell Client, Groupwise and especially ConsoleOne do not like being recovered out of Sleep as all the network connections are dropped and do not recover gracefully. Groupwise and the drive mappings were not an issue as rebooting and logging in again resolved that issue without much fuss. ConsoleOne on the other hand has not recovered gracefully at all. Now when attempting to make a change to a user I get communication errors and when trying to change a users password I get the following error:
    (Error 0x8801) A request was attempted with and invalid or nonattached connection handle.
    Further investigation (i.e. clicking on Details :) ) produces this:
    0x8801 CONN INVALID
    Source
    Client Services
    Explanation
    An attempt by an application to request a connection failed. If a connection is closed, it becomes invalid.
    Possible Cause
    The connection handle that is being used by the requesting application no longer refers to a given connection slot in the requester's connection table. In this case, the application, such as an executable file or driver, might be out of date.
    Possible Cause
    An application might request that a connection be closed without any regard to other applications that point to the open connection.
    Action
    Try the task again. If the error persists, contact the developer of the application for the latest version of the application.
    Possible Cause
    The server ran out of connections.
    Action
    To free a connection, have a user who is connected to the server log out. Or, to increase the number of connections allowed for that server, go to a workstation where a user is connected to the server and has Supervisor rights, and increase the number of connections allowed.
    Possible Cause
    The software might not allow more connections for the client. For example, in some of the NetWare 3.12 utilities, like MAP and CAPTURE, this error will be returned if the workstation is attached to 9 or more servers. In NetWare 3.12, these utilities were designed to provide functionality for only 8 servers.
    Action
    If you desire to increase the number of connections that a workstation can have, use a version of the software that will allow more connections. The utilities in NetWare 4 and later versions allow this number of connections.
    Possible Cause
    The connection might have been closed at the server, such as by an administrator clearing a connection using MONITOR.
    Action
    If desired, have the user log in again to the network.
    A trademark symbol (,TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For information on trademarks, see Legal Notices.
    Error Codes Contents
    So - a little ambiguous in the Possible Cause/Action scenarios. I did try uninstalling my Novell Client and re-installing without NMAS as this has been known to cause issues.
    The other thing I would've liked to have tried was re-installing ConsoleOne - but there is the small issue of C1 checking for an up to date version of the Novell Client being present and as was entirely expected C1 doesn't recognise the Beta Novell Client 2 for Windows Vista/2008 as being a viable up to date Windows client and promptly boots you out of the install siting that version 4.91 is a much more up to date client and that I should install that instead before trying to update C1... Nice...
    You might ask how I got C1 working on Windows 7 in the first place - well it was fairly straight forward - I copied the installation off the network rather than trying to do a local install as I have seen many instances of people having to do registry hacks to get it installing - this doesn't make much sense to me as the reality is that the majority of enterprise environments use Windows and within the next 6-12 months Windows 7 is going to start having a level of penetration making our having to administer to it inevitable.
    Not being able to administer to your environment because the tools don't work is not really acceptable. Granted W7 is in RC1 at the moment and as such is not strictly a released OS and as such isn't 'supported' surely it's better to start looking into this stuff sooner rather than later. I'd use iManager but it is an utterly painful and woefully non-intuitive tool when compared to C1. There is a HUGE amount of work left to go toward making that one a viable admin tool.
    So rant over - my questions:
    1. Is ConsoleOne a dead admin tool and is it something that we as network administrators should be fogetting in favor of iMangler?
    2. Does anyone have a more definitive idea what might be causeing the 0x8801 CONN INVALID error and what might be a way of fixing it as for now ConsoleOne is a significantly better admin tool for us.
    3. Are the any plans for Windows 7 support and when is Novell going to start making this support available to the end users?
    4. As far as Novell admin tools go - am I missing something? Is there a super intuitive clever admin tool out there that nicely centralises our workload?
    Many thanks!
    Steve

    Originally Posted by Marcel_Cox
    Well, Novell doesn't support running ConsoleOne on anything beyond Windows
    XP. About the time NetWare 6.0 was relased more than half a dozen years
    ago, Novell decided that the future direction was iManager and that all
    new poroducts should be managed through iMAnager. Alas, as so often,
    Novell doesn't have the power to impose its own decisions to its own
    product teams and so some teams continued to use ConsoleOne as their main
    management tool, even though the death of ConsoleOne was clearly and
    loudly announced in advance. This now leaves the customers in the bad
    situation that a recently shipped product like Groupwise 8 uses a dead an
    unsupported Management tool ConsoleOne.
    Bad is one way to put it, extremely amateurish is another. How can a company as large and established as Novell after six years still get this realtively basic thing so wrong? Don't get me wrong, I've been a Novell fan for years but, there is something terribly wrong with the development process if upper management can't control their own dev teams!
    So not only are we as customers faced with a piecemeal approach to our admin processes but we're also going to have to face having to administer with externally unsupported tools whilst the dev teams still insist on plugging away with them. Personally I'd start putting my time an effort back into getting ConsoleOne into a usable state as it is far superior (I can't believe I'm saying this about Conslow 1 ;) ) admin tool compared to the entirely unintuitive iManager. Either that or employ some accessability specialists to work on iManager because in it's current state it is not a particularily friendly structure to work through.
    Originally Posted by Marcel_Cox
    Now the fact that you first got ConsoleOne to work is because you have
    been using an older version of ConsoleOne which didn't check for the
    client version yet. That last version of consoleOne does in fact include a
    client version check and refuses to run on a client with a version number
    less than 4.91 (assuming of course the v4.91 client for Windows XP). Now
    the newer clients for Vista and beyond have version numbers 1 and 2 which
    are of course lower than 4.91 and therefore ConsoleOne refuses to run. You
    can however cheat and make ConsoleOne think you have a newer client
    version. This is described here:
    Installing and Running ConsoleOne on Windows Vista
    Cheers for the reply Marcel, I do appreciate it despite my gripes about the situation. I used the registry hack and it did allow me to install 1.3.6h successfully - after renaming the old install directory of course. Unfortunately I still have the same issue as before. I also tried installing 1.3.6h over the top of the old install as well so that it carried across all my snapins with the same unsuccessful result.
    Currently any user password resets are being done via iManager, which by the way I still have to figure out how to assign roles etc to myself, using an admin user account which is not overly desireable. Any major changes are still being done through ConsoleOne with my dual booted XP install which seems perfectly happy.
    Being completely aware of how annoying it is to hear someone b*tch and moan about and issue and not offer any solutions I would offer my services/suggestions as a long time admin for a potential remodeling of iManager to a much more usable and admin friendly interface however I have no idea either who to talk to or whether they would listen.
    Anyway - again I appreciate your response and if anything else comes to mind please let me know!

  • Where to download the "Windows 2000 Wireless 802.1X hot fix"?

    From the "Cisco Aironet Wireless LAN Client Adapters Configuration Guide for Windows", it indicates that Windows 2000 can support host-based EAP with the "Service Pack 3 or greater and the Windows 2000 Wireless 802.1X hot fix".
    However, I cannot find the 802.1x hot fix in Microsoft. Please kindly advise how I can download this hot fix. And, what is the function of this 802.1 hot fix?
    Thanks!!!!

    Hi!
    Here you have the link to the hotfix :
    http://www.microsoft.com/downloads/release.asp?ReleaseID=45017&area=search&ordinal=1
    Regards
    Fredric

  • Failed connection Windows 7 clients with WLC2504+NPS 2012

    Hello
    I have some interesting experience. I configured my wireless controller 2504 with a Windows 2012 Server as radius server for authenticating the active directory's users. So, I have one Windows 2012 R2 server configured as a Domain Controller and installed and configure NPS , and  CA server configured in another Windows 2008 R2 Server. Also I have  one clients PC's with Windows 8.1 and several Windows 7 connected to My Domain, also iPad and Android devices out  of Domain of course.
    I used this sources when configuring it.
    http://www.cisco.com/c/en/us/support/docs/wireless/5700-series-wireless-lan-controllers/117684-configure-WLAN-00.pdf
    http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/115988-nps-wlc-config-000.pdf
    The problem is, that all Windows 7 clients do not connect to my SSID with Auth 802.1.x + PEAP , but other clients connect successfully and automatically without problems. 
    I tried a lot of action, for example , from this source http://www.networkworld.com/article/2160056/security/tips-for-troubleshooting-802-1x-connections.html
    But I have no success to resolve it. I ensured that W7 PC using the correct CertAutority. But,  anyway I reinstalled this Cert.
    I have no idea anymore. Please help.
    Some logs in attachments.  

    Thank you for your reply, Sebastian
    Yes, I checked my certificates, and I tried to install manually a certificate of NPS server. Also tried to uncheck the Validate server certificate option. The result was the same - no connect, only logs in controller slightly was changed.  
    Also in advanced section I chosen and User Authentication and User/Computer Authentication. The same result.
    I want to notice, that I configured one else radius server - the Cisco ACS 4.2. This server is not connected with Active Directory. And another ssid is fastened with this radius by EAP. The Windows 7 client connect to this ssid with the following options:
    Unchecked the Validate server certificate
    Unchecked Use Windows logon
    In Advanced Section, check and choose User Authentication, and save the local ACS username and password.
    Now, I want to install a radius on Windows 2003 Server, this server connected to Domain. Let's see how this works out.

  • EAP with Windows 2000 client and IAS server

    Several messages on this site point to peole using EAP on a Windows 2000 client and authenticating against an IAS server. I am running an Aironet 350 AP and trying to setup my Windows 2000 clients to use EAP only and authenticate against a Windows 2000 AD forest via IAS. The access point and client are on the latest firmware and drivers (12.0 for AP). I have two basic questions.
    1. It is my understanding that by enabling Network-EAP as the only authenticaiton type that users will authenticate and then dynamic WEP keys will be used, greatly reducing the risks of compromised WEP keys while at the same time keeping the data encrypted.
    2. Does anyone have a quick HOW-TO or point-by-point list of how to configure the Windows 2000 client to authentication using the Network-EAP method? I am currently running into a situation where no matter what I configure on the client, the IAS server reports and error with "Reason: The authentication type is not supported on this system." I also noticed that the "Authentication-Type" and "EAP-Type" fields shown in the IAS messages in the Windows 2000 Event Viewer log have the value "<undetermined>". Has anyone else run into this?

    I'm having a similar problem. I'm trying to do PEAP and it appears that IAS is not handling the request properly. It keeps trying to log the user PEAP-##### in instead of setting up the TLS and then asking for Username, Pass, Domain. The IAS error message I'm getting is:
    User PEAP-00097CFCD901 was denied access.
    Fully-Qualified-User-Name = APPLY\PEAP-00097CFCD901
    NAS-IP-Address = 172.16.200.31
    NAS-Identifier = AP1
    Called-Station-Identifier = 004096570d87
    Calling-Station-Identifier = 00097cfcd901
    Client-Friendly-Name = WirelessAP
    Client-IP-Address = 172.16.200.31
    NAS-Port-Type = 19
    NAS-Port = 37
    Policy-Name =
    Authentication-Type = EAP
    EAP-Type =
    Reason-Code = 8
    Reason = The specified user does not exist.
    So if anybody has the needed settings for Win2k (SP3 and 802.1x patch) IAS it would be much appreciated.
    Ben
    Note: if I had PEAP-####### as a user in Win2k I get:
    User PEAP-00097CFCD901 was denied access.
    Fully-Qualified-User-Name = apply.org/Users/PEAP TEST
    NAS-IP-Address = 172.16.200.31
    NAS-Identifier = AP1
    Called-Station-Identifier = 004096570d87
    Calling-Station-Identifier = 00097cfcd901
    Client-Friendly-Name = WirelessAP
    Client-IP-Address = 172.16.200.31
    NAS-Port-Type = 19
    NAS-Port = 37
    Policy-Name = Wireless Policy
    Authentication-Type = EAP
    EAP-Type =
    Reason-Code = 16
    Reason = There was an authentication failure because of an unknown user name or a bad password.

  • Windows 2008 Server and Windows 8 clients

    Hey Guys,
    I have had this problem for sometime now and really need a solution. I have Windows 2008 Enterprise Server running about 200+ terminal services clients. All Windows XP clients are fine, Windows 7 clients have issues when they get an updated version of
    remote desktop client(to solve the issue we simply rollback the update), Windows 8 clients cannot connect and use out remote app. The issue stems from the newer version of remote desktop client (on windows 7 and embedded in windows 8) cannot connect to our
    terminal server and generates an error and immediately disconnects. The error says "
    Your computer can't connect to the remote computer because an error occurred on the remote computer that you want
    to connect to
    So my questions are, how can i update my Windows 2008 Terminal server version to support these clients, or do u have migrate to Windows 2012? Or is there a solution to my current problem which will allow my client to connect and use the remoteapps?

    Hi,
    Thank you for posting in Windows Server Forum.
    Please follow the below steps and verify result.
    LAN manager authentication level settings (Local security policy->Local Policies->Security Options->Network Security: LAN Manager Authentication level). 
    Try to change it to "Send NTLMv2 response only" 
    Snap:
    If still face the issue please install this Hotfix.
    RDS client computer cannot connect to the RDS server by using a remote desktop connection in Windows
    http://support.microsoft.com/kb/2752618/
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Windows Update Client failed to detect with error 0xc8000247 after using Lenovo System Update 5

    My Windows 7, SP1 was running fine, until I installed few updates on 10/15 using Lenovo System Update 5 then Windows Update stopped working, shows as RED:
    {CE3119AD-35EF-41CF-9C21-C7698FEB8393}    2013-10-14 21:53:00:256-0700    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 4 updates.
    {EB17A01A-EB6E-49FF-9EA2-AA0DD063B4B1}    2013-10-15 04:15:54:069-0700    1    162    101    {C61A0D00-3E51-48AC-B0AF-1D3E02B9E5D3}    201    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {77DAE88F-2795-4258-8BBF-8D27E53662CF}    2013-10-15 12:10:38:196-0700    1    193    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Restart Required: To complete the installation of the following updates, the computer must be restarted. Until this computer has been restarted, Windows cannot search for or download new updates:  - Security Update for Windows 7 for x64-based Systems (KB2862330)
    {1398F777-3AEF-4D1D-BE4C-407EC4AEAD4C}    2013-10-15 12:15:25:676-0700    1    183    101    {C61A0D00-3E51-48AC-B0AF-1D3E02B9E5D3}    201    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows 7 for x64-based Systems (KB2862330)
    {A220898A-E5FE-4FE7-8413-2B0C7B4013D0}    2013-10-15 12:15:25:766-0700    1    202    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Reboot completed.
    {A5400FF2-33ED-4A47-8409-13E5DFE16A6D}    2013-10-15 19:29:31:486-0700    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    ChkWuDrv    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    {43C533EE-775D-445E-A652-06648B72DE65}    2013-10-15 19:29:49:702-0700    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    ChkWuDrv    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    {D6AAAFFB-7F18-4A7E-B39D-1BA09CDC5E6D}    2013-10-15 19:30:05:744-0700    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 3 updates.
    {4E73B1C1-5BA2-415D-AB34-92F7AB3DB418}    2013-10-15 19:30:08:753-0700    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    ChkWuDrv    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    {51248882-41AC-4E59-B813-87AD326310AD}    2013-10-15 20:00:05:044-0700    1    183    101    {DBD3B4E9-0357-47DA-8317-D0CF2163BFE6}    501    0    wusa    Success    Content Install    Installation Successful: Windows successfully installed the following update: Hotfix for Windows (KB2661796)
    {FB2B8E5E-442C-4E76-B23D-6A41B4324C9D}    2013-10-16 00:11:39:832-0700    1    148    101    {00000000-0000-0000-0000-000000000000}    0    c8000247    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0xc8000247.
    Lenovo Thinkpad W500, Intel (R), Windows 7, SP1, latest updates as of Oct 15
    (1) Checked Setting,  set to automatic update whenever, even changed to never update, rebooted the OS and changed back to automatic update and rebooted the OS.
    (2) Stopped Windows Update Services, renamed SoftwareDistribution folder and started the window update services and rebooted.
    (3) Ran MS FIXIT
    (4) Ran System File checker Scan (sfc /scannow)
    (5) Ran CHKDSK /F
    (6) Installed "Intel Rapid Storage Technology" drivers from Lenovo site
    (7) Ran Update for Windows 7 for x64-based Systems (KB971033)
    None of the above possible recommended solutions were able to fix the issue yet and now I am getting a message your Window is Not Genuine!
    Any help or guidance is appreciated.
    Solved!
    Go to Solution.

    The Lenovo System Update installed the "Intel Matrix Storage Manager driver 8.9.2.1002" right before the Windows Upgrade got broken. So in the Device Manager under IDE ATA/ATAPI Controllers, I choose Intel ICH9M-E/M SATA AHCI Controller, on the Driver Tab, I choose the option "Roll Back Driver" and after rolling back the driver and restarting the OS, now Windows Update is working like a Champ!
    The End!

  • Windows 7 clients not Reporting Status to WSUS (downstream server) server running Windows 2012 R2

    We have recently upgraded our WSUS server to Windows 2012 R2. Now none of the PCs reporting their status to the WSUS server and not getting updates at all. The PCs are contacting the Server but not reporting their status. Stopped the Firewall on Client and
    Server. BITS and windows updates services are running. 
    Record the system time of the Windows 7 client.
    Reboot the Windows 7 client.
    Run this command from a command prompt: wuauclt /resetauthorization /detectnow.
    Wait =30= minutes.
    Performed the above steps. Please see the updates logs from a client.
    2015-03-16 12:48:44:617
    1040 15a4
    Shutdwn user declined update at shutdown
    2015-03-16 12:48:44:617
    1040 15a4
    AU Successfully wrote event for AU health state:0
    2015-03-16 12:48:44:618
    1040 15a4
    AU AU initiates service shutdown
    2015-03-16 12:48:44:649
    1040 15a4
    AU ###########  AU: Uninitializing Automatic Updates  ###########
    2015-03-16 12:48:46:506
    1040 15a4
    Report CWERReporter finishing event handling. (00000000)
    2015-03-16 12:48:46:584
    1040 15a4
    Service *********
    2015-03-16 12:48:46:584
    1040 15a4
    Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2015-03-16 12:48:46:584
    1040 15a4
    Service *************
    2015-03-16 12:54:23:139
    1024 1060
    Misc ===========  Logging initialized (build: 7.6.7600.320, tz: -0400)  ===========
    2015-03-16 12:54:23:214
    1024 1060
    Misc  = Process: C:\Windows\system32\svchost.exe
    2015-03-16 12:54:23:264
    1024 1060
    Misc  = Module: c:\windows\system32\wuaueng.dll
    2015-03-16 12:54:23:139
    1024 1060
    Service *************
    2015-03-16 12:54:23:264
    1024 1060
    Service ** START **  Service: Service startup
    2015-03-16 12:54:23:265
    1024 1060
    Service *********
    2015-03-16 12:54:24:262
    1024 1060
    Agent  * WU client version 7.6.7600.320
    2015-03-16 12:54:24:263
    1024 1060
    Agent  * Base directory: C:\Windows\SoftwareDistribution
    2015-03-16 12:54:24:272
    1024 1060
    Agent  * Access type: No proxy
    2015-03-16 12:54:24:532
    1024 1060
    Agent  * Network state: Connected
    2015-03-16 12:55:17:235
    1024 1060
    Report CWERReporter::Init succeeded
    2015-03-16 12:55:17:235
    1024 1060
    Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2015-03-16 12:55:17:235
    1024 1060
    Agent  * Prerequisite roots succeeded.
    2015-03-16 12:55:17:235
    1024 1060
    Agent ***********  Agent: Initializing global settings cache  ***********
    2015-03-16 12:55:17:235
    1024 1060
    Agent  * WSUS server: http://ewd-srv-01.resultstel.net:8530
    2015-03-16 12:55:17:235
    1024 1060
    Agent  * WSUS status server: http://ewd-srv-01.resultstel.net:8530
    2015-03-16 12:55:17:235
    1024 1060
    Agent  * Target group: Eastwood
    2015-03-16 12:55:17:235
    1024 1060
    Agent  * Windows Update access disabled: No
    2015-03-16 12:55:17:247
    1024 1060
    DnldMgr Download manager restoring 0 downloads
    2015-03-16 12:55:17:248
    1024 1060
    AU ###########  AU: Initializing Automatic Updates  ###########
    2015-03-16 12:55:17:249
    1024 1060
    AU  # WSUS server: http://ewd-srv-01.resultstel.net:8530
    2015-03-16 12:55:17:249
    1024 1060
    AU  # Detection frequency: 22
    2015-03-16 12:55:17:249
    1024 1060
    AU  # Target group: Eastwood
    2015-03-16 12:55:17:249
    1024 1060
    AU  # Approval type: Scheduled (Policy)
    2015-03-16 12:55:17:249
    1024 1060
    AU  # Scheduled install day/time: Every day at 3:00
    2015-03-16 12:55:17:249
    1024 1060
    AU  # Auto-install minor updates: Yes (Policy)
    2015-03-16 12:55:17:249
    1024 1060
    AU  # Will interact with non-admins (Non-admins are elevated (User preference))
    2015-03-16 12:55:17:249
    1024 1060
    AU  # Will display featured software notifications (User preference)
    2015-03-16 12:55:17:259
    1024 1060
    Agent Switching to hardware-verified ClientId.
    2015-03-16 12:55:17:260
    1024 1060
    AU Setting AU scheduled install time to 2015-03-17 07:00:00
    2015-03-16 12:55:17:402
    1024 1060
    Report ***********  Report: Initializing static reporting data  ***********
    2015-03-16 12:55:17:402
    1024 1060
    Report  * OS Version = 6.1.7601.1.0.65792
    2015-03-16 12:55:17:402
    1024 1060
    Report  * OS Product Type = 0x00000030
    2015-03-16 12:55:17:600
    1024 1060
    Report WARNING: Failed to load reporting information from WMI with hr = 80041002.
    2015-03-16 12:55:17:601
    1024 1060
    Report  * Locale ID = 1033
    2015-03-16 12:55:17:654
    1024 1060
    AU Successfully wrote event for AU health state:0
    2015-03-16 12:55:17:655
    1024 1060
    AU Initializing featured updates
    2015-03-16 12:55:17:655
    1024 1060
    AU Found 0 cached featured updates
    2015-03-16 12:55:17:655
    1024 1060
    AU Successfully wrote event for AU health state:0
    2015-03-16 12:55:17:656
    1024 1060
    AU Successfully wrote event for AU health state:0
    2015-03-16 12:55:17:656
    1024 1060
    AU AU finished delayed initialization
    2015-03-16 12:55:23:261
    1024 1194
    Report CWERReporter finishing event handling. (00000000)
    2015-03-16 12:55:41:121
    1024 1074
    AU Triggering AU detection through DetectNow API
    2015-03-16 12:55:41:122
    1024 1074
    AU Triggering Online detection (non-interactive)
    2015-03-16 12:55:41:193
    1024 1060
    AU #############
    2015-03-16 12:55:41:193
    1024 1060
    AU ## START ##  AU: Search for updates
    2015-03-16 12:55:41:193
    1024 1060
    AU #########
    2015-03-16 12:55:41:218
    1024 1060
    AU <<## SUBMITTED ## AU: Search for updates [CallId = {6382DEFC-F99E-4A2A-B104-48CF9BE2D760}]
    2015-03-16 12:55:41:218
    1024 1194
    Agent *************
    2015-03-16 12:55:41:218
    1024 1194
    Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-03-16 12:55:41:218
    1024 1194
    Agent *********
    2015-03-16 12:55:41:218
    1024 1194
    Agent  * Online = Yes; Ignore download priority = No
    2015-03-16 12:55:41:218
    1024 1194
    Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0
    and DeploymentAction='Uninstallation' and RebootRequired=1"
    2015-03-16 12:55:41:218
    1024 1194
    Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2015-03-16 12:55:41:218
    1024 1194
    Agent  * Search Scope = {Machine}
    2015-03-16 12:55:41:218
    1024 1194
    Setup Checking for agent SelfUpdate
    2015-03-16 12:55:41:219
    1024 1194
    Setup Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320
    2015-03-16 12:55:45:440
    1024 1194
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2015-03-16 12:55:45:893
    1024 1194
    Misc Microsoft signed: NA
    2015-03-16 12:55:45:897
    1024 1194
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPD98D.tmp with dwProvFlags 0x00000080:
    2015-03-16 12:55:45:979
    1024 1194
    Misc Microsoft signed: NA
    2015-03-16 12:55:46:014
    1024 1194
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2015-03-16 12:55:46:019
    1024 1194
    Misc Microsoft signed: NA
    2015-03-16 12:55:46:050
    1024 1194
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2015-03-16 12:55:46:055
    1024 1194
    Misc Microsoft signed: NA
    2015-03-16 12:55:46:093
    1024 1194
    Setup Determining whether a new setup handler needs to be downloaded
    2015-03-16 12:55:46:093
    1024 1194
    Setup SelfUpdate handler is not found.  It will be downloaded
    2015-03-16 12:55:46:093
    1024 1194
    Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.320"
    2015-03-16 12:55:52:237
    1024 1194
    Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.320" is already installed.
    2015-03-16 12:55:52:237
    1024 1194
    Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.320"
    2015-03-16 12:55:53:377
    1024 1194
    Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.320" is already installed.
    2015-03-16 12:55:53:502
    1024 1194
    Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.320"
    2015-03-16 12:55:56:705
    1024 1194
    Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.320" is already installed.
    2015-03-16 12:55:56:896
    1024 1194
    Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2015-03-16 12:56:01:618
    1024 1060
    AU AU received policy change subscription event
    2015-03-16 13:00:00:824
    1024 1194
    PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2015-03-16 13:00:00:824
    1024 1194
    PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://ewd-srv-01.resultstel.net:8530/ClientWebService/client.asmx
    2015-03-16 13:00:01:001
    1024 1194
    PT WARNING: PTError: 0x80041002
    2015-03-16 13:00:01:001
    1024 1194
    PT Initializing simple targeting cookie, clientId = f86ac648-7394-46eb-8f40-eb605f77d86b, target group = Eastwood, DNS name = ewd-wc-420-235.resultstel.net
    2015-03-16 13:00:01:001
    1024 1194
    PT  Server URL = http://ewd-srv-01.resultstel.net:8530/SimpleAuthWebService/SimpleAuth.asmx
    2015-03-16 13:00:01:833
    1024 1194
    Agent WARNING: Failed to evaluate Installed rule, updateId = {F92A18E7-8784-4828-89C9-F80085A422A7}.202, hr = 80041002
    2015-03-16 13:00:02:004
    1024 1194
    Agent WARNING: Failed to evaluate Installed rule, updateId = {C735DBB1-06B4-49F2-815F-97976B4B86A4}.102, hr = 80041002
    2015-03-16 13:00:08:676
    1024 1194
    Agent WARNING: Failed to evaluate Installed rule, updateId = {6A8FE277-1048-48B1-803B-4580C15BBDF1}.100, hr = 80041002
    2015-03-16 13:07:37:795
    1024 1194
    PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2015-03-16 13:07:37:795
    1024 1194
    PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://ewd-srv-01.resultstel.net:8530/ClientWebService/client.asmx
    2015-03-16 13:07:37:988
    1024 1194
    PT WARNING: PTError: 0x80041002
    2015-03-16 13:07:41:893
    1024 1194
    PT WARNING: GetExtendedUpdateInfo failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    2015-03-16 13:07:41:893
    1024 1194
    PT WARNING: SOAP Fault: 0x000190
    2015-03-16 13:07:41:893
    1024 1194
    PT WARNING:     faultstring:Fault occurred
    2015-03-16 13:07:41:893
    1024 1194
    PT WARNING:     ErrorCode:InternalServerError(5)
    2015-03-16 13:07:41:893
    1024 1194
    PT WARNING:     Message:(null)
    2015-03-16 13:07:41:893
    1024 1194
    PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetExtendedUpdateInfo"
    2015-03-16 13:07:41:893
    1024 1194
    PT WARNING:     ID:4cd69d60-d69b-4591-88ad-5687cdda3265
    2015-03-16 13:07:41:893
    1024 1194
    PT WARNING: PTError: 0x8024400e
    2015-03-16 13:07:41:893
    1024 1194
    PT WARNING: GetExtendedUpdateInfo_WithRecovery: 0x8024400e
    2015-03-16 13:07:41:893
    1024 1194
    PT WARNING: Sync of Extended Info: 0x8024400e
    2015-03-16 13:07:41:893
    1024 1194
    PT WARNING: SyncServerUpdatesInternal failed : 0x8024400e
    2015-03-16 13:07:41:914
    1024 1194
    Agent  * WARNING: Exit code = 0x8024400E
    2015-03-16 13:07:41:914
    1024 1194
    Agent *********
    2015-03-16 13:07:41:914
    1024 1194
    Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2015-03-16 13:07:41:914
    1024 1194
    Agent *************
    2015-03-16 13:07:41:914
    1024 1194
    Agent WARNING: WU client failed Searching for update with error 0x8024400e
    2015-03-16 13:07:41:929
    1024 1194
    Report CWERReporter finishing event handling. (00000000)
    2015-03-16 13:07:41:929
    1024 1194
    Report CWERReporter finishing event handling. (00000000)
    2015-03-16 13:07:41:929
    1024 1194
    Report CWERReporter finishing event handling. (00000000)
    2015-03-16 13:07:41:929
    1024 1194
    Report CWERReporter finishing event handling. (00000000)
    2015-03-16 13:07:41:929
    1024 1194
    Report CWERReporter finishing event handling. (00000000)
    2015-03-16 13:07:41:929
    1024 1194
    Report CWERReporter finishing event handling. (00000000)
    2015-03-16 13:07:41:930
    1024 1194
    Report CWERReporter finishing event handling. (00000000)
    2015-03-16 13:07:41:930
    1024 1194
    Report CWERReporter finishing event handling. (00000000)
    2015-03-16 13:07:42:021
    1024 14f4
    AU >>##  RESUMED  ## AU: Search for updates [CallId = {6382DEFC-F99E-4A2A-B104-48CF9BE2D760}]
    2015-03-16 13:07:42:021
    1024 14f4
    AU  # WARNING: Search callback failed, result = 0x8024400E
    2015-03-16 13:07:42:021
    1024 14f4
    AU  # WARNING: Failed to find updates with error code 8024400E
    2015-03-16 13:07:42:021
    1024 14f4
    AU #########
    2015-03-16 13:07:42:021
    1024 14f4
    AU ##  END  ##  AU: Search for updates [CallId = {6382DEFC-F99E-4A2A-B104-48CF9BE2D760}]
    2015-03-16 13:07:42:021
    1024 14f4
    AU #############
    2015-03-16 13:07:42:021
    1024 14f4
    AU Successfully wrote event for AU health state:0
    2015-03-16 13:07:42:021
    1024 14f4
    AU AU setting next detection timeout to 2015-03-16 22:07:42
    2015-03-16 13:07:42:022
    1024 14f4
    AU Setting AU scheduled install time to 2015-03-17 07:00:00
    2015-03-16 13:07:42:022
    1024 14f4
    AU Successfully wrote event for AU health state:0
    2015-03-16 13:07:42:022
    1024 14f4
    AU Successfully wrote event for AU health state:0
    2015-03-16 13:07:46:919
    1024 1194
    Report REPORT EVENT: {CB48FD20-D762-4E5E-8CCA-5C27F3CFA04A}
    2015-03-16 13:07:41:913-0400 1
    148 101
    {00000000-0000-0000-0000-000000000000}
    0 8024400e
    AutomaticUpdates Failure
    Software Synchronization Windows Update Client failed to detect with error 0x8024400e.
    2015-03-16 13:07:47:022
    1024 1194
    Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2015-03-16 13:07:47:022
    1024 1194
    Report WER Report sent: 7.6.7600.320 0x8024400e 00000000-0000-0000-0000-000000000000 Scan 101 Managed
    2015-03-16 13:07:47:022
    1024 1194
    Report CWERReporter finishing event handling. (00000000)
    2015-03-16 13:14:23:923
    1024 1194
    PT WARNING: PTError: 0x80041002
    2015-03-16 13:14:23:923
    1024 1194
    Report Uploading 1 events using cached cookie, reporting URL = http://ewd-srv-01.resultstel.net:8530/ReportingWebService/ReportingWebService.asmx

    Don thank you for the reply.
    But I do have the same issue on the other PCs as well on which WMI is good. And also i pointed the above PC to my primary WSUS server which is running windows 2003 and it reported successfully and downloaded the approved updates.
    please see the below logs from the same PC after pointing to our wsus running on win2003.
    2015-03-17 14:41:08:507
    1020 f1c
    Inv   # Talking to WSUS server = http://atl-wsus-1:8530
    2015-03-17 14:41:08:508
    1020 f1c
    Inv   # Downloading Rule file from = http://atl-wsus-1:8530/Inventory/InventoryRules.cab
    2015-03-17 14:41:08:508
    1020 53c
    AU #########
    2015-03-17 14:41:08:508
    1020 53c
    AU ##  END  ##  AU: Search for updates [CallId = {54490DE2-CF7B-4017-A553-6C8C1532E621}]
    2015-03-17 14:41:08:508
    1020 53c
    AU #############
    2015-03-17 14:41:08:510
    1020 53c
    AU Successfully wrote event for AU health state:0
    2015-03-17 14:41:08:510
    1020 53c
    AU Featured notifications is disabled.
    2015-03-17 14:41:08:510
    1020 53c
    AU AU setting next detection timeout to 2015-03-18 16:13:54
    2015-03-17 14:41:08:510
    1020 53c
    AU Setting AU scheduled install time to 2015-03-18 07:00:00
    2015-03-17 14:41:08:510
    1020 53c
    AU Successfully wrote event for AU health state:0
    2015-03-17 14:41:08:510
    1020 53c
    AU Auto-approving update for download, updateId = {58406504-5709-46CA-BB54-3FE9628545AA}.202, ForUx=0, IsOwnerUx=0, HasDeadline=0, IsMinor=0
    2015-03-17 14:41:08:510
    1020 53c
    AU Auto-approving update for download, updateId = {B9D0F709-E6A7-4383-AFB3-E35FB9CB0AAA}.203, ForUx=0, IsOwnerUx=0, HasDeadline=0, IsMinor=0
    2015-03-17 14:41:08:510
    1020 53c
    AU Auto-approving update for download, updateId = {2CA8E6E8-FC4A-4974-A208-18CDF1D01D86}.203, ForUx=0, IsOwnerUx=0, HasDeadline=0, IsMinor=0
    2015-03-17 14:41:08:510
    1020 53c
    AU Auto-approving update for download, updateId = {6C2547EE-DC7B-4080-8884-A040572C5EC4}.204, ForUx=0, IsOwnerUx=0, HasDeadline=0, IsMinor=0
    2015-03-17 14:41:08:510
    1020 53c
    AU Auto-approving update for download, updateId = {673027F3-841E-4215-88BE-A0BFB456B2B1}.207, ForUx=0, IsOwnerUx=0, HasDeadline=0, IsMinor=0
    2015-03-17 14:41:08:510
    1020 53c
    AU Auto-approved 5 update(s) for download (NOT for Ux)
    2015-03-17 14:41:08:510
    1020 53c
    AU #############
    2015-03-17 14:41:08:511
    1020 53c
    AU ## START ##  AU: Download updates
    2015-03-17 14:41:08:511
    1020 53c
    AU #########
    2015-03-17 14:41:08:511
    1020 53c
    AU   # Approved updates = 5
    2015-03-17 14:41:08:512
    1020 53c
    AU AU initiated download, updateId = {58406504-5709-46CA-BB54-3FE9628545AA}.202, callId = {F3389077-03F0-4625-83EF-CAAEBA8ED147}
    2015-03-17 14:41:08:513
    1020 53c
    AU AU initiated download, updateId = {B9D0F709-E6A7-4383-AFB3-E35FB9CB0AAA}.203, callId = {B94BF4E5-5709-4D22-924A-5C5B8D4712C9}
    2015-03-17 14:41:08:514
    1020 53c
    AU AU initiated download, updateId = {2CA8E6E8-FC4A-4974-A208-18CDF1D01D86}.203, callId = {D330B2E0-CA38-4ED9-894A-36717C01F09A}
    2015-03-17 14:41:08:515
    1020 53c
    AU AU initiated download, updateId = {6C2547EE-DC7B-4080-8884-A040572C5EC4}.204, callId = {B6B35AC2-9BC1-4CFA-8421-D666C79464AD}
    2015-03-17 14:41:08:516
    1020 53c
    AU AU initiated download, updateId = {673027F3-841E-4215-88BE-A0BFB456B2B1}.207, callId = {F0D00A6F-36BC-4680-9BE4-4005742A2C93}
    2015-03-17 14:41:08:516
    1020 53c
    AU Setting AU scheduled install time to 2015-03-18 07:00:00
    2015-03-17 14:41:08:516
    1020 53c
    AU Successfully wrote event for AU health state:0
    2015-03-17 14:41:08:516
    1020 53c
    AU AU setting pending client directive to 'Download Progress'
    2015-03-17 14:41:08:518
    1020 53c
    AU Successfully wrote event for AU health state:0
    2015-03-17 14:41:08:518
    1020 53c
    AU   # Pending download calls = 5
    2015-03-17 14:41:08:518
    1020 53c
    AU <<## SUBMITTED ## AU: Download updates
    2015-03-17 14:41:08:520
    1020 53c
    AU Successfully wrote event for AU health state:0
    2015-03-17 14:41:08:964
    1020 f1c
    Misc Validating signature for C:\Windows\SoftwareDistribution\Inventory\InventoryRule\InventoryRules.cab with dwProvFlags 0x00000080:
    2015-03-17 14:41:08:976
    1020 f1c
    Misc  Microsoft signed: NA
    2015-03-17 14:41:08:993
    1020 f1c
    Inv   # Inventory Rule id = 8226C3A1-70D4-4848-B441-1555AC820A23, version = 1.0
    2015-03-17 14:41:09:022
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:086
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:118
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:150
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:182
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:214
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:246
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:278
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:310
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:342
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:374
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:406
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:438
    1020 f1c
    Inv WARNING: Inventory: Failed to connect to the root\cimv2 namespace 0x80041002
    2015-03-17 14:41:09:471
    1020 f1c
    PT WARNING: PTError: 0x80041002
    2015-03-17 14:41:10:590
    1020 f1c
    Inv #########
    2015-03-17 14:41:10:590
    1020 f1c
    Inv ##  END  ##  Inv: Inventory Collection
    2015-03-17 14:41:10:590
    1020 f1c
    Inv #############
    2015-03-17 14:41:10:592
    1020 f1c
    DnldMgr *************
    2015-03-17 14:41:10:592
    1020 f1c
    DnldMgr ** START **  DnldMgr: Downloading updates [CallerId = AutomaticUpdates]
    2015-03-17 14:41:10:592
    1020 f1c
    DnldMgr *********
    2015-03-17 14:41:10:592
    1020 f1c
    DnldMgr   * Call ID = {F3389077-03F0-4625-83EF-CAAEBA8ED147}
    2015-03-17 14:41:10:592
    1020 f1c
    DnldMgr   * Priority = 2, Interactive = 0, Owner is system = 1, Explicit proxy = 0, Proxy session id = -1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2015-03-17 14:41:10:592
    1020 f1c
    DnldMgr   * Updates to download = 1
    2015-03-17 14:41:10:592
    1020 f1c
    Agent   *   Title = Security Update for Windows 7 (KB3029944)
    2015-03-17 14:41:10:592
    1020 f1c
    Agent   *   UpdateId = {58406504-5709-46CA-BB54-3FE9628545AA}.202
    2015-03-17 14:41:10:592
    1020 f1c
    Agent   *     Bundles 1 updates:
    2015-03-17 14:41:10:592
    1020 f1c
    Agent   *       {CF9A0A9F-EA32-4B84-8B11-647F8DE3432C}.202
    2015-03-17 14:41:10:598
    1020 f1c
    DnldMgr ***********  DnldMgr: New download job [UpdateId = {CF9A0A9F-EA32-4B84-8B11-647F8DE3432C}.202]  ***********
    2015-03-17 14:41:10:599
    1020 f1c
    DnldMgr   * Queueing update for download handler request generation.
    2015-03-17 14:41:10:599
    1020 f1c
    DnldMgr Generating download request for update {CF9A0A9F-EA32-4B84-8B11-647F8DE3432C}.202
    2015-03-17 14:41:13:863
    1020 f1c
    Handler Generating request for CBS update CF9A0A9F-EA32-4B84-8B11-647F8DE3432C in sandbox C:\Windows\SoftwareDistribution\Download\4fa5441bcc144c4a7917304858841f6b
    2015-03-17 14:41:13:863
    1020 f1c
    Handler Selected payload type is ptExpress
    2015-03-17 14:41:13:863
    1020 f1c
    Handler Detected download state is dsStart
    2015-03-17 14:41:13:863
    1020 f1c
    Handler Adding windows6.1-kb3029944-x86-express.cab (entire file) to request list.
    2015-03-17 14:41:13:864
    1020 f1c
    Handler Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0 
    2015-03-17 14:41:13:864
    1020 f1c
    DnldMgr ***********  DnldMgr: New download job [UpdateId = {CF9A0A9F-EA32-4B84-8B11-647F8DE3432C}.202]  ***********
    2015-03-17 14:41:16:436
    1020 f1c
    DnldMgr   * BITS job initialized, JobId = {675985CD-3133-4157-9D02-06CC33C29C49}
    2015-03-17 14:41:16:473
    1020 f1c
    DnldMgr   * Downloading from http://wsus.ds.download.windowsupdate.com/c/msdownload/update/software/secu/2015/01/windows6.1-kb3029944-x86-express_0c21886fd0931285b2d3a29773d3673c947f60b3.cab to C:\Windows\SoftwareDistribution\Download\4fa5441bcc144c4a7917304858841f6b\windows6.1-kb3029944-x86-express.cab
    (full file).
    2015-03-17 14:41:16:644
    1020 f1c
    Agent *********
    2015-03-17 14:41:16:644
    1020 f1c
    Agent **  END  **  Agent: Downloading updates [CallerId = AutomaticUpdates]
    2015-03-17 14:41:16:644
    1020 f1c
    Agent *************
    2015-03-17 14:41:16:645
    1020 f1c
    DnldMgr *************
    2015-03-17 14:41:16:645
    1020 f1c
    DnldMgr ** START **  DnldMgr: Downloading updates [CallerId = AutomaticUpdates]
    2015-03-17 14:41:16:645
    1020 f1c
    DnldMgr *********
    2015-03-17 14:41:16:645
    1020 f1c
    DnldMgr   * Call ID = {B94BF4E5-5709-4D22-924A-5C5B8D4712C9}
    2015-03-17 14:41:16:645
    1020 f1c
    DnldMgr   * Priority = 2, Interactive = 0, Owner is system = 1, Explicit proxy = 0, Proxy session id = -1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2015-03-17 14:41:16:645
    1020 f1c
    DnldMgr   * Updates to download = 1
    2015-03-17 14:41:16:645
    1020 f1c
    Agent   *   Title = Security Update for Windows 7 (KB3004361)
    2015-03-17 14:41:16:645
    1020 f1c
    Agent   *   UpdateId = {B9D0F709-E6A7-4383-AFB3-E35FB9CB0AAA}.203
    2015-03-17 14:41:16:645
    1020 f1c
    Agent   *     Bundles 1 updates:
    2015-03-17 14:41:16:645
    1020 f1c
    Agent   *       {151B27A0-4EA8-428F-BE06-C90A3CF0C2CA}.203
    2015-03-17 14:41:16:648
    1020 f1c
    DnldMgr ***********  DnldMgr: New download job [UpdateId = {151B27A0-4EA8-428F-BE06-C90A3CF0C2CA}.203]  ***********
    2015-03-17 14:41:16:649
    1020 f1c
    DnldMgr   * Queueing update for download handler request generation.
    2015-03-17 14:41:16:649
    1020 f1c
    DnldMgr Generating download request for update {151B27A0-4EA8-428F-BE06-C90A3CF0C2CA}.203
    2015-03-17 14:41:16:678
    1020 f1c
    Handler Generating request for CBS update 151B27A0-4EA8-428F-BE06-C90A3CF0C2CA in sandbox C:\Windows\SoftwareDistribution\Download\963019da42f4a0388fdc4337be401b25
    2015-03-17 14:41:16:678
    1020 f1c
    Handler Selected payload type is ptExpress
    2015-03-17 14:41:16:678
    1020 f1c
    Handler Detected download state is dsStart
    2015-03-17 14:41:16:678
    1020 f1c
    Handler Adding windows6.1-kb3004361-x86-express.cab (entire file) to request list.
    2015-03-17 14:41:16:687
    1020 f1c
    Handler Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0 
    2015-03-17 14:41:16:687
    1020 f1c
    DnldMgr ***********  DnldMgr: New download job [UpdateId = {151B27A0-4EA8-428F-BE06-C90A3CF0C2CA}.203]  ***********
    2015-03-17 14:41:16:732
    1020 f1c
    DnldMgr   * BITS job initialized, JobId = {27F85F04-0E56-4BFA-93E3-4D6BCB3ECB4F}
    2015-03-17 14:41:16:758
    1020 f1c
    DnldMgr   * Downloading from http://wsus.ds.download.windowsupdate.com/c/msdownload/update/software/secu/2014/12/windows6.1-kb3004361-x86-express_47f37958063afd2521ca42de8904b55d1aa85b89.cab to C:\Windows\SoftwareDistribution\Download\963019da42f4a0388fdc4337be401b25\windows6.1-kb3004361-x86-express.cab
    (full file).
    2015-03-17 14:41:16:809
    1020 f1c
    Agent *********
    2015-03-17 14:41:16:809
    1020 f1c
    Agent **  END  **  Agent: Downloading updates [CallerId = AutomaticUpdates]
    2015-03-17 14:41:16:809
    1020 f1c
    Agent *************
    2015-03-17 14:41:16:811
    1020 f1c
    DnldMgr *************
    2015-03-17 14:41:16:811
    1020 f1c
    DnldMgr ** START **  DnldMgr: Downloading updates [CallerId = AutomaticUpdates]
    2015-03-17 14:41:16:811
    1020 f1c
    DnldMgr *********
    2015-03-17 14:41:16:811
    1020 f1c
    DnldMgr   * Call ID = {D330B2E0-CA38-4ED9-894A-36717C01F09A}
    2015-03-17 14:41:16:811
    1020 f1c
    DnldMgr   * Priority = 2, Interactive = 0, Owner is system = 1, Explicit proxy = 0, Proxy session id = -1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2015-03-17 14:41:16:811
    1020 f1c
    DnldMgr   * Updates to download = 1
    2015-03-17 14:41:16:811
    1020 f1c
    Agent   *   Title = Security Update for Windows 7 (KB3031432)
    2015-03-17 14:41:16:811
    1020 f1c
    Agent   *   UpdateId = {2CA8E6E8-FC4A-4974-A208-18CDF1D01D86}.203
    2015-03-17 14:41:16:811
    1020 f1c
    Agent   *     Bundles 1 updates:
    2015-03-17 14:41:16:811
    1020 f1c
    Agent   *       {EE556F37-7EAC-42B3-BD29-653F98E6E364}.203
    2015-03-17 14:41:16:814
    1020 f1c
    DnldMgr ***********  DnldMgr: New download job [UpdateId = {EE556F37-7EAC-42B3-BD29-653F98E6E364}.203]  ***********
    2015-03-17 14:41:16:815
    1020 f1c
    DnldMgr   * Queueing update for download handler request generation.
    2015-03-17 14:41:16:815
    1020 f1c
    DnldMgr Generating download request for update {EE556F37-7EAC-42B3-BD29-653F98E6E364}.203
    2015-03-17 14:41:16:843
    1020 f1c
    Handler Generating request for CBS update EE556F37-7EAC-42B3-BD29-653F98E6E364 in sandbox C:\Windows\SoftwareDistribution\Download\7db602a9c625e53b175ecb83170441ba
    2015-03-17 14:41:16:843
    1020 f1c
    Handler Selected payload type is ptExpress
    2015-03-17 14:41:16:843
    1020 f1c
    Handler Detected download state is dsStart
    2015-03-17 14:41:16:843
    1020 f1c
    Handler Adding windows6.1-kb3031432-x86-express.cab (entire file) to request list.
    2015-03-17 14:41:16:844
    1020 f1c
    Handler Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0 
    2015-03-17 14:41:16:845
    1020 f1c
    DnldMgr ***********  DnldMgr: New download job [UpdateId = {EE556F37-7EAC-42B3-BD29-653F98E6E364}.203]  ***********
    2015-03-17 14:41:16:881
    1020 f1c
    DnldMgr   * BITS job initialized, JobId = {6C5B3B60-DB8B-4B6F-9E40-D99CA43B366D}
    2015-03-17 14:41:16:906
    1020 f1c
    DnldMgr   * Downloading from http://wsus.ds.download.windowsupdate.com/c/msdownload/update/software/secu/2015/01/windows6.1-kb3031432-x86-express_fb5326e90facfe6de39cf44fc4ed5ec630968ba5.cab to C:\Windows\SoftwareDistribution\Download\7db602a9c625e53b175ecb83170441ba\windows6.1-kb3031432-x86-express.cab
    (full file).

  • Office 2013 windows 'pop-under' when run as remote apps on Server 2008R2 from Windows 7 clients

    We have an environment with Windows 7 clients running Office 2013 via RDS on Windows Server 2008R2.
    When users double click emails from Outlook, they 'pop-under', forcing the user to relocate the window which has fallen behind the application's primary window, leaving behind a slight redraw of what is supposed to be the pop-up window. Users also experience
    difficulty opening application menu/help items and any other dialogue boxes in any/all of the other Office 2013 apps we've deployed via RDS.
    This issue persists only on Win7 PCs (WinXP does not exhibit this behaviour). The RDP clients range from 6.2.92 to 6.1.7601
    We have applied the hot-fixes applicable to all of the following KB articles:
    - KB983533 (failed / update not applicable)
    - KB2384602 (failed / update not applicable)
    - KB2614136 (failed / update not applicable)
    - KB2580346 (Installed successfully, but issue unresolved)
    - KB2522762 (Installed successfully, but issue unresolved)
    - KB2538047 (Installed successfully, but issue unresolved)
    - KB2604066 (Installed successfully, but issue unresolved)
    - KB2705427 (Installed successfully, but issue unresolved)
    - KB2682814 (Installed successfully, but issue unresolved)

    Hi,
    Please give the new Remote Desktop Client 8.1 for Windows 7 a try when it is re-released (it was removed temporarily due to an issue with smart cards).  It has fixes related to z-order issues, which
    may correct the problem you are seeing.
    Update for RemoteApp and Desktop Connections features is available for Windows
    http://support.microsoft.com/KB/2830477
    Thanks.
    -TP

  • View change in the middle of sessions to Windows 7 clients with OneDrive

    Some Windows 7 clients habe reported that the view changes in the middle of sessions to Windows 7 clients with OneDrive.
    For example they have been able to see image pictures as normal in the beginning of sessions and then suddenly only image names !

    Hi  yourDragonXi,
    Is it a desktop One drive or a web browser Onedrive content? According to your description, the should be a Sync process when you open the images, besides a screenshot will be helpful to find the explanation.
    Thanks and Regards
    Wade Liu
    TechNet Community Support

  • Error while connecting to SAP Server from Windows XP Client.

    Hi,
    I am facing the problem while i am trying to connect my Windows XP Clients( With Service Pack 3, DI-API Installed and Microsoft SQL Server Native Client Installed) to SAP server i got follwoing Error.
    Connection Failed :
    SQL State : '08001'
    SQL Server Error : 233
    [Microsoft][SQL Native Client]Named Pipe Provider Could not open the connection SQL Server [233].
    Connection Failed :
    SQL State : "HYT00"
    SQL Server Error : 0
    [Microsoft][SQL Native Client]Login Timeout Expired
    Connection Failed:
    SQL State :'08001'
    SQL Server Error : 233
    [Microsoft][SQL Native Client]An Error has occured while establishing new connection to the server.
    When connecting SQL Server 2005, this failure may caused by the fact that under the default setting SQL Server does not allow remote connection.
    Regards,
    Arpit Shah

    Hi Arpit,
    Solution of Error in starting B1 after installation should help here too.
    Kind regards
    Mario
    SAP Business One Forums team

  • Windows 7 client can't connect to Server 2008 R2 Print Server VM (ESXi 5.5)

    I have an issue today that is driving me bonkers.
    I recently came on-board to a company in my area as the system administrator and this network has everything and the kitchen sink wrong with the network layout, probably the worst I've seen and I'm slowly but surely fixing it day by day.....
    Well today I decided I was going to spin up another VM from a template and make a Print Server, seems harmless right? --- I thought so too, added all of the printers to the server and did test pages, all was dandy, but then I tried to add the printers to
    clients and other server and the real fun has begun, I'm truly perplexed now...
    I added a VM to my esxi 5.5 cluster at work that is a 2008 R2 server with only print management on it. I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via
    DNS. I can test printers directly from the print server successfully printing out test pages however whenever I try to map printers you know from the directory in 'devices and printers' from any of the Windows 7 clients or any of the other 2003/2008 servers
    I get the classical "Windows cannot connect please check the network connection and make sure sure the printer is turned on". I disabled the windows firewall and I made the point to print GPO set to disabled and still no luck. Again I can print to
    all of the printers internally inside of the VM (so I know it communicating to all of the printers), I just can't connect to the printers listed in the directory on any of external desktop/client, it's like so annoying. spent about 6 hours until my brain just
    couldn't think anymore, was about to go BS on the VM.
    The only thing I can think of, as I was driving home, is that there is a GPO on one of the DC that has a desginated print server policy set. But prior to last week the forest leve was 2000 and now it's 2003. I just don't know Server 2000 enough to know if GPO's
    worked in the same way they do in 2003.
    Right now printers are connected to other servers in a ad hoc mentality it seems, there has never been a true print server.
    Anyone ever have this problem before?
    I'm truly puzzled...

    Hi Mid.Hudson-IT,
    Before we begin ,we should ensure we have configured the printer server correctly .
    Here is a link for reference of configuring the printer server .
    Print server role: Configuring a print server
    https://technet.microsoft.com/en-us/library/cc775791(v=ws.10).aspx
    "I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via DNS"
    From this sentence ,I can`t figure out whether you have tried to ping the server both with the IP adress and name adress from the client ?
    If we can ping the print server from the client,we can ensure the connection to the printer server is good .
    Then we can try to install the printer driver directly to have a check .In the adress bar of Windows Explorer ,input "\\server name \the printer name"
    If we cannot ping the print server ,we should troubleshoot the network issue firstly.
    We also can check the event viewer for more information to troubleshoot this issue .
    Best regards

  • Why is RV082 PPTP no longer working with Windows 7 clients?

    RV082 Firmware Version 2.0.2.01-tmRV082 Firmware Version 2.0.2.01-tm
    I have successfully used the built-in Windows 7 VPN (PPTP) to connection to an RV082 (Firmware 2.0.2.01-tm) many times in the past. The Windows 7 client stopped working recently, now producing "error 691: the remote connection was denied because the user name and password combination is not recognized." I have the same problem from two different Windows 7 clients and Windows XP clients still work.

    Hi Tad,
    since this question is about a product in the Cisco Small Business / Linksys range, I suggest you move it to the community, where you will have a better chance of getting expert advice.
    best regards,
    Herbert
    Cisco Moderator

Maybe you are looking for