Monday, 11 March 2019

Unable to Log In to Visual Studio

Recently, one of my users complaining because they he could not activate Visual Studio with his MSDN account. It works fine on another machine, but not his. I tried mine, and I still got the same error - thus it was safe to rule out it is not license / user issues, but more towards computer issue.

Error :

Microsoft Visual Studio
We could not add the account
Service returned error. Check InnerException for more details

Troubleshooting :

  1. Back to basic - let's start from beginning... Trying to sign in will throw this error window.

  2. Selecting Close on above window would throw this Security Alert warning.

  3.  Selecting View Certificate on above window would give us this.

  4.  Let's view Certification Path, and view Root CA certificate by selecting the root certificate in Certification path | View Certificate

  5.  So it seems the Root CA (in my case) is issued by Baltimore CyberTrust Root.

  6.  Do I have that on that machine? Let see... Launch Microsoft Management Console by going to Run | type MMC | press Enter. Select File | Add/Remove Snap-in...

  7.  Choose Certificate | Add > 

  8.  Select Computer account | Next >

  9.  Select Local computer | Finish

  10.  Select OK

  11.  Browse to Console Root | Certificate | Trusted Root Certification Authorities | Certificates. On right column..... oh no! Baltimore CyberTrust Root certificate was not there!

Resolution :

  1. Now let's install the cert! download the CA (in my case, I downloaded from here : ).

  2.  At the same MMC console, right click at Certificate | All Tasks | select Import...

  3.  Select Next >

  4.  Browse to the CA file | select Next >

  5. Place the cert on below store | select Next >
    Store : Trusted Root Certification Authorities

  6.  Select Finish

  7.  Select OK

  8.  Refresh the console, then we could see the cert is now installed.

  9. Tried to sign in again, we shall now pass!

Friday, 8 March 2019

Unable to Patch Server - Access is Denied

I faced this issue a few months back, where I could not patch one of our servers. Whenever I tried, I will got this :

Error : 
Windows Update Standalone Installer

Installer encountered an error :  0x80070005

Access is denied.

Troubleshooting :

Troubleshooting 101 - check the service. Turned out, Windows Update service could not be found in the server...

Resolution :

There are 2 easy ways to resolve this....

Method 01 :
1) Go to a working server.
2) launch REGEDIT.
3) export below Registry key.
Registry key : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv
4) import to the target server
5) restart the server

Method 02 : 

1) Apply below Registry Keys to the server :

"DisplayName"="Windows Update"

2) Outcomes...

3) Restart server once done

4) Windows Update service is visible now.


Thursday, 1 February 2018

Microsoft Outlook Signature : Location of the File

Another simple post - Where is the location of Outlook Signature ? It is at........


So there are 3 files : 

*.htm - for HTML email format
*.rtf - for Rich Text email format
*.txt - for plain Text email format

all of them can be edited via Microsoft Word. simple as, aye?

Thursday, 25 January 2018

Windows OS Deployment : Windows setup could not configure Windows to run on this computer's hardware.

I got this error while deploying Windows OS to my environment. It should be straightforward process, but somehow I got stuck with this. Clicking OK will restart the machine, and it still won't resolve the issue. Workaround? run msoobe.exe manually.

Issue : 
Windows setup could not configure Windows to run on this computer's hardware.

Workaround :
  1.  Press Shift + F10, command prompt window will opened

  2.  Change the directory to C:\Windows\System32\oobe
    CMD :
    cd C:\Windows\System32\oobe

  3.  execute msoobe.exe
    CMD : msoobe or msoobe.exe

  4.  This screen appeared. Proceed with deployment.

  5.   Once all done, we'll be back to this screen, restart the machine by using command prompt or just click OK at the message box.


Thursday, 18 January 2018

Thursday, 11 January 2018

How To : Group Policy Processing ( GPP ) : Add / Edit / Remove INI FIle

It is a common practice for applications to have configurations set in INI file. It may contain information such as language, key, connection setting, version, and so forth. Updating INI file might not affect the application coding, but it may affect on how the application behave. There are multiple ways to update the file, one of it is by using Group Policy Preference ( GPP ). 

In this example, I want to update a key file at a specific location with a specific information.

Information : 

  • File Location : C:\Temp\key\keyfile.key
  • Content of AppsKey.key :

As mentioned by Microsoft here, below format must be followed :

How To Do :

  1.  Edit the policy. Navigate to Preference | Windows Settings

  2.  Right click INI Files | New | Ini File

  3.  This screen will appear...

    Action = Different action will do different thing. Refer to the table below
    File Path = where to put the file. If the folder does not exist, the folder will be created. If the file does not exist, the file will be created. If the file exists, the action will affect the INI file content.
    SectionName = In which section the key will resides
    PropertyName = the property of the key
    PropertyValue = value of the key

  4. Therefore...
    Action = Replace
    File Path = C:\Temp\key\keyfile.key
    SectionName = Setup
    PropertyName = ApplicationKey
    PropertyValue = XXXX-XXXX-XXXX-XXXX

  5.  If there are more keys needed, create more entries. Note that, Update and Replace will give the same result.


Thursday, 4 January 2018

GPO : Failed to Open Group Policy Object

This happened to my environment anew days ago, where I was not able to edit my group policy with below error. The GPO is working fine, just that I could not make any changes on it.

Issues :

Failed to open the Group Policy Object. You might not have the appropriate rights.

Details :

The system cannot find the path specified.

Troubleshooting :
  1. Manually assigned delegated permission (with Edit settings, delete & modify security) - not working
  2. Tried to edit the policy from PDC Emulator server - not working
  3. Checked the availability of the GPO folder in SYSVOL, the GPO folder is available.

Resolution :

A bit of Googling, I got this :

This is the issue, I executed the Procmon & found that process is trying to access the Registry.pol file under User folder under the policy path & it is failing to access, even though user configuration are not configured.

It turned out, a folder named 'User' was missing from the GPO folder, which causing GPO Editor unable to read the content, thus throwing the error. 

An empty folder created with the name of User, and it resolved the issue.