Search the Community
Showing results for tags 'server 2008 r2'.
Found 4 results
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 everyone, Our company has about 15 physical servers and 30 virtual servers. Due the large amounts of service requests by our colleagues we are behind in documenting the network infrastructure and the servers specifically. If I have to document them all manually it will take at least a full week to complete, so I was wondering if there are any tools for Server 2008 R2 servers to export information. Mainly interested in one or more tools to get the following information: - Network card settings - Disk Management (Disks, size, online/offline, status) - Present network shares - Installed Windows Roles and Features - Page file (location, maximum size) - Device Manager - Installed software (Version, install date, supplier) - Services (all services, their start up type, logon as and status) ANY help in the form of tools that you can provide would be greatly appreciated! Kind regards, Dennis
This is bugging my terribly, I have a 2008 R2 server running AD, DNS, and DHCP. Everytime I restart the box it hangs at "Applying Computer Settings" for anywhere between 5 and 30 minutes, for seemingly no reason. I have looked at logs, and found nothing. I read a bit and thought it may be group policy, so I ran dcgpofix (nothing in GPO as of now anyways) and it made no improvment. Also found some people saying that it was IPv6 was disabled, i've tried booting with it on and off (don't see how that would make a difference anyways) and nothing changed. I then found a KB http://support.microsoft.com/kb/2004121 about this, and tried that registry key hack, with no avail (turns out it doesn't work the same way in R2 as it did in R1). Any suggestions or advise that I should try? It's ridiculous that it sits there using no more than 1% CPU, no disk activity, and no network and takes up to 30 minutes to get off that screen.Help! Thanks!
Hi guys, I stumbled across this site through google and I think this might be the best place for me to ask some broad (as well as some very pointed) questions about the whole thing. First off, this acronym soup is killing me. I've got a pretty healthy list of things I need to remember now. With that being said, here is what I currently am doing to deploy Windows 7 to our computers (Mostly Dells): 1. Use MDT to add applications, out-of-box drivers (organized into Operating system, then machine model), and a custom task sequence to rename the primary partition "Local Disk". 2. Add the Lite Touch iso created by MDT into WDS. Do a normal WDS deployment via PXE So my questions really are these: 1. Is this a reasonable way to do it? 2. How can I improve it to make it as automated as possible? 3. Where does WSIM come into play? I would love to be able to define some settings, but also they very from computer to computer slightly. Can I create multiple autounattend.xml files that all use the same install.wim file? 4. How can I set the computer name automatically to be the dell service tag during install instead of declaring it during the Deployment Wizard? 5. How do I update my install.wim file with new Windows Updates offline (by NOT installing Windows onto a reference machine and capturing a new wim file)? 6. In a general sense, can I continue to do most things in MDT and then use WDS to actually push the OS out? Is that the standard method? Thanks! Brian