Share via

Windows long path issue workaround

AnnaG 131 Reputation points
2024-03-20T10:41:42.92+00:00

Hello all

We have a long path issue. No fix for this as too many on the file server. We are migrating data and the destination server name is longer than the source which will result in more characters being used for users to Map drives on their Windows 10 devices.

I have look at a few articles on this and using Computer Name Aliases instead of DNS CName records. Does this mean if I use Netdom computername <computer> /add:<ALIAS>, this is not the same as going into the DNS management console and creating a cname there? I certainly cannot see any CNAME created in DNS so I guess it is completely different and found this article

https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/using-computer-name-aliases-in-place-of-dns-cname-records/ba-p/259064

If this works then I guess it is fine to use this method to access shares using a shorter path right? Still will be using Kerberos etc. so no downside?

Just wanted to ask whether anyone is doing this and any issues? Every time I have worked on a migration the server name character length has been the same until know which is why it will cause issues unless we come up with an alternative solution.

To make things more complicated i read "It’s not enough to just create a CNAME on your DNS server. You must disable strict name checking to allow the server to respond using a different name."

https://4sysops.com/archives/disable-strict-name-checking-with-powershell/#:~:text=Strict%20name%20checking%20is%20a,to%20its%20proper%20computer%20name.

Thanks in advance.

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,195 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,636 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Marcin Policht 18,270 Reputation points MVP
    2024-03-20T11:12:52.9+00:00

    Adding network locations to the local PATH environment variable is in general not a good idea because any network issues are likely to severely impact performance of the local computer.

    Note that you only need to rely on path when not specifying full path to a target file, so you might want to assess to what extent that's actually needed. In addition, keep in mind that using short names (as opposed to FQDN) will impact Kerberos

    hth

    Marcin

  2. Ian Xue (Shanghai Wicresoft Co., Ltd.) 34,271 Reputation points Microsoft Vendor
    2024-03-22T08:14:02.5533333+00:00

    Hi AnnaG，

    Thanks for your post. You can use the to migrate data and they shouldn’t have the length limit for migrating data.

    robocopy D:\Files \newserver\d$\Files /e /copyall /xd "AI_RecycleBin" "DfsrPrivate" "$RECYCLE.BIN" "System Volume Information"

    Also, here is the article for how to make file path over 260 characters, just for your reference and hope it is helpful.

    How to Make Windows 10 Accept File Paths Over 260 Characters (howtogeek.com)

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    0 comments