none
how to map arabic folder names with net use command (i need to use in logon script) RRS feed

  • Question

  • hi,

    i need to map network drives through logon script, but when i put net use and folder name which name is in arabic its not working , can anyone suggest how to use net use or alternate command to map the folders which is in arabic.

    Thanks

    • Moved by Bill_Stewart Wednesday, September 13, 2017 9:08 PM This is not non-English localization support forum
    Thursday, July 20, 2017 7:47 AM

All replies

  • Use Group Policy to set mapped drives.

    \_(ツ)_/

    • Proposed as answer by Bill_Stewart Tuesday, July 25, 2017 3:44 PM
    • Unproposed as answer by Balal Ahmad Wednesday, July 26, 2017 3:49 AM
    Thursday, July 20, 2017 7:56 AM
  • NET USE will not work with Unicode if you do 't save the file as a Unicode file.

    You can use Group Policy or use PowerShell as a logon script with New-PsDrive.

    Since a drive only needs to be mapped once then just tell the users to map the drives with File Explorer and select to persist the drive.


    \_(ツ)_/


    • Edited by jrv Thursday, July 20, 2017 9:44 AM
    Thursday, July 20, 2017 9:44 AM
  • Roaming profiles are very good for maintaining connected resources between workstations and also provide automatic profile backup capabilities.

    GP Preferences can map per user using targeted preferences.

    In general we map drives by group membership.  If we need a set of users to have access to a resource we just add them to the group.  On next login or next GP refresh they will get the new group assigned drive.

    AD is designed to work from the business model and job assignment coiled around concepts like task, department and job.  By designing from this perspective we can abandon old pre-AD methods like logon scripts and concentrate on job tasks and resources.

    Logon scripts are really a leftover from NT4 and Windows 9x and earlier.  Correct deployment of AD around the business model and corporate structure make all of this much simpler.  The history of GP from W2K server on has been to allow GP to more completely manage this.  Coupled with SCCM or other system tools we can also manage the hardware and applications deployment based on AD definition and resources.

    If we add terminal server (RDS) into this for users that move frequently we can further reduce configuration and persistence issues.

    All of this becomes even more important when considering moving the datacenter into the cloud.

    In modern AD Group Policy you can just add a PowerShell script to the GP that is assigned to the user by group or OU.  Using the old "profile" tab to define a logon script has been pretty much abandoned in favor of GP assigned scripts.  In GP we can assign multiple scripts to a user with each assignment controlled by a group or WMI filter

    Time to learn modern Windows, Active Directory and Group Policy.  Since 2000 this has been available yet desktop techs continue to use old NT4/W9x methods.


    \_(ツ)_/


    • Edited by jrv Thursday, July 20, 2017 10:44 AM
    Thursday, July 20, 2017 10:36 AM
  • You have to set your locale to one that supports Arabic characters.


    \_(ツ)_/

    Sunday, July 23, 2017 11:56 AM