Freeware / Open Source Softwares Installer in Single Click for Windows

After Installing an OS (Windows) we need to install tons of software and just sitting ideal in front of PC to wait for Accept License and click Next..Next.......and Next. Now : give a try to Ninite Software and get rid of all such problem, Simply

1. Click all the apps you want (Chrome/Firefox/AVG/Google Drive/VLC/Java etc.).
2. Click Get Installer and run it
    Ninite installs apps for you in the background. No clicking next. Say NO to
    toolbars or other junk.
3. Run it again later Your installer will update apps to the latest versions. If
     something is up-to-date it will skip it.


 Ninite - Install or Update Multiple Apps at Once.

source

Grub2 Splashimage

GRUB 2's splash image/background capability is greatly enhanced over its predecessor, GRUB 0.97. This page provides information on how to add a background image, change font colors and resolutions on the GRUB 2 menu without using a theme. The developers have created a set of compatible background images available as a package download but GRUB 2 accepts a variety of popular image formats. The user may choose any compatible image to use on the GRUB 2 menu.

sudo apt-get install grub2-splashimages

sudo update-grub 

Once installed, the images are located in the /usr/share/images/grub folder. 

1. GRUB_BACKGROUND setting in /etc/default/grub
2. First image found in /boot/grub
   • The first image found, in this order: jpg, JPG, jpeg, JPEG, png, PNG, tga, TGA
   • If multiple images of the same extension, alphanumerically.
3. Wallpaper designated in /usr/share/desktop-base/grub_background.sh (if desktop-base installed)
4. WALLPAPER= line in /etc/05_debian_theme * GRUB 1.98 only
   • The default setting is /usr/share/images/desktop-base/desktop-grub.png (the desktop-base package must be installed)
5. Default theme (no image): default_theme colors specified in /etc/grub.d/05_debian_theme

Note: Not all these options are available in GRUB 1.98

source

Autodesk AutoCAD : Network Deployment

Create a Deployment

Use this procedure to create a new deployment from the installer. In the process, you can create a default deployment by accepting the default configuration of each installed product, or you can create a custom deployment by customizing the configuration settings of one or more products in the deployment.

Important: When you specify the path to the administrative image, the use of a Universal Naming Convention (UNC) path is strongly recommended to ensure that the path will be the same for all users over the full lifecycle of the product. Also, if your administrative image is nested inside a series of subfolders, you risk exceeding the path length limit set by the Windows operating system. Avoid this possibility by placing your administrative image in a location at or near the top directory of the server, such as \\serverXX\Deployments.

1. Close all running applications on your computer.
2. Start the installer.
3. On the first page, if language choices are available, select a language for the deployment instructions, and then click Create Deployment.
4. On the Configure <name> page, Administrative Image section, specify the following data:
   1. Enter a descriptive name for the deployment that identifies the user group, platform, or other attribute to differentiate this deployment from others.
   2. Enter the path or browse to the shared network folder where you want to create and store your administrative image. Users install the program from this location.
   3. Select either 32-bit or 64-bit for the target operating system.
   4. Choose whether to include only the products required by this configuration.
      • If selected, the deployment cannot be modified in future to include additional products.
      • If unselected, the administrative image will include all possible products, so the current deployment can be modified in any way.
5. In the Installation Settings section, select one or more of these options:
   • Silent mode runs the installation in background, without prompting the user for any input.
     Note: Silent mode can automatically restart the user's computer without warning after installation.
   • Log file on each workstation can enable users to review and troubleshoot their own installations.
   • Network log file in a central location supports the network administrator in reviewing data for all installations.
     Note: The network log file must be in a shared folder where users of the deployment have read-write access. Otherwise, log data for user installations cannot be written to the log file.
6. Review and accept the Autodesk software license agreement.
7. On the Product Information page, select your license type, and enter your serial number and product key. If this data is valid, green check marks appear.
8. If you are sure that the product information is correct, click Next.
9. On the Create Deployment Configuration page, select the products to include in the deployment.
10. If you need to configure settings for a product, click the product name to open the configuration panel where you can review and change settings.
    Important: The configuration settings you choose apply to every instance of the product installed from the deployment. After the deployment is created, these settings can be changed only by modifying the deployment.
    Configuration settings vary widely by product. For more information, see the Installation Help supplement for the product.
11. Click Create to create the deployment.
    After the deployment is created, the Deployment Configuration Complete page opens, showing the path to the new deployment and a link for registering products online.
12. After you have finished using this screen, click Finish. 

To Create a Combined 32- and 64-bit Deployment

 

How to deploy products in a hybrid environment.

If you are deploying products on a network that includes both 32- and 64-bit computers, consider creating a combined deployment that detects the computer type and delivers the matching deployment.

Important: Before starting this procedure, ensure that all products in the deployment support 32-bit operating systems.

1. Create separate 32- and 64-bit deployments from the product installers and store them in the same deployment folder. Include either '32' or '64' in the deployment name to clearly designate the type.
2. In the deployment Tools folder, double-click the CombineDeploy.exe tool.
3. In the tool panel, browse to the 32- and 64-bit deployments, and then enter a descriptive name for the combined deployment.
   The combined deployment is saved in the same folder as the 32- and 64-bit deployments. 
   
   
    
   About the Administrative Image

   
   
   After you have created the deployment, users can install the program using the shortcut (.LNK file) located in the deployment folder with the administrative image. The shortcut name matches the deployment name that you specified when creating the deployment. Notify users of the shortcut name and location. Instruct them to double-click the shortcut to start the installation. If the deployment uses silent mode, advise users to keep other applications closed during the installation, because their computers might restart automatically after products are installed. 

   
   

   
   

   About Uninstalling Products

   
   

   Directs you to a batch file created with each deployment for this purpose.

   Each deployment includes a batch file that you can use to automate the uninstallation of some or all of the products in the deployment. Along with the file there is a text document that explains how to customize the batch file for your use. The files are located in the <deployment name>\SMS_SCCM scripts folder, and the file names are as follows:

   • <deployment name>_Uninstall.txt
   • Product_Uninstall_ReadMe.txt

   In summary, the process involves converting the .TXT file to a .BAT file with ANSI encoding, and then uncommenting a line in the file for each product that you want to uninstall.

   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   

Source

Desktop Sharing on Ubuntu

1. Opened Internet > Desktop Sharing
2. Checked Allow other user to view your desktop (and optionally Control desktop)
3. Require the user to enter this password: (then I put my password in)
4. Clicked Close. 

Then did "sudo apt-get update"

Then "apt-get install dconf-tools"

Started Internet > Dconf Editor and only did this:

dconf > org > gnome > desktop > remote-access > require-encryption - uncheck

Then was able to access it using Real VNC or TIght VNC using the password I entered above, using the default port.
 

Down side - vnc will only connect if I've logged into the physical machine.

Source

Reset Password in Ubuntu

Method 1

By default the first user's account is an administrative account.

1. Reboot your computer.
2. Hold Shift during boot to start GRUB menu.
3. Choose (recovery mode) 
4. Choose root from options 
5. You will be at root@ubuntu:~#
6. Put command      

       mount -rw -o remount / 

            

               OR

      

       mount -o remount,rw /

    7.  Next reset the Password

            root@ubuntu:~# passwd <first user name> 

            Enter new UNIX password: 

            Retype new UNIX password: passwd: 

            password updated successfully 

            root@ubuntu:~#

Source

Method 2

From the official Ubuntu LostPassword documentation:

1. Reboot your computer.
2. Hold Shift during boot to start GRUB menu.
3. Highlight your image and press E to edit.
4. Find the line starting with "linux" and append rw init=/bin/bash at the end of that line.
5. Press Ctrl + X to boot.
6. Type in passwd username.
7. Set your password.

Source

Ubuntu LAN Driver RTL8111/8168/8411

Ubuntu 14.04 Linux LAN Driver RTL8111/8168/8411 

Specially for Dell OPTIPLEX 3020 Desktop

Open Terminal and type the commands in sequence

sudo apt-get install linux-headers-generic build-essential dkms
wget http://ftp.us.debian.org/debian/pool/non-free/r/r8168/r8168-dkms_8.040.00-1_all.deb
sudo dpkg -i r8168*.deb
echo "blacklist r8169" | sudo tee -a /etc/modprobe.d/blacklist-r8169.conf
sudo modprobe -rfv r8169
sudo modprobe -v r8168
sudo service network-manager restart