Solved – Office 2016 Professional Plus Error 1935 during installation

Hello Everyone, good morning.

Our organization are going to start migrating the Microsoft office into office365 in the middle of pandemic Covid-19. We are using the Office2016 as a client of Office365.

and when I try to Install the Office 2016 in the users computer, I found problem with error 1935 like below pictures.

error 1935

to solved above error just do rename or delete the registry below :

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppModel

After that try to reinstall the office 2016 again, and you’re installation will be successfull.

Thank you for reading this article. And I hope the solution will help you too with the problem.

source:

Guide to Move iSCSI File server to the new server

Hello Everyone, I hope you’re doing well in the middle of pandemic Covid-19. Today I will share my experience when I’m doing migration from file server with iSCSI NAS connected. In my environment my old server using windows server 2008r2 and the new file server will be using windows server 2016. And I’m using NAS from Synology.

And here are the workaround that I used to migrate my server.

  1. The first thing that we need to do is installing the new server, and make sure all feature for File sharing are activated.
  2. After that backup/export the registry key on the old server, the registry key path that you need to backup are : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares
  3. Copy the registry key backup to the new server
  4. Import registry key to the new server
  5. Shutdown the old server
  6. Change the new server name and IP address same like the old server
  7. After the change name server, you will need to restart the server but before you restart it , you need to connect the iSCSI to the new server.
  8. After iSCSI has been connected, restart the server
  9. and then Voila all your shared folder has been restore successfully

The registry key at #2 are the key for the this migration. As long as drive letter on the new server the same as on the old server it will work perfectly. I would hate to see you manually re-create hundreds of shares on a file server

ok I hope everyone who read this can successfully move their File server to the new version like I did. Thank you

source:

this link

Solved – Windows Update error code 80092004 with kb4535102

Hello everyone, one of my server are having problem with windows update. This server still using windows server 2008r2. And when I try to install kb4535102 it will always show up error code 80092004.

After try to do some troubleshoot and googling from the error code, I found that I need to install missing kb that makes the error code.

The missing kb for this error are kb4490628, after install the kb4490628 manually and then I can install the kb4535102 without any error.

I hope anybody who read this article will solved the problem with same workaround.

source :

  1. here and
  2. here

Windows 10 – keyboard shortcut effect that make your users thinks the computers was broken

Hi this is my first post in 2020.

Sometimes when i’m doing the support time, some user are asking some weird problem after using the shortcut of the keyboard.

last question when i’m write this article is “why my display change into b/w colour?” 🙂

and here are the shortcut

rotate the display = ctrl + alt + arrow up/down/left/right

Change the display into black and white = windows button + ctrl + c

If there is any other shortcut that make your users thinks the computer was broken, please let me know more on the comment section..

Thank you

some source

Solved – kb3045313 error 643 in windows server 2012R2

Hello,

i found one of my server (windows server 2012R2) which contain symantec backup exec cannot install one update with kb3045313, it always show error 643.

so many failed status

after some research in the internet, i found that this problem come from .net framework as it describe in this article

after i installed the .net framework 3.5 , and then i reinstall the kb3045313.

And it succeeded as you can see in the picture above.