ECS Installation Manual

Basically to create an icon that prevent user from deleting it, we call this icon as shell object. If you don't what keyword to search in google, I would suggest using "create shell object". Anyway I found these two article which might help, if you are looking for article that help you create icon that cant be deleted by user or we call it shell object. Add Custom Folder to My Computer or the Desktop (All Windows) Popular http://www.pctools.com/guides/registry/detail/73/ Shellfolders & -objects Create and add your own folders/objects at places you're not supposed to, and make them behave like shell objects. http://www.virtualplastic.net/html/ui_shell.html ---

I found this Free Desktop Management Software , it might be something that you are looking. http://www.spiceworks.com/ Manage Everything IT... for Free! Spiceworks is the complete network management & monitoring, helpdesk, PC inventory & software reporting solution to manage Everything IT in small and medium businesses. Powered by 750,000 IT Pros Like You The Spiceworks IT Community is available to answer questions while you work directly in the application. It’s 100% Free. Download Now! Spiceworks is completely free…and you can get started in less than 5 minutes. Download now . ---

I found these two articles about booting into acronis environment using PXE. Source : http://thesystemadministrator.com/the_system_administrator/tips_%26_tricks/pxe%2c_aka_pre-execution_environment_-_part_1/ http://thesystemadministrator.com/the_system_administrator/tips_&_tricks/pxe,_aka_pre-execution_environment_and_acronis_-_part_2/ Few days ago, I’ve received 50 new servers without any OS preinstalled. The servers came without floppy drive and CD/DVD. I tried to connect an external CD (USB) or Disk on Key, but servers didn’t start. So, I decided to run PXE Boot . If you don't know what PXE is, here’s what is written in Wikipedia: “The Preboot Execution Environment (PXE, aka Pre-Execution Environment, or 'pixie') is an environment to boot computers using a network interface card independently of available data storage devices (like hard disks) or installed operating systems.” There are several solutions of PXE implementation. Microsoft has its Remote Installation Ser

For those who still need to use vi instead of vim, this might be a good guide. Introduction The VI editor is a screen-based editor used by many Unix users. The VI editor has powerful features to aid programmers, but many beginning users avoid using VI because the different features overwhelm them. This tutorial is written to help beginning users get accustomed to using the VI editor, but also contains sections relevant to regular users of VI as well. Examples are provided, and the best way to learn is to try these examples, and think of your own examples as well... There's no better way than to experience things yourself. EX Commands Conventions In this tutorial, the following convention will be used: ^X denotes a control character. For example, if you see: ^d in the tutorial, that means you hold down the control key and then type the corresponding letter. For this example, you would hold down the control key and then type d . Before You Begin The VI editor uses the fu

If you need a guide on how to configure SSH automation login, here is the steps. SSH Automatic Login Of course this is not the right phrase for it. It should be something like “key-based authorization with SSH”. Or simply “publickey authorization”. Or “unattended ssh login”. But I guess you know what I mean. Here are the steps: 1. Create a public ssh key, if you haven’t one already. Look at ~/.ssh. If you see a file named id_dsa.pub then you obviously already have a public key. If not, simply create one. ssh-keygen -t dsa should do the trick. Please note that there are other types of keys, e.g. RSA instead of DSA. I simply recomend DSA, but keep that in mind if you run into errors. 2. Make sure your .ssh dir is 700: chmod 700 ~/.ssh 3. Get your public ssh key on the server you want to login automatically. A simple scp ~/.ssh/id_dsa.pub remoteuser@remoteserver.com: is ok. 4. Append the contents of your public key to the ~/.ssh/authorized_keys and remove it.