Skip to main content

Watch Out! Telephone Tech. Support Scams

Watch out for a scam that’s on the go at the moment.  It goes like this:

You get called up out of the blue by “Microsoft” or some such reputable-sounding company.  The person who calls you normally seems to have an Indian-sounding accent.  I purely mention the caller’s accent as it seems to be a common feature – you should watch out for this kind of scam regardless of the caller’s accent.  You are told that your computer is infected with a virus or with malware.  You are often asked if your computer has been running slowly or freezing lately.

Of course they’ve got the solution for you!  At this point you’re often transferred to their “superior” or “manager” who tells you of the sorry state your poor computer is in and how they have the means to fix it.  For a fee of course.  This usually seems to range from 120 to 260 euro.

The “fix” seems to involve them getting you to browse to their website and download some remote access software which they then use to take remote control of your PC.  At this point God knows what could happen!  They have remote control of your PC and could install malware, key-loggers, web-cam spy software, anything really.  They could look at your personal data, delete important data or system files, you name it.

What often seems to happen is they get you to look at your event log, tell you that the errors you’re (inevitably) seeing are due to an infection and then remote access your PC and perform a set of fairly pointless tasks such as defragging the hard drive and running Disk Cleanup.  Often they apparently turn of the event-logging service so now you won’t see any more errors appearing!  They then charge you for this waste of time.

Beware!  No legitimate business will contact you out of the blue in this way.  How would Microsoft know you have a virus and take it upon themselves to go and fix it for you?  It’s all a load of nonsense so just hang up and don’t engage with them.

Here’s an example of what can happen:

Symantec sample telephone support scam

Comments

Popular posts from this blog

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

Convert Ruckus AP from Unleashed to ZoneDirector-managed

Here is the method to convert a Ruckus Unleashed AP to one which can be managed by a Ruckus ZoneDirector controller: - Login to https://support.ruckuswireless.com/ - Click "Downloads" - Choose the correct product, e.g. Ruckus R550 - Choose a "standalone" version along the lines of 118.2.0.0.875.bl7 or something similar - Agree to terms and download the software - Connect to the AP's IP address - It should open the setup wizard, showing "Unleashed Installation" - Click "Local Upgrade" - Choose the firmware image file you just downloaded - It will upload, process, and then be ready for upgrade when you click "Yes" - After this, the ZD should detect the new AP - The new AP will then need to be approved - The new AP will then be upgraded to the correct software by the ZD - The new AP will then reboot and should be ready to use - Don't forget that, for the ZD to even detect, let alone manage the new AP, it must have enough licenses

DNS Dynamic Updates & DNS Scavenging

I was encountering an issue at a customer's site where the DNS records of their client PCs often would be behind or out of sync with the records in DHCP.  Usually the IP address would be older in DNS and this was causing issues with scripts executing and network tools correctly resolving client PC hostnames to their correct IP addresses. I realised I needed to make some changes to their dynamic DNS updating configuration.  After a lot of reading through Microsoft's documentation and various online forums, this is what I ended up configuring.  Hopefully this may help someone, some day: - Make the DHCP server a member of the "DnsUpdateProxy" group -  Create a new user account, in the "Users" OU, called "dnsdynamicupdates"   - This new user only needs to be a member of the "Domain Users" group - no special privileges   - Make the password strong and set it to never expire - Set this new user as the credentials used by the DCHP server in IPv4...