Windows 2008 R2 server unable to browse UNC shares

Hi All..
I appreciate if anyone could assist with pointing me in the right direction. I have a 2008 R2 server which operates as our SCCM server. For some reason, in the last few days has lost the ability to browse UNC shares from itself, to any other host on the
network or it's own local shares. 
DNS resolution and WINS both are working correctly. The affected server can ping any other host on our network, via IP and host alias or FQDN.
For purposes of trying to rule the problem out, I have tried combinations of disabling all WINS and NetBIOS settings on the server, simply in an attempt to see if the issue was DNS, WINS or NetBIOS related. In all cases, attempting to browse another host
using the UNC share , i.e. <\\hostname\sharename> or <\\host-ip\sharename>
Doing a net view \\localhost or net view \\remote-server returns the correct list of shares. When trying to map a drive via net use x: \\remote-server\share I get;
System error 67 has occurred.
The network name cannot be found.
And when browsing via Windows explorer I get the message
Error Code: 0x90070043
The network name cannot be found
The same results happen for netbios name, FQDN and IP address.
From the other side, every other host that I've tested can access shares on the the affected server. (I've tested XPSP3, WIN7 64-bit, WIN2003 32-bit, WIN2008 & WIN2008R2 hosts)
I have also tried a "nbtstat -a <remote-hostname>" and "nbtstat -a <remote-host-ip>" and the information returned corresponds with the WINS server details.
I have also tried an "nbtstat -S 2" whlist attempting to open a UNC share, but no corresponding entries appear while attempting to UNC browse.
I should point out that the error notification (of the failure to connect) is instantaneous as if the server isn't even attempting to try going remotely. (i.e. no timeout) Which leads me to thinking there's a configuration setting somewhere that's causing
this problem??
There are no 3rd party firewalls installed, the windows firewall service is started by default but all the profiles for the firewall are turned off. We have tried setting firewall to on and allow all traffic, but the problem remains. All ports are open inbound
and outbound as I can telnet to ports 139 and 445 of other servers from this server. I have also tried enabling all netbios rules that were disabled on the windows firewall (in order to rule out any potential conflict).
The server was running Sophos 9.7 AV, I have tested completely removing the AV software from the server in order to rule out any potential conflict. This did not resolve the issue.
I have also verified that it's not down to a disabled computer domain account.
The servers are only operating IPv4, and obviously have File and Print services enabled, and client for Microsoft Networks.
The AD domain was upgraded, many weeks prior, from an AD2003 domain to an AD2008, and the server was operating as expected until I discovered that the UNC shares were no longer working on this affected host.
While it is not affecting config manager clients connecting to the server, is has an impact if a SCCM task sequence needs to retrieve data from a UNC share.
As mentioned the server is a 2008 R2 box, it's a virtual machine operating on ESXi 4.1U1. The OS is fully patched and and VMware tools are up to date. The server is a member server of our AD domain. We have many other similarly configured 2008 R2 servers
operating on the same ESXi host; in fact we have 2008R2 hosts acting as SCOM, SCOM RMS and SQL2008 R2 servers. All these servers are operating on the same IP subnet. All of these servers are operating with the same network configuration (with the exception
of different static IP addresses).
We have tried removing and reinstalling the VMware tools, and removing and reinstalling the Intel NIC, this hasn't made any difference either. I have also tried changing from the Intel NIC to a VMware VMXnet NIC. This has not made a difference.
Any suggestions would be really be greatly appreciated as I've not been able to solve this to date..I will gladly supply any additional info if it can help anyone in the future, should they come across this problem.
DE
-Dropped everything to work on the problem :D

Hi,
Just giving this thread a bit of a bump on this thread as I'm still trying to figure this one out..
I did resort to restoring from backup, to get my server working, but I'm encountering the issue on another 2008 R2 box, which is not good. So any suggestions you can think of would be appreciated. I think that this issue is more of a network protocol related
nature, rather than application issue.. I'd appreciate if anyone could suggest how to proceed further on this one..
Below are two snippets of wireshark captures, one is between the affected 2008 R2 host & a windows 2003 server, and the second one is between a working 2008 R2 host and the same 2003 server (used in the first example). In the test examples, I am simply
doing a start -> run; then typing \\2003servername\ and pressing enter. Below is the network traffic between the two hosts, after I hit return;
TEST#1 - Affected server (192.168.125.33), target remote server (192.168.125.6) - Affected server is 2008 R2, remote server is 2003 R2 Enterrpise 64-bit SP2
465 6.020857 192.168.125.33 192.168.125.6 TCP 52716 > microsoft-ds [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=8 SACK_PERM=1
474 6.021445 192.168.125.6 192.168.125.33 TCP microsoft-ds > 52716 [SYN, ACK] Seq=0 Ack=1 Win=16384 Len=0 MSS=1460 WS=0 SACK_PERM=1
475 6.021479 192.168.125.33 192.168.125.6 TCP 52716 > microsoft-ds [ACK] Seq=1 Ack=1 Win=65536 Len=0
476 6.021533 192.168.125.33 192.168.125.6 SMB Negotiate Protocol Request
481 6.022013 192.168.125.6 192.168.125.33 SMB Negotiate Protocol Response
482 6.022596 192.168.125.33 192.168.125.6 TCP [TCP segment of a reassembled PDU]
483 6.022601 192.168.125.33 192.168.125.6 SMB Session Setup AndX Request
484 6.022809 192.168.125.6 192.168.125.33 TCP microsoft-ds > 52716 [ACK] Seq=182 Ack=2356 Win=65535 Len=0
485 6.023891 192.168.125.6 192.168.125.33 SMB Session Setup AndX Response
486 6.024115 192.168.125.33 192.168.125.6 SMB Tree Connect AndX Request, Path: \\2003servername\IPC$
487 6.024321 192.168.125.6 192.168.125.33 SMB Tree Connect AndX Response
488 6.024455 192.168.125.33 192.168.125.6 SMB Trans2 Request, GET_DFS_REFERRAL, File: \2003servername\.
489 6.024653 192.168.125.6 192.168.125.33 SMB Trans2 Response, GET_DFS_REFERRAL, Error: STATUS_NO_SUCH_DEVICE
490 6.024821 192.168.125.33 192.168.125.6 SMB Tree Connect AndX Request, Path: \\2003servername\.
491 6.024995 192.168.125.6 192.168.125.33 SMB Tree Connect AndX Response, Error: STATUS_BAD_NETWORK_NAME
492 6.025136 192.168.125.33 192.168.125.6 SMB Tree Connect AndX Request, Path: \\2003servername\.
493 6.025313 192.168.125.6 192.168.125.33 SMB Tree Connect AndX Response, Error: STATUS_BAD_NETWORK_NAME
516 6.221682 192.168.125.33 192.168.125.6 TCP 52716 > microsoft-ds [ACK] Seq=2700 Ack=709 Win=64768 Len=0
I can reproduce the same network traffic against 2008 R2 host, only the SMB traffic will show as SMBV2
TEST#2 - To compare this, I ran the same test (above) using a working 2008 R2 host, against the same 2003 remote server. You will see that it is considerably more network traffic, than the above
failed example.
321 5.277323 192.168.125.14 192.168.125.6 TCP 64518 > microsoft-ds [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=8 SACK_PERM=1
322 5.277482 192.168.125.6 192.168.125.14 TCP microsoft-ds > 64518 [SYN, ACK] Seq=0 Ack=1 Win=16384 Len=0 MSS=1460 WS=0 SACK_PERM=1
323 5.277509 192.168.125.14 192.168.125.6 TCP 64518 > microsoft-ds [ACK] Seq=1 Ack=1 Win=65536 Len=0
324 5.277575 192.168.125.14 192.168.125.6 SMB Negotiate Protocol Request
325 5.277978 192.168.125.6 192.168.125.14 SMB Negotiate Protocol Response
326 5.278537 192.168.125.14 192.168.125.6 SMB Session Setup AndX Request
327 5.278758 192.168.125.6 192.168.125.14 TCP microsoft-ds > 64518 [ACK] Seq=182 Ack=2358 Win=65535 Len=0
328 5.279557 192.168.125.6 192.168.125.14 SMB Session Setup AndX Response
329 5.279803 192.168.125.14 192.168.125.6 SMB Tree Connect AndX Request, Path: \\2003servername\IPC$
330 5.279992 192.168.125.6 192.168.125.14 SMB Tree Connect AndX Response
331 5.280129 192.168.125.14 192.168.125.6 SMB Trans2 Request, GET_DFS_REFERRAL, File: \2003servername\.
332 5.280316 192.168.125.6 192.168.125.14 SMB Trans2 Response, GET_DFS_REFERRAL, Error: STATUS_NO_SUCH_DEVICE
333 5.280471 192.168.125.14 192.168.125.6 SMB Tree Connect AndX Request, Path: \\2003servername\.
334 5.280607 192.168.125.6 192.168.125.14 SMB Tree Connect AndX Response, Error: STATUS_BAD_NETWORK_NAME
335 5.280742 192.168.125.14 192.168.125.6 SMB Tree Connect AndX Request, Path: \\2003servername\.
336 5.280877 192.168.125.6 192.168.125.14 SMB Tree Connect AndX Response, Error: STATUS_BAD_NETWORK_NAME
337 5.281675 192.168.125.14 192.168.125.6 SMB NT Create AndX Request, FID: 0xc006, Path: \wkssvc
338 5.281933 192.168.125.6 192.168.125.14 SMB NT Create AndX Response, FID: 0xc006
339 5.282084 192.168.125.14 192.168.125.6 DCERPC Bind: call_id: 2, 3 context items, 1st WKSSVC V1.0
340 5.282252 192.168.125.6 192.168.125.14 SMB Write AndX Response, FID: 0xc006, 160 bytes
341 5.282354 192.168.125.14 192.168.125.6 SMB Read AndX Request, FID: 0xc006, 1024 bytes at offset 0
342 5.282523 192.168.125.6 192.168.125.14 DCERPC Bind_ack: call_id: 2 Unknown result (3), reason: Abstract syntax not supported
343 5.282633 192.168.125.14 192.168.125.6 WKSSVC NetWkstaGetInfo request Level:100
344 5.282907 192.168.125.6 192.168.125.14 WKSSVC NetWkstaGetInfo response
345 5.283036 192.168.125.14 192.168.125.6 SMB Close Request, FID: 0xc006
346 5.283195 192.168.125.6 192.168.125.14 SMB Close Response, FID: 0xc006
347 5.283449 192.168.125.14 192.168.125.6 SMB NT Create AndX Request, FID: 0xc00a, Path: \srvsvc
348 5.283666 192.168.125.6 192.168.125.14 SMB NT Create AndX Response, FID: 0xc00a]
349 5.283793 192.168.125.14 192.168.125.6 DCERPC Bind: call_id: 2, 3 context items, 1st SRVSVC V3.0
350 5.283957 192.168.125.6 192.168.125.14 SMB Write AndX Response, FID: 0xc00a, 160 bytes
351 5.284059 192.168.125.14 192.168.125.6 SMB Read AndX Request, FID: 0xc00a, 1024 bytes at offset 0
352 5.284210 192.168.125.6 192.168.125.14 DCERPC Bind_ack: call_id: 2 Unknown result (3), reason: Abstract syntax not supported
353 5.284302 192.168.125.14 192.168.125.6 SRVSVC NetSrvGetInfo request
354 5.284527 192.168.125.6 192.168.125.14 SRVSVC NetSrvGetInfo response
355 5.284638 192.168.125.14 192.168.125.6 SMB Close Request, FID: 0xc00a
356 5.284790 192.168.125.6 192.168.125.14 SMB Close Response, FID: 0xc00a
358 5.339168 192.168.125.14 192.168.125.6 SMB NT Create AndX Request, FID: 0x000e, Path: \srvsvc
359 5.339549 192.168.125.6 192.168.125.14 SMB NT Create AndX Response, FID: 0x000e
360 5.339689 192.168.125.14 192.168.125.6 DCERPC Bind: call_id: 2, 3 context items, 1st SRVSVC V3.0
361 5.339839 192.168.125.6 192.168.125.14 SMB Write AndX Response, FID: 0x000e, 160 bytes
362 5.339905 192.168.125.14 192.168.125.6 SMB Read AndX Request, FID: 0x000e, 1024 bytes at offset 0
363 5.340056 192.168.125.6 192.168.125.14 DCERPC Bind_ack: call_id: 2 Unknown result (3), reason: Abstract syntax not supported
364 5.340130 192.168.125.14 192.168.125.6 SRVSVC NetShareEnumAll request
365 5.340276 192.168.125.6 192.168.125.14 SMB Write AndX Response, FID: 0x000e, 92 bytes
366 5.340336 192.168.125.14 192.168.125.6 SMB Read AndX Request, FID: 0x000e, 1024 bytes at offset 0
367 5.340482 192.168.125.6 192.168.125.14 SMB Read AndX Response, FID: 0x000e, 1024 bytes
368 5.340547 192.168.125.14 192.168.125.6 SMB Read AndX Request, FID: 0x000e, 2480 bytes at offset 0
369 5.340722 192.168.125.6 192.168.125.14 TCP [TCP segment of a reassembled PDU]
370 5.341016 192.168.125.6 192.168.125.14 SRVSVC NetShareEnumAll response
371 5.341045 192.168.125.14 192.168.125.6 TCP 64518 > microsoft-ds [ACK] Seq=4575 Ack=5925 Win=65536 Len=0
374 5.341538 192.168.125.14 192.168.125.6 SMB Close Request, FID: 0x000e
375 5.341693 192.168.125.6 192.168.125.14 SMB Close Response, FID: 0x000e
401 5.603988 192.168.125.14 192.168.125.6 TCP 64518 > microsoft-ds [ACK] Seq=4620 Ack=5964 Win=65536 Len=0
Again, I can repeat the same test against a 2008 R2 server, and I will get the same output, except the SMB traffic will be SMBV2
It appears to me that the issue is protocol related, as you can see in test#1 between the second-last and the last line of network traffic, it jumps from "STATUS_BAD_NETWORK_NAME" to a TCP/IP [ACK] response. Yet in
test#2 you can see that after line 336 (shown below), you can see it calls "wkssvc", which I'm assuming is the workstation service.. which we don't see at the first (failed) test..
337 5.281675 192.168.125.14 192.168.125.6 SMB NT Create AndX Request, FID: 0xc006, Path: \wkssvc
338 5.281933 192.168.125.6 192.168.125.14 SMB NT Create AndX Response, FID: 0xc006
339 5.282084 192.168.125.14 192.168.125.6 DCERPC Bind: call_id: 2, 3 context items, 1st WKSSVC V1.0
If there's anyone out there that can assit, it really would be much appreciated.
Thanks in advance..
-Dropped everything to work on the problem :D

Similar Messages

  • Unable to login to Report Service on Windows 2008 R2 server

    I have reporting services installed on a Windows 2008 R2 server, When I make and RDP connection to the server and go to http://servername/Reports everything works fine. When I try to connect from another client to the web service, it asks for username and
    password. it fails 3 times and the shows a blank page.
    When I see the Event Viewer in the server (Windows Logs --> Security, I can see an Audit Failure:
    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          9/4/2014 11:46:25 AM
    Event ID:      4625
    Task Category: Logon
    Level:         Information
    Keywords:      Audit Failure
    User:          N/A
    Computer:      MI-SWACO-DB.houston.livequest.net
    Description:
    An account failed to log on.
    Subject:
        Security ID:        NULL SID
        Account Name:        -
        Account Domain:        -
        Logon ID:        0x0
    Logon Type:            3
    Account For Which Logon Failed:
        Security ID:        NULL SID
        Account Name:        Administrator
        Account Domain:        HOUSTONLQ
    Failure Information:
        Failure Reason:        An Error occured during Logon.
        Status:            0xc000035b
        Sub Status:        0x0
    Process Information:
        Caller Process ID:    0x0
        Caller Process Name:    -
    Network Information:
        Workstation Name:    MI-SWACO3
        Source Network Address:    -
        Source Port:        -
    Detailed Authentication Information:
        Logon Process:        
        Authentication Package:    NTLM
        Transited Services:    -
        Package Name (NTLM only):    -
        Key Length:        0
    This event is generated when a logon request fails. It is generated on the computer where access was attempted.
    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
    The Process Information fields indicate which account and process on the system requested the logon.
    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
    The authentication information fields provide detailed information about this specific logon request.
        - Transited services indicate which intermediate services have participated in this logon request.
        - Package name indicates which sub-protocol was used among the NTLM protocols.
        - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
        <EventID>4625</EventID>
        <Version>0</Version>
        <Level>0</Level>
        <Task>12544</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8010000000000000</Keywords>
        <TimeCreated SystemTime="2014-09-04T16:46:25.247229500Z" />
        <EventRecordID>8917</EventRecordID>
        <Correlation />
        <Execution ProcessID="504" ThreadID="1344" />
        <Channel>Security</Channel>
        <Computer>MI-SWACO-DB.houston.livequest.net</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="SubjectUserSid">S-1-0-0</Data>
        <Data Name="SubjectUserName">-</Data>
        <Data Name="SubjectDomainName">-</Data>
        <Data Name="SubjectLogonId">0x0</Data>
        <Data Name="TargetUserSid">S-1-0-0</Data>
        <Data Name="TargetUserName">Administrator</Data>
        <Data Name="TargetDomainName">HOUSTONLQ</Data>
        <Data Name="Status">0xc000035b</Data>
        <Data Name="FailureReason">%%2304</Data>
        <Data Name="SubStatus">0x0</Data>
        <Data Name="LogonType">3</Data>
        <Data Name="LogonProcessName">
        </Data>
        <Data Name="AuthenticationPackageName">NTLM</Data>
        <Data Name="WorkstationName">MI-SWACO3</Data>
        <Data Name="TransmittedServices">-</Data>
        <Data Name="LmPackageName">-</Data>
        <Data Name="KeyLength">0</Data>
        <Data Name="ProcessId">0x0</Data>
        <Data Name="ProcessName">-</Data>
        <Data Name="IpAddress">-</Data>
        <Data Name="IpPort">-</Data>
      </EventData>
    </Event>
    The firewall is OFF in both client and server.
    I saw a similar question and the answer is related to firewall which is not may case.

    Hi Mario,
    According to your description, when you try to access the Report Manager in another client, a login dialog prompt. After typing a valid username and password 3 times, a blank page displays.
    Generally, the issue is always caused by the Report Server is configured to use Kerberos authentication, while the Service Principal Name(SPN) is not configured correctly. To fix this issue, please refer to the following methods:
    Register an SPN for the Report Server service under the domain user account.
    Change the service account to run under a built-in account such as Network Service.
    Remove RSWindowsNegotiate and ensure RSWindowsNTLM is specified in the rsreportserver.config file.
    Besides, the issue can also be caused by the Internet Explorer (IE) didn't pass the user's credential to the Report Server automatically or the IE is not Windows Integrated enabled. For more detail steps about how to address this issue, please refer to the
    following steps:
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/184c4f6c-b292-4f9a-beca-80b70f4392fe/report-manager-prompts-3-or-4-times-for-usernamepassword-before-letting-users-in?forum=sqlreportingservices
    Reference:
    Resolving Kerberos Authentication Errors When Connecting to a Report Server
    Solving the Reporting Services Login issue in the February CTP of SQL Server 2008
    If there are any other questions, please feel free to ask.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Unable to list SFTP Directory on windows 2008 r2 server from internet

    Hi experts,
    I have configured a SFTP on windows 2008 r2 server. And i am using the Filezilla on client machine to connect to SFTP server.
    The connection works properly on internal network but it displays error when i connect from internet.
    Error: GnuTLS error -53: Error in the push function.
    Response: 550 Data channel timed out.
    Error: Failed to retrieve directory listing
    This machine is publish with public IP and port22. The connection and authorization process gets complete but stops are Directory Listing.
    PLease suggest the troublshooting steps..
    Let me know if any more info is rquired.

    Hi,
    Do you also use the Filezilla to configure SFTP server? Since you use Filezilla on client machine to connect to SFTP server, I would suggest you ask for help from Filezilla forums for better and accurate answer.
    https://forum.filezilla-project.org/
    Best Regards,
    Mandy 
    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.

  • INS-20802: Problem installing Grid Infrastructure on Windows 2008 R2 Server

    Hello,
    I try to install the Grid Infrastructure on a Windows 2008 x64 Server. Everything works fine (the SCAN configuration and Verify) but at the end of the installation process I get the following error message:
    [INS-20802]: Grid Infrastructure Configuration not successfull.
    The errors that I found in the file oraInstall2012-02-27_11-58-26AM.log inside the INVENTORY\LOGS directory :
    INFO: Unable to read C:/app/11.2.0/grid/inventory/ContentsXML/comps.xml. Some inventory information may be lost.
    INFO: Install type for "Oracle Database 11g 11.2.0.3.0 " is "ASM".
    INFO: Conflict while setting install type of "Required Support Files 11.2.0.3.0 " to "Typical (Typical)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.assistants.server 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.ntrdbms.oraconfig 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.xdk 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.xdk.server 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.mgw.common 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.rdbms.install.seeddb 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.ctx 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.owb.rsf 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.sysman.console.db 10.1.0.2.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.rdbms.oci 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.ovm 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.sqlj.sqljruntime 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.rdbms.hsodbc 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.marvel 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.dbdev 11.2.0.3.0.
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.dbjava.server 11.2.0.3.0.
    INFO: Install type for "Cluster Ready Services Files 11.2.0.3.0 " is "Complete".
    INFO: Conflict while setting install type of "HAS Common Files 11.2.0.3.0 " to "Complete (Complete)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
    INFO: Install type for "Oracle Net Listener 11.2.0.3.0 " is "Typical".
    INFO: Install type for "Oracle Internet Directory Client 11.2.0.3.0 " is "Typical".
    INFO: Install type for "Oracle JVM 11.2.0.3.0 " is "Typical".
    INFO: OUI-10066:Not all the dependencies for the component Oracle JVM 11.2.0.3.0 could be found. Missing component oracle.javavm.companion 11.2.0.3.0.
    INFO: Install type for "Oracle Net 11.2.0.3.0 " is "Typical".
    INFO: Install type for "Oracle Netca Client 11.2.0.3.0 " is "Typical".
    INFO: Install type for "SQL*Plus 11.2.0.3.0 " is "Typical".
    INFO: Install type for "Oracle Database Utilities 11.2.0.3.0 " is "Typical".
    INFO: OUI-10066:Not all the dependencies for the component Oracle Database Utilities 11.2.0.3.0 could be found. Missing component oracle.omwb 10.1.0.1.0.
    INFO: Install type for "Oracle Recovery Manager 11.2.0.3.0 " is "Typical".
    INFO: Install type for "PL/SQL 11.2.0.3.0 " is "Typical".
    INFO: Install type for "HAS Files for DB 11.2.0.3.0 " is "Typical".
    INFO: Install type for "Assistant Common Files 11.2.0.3.0 " is "Typical".
    INFO: Conflict while setting install type of "Oracle Help For Java 4.2.9.0.0 " to "Typical (Typical)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
    INFO: Conflict while setting install type of "Buildtools Common Files 11.2.0.3.0 " to "Typical (Typical)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
    INFO: Conflict while setting install type of "Sun JDK 1.5.0.30.03 " to "Maximum (Complete)". Install type already set to "Maximum (Complete)". Seting it to "Custom (Custom)".
    INFO: OUI-10066:Not all the dependencies for the component Assistant Common Files 11.2.0.3.0 could be found. Missing component oracle.bali.kodiak 1.2.1.0.0I.
    INFO: Install type for "HAS Common Files 11.2.0.3.0 " is "Custom".
    INFO: Install type for "Oracle Multimedia 11.2.0.3.0 " is "Typical".
    INFO: Install type for "Oracle Multimedia Locator 11.2.0.3.0 " is "Typical".
    INFO: Install type for "Required Support Files 11.2.0.3.0 " is "Custom".
    INFO: Conflict while setting install type of "Oracle Net Required Support Files 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
    INFO: Conflict while setting install type of "Oracle Globalization Support 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
    INFO: Conflict while setting install type of "Oracle Core Required Support Files 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
    INFO: Conflict while setting install type of "RDBMS Required Support Files 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
    INFO: Conflict while setting install type of "Oracle RAC Required Support Files-HAS 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
    INFO: Install type for "Oracle JDBC/THIN Interfaces 11.2.0.3.0 " is "Typical".
    INFO: OUI-10066:Not all the dependencies for the component Oracle JDBC/THIN Interfaces 11.2.0.3.0 could be found. Missing component oracle.dbjava.ucp 11.2.0.3.0.
    INFO: Install type for "Oracle Core Required Support Files 11.2.0.3.0 " is "Custom".
    INFO: Install type for "Installation Common Files 11.2.0.3.0 " is "Typical".
    INFO: Install type for "Precompiler Required Support Files 11.2.0.3.0 " is "Custom".
    INFO: Install type for "Parser Generator Required Support Files 11.2.0.3.0 " is "Custom".
    INFO: Install type for "Agent Required Support Files 10.2.0.4.3 " is "Custom".
    INFO: Install type for "XDK Required Support Files 11.2.0.3.0 " is "Custom".
    INFO: Install type for "Oracle RAC Required Support Files-HAS 11.2.0.3.0 " is "Custom".
    INFO: Install type for "Buildtools Common Files 11.2.0.3.0 " is "Custom".
    INFO: Install type for "Oracle Globalization Support 11.2.0.3.0 " is "Custom".
    INFO: Install type for "Oracle Locale Builder 11.2.0.3.0 " is "Custom".
    INFO: Conflict while setting install type of "Oracle JFC Extended Windowing Toolkit 4.2.36.0.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
    INFO: Install type for "Oracle Clusterware RDBMS Files 11.2.0.3.0 " is "Typical".
    INFO: Install type for "Cluster Verification Utility Common Files 11.2.0.3.0 " is "Typical".
    INFO: Install type for "CFS 11.2.0.3.0 " is "Complete".
    INFO: Install type for "Oracle Notification Service (eONS) 11.2.0.3.0 " is "Typical".
    INFO: Install type for "Cluster Verification Utility Files 11.2.0.3.0 " is "Complete".
    INFO: Install type for "Oracle LDAP administration 11.2.0.3.0 " is "Typical".
    INFO: Install type for "Deinstallation Tool 11.2.0.3.0 " is "Complete".
    INFO: Conflict while setting install type of "Oracle Database Deconfiguration 11.2.0.3.0 " to "Complete (Complete)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
    INFO: Install type for "Enterprise Manager Common Files 10.2.0.4.3 " is "Complete".
    INFO: Install type for "Oracle Notification Service 11.2.0.3.0 " is "Typical".
    INFO: Install type for "Oracle Help For Java 4.2.9.0.0 " is "Custom".
    INFO: Conflict while setting install type of "Bali Share 1.1.18.0.0 " to "Custom (Custom)". Install type already set to "Maximum (Complete)". Seting it to "Custom (Custom)".
    INFO: Conflict while setting install type of "Oracle Ice Browser 5.2.3.6.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
    INFO: Install type for "Oracle Ice Browser 5.2.3.6.0 " is "Custom".
    INFO: Conflict while setting install type of "Oracle Extended Windowing Toolkit 3.4.47.0.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
    I have read and implemented all the settings described in DOCs ID 811271.1 , ID 810394.1 and RAC on Windows Step by Step Installation Instructions.
    After many attempts with the same error Ii am trying to install in a single node (RAC1). But the error looks the same, my server is clean with no oracle.
    Note: For this installation I downloaded and uncompressed the files p10404530_112030_MSWIN-x86-64_1of7.zip, p10404530_112030_MSWIN-x86-64_2of7 and p10404530_112030_MSWIN-x86-64_3of7 of the oracle site.
    I do not know what to do for this installation work.
    Thanks

    My recommendation would be to format the disks and install Linux.
    And I say that only half-jokingly. Fail-over with Windows is never as fast or as transparent as with a *NIX O/S.
    As to your specific issue ... open an SR with Oracle Support. Hardly anyone uses Windows for Oracle ... even fewer with RAC ... for the reason I gave above.

  • Oracle 11g ODAC 11.1.0.6.21 on Windows 2008 Standard server gives TNS error

    Hi,
    I have Oracle 11g ODAC 11.1.0.6.21 installed on my Application server that has 32 bit Windows 2008 Standard. The Oracle database 10g is installed on another 2008 server. On database server I can connect using SQLPlus. But on application server I cannot connect using ODAC SQLPlus. I have given correct service name in tnsnames.ora file.
    Error is ORA-12154 TNS: Listener cannot resolve service name
    What's wrong? Is 11.1.0.6.21 not meant for Windows 2008? I did not get any errors while installing.
    This 11.1.0.6.21 works perfectly for me on XP machine.
    I have browsed this forum but not getting clear steps to peform.
    Can someone guide me what is needed?
    Thanks
    Shrini

    Hi,
    The request to connect from the client is reaching the server but it seems the parsing of the service name is either wrong or the information is correct. Here are a couple of suggestions.
    If you have a good known set of sqlnet.ora and tnsnames.ora files on another client where the same connection descriptor works, then backup the curreny client network config files and copy the good known files to the Windows 2008 web server where you see the error. Make sure you recycle the worker processes once the files have been copied.
    Try to connect via Ezconnect and by pass the config files to see if you get the same error.
    //hostname:port/servicenameofdb
    where hostname is the machine where the target database is running
    port is the port on the DB machine where the tns listener is running and listening
    service name is the service name of the target DB
    Use this syntax in the connect string box when attempting to connect from SQL PLUS out of the ODAC home.
    You can also run lsnrctl utility on the server and vertify there is a handler for the service name or instance that is the target,
    HTH
    Jenny B.

  • Wyse Thin client not connecting to Windows 2008 R2 server

    Configuration
    SBS 2011 Server 
    Windows 2008 R2 server with Remote Desktop Services installed, License Manager installed.
    WYSE WT3125SE thin clients with Windows CE 5
    I setup the Windows 2008 with Remote Desktop Services and was able to successfully connect the Thin client.   Then I installed the License Manger and applied my Open license using User Cals.  Was able to login.  Next day I get the following
    error-"Because of a security error, the client could not connect to the remote computer.  Verify that you are logged onto the network and then try connecting again"    I still can connect fine from other machines even Windows Home Ed.  
    I remove license server and still was unable to connect.   Built a second Windows 2008 R2 server with RDS on it.  Was able to connect without issue.   Pointed it to the first RDS server license manager and have still been able to connect with
    the Thin Client.   The thin client can rdp to the SBS server without issue in admin mode, can connect to RDS2 server but not RDS1 with the license manger.    So my issue is with the license and so my question is what is it with the license server
    running on that server that is keeping thin client from connecting.  I even did a reload of RDS1 and tested connecting throughout the process and it worked up until I applied the license and then it stops. And then if I uninstall the license, rds, remove
    from domain still not able to connect.  Any help would be appreciated.

    We had the same problem with older terminals after cloning a 2008R2 rds server and sysprep it.
    The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error : Because
    of a security error, the client could not connect to the remote computer.  Verify that you are logged onto the network and then try connecting again"
    After reading all of the postings about this issue and tried the reactivate solution of the license server,
    I was sure that it had something to do with the x509 certificates that are generated the first time you connect to a valid license server.
    What I did, I installed a new license server activate it but did not install licenses on it.
    I pointed the defective rds server to the newly installed license server and deleted the following registry keys:
               HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
    Certificate
    X509 Certificate
    X509 Certificate ID
    X509 Certificate2
    Then reboot.
    After the reboot all old terminals can connect fine again. As final step I pointed the rds server to the same license server as the other ones,
    reboot and all worked fine.
    So conclusion is that when you pont a rds server to a license server that has the new type of licenses on it it will generate the wrong x509 certificates
    that are not supported by the older clients, by pointing it first to 1 without any rds calls on it, it generates the older x509 certificates which are compatible with the older rdp clients then the switch to new license server will then not regenerate the
    x509 certs so it keeps working.
    I hope this helps someone
    This issue was driving me crazy so very happy that it is resolved now
    Cheers Frits

  • Default OS performance counters processor, memory, logincal disk are missing in windows 2008 standard server

    I have a windows 2008 standard server in which the default OS performance counters counters processor, memory, logincal disk are missing.
    I tried using exctrlst.exe tool. This tool shows that the respective performance counters are already enabled but when I check in perfmon.msc, these counters are not visible.
    I also tried to rebuild the performance counters from the OS disk. but it did not worked. still the counters are missing.
    Because of these counters are missing, am unable to monitor the utilization of CPU, memory and disks.
    any suggestions, workaround, recommendations or solutions. it will be more helpful and highly appreciated !!!!.
    Regards,
    GK.
    GK

    Hi GK,
    According to your description, it seems that the issue was the same as the one described in the article below. If you are running Windows Server 2008 64-bit, you can check the KB below:
    http://support.microsoft.com/en-us/kb/2554336
    In addition, the articles below would also be helpful to you:
    How to manually rebuild Performance Counter Library values
    Missing Performance Counters
    Best regards,
    Susie
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • OS X Leopard and Windows 2008 file server mount_smbfs

    Hello
    I am unable to use the command mount_smbfs to mount a share on a Windows 2008 file server in OS X 10.5.8 Leopard.
    Here is what I am trying to do:
    I have a Mac Mini running OS X 10.5.8 that is joined to a Windows 2003 Active Directory domain. I also have a stand alone Windows file server running Windows Server 2008.
    I want to mount a share on the Windows 2008 file Server using the command line and not Finder. I do have a reason for wanting to do this which I wont bore you with.
    On the Mac Mini, I log in with an Domain account that has permission to access the file shares on the Windows 2008 file server. In Terminal I do the following:
    cd /Users/username
    mkdir mountpoint
    mount_smbfs //windows2008server/fileshare /Users/username/mountpoint
    This command should mount the share "fileshare" hosted on server "windows2008server" in the folder "mountpoint" on the Mac Mini.
    Here is the problem:
    When I execute this command, I get:
    Password: so I put in my password
    then I get:
    mount_smbfs: mount error: /Users/username/mountpoint: Broken pipe
    Analysis of the problem:
    I tried exactly the same commands to mount a share on a Windows 2003 file server. I am not asked for my password and the share mounts perfectly. I also tried the same command in OS X 10.6 to mount a share on a Windows 2008 file server, again, I was not asked for my password and the share mounted perfectly.
    So the problem is only mounting Windows 2008 file shares using mount_smbfs in OS X 10.5.8. I am not sure quite what is going wrong here, as the Mac is joined to the domain, it is granted a Kerberos ticket so should not be asking for my password. Is this a known bug in OS X 10.5? Is there a fix/workaround for it?
    Many thanks
    Richard.

    Not sure what user the mount command defaults to. You may want to specify your user name in the mount command (you can also specify the password). Try using this:
    mount_smbfs //username@windows2008server/fileshare /User/username/mountpoint
    Of course substituting the Windows 2008 account name you are mounting with for the username.
    Cheers,
    Dave

  • BO XI 3.1 SP2 error while installing in Windows 2008 ENT Server 32 Bit

    Hi
    We have  windows 2008 enterprise edition 32 Bit SP2 , While installing  BO 3.1 SP2 we are getting the following error.
    "Some files could not be created.
    Please close all applications, reboot Windows and restart this installation."
    1.we do have enough space as well as we are installing it through administrator account.
    2.I increase the virtual memory size from 2 GB to 4 GB, still same error.
    3.we downloaded the software in two diffrent machines. We tried extracting the "exe" file in two machine but still getting the same error.
    4.We dont have any firewall connected and windows firewall is off.
    Is there BO 3.1 Sp2 is available for windows 2008 ent server 32-Bit?
    Because In the download site there is Windows Server on IA32 32-bit.
    is it the correct version?
    Please help us to solve this problem
    Thanks

    We have opened a ticket for this. After subsequent discussion with the forum support person we have installed BO Enterprise 3.1 SP2 fixed pack 2.5 on the server (Windows Server 2008 SP2). On the client side, we have also installed BO Enterprise 3.1 SP2 fixed pack 2.5 and Live Office SP2 fixed pack 2.5.
    Once we tried to use the Web Intelligence document based on OLAP Universe in excel through Live Office it gives the following error.
    "Failed to get the document information. (LO 26315)  A database error occured. The database error text is: Failed to set properties (The component Microsoft® OLE DB Provider for Analysis Services returned server error (Database 'Sales' does not exist.)). (WIS 10901)(6315)".

  • Does WCS run on Windows 2008 R2 server?

    Can anybody share his/her experience with running WCS on Windows 2008 R2 server?
    Is it possible and did you experience any problems with it? (during installation or during normal usage)
    Is it supported by Cisco already?
    Our distributor is a little bit vague about that, that's is why I am asking it here.

    From WCS 7 release notes :
    Operating Systems Requirements
    The following operating systems are supported:
    •Windows 2003/SP2 and Windows 2003 R2/SP2 32-bit installations with all critical and security Windows updates installed.
    Windows 2003/SP2 64-bit installations are not supported. A 32-bit  operating system running on a 64-bit capable hardware is supported.
    Windows 2003 32-bit installations provide support for up to 64 GB of RAM  if Physical Address Extension (PAE) is enabled. See the Windows  documentation for instructions on enabling this mode.
    •Red Hat Linux Enterprise Server 5.X 32-bit operating system installations.
    Red Hat Linux Enterprise Server 5.X 64-bit operating system  installations are not supported. A 32-bit operating system running on a  64-bit capable hardware is supported.
    •Windows  2003 and Red Hat Linux version support on VMware ESX version 3.0.1 and  above with either local storage or SAN over fiber channel.
    Individual operating systems running WCS in VMware must follow the specifications for the size of WCS that you intend to use.
    No Windows 2008 ! I know lots of people have been crying for it and it should be coming in next releases but no promises as of now :-(
    Nicolas

  • SAPSprint installation on Windows 2008 R2 Server 64-bit

    Dear Gurus,
    as we change our print server to Windows 2008 R2 Server 64-bit I need to install SAPSprint for SAP printing with connection type 'S' out of a NW7.0 based system on HP-UX.
    Till now we used SAPlpd on a 32-bit Windows Server......
    1) Do I simply need to install the xSPrint.exe or can this happen only in combination with the whole SAPGui?
    2) According to note 66971 for Windows 2008 R2 Server 64-bit only SAPGui 7.20 is supported.
    Does this mean that I also have to use SAPSprint release 7.20 or can I use any other release as well.
    On our Windows clients we run SAPGui 7.10.
    Is there any correlation between the SAPGui running on the clients and the SAPGui / SAPSprint release running on the print server or can I simply install the highest SAPSprint release 7.20 on the print server to be sure that it will work with WK8 R2 64-bit?
    I hope I could explain my problem and I am looking forward to your reply.
    Thanks a lot in advance!
    Günter

    Dear Günter.
    Your question is spread over some different areas. Let me point out some tracks to follow:
    There is only a 32-bit version of SAPSprint but that one works also under 64-bit; please refer to SAP note 894444.
    Regarding SAPgui, in general it is recommended to have the last version as it is downwards-compatible with older versions.
    But specially, let me highlight that Windows 2008 R2 is not yet listed in the PAM - and hence not yet supported. The technical prerequisites are met (with a special kernel patch) but not all software is released.
    In fact, and just to provide you further details it is not possible to expect the 710 products released for Windows Server 2008 R2 before around four weeks; 700 products will be released even after 710.
    See SAP note 1383873 ("Windows Server 2008 R2 Support").
    You can be always up to date with the latest Windows news at:
    --> Support of Microsoft Windows Server 2008 R2
    Cheers!

  • Moving SAP Content Server/MaxDB 7.6 to a Windows 2008 R2 Server

    Hi All.
    We are in the process of upgrading our server where the SAP content server is located.  We are going from SAP CS 6.30/MaxDB 7.6 to a Windows 2008 R2 server where we want to install SAP CS 6.40/MaxDB 7.8.  I have been following the latest manual from SAP for upgrading to MaxDb 7.8  (2010-10-05) from MaxDb 7.6 using the in-place method.
    To date we have installed MaxDB 7.6 on the server.  We restored our latest backup and performed the index checks as spelled out in the manual.  I have the database in ADMIN mode and went to run the MaxDb 7.8 install for the 64 bit window version.  THe install GUI comes up, but the Update selection is grayed out.  This tells me that the install program can not detect our existing database.  I did make sure I was running the install as Admim so I do not think that is the issue.
    This is the second time I have tried this upgrade.  The first time I did a comand line upgrade by runing the .bat file DBUPDATE.bat. We have a 110 Gbyte database and this upgrade ran in about 15 minutes, and of course when I went to openthe database it was toast.  Do not want to make the same mistake again.
    One other point, since we did a restore of the database, then the index check, we did not run a backup as the manual suggested as we felt it was not necessary.  Does the system require a backup before upgrade and that is why it does not see the database?
    Any assistance will be greatly appreciated.

    I beleive we have resolved the issue with upgrading the database, but now we are having a problem with Datbase Studio 7.8.  Before the upgrade we used Data Manager 7.6.  After the upgrade we installed Database Studio 7.8 and when we go to start it up, we are getting the Problems opening perspective 'com.sap.sdb.tools.ut.perspectives.mainPerspective'. I followed the instruction in another post Problems opening perspective in Database Studio, but we still are getting the error.
    Can anybody offer any assistance as we are getting close to the weekend when we want to do the cutover and we are not even done with our first pass at upgrading the SAP content server.
    Thanks
    John

  • Windows 2008 R2 Server not showing update history and not detecting new updates

    Hi Sirs,
    We have a Windows 2008 R2 server which is showing an empty windows update history, and is not detecting new updates from the WSUS server. It says that the windows is up to date, no error when trying to detect new updates, but I doubt it because when I checked
    the installed updates menu, it shows that that the most recent update date installed was last 2013, it just stop detecting and installing updates. I've already tried the ff workarounds but to no avail:
    1. restart wuauserv and bits service
    2. rename/delete the software distribution folder
    3. reinstalled the update agent/restarted the server
    4. deleted the susclientid on the registry
    Thanks in advanced for your help.
    here's the windowsupdate.log:
    2014-07-22    00:57:06:728     928    a34    AU    #############
    2014-07-22    00:57:06:728     928    a34    AU    Successfully wrote event for AU health state:0
    2014-07-22    00:57:06:728     928    a34    AU    Featured notifications is disabled.
    2014-07-22    00:57:06:728     928    a34    AU    AU setting next detection timeout to 2014-07-21 20:50:56
    2014-07-22    00:57:06:728     928    a34    AU    Successfully wrote event for AU health state:0
    2014-07-22    00:57:06:728     928    a34    AU    Successfully wrote event for AU health state:0
    2014-07-22    00:57:11:727     928    abc    Report    REPORT EVENT: {AF0753F1-F6F9-4583-87B0-A0B0AEA0C6A7}    2014-07-22 00:57:06:728+0800    1  
     147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows
    Update Client successfully detected 0 updates.
    2014-07-22    00:57:11:727     928    abc    Report    REPORT EVENT: {188957AA-577F-4DC5-9CDB-2D8CFEE96670}    2014-07-22 00:57:06:728+0800    1  
     156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting
    client status.
    2014-07-22    00:57:11:727     928    abc    Report    CWERReporter finishing event handling. (00000000)
    2014-07-22    01:11:10:931     928    abc    Report    Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
    2014-07-22    01:11:10:947     928    abc    Report    Reporter successfully uploaded 2 events.
    2014-07-22    04:50:56:736     928    1130    AU    #############
    2014-07-22    04:50:56:736     928    1130    AU    ## START ##  AU: Search for updates
    2014-07-22    04:50:56:736     928    1130    AU    #########
    2014-07-22    04:50:56:736     928    1130    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
    2014-07-22    04:50:56:736     928    d08    Agent    *************
    2014-07-22    04:50:56:736     928    d08    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    04:50:56:736     928    d08    Agent    *********
    2014-07-22    04:50:56:736     928    d08    Agent      * Online = Yes; Ignore download priority = No
    2014-07-22    04:50:56:736     928    d08    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"
    2014-07-22    04:50:56:736     928    d08    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-07-22    04:50:56:736     928    d08    Agent      * Search Scope = {Machine}
    2014-07-22    04:50:57:017     928    d08    Setup    Checking for agent SelfUpdate
    2014-07-22    04:50:57:017     928    d08    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-07-22    04:50:57:017     928    d08    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    04:50:57:017     928    d08    Misc     Microsoft signed: Yes
    2014-07-22    04:50:59:611     928    d08    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    04:50:59:611     928    d08    Misc     Microsoft signed: Yes
    2014-07-22    04:50:59:611     928    d08    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    04:50:59:611     928    d08    Misc     Microsoft signed: Yes
    2014-07-22    04:50:59:626     928    d08    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    04:50:59:626     928    d08    Misc     Microsoft signed: Yes
    2014-07-22    04:50:59:626     928    d08    Setup    Determining whether a new setup handler needs to be downloaded
    2014-07-22    04:50:59:626     928    d08    Setup    SelfUpdate handler is not found.  It will be downloaded
    2014-07-22    04:50:59:626     928    d08    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    04:51:01:095     928    d08    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    04:51:01:095     928    d08    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    04:51:01:110     928    d08    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    04:51:01:110     928    d08    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    04:51:01:142     928    d08    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    04:51:01:142     928    d08    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-07-22    04:51:01:860     928    d08    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-07-22    04:51:01:860     928    d08    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    04:51:01:891     928    d08    PT    WARNING: Cached cookie has expired or new PID is available
    2014-07-22    04:51:01:891     928    d08    PT    Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
    2014-07-22    04:51:01:891     928    d08    PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
    2014-07-22    04:51:04:485     928    d08    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-07-22    04:51:04:485     928    d08    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    04:51:04:875     928    d08    Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
    2014-07-22    04:51:04:875     928    d08    Agent    *********
    2014-07-22    04:51:04:875     928    d08    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    04:51:04:875     928    d08    Agent    *************
    2014-07-22    04:51:04:875     928    1278    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
    2014-07-22    04:51:04:875     928    1278    AU      # 0 updates detected
    2014-07-22    04:51:04:875     928    1278    AU    #########
    2014-07-22    04:51:04:875     928    1278    AU    ##  END  ##  AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
    2014-07-22    04:51:04:875     928    1278    AU    #############
    2014-07-22    04:51:04:875     928    1278    AU    Successfully wrote event for AU health state:0
    2014-07-22    04:51:04:875     928    1278    AU    Featured notifications is disabled.
    2014-07-22    04:51:04:875     928    1278    AU    AU setting next detection timeout to 2014-07-22 00:38:28
    2014-07-22    04:51:04:875     928    1278    AU    Successfully wrote event for AU health state:0
    2014-07-22    04:51:04:875     928    1278    AU    Successfully wrote event for AU health state:0
    2014-07-22    04:51:09:874     928    d08    Report    REPORT EVENT: {FE398C01-75A1-4AD8-8C43-0894FCFCE13F}    2014-07-22 04:51:04:875+0800    1  
     147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows
    Update Client successfully detected 0 updates.
    2014-07-22    04:51:09:874     928    d08    Report    REPORT EVENT: {CDA386AD-6392-4C34-859E-35307BCB5EA0}    2014-07-22 04:51:04:875+0800    1  
     156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting
    client status.
    2014-07-22    04:51:09:874     928    d08    Report    CWERReporter finishing event handling. (00000000)
    2014-07-22    05:05:09:109     928    d08    Report    Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
    2014-07-22    05:05:09:109     928    d08    Report    Reporter successfully uploaded 2 events.
    2014-07-22    08:38:28:883     928    1130    AU    #############
    2014-07-22    08:38:28:883     928    1130    AU    ## START ##  AU: Search for updates
    2014-07-22    08:38:28:883     928    1130    AU    #########
    2014-07-22    08:38:28:883     928    1130    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
    2014-07-22    08:38:28:883     928    53c    Agent    *************
    2014-07-22    08:38:28:883     928    53c    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    08:38:28:883     928    53c    Agent    *********
    2014-07-22    08:38:28:883     928    53c    Agent      * Online = Yes; Ignore download priority = No
    2014-07-22    08:38:28:883     928    53c    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"
    2014-07-22    08:38:28:883     928    53c    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-07-22    08:38:28:883     928    53c    Agent      * Search Scope = {Machine}
    2014-07-22    08:38:29:195     928    53c    Setup    Checking for agent SelfUpdate
    2014-07-22    08:38:29:195     928    53c    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-07-22    08:38:29:195     928    53c    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    08:38:29:195     928    53c    Misc     Microsoft signed: Yes
    2014-07-22    08:38:31:804     928    53c    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    08:38:31:804     928    53c    Misc     Microsoft signed: Yes
    2014-07-22    08:38:31:804     928    53c    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    08:38:31:820     928    53c    Misc     Microsoft signed: Yes
    2014-07-22    08:38:31:820     928    53c    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    08:38:31:820     928    53c    Misc     Microsoft signed: Yes
    2014-07-22    08:38:31:835     928    53c    Setup    Determining whether a new setup handler needs to be downloaded
    2014-07-22    08:38:31:835     928    53c    Setup    SelfUpdate handler is not found.  It will be downloaded
    2014-07-22    08:38:31:835     928    53c    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    08:38:33:241     928    53c    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    08:38:33:241     928    53c    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    08:38:33:272     928    53c    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    08:38:33:272     928    53c    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    08:38:33:288     928    53c    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    08:38:33:288     928    53c    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-07-22    08:38:33:991     928    53c    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-07-22    08:38:33:991     928    53c    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    08:38:34:038     928    53c    PT    WARNING: Cached cookie has expired or new PID is available
    2014-07-22    08:38:34:038     928    53c    PT    Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
    2014-07-22    08:38:34:038     928    53c    PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
    2014-07-22    08:38:36:616     928    53c    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-07-22    08:38:36:616     928    53c    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    08:38:37:022     928    53c    Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
    2014-07-22    08:38:37:022     928    53c    Agent    *********
    2014-07-22    08:38:37:022     928    53c    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    08:38:37:022     928    53c    Agent    *************
    2014-07-22    08:38:37:022     928    aa8    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
    2014-07-22    08:38:37:022     928    aa8    AU      # 0 updates detected
    2014-07-22    08:38:37:022     928    aa8    AU    #########
    2014-07-22    08:38:37:022     928    aa8    AU    ##  END  ##  AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
    2014-07-22    08:38:37:022     928    aa8    AU    #############
    2014-07-22    08:38:37:022     928    aa8    AU    Successfully wrote event for AU health state:0
    2014-07-22    08:38:37:022     928    aa8    AU    Featured notifications is disabled.
    2014-07-22    08:38:37:022     928    aa8    AU    AU setting next detection timeout to 2014-07-22 04:15:53
    2014-07-22    08:38:37:022     928    aa8    AU    Successfully wrote event for AU health state:0
    2014-07-22    08:38:37:022     928    aa8    AU    Successfully wrote event for AU health state:0
    2014-07-22    08:38:42:021     928    53c    Report    REPORT EVENT: {45B5AD35-C612-4C43-8FE0-DFC63B114FC9}    2014-07-22 08:38:37:022+0800    1  
     147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows
    Update Client successfully detected 0 updates.
    2014-07-22    08:38:42:021     928    53c    Report    REPORT EVENT: {BA606714-0153-41BA-ADC8-78520F678D97}    2014-07-22 08:38:37:022+0800    1  
     156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting
    client status.
    2014-07-22    08:38:42:021     928    53c    Report    CWERReporter finishing event handling. (00000000)
    2014-07-22    08:52:41:224     928    53c    Report    Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
    2014-07-22    08:52:41:240     928    53c    Report    Reporter successfully uploaded 2 events.
    2014-07-22    12:15:53:027     928    1130    AU    #############
    2014-07-22    12:15:53:027     928    1130    AU    ## START ##  AU: Search for updates
    2014-07-22    12:15:53:027     928    1130    AU    #########
    2014-07-22    12:15:53:027     928    1130    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
    2014-07-22    12:15:53:043     928    a58    Agent    *************
    2014-07-22    12:15:53:043     928    a58    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    12:15:53:043     928    a58    Agent    *********
    2014-07-22    12:15:53:043     928    a58    Agent      * Online = Yes; Ignore download priority = No
    2014-07-22    12:15:53:043     928    a58    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"
    2014-07-22    12:15:53:043     928    a58    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-07-22    12:15:53:043     928    a58    Agent      * Search Scope = {Machine}
    2014-07-22    12:15:53:308     928    a58    Setup    Checking for agent SelfUpdate
    2014-07-22    12:15:53:308     928    a58    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-07-22    12:15:53:308     928    a58    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    12:15:53:324     928    a58    Misc     Microsoft signed: Yes
    2014-07-22    12:15:55:901     928    a58    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    12:15:55:901     928    a58    Misc     Microsoft signed: Yes
    2014-07-22    12:15:55:901     928    a58    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    12:15:55:917     928    a58    Misc     Microsoft signed: Yes
    2014-07-22    12:15:55:917     928    a58    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    12:15:55:917     928    a58    Misc     Microsoft signed: Yes
    2014-07-22    12:15:55:933     928    a58    Setup    Determining whether a new setup handler needs to be downloaded
    2014-07-22    12:15:55:933     928    a58    Setup    SelfUpdate handler is not found.  It will be downloaded
    2014-07-22    12:15:55:933     928    a58    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    12:15:57:167     928    a58    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    12:15:57:167     928    a58    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    12:15:57:167     928    a58    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    12:15:57:167     928    a58    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    12:15:57:198     928    a58    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    12:15:57:198     928    a58    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-07-22    12:15:57:917     928    a58    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-07-22    12:15:57:917     928    a58    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    12:15:57:963     928    a58    PT    WARNING: Cached cookie has expired or new PID is available
    2014-07-22    12:15:57:963     928    a58    PT    Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
    2014-07-22    12:15:57:963     928    a58    PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
    2014-07-22    12:16:00:572     928    a58    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-07-22    12:16:00:572     928    a58    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    12:16:00:932     928    a58    Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
    2014-07-22    12:16:00:932     928    a58    Agent    *********
    2014-07-22    12:16:00:932     928    a58    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    12:16:00:932     928    a58    Agent    *************
    2014-07-22    12:16:00:932     928    1120    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
    2014-07-22    12:16:00:932     928    1120    AU      # 0 updates detected
    2014-07-22    12:16:00:932     928    1120    AU    #########
    2014-07-22    12:16:00:932     928    1120    AU    ##  END  ##  AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
    2014-07-22    12:16:00:932     928    1120    AU    #############
    2014-07-22    12:16:00:932     928    1120    AU    Successfully wrote event for AU health state:0
    2014-07-22    12:16:00:932     928    1120    AU    Featured notifications is disabled.
    2014-07-22    12:16:00:932     928    1120    AU    AU setting next detection timeout to 2014-07-22 08:15:22
    2014-07-22    12:16:00:932     928    1120    AU    Successfully wrote event for AU health state:0
    2014-07-22    12:16:00:932     928    1120    AU    Successfully wrote event for AU health state:0
    2014-07-22    12:16:05:931     928    a58    Report    REPORT EVENT: {25E75367-1205-4F59-A812-02DA28BB3234}    2014-07-22 12:16:00:932+0800    1  
     147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows
    Update Client successfully detected 0 updates.
    2014-07-22    12:16:05:931     928    a58    Report    REPORT EVENT: {FE1434F8-C6AF-4F87-B3DF-6E4D6C4B05FB}    2014-07-22 12:16:00:932+0800    1  
     156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting
    client status.
    2014-07-22    12:16:05:931     928    a58    Report    CWERReporter finishing event handling. (00000000)
    2014-07-22    12:30:05:116     928    a58    Report    Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
    2014-07-22    12:30:05:131     928    a58    Report    Reporter successfully uploaded 2 events.
    2014-07-22    14:05:29:584     928    10a0    AU    Triggering AU detection through DetectNow API
    2014-07-22    14:05:29:584     928    10a0    AU    Triggering Online detection (interactive)
    2014-07-22    14:05:29:584     928    1130    AU    #############
    2014-07-22    14:05:29:584     928    1130    AU    ## START ##  AU: Search for updates
    2014-07-22    14:05:29:584     928    1130    AU    #########
    2014-07-22    14:05:29:584     928    1130    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
    2014-07-22    14:05:29:584     928    8e0    Agent    *************
    2014-07-22    14:05:29:584     928    8e0    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    14:05:29:584     928    8e0    Agent    *********
    2014-07-22    14:05:29:584     928    8e0    Agent      * Online = Yes; Ignore download priority = No
    2014-07-22    14:05:29:584     928    8e0    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"
    2014-07-22    14:05:29:584     928    8e0    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-07-22    14:05:29:584     928    8e0    Agent      * Search Scope = {Machine}
    2014-07-22    14:05:29:584     928    8e0    Setup    Checking for agent SelfUpdate
    2014-07-22    14:05:29:584     928    8e0    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-07-22    14:05:29:584     928    8e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    14:05:29:600     928    8e0    Misc     Microsoft signed: Yes
    2014-07-22    14:05:29:616     928    8e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    14:05:29:631     928    8e0    Misc     Microsoft signed: Yes
    2014-07-22    14:05:29:631     928    8e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    14:05:29:631     928    8e0    Misc     Microsoft signed: Yes
    2014-07-22    14:05:29:647     928    8e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    14:05:29:662     928    8e0    Misc     Microsoft signed: Yes
    2014-07-22    14:05:29:662     928    8e0    Setup    Determining whether a new setup handler needs to be downloaded
    2014-07-22    14:05:29:662     928    8e0    Setup    SelfUpdate handler is not found.  It will be downloaded
    2014-07-22    14:05:29:662     928    8e0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    14:05:29:662     928    8e0    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    14:05:29:662     928    8e0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    14:05:29:694     928    8e0    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    14:05:29:694     928    8e0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    14:05:29:709     928    8e0    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    14:05:29:725     928    8e0    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-07-22    14:05:30:037     928    8e0    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-07-22    14:05:30:037     928    8e0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    14:05:30:053     928    8e0    PT    WARNING: Cached cookie has expired or new PID is available
    2014-07-22    14:05:30:053     928    8e0    PT    Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
    2014-07-22    14:05:30:053     928    8e0    PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
    2014-07-22    14:05:35:630     928    8e0    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-07-22    14:05:35:630     928    8e0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    14:05:36:411     928    8e0    Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
    2014-07-22    14:05:36:411     928    8e0    Agent    *********
    2014-07-22    14:05:36:411     928    8e0    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    14:05:36:411     928    8e0    Agent    *************
    2014-07-22    14:05:36:411     928    1360    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
    2014-07-22    14:05:36:411     928    1360    AU      # 0 updates detected
    2014-07-22    14:05:36:411     928    1360    AU    #########
    2014-07-22    14:05:36:411     928    1360    AU    ##  END  ##  AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
    2014-07-22    14:05:36:411     928    1360    AU    #############
    2014-07-22    14:05:36:411     928    1360    AU    Successfully wrote event for AU health state:0
    2014-07-22    14:05:36:411     928    1360    AU    Featured notifications is disabled.
    2014-07-22    14:05:36:411     928    1360    AU    AU setting next detection timeout to 2014-07-22 10:01:01
    2014-07-22    14:05:36:411     928    1360    AU    Successfully wrote event for AU health state:0
    2014-07-22    14:05:36:411     928    1360    AU    Successfully wrote event for AU health state:0
    2014-07-22    14:05:41:410     928    8e0    Report    REPORT EVENT: {6A2B180E-A95F-42F7-B775-5750DFFD6ECD}    2014-07-22 14:05:36:411+0800    1  
     147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows
    Update Client successfully detected 0 updates.
    2014-07-22    14:05:41:410     928    8e0    Report    REPORT EVENT: {83041427-693D-4A42-AED0-E8E7BFB8E7E3}    2014-07-22 14:05:36:411+0800    1  
     156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting
    client status.
    2014-07-22    14:05:41:410     928    8e0    Report    CWERReporter finishing event handling. (00000000)

    No Service Pack 1 installed. Does this mean that no updates will be detected if SP1 is not installed? thanks
    That's exactly what that means!
    Updates have not been available for Windows Server 2008 R2 *RTM* systems since April, 2013.
    http://support.microsoft.com/lifecycle/?p1=14134
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Acrobat 9 Reader with Windows 2008 Terminal Server

    I am setting up a Windows 2008 Terminal Server and i need to have the Adobe Acrobat Reader installed. I downloaded and installed the Vista version and it worked from the console but when i try to access it via a terminal server session the application just crashes. If i try and run it as administrator in the same terminal server session it launches fine.
    Any suggestions????
    Jason
    p.s The associated event log error is:
    Log Name:      Application
    Source:        Application Error
    Date:          7/31/2008 1:17:57 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Comet.invera.com
    Description:
    Faulting application AcroRd32.exe, version 9.0.0.332, time stamp 0x4850f0a3, faulting module Annots.api, version 9.0.0.332, time stamp 0x4850e57f, exception code 0xc0000005, fault offset 0x001bd9e0, process id 0x1458, application start time 0x01c8f3316002e3b7.
    Event Xml:
        1000
        2
        100
        0x80000000000000
        3663
        Application
        Comet.invera.com
        AcroRd32.exe
        9.0.0.332
        4850f0a3
        Annots.api
        9.0.0.332
        4850e57f
        c0000005
        001bd9e0
        1458
        01c8f3316002e3b7

    Jason...
    Make Certain that you Had the Server In "TS-Install" Mode When you Installed Acrobat. It Is In your Control Panel. I Have Pasted the MS Help File Below.
    Install Programs on a Terminal Server
    You should install the Terminal Server role service on the computer before you install any programs that you want to make available to users. If you install the Terminal Server role service on a computer that already has programs installed, some of the existing programs may not work correctly in a multiple user environment. Uninstalling and then reinstalling the affected programs may resolve these issues.
    To ensure that an application is installed correctly to work in a multiple user environment, you must put the terminal server into a special installation mode before you install the application on the terminal server. This special installation mode ensures that the correct registry entries and .ini files that are needed to support running the application in a multiple user environment are created during the installation process.
    You can put a terminal server into this special installation mode by using either of the following:
    Install Application on Terminal Server tool under Programs in Control Panel. This tool will run a wizard to help install the application.
    Change user /install command at a command prompt. You will have to start the installation of the application manually.
    After the application is installed, you must put the terminal server into execution mode before remote users begin using the application. The Install Application on Terminal Server tool will automatically put the terminal server into execution mode when it is finished running. To put the terminal server into execution mode from a command prompt, use the change user /execute command.
    Additional considerations
    Some programs may require minor setup modifications to run correctly on a terminal server.
    If you have programs that are related to each other or have dependencies on each other, you should install the programs on the same terminal server. For example, you should install Microsoft Office as a suite on the same terminal server instead of installing individual Office programs on separate terminal servers.
    You should consider installing individual programs on separate terminal servers in the following circumstances:
    The program has compatibility issues that may affect other programs.
    A single program and the number of associated users may fill server capacity.
    For more information about the change user command-line tool, see the Terminal Services Command Reference (http://go.microsoft.com/fwlink/?LinkId=89674).
    For more information about deploying programs on a terminal server, see the Terminal Server page on the Windows Server 2008 TechCenter (http://go.microsoft.com/fwlink/?LinkId=79608).

  • Add Windows 2008 Terminal Server to RWW/RWA

    I would like to add our Windows 2008 Terminal Server (not R2) to RWW in Windows 2012R2 Essentials.  The connect computer wizard did not work on the Windows 2008 server, returning Win32 error.  
    How do I add the 2008 TS to the devices listing in RWW without using the connector wizard (as it does not work).   The Windows 2008 server has been join to the same domain manually.

    You cant add it as a tile device in the way you could in SBS 2011 Standard.
    You can create an RDP file, and save that so it is accessible via the RWA then add a link to the RWA to that file.
    You may need to tweak IIS to allow .rdp files.
    Robert Pearman SBS MVP
    itauthority.co.uk |
    Title(Required)
    Facebook |
    Twitter |
    Linked in |
    Google+

Maybe you are looking for

  • Black screen with dual head with kernel 3.7

    When I boot my (rather old) laptop with a VGA screen attached, the main LVDS screen goes totally black (with no backlight) at loading the module i915 and the VGA screen goes black (but one can see the backlight is on). When I boot without the VGA scr

  • Java seems to be having a buffer error....

    Ok let me start by saying I do not know any JAVA programming. I just trying to fix something that some dump programmer charged me a ton of money for and it does not work right... The program reads a XML stream and creates XML files... The read works

  • Restore X201 from Rescue and Recovery file says it will take 6 days complete

    Hi, I had a malware issue that messed up my firewall (McAfee) and so I decided to restore from a RnR file.  The file is located on my home network drive so I connnected via ethernet cable and initiated the full restore of the file.  I'm running an X2

  • Inactivation error in Declaring Fault Message type.

    Hi all,   when iam trying to create a message type with refering to data type "ExchangeFaultdata" , and when iam activating the corresponding message interface it says the the Message type that iam using is reffering to a inactive message type. i tri

  • Tab order help

    i am facing a problem with my tab order. Suppose i place certain components on a panel let's say base panel.On the same base panel i place another panel . I want the tab order in a way where initially the components which are out of the base panel re