takes ten minutes tops.Īlternatively you could also make the same Share name on each server for yourĪcad support files, and map it to the same drive letter for each office. This way i can change all paths for all users with a text editor using find replace. I use BAT scripts and REG files to simply and quickly modify the Windows Registry instead of using a Shortcut switch and the Autodesk ARG file. I find that UNC paths are the ONLY way to know that everyone is getting the correct Acad local setup files in a WAN scenerio. my personal office just moved locations and got a new server. >i support 6 offices each with there own servers and different mapped drive letters. >profiles, where the portability of mapped drive letters is a much better >However, I don't think that AutoCAD forces/implies UNC pathing in user >actually have no drive letters mapped to network shares. >when logged in as a local administrator on the workstation, which might With a UNC path, that install works no matter what, even >from a workstation with a different drive letter mapping, you will get a >an install on the server, using a drive letter path, then try to install >I think the UNC path is only for installs. >why does the software raise a red flag at installation >any hardware mapped drives are preferable in this case but still not >want is a solution that is completely logical and not dependent on >Depending on your infrastructure, what you most likely ultimately Layton" wrote in Stachoni wrote in message: > listed, even though they are saved to mapped drives. > Project Navigator in ADT forces the UNC pathing in its file path name when It even applies the unc to xrefs which in my mind is a big no no. > profiles, where the portability of mapped drive letters is a much better > However, I don't think that AutoCAD forces/implies UNC pathing in user > actually have no drive letters mapped to network shares. > when logged in as a local administrator on the workstation, which might > from a workstation with a different drive letter mapping, you will get a > an install on the server, using a drive letter path, then try to install > I think the UNC path is only for installs. Listed, even though they are saved to mapped drives. Project Navigator in ADT forces the UNC pathing in its file path name when Profiles, where the portability of mapped drive letters is a much better However, I don't think that AutoCAD forces/implies UNC pathing in user When logged in as a local administrator on the workstation, which mightĪctually have no drive letters mapped to network shares. The idea being that if you buildĪn install on the server, using a drive letter path, then try to installįrom a workstation with a different drive letter mapping, you will get aįailed install. I think the UNC path is only for installs. > why does the software raise a red flag at installation > any hardware mapped drives are preferable in this case but still not > want is a solution that is completely logical and not dependent on > Depending on your infrastructure, what you most likely ultimately Layton" wrote in Matt Stachoni wrote in message: * The input directory can only be a drive letter + colon ONLY e.g."Corey A. I use the getUNC macro from the really good paper “The Path, The Whole Path, And Nothing But the Path, So Help Me Windows” by Arthur L. I need to get UNC path for a mapped drive as different users have their HOME drive on different servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |