1. Click Start, click Run, type regedit, and then click OK.
2. Navigate to the following key:
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
3. In the right pane, double-click the IRPStackSize value.
   NOTE: If the IRPStackSize value does not already exist, use the following procedure to create it:
   1. Click Edit, point to New, and then click DWORD Value.
   2. Type IRPStackSize, and then press ENTER to name the value.
      NOTE: Type IRPStackSize exactly as it is displayed. The value name is case sensitive.
   3. Click Edit, and then click Modify
   4. In the Data Value box, type 15 (decimal) and close the Registry Editor.
4. Click Edit, and then click Modify
5. Change the Base to decimal.
6. If you created the IRPStackSize value using the procedure described in step 3, the default value is 15. It is recommended that you increase the value by 3. Therefore, if the previous value was 11, type 14, and then click OK.
7. Close the Registry Editor.

If the problem persists after you complete this procedure, increase the value of IRPStackSize even more. The default value of the IRPStackSize parameter is 15. The range is from 11 (0xb hexadecimal) through 50 (0x32 hexadecimal).

You may receive an "Access Denied" error when you attempt to use one of the SmartCode VNC Manager remote managment tools, for example, Service Manager, or when you attempt to deploy VNC server to a remote PC. The steps below can help you to troubleshoot the problem:

• Make sure that you have entered a valid administrative logon credentials
• Windows XP: Simplified File Sharing must be turned off. To turn it off: Open Windows Explorer. Tools->Folder Options->View. Uncheck "Use simplified file sharing" item.
• Windows Vista / 7 / 8 / 10 / 11 with UAC turned on: Change the value of the LocalAccountTokenFilterPolicy registry entry on the remote Windows Vista/7/8/10-based computer so that the full credentials can be passed between the computer running SmartCode VNC Manager and the remote computer. For more information, see the following article in the Microsoft Knowledge Base.
• You should check that Allow Distributed COM setting is enabled on the computer you are trying to deploy to (it's enabled by default but some software might turn it off). To do so you should open Component Services snap-in. Start->Administrative Tools->Component Services. 
• When snap-in is running in the left tree navigate to: Console Root->Component Services->Computers->My Computer and select Properties command.
  NOTE: you must run the snap-in on the computer you are trying to deploy to. Or you can also connect to the computer remotely by running New->Computer context menu command available for the Console Root->Component Services->Computers tree node.
  
  Do not close the properties window and proceed to the next step.
• Ensure that under the default access permission the SYSTEM user has "Remote Access" permission enabled.
  
  

Watch demo video

The VNC Deployment Wizard

SmartCode VNC Manager includes the VNC Deployment Wizard that can be used for remote VNC deployment. No other VNC deployment solution offer such advanced features as ours. The Wizard supports deployment of the latest versions of UltraVNC, RealVNC and TightVNC.

To start the VNC Deployment Wizard open a context menu on the registered computers list and select VNC Tasks -> VNC Deployment Wizard command (Ctrl+D shortcut).

Page 1: Select Deployment Job

1. Allows you to start a new deployment job or reuse a previously saved one.
2. Contains list of previously saved deployment jobs.
3. This setting as well as the setting 4 will be enabled if "User previously saved VNC server deployment job" settings is selected.  If the "Skip..." checkbox is checked clicking on the Next button will skip the Deployment Wizard job settings page and bring you straight to the "Ready to Start VNC Deployment" page.
4. When you save a VNC deployment job the list of target computers is stored with the job. You have the options to reuse the same computer addresses or start with a new list. In this case the target computers list will be pre-initialized with the list of addresses of the computers selected in the registered computers list.

Page 2: Select Task

This allows to specify tasks that you want to execute. At least one of the tasks must be selected.

1. Place checkmarks next to the VNC distributions that you want to uninstall. Original VNC distributions are prefixed with "Native" text and VNC distributions deployed by the VNC Deployment Wizard are prefixed with "SmartCode".
2. Select a VNC distribution that you want to deploy to a remote computer from the combobox.
3. The "Upload custom registry entries" task allows you to create user-defined registry keys or values on a remote computer. This could be useful when you need further fine-tune VNC deployment process and customize VNC server settings that are not available via the Wizard configuration pages.

Page 3: Select VNC Deployment Components

This page allows you to specify which VNC components should be deployed. This page appears only if you selected to deploy a VNC distribution on the previous Wizard page.

1. Allows you to specify the installation folder. You can choose to the "absolute path" or let the Wizard to automatically determine the installation folder for you.
2. Allows you to specify which VNC components should be installed. The options that are grayed out are only available when you are deploying UltraVNC distribution.
3. These are setting that could be used to troubleshoot failed VNC deployment.
   "Create log file during deployment" - will create MSI log file on a remote computer.
   "Skip the post-installation validation step" - when this option is checked the VNC Deployment Wizard will run a WMI query that checks if the MSI package that has been deployed is actually listed in the Add/Remove programs list. Absence of the MSI package from this list is a sign that the deployment has failed.

Page 4: VNC Server Configuration This page allows you to specify the VNC server settings. Depending on the VNC distribution being deployed you will see settings supported by the particular VNC server software.

Page 5: VNC Server Firewall Settings

This page allows you to configure firewalls rules that will be created on a remote computer during VNC server installation.

1. Allows you to specify which firewall rules should be created.
   "Create a rule that controls connection for a TCP port" will open a single port in the remote computer firewall. It will use the port number that was specified on the VNC server settings configuration page.
   "Create a rule that controls connection for the VNC server executable file" will create a program exception rule that will allow [INSTALLDIR]\winvnc.exe process to receive incoming connections.
2. The profile checkbox allow to specify for which network profiles the firewall rule should be enabled. This feature is supported on a computer with Windows Vista or new OS installed.
3. If this checkbox is checked the firewall rules that were created by the Wizard will be deleted during VNC package uninstallation.

Page 6: Upload Custom Registry Values

This page allows you to specify registry keys and values that will be created on a remote computer. You can run this task as part of the VNC deployment or as stand-alone task when you need to upload a registry entries to a multiple computers. Alternatively you can use SmartCode Registry Editor that is part of the VNC Manager toolset that offers more advanced registry uploading features.

1. The Destination Registry via shows list of the registry keys and values that will be created on a remote computer.
2. The Connected Registry view allows you to connect to a remote computer and browse its registry. You can also use the "Add to Destination Registry" command to copy values from the Connected Registry to the Destination Registry view. This offer an easy way to copy registry settings from one computer to another without any need to use import to and export from a .reg file.

Page 7: Enter Target Computers Addresses This page allows you to specify to specify the computers on which the Wizard should execute its tasks. You must enter administrative logon credentials that will be used to login to a remote computer. You must provide a name for a shared that can be used to upload VNC installation package. The Wizard will use the user credentials 1) to open this network share.

Page 7: Completing the VNC Deployment Wizard This page allows you to specify to specify the computers on which the Wizard should execute its tasks. This list shows list of the deployment jobs statuses. Click on the Details or the Show Log buttons to see more detailed information. Check the "Save this deployment job" checkbox and type a new name if you want this deployment job to be saved.

APPLIES TO: SmartCode VNC Manager (Enterprise Edition) v5.0.16.0 or newer

Watch demo video

allow 0x3 domain\account
or
deny 0x3 domain\account

0x1 is ViewOnly, 0x3 is Interact and implies that you can also view the remote desktop.

domain can be a computername or the name of a domain.
If domain is not specified (like deny 0x3 account), Windows tries to match the account name to a local or a domain account.
It is not recommended to omit the domain part since this may lead to unexpected results.

account can be groupname or username.

If the accountname contains spaces, the domain\account expression is to be enclosed in quotationmarks:
allow 0x3 "domain\account"
Even if the accountname doesn't contain spaces, quotationmarks won't hurt.

MSLogonACL has two abbreviations for special domains:
one dot to denote the computername and two dots to denote the computer's domain:
.\account for a local account on the computer
or
..\account for an account in the computer's domain.

To enable MSI logging, you must perform the following steps:

1. Run the VNC Deployment Wizard.
2. Select a VNC distribution to install.
3. On the Select Components page check "Create log file during deployment" check box.
4. Proceed with the rest of the Wizard pages.

]]>

One of the “killer” features of SmartCode VNC Manager is the VNC Deployment Wizard that allows remote installation and un-installation of the most popular VNC distributions. The Wizard uses in-house developed MSI packages. This article list the public properties supported by the RealVNC 5.0.0 MSI package.

RealVNC Enterprise MSI package can be found at:
C:\Program Files\SmartCode Solutions\VNC Manager (Enterprise Edition)\RealVNC 5.0.0 (Repack by SmartCode Solutions).msi

The latest version of SmartCode VNC Manager can be found here.

APPLIES TO: SmartCode VNC Manager (Enterprise Edition) v6.9.1 or newer

One of the “killer” features of SmartCode VNC Manager is the VNC Deployment Wizard that allows remote installation and un-installation of the most popular VNC distributions. The Wizard uses in-house developed MSI packages. This article list the public properties supported by the TightVNC 2.7.110 MSI package.

TightVNC MSI package can be found at:
C:\Program Files\SmartCode Solutions\VNC Manager (Enterprise Edition)\TightVNC 2.7.10 (Repack by SmartCode Solutions).msi

The latest version of SmartCode VNC Manager can be found here.

APPLIES TO: SmartCode VNC Manager (Enterprise Edition) v6.8.8 or newer

1. Must have Windows XP/7/8/10/11 or Windows Server 2003/2008/2012/2016/2019/2022 installed.
2. Must have a writable share, which will be used by the deployment wizard to copy a VNC deplyment package to the remote computer
3. Windows XP: Simplified File Sharing must be turned off. To turn it off: Open Windows Explorer. Tools ⇾ Folder Options ⇾ View. Uncheck "Use simplified file sharing" item.
4. Windows Vista with UAC turned on: Change the value of the LocalAccountTokenFilterPolicy registry entry on the Windows Vista-based computer so that full credentials can be passed between the computer with the VNC Deployment Wizard and the remote computer. For more information, see the following article in the Microsoft Knowledge Base: How to change the Remote UAC LocalAccountTokenFilterPolicy registry setting in a Windows Vista image
5. The remote computer's firewall must allow WMI connections. To enable WMI connections, Open the Group Policy Object Editor snap-in (gpedit.msc) to edit the Group Policy object (GPO) that is used to manage Windows Firewall settings in your organization. Open Computer Configuration, open Administrative Templates, open Network, open Network Connections, open Windows Firewall, and then open either Domain Profile or Standard Profile, depending on which profile you want to configure. Enable the following exception: "Allow Remote Administration Exception" and "Allow File and Printer Sharing Exception".