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


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

Solved – windows time service not starting automatically on work-group environment

i found the problem that show up the windows time services not running when using workgroup environment.

and for the solution, please use this workaround.

Method 1

Run the following command to delete the trigger event that’s registered as the default setting and to change the Startup Type setting for the Windows Time service from Manual to Automatic:

sc triggerinfo w32time delete

Method 2

Run the following command to define a trigger event that suits your environment. In this example, the command determines whether an IP address is given to a host, and then it starts or stops the service.

sc triggerinfo w32time start/networkon stop/networkoff


Method 3

Change the Startup Type of the Windows Time service from Manual to Automatic (Delayed Start).

Note If the Startup Type of the Windows Time service is set to Automatic (Delayed Start), the Windows Time service may be started by the “Time Synchronization before the Service Control Manager starts the Windows Time service” task. (This depends on the startup timing of the Windows operating system in question.)

In this situation, the service triggers an automatic stop after the success of the Time Synchronization task. Therefore, if you use Method 3, you must disable the “Time Synchronization to avoid the task to start the Windows Time service” task. To do this, follow these steps:
Start the Task Scheduler.
Under Task Scheduler Library / Microsoft / Windows / Time Synchronization, click Synchronize Time.
Right-click, and then click Disabled on the shortcut menu.



Windows 2003 – Can we deleted c:\windows\system32\logfiles\W3SVC1

Last week our exchange server drive C hard drive space, growth abnormally. We’re using windows server 2003r2.

After analyze all folder in drive C, I found that the c:\windows\system32\logfiles\W3SVC1 have the biggest space in drive C.

Because I don’t know if the log in folder can be deleted, so I googling the solution and I found this solution.

After do the solution (deleted the file using scheduler) my hardisk capacity becomes free by 50%.

Hope this workaround will help some people.

Citrix Xen Server – Changing the frequency of log rotation (for example to resolve a lack of disk space)

Credit to Steven Wright, because this article help me so much. If you have problem like me, please follow below procedure to resolve it :

Connect putty and logon into xen server host using root user.

Use “vi” (a text editor) to edit the /etc/logrotate.conf file

Changed the rotate value into what you want and set the log to compress (delete the #).

Press “I” for insert and press “x” to delete. Esc to return to command mode.

After finish, press “:wq” (w = Write and q= quit).