This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 80%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
We need to migrate a Server 2008 file server to Server 2019. All the shared files are stored on iSCSI targets.
Is there any reason we can't simply build a new server with the same name and IP address, disconnect the iSCSI drives from the old server, reconnect iSCSi targets to the new server and import the file share registry keys from the 2008 server to the 2019 server?
Are any additional steps required?
Hi,
As far as I'm concerned, it's recommended to set up Server 2019 with new IP address and name, then refer to the following about how to migrate Server 2008 file server to Server 2019 with storage migration service. On the ISCSI target server, in the target, add Server 2019 to connect.
After migration, remove the old server in the target and retire Server 2008.
https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/migrate-data
https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview
Thanks for your time!
Best Regards,
Anne
-----------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
It is many terabytes of data. We do not want to make a second copy files on a new server using the storage migration service. I thought you only use the storage migration service when copying files to new hardware.
Many users are connecting to file shares on the old server via IP address or host name. If the new server has a different host name and IP address, many things will break.
What is there to gain by having the new server use a different name and IP address?
What is there to gain by using the storage migration service if we don’t want copy the files to new storage media?
@Xiaowei He
Your answer doesn’t make sense to me.
Did you see me response?
The Storage Migration Service links do not address handling systems using iSCSI drives.
It doesn’t appear to be logical to use SMS to copy files to different storage media rather than just mount the existing drives from a new server.
Can you explain further?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 74%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
@KJ Did you ever figure this out? I am looking to do the same thing. Except I am upgrading from server 2012 r2 to 2019. The only iSCSI configuration I see on my server is managed in the iSCSI initiator it looks like. I don't see anything in Server Manager > File and Storage Services pane. Here are the steps I have pieced together so far for this process. I know this was awhile ago for you just curious if you can offer anything to this. Thanks in advance...
Migrating iSCSI
• On Old Server
o Go to disk management and remove the drive letters
o Go to control panel > iSCSI initiator and document the target settings under the Discovery tab, Persistent target settings, and Bound Volume/Devices settings
o Then delete target connection to SAN
• On New Server
o Go to iSCSI initiator and note the initator node name (iqn)
• On the SAN
o Modify Lun Mask by removing old initator name and add new initator name
o If using CHAP modify that as well to reflect the new (iqn)
• On New Server
o Open iSCSI initator
o Add SAN as target using the settings from earlier
o Go to Targets tab and log it in (tick to auto mount iSCSI LUN at reboot)
• At this point the disk should show up in disk management
• Right click the LUN and select “Change drive letter and Path”
• Select “Add and assign driver letter” G: (for example)
• On Old Server
o Export this registry key which contains the shares
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares
• On New Server
o Import that registry key
o Reboot the server