Typically used for virtual environments like Citrix Provisioning or VDI where the use of -clone is not effective due to Device MIDs being the same.Įxample: wsasme.exe /key=xxxx-xxxx-xxxx-xxxx-xxxx /silent -uniquedevice The hostname remains untouched so it will be reported into the console exactly as it exists within the OS. In this case, the unique hostname will allow there to be unique machine IDs. This is useful if they have machines where the OS or hardware are cloned but the hostnames are always different. uniquedeviceTakes a checksum of the hostname and modifies the machine IDs with it. Note: For use when InstanceMID's are matching causing duplicates in the console or endpoints replacing endpoints at each poll interval. Wsasme.exe /key=xxxx-xxxx-xxxx-xxxx-xxxx /silent -clone If the OS is reinstalled, the ID will change. This value will persist if the agent is uninstalled/reinstalled so that existing agents won't move to other IDs. The product log will indicate this flag being present for the administrator to be aware of which PC they're looking at, for example "Applied unique machine ID: C8137921" where C8137921 matches the hostname, for example, PCHOSTNAME-C8137921, as well as the first 8 bytes of both the InstanceMID and DeviceMID to allow each of them to be identifiable and different than the original IDs. cloneFor cloned machines/VMs use this to have the agent create a persistent, unique value on the PC which will change what is displayed in the portal for the machine IDs and the hostname of the PC. Example: wsasme.exe/autouninstall=passwordīy default, SecureAnywhere does not display in the Add/Remove Programs list in the Control Panel, which prevents the user from removing the software in unmanaged mode. lockautouninstall=passwordCorresponds to /lockautouninstall. nostartInstalls without starting SecureAnywhere. key=keycodeInstalls with the provided keycode, with or without hyphens. More options are available for more information, contact Webroot Business Support. Run the installer from a command line, using any of the command options listed in the following table. On the endpoint, download the SecureAnywhere installer file:Ģ. To run a background installation from a command line:ġ. (You can only change the displayed language during installation, not after.)ĭuring installation, SecureAnywhere runs an immediate scan on the endpoint. To change the language displayed in SecureAnywhere, click the Change Language button and select from the supported languages. (CAPTCHA requires you to read distorted text on the screen and enter the text in a field before performing any critical actions.) This option enables self-protection and the CAPTCHA prompts. Protect the SecureAnywhere files, processes, and memory from modification.This option changes the Webroot installation filename to a random name (for example, “QrXC251G.exe”), which prevents malware from detecting and blocking Webroot’s installation file. Randomize the installed filename to bypass certain infections.This option places a shortcut icon on the Windows Desktop for SecureAnywhere. Create a shortcut to SecureAnywhere on the desktop.Optionally, you can click Change installation options at the bottom of the installation panel and set these options: Your keycode is shown in the Resources tab.ģ. In the installation panel (shown below), enter the keycode. The installer file is available from the Resources tab or by clicking this link:Ģ. On the endpoint, download the SecureAnywhere installer file. Use command-line options with the installer to deploy to endpoints that are behind a proxy server.ġ.Use additional commands with the executable file to deploy it in the background.This method is useful if you plan to use your own deployment tool and if you prefer not to use MSI commands to run the installation in the background.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |