Stop the SPAM free for 14 days!

Stop the SPAM free for 14 days!

Is your Inbox continually flooded with unwanted email?
Are you tired of wasting valuable time deleting SPAM?
Does SPAM make your Blackberry or iPhone practically unusable?

Eitex has the answer!

Spam is a big problem for organisations that receive thousands of harmful and unwanted emails everyday. Today, spam accounts for 85-90% of all emails. With external email scanning from Eitex you can forget all about spam and viruses, and concentrate on tasks that will add value to your business.

Interested?

We are currently offering a free 14 day ‘Stop the SPAM’ trial. You simply will not believe how effective the service is!

There is no software to install* and no system downtime.

A product brochure is available at www.eitex.co.uk/downloads/SPAM.pdf

How do I get my free trial?

To Sign-up for your free 14 day trial please enter your details on our Enquiry Form with the words 'Stop the SPAM' in the 'Nature of Enquiry' field.

Alternatively if you would like to discuss this further, please call me directly on 01924 918 419.

Dean Spencer
SPAM Assassin

'Pay as you go' IT Support

Eitex have launched a 'pay-as-you-go' IT Support service which is thought to be the first of its kind.

The ‘pay-as-you-go’ model is used by mobile phone companies and proves to be very popular for clients who want the same level of service, but don't want to be tied to an annual contract for IT Support.

The revolutionary concept means that customers are able to buy or top-up minutes as they would with a mobile phone, and use those minutes in exchange for IT Support as and when needed. Managing director Dean Spencer said: “We have always endeavoured to stand out from the crowd by being onestep ahead of the competition, and this service has been no different."

We pride ourselves on thinking outside the box. “The service does away with an annual contract which makes it attractive to smaller businesses and it’s also attracting attention from some larger clients too”.

The PAYG IT Support service is offered throughout Yorkshire and the UK.

Automating Badmail housekeeping on an IIS SMTP Server, or even disabling it completely!

Anyone managing an IIS SMTP Server will probably at some time or other come accross the problem of how to manage the Badmail folder, which in most cases, if left unattended will grow huge, but more important will contain thousands if not millions of files, thus affecting the performance of the server in question, or at least slowing down admin tasks on the server.

A lot of users will probably manually clean out the folder periodically or better still setup a batch file as a scheduled task, however there is a better way.

Microsoft's Exchange team wrote a script some time back to help manage this problem on Exchange Servers and the script works equally well for IIS. It is a lot more configurable than a simple Batch file and allows you to either remove or archive old Badmail for a set period. It even has an option to disable Badmail completely should you wish. The scipt and further information is available at the URL below. It comes as a self extracting archive and I cannot stress enough that you should read the accompanying Word Document "Badmail Deletion and Archival Script.doc" that extracts with the script before using it.

http://support.microsoft.com/?id=867642

If you just want to disable Badmail however and want to do it manually, quickly and easily, rather than using the script, all you need to do is to Deny Write Access for the SYSTEM account to the Badmail folder, however I went the whole hog and stopped all accounts having write access to the folder, however ensure you are the owner of the folder before you do this, just in case ;-)

Please note however that you should not disable Badmail generation if there are any applications that use the SMTP PickUp mail folder. Badmail generated by PickUp will then not leave the PickUp folder and the SMTP Server will repeatedly try to move the file to the Badmail folder which can cause performance problems.

As usual, you use any of the information here at your own risk. This worked fine for me, but we are not responsible for any issues relating to this blog.

If you require any assistance though please feel free to contact us about our products and services.

Andrew Aedy
Eitex IT Support

Move shares from one server to another.

Ever need to move shares from one server to another or need to reinstall Windows over an existing installation? Whilst keeping NTFS permissions and Share permissions? Well here's how.

The steps that are outlined below shows you how to modify the registry. Serious problems might occur if the registry is modified incorrectly. Please take care and use this method at your own risk. Please take a full backup of your server/computer including the registry before continuing with this procedure.

To save only the existing share names and their permissions on Windows follow these steps. Note This procedure applies only to NetBIOS shares and not to Macintosh volumes.

A. On the existing Windows installation that contains the share names and permissions that you want to save, start Registry Editor (Regedt32.exe).

B. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
SYSTEM\CurrentControlSet\Services\LanmanServer\Shares

C. Save or export the registry key.
o For Windows NT and Windows 2000, click Save Key on the Registry menu.
o For Windows Server 2003, click Export on the File menu.

D. Type a new file name (a file extension is not necessary), and then save the file to a floppy disk or removable USB drive.

E. Reinstall Windows or move data from one server to another.

F. Run Registry Editor (Regedt32.exe). (On newly installed server or on Destination server)

G. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
SYSTEM\CurrentControlSet\Services\LanmanServer\Shares

H. Restore or import the registry key.
o For Windows NT and Windows 2000, click Restore on the Registry menu.
o For Windows Server 2003, click Import on the File menu.

I. Type the path and file name of the file that you saved in steps 3 and 4.
Caution This step overrides the shares that already exist on the Windows computer with the share names and permissions that exist in the file you are restoring. You are warned about this before you restore the key.

J. Restart the server.

Note After you complete this procedure, if you decide that you should not have restored the Shares key, restart the computer and press the SPACEBAR to use the last known good configuration. After you restore the shares key, the shares can be used by network clients. If you run the net shares command on the server, the server displays the shares; however, File Manager does not display the shares. To make File Manager aware of the newly restored shares, create any new share on the server. File Manager displays all of the other shares after you restart the server or stop and restart the Server service.

Only permissions for domain users are restored. If a local user was created in the previous Windows NT installation, that local user's unique security identifier (SID) is lost. NTFS permissions on folders and files are not affected when you save and restore the shares key.

This is a risky procedure and if done wrongly can make your system inoperable. If you require assistance we are able to offer IT support on an individual 'Per Incident' basis, or on a contract basis - which ever suits your needs at the time.

Sage running slow when using Sophos

For Sage to run at optimal performance Sage recommend excluding certain file extensions from with Sophos or your anti-virus software.

The following file types may be excluded from the file scan:

Data Files:

*.DTA
*.DTH
*.COA

Report and Layout Files:

*.SRT
*.SLY
*.SLT
*.SLB
*.RPT

Sage 50 Accounts:

*.report
*.layout
*.letter
*.label

Memo Files:

*.SLM
*.PLM
*.NLM
*.ILM
*.BLM
*.CLM
*.DLM

Criteria Files:

Note: In the case of criteria files, the * represents the Sage Accounts user name that created the file. For example, Manager.slc

*.SLC
*.SLI
*.PRC
*.PRI
*.NMC
*.NMI
*.BKC
*.BKI
*.SKC
*.SKI
*.IVC
*.IVI
*.SPC
*.SPI
*.PCC
*.PPI
*.PCI
*.REC
*.REI
*.SAC
*.SAI
*.IPC
*.IPI
*.PDC
*.PDI

Sage Reports:

Edit Logon.bat > \\servername\NETLOGON\logon.bat

Add these lines:

cd C:\Program Files\Sage\Accounts\
mkdir Reports_Temp

1. Open the Windows registry and locate the following key:

HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\SageLine50v15

2. Within this key, create a new String Value called TempPathname.

Note: TempPathname is case sensitive. Using the wrong case causes an error message when running reports in Sage Accounts.

3. Modify the String Value and in the Value data box, type in the path to the folder where you want the temporary files to be created (This is the location of the folder that is being created in the logon script)

4. You can now configure your anti-virus software to exclude the following file types specifically in this folder:

*.TMP
*.000
*.001
*.002

All reports will be placed in here and not scanned by Sophos.

Hope this works for you. If you have any issues please feel free to contact us.

Dean Spencer
Eitex IT Support

IT Support Leeds

IT Support Problems? can't logon to your network, or access email? Computer problems are very counter productive, frustrating and ultimately costly for businesses.

Our team of local engineers are able to react quickly when problems occur, and remove the burden of IT support

Our pro-active IT Support mechanisms are the key to this service. We are able to actively monitor your systems, servers and network for ongoing threats, system alerts, virus attacks and much more.!

Our support and maintenance packages include Help Desk Services, Telephone support, on-site IT support in and around Leeds, and active monitoring of your systems.

Whether you are an IT Technician, IT Advisor / Co-ordinator, or simply and IT user - we can help support & maintain your systems.

Find out what our customers are saying? click here

How to run Windows Live Messenger on Windows XP x64 and Server 2003

IT Support from Eitex.

If you have tried to install the latest version of Messenger Live on to Server 2003 or Windows XP x64 then you may have received the following error message:

Sorry, Windows Live programs cannot be installed on Windows Server, Windows XP Professional x64 Edition, or Windows operating systems earlier than Windows XP Service Pack 2.

The official download site for Windows Live Messenger states Windows 2003 Server and Windows XP x64 are not supported..

In actual fact it is the installer which is incompatible with these operating systems, not the program itself! To get round this an MSI install file has been created. This unsupported installer works fine although the responsibility of installing it is yours!

You can download the MSI file from here.

Once installed you may get the following error:

We were unable to sign you into Windows Live Messenger at this time. Please try again later

If you get this error you will need to install contacts.msi which can be downloaded from here. Again, this worked fine for me, but the responsibility is yours!

Hope this works for you.

Dean Spencer
Eitex IT Support