| Setting up the server
For Assasin 2.0 to function properly you will need a correctly configured Assasin 2.0 SERVER installed on the computer(s) that you may want to administrate remotely. This section will explain the process of setting up and preparing the server before installing it on the remote computer. 1. Launching the server creator: In the Assasin 2.0 client, go to File->New server, the server creator should now pop up in a new window looking like this: 2. Past Server Records: This list is simply an organizer for your existing servers, each server is given an unique ID. You may select a server from the list to edit, or leave untouched to create a brand new server. 3. Server Type: You get to this section by hitting the 'server type' tab, this is where you select in what directory on the remote computer the server executable and configuration files should save to. You have the following options for directories that will hold the assasin directory: Windows Dir (server will create directory in c:\windows) System Dir (server will create directory in c:\windows\system32) Program Files (server will create directory in c:\Program Files). Please note: Assasin server will automatically detect the drive letter of which your operating system is installed on. After selecting the directory, you will have to select what to call the root folder for the assasin 2.0 installation. This option is called 'Dir to create'. Please keep the directory name as simple as possible to avoid any conflicts. Next step is to choose the executable name. This option is called 'EXE Filename'. It is important that you end the name with '.exe', for example 'server.exe' is a VALID name, but 'server' is INVALID. Now you have to choose weither you want to enable FWB (Firewall Bypass) or not. Simply select the one that is suitable to you. If you selected to use it, you can enter up to 3 executables that you would want to inject the server into, and what port the server should use for connections. If you choose to use FWB you may wonder how it works, here is a brief explanation: Once the computer with the server installed boots up, the server will inject itself into another applications memory space. This is the application(s) that you have to specify. If you want the server to bypass a firewall you will have to inject into an application that the firewall trusts. 4. Server Settings: You have to enter at least one http location of a text file, you may enter up to 3 to increase the chance of connection success. This option is called 'Urls' and will have to be entered in a valid format, e.g.: 'http://www.thehost.com/username/docs/log.txt' 'log.txt' will contain the connection details that the server will download and use. Note: If you don't set this option up correctly, it will result in the server not connecting to the client. Server icon: this option allows you to customize the icon for the server, you may want it to be like a program or image file. To change it click the folder icon, and browse until you find your icon. If left blank, a default icon will be assigned. 5. Startup Methods This is where you choose how you want the server to be started when windows starts. You can either make it start from registry every time the pc starts, from registry as a service or from win.ini/system.ini. Either of these settings will result in the same result (server starts when windows starts), but they work in different ways. If you are not sure what alternative to use, select Registry-Run and give it a simple key name. 6. Extra Settings Options These extra settings are partly optional, but it still recommended that you go through them all and set it up the way that you want. Unique Server ID: This number identifies the specific server, if you ever need to change a server at a later date this is very useful if you have a lot of servers. Password for connecting client side: This is a very important option, obviously. Very important to have a good password. When the server connects to the client, the client password will have to match the server password. Melt server: If this is selected, the installation file for the server will remove itself after it has been installed. Very useful if you are installing a lot of servers on a lot of computers as it saves you from deleting the setup file manually. Enable keylogger: If selected, offline keylogger will start logging as soon as the server is installed. Jpg dll, FTP dll, Fun dll, webserver dll - select the plugins that you want binded with the default installation file. You may want to leave them and upload them at a later date through the client (recommended). Extra binded file: Optional file that you can include in the installation package, this could be a picture or another executable that you wish to include in the installation package. 7. Notification: In most cases, you would like the server to notify you in some way when the computer that your are administrating remotely is online. There are lots of ways in Assasin 2.0: ICQ CGI MSN IRC PHP SMTP Each method has its own settings, you would normally only use 1 or 2 of these, but you can of course use as many as you want for each server. Your identification strings will apply to all of the notification methods. The interface of which you specify your notification settings is quite self explainary, although if you are not sure here is a quick explanation: When the server starts, it will send the notification straight away, e.g if you have configured ICQ notify to send a notification to a specific UIN, it will do exactly that. If you have it configured for MSN notify, it will log into the temporary account and send a message to your account with the notification string. This way you can instantly tell if any of the systems that you administrate are online. 8. Extra Messages If you haven't read the license agreement already, you should keep this box ticked so that it will show the agreement when the server is installed. If you agree to the terms you can choose not to display the message when the server installs. Optionally, you can specify a custom message to display when the server installs. 9. EXE/Service ban This feature allows you to dissalow processes or services on the remote system. If a banned feature is launched, the server will automatically shut it down. Use this feature with great caution, as it can result in system instability on the remote system if used incorrectly. 10. Summary: You should now be able to configure your server to a working standard. Now Experiment with the server locally to make sure that everything works properly before you deploy it. Back to help menu
Home | Disclaimer | Requirments | Help | Contact