2008 R2 Server Time problems - Gaining/Losing 6s/min

I'm having problems with a server on our network. I can go for days without a problem but then without warning the server will either gain or lose time at anywhere up to around 6 seconds per minute.  The server is running Server 2008 R2, member
server, IIS running internal sites, SiteCore CMS v6.4.1.
The w32time service is configured as follows
PDC - retrieves it's time from uk.pool.ntp.org, all other DCs and member servers have the w32tm service configured to syncfromflags:domhier.
The server in question is a virtual machine running on a server 2012 Hyper-V cluster.  All of the virtual servers on there have the Hyper-V time sync service enabled however we have edited the registry to set HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider\Enabled
to 0.
w32tm /query /source responds with a DC local to the server.
I've been monitoring the server for a number of days by outputting  the following command to a file on the server w32tm /stripchart /computer:localdc /dataonly and on the whole the server has been within +-5 seconds of the reference computer.
At approximate 13:06 this afternoon the server started to lose approximately 0.1s every second and is still doing so.  I've tried running the following command w32tm /resync /computer:localdc /nowait but to no avail.  I've had to manually change
the time in order to get services available again.
I've searched through the event logs on the server at or around 13:06 and can't find anything of any significance happening at that time.  I'm unable to restart the server during work hours as it's got key services running on it.
Any help on how to keep the time in sync on the server would be appreciated.

I would recommend that you read the Wiki I started here: http://social.technet.microsoft.com/wiki/contents/articles/18573.time-synchronization-in-active-directory-forests.aspx
As I mentioned:
Microsoft do not guarantee and do not support the accuracy of Windows Time Service between nodes on a network as this service is not a full-featured NTP solution that can meet time-sensitive application needs. Windows Time Service was not designated in such
way that it maintains time synchronization to the range of one (1) or two (2) seconds.
If you have an application that needs to have a high accuracy NTP solution then Windows Time Service should not be used in this case. Instead, third party software are available to satisfy this need.
High Accuracy W32time Requirements: http://blogs.technet.com/b/askds/archive/2007/10/23/high-accuracy-w32time-requirements.aspx 
Support boundary to configure the Windows Time service for high accuracy environments:http://support.microsoft.com/kb/939322/ 
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile
Thanks for that Mr X, I have already been on that page and implemented the Windows time service in the manner described in the article and in the other articles relating to configuring the Windows time service in a Hyper-V environment.
The issue is not relating to the configuration of the service as a whole as my other 72 server instances are working fine, it is just this one that is giving me a problem.  I have no need for a high accuracy environment, just one that keeps general
time and doesn't lose or gain 6 seconds/minute at random intervals through out the day.
I have been doing some further problem analysis since my original post with regards to the Hyper-V time sync service and my results are as follows.
When the time is a long way out on the server restarting the Hyper-V time sync service resets the time to the correct time instantly.
If you live migrate the VM to another host in the Hyper-v cluster when the time is incorrect, again the time resets to the correct time instantly.
I have reinstalled the Hyper-V integration services but this has had no effect on the problem.
As a last ditched attempt to resolve the issue I have re-enabled the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\w32time\TimeProviders\VMICTimeProvider
registry key so that when you run a w32m /query /source command the result is "VM IC Time Synchronization Provider"
I'll report back my findings.

Similar Messages

  • Window 2008 R2 datacentre server time problem

    Hi Team,
    I have one window 2008 R2 data centre server, which having time problem, I have setted IST time zone but time coming 15 minute delay, I have tried to correct time by manual but time goes again 15 minute delay itself.
    Please guide how to solve it and but i don't want to use NTP, as this server is on workgroup.
    Regards
    Inder Singh Rawat

    Hi ,
    I followed following step to build NTP in window server 2008 R2.
    Enabling & Configuring NTP Server
    1. Change the server type to NTP.
    Click Start, click Run, type regedit, and then click OK.
    Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type
    In the pane on the right, right-click Type, and then click Modify. In Edit Value, type NTP in the Value data box, and then click OK.
    2. Set AnnounceFlags to 5. 
    Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
     In the pane on the right, right-click AnnounceFlags, and then click Modify. In Edit DWORD Value, type 5 in the Value data box, and then click OK.
    3. Enable NTPServer.
    Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer
     In the pane on the right, right-click Enabled, and then click Modify .In Edit DWORD Value, type 1 in
    the Value data box, and then click OK
    4. Specify the time sources.
    Open a command prompt and type the command as below: w32tm /config /manualpeerlist:peers /syncfromflags:manual /reliable:yes /update
    peers: time.windows.com or time.nist.gov
    eg: w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /reliable:yes /update
    5. At the command prompt, type the following command to restart the Windows Time service, and then press Enter:
    net stop w32time 
    net start w32time  
    i run following useful command.
    1. To resynchronize time : w32tm /resync  or w32tm /resync /rediscover
    2. To verify the configuartion : w32tm /query /configuration and w32tm /query /status
    3. Display the current time zone settings : w32tm /tz
    Now what problem i am facing , when server goes restart "Window time service stoped" and ntp corrupted.
    Even Window time service is set automatically, when i do configure again then NTP work proper.
    Please help how to resolve this problem, if server restart NTP goes corrupted becuase of window time service stopped.
    Regards
    Inder Singh Rawat

  • I install LION on my mac pro 2008 and it's alway's pop with " there was a problem connecting to the server " Time Capsule" .How can i remove this popup. My Time machine is working fine and also rename it. But the popup keeps on coming with the old name.

    I installed LION on my mac pro 2008 and it's alway's pop with " there was a problem connecting to the server " Time Capsule" .How can i remove this popup. My Time machine is working fine and also rename it with less than 7 karakters. But the popup keeps on coming with the old name.

    I have a BT Infinity router plugged into the Time Capsule, not sure where the radio settings are?
    They are able to use the network settings of the TC i.e. they can connect to the internet via the wifi through the TC but when they try and connect to the AirPort Disk this is where it is not allowing a connection.
    I don;t have the drive shared out at all at the moment, is this necessary?  How do I do this if so?
    I have attached the screen shots of all the settings.
    Thanks again for your help.

  • How to secure connection in sql server 2008? my main problem is which certificate should i add in mmc

    i'm recently working on hardening of sql server 2008. now i face with a problem. my problem is  how to secure connection in sql server 2008?  my main problem is which certificate should i add in mmc? what are these certificates about?and guide
    me in choosing the appropriate certificate.
    and how should i know that the connection in sql server is secured?
    plz guide me from the beginning cause i'm rookie in this subject.
    thanks in advance.

    Hi sqlfan,
    Question 1: my problem is how to secure connection in sql server 2008?
    Microsoft SQL Server can use Secure Sockets Layer (SSL) to encrypt data that is transmitted across a network between an instance of SQL Server and a client application. For more information about Encrypting Connections to SQL Server, please refer to the following
    article:
    http://technet.microsoft.com/en-us/library/ms189067(v=sql.105).aspx
    Question 2: my main problem is which certificate should i add in mmc? what are these certificates about?and guide me in choosing the appropriate certificate.
    To install a certificate in the Windows certificate store of the server computer, you will need to purchase/provision a certificate from a certificate authority first. So please go to a certificate authority to choose the appropriate certificate.
    For SQL Server to load a SSL certificate, the certificate must meet the following conditions:
    The certificate must be in either the local computer certificate store or the current user certificate store.
    The current system time must be after the Valid from property of the certificate and before the Valid to property of the certificate.
    The certificate must be meant for server authentication. This requires the Enhanced Key Usage property of the certificate to specify Server Authentication (1.3.6.1.5.5.7.3.1).
    The certificate must be created by using the KeySpec option of AT_KEYEXCHANGE. Usually, the certificate's key usage property (KEY_USAGE) will also include key encipherment (CERT_KEY_ENCIPHERMENT_KEY_USAGE).
    The Subject property of the certificate must indicate that the common name (CN) is the same as the host name or fully qualified domain name (FQDN) of the server computer. If SQL Server is running on a failover cluster, the common name must match the host
    name or FQDN of the virtual server and the certificates must be provisioned on all nodes in the failover cluster.
    Question 3: how should i know that the connection in sql server is secured?
    If the certificate is configured to be used, and the value of the ForceEncryption option is set to Yes, all data transmitted across a network between SQL Server and the client application will be encrypted using the certificate. For more detail about this,
    please refer to Configuring SSL for SQL Server in the following article:
    http://technet.microsoft.com/en-us/library/ms189067(v=sql.105).aspx
    If you have any question, please feel free to let me know.
    Regards,
    Donghui Li

  • There was a problem connecting to the server "Time Capsule".  The share does not exist on the server. Please check the share name, and then try again.

    The following error pop's up as an [OK] dialogue box after logging in the iMac,
    There was a problem connecting to the server "Time Capsule".
    The share does not exist on the server. Please check the share name, and then try again."
    As it happens, a connection to the Time Capsule is established usually, anyway. On occasion it doesn't.
    I have a Volume, Data, on the capsule, which similarly, usually mounts, but occassionally doesn't, with access permissions denied.
    Any suggestions on how begin to work out how to achieve networking seamlesness?

    First, restart the Time Capsule by disconnecting the power adapter and reconnecting it. If other devices on the network can see it, you can skip this step.
    From the menu bar, select
     ▹ System Preferences ▹ Network
    Click the lock icon in the lower left corner of the window and authenticate to unlock the settings, if necessary. Click the Advanced button, then select the TCP/IP tab in the sheet that drops down. Click Renew DHCP lease.
    Try again to back up.
    If you still can't, open the Time Machine preference pane and delete the TC from the list of backup destinations. You may have to unlock the settings by clicking the lock icon in order to do this. Then add it back.

  • Autologin on Windows Server 2008 R2 - local Administrator problem

    I needed an user to autologin on a Windows Server 2008 R2 server.
    Configured it following this guide: http://www.danj.co.uk/2011/06/enable-autologon-for-windows-2008-r2.html
    In addition I added the login information by using the Autologon tool from sysinternals: http://technet.microsoft.com/en-us/sysinternals/bb963905.aspx
    Now the user I configured autologins successfully. The only downside is that now you can login with the local Administrator account by just hitting enter, as it now doesn't check the password and instead has a blank one. I think this comes from the User
    accounts screen where I unticked the checkbox and also the Administrator account is listed. When trying to remove the local Administrator it tells me that it will delete the account. I don't want that.
    How do I keep autologin of the user I configured but also have the local Administrator account check his password?

    Hello,
    please see
    http://www.expta.com/2008/04/how-to-enable-autologon-for-windows.html
    Best regards
    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://blogs.msmvps.com/MWeber
    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
    Twitter:  

  • 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.

  • Edge Animate causing Server Time Out Error and other problems

    Site is not verifying due to Server Time Out error. Also menu which was created with Adobe Edge Animate does not show up as navigation in a site map or when bots read the site. Site won't verify or index in google.
    Suggestions on how to fix this would be helpful and appreciated.
    This is the website address. please type in Without any spaces:
    louis place cafe DOT com DOT au

    Site is not verifying due to Server Time Out error. Also menu which was created with Adobe Edge Animate does not show up as navigation in a site map or when bots read the site. Site won't verify or index in google.
    Suggestions on how to fix this would be helpful and appreciated.
    This is the website address. please type in Without any spaces:
    louis place cafe DOT com DOT au

  • Exchange Server 2010 - Problem configuring my server 2008 so my clients can use Outlook to send/receive e-mails

    Hi,
    I am new to the servers and domains stuff. Therefore i have setup succesfully a Server 2008 R2 server with AD, DHCP, DNS roles installed. I configured the roles as i wanted and then i installed Exchange Server 2010 so the clients can use Outlook to send
    receive mails in and out of the domain.
    I can send/receive mails inside the domain (disalfa.com) but i cannot send/receive mails outside the domain. I configured the Exchange properly, i am sure of that. I am 99,9% i did something wrong with the DNS (A records, MX records, etc.).
    Also is there something i must do from the control panel of the site i purchased the domain name and the mails?
    Can someone guide me so i can manage to work this out?
    Server 2008 -  192.168.1.250
    Registered Domain - disalfa.com
    Thank you in advance

    Hi ,
    I recommend you refer to the following article to configure your external mail flow:
    Configure Internet Mail Flow Directly Through a Hub Transport Server
    Prerequisites
    Register MX resource records for all accepted domains in a public domain name system (DNS) server. Consult the documentation of your DNS provider for information about how to register MX records for your domain. Detailed procedures about how to complete
    this step are outside the scope of this topic.
    Configure network gateways to allow SMTP traffic to and from the Hub Transport server. Consult the documentation for your network routers and firewalls for information about how to route SMTP traffic to and from the Hub Transport server. Detailed procedures
    about how to complete this step are outside the scope of this topic.
    Best regards,
    Niko Cheng
    TechNet Community Support

  • SMS 2008 Server time out same time every hour

    Our server times out at the same time every hour. Any computer connected to our network at exactly xx:53, any program or anything you are attempted to do goes to the loading circle and says not responding. It stays that way until xx:54. Every hour, every
    day. However, nothing shows up on the error reports.

    Hi MNQWolfe,
    Based on your description, I suggest that you should firstly check if there any program or feature (such as antivirus program, update, backup and so on) started
    working at that time. Also, please monitor the Task Manager or Resource Monitor to check if any process was started at that time.
    In addition, it seems to be a network issue. Please run a sniffer on the server. You can use Microsoft Network Monitor 3.4 to monitor and then check ARP messages
    and so on.
    Microsoft Network Monitor 3.4
    http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=4865
    Hope this helps.
    Best regards,
    Justin Gu

  • New WSUS on Server 2012 - problem with win8 clients

    Hi,
    Two weeks ago we created a new Server 2012 and installed the WSUS role from scratch on it.  Its version number is:  6.2.9200.16384.  It replaced a Server 2008 WSUS server.  After some time all the win7 clients updated and reported as
    they did on the old and replaced server.
    However all our win8 clients refuse to update against this server.  They show correctly up in WSUS server console each with 107 needed updates day after day.  We have rebooted them and done numerous wuauclt /resetauthorization /detectnow and wuauclt
    /detectnow /reportnow, but to no avail.
    I paste in some lines from a win8 client winupdate log at the end of this message if someone can figure out what I have to do to get these clients update as they did against the old wsus server.  Thanks for help on this issue.
    regards Tor
    2014-02-03    08:33:38:008     920    153c    Agent    *************
    2014-02-03    08:33:38:008     920    153c    Agent    ** START **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:38:008     920    153c    Agent    *********
    2014-02-03    08:33:38:008     920    153c    Agent      * Online = Yes; Ignore download priority = No
    2014-02-03    08:33:38:008     920    153c    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-02-03    08:33:38:008     920    153c    Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-02-03    08:33:38:008     920    153c    Agent      * Search Scope = {Machine & All Users}
    2014-02-03    08:33:38:008     920    153c    Agent      * Caller SID for Applicability: S-1-5-18
    2014-02-03    08:33:38:008     920    153c    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2014-02-03    08:33:38:008     920    1990    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {ABC7E77F-635F-4192-9B92-CBF9B1CB8AB0} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2014-02-03    08:33:38:008     920    1990    AU      # 0 updates detected
    2014-02-03    08:33:38:008     920    1990    AU    #########
    2014-02-03    08:33:38:008     920    1990    AU    ##  END  ##  AU: Search for updates  [CallId = {ABC7E77F-635F-4192-9B92-CBF9B1CB8AB0} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2014-02-03    08:33:38:008     920    1990    AU    #############
    2014-02-03    08:33:38:023     920    153c    Misc     Microsoft signed: Yes
    2014-02-03    08:33:38:023     920    153c    Misc     Infrastructure signed: Yes
    2014-02-03    08:33:38:023     920    153c    EP    Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "http://fe1.ws.microsoft.com/w8/2/redir/storeauth.cab"
    2014-02-03    08:33:38:023     920    153c    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\117CAB2D-82B1-4B5A-A08C-4D62DBEE7782\wuredir.cab:
    2014-02-03    08:33:38:039     920    153c    Misc     Microsoft signed: Yes
    2014-02-03    08:33:38:039     920    153c    Misc     Infrastructure signed: Yes
    2014-02-03    08:33:38:039     920    153c    EP    Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Client/Server URL: "https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx"
    2014-02-03    08:33:38:055     920    153c    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-02-03    08:33:38:055     920    153c    PT      + ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}, Server URL = https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx
    2014-02-03    08:33:38:055     920    153c    Agent    Reading cached app categories using lifetime 604800 seconds
    2014-02-03    08:33:38:055     920    153c    Agent    Read 0 cached app categories
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {E7FF661C-6A03-4387-A1EE-1D723B52EF60}.3 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {A9A0E183-0667-46D6-84E4-17CEBCEE5A22}.1 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Found 13 updates and 31 categories in search; evaluated appl. rules of 69 out of 94 deployed entities
    2014-02-03    08:33:39:211     920    153c    Agent    *********
    2014-02-03    08:33:39:211     920    153c    Agent    **  END  **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:211     920    153c    Agent    *************
    2014-02-03    08:33:39:211     920    1a64    Report    REPORT EVENT: {0786C161-F6DC-4842-85D6-9506124654AD}    2014-02-03 08:33:38:008+0100    1  
     147 [AGENT_DETECTION_FINISHED]    101    {00000000-0000-0000-0000-000000000000}    0    0    Windows Update Command Line    Success    Software Synchronization  
     Windows Update Client successfully detected 0 updates.
    2014-02-03    08:33:39:211     920    1a64    Report    REPORT EVENT: {1E5D9728-220F-44A3-8BCC-ADE69687531D}    2014-02-03 08:33:38:008+0100    1  
     156 [AGENT_STATUS_30]    101    {00000000-0000-0000-0000-000000000000}    0    0    Windows Update Command Line    Success    Pre-Deployment Check  
     Reporting client status.
    2014-02-03    08:33:39:211     920    1a64    Report    REPORT EVENT: {57BAB7D0-685B-4D73-BDF7-82AFCE8675B0}    2014-02-03 08:33:39:211+0100    1  
     147 [AGENT_DETECTION_FINISHED]    101    {00000000-0000-0000-0000-000000000000}    0    0    Windows Update Command Line    Success    Software Synchronization  
     Windows Update Client successfully detected 13 updates.
    2014-02-03    08:33:39:211     920    1a64    Report    CWERReporter finishing event handling. (00000000)
    2014-02-03    08:33:39:227     920    153c    Agent    *************
    2014-02-03    08:33:39:227     920    153c    Agent    ** START **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:227     920    153c    Agent    *********
    2014-02-03    08:33:39:227     920    153c    Agent      * Online = No; Ignore download priority = No
    2014-02-03    08:33:39:227     920    153c    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-02-03    08:33:39:227     920    153c    Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-02-03    08:33:39:227     920    153c    Agent      * Search Scope = {Current User}
    2014-02-03    08:33:39:227     920    153c    Agent      * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1155
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {A9A0E183-0667-46D6-84E4-17CEBCEE5A22}.1 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Found 11 updates and 29 categories in search; evaluated appl. rules of 58 out of 94 deployed entities
    2014-02-03    08:33:39:258     920    153c    Agent    *********
    2014-02-03    08:33:39:258     920    153c    Agent    **  END  **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:258     920    153c    Agent    *************
    2014-02-03    08:33:39:258     920    153c    Agent    *************
    2014-02-03    08:33:39:258     920    153c    Agent    ** START **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:258     920    153c    Agent    *********
    2014-02-03    08:33:39:258     920    153c    Agent      * Online = No; Ignore download priority = No
    2014-02-03    08:33:39:258     920    153c    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-02-03    08:33:39:258     920    153c    Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-02-03    08:33:39:258     920    153c    Agent      * Search Scope = {Current User}
    2014-02-03    08:33:39:258     920    153c    Agent      * Caller SID for Applicability: S-1-5-21-2212025170-3189117132-1219651784-500
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
    2014-02-03    08:33:39:305     920    153c    Agent    *********
    2014-02-03    08:33:39:305     920    153c    Agent    **  END  **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:305     920    153c    Agent    *************
    2014-02-03    08:33:39:305     920    153c    Agent    *************
    2014-02-03    08:33:39:305     920    153c    Agent    ** START **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:305     920    153c    Agent    *********
    2014-02-03    08:33:39:305     920    153c    Agent      * Online = No; Ignore download priority = No
    2014-02-03    08:33:39:305     920    153c    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-02-03    08:33:39:305     920    153c    Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-02-03    08:33:39:305     920    153c    Agent      * Search Scope = {Current User}
    2014-02-03    08:33:39:305     920    153c    Agent      * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1323
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
    2014-02-03    08:33:39:352     920    153c    Agent    *********
    2014-02-03    08:33:39:352     920    153c    Agent    **  END  **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:352     920    153c    Agent    *************
    2014-02-03    08:33:39:352     920    153c    Agent    *************
    2014-02-03    08:33:39:352     920    153c    Agent    ** START **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:352     920    153c    Agent    *********
    2014-02-03    08:33:39:352     920    153c    Agent      * Online = No; Ignore download priority = No
    2014-02-03    08:33:39:352     920    153c    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-02-03    08:33:39:352     920    153c    Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-02-03    08:33:39:352     920    153c    Agent      * Search Scope = {Current User}
    2014-02-03    08:33:39:352     920    153c    Agent      * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1282
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
    2014-02-03    08:33:39:383     920    153c    Agent    *********
    2014-02-03    08:33:39:383     920    153c    Agent    **  END  **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:383     920    153c    Agent    *************
    2014-02-03    08:33:39:383     920    1990    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {66AF0139-896D-4607-8660-B66D2B58EA26} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-02-03    08:33:39:383     920    1990    AU      # 12 updates detected
    2014-02-03    08:33:39:383     920    1990    AU    #########
    2014-02-03    08:33:39:383     920    1990    AU    ##  END  ##  AU: Search for updates  [CallId = {66AF0139-896D-4607-8660-B66D2B58EA26} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-02-03    08:33:39:383     920    1990    AU    #############
    2014-02-03    08:33:39:383     920    1990    AU    All AU searches complete.
    2014-02-03    08:33:39:383     920    1990    AU    AU setting next detection timeout to 2014-02-03 10:18:51
    2014-02-03    08:33:44:211     920    1a64    Report    CWERReporter finishing event handling. (00000000)
    2014-02-03    08:41:39:472     920    1a64    EP    Got WSUS Client/Server URL: "http://elias:8530/ClientWebService/client.asmx"
    2014-02-03    08:41:39:472     920    1a64    PT    WARNING: Cached cookie has expired or new PID is available
    2014-02-03    08:41:39:472     920    1a64    EP    Got WSUS SimpleTargeting URL: "http://elias:8530"
    2014-02-03    08:41:39:472     920    1a64    PT    Initializing simple targeting cookie, clientId = c5e26849-287b-4b96-ba5d-1489d6fad2f2, target group = , DNS name = dt-ikt-tor.framnes.lan
    2014-02-03    08:41:39:472     920    1a64    PT      Server URL = http://elias:8530/SimpleAuthWebService/SimpleAuth.asmx
    2014-02-03    08:41:39:519     920    1a64    EP    Got WSUS Reporting URL: "http://elias:8530/ReportingWebService/ReportingWebService.asmx"
    2014-02-03    08:41:39:519     920    1a64    Report    Uploading 2 events using cached cookie, reporting URL = http://elias:8530/ReportingWebService/ReportingWebService.asmx
    2014-02-03    08:41:39:566     920    1a64    Report    Reporter successfully uploaded 2 events.
    2014-02-03    08:42:13:212     920    178c    Report    WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
    2014-02-03    08:43:40:450     920    178c    AU    ###########  AU: Uninitializing Automatic Updates  ###########
    2014-02-03    08:43:40:450     920    178c    WuTask    Uninit WU Task Manager
    2014-02-03    08:43:40:513     920    178c    Service    *********
    2014-02-03    08:43:40:513     920    178c    Service    **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-02-03    08:43:40:513     920    178c    Service    *************

    Today I opened Control Panel / Windows Updates and first did a check for new updates (from the WSUS server).  Nothing was found and it reported Windows is Updated.   Then I clicked the link Check for updates from Microsoft via internet, and
    it found around 24 updates.
    This is confirmation of the point that I made in the previous post. The updates are *NEEDED* by this system, but the updates were not *AVAILABLE* from the assigned WSUS Server. You were able to get them from Windows Update, but that does not fix your continuing
    issue with the WSUS Server.
    but it still reported the original 108 Needed updates.
    Exactly. As previously noted, the client is functioning perfectly. The problem is NOT with the client; the problem is with the WSUS Server. The updates that this client needed were not AVAILABLE to be downloaded from the WSUS server.
    Why this is the case requires further investigation on your part, but is either because the updates are not properly approved, or the update FILES are not yet downloaded from Microsoft to the WSUS server.
    It appears that the wsus server doesn't get any information back from the client despite that it displays new Last contact and Last Status report timestamps.
    This conclusion is incorrect. The WSUS Server got every bit of information available from the client -- you've confirmed this by the number of updates reported as "Needed" by the Windows Update Agent to the WSUS Server.
    I assumed that the log would display if the updates were downloaded or not.
    It will log when the updates are actually downloaded. If there's no log entries for updates being downloaded, then they're not being downloaded. If the logfile says "Found 0 updates", then that means exactly what it says: It couldn't find any approved/available
    updates to download.
    In your case it "Found 11 updates", but now it will be impossible to diagnose that fault, because you went and got them from Windows Update.
    All Win8 versions are checked in the WSUS server's Product list so the updates should at least have been downloaded to the server.
    This is why understanding the infrastructure is so critical. Your conclusion is invalid based on the premise given, and you may be using improper terminology which only confuses the rest of us as well.
    First, selecting updates for synchronization only gets the update metadata (i.e. the detection logic) downloaded to the WSUS database.
    The Second Step in this process is to Approve those updates for one or more WSUS Target Groups that contain the appropriate client systems. Following the approval of an update, the WSUS Server downloads the INSTALLATION FILE for that update.
    Once the WUAgent sees an approved update and the installation file is available, then the WUAgent will download the file and schedule the update for installation.
    Most of the post I read about my problem is about upgrading a 2008 WSUS server to support Win8 / Server 12 clients.  When I try to run this update on my Server 12 WSUS it refuses to run (probably because it is for Server 2008).
    Yeah.. totally different issue in those posts than what you're describing here.
    What should I do to try to track down the problem?
    Well.... now that it's 11 days since the logfile was posted, and you've already updated that system, we'll first need to find another system exhibiting the same issue.
    Then I'll need to ask a number of questions to properly understand the environment, as well as what you have or have not done.
    Then, from there, we can attempt to figure out why your Windows 8 client apparently sees some updates as approved/available but is still not downloading them. We do not yet have sufficient information to even speculate on a possible cause -- there are several.
    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.

  • External drive conntected to Time Capsule keeps losing connection

    I've been having this problem since I bought my TC over one year ago. Other than this everything works fine (aside from the occasional need for a restart).
    I have an external 500GB drive attached to my 500GB TC via usb. I use the TC strictly for backups and the other drive to host my media files. When I want to use those files I switch on the drive. Only about half of the time does that work. When it does work everything is fine. I see the drive in the finder as expected.
    When it doesn't work, I can see the drive name in the finder. But if I click to go into the folder, I get an error saying that the connection cannot be found.
    It shows up in the Airport Utility as normal.
    Powering the drive off and on does not help.
    Relaunching the finder doesn't help either.
    The only way I can connect to the drive again is to either logoff and log back into my mac, or restart the TC.
    It seems that my computer is remembering some kind of network disk mounting settings that don't get refreshed when I turn on the drive, but then do get refreshed when I logoff and back in. Does anyone know how I could force that refresh to happen? Has anyone had this problem before?
    Any suggestions would be much appreciated
    PS all my software and firmware are the latest.
    Thanks.

    OS X fan
    This helped meRe: Time Capsule keeps losing connection in Finder 
    Dec 17, 2013 4:08 AM (in response to whootang12)
    Left click on the Finder icon from the Dock and click "Connect to server...", go to recent server and click on your Airport Time Capsule.
    THANK YOU!!!!
    This solved it for me!

  • 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

  • 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

  • Server time out by full Optimize application process

    Hello,
    we have problem with full optimize application processing. We have got error message "Server time out"  on the Processing OLAP Database.
    our test environment on the VM x64bit, Server 2008
    Please anybody helps me to solve this issue.
    P.S. other optimize processes are workable (lite and Incremental)
    Thanks
    Arai

    Hi,
    Please see Note 1277009.
    This might resolve your issue.
    Karthik AJ

Maybe you are looking for

  • How do I organise albums chronologically in itunes on my iPad?

    If I select an artist within iTunes on my iPad, the albums are listed chronologically. I can't find the settings to change this to alphabetical. Any advice much appreciated!

  • Deploying BEA Portal App in Managed Server problems....

    Hello, I have a BEA portal application (exploded EAR) that I want to deploy in a managed server. I first created a regular portal domain (8.1 SP4). I then created a managed server via the console. When I went to deploy my portal application (in the c

  • Select Expert

    When using the Record Selection tool from the Standard report creation wizard, the drop down list in the Record select is not being populated with data. However, when using the select expert from a blank report the drop down is working just fine. Any

  • Passing values from sub sequence to caller

    Hi All I am using TestStand 4.0. In the setup of my top level sequence I call a sub sequence to calibrate RF cable losses on the test site. These cable losses need to be passed back up to the top level sequence so they can then be stored and used thr

  • Problems installing SAP GUI 7.1 patch level 4 for Bex Analyzer

    Hi all, I have a problem installing the SAP GUI for BW - running office 2003, have tried to install without success.  The old Bex tools seem to work, but not the new ones and when opening any of the tools report designer or web application designer I