Mapped drive logon script not working (Troubleshoot Guide)

Users have reported that they occasionally experience problems Mapped drive logon script not working: I know that turning on machine tunnels fixes the problems with the login script. Initially accessible, mapped drives later become inaccessible. It is occasionally possible to access the mapped drive using UNC to navigate to its short name or even FQDN. This impacts random people, and I’ve verified that all App Connectors’ DNS servers are accurate.

The poor network connection (the speed at which data is sent from the domain controller distributing policy updates to the computers in the group) discovered during the first login process is the cause of the logon script via group policy not working issue.

Unless the policy processing settings are created to override the program’s specified reaction to the slow link, the login script won’t run if the Group Policy slow link is detected.

Mapped drive logon script not working:

If the issue is irregular, the Fast Logon Feature or Slow Link may be the reason. Let’s attempt the troubleshooting methods listed below:

Disable Fast Logon:

Go to [Computer Configuration/ Policies/ Administrative Templates/ System/Logon] in the default Domain GPO after opening it. Allowing the machine to “Always check for the network at startup and logon” is a good practice.

Enforce policy setting:

Select [Computer Configuration/ Policies/ Administrative Templates/ System/ Group Policy] from the drop-down menu. Please select the appropriate policy processing policy and enable the following based on your policy settings:

Permit processing over a sluggish network connection Even if the Group Policy objects have not altered procedure. Restart the client after running “gpupdate /force” on the DC. If the problem continues, open GPMC on DC, click Group Policy Result, select Group Policy Result Wizard from the context menu, and then follow the wizard’s instructions to gather a report of the Windows 7 system.

When it’s finished, use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the file and provide us with the download location by selecting Save Report from the context menu in the right panel.

How to fix Mapped drive logon script not working:

Creating or modifying a Group Policy Object (GPO) to change the default behavior is the answer or workaround to the issue of logon scripts not executing, running, or functioning:

1. Right-click a domain object in the Active Directory Users and Computers Microsoft Management Console (MMC) snap-in and choose Properties.
2. Click the tab for Group Policy.
3. Run Group Policy Management and omit the first two steps using the Group Policy Management Console snap-in for MMC.
4. Click Edit after selecting the Default Domain Policy (or any other enforced domain policy). (Right click in the Group Policy Management interface on the Enforced Domain Policy or the Default Domain Policy you want to update.)
5. Go to System > Administrative Templates > System > Group Policy under Computer Configuration.
6. Check for scripts that handle policy. Select (check) Enabled by performing a double click on Scripts policy processing. Then check the box that says “Allow processing across a sluggish network connection” and click OK.

Note that further default actions that are not carried out when a sluggish link is discovered can also be changed:

• processing of the folder redirection policy
• Processing of disc quota policies
• processing scripts for policies
• Processing of EFS recovery policies
• processing of software installation policies
• processing of IP security policies
• processing of the Internet Explorer maintenance policy
• processing of wireless policies
• Snap the MMC snap-in shut.
• Restart the workstation or remote computer.

Additionally, you can change the default settings for slow link connections for users, which take effect regardless of the computer on which a user logs. The procedure will be similar to what was just described, but instead of going to Computer Configuration, go to User Configuration. Visit Administrative Templates -> System -> Group Policy after that. Select the Allow processing across a sluggish network connection check box after turning on the Scripts policy processing (by selecting the Enabled radio button).

in Windows 10, how can I execute a logon script?

Run a script when Windows 10 starts up.

1. Make the batch file’s shortcut.
2. Right-click the shortcut file and choose Cut after it has been created.
3. Select Programs or All Programs from the Start menu.
4. After the Startup folder has been opened, select Edit from the menu bar, then choose Paste to paste the shortcut file.

To Conclude the following:

In a nutshell all about Mapped drive logon script not working, a straightforward batch script uses group membership to map specific discs for some users while leaving other users’ drives unmapped. I hardly ever locked down the surroundings.

Nothing in the group policy’s user configuration section is specific to the new terminal server. All users have no issues using the login script when logging into their workstations because it runs from the default domain policy.

Frequently Asked Questions