Epson Workforce WF-3640 Keeps Going Offline

My Epson WF-3640 printer kept going offline, even though it was turned on, and connected to my local LAN. I could even use it to scan documents, but I just could not print with it. If I checked its status in Windows, it would show that it was offline:

 

Not only that, each time Epson's software updater did an update, it could not find the existing printer, so it added another copy of the Epson FAX printer.

The cause of this problem is that Epson printer driver installer installs the printer with a standard TCP/IP port. But when the printer's TCP/IP address changes, Windows will no longer be able to find the printer. You can right click on the printer, select "Printer Properties", and then go to the "Ports" tab to verify this:

I suppose that you can assign the printer a static IP address. But usually this would be too much of a hassle.

It turns out that Epson has a printer port software called "EpsonNet Print". You can google for it, or you can just go to the link http://support.epson.net/win7/updates/network/001_dl.html and download the software there. If you install the Epson printer software combo, it would probably include this as well. But because the date on the combo software is older than the printer driver, people would likely not install this software combo.

Once the EpsonNet Print software is installed, you can add a new port of the type "EpsonNet Print":

 

This port will work with whatever IP address the Epson printer happens to be on. You would then repeat this for the Epson WF-3640 Series (FAX) printer, and then delete all the other copies.

From here on, each time the printer is turned on, it will always be shown as "online" in Windows.

Move Resource Group to a New Subscription on Azure Cloud

I have all of my resources in a single resource group. When I tried to move this resource group to a new subscription, I got an error saying that "Move resources specified storage account(s) yourStorageAccountName are not found with sourceSubscription..., sourceResourceGroup yourTargetResourceGroup, targetSubscription..., targetResourceGroup yourSourceResourceGroup."

It turned out that you cannot move all resources in a resource group at once if they are not in the same region. Some of my resources are in the region US West, and some are in the region US West 2.

So, I first selected all resources in the region US West 2, and moved them. After the move was done, I selected all of the remaining resources in the region US West, and moved them as well.

Everything went without any errors.