Category Archives: تقنيات

by

Move WhatsApp Data to New Android Phone

Why this note?
Because I didn’t find one on the Internet addresses the gap issue.
See, the problem when you use the cloud backup you may not have enough cloud space. And more, between the moment you start the backup, until the backup is completed, you may receive several messages and medias. Which most likely will be lost once you switch to the next phone.

So, here we goes:

  1. Disconnect your Google drive from WhatsApp

Follow this article for the details: https://www.quora.com/If-I-have-both-a-Google-Drive-and-a-local-backup-of-WhatsApp-chats-how-do-I-ensure-WhatsApp-picks-up-the-local-version-to-restore-when-I-reinstall

  1. Get backup of WhatsApp folder to SD or Flash disk, and copy it to the new phone
  2. Install WhatsApp on new phone, and pay attention to the step after activation. If no backup is detected, or if it is trying to restore a cloud backup, then you missed something

Good luck 🙂

by

XG Virtual Firewall on KVM and Openstack ERROR firstboot failed

Yep, no much result on the web about this subject.

I don’t know what the cause, nor why Sophos didn’t take it seriously.

Anyway, if you’ve downloaded version 16 of Sophos XG virtual appliance for KVM and you got the nice error message of

firstboot failed: swapon /dev/swap

But, if you know and sure you’ve done everything right and as per Sophos documents, then most likely you have the same issue we run through.

For some unclear reason we were able to solve this by having the Hyper-V version of the same appliance and run it on KVM platform 🙂

Our team members are testing it now on OpenStack with our service provider to make sure of the compliance.

HTH

by

HAproxy Errors and No Logging

Basically, you’re running HAproxy 1.7.x on Debian/Ubuntu and have no logging under /var/log or you’re getting log files full of errors like:

haproxy-systemd-wrapper [26417] sendmsg logger #2 failed: Connection refused

There are many reasons for this problem, but most of the solutions are related to standard setups, which means if you have version 1.7 by the time this post is published, you’re not getting the binaries through standard apt-get libraries. Thus, you don’t have standard setup 😉

Anyway, if you’ve installed version 1.7 directly, then simply remove it, and remove pointers in apt-get libraries to its source.

Install version 1.6 from the standard libraries, and test the functionality of HAproxy, then test the functionality of the logging.

Finally, you can upgrade to version 1.7 and logs will keep working for you.

Don’t ask me why, I don’t have time to find the root cause 🙂

HTH

by

Change Password on OWA Using UPN

Exchange 2013/2016 OWA allows users to change their passwords, and additionally, helps administrators to force users to change their passwords.
After first login, and when the user tries to use UPN on password change page, OWA will return an error saying username/password combination is not correct. Which is not true, but OWA tells the user to use the format domain\username not the UPN.
This is because the home directory (OWA Virtual Directory) is configured to use that format for authentication. Although it’s ok to use UPN to login, for some reason the DLL file responsible for the password change is not able to tolerate that format.
Changing OWA virtual directory authentication settings to use UPN format will solve this issue for your users.
HTH,

by

Exchange 2016 Readiness Checks Error

I’m not an expert of Exchange, but I wasn’t able to find something clear in the documentation saying I must install new Exchange server (2016) on the same site as existing one (2013) and move it later!

Anyway, the list of errors I got in the Readiness Checks page wasn’t useful at all. However, looking at the ExchangeSetup log file was.

If you are receiving something like:

Global updates need to be made to Active Directory, and this user account isn’t a member of the ‘Enterprise Admins’ group

Or

You must be a member of the ‘Organization Management’ role group or a member of the ‘Enterprise Admins’ group to continue

And you’re sure the account running the setup has these rights, then most likely you’re trying to install the first Exchange server of this version on AD site that has no Exchange servers at all.

My solution, actually it was a work around, was simply to move domain controllers to a site with Exchange servers, remove the subnet from AD Sites and Services, and reboot the new Exchange server.

After 15 minutes, just enough time for AD replication to take place, I logged in again to the server and started the Exchange setup, and it works just fine.

HTH