Search the Community
Showing results for tags 'server 2003'.
WannaCry was a disaster that could have been prevented if people took notice. If you didn’t hear about it you must have been asleep, here is a refresher. After WannaCry, most businesses took notice and updated their operating systems, patched them and took measures to avoid a further outbreak. But today, May 14th, 2019, Microsoft has released information that warns of yet another WannaCry-like worm. Note: If you are using Windows 10, you are OK, you are not vulnerable to this CVE. If not, and if you are still on Windows 7 then start upgrading to Windows 10 by using the Inplace Upgrade Task Sequence I explain about here or if you cannot upgrade immediately, then patch Windows 7 to protect it from this vulnerability. Vulnerable in-support systems include Windows 7, Windows Server 2008 R2, and Windows Server 2008. Downloads for in-support versions of Windows can be found in the Microsoft Security Update Guide. Customers who use an in-support version of Windows and have automatic updates enabled are automatically protected. Out-of-support systems include Windows 2003 and Windows XP. If you are on an out-of-support version, the best way to address this vulnerability is to upgrade to the latest version of Windows. Even so, we are making fixes available for these out-of-support versions of Windows in KB4500705. If however you are running Windows XP, yes…. that old unsupported operating system then take warning ! Today, Microsoft has warned against the wormable capabilities from this CVE (critical Remote Code Execution vulnerability) and they blogged about what to do to avoid it happening to you. Read that blog post here: https://blogs.technet.microsoft.com/msrc/2019/05/14/prevent-a-worm-by-updating-remote-desktop-services-cve-2019-0708/ It’s very clear from their text that this is all about protecting customers from the next worm, so pay attention and if you have old operating systems that are in support and affected, then update immediately. Note: This is so serious that even Windows XP and Windows Server 2003 are getting updates from Microsoft for this vulnerability. You can download those updates from Microsoft Catalog here. https://support.microsoft.com/en-ca/help/4500705/customer-guidance-for-cve-2019-0708
I'm having some problems with downstream servers syncing with the upstream server. All WSUS Servers are WSUS Server Version: 3.2.7600.256 and I have installed KB2720211 and KB2734608. The Database is held in the Windows Internal Database The Upstream server is synchronising with Windows Update absolutely fine, and downloading updates OK. The three downstream servers however are not. They are reporting as failed with the below message = Result = An error occurred with the server’s data store. Clicking Details shows the below detailed message = SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout) at System.Data.SqlClient.SqlDataReader.Read() at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ReadOneRow() at Microsoft.UpdateServices.Internal.DataAccess.HideUpdatesForReplicaSync(String xmlUpdateIds) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ProcessHiddenUpdates(Guid hiddenUpdates) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ReplicaSync() at Microsoft.UpdateServic Whats also weird is the computer status is being sync’d to the upstream server and the downstream servers are downloading new updates, yet the sync is still failing? Can anyone shed some light? The upstream server = Server 2003 1 Downstream server = Server 2008 R2 2 Downstream Servers = Server 2003
Hello, If my current SCCM 2007 R2 is installed on a 32bit Windows Server 2003, and I plan on migrating to SCCM 2012 on Server 2008 R2 x64, will there be any problems with the migration process going from a 32bit to 64bit environment? The reason I ask is that I read in a forum post somewhere that an admin in a similar situation did the following steps: performed a full backup of SCCM 2007 running on W2K3 32bit, reinstalled SCCM 2007 on a different server running W2K8 x64 and restored from that backup he made essentially creating a mirrored install but on a x64 OS instead, they then installed SCCM 2012 on the new production server (also W2K8 x64) and finally went into the standard migration steps. This seemed rather convoluted to me, and I found no other posts that claimed there was any need to first mirror your SCCM 2007 from a 32 to a 64bit environment before attempting a full migration to SCCM 2012. Thanks in advance, T