Exceptional IT solutionsCodework Logo
Home Company Products Services Alliances Contact Us
Product Home
Download Trial
Features in Detail
Pricing and Ordering
User Guide
DataSheet
What's New?
BrowseControl
Enable and Disable Internet Usage to Control Surfing on PCs
Installation Help
1.  Does the BrowseControl Server Or Console need to be installed on a Server OS? Back
No, the BrowseControl Server is not restricted to a Server OS. It can be installed on Windows 2000 Professional, XP Home/professional.

The Console can be installed on Windows 98 and above.

Note: as of BrowseControl Version 2 the Windows NT operating systems is not supported.
2.  How do I install all components of BrowseControl onto a Single PC - Standalone/Home user? Back
If you are planning to use or test BrowseControl on a single PC, please install the Client, the Console and the Server onto the same computer. During the Client install, please enter LOOPBACK as the Server name when prompted.
3.  Why can't I see the Client in the Console window after installing? Back
This problem is typically caused via connectivity problems between the Console and Client. There are 2 methods that may fix this problem.

a) Check the client/console connection

  1. Ensure that the Client is installed with admin login rights
  2. Make sure the Client service is running.
  3. Make sure there are no firewall and/or virus scan software intercepting with the Client and Console.
  4. Use IP address instead of Computer Name to connect to the Console

    Run the following script on the run command of the Client PC: cwClient.exe –pv Admin (please note that Admin is case sensitive). If the password was changed during the installation of the Client, then please substitute it in place for “Admin”.

    This will bring up the client interface. On the interface, click on Connection tab to check the entry for the Server IP address or computer name. To edit the data click on the Edit button.

  5. Ping the Console from the Client.
  6. Ensure that port 3050, 8998 and 8999 is not used by any other application.
  7. Reboot Client.
b) Remotely redirect BrowseControl Clients connection to the desired Server

  1. From BrowseControl Console select Advanced --> Redirect Clients.
  2. The Server Name/IP Address to which the Clients are to be redirected will be retrieved automatically by the Console.
  3. Enter the Password of the Client which is to be redirected.
  4. You can either select to connect all BrowseControl Clients to the mentioned Server or specify the Clients that are to be redirected.
  5. Alternatively you can force all BrowseControl Clients with the Given Password to be connected to the current Server by checking the "Force connection to the current server" checkbox. This will force the Clients to get connected to the current Server even if they are connected to other Servers.
If you have further issues contact support@codework.com
4.  How do I configure BrowseControl so that it works with my Proxy Server? Back
You do not have to install BrowseControl onto your Proxy Server.

  1. On the BrowseControl Console menu, right click on the computers icon, select Group Settings. Click on the Port/Proxy tab. In the HTTP text box, enter the Proxy Server port. Ensure that the Filter Type is “HTTP Filter”.
  2. Add another HTTP port, with a Port No of 80 and Filter Type of “Blocked”.
5.  I have lots of machines and can not go to each one to install the BrowseControl Client.How do I deploy the Client? Back
There are two methods to remotely install BrowseControl Client on to desired PCs.

  1. BrowseControl is distributed in MSI (Microsoft Installer) format. This facilitates the deployment of BrowseControl through Microsoft Active Directory, SMS, Altiris and many other Software Deployment Tools that support the MSI Standard.
  2. BrowseControl has a built in Remote Installer. To use this feature follow the steps below. If you are running Windows Vista on the PC you intend to install the Client on, please disable UAC.

    1. On the menu bar click on Advanced --> Remote Install Client(s).


    2. Enter/Browse the path of the Client msi file on the Server computer.


    3. Enter the Server name/IP address and the Client password. In case the Client password is not mentioned then the password is taken as the default ‘Admin’. Click Next.


    4. Select the PC’s on the network where the Clients are to be installed. Click Next


    5. Enter the Username and Password of an Administrator account of the PC where the Client has to be installed. Click Next.


    6. The Client component will be installed on the selected PC.
6.  Why does the Remote Client Installer return the error messages “Access Denied” or “RPC server is unavailable”? Back
The most common error reported by the operating system for WMI problems is Access Denied. As you might have guessed, there are many causes for ‘Access Denied’ and ‘RPC server is unavailable’. The following list provides possible solutions for this issue.
  • Click Start, click Run, type in “net start rpcss” the Open box, and then click OK. Test to see if this resolves the issue. If the issue still occurs, continue to the next step.
  • Make sure that the username and password you have supplied for each computer correspond to an administrator account on the target computer. That account MUST have a non-blank password.
  • Check that DCOM is enabled on both the host and the target PC. Check the following registry value on both computers (go to start menu > run > type in “Regedit”):
    HKey_Local_Machine\Software\Microsoft\OLE. The value: Enable DCOM, should be set to 'Y'
  • Make sure WMI is installed. WMI is present by default in all flavors of Windows 2000 and later operating systems, but must be installed manually on NT4 systems. To check for the presence of WMI, type "wbemtest" into the Run box (Start Menu). If the WMI Tester application starts up, then WMI is present, if not, it must be installed.
  • On a Windows XP Pro computer, make sure that remote logons are not being coerced to the GUEST account ("ForceGuest", which is enabled by default computers that are not attached to a domain). To do this, open the Local Security Policy editor (e.g. by typing secpol.msc into the Run box). Expand the "Local Policies" node and select "Security Options". Now scroll down to the setting titled "Network access: Sharing and security model for local accounts". If this is set to "Guest only", change it to "Classic" and restart your computer.
  • Also on an XP computer running SP2, configure the firewall to allow remote administration. To do this, open a command prompt and type: netsh firewall set service RemoteAdmin
  • If you have other internal firewalls on your network, you may have to configure them to allow WMI messages.
  • Even if you are not knowingly running any firewall software, bear in mind that big-name antivirus solutions such as those produced by McAfee and Symantec often contain their own firewall functionality. If such software is not properly configured to allow WMI traffic, then this may be the cause of the problem.
  • Make sure that no remote access or WMI-related services have been disabled. On an XP machine, the following services should be running (or at least allowed to start on demand):
    COM+ Event System
    Remote Access Auto Connection Manager
    Remote Access Connection Manager
    Remote Procedure Call (RPC)
    Remote Procedure Call (RPC) Locator
    Remote Registry
    Server
    Windows Management Instrumentation
    Windows Management Instrumentation Driver Extensions
    WMI Performance Adapter
    Workstation