Digi - Check Call Diverts

How to check for "Call Diverts" settings on your own phone for Digi Telco only.

A. Call Forwarding.

1. To check call forwarding status : Press --> *#21# --> Dial.
2. You will receive a MIM message from Digi on the status.

3. To cancel all forwarding : Press --> ##21# --> Dial.
4. You will receive MIM message again on the cancellation.

B. Forwarding to Voice Mail when "Unreachable".

1. To check status : Press --> *#62# --> Dial.
2. To cancel : Press --> ##62# --> Dial.

C. Forwarding to Voice Mail when "Busy".

1. To check : Press --> *#67# --> Dial.
2. To cancel : Press --> ##67# --> Dial.

D. To cancel all types of forwarding : Press --> ##002# --> Dial.

!!! HAPPY COMPUTING !!!

Windows 10 - Latest ISO Download

As Windows 10 kept on updating their version and my notebook have been configured to automatically run "Windows Update" periodically its no surprise that my notebook is updated to the latest version (1803) and build.

But sometimes I do need to perform a clean install of Windows 10 and it makes no sense to install an older version and run the updates via internet to make it up-to-date. It will be best to install the latest version & build from the start, luckily Microsoft do provide the downloads of ISO file format thus making our life more easier.

1) The link of the download here : https://www.microsoft.com/en-au/software-download/windows10

2) You will see the below website, just click the "Download tool now" button as shown. There's no indication which version of Windows 10 you will be downloading and as such I assumed that its the latest version (as of publishing the latest version is 1803).

3) You will be prompted to either "Run" or "Save as" option, for my case I preferred to save it locally first. The tool is small in size (about 18.7MB), once the download completed just run the tool.

4) When prompted by UAC, just click "Yes" button to continue.

5) The tools will start the loading process (ensure that your computer is still connected to the internet), please be patience and wait for it to load.

6) You will need to click "Accept" button to agreed to the license terms.

7) On the next screen, select option "Create installation media (USB flash drive, DVD or ISO file) for another PC" and proceed to click the "Next" button.

DO NOT choose "Upgrade this PC now" as this will upgrade the current computer to Windows 10, so choose correctly.

8) Now select the correct "Language" and "Architecture" that you want to download and click "Next" button to continue.

PS: You may need to "Deselect/Untick" the option "Use the recommended options for this PC" to be able to select the language, Edition & architecture.

9) Now select "ISO file" option and click "Next" button.

If you choose "USB flash drive" option you will be prompted to insert a blank USB flash drive with at least 8GB of capacity, this option will be very slow and time consuming thus not recommended at all.

10) You will be prompted to the location to save the file, choose your preferred download location (eg. C:\Downloads), you may also rename file to something more appropriate and recognizable (eg. Win10_1803_x64.iso) and proceed to click the "Save" button to start the download process.

11) The download is starting, the file size of my copy is about 3.46GB and depending on your internet speed the download time may varies.

12) Once the download completed, you can use your preferred methods or media type for the installation, such as burning it to a DVD disc or use a 3rd party tools to transfer & make it bootable on a USB flash drive (eg. Rufus-3.1.exe).

Do take note that the ISO file downloaded is from Microsoft's website directly thus I'm pretty sure its safe and free from viruses, but due to the instability of my internet connectivity I have downloaded the file twice just to ensure its free from corruption (aka missing packet) and scan it with anti-virus of my own.

Also the download doesn't contains any CD-Key inside (don't ask me for it), as long as you are using a valid OEM license (usually embedded into your computer's UEFI) the activation is automatic upon detection of internet connectivity. If you have a Retail license then you already have the key, just key-in and activate it normally.

For other licensing like VLK/MAK, please refer to your IT Administrator for the activation (but be prepared to answer some questions on why you need it). That's all for now and thanks for reading.


!!! HAPPY COMPUTING !!!

Notebook - Samsung Keyboard Dock AA-RD7NMKD (Disassembly)

It's been sometime now since my last posting, it was due to my heavy workload at that time and coincides with the hand-over exercise to my replacement (I've moved to new company) :)

A friend of mine recently requested my help on checking his Samsung Tablet/Notebook (XE500T1C) and the Keyboard Dock (AA-RD7NMKD), he told me that the keyboard & the touchpad no longer works after an upgrade to Win8.1 version. Now based on my understanding that any OS upgrades will usually breaks the original drivers, however this was not the case even after I've reformatted it thus my troubleshooting went hardware side.

1) This is the how it looks like (before disassembly).

2) At the bottom, remove those "Rubbers Stand-Off" as circled in the picture.

3) After removing it will reveals the hidden screws as shown here.



 

 

4) After removing those hidden screws, you will need to "slowly peel-off" the cover, try not to breaks any of the inter-lock mechanism.

 

 

5) The inside view of keyboard docking unit.

 

 

Upon checking the hardware and cables, all components was in working condition. It seems nothing is wrong here but once I go in-depth diagnostics... I've found the I/O chip is faulty as shown below here.

 

 

With this chip malfunction, it have affected the following components :-

 

• Keyboard
• Touchpad
• USB ports (all ports)
• Lid Sensor

The only components that is still working is the charging module, due to lack of tools and resources to get a replacement chip, I was unable to repair/replace that faulty chip..... sadly.....

 

I've no choice but to inform my friend to either use an USB or Bluetooth Keyboard & Mouse for his daily use and since the tablet is still in good condition (albeit the faulty docking unit) he can still use the touchscreen and the stylus for his work.

 

Note : Always be extra cautious when performing disassembly of an aging notebooks/tablets etc. As over the time those covers, inter-locking mechanism, rubbers etc. will tends to break-off or cracks easily due to hardened & aging plastics.

 

 

!!! HAPPY COMPUTING !!!

 



Windows 7/10 - Printer Sharing (A policy enabled on your computer that blocks Windows NT 4.0 kernel drivers)

Recently I've encountered a very weird and odd problems when performing printer sharing in Windows 7/10.

The Windows 10 (aka PC-1) is connected with a new HP LaserJet Pro M402dn via a USB cable, the drivers installed without any problems and sharing was configured with correct credentials and permissions.

Now the problems occurs on a Windows 7 (aka PC-2) which need to use that new printer and since its networked the sharing should have no problems, but there's where I encountered the problems. It kept on prompting the same error message "A policy enabled on your computer that blocks Windows NT 4.0 kernel drivers...."

I was surprised on this error, as there's no policy configured for such blocking on both of the computers. Well, I will just go have a look in the local GPO and there's nothing configured on the kernel thingy.

Well, "Googling" was my next choice and found out that this was a common problems for Windows 7 which are not properly patched. Well doing a full patching will waste my time thus I go for more shorter time workaround which was a very simple steps :-

1. Open --> Services.

2. Browse for --> Print Spooler --> and Stop it.

3. Next, open Windows Explorer and browse to --> C:\Windows\System32\spool\drivers folder.

4. Inside the folder contains 2 folders called "W32x86" and "x64" folders, now you will need to rename both folders to another. I just add a ".old" to them, which end up to "W32x86.old" and "x64.old" folders name.

5. Now, go back to "Services" and START back the "Print Spooler" service.

6. Next is add the shared printer manually, by either creating a "Local Port" (eg. \\[Hostname]\[Printer 's Shared Name]) or by IP Address and manually point it to the correct drivers.

Simple as that and it only takes me 5 minutes.

HAPPY COMPUTING !!!

Windows 10 - Install .NET Framework 3.5 (Offline Method)

Windows 10 have been released for quite sometimes now, for those who involved in creating a master image (reference image for mass deployment) find it some features was not enabled by default and vice versa.

Sadly, some drivers or applications required the use of .NET Framework 3.5 (includes .NET 2.0 & 3.0) to works correctly.

Some applications may have bundled the offline installer together while others doesn't and I find troublesome to connect to internet to download the installer (which took me about 20 mins to complete & time wasting).

Actually the .NET Framework 3.5 was already inside the Windows 10 DVD but it was not installed by default. I find this to be odd as when you enabled the features via the "Programs and Features" menu, the wizard will still connects to the internet instead of searching for it in the DVD itself.

Follow these steps to install the .NET Framework 3.5 (includes .NET 2.0 & 3.0) from the DVD source :-

1. Ensure the Windows 10 DVD is inserted then run the "Command Prompt" as administrator.

2. Type in the following command --> dism /online /enable-feature /featurename:NetFX3 /All /Source:E:\sources\sxs /LimitAccess

Note : the [E:] drive corresponds to your DVD drive letter and may differ from your computer.

3. Please be patience and leave it to run until complete (as shown below).

4. After completion you can now check it via the "Programs and Features" menu, the ".NET Framework 3.5 (includes .NET 2.0 & 3.0)" features is now selected and enabled.

5. You might need to restart your computer before continue any drivers or applications installations.

!!! HAPPY COMPUTING !!!

Windows 10 - Remove Provisioned Apps

This is my second post about Windows 10 built-in apps (Provisioned Apps), some of us just don't like the built-in apps... just like the ridiculous Xbox apps which I find it to be best at hogging system resources.

Now my last post was to remove those built-in apps, but later I found it was still in Windows 10 when another user logged-in. After much googling and studying MSDN and TechNet, I found a powershell script and I wrote some sample of my own.

First of all, you still need to run the previous powershell script to ensure that all users are not provisioned with the built-in apps, just in case I have re-posted those script here for your references.

Get-AppxPackage -allusers *3dbuilder* | Remove-AppxPackage Get-AppxPackage -allusers *windowsalarms* | Remove-AppxPackage Get-AppxPackage -allusers *zunevideo* | Remove-AppxPackage Get-AppxPackage -allusers *officehub* | Remove-AppxPackage Get-AppxPackage -allusers *skypeapp* | Remove-AppxPackage Get-AppxPackage -allusers *getstarted* | Remove-AppxPackage Get-AppxPackage -allusers *zunemusic* | Remove-AppxPackage Get-AppxPackage -allusers *solitairecollection* | Remove-AppxPackage Get-AppxPackage -allusers *bingfinance* | Remove-AppxPackage Get-AppxPackage -allusers *bingnews* | Remove-AppxPackage Get-AppxPackage -allusers *people* | Remove-AppxPackage Get-AppxPackage -allusers *windowsphone* | Remove-AppxPackage Get-AppxPackage -allusers *commsphone* | Remove-AppxPackage Get-AppxPackage -allusers *bingsports* | Remove-AppxPackage Get-AppxPackage -allusers *windowsstore* | Remove-AppxPackage Get-AppxPackage -allusers *bingweather* | Remove-AppxPackage Get-AppxPackage -allusers *xboxapp* | Remove-AppxPackage Get-AppxPackage -allusers *twitter* | Remove-AppxPackage Get-AppxPackage -allusers *office.sway* | Remove-AppxPackage Get-AppxPackage -allusers *xboxonesmartglass* | Remove-AppxPackage Get-AppxPackage -allusers *messaging* | Remove-AppxPackage

Note : You can choose which apps you want to retain back. 

After you have completed the above script, now you can run the 2nd script as below, also you can choose which apps you want to retain back.

Remove-AppxProvisionedPackage -online -packagename Microsoft.3DBuilder_11.0.47.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.BingWeather_4.9.51.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.Getstarted_3.11.3.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.Messaging_2.7.1001.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.MicrosoftOfficeHub_2015.6801.23751.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.MicrosoftSolitaireCollection_3.9.5100.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.Office.OneNote_2015.6868.57981.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.OneConnect_1.1605.17.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.People_2016.709.155.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.People_2016.709.155.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.SkypeApp_11.4.86.0_neutral_~_kzf8qxf38zg5c Remove-AppxProvisionedPackage -online -packagename Microsoft.StorePurchaseApp_1.0.454.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.WindowsAlarms_2016.622.2118.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename microsoft.windowscommunicationsapps_2015.6868.41201.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.WindowsFeedbackHub_1.3.1741.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.WindowsMaps_2016.701.2235.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.WindowsStore_11606.1001.394.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.XboxApp_2016.623.248.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.XboxIdentityProvider_2016.616.818.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.ZuneMusic_2019.6.19261.0_neutral_~_8wekyb3d8bbwe Remove-AppxProvisionedPackage -online -packagename Microsoft.ZuneVideo_2019.6.19281.0_neutral_~_8wekyb3d8bbwe

 

After completion, you just need to restart the computer. Please be aware that if an apps was still provisioned to a user, you cannot remove that apps. As such it is important that you ensure no users is still requiring that apps before removing.

I find this to be useful especially when you want to create a consistent operating environment (COE) for a corporate/enterprise system.

!!! HAPPY SCRIPTING !!!
!!! HAPPY CHINESE NEW YEAR !!!

Office 2016 - Outlook AutoDiscover.xml

Recently one of my client have upgraded their Microsoft Office from 2013 to 2016 version and have encountered problems in creating an Outlook profile for their new employee(s).

What I have discovered is that Outlook 2016 no longer provide the "Outlook Anywhere" features whereby all Outlook accounts must be connected to Exchange server directly for .ost synchronization thus the feature is no longer available.

According to Microsoft the reason behind the changes is having .ost directly connected to Exchange server is for more stability & reliability... yeah rite. To me it seems more to forcing customers to upgrade their Exchange server for the new functions & features.

Anyway, luckily I am not the first one to encounter this problems any there are many solutions out there, but this is one particular solution that have worked for me.

And here are the steps :-

1. First you will need to create an "autodiscover.xml" file with the following contents. You can do this by using notepad.

<?xml version="1.0" encoding="UTF-8"?> -<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> -<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> -<Account> <AccountType>email</AccountType> <Action>redirectUrl</Action> <RedirectUrl>https://autodiscover.[FQDN]/autodiscover/autodiscover.xml</RedirectUrl> </Account> </Response> </Autodiscover>

Note : Change the [FQDN] to your domain name (eg. domain.com or domain.com.my)

 

2. Next is to modify the registry so that Outlook 2016 is aware of the "autodiscover,xml" file and its path.

 

3. Open --> regedit --> Browse to --> HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover.

Note : Create "AutoDiscover" key if not available.

 

4. Create --> String Value = [FQDN].

Note : Change the [FQDN] to your domain name (eg. domain.com or domain.com.my)

 

5. Then modify the value of the "String Value" = [Path to "autodiscover.xml" file], for example (C:\AutoDiscover\autodiscover.xml)

 

6. Below is the example of the registry, you may use this to import the registry but remember to modify it accordingly before importing.

Windows Registry Editor Version 5.00   [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\outlook\AutoDiscover] "[FQDN]"="[Path]\\autodiscover.xml"

 

7. Now you can open Outlook 2016 and use its wizard to configure user's account accordingly, Outlook should be able to locate your Exchange server now and will prompt for username and password.

 

8. At certain times, Outlook will prompt for username & password twice or thrice or sometimes more (depends whether your Exchange's autodiscover is published correctly or not), and sometimes it may prompt for certificate installations.

 

9. This is normal as your Exchange is trying to authenticate you by using both MAPI & HTTPS protocol and certificate (if any). Thus the multiple prompts for username & password.

 

Some user(s) have claimed that this also works with Office 365 environment, but I have to test it out and unsure of the outcome. But for my customer's environment this just works perfectly.

 

!!! HAPPY COMPUTNG !!!