New WSUS server same name

I setup a new WSUS server and then changed name of old one to something else and then renamed new one what the old one was. None of the clients are connecting to new WSUS server even though the GPO should be pointing to correct name. Is there something else
I have to do in order for PCs to sync now?

Hi Jason,
Agree with Daniel.
Besides, do you install the WSUS on Windows Server 2012 R2? If yes, have you change the port in the GPO? WSUS server has changed the default port in Windows Server 2012R2.
On WSUS 3.2 and earlier, port 80 for HTTP and 443 for HTTPS
On WSUS 6.2 and later (at least Windows Server 2012), port 8530 for HTTP and 8531 for HTTPS
Best Regards.
Steven Lee 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 Support, contact [email protected]

Similar Messages

Migrate WSUS server from 2003x86 to 2008x64, new hardware, use same name and IP address?

Searching through the WSUS forums and reading the TechNET migration documentation, I have bits and pieces of information to make this a smooth transition...I think. I have a plan in mind but
would like the communities input on what I am thinking before moving forward and having it blowup in my face :). <o:p></o:p>
I have the following currently:<o:p></o:p>
A single WSUS 3.0 SP2 server, running on Server Win2003x86, using the default WID (susdb.mdf) on the same server. I have SQL 2005 Express installed on this server as well for other services
but this has no bearing on the WID correct?<o:p></o:p>
What I would like to do:<o:p></o:p>
I have a new server (a much better one) that I would like to move WSUS on to, that will be running Server Win2008x64 (I have to setup first). <o:p></o:p>
Steps that I would like to follow:<o:p></o:p>
1. I will go through and setup this new server with all M$ updates etc... under a new name (ex. wsusnew) and DHCP acquired IP address and then power it down. <o:p></o:p>
2. Get on my current WSUS server and backup all current WSUS settings, groups, DB etc... to a network location for temporary storage. Then power it down.<o:p></o:p>
3. Delete the current WSUS server computer object in AD, DNS entry I will leave because my intension is to give the same IP address to the new WSUS server.<o:p></o:p>
4. Start the new server, static assign the IP address from the old WSUS server to this new server and then change the name of (wsusnew) to the old servers name, which should be ok sense I deleted
the AD object in step 3.<o:p></o:p>
5. After the obvious restart, the new server will have the same name and IP address as the old server. <o:p></o:p>
6. Now that the new server is up (with same settings name/IP as old server), I will then go through and install the WSUS role on the server and restore my WSUS information.<o:p></o:p>
Questions:<o:p></o:p>
1. Step 2 above, is it possible to do this, without making replica servers? I kept reading about this as I was researching doing this, I would rather just copy the DB and folders and simply
put them in-place on the new server.<o:p></o:p>
2. Step 6 above, restoring of the data, what is the proper way to do this in the scenarioI described? <o:p></o:p>
Thank you to anyone who can provide me some information.
Jeff

Thank you for the reply, I will follow and let you know. Proabably be next week sometime before I'm able to try though. So look for a reponse then. Thank you again.
Jeff
OR...
You can use the much more simple, much more reliable, and much more proven method of:
Install new server as a replica of the old.
Replicate.
Configure new server as upstream server.
Point clients to new server.
Turn off old server after all clients have redirected to the new server.
For everybody that has tried the backup/restore the database procedure described above, they have encounted complications of one form or another.
WSUS has a built-in and fully supported comprehensive replication capbility. use it! :-)
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

Clients not updating from new WSUS server

I had 2 DCs in place running 2008 and 2003. The 2003 server was also running WSUS. It has been replaced with a 2012 R2 Essentials server which is now the FSMO holder and I installed WSUS on it using the standard options like I always do. Administration
runs on 8530.
I updated the GPOs with the new server's name. All clients can ping the WSUS server by name. All clients are reporting to the server and updates have been approved days ago. However none of the clients, including the server itself, are seeing any new updates
available even though the WSUS console shows they are reporting.
I've searched the registry of the 2008 DC for references to the old WSUS server and none were found. I looked in the registry key where you would find the value put there from the GPO and it correctly shows the current WSUS server.
I looked in the windowsupdate log on the 2008 DC and I don't see any errors. So I'm stumped as to why the clients can at least see the WSUS server and report to it but they aren't seeing the approved updates. Any ideas?
Jonathan

Hi Jonathan,
Have you checked if the update is downloaded successfully? The update will not be available until it has been downloaded on the WSUS server.
Best Regards.
Steven Lee 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 Support, contact [email protected]
Yes the updates have all downloaded as verified in the WSUS console. So the updates are there, the clients are reporting in and showing what updates they need, but what is not happening is that final connection so you see the little "pending updates"
icon in the system tray. I've done wuauclt /detectnow many times (used to doing this with other sites I manage) and had WU check for updates but it always shows none available.
Jonathan

Testing updates with a new WSUS server

We recently created a new WSUS server and added a test target group consisting of 6 test PCs. My question is if I approve updates tonight to just the target group, will I be able to push out those same updates to our staff PCs next Thursday? (We typically
approve updates on the 4th Thursday of the month for a 3:00am Friday install via our WSUS GPO.) Or will the staff PCs miss out on this month's updates due to the test push? I.e.: is it "one and done" with the approved updates.
Thanks
Hank Vare

A couple of thoughts to share....
First, with respect to your approvals. This is exactly why target groups exist. So if today (Thursday) you approve updates for the target group, then the computers in that target group will get these updates sometime over the next 24-48 hours (depending
on a lot of variables that affect the process from the time of approval to the time of installation). When you're ready to deploy them to more systems, you just ADD the approvals for the extra target group(s) that contain the additional systems.
Second... approving updates on Thursday for a 3am Friday installation is a procedure likely doomed to some percentage of failure. In fact, if you've already been doing this I'm surprised it hasn't already happened. So let's dive into some of those "variables"
I mentioned in the first paragraph and better understand the risks.
When you approve the updates, they have to be downloaded from Microsoft. That takes some amount of time.
AFTER the updates are downloaded from Microsoft, the client has to "check in" with the WSUS Server to see if there are any new/available updates to download. That "check in" could occur at anytime up to 22 hours AFTER the updates have
been downloaded (which, right here, already blows the 3am target).
When the client has discovered available update to download, then it actually has to download them AND the download has to complete before 3am Friday, or those updates will not be scheduled for installation at your weekly event.
NOW.. having said that, introducing a TEST GROUP may actually mitigate some of that risk -- unless your test group is also scheduled to install updates ONLY on Friday at 3am, in which case, some of your test group might not get any updates at all.
As a general rule, your initial approval of an update should be at least 48 hours in advance of the time in which you want the clients to actually install the updates. This gives the WSUS server several hours to download the updates, it accounts for the
up-to-22-hours that may lapse before the client discovers the updates as available, and it gives the client several hours to download the updates from the WSUS server, so they are on the local machine prior to the scheduled installation time.
Additionally, if there are downstream/replica servers involved in the environment, you'll need to add another 48 hours for each level of replication -- because replica servers get updates exactly like clients do.
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.

Delete existing RecordStore and then open a newer one with same name

Hey All,
I'm working in J2Me for Nokia S40 DP2.0 SDK 1.0.
I want to delete my existing RecordStore (i. e; Products) and then open a new RecordStore as same name(Products) But
There is an Exception thrown that RecordStore is Open;
my deletion process is given below :
public void deleteRecStore(String recordName) {
if (RecordStore.listRecordStores() != null) {
try {
RecordStore.deleteRecordStore(recordName);
} catch (Exception e) {
e.printStackTrace();
public void createRecStore(String recordName, Vector data, int insertType) {
if(recordName.equals("") && (recordName != null)) {
try {
if(insertType == this.NEW_REC) {
rs = RecordStore.openRecordStore(recordName,true);
this.closeRecStore();
this.deleteRecStore(recordName);
rs = RecordStore.openRecordStore(recordName,true);
Can anybody pls help me...
why I can't open a new recordstore like this ??
If there any process then what is that ???
Rania...

This question belongs in the [CLDC and MIDP forum|http://forums.sun.com/forum.jspa?forumID=76]. I'll move it there in an hour or so.
I would suggest that in addition to printing the stack trace of any Exception, you could append the Exception.toString() to a Form (or display it in an Alert) to see whether any exceptions are being thrown.
db

Why won't my clients register with my new WSUS server??

Hi All,Been running WSUS 3.0 SP2 on Server 2008 for a good few years now (originally moved away from it running on Server 2003 when I first started in my current role), and a couple of days back, I finally got round to throwing up a new 2012 VM with the WSUS role installed...When I moved clients from the 2003 WSUS to the 2008 instance, literally all I did was change the intranet location in the GPO I had created for WSUS to point to the 2008 server, and voila! Clients started reporting in within a few hours!This time, it's been 2 days now, and even though I've changed the GPO, and verified that it has updated on the clients by using GPResult, none of them have contacted the new WSUS server yet...I've tried running wuauclt with the /detectnow and /reportnow switches, and nothing.How exasperating!
This topic first appeared in the Spiceworks Community

Hi All,Been running WSUS 3.0 SP2 on Server 2008 for a good few years now (originally moved away from it running on Server 2003 when I first started in my current role), and a couple of days back, I finally got round to throwing up a new 2012 VM with the WSUS role installed...When I moved clients from the 2003 WSUS to the 2008 instance, literally all I did was change the intranet location in the GPO I had created for WSUS to point to the 2008 server, and voila! Clients started reporting in within a few hours!This time, it's been 2 days now, and even though I've changed the GPO, and verified that it has updated on the clients by using GPResult, none of them have contacted the new WSUS server yet...I've tried running wuauclt with the /detectnow and /reportnow switches, and nothing.How exasperating!
This topic first appeared in the Spiceworks Community

Export Approuved Update from old server WSUS to the new WSUS server

Hello,
I want to export all update approuved from one old WSUS server to one new WSUS server
Can you help me please ?
Best Regard

Hi,
>>I want to export all update approuved from one old WSUS server to one new WSUS server ?
There are three steps to exporting and then importing updates:
Make sure that the options for express installation files and update languages on the exporting server are compatible with the settings on the importing server. This ensures that you collect the updates you intend to distribute.
Copy updates from the file system of the export server to the file system of the import server.
Export update metadata from the database on the export server, and import it into the database on the import server. The last section explains how to import exported updates to a replica server
Here is the official solution:
https://technet.microsoft.com/en-us/library/cc720486(v=ws.10).aspx
Best Regards.
Steven Lee 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 Support, contact [email protected]

New WSUS server optimization

Hi,
I have an opportunity to deploy a new WSUS 3.0 SP2 ( 2008 R2 server) from scratch.
I enabled the Sync / classifications and Product list that i need to patch.
(XP , Win 7 , Server 2003 , Server 2008 and server 2008 R2 -- Security , critical and updates)
Language English
Now this got me around 6392 Updates that i see as Unapproved and status Any View.
I need to keep the stuff clean from the offset
1.So what should i approve for install
2.What should i decline
3.When should i run server cleanup wizard
Any strategy

1.So what should i approve for install
That really depends on the current patch state of the clients of this WSUS server. For starters, you should not approve any updates that are not already reported by clients as NEEDED. Second, you should not approve any superseded updates. Beyond that, however,
there may still be additional updates that you should approve.
2.What should i decline
When you get to the point that superseded updates are reported as 100% Installed/Not Applicable, then you should decline those updates. In addition, you can also decline anything you'll absolutely never need, such as Itanium updates. Also, if you're synchronizing
Windows Server 2008 and Windows Server 2008, you're getting both x86 and x64 updates. You may or may not need updates for any one of those four platforms.
3.When should i run server cleanup wizard
At least once a month, but only if performed in conjunction with other required administrative procedures.
Any strategy
Removing unneeded update approvals
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.

New WSUS server not showing computers correctly.

Hi All,
I've recently migrated WSUS servers and everything has come intact apart from the grouping. The groups have come over but all the computers are showing under 'Unassigned Computers'.
I've manually removed and added a number of computers but it doesn't show any computers.
Thanks

Hi,
I've only just taken over setting up of WSUS from my colleagues and he's setup computer groups in WSUS and adds the computers to the groups via Active Directory Users and Computers.
The WSUS GPO only sets
Allow non-administrators to recieve update notifications
Allow signed updates from an intranet Microsoft update service location
Configure Automatic updates (Configure automatic updating, Scheduled install day, scheduled install time)
Enabling Windows Update Power Management to automatically wake up the system to install scheduled updates
Specify intranet Microsoft update services location (Set the intranet service for detecting updates, set the intranet statistics server)
Turn on recommended updates via Automatic Updates
Turn on Software Notifications.
Not sure how much help that is!
Well, that is your issue then, if you are using client side targeting with the WSUS Server you will need to place the WSUS Group in the Group Policy. Here is a good technet article to get you started.
http://technet.microsoft.com/en-us/library/cc708574(WS.10).aspx
Hope this helps.

Automator and applescript to copy new files in a folder with same name as parent folder

I have an iMac with a pictures folder (Finder folder) containing several subfolders with pictures. As per now, all these subfolders are imported into an iPhoto library (and the structure of the Finder pictures folder is thus maintained: The iPhoto events are named the same as the Finder subfolder). I.e. I have not created any albums in iPhoto.
I have also set up a workflow, where new iPhone photos are automatically being synced to specified Finder folders within the iMac pictures folder. So what I want to do is to make a workflow to import potential new photos from week to week into the existing iPhoto structure. I know iPhoto has this Autoimport folder, so this one is unpacked and "mapped". So, this is what I´m hoping to do:
Automator (iCal - want to do this on a weekly basis):
- Get specified Finder items -- set to target folder = iMac pictures folder
- Get folder content (with subfolders)
- Filter Finder items
     - Items from the last 7 days (which then would be any new files created last week)
- Applescript/shell script loop(?)
     - Get folder name for each file´s (from previous step) parent folder
     - Create new folder with same name as the file´s parent folder (if not already existing) under the iPhoto Autoimport folder
     - Copy the given file into the folder from above
- Run iPhoto application (Automator task), which then should just auto import the new photos according to the Finder folder structure
Whith the workflow above, I aim to maintain the existing iPhoto structure, and just import new photos into the existing structure. Creating folder names under the Autoimport, similar as the existing Finder folder names / iPhoto events should make it possible to have the new files imported under the existing event, right?

Anyone?
I have now switched to Aperture (from iPhoto) due to Aperture´s capability to handle Finder folder structure, and due to the possibility of having the pictures within Aperture as referenced files to the pictures within the Finder folders (i.e. possibility to delete pictures from both library and Finder folder at the same time).
So I have a superior Finder folder called "Album". Within "Album" I have several subfolders (sub albums) containing pictures. The "Album" folder with subfolders are imported into Aperture as "Projects and albums", and the pictures are uploaded within the Aperture structure as referenced files. So for now the Aperture structure is more or less a direct mirror of the Finder folder structure, whereas "Album" is the project.
And this is my current workflow in Automator, but I´m searching help with my Applescript:
- Get specified Finder items (target folder = the superior Finder folder "Album")
- Get Folder content
- Filter Finder items (to look for potential new files to import into Aperture)
     - Kind is not folder
     - Date created last X days
The output files from this task enters an Applescript
on run {input, parameters}
       repeat with f in input (**Loop**)
               tell application "Finder"
                      set fileName to name of (f)
                      set parentFolder to name of container of (f)
                      tell application "Aperture"
                             tell library 1
                                    tell project "Album"
                                           if (exists album parentFolder) then
                                             ** I then would like to check if fileName already exist within the existing album**
                                             ** If not existing, I would like to import file f into the existing album as a referenced file**
                                           else if not (exists album parentFolder) then
                                                   make new album with properties {name:parentFolder}
                                            ** I then would like to import file f into the new album as a referenced file**
                                           end if
                                    end tell
                             end tell
                      end tell
               end tell
       end repeat
end run

Best way to replace WSUS Server that isn't working?

Hi, this is a followup (aka admission of defeat) to the post linked below. Our SCCM installation was done in a hurry by one of my Coworkers about two months ago, and there are a few areas which are incomplete.   One of them happens
to be software updates.   I have spent a great deal of time trying to troubleshoot why our clients aren't updating, and am realizing that my time might be better spent just replacing the WSUS server.
Our setup: All servers are hosted on Hyper-v. SCCM 2012R2 is on server 2012R2. The sql server runs on sql server 2012, on seperate 2012R2 machine. WSUS is currently set up on a 2012 R2 machine, but it isn't working. The WSUS
server is configured to use the same SQL server instance as the SCCM server.
If I take the step of replacing the WSUS machine, what would the best path be? Should I:
Remove the software update point site system role as as described at the end of this document,
http://technet.microsoft.com/en-us/library/gg712312.aspx    then just turn off the current wsus server?
If so, do I need to worry about the SQL server, or can I just go about configuring a new WSUS server and adding it back in to SCCM?
If anyone can point me to their favorite list of step by step instructions for getting software updates working with SCCM, I'd appreciate it.
Thanks,
Kevin
My post from yesterday:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/b07516e4-757e-4ba8-889f-a33374a2c370/updates-not-applying-scan-failed-with-error-0x80072efd?forum=configmanagersecurity

Yes, Thank you! I did reinstall WSUS on a new server, which turned out not to be the root of my problem (Although, confirming that it was done properly was worth the time).
After reinstalling WSUS, I was still getting the error:
Group policy settings were overwritten by a higher authority (Domain Controller) to: Server and Policy NOT CONFIGURED WUAHandler 4/9/2014 5:43:01 PM 3344 (0x0D10)
After a bit more searching, I found someone suggesting setting the "Allow signed updates" group policy to not configured, in addition to the "Specify intranet Microsoft Update Service Location".
I also read that the SCCM client will take care of most update settings, so I also set "Configure Automatic Updates", and "Turn on recommended updates via automatic updates" to Not Configured, and my Endpoint Protection began updating nicely.
Thanks for pointing me to Gerry's site, it's a great resource!
Thanks also for helping.
Kevin

Upstream WSUS Server and Sync

Hello,
Environment : 1. Server 2008 R2 Main Upstream server, hosts update content locally, SQL DB on another system.
2. 2 - Server 2008 R2 downstream servers, host update and sql content locally.
We had our Main Upstream WSUS server crash after applying KB2734608-x64 on a Server 2008 R2 box. Our database resides on a different SQL server on the same domain. When we tried to launch the WSUS interface the mmc console
it would crash. ( MMC has detected an error in a snap in and will unload it. was the error). Looked at the logs and it seems like it could not connect to the database. Anyways after trying many fixes, i decided to re-install WSUS until it got to the point
where it would not allow me to re-install got errors in the log of " InstallWsus: MWUS installation failed ( error 0x80070643: fatal error during installation with other ones like CInstallDriver and CSetupDriver:.....blah blah). I was messing with the
back end database and accidentally deleted it, so i had to restore the latest backup from a month ago ( we typically back on a weekly basis with incrementals, but our backups where failing and we didn't know of this because of a complicated situation
with our client..anyways). My question is once i get the WSUS connected backup what can i expect from the downstream servers in terms of Synchronization? I am assuming initially we will have re approve all updates on the upstream server, before the downstream
server successfully sync? I know i have to recycle the WSUS application pool and reset the update content, anything else? Also any advice on installing that patch? We initially tried to install it because some clients were not reporting into the console properly.
( I know we are on a downward spiral here, any help is appreciated. Will probably end up rebuilding the VM from scratch re-installing WSUS )
Server 2008 - MCITP, Server 2012 - MCSA

Because you had previously attempted the installation of KB2734608 on the WSUS server, it's likely that the database schema has already been modified, making it impossible to connect a downlevel WSUS server to that database. It's unfortunate that you uninstalled
WSUS (probably not necessary and notably complicates the situation), but c'est la vie.
Of course, apparently all that is also irrelevant since you also trashed the back-end database and restored it, so now that database does not have the schema mods imposed by KB2734608.
So, once you get this new WSUS server installed to the restored database, the downstream servers (where I presume you have not yet installed KB2734608 since this update must be installed from the top down) will just keep on truckin'. The only updates you'll
need to approve are the ones that were approved since the last database backup (which hopefully was after you approved this month's Patch Tuesday updates, otherwise you'll likely have a fair amount of work to be done).
Successful synchronization is not a function of the state of the approvals on the upstream server, but if there are any updates NotApproved on the upstream server that were previously approved, a replica server will lose those approvals and client systems
won't get the update until it is (re)approved, the replica resynchronized, and the client performs another detection to (re)find that (new) approval.
I don't know where the "recycle the app pool and reset the update content" stuff is coming from. You're installing a new front-end WSUS server onto an existing database that's already functional. No other actions are required.
As regards successfully installing KB2734608, I suggest thoroughly reading the KB article for starters... TWICE!
First requirement of successfulling installing this update is having a healthy
WSUS server. Not sure why your particular installation failed (installation failures of KB2734608 are pretty rare, as opposed to those encountered by KB2720211), but they're almost always related to existing dysfunctions within the WSUS server.
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.

Agent install with replacement machine with same name

we replace old workstations with new ones with same name, SCCM does not update, it still shows the machine with an active agent, but it never gets installed on the new machine. what do I need to do to get the agent on the new machines?
Pat

Hi,
If you are trying to use autimatic client push it will not install the client that scenario as the computername is already active in SCCM. You could use a startup script in a GPO to always make sure that the client is installed on all computers, Jason Sandys
has written a great one, you can find it here..
http://blog.configmgrftw.com/configmgr-client-startup-script/
In the scenario above you also risk getting a duplicate in SCCM as the new computer with the old name has new hardware.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Moving from 10gR2 Db on Unix (Tru64) to a new Linux server (10gR2)

Hi,
We are planning on moving our oracle 10gR2 Db on Unix (Tru64) to a new Linux server (same database 10gR2). Interested in discussing the easiest way for a newbie to get the data over to the new box. We currently perform a 'COLD" backup and have no transaction logging. The database is a data warehouse so stopping the database and backing up the files is not a issue. The database size is 500GB.
The Oracle ADDM on our current box is showing "individual database segments responsible for significant user I/O". There is a tablespace with about 30 separate data files that need to be "reorganized"!
Should we perform the reorganize before the migration or after on the new faster box?
What is the easiest way to do this for a newbie? Thanks.

Since your source and target platform all little ENDIAN format. Cold copy from OS level is fastest and easiest way.
If you plan to reorg the tablespace along the way, you have to do export/import, use data pump since you are on 10g.

What is my WSUS server doing?!

Hi All,Rolled out a new WSUS server last week, and I've been running around trying to get all my clients fully updated...I've changed my WSUS reporting frequency from 22hrs to 2hrs via GPO, and this has taken effect, so I can see a clearer picture in the interim, whilst I get everything updated. However, I notice that, for instance, our single remaining XP machine reports to WSUS that it still has 26 updates outstanding... Now, I have installed all updates that have come from WSUS on this machine, and I have forced it to reportnow and detectnow, and I have read the WindowsUpdate.log, which tells me that it successfully connects to WSUS, and finds no updates available. I have also taken the XP machine to Windows Update manually and downloaded ALL available updates (there were 3, not 26!) and it has since reported into WSUS,,,Yet it...
This topic first appeared in the Spiceworks Community

Migrating your database to a new datacenter can be a high-risk and time-consuming process. A database contains state, and can be much harder to migrate as compared to web servers, queues or cache servers.In this blog post, we will give you some tips on how to migrate your data from one service provider to another. The process is somewhat similar to our previous post on how to upgrade MySQL, but there are a couple of important differences.
This is the seventh installment in the Become a MySQL DBA blog series. Our previous posts in the DBA series include Database Upgrades, Replication Topology Changes, Schema Changes, High Availability, Backup & Restore, Monitoring & Trending.MySQL Replication or Galera?Switching to another service provider (e.g., moving from AWS to Rackspace or from colocated servers to cloud) very often means one would...

New WSUS server same name

Similar Messages

Maybe you are looking for