Move a folder share to other VM and keep mapping?

I have a Windows 2003 Server VM named "nas01" that has a Shared Folder called "IT" on it, which is shared via File Server Management.
It basically holds some files or ISOs for folks in a security group to access, and people map to the \\nas01\IS share from their Windows clients.

Since I'm trying to get rid of this 2003 server and this share is on a virtual disk, how could I move the disk to another server and keep the mapping?
Would the approach be to somehow unmount the virtual disk that has this partition on it, then mount it to another server that's running Windows? Target server would be a 2008 or 2012.

If so, not sure the best practice here on moving the disk, and how I could maintain the mapping without having to re-map. Perhaps I don't maintain the mapping and just reconfigure a group policy to take care of it.

There's also a ".vSphere-HA" folder on this share and I can't open it, says access is denied. I'm not sure if that's a folder that's being used by some component in vSphere or vCenter for anything. Does that look familiar?

Thoughts, suggestions, experiences?

Much appreciated
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
De-attach and remove the virtual disk from the Windows 2003 Server, (Right Click the VM, Edit Settings, Remove disk (not delete from datastore).

Add this disk to Windows 2008 Server, (Right Click the VM, Edit Settings, Add disk browse datastore and add the disk.

Then you will have to re-share the folder.

But all the permissions on the NTFS disk will be the same, and intact.

vSphere-HA don't worry about this file, this is used by VMware vSphere HA - it's normal.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
garryshapeAuthor Commented:
Ok so as far as attaching it to the other server, I'll need to make sure there's enough space on that datastore the target VM is on? Or would the disk remain on its current datastore? Just making sure there's no other necessary migration.
It's like a 500GB disk
In VMWare the Hard Drives are simply VMDK files.    You can attach and remove them fairly easy, like unplugging a drive from one computer to another.    Andrews steps are spot on.    If your HD (VMDK File) is 500 GB in size you'll need at least 500GB on a new ESX server.   Otherwise if they are on the same server, you can copy/move and paste the VMDK file from the old VM directory into the new one.   Done.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Are you moving the virtual machine disk between HOSTS and Datastores, otherwise the VMDK (virtual disk) stays where it is, it does not move, you are just de-attaching and re-attaching to virtual machines.
I would also look to use DFS for the UNC paths. THis means you can move the data between servers easily and still keep the same unc path. You dont need to replicate the data just use it to keep the unc paths that users have static even though the server that serves the share changes.
Basically you publish the dfs share as \\\share   and in the DFS config you have that share point to \\server1\share .... if you move the share to \\server2\share2   you just update the DFS config and users still connect to \\\share.  
Makes moving shares and things around easy without breaking users shortcuts and apps references etc.
garryshapeAuthor Commented:
Ok yeah that sounds like it could work.

We do have DFS currently, but interestingly it's only used for establishing shorcuts to shared folders on other servers, but no  replication is being utilized. I suspect it is because we're low on storage but I'm still trying to figure out new environment
garryshapeAuthor Commented:
It's also mapped as a datastore in vSphere apparently
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The Virtual Machine OS, has got nothing to do with the vSphere datastore, it does not see it!

VM OS does not even know it's a VM, or has VMDKs!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.