Global - Network Drives
The Manage network drives window maps network shares to drive letters for the account that the VisualCron Server service runs under. By default that is the SYSTEM account. Windows keeps mapped drives per logon session, so the Server does not see the drives you map in your own Windows session. Map drives here when a Task that runs as the Server service account, without a Credential, needs a drive letter.
When a Task can use a UNC path such as \\<server>\<share>\<folder>, use the UNC path together with a Credential instead. A UNC path does not depend on a drive mapping being in place.
To open the window, go to Server -> Global objects -> Network drives.

Manage network drives window
The list has the following columns:
- A status icon without a heading: connected or disconnected, see below
- Drive: the drive letter
- Path: the UNC path the letter is mapped to
- Credential: the Credential used for the mapping. "No Credential id specified" means none. "Could not find Credential" means the Credential has been deleted, or you do not have permission to see it
- Controlled: "True" for a drive mapped from this window, which the Server maps again each time it starts. "False" for a drive that the Server found already mapped for its service account, at this start or an earlier one, for example by a script that ran as that account. The Server lists such a drive but does not map it at startup, and the entry can stay in the list after the mapping is gone
For a drive with Controlled "True", the status icon shows the result of the mapping at Server startup, or of the last Map drive or Reconnect that succeeded. A failed attempt shows only until the Client connects to the Server again, see Map a drive and Reconnect a drive. For a drive with Controlled "False", it shows whether the drive could be reached when the Server first listed it. The Server does not check the drives again in between, so a drive whose share has become unavailable can still show as connected.
The toolbar has the following buttons:
- Map drive: opens the Map Network Drive window, see Map a drive
- Unmap drive: removes the selected drive from the list and disconnects it, see Unmap a drive
- Reconnect: maps the selected drive again, see Reconnect a drive
- Audit log: opens the Audit log for network drives
Right-click a row to open a shortcut menu with Map drive, Audit log and Versions... Versions.. shows the version history of the selected drive entry. To unmap a drive, use the Unmap drive button or press Delete.
Map a drive
-
Click Map drive. The Map Network Drive window opens.

-
In the Credentials group, select the Credential of an account that can access the share: a domain account, or a local account on the file server. Type in the Filter.. box to shorten the list. If the account is not in the list, add it first in Credentials. You can also select No Credential to connect with the identity of the Server service account; see Which account authenticates the mapping, including the Credential not found warning there.
-
In the Drive info group, select the letter in the Drive list. The default is the highest letter, from "Z:" down, that no entry in the Manage network drives window uses. Letters in use on the Server computer are not taken into account, so choose a letter that is free there (see the warning below).
-
In Path, enter the UNC path of the share, for example
\\<server>\<share>. The folder button opens a folder browser if your user has the Remote file explorer permission with Read; without it, the Client shows a permission message. When the Client is connected to a remote Server, the browser shows the folders of the Server computer. In all cases, check that Path is a UNC path that the Server computer can reach. -
Click Map drive at the bottom of the Map Network Drive window.
If the selected letter is already mapped on the Server, VisualCron disconnects the existing mapping first, without asking. If the letter is already in the list and the new mapping succeeds, the new path and Credential replace that entry. If the new mapping fails, the old mapping has in most cases been disconnected as well. Only if Windows refuses to disconnect it does the old mapping stay; the new mapping then fails with a message from Windows.
If the mapping succeeds, the window closes and the drive appears in the list with Controlled "True".
If the mapping fails, the window stays open. In most cases the Server shows a message that starts with "Could not map drive", followed by the message from Windows; see Troubleshooting. If the selected Credential has been deleted, no message appears, and the Server log shows "Could not find Credential when mapping drive."
After a failed mapping, the list shows the drive as disconnected, but the Server has not saved the attempt:
- For a letter that was not in the list, the row stays until the Client connects to the Server again. Unmap drive cannot remove it; disconnect the Client from the Server and connect again to clear it.
- For a letter that was already in the list, the row shows the new path until the Client connects to the Server again. It then shows the earlier entry again, with its earlier path, Credential and status. That status can be connected although the earlier mapping was disconnected (see the warning above).
When the Server starts
Each time the VisualCron Server service starts, it tries once to map every drive whose Controlled value is "True". If a drive cannot be mapped, for example because the file server is not yet available, the Server logs an error that the drive "could not be mounted" (see Log) and shows the drive as disconnected. The Server does not retry on its own. The drive is mapped again when you click Reconnect. Importing network drive settings with Import settings can also map the Controlled drives again.
Jobs that use the drive letter fail until the drive is mapped again.
- After the Server computer restarts, open the Manage network drives window, select each drive that is shown as disconnected and click Reconnect.
- After the file server restarts, the icon can still show the drive as connected. If a Job cannot reach the drive, select the drive and click Reconnect.
For Tasks that do not need a drive letter, use a UNC path with a Credential.
Reconnect a drive
Select a drive in the list and click Reconnect. VisualCron disconnects the drive and maps it again with the Credential stored for it. If this succeeds, the status icon shows the drive as connected and Controlled is set to "True", so the Server also maps the drive each time it starts. If it fails, the Server shows a message that starts with "Could not map drive", see Troubleshooting. The drive is then no longer mapped, unless Windows refused to disconnect it. The list shows the drive as disconnected until the Client connects to the Server again, and then shows the status from before the attempt, which can be connected. If the Credential of the drive has been deleted, no message appears, and the Server log shows "Could not find Credential when mapping drive."
A drive with no Credential stored, which includes every drive listed with Controlled "False", is mapped again with the identity of the Server service account. Most shares do not accept that identity, so Reconnect can turn a working mapping into a failed one. To have the Server map such a drive at startup with an account that has access, click Map drive, select the same letter and path, and select a Credential.
Unmap a drive
Select a drive and click Unmap drive, or press Delete. The drive is removed from the list and disconnected on the Server right away, without a confirmation. The Server no longer maps it at startup. If Windows cannot disconnect the drive, the entry is still removed, and the Server shows a message that starts with "Could not unmap drive".
Which account authenticates the mapping
The VisualCron Server service maps the drive itself. The mapping does not run in the execution context of a Task, so the account that the service runs under matters:
- With a Credential: the user name and password of the Credential are used to connect to the share. If the Credential stores the domain separately and the user name does not already include one, the user name is sent as
<domain>\<user> - With No Credential: no user name or password is sent, and the connection uses the identity of the service account. Under the default SYSTEM account that is the computer account of the VisualCron Server computer, which most file shares do not grant access to
As described at the top of this page, a drive mapped by one account is not visible to another. If you prefer not to store a Credential for the drive, you can run the VisualCron service under a domain account that has access to the share and map the drive with No Credential; the mapping then uses that account's identity. See Credentials for the account options, and note the warning below.
When the running Server maps a drive with No Credential, or a drive whose Credential has been deleted, it raises the VisualCron event Credential not found. This happens, for example, when you click Map drive or Reconnect. A Job with a VisualCron Event Trigger on that event can start. To avoid this, select an existing Credential for the drive.
Authentication protocol
VisualCron does not choose an authentication protocol for network shares. It passes the user name and password to Windows, and Windows negotiates Kerberos or NTLM on its own. VisualCron has no setting that prefers, forces or falls back to either protocol, and it does not record which protocol was used. It logs only whether the mapping succeeded.
To find out which protocol Windows used, check the Windows event logs:
- On the file server, Security event ID 4624. The Authentication Package field names the protocol, and the Package Name (NTLM only) field is filled in only when NTLM was used
- On a domain controller, event IDs 4768 and 4769 indicate Kerberos, and event ID 4776 indicates NTLM
If NTLM is disabled at operating system or domain level, VisualCron cannot use NTLM on its own, because it has no separate NTLM implementation for network drives. Windows then uses Kerberos, or the connection fails.
Troubleshooting
Most headings below are Windows messages that follow "Could not map drive" in the message from the Server.
A specified logon session does not exist
On the VisualCron Server computer, open the Local Group Policy Editor and go to Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options. Set Network access: Do not allow storage of passwords and credentials for network authentication to Disabled. Then map the drive again.


The specified network password is not correct
Check the password of the Credential, and check that its user name and domain are those of an account that can access the share. If they are correct, also check that the clocks of the VisualCron Server computer and the file server are in sync.
The network path was not found / The network name cannot be found
These messages point to the server name or the share name. From the VisualCron Server computer, check that the server name resolves and that the share can be reached. Also check that Path is a plain UNC path, without a prefix such as http://, and that the share name is spelled correctly.
Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed
The Server service account already has a connection to that server under another user name, for example another drive in the list that uses a different Credential. Give every drive on that server the same Credential, or unmap the other drive, and map the drive again.
Access is denied
If the share is an IFS share on an IBM i (AS400) server and the Credential is correct, the IFS server may not accept the LAN Manager authentication level of the VisualCron Server computer. In the Local Group Policy Editor, under Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options, the setting is Network security: LAN Manager authentication level.
This policy applies to every outgoing connection of the computer, not only to VisualCron, and a lower level allows weaker authentication. Get approval from your security team before you change it.