Items filtered by date: December 2015

Sunday, 05 September 2010 17:47

My Ubuntu Linux Notes

These are my notes specific to Ubuntu Linux.

Logical Volume Management (LVM)

This is enabled by default in the Ubuntu setup but can easily be unchecked and avoided.

  • General
    • Key Features
      • LVM is a dynamic disk that has to be online to be cloned.
      • Partitions can be resized or moved while online without affecting services.
      • LVM can do snapshots.
      • The LVM has to be on for it's partitions to be cloned.
      • It is designed for larger installations.
    • Don't use for Virtual machines. Snapshoting will be done above the VM if at all (i.e. TrueNAS). Adding LVM adds an extra layer of complexity.
    • Other phrases: LVM Group / LVM Volumes / LVM Storage / Dynamic LVM GPT
    • Lvm - Ubuntu Wiki - LVM stands for Logical Volume Management. It is a system of managing logical volumes, or filesystems, that is much more advanced and flexible than the traditional method of partitioning a disk into one or more segments and formatting that partition with a filesystem.
    • server - What is LVM and what is it used for? - Ask Ubuntu
      • As a Linux/Ubuntu newbie, what is LVM and what is it used for? In terms of a web server installation, what benefits does it provide? Would you recommend using it?
      • You can think of LVM as "dynamic partitions", meaning that you can create/resize/delete LVM "partitions" (they're called "Logical Volumes" in LVM-speak) from the command line while your Linux system is running: no need to reboot the system to make the kernel aware of the newly-created or resized partitions.
      • Other nice features that LVM "Logical Volumes" provide are:
        1. If you have more than one hard-disk, Logical Volumes can extend over more than one disk: i.e., they are not limited by the size of one single disk, rather by the total aggregate size.
        2. You can set up "striped" LVs, so that I/O can be distributed to all disks hosting the LV in parallel. (Similar to RAID-0, but a bit easier to set-up.)
        3. You can create a (read-only) snapshot of any LV. You can revert the original LV to the snapshot at a later time, or delete the snapshot if you no longer need it. This is handy for server backups for instance (you cannot stop all your applications from writing, so you create a snapshot and backup the snapshot LV), but can also be used to provide a "safety net" before a critical system upgrade (clone the root partition, upgrade, revert if something went wrong).
      • While being most useful on server systems, I think that features 1. and 3., combined with LVM's ability to create/resize/delete LVs on the fly, are quite handy on desktop systems as well. (Especially if you experiment a lot with the system.)
      • Downsides
        • Of course, all of this comes at a price: the initial setup of LVM is more complex than just partitioning a disk, and you will definitely need to understand the LVM terminology and model (Logical Volumes, Physical Volumes, Volume Groups) before you can start using it. (Once it is set up, using it is much easier, though.)
        • Also, if you use LVM across hard drives, you may lose all your data when only one drive fails.
        • What is LVM?
        • When should you use LVM?
          • The first thing your should consider before setting up LVM is what you want to accomplish with your disks and partitions. Some distributions, like Fedora, install with LVM by default.
          • If you are using Ubuntu on a laptop with only one internal hard drive and you don't need extended features like live snapshots, then you may not need LVM. If you need easy expansion or want to combine multiple hard drives into a single pool of storage then LVM may be what you have been looking for.
        • Setting up LVM in Ubuntu
    • What is Logical Volume Management and How Do You Enable It in Ubuntu? | How-To-Geek
      • Logical Volume Management (LVM) is a disk management option that every major Linux distribution includes.
      • Whether you need to set up storage pools or Logical Volume Management (LVM) is a disk management option that every major Linux distribution includes.
      • Whether you need to set up storage pools or just need to dynamically create partitions, LVM is probably what you are looking for.
      • First thing to know about using LVM is there is no easy way to convert your existing traditional partitions to logical volumes. It is possible to move to a new partition that uses LVM, but that won't be something that we will cover in this article.
    • Logical Volume Manager (LVM) versus standard partitioning in Linux | Enable Sysadmin | Red Hat - Use this guide to integrate the flexibility, scalability, and increased features of LVM into your server storage strategies. Traditional partitioning is good, but LVM is better.
  • Misc
  • Tutorials
  • Cloning / Imaging
  • Backup
    • How To Take LVM Backup In Easy Steps | Zindagi Technologies - In our previous blog, we show how we configure Logical Volume Group. Now, if we are talking about LVM backups, for many several reasons a volume group may become corrupted after unintended user intervention. there are two useful commands – vgcfgbackup and vgcfgrestore. Using this command, we take a backup of our accidentally delete the volume and we also restore it. These commands allow you to back up the metadata of the volume group. In many cases, the LVM configuration is corrupted. LVM may also be damaged when some disk fails and rebooting OS fails to boot. Therefore, it is important to have an LVM configuration backup.
  • Resizing

 

SORT these below

  • Use Synaptic Package Manager in the GUI for a easier experience installing and removing packages.
    sudo apt install synaptic
  • The location where packages are run from and placed with wget are /home/shoulders/
  • By default the root account is disabled for security.
  • gadmin-proftpd is a GUI for proftpd ftp server
  • sudo / su is a command to allow you to run as root. Similiar to 'Run as administrator'
  • Alt + F2 brings up the terminal
  • First press "Alt F2" on your keyboard then type in "gksu nautilus".
  • Now you are running the file browser as root in gnome.
  • Or you can do the same thing in kde only look for "run command" in the kmenu and type in "kdesu dolphin".
  • To run file explorer as root

 

 

 

 

Published in Linux
Sunday, 05 September 2010 17:39

Retrospect Various Issues

Retrospect will not sync files and copy data properely even when configured properely, try the following

  • make more free space on the drive i want to back up ie. D: drive
  • delete the configuration file and resetup
  • turn of damon tools, reg mechanic , antivirus and other stuff like that
  • reinstall might help
  • leave for ages

Also See Understanding the Retrospect HD Restore Log [193431]

Log Location

Vista / Windows 7 - C:\ProgramData\RetroExp\operations_log.utx

Published in Data Recovery
Sunday, 05 September 2010 00:00

How to Install Sage Corporation TAX

  • Corporation Tax is files based
  • These are the files to backup
    c:\Shared Files\Sage Corporation Tax\
  • there are good upgrade instructions on the install disk
  • on josies server the files are located at c:\Shared Files\Sage Corporation Tax\
  • the client data files are located c:\Shared Files\Sage Corporation Tax\Client Data\
  • all client machines have their z:\ drive mapped to c:\Shared Files\Sage Corporation Tax\
  • the update only updates sage corporation tax and will not affect any other sage product. it primarily only update the programs software but can alter databases.

Installing Sage Corporation Tax as a network install version

First, On the server:(assumes server name is \\server)

  • create a folder for containing all you sage corporation tax files, i used 'Sage Corporation Tax' and i placed it on the server as follows:
    C:\Shared Files\Sage Corporation Tax\
  • share out 'Sage Corporation Tax'. I gave everyone access rights (tweak these if required)
  • within 'Sage Corporation Tax' folder,  create 2 sub folders:
    'Install Files'  - this will contain install files
    'client Data'  - this will contain the actual data
  • copy the content of the whole install CD from sage to 'Install Files'

Second, your first client PC: - might be required on secondary client PCs, or just run setup from network location - needs checking

  • map Z:\ drive to \\server\Sage Corporation Tax   -  (if you have issues use a batch file to create persistent connection)
  • run setup from the z:\Install Files
  • follow the installation through as default until you come across, set the 'shared files location and 'working folder'. Set as below
    shared folder = Z:\
    working folder = Z:\Client Data\
  • continue installation and finish
  • run sage corporation tax and login
    default username and password are:
    administrator
    password
  • you should now be prompted to enter a serial/activation key, for this contact sage

tweaks that are required after install:

  • NB: short name = client file name

check software is correctely pointed to files

  • open up corporation tax tools\application settings\shared folder
    password = (changes every hour, get from sage)
    it should say z:\

network deployment settings

to setup the the automatic client machines over the network automatically a folder has been setup on the server
c:\Shared Files\Sage Corporation Tax\Install Files\
This needs to be tied in to the client machines as follows:

set this folder for network deployment in sage tracker

  • open Programs / SAGE / Sage Tracker (powered by ONESOURCE)
    default username and password:
    administrator
    password
  • goto File / Launch Policy Editor
  • This will open the  'ONESOURCE Policy Settings' Window
  • select the 'Network Deployment' Tab
  • set the CD image location to:
    Z:\Install Files  -  (not  c:\Shared Files\Sage Corporation Tax\Install Files\)
  • 'Policy file'  should be pointing to Z:\client.policy

you can then copy all the contents of the corporation update cd from sage in to the is folder
c:\Shared Files\Sage Corporation Tax\Install Files\, if there is already stuff in there delete it.
now when a client logs in to there machine it will prompt for an update to be applied etc..

Additional Operations

create a new company

  • intially we need to make sure the client files default location is correct
  • select save
  • it should prompt you where to save files, select Z:\CLIENT DATA
     

delete a company

  • this is done through 'sage tracker', open the tracker software
  • select files/clients/remove
  • a tree structure will with a + next to it to and it will expands to like below:

    All year-ends for all clients
    All year-ends for Lancastrian It
    31/03/2010 - z:\CLIENT DATA\Lancastrian IT09.ABC
    31/03/2010 - <unknown>
     
  • you put a tick in what you want to delete.

    - selecting All year-ends for all clients deletes everything,
    - to delete just the company in question select All year ends for Lancastrian IT09.ABC
    - or you can just delete a particular period for a particular company

UPGRADING -  (when a new CD comes out)

  • delete the contents of the z:\Install Files\ (on the server it is c:\Shared Files\Sage Corporation Tax\Install Files\ ) and then copy the new CD contents into it.

Following the instructions below if sage prompts for a software update when a user logs on:

The client is prompted to run the update the following options appear

First Page of options:

  1. select single user
  2. select multi user

you should choose multi user

  • single user will install all files locally
  • multi user will assume that the install is a network based and will read the setup information, and use that setup information to perform the update with the network settings already in place

- leave the install directory alone as you do not need to change it from default
- the install then starts.
- that is all that is required the software will now work as normal

Backing Up

  • sage corporation tax has no automatic backup procedure
  • to backup the following folder on the server needs to be backed up
    c:\Shared Files\Sage Corporation Tax\  (possibly just client data)
  • if normal backup is configured to backup the whole of the c:\Shared Files\, nothing else is required as backups are by proxy automatic

Additional Notes - not clarified and at what point they are needed. They should be part of intial installation or possibly the upgrade procedure

  • Next
  • Accept
  • Select Multi User
    Destination Folder = C:\Program Files\Sage\SCT(pbo)\
  • next
    working folder = Z:\Client Data
  • next
    abacus = onesource
  • check sage Tracker works

 

Sage Corporation Tax is not SQL based but file based

Additional Notes

I found these notes about installing Sage Corporation Tax, I am note sure when i did these and if they are better than the ones above. So for completeness i am adding them. I can always delete them later if they are no good.

Installing sage corporation tax

  • on the server setup a shared folder, i used 'Sage Corporation Tax', mapped to clients as Z:\
  • Create 2 folders, 'Install Files', 'client Data'
  • copy the files of the install CD to 'Install Files'
  • run setup from the z:\Install Files
  • follow the installtion through as default until you come across an options to set the 'shared files location
  • set this location as z:\
  • continue installation and finish

default username ad password are

administrator
password

  • run sage corporation tax and login
  • you should now be prompted to enter a serial/activation key, for this contact sage

tweaks that are required after install:

short name = client file name

  • check software is correctely pointed to files

    open up corporation tax  tools\application settings\shared folder
    password = 20 (changes every hour)
    it should say z:\
  • network deployment settings

    open up sage tracker  file\launch policy editor
    network deployment
    make sure it points at z:\Install Files

    when a new CD comes out, delete the contents of the z:\Install Files and then copy the new CD contents into it.
    When a user then logs on, sage will prompt for a software update if required.
  • intially we need to make sure the client files default location is correct

    create a new company
    select save
    it should prompt you where to save files, select Z:\CLIENT DATA
  •  delete a company

    this is done through 'sage tracker', open tracker
    select files/clients/remove
    a tree structure will with a + next to it to and it will expands to like below:

    All year-ends for all clients
      All year-ends for Lancastrian It
        31/03/2010 - z:\CLIENT DATA\QuantumWarp09.ABC
        31/03/2010 - <unknown>

    You put a tick in what you want to delete.
    - selecting All year-ends for all clients deletes everything,
    - to delete just the company in question select All year ends for Lancastrian IT09.ABC
    - or you can just delete a particular period for a particular company
Published in Sage
Sunday, 05 September 2010 00:00

How to Install Sage Accounts Production

  • sage acounts productions is file based
  • the data to backup is
    C:\Shared Files\Sage Accounts Production\  (data is actually in C:\Shared Files\Sage Accounts Production\\APEXDATA\)
  • install disc has some good instructions on it
  • 'Sage Practice Solution' is SQL based and present on the same disc

These are instructions to set Sage Accounts Production as a network based setup

These instructions install the data files and a setup program to the remote location you select only. it does not install the software but rather create the data container


The Following Assumes:

  1. the server is called \\server
  2. shared folder for Sage Accounts Productions Data is - C:\Shared Files\Sage Accounts Production\
  3. mapped drive letter to use on the clients is Y:

Server:

  • create a folder on the server

    C:\Shared Files\Sage Accounts Production
     
  • share it out, everyone permissions unless other is required
  • put install CD in the Server
  • Run setup/install
  • select network install
  • next
  • you will no be prompted to confirm where the 'Client List' and 'Client Data' will live. (This part will configure the ini file of the shared folder), Set as follows:

    Client List - Y:\APEXDATA\  -  aka 'Client List Path'
    Client Data - Y:\APEXDATA\  -  aka 'Default Data Path'
     
  • click next and finish install
  • The server setup should now be finished and you will see the following message.

sage-accounts-production-workstation-client-software-UNC

Client Setup

  • map  \\server\Sage Accounts Production\ folder to Y:\
  • Run Y:\setup.exe
  • this will install 'Sage Accounts Prodcution' to the local/client machine with the settings already preset from the server (ie data locations)
  • on a fresh install the serial which is randomly created in the software needs to be validated by Sage,
  • once validated on one machine all installs are validated because it validates the data files not the PC
  • do updates, and is now done

Upgrading

Server

NB: 'Practise Solution' is installed as well as 'Sage Accounts Productions' from the same disk.

  • put DVD in to the server
  • click next
  • backup page appears
  • backup files for practice solution
  • doing install
  • the process backsup 'Sage Financial Database'

Client

  • open client and they will start to update
  • select workstation if asked

Additional Notes

I found these notes about installing Sage Accounts Production, I am note sure when i did these and if they are better than the ones above. So for completeness i am adding them. I can always delete them later if they are no good.

Installing Sage Accounts Production?

  • create a folder on the server
  • share it out, i used y:
  • put cd in and run on client
  • select network install

what this does is installs the data files and a setup program to the remote location you select only.
it does not install the software but rather create the data container

  • when the above has completed go to the shared 'Sage Accounts Production' folder ie y:\ and run setup.
    - this will install 'Sage Accounts Prodcution' to the local machine with the settings already preset
  • on a fresh install the serial wihich is randomly created in the software needs to be validated by sage,
    - once validated on one machine all installs are validated because it validates the data files
  • do updates, and is now done

Updating

Just run this, select workstation and all is well

\\SERVER\Sage Accounts Production Installers\Sage AP\Updates\Workstation\Setup.exe

Update Alert

Your workstations might see this message pop up if there is an update available

sage-account-production-update-is-now-available

 

Published in Sage

Method 1

  • For Windows XP and 2000 users, open and copy from the following location:

    C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref

  • Windows Vista and Windows 7 users, open and copy from the following location:

    C:\ProgramData\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref

Method 2

Download a manual definition updater here

 

Published in Malware Removal

When I try to set up a Laserjet 1012 on 32 bit Windows 7, the machine chooses IEEE 1284.4 generic printer drivers, and the installation fails. The printer shows up as an HP 1012 under Unspecified devices, and nothing new shows up under Printers and Faxes. I have HP VIsta drivers that HP claims will work under Windows 7.


1. Install the printer with the following drivers (please note that this works on the 32-bit version of Windows 7)

HP LaserJet 1012 Printer- HP LaserJet 1010/1012/1015 Host Based Driver - HP Business Support Center

2. The printer might not work at first, but it is ok, as long as Windows grabs the drivers into its database.

3. Go to START > Devices and Printers... Remove ALL your printers...

4. Restart your computer

5. After logging in, Windows will automatically detect and reinstall your printers, including the HP1012 using a driver called HP1012HB

HB stands for Host Based.

or

1) Select the driver manually.
2) Click "Windows Update" to force Windows to refresh the driver list.
3) Select HP Lasterjet 1015.

or

The 1012 will install on my 64-bit Windows 7 Home Premium machine two ways:

1. Download the LaserJet 1015 64-bit host based driver from the HP site and extract it to a folder on your hard drive. Install the 1012 and point to the folder when prompted for a driver. The printer will show up as a LaserJet 1012HB. The downside to this solution is that printing will take up to twice as long as you're used to.

2. Click "add a printer" and install a phantom LaserJet 3055 PCL5 using the Windows version of the driver (you may need to use Windows Update for that choice to show up.) Plug in the printer and it will be recognized as an "unrecognized device," but it will print as the LaserJet 3055 (you can make that the default.) The unrecognized device Icon may eventually disappear -- mind did.

The 3rd method some people have suggested -- installing a phantom 1015, then trying to install the 1012 XP driver, then deleting the 1015, then plugging in the printer -- works on my 32-bit machine but not the 64-bit.

Meanwhile, with the help of a post in another HP thread, I was able to solve the issue of printing across the network! The author wrote:

"Re: printing to HP laserjet 1012 on home network I'd say that the driver that the XP machine is using is the not the same name as the driver that is installed on the Vista machine. You will not be able to connect to the printer over RPC (Remote Procedure Calls) but you can connect using SMB (Server Messaging Blocks).

Create a local printer on the Vista machine that uses a Local Port in the form \\XPMachine\Printshare. Use the driver that was installed when you plugged the device directly to the USB port."

Published in Windows 7
Saturday, 04 September 2010 19:48

How to stop auto import of images by Picasa

Whenever I put my memory card in the card reader, it would open Picasa and start to import, pictures and videos. I organize my photos in my E:/ partition, and do not want Picasa to import anything unless I specifically tell it to.


To stop Picasa from uploading all your pictures from the card, go to Windows Explorer, right click the card and select Properties. Then select the AutoPlay tab. Then, in the drop down box, select "Mixed content". Then click "Open folders to view files". [Apply] and [ OK ]. Now when you plug in the card in the card reader it'll only open a  Windows Explorer window so you can view the files.

Published in Applications

Internet Explorer was not able to open this Internet site can happen when you try and download a PDF from a HMRC website. It seems to be caused becaus ethe PDF needs to be encrypted.


If you use Microsoft Internet Explorer you may need to adjust your settings to successfully download the software.

In Internet Explorer for Windows:

(1) go to Tools - Internet Options

(2) Advanced tab

(3) under Security, ensure the ‘Do not save encrypted pages to disk’ is checked

(4) click Ok

Published in Microsoft Other

Cause

The add-in was installed under another user account and the OfficeLive registry subkey necessary for that checkbox entry to be logged in the registry is not created for other users. You need to manually create the OfficeLive subkey under HKEY_CURRENT_USER\Software\Microsoft for any user on that computer that wants to suppress that add-in by checking the box. After the OfficeLive subkey is created the appropriate registry entry FirstRunDontShow will be created once Word, Excel, and PowerPoint are started and if the checkbox is selected it will no longer show on subsequent launches of those applications.

The issue can be resolved by adding a base registry key named OfficeLive under the HKEY_CURRENT_USER\Software\Microsoft subkey, once that key has been created the next time you start Word it should create two new DWORD entries (FirstRunCredsDeleted and FirstRunDontShow), both set to 1.


Solution

Install Office Live Update 1.4

http://www.microsoft.com/downloads/details.aspx?FamilyId=36bac9da-1ee4-40df-b06c-a327269f2b63&displaylang=en

OR Registry FIX

Steps:

WARNING : If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

1. Logged in as the user that has the problem, click on Start, clcik Run, type regedit, click OK.

2. On the left pane expand HKEY_CURRENT_USER, expand Software, select Microsoft.

3. From the Edit menu point to New and select Key.

4. Type OfficeLive and press the Enter key.

5. Close Registry Editor.

6. Start Word, Excel, or PowerPoint, you'll get the prompt, make sure 'Do not show me this message again' is checked, click Continue.

7. Close the application (Word, Excel, or PowerPoint), the registry DWORD values should be created under OfficeLive for that user.

Published in Microsoft Office
Saturday, 04 September 2010 19:07

Why is LPR Byte Counting Enabled required?

Question: RPM does not receive print jobs from the Windows Standard TCP/IP Port unless the LPR Byte Counting Enabled option is selected. What is "LPR byte counting" and why must it be selected?

Answer: The simple answer is this: if Microsoft implemented their LPR to send zero as the number of bytes, then RPM would be able to handle that correctly. As it is Microsoft sends an impossibly huge number, instead of the actual size of the file in bytes.

The LPR/LPD protocol allows for zero as the file size though sending the actual size is typical. There are a few LPR clients in the world which handle this correctly, and RPM works as you would expect in either case.

The longer answer follows.

"LPR byte counting" forces Windows to count the number of bytes in the file and send this value in the Receive data file subcommand. To understand why this does not work, you must first understand the steps in sending a print job using the LPR/LPD protocol.

  1. The LPR client sends the Receive a printer job command.
  2. RPM replies with an acknowledgment (ACK).
  3. When the LPR client receives the ACK, it can proceed. The client then sends the Receive control file subcommand.
  4. When the LPR client receives an ACK from RPM, the control file is sent. RPM will then respond with another ACK.
  5. The LPR client now sends the Receive data file subcommand. The size must either be set to the actual size of the data file, or set to 0. This is one area where Microsoft does not follow the protocol specifications.
  6. When the client receives the ACK, it will send the data file. Once the data file has completed, the connection is closed by both parties.

When LPR byte counting enabled is turned off, Microsoft sets the <file size> to a size much larger than the actual size. It is set neither to 0 nor the actual file size. When RPM receives a file much smaller than the specified file size, RPM believes that the entire file was not sent, deletes the "incomplete" file, and waits for the file to be sent again.

RFC1179 states that you may set the size of the data file to 0, however, it does not discuss how the LPD Server should handle this "unknown length file". RPM handles the "unknown length file" situation by receiving all data from the request to send the data file until the connection is closed by the LPR client.

RPM can also handle the opposite situation, in which the file is actually 0 bytes. You tell RPM to close the connection after a specified amount of time.

To do this, follow these instructions.

  1. Choose LPD Options from the Options menu.
  2. Select Enable zero length file transfers. 600 seconds is the default amount of time to wait, however, you may raise or lower this value to meet your needs.
Published in Printers
Page 79 of 96