Network Folder Password Protection

My wife needed this for work and I thought that this was great! I found the post on TeachME-Buzz.

1. Open Notepad and copy the code below
2. Change your password in the code it's shown the place where to type your password.
3. Save file as locker.bat
4. Now double click on locker.bat
5. I t will create folder with locker automatically for you. After creation of the locker folder, place the contents you want to lock inside the locker folder and run locker.bat again .

<---The code, copy the whole thing---->

cls
@ECHO OFF
title Folder Locker
if EXIST "Control Panel.{21EC2020-3AEA-1069-A2DD-08002B30309D}" goto UNLOCK
if NOT EXIST Locker goto MDLOCKER
:CONFIRM
echo Are you sure u want to Lock the folder(Y/N)
set/p "cho=>"
if %cho%==Y goto LOCK
if %cho%==y goto LOCK
if %cho%==n goto END
if %cho%==N goto END
echo Invalid choice.
goto CONFIRM
:LOCK
ren Locker "Control Panel.{21EC2020-3AEA-1069-A2DD-08002B30309D}"
attrib +h +s "Control Panel.{21EC2020-3AEA-1069-A2DD-08002B30309D}"
echo Folder locked
goto End
:UNLOCK
echo Enter password to Unlock folder
set/p "pass=>"
if NOT %pass%== type your password here goto FAIL
attrib -h -s "Control Panel.{21EC2020-3AEA-1069-A2DD-08002B30309D}"
ren "Control Panel.{21EC2020-3AEA-1069-A2DD-08002B30309D}" Locker
echo Folder Unlocked successfully
goto End
:FAIL
echo Invalid password
goto end
:MDLOCKER
md Locker
echo Locker created successfully
goto End
:End


Just make sure that the phrase "type your password here" is fully replaced by your password. So if your password was "chain123"the line:

if NOT %pass%== type your password here goto FAIL

would turn out to be:

if NOT %pass%== chain123 goto FAIL

Let me know how it goes!

SugarCRM Overview

Thanks to The Sugar Refinery for this post!

Key Concepts - What is SugarCRM

Customer Relationship Management (CRM) is a term given to the process of managing your relationship with your customers...better.

But what does that mean in practical terms? How does it improve your business? How does it add value and increase your bottom line?

This article will walk you through how a CRM solution, such as SugarCRM, fits within your organisation and how it benefits you, your staff, your customers and ultimately your profitability.

It covers:

• Managing Leads
• Qualifying and Converting Leads
• Managing Opportunities
• Keeping track of Activities
• Management Reporting and Forecasting
• Summary of the Benefits

Managing Leads

Consider the various ways new customers interact with your business:

These are broad categories, but your first contact with a customer, will likely be through one of these methods. Further more, the contact may be initiated by you, or simply by the customer. For example:

• Phone: You may cold-call a prospective list of customers or alternately, you may receive enquiries from customers who have simply seen your web site or an ad in the yellow pages.
• eMail: You may receive email enquiries or people may reply in repsonse to email based marketing initiatives such as newsletters.
• Web: You may receive enquiries from a web based "contact us" form. In addition, you may promote your web site through various marketing initiatives such as Google Adwords.

Your business may have additional lead sources not covered here depending on your specific marketing methods. Perhaps you have door-to-door salesmen, or run campaigns via SMS text messaging. The point is, there are many sources from which you may receive contact from potential customers.

A CRM system will first of all provide you a unified way of managing those leads. So for example, with SugarCRM, inquiries through a web based contact form can automatically create leads in your system. Similarly, the email integration allows one click lead creation once you've received an email. Cold call lists can be imported into the system and integrated with your telephony system so that staff can work systematically through a of leads.

Furthermore, by tracking the lead source of each and every lead, you can report on the success of marketing campaigns and measure the return on investment of those campaigns.

Key point: What is the difference between a lead and a customer?

A lead is someone who may, one day, become a customer but you're not yet sure if they will. For example, let's say you arrive at the office at 9am, and there is a message on the answer machine, "Hi my name is John Smith. I'm calling about your ABC product. Can you call me back on...." This lead may well become a customer. But it does need qualifying. Perhaps the caller isn't interested in buying ABC product at all. Perhaps, they're actually a supplier offering you a better price than your existing supplier. In short, until you talk to them, you can't decide.

Qualifying & Converting Leads

This is the process of deciding whether your lead is really a potential customer. It involves assigning someone to manage the lead, gathering additional information from the customer, and then deciding whether the lead is suitable to be converted into an opportunity.

Assigning the lead

Your first task may simply be to decide who deals with the enquiry. Perhaps in your organisation different people manage different types of enquiry? Or perhaps you organise work based on the customer's geographic location? Or perhaps, as with many small businesses, you simply do everything yourself. A CRM system allows flexibility. Leads may be assigned to specific individuals if required. If so, they will then pop into a queue for the relevant staff member to qualify. This process may even be automated through the implementation of defined work flow process.

SugarCRM showing leads assigned to an individual" title="My Leads SugarCRM Screenshot" border="0">

Methods of Qualification

Just as you receive enquiries through a variety of channels, so you may also qualify leads in different ways. You might, for example, reply to an email with further information. You may phone the lead up and talk to them. You might schedule a meeting to discuss in person. A CRM system allows you to manage these basic activities, schedule calls, send emails, arrange meetings etc.

During all of these activities, however, the purpose is to gather more information about the potential customer, and decide whether they really might be interested in buying something. The initial requirements are to gather:

• The customers contact details
• Determine where they heard of you (the lead source and potentially marketing campaign source)
• Determine if they have ever been a customer (IE. already have an account)
• And finally determine what product or service they are interested in buying

Once you have this information you are ready to convert your lead into an Opportunity.

SugarCRM work flow process of converting a lead to an opportunity" title="SugarCRM Lead to Opportunity process" border="0">

Typically, this will involve setting up a new Account for the customer, ensuring the contact details from the Lead are transformed into a full Contact record and recording details of the Opportunity.

Fortunately, a CRM system such as SugarCRM makes this process very simple - it's a one-click process.

So what sort of information makes up an Opportunity? Generally, this will be information about the potential sale. So, it may include the potential size of any deal, the probability of winning the deal, an estimated close date, and the stage the Opportunity is at. Such stages may include:

• Qualifying and analysing
• Proposal
• Negotiation and Review
• Closed Won
• Closed Lost

Managing Opportunities

A flexible system such as SugarCRM will allow assignment of the opportunity to various members of your team at various stages of the process. This allows for effective management, ownership and tracking of each and every opportunity within your organisation.

SugarCRM showing an individuals Top Ten Opportunities" title="Top Ten Opportunities SugarCRM screen shot" border="0">

Furthermore, as the Opportunities contain potential financial information, along with sales status and expected close dates, it's possible to report on this information in a very useful way (more on that later).

SugarCRM of a dashlet sales pipeline" title="Sales Pipeline" border="0">

Managing Activities

The above sections have covered the basics of making and tracking a sale. But there is often a lot of activity that goes on around this process. Here are just some of those activities:

Depending upon the individual characteristics of your business, there may be a good deal of correspondence between you and your customer - either by email or phone. You may produce quotes, send fact sheets and receive purchase orders and produce invoices. You might regularly meet with your client, either alone or with other members of your organisation. An intense negotiation stage may take place. You may need to collaborate with other members of your organisation and chase them up on where they are on tasks you've assigned them.

Wouldn't it be great to have a system that helped track, organise and manage all of that in one place? That's exactly what a CRM system does. It allows you to not only manage all of your activities but also to relate those to particular Accounts or Opportunities. This makes finding information a breeze. Want to know when the quote for a client is due? It's in your diary. Want to know what fact sheets your colleague has already sent them? It's recorded against the customer. Want to review all the emails that have been sent to your client? It's all there.

A CRM system turns your office into a well oiled machine. It makes your work more efficient and gives you a complete view of your history with the customer.

It allows you to manage that relationship better, and allows you to profile customers for future marketing.

Management Reporting and Forecasting

One of the great advantages of having a centralised repository holding so much information about your customers and your sales is the ability to produce useful and effective reports. Here are a few examples of the types of information that can easily be extracted:

• Sales information - broken down by sales staff, or month, or sales status, or marketing campaign
• Return on Investment for marketing strategies
• Customer extracts - for example, all customers with opportunities in a particular status
• Workloads - who is dealing with the bulk of your work
• Project management - what stage is your project at? What tasks are complete or overdue?

A CRM system such as SugarCRM can provide many different types of report. Information can be presented in either text form (such as customer lists) or in graphical form. Alternately, information can be filtered, sorted, and then exported to popular products such as Microsoft Word or Excel.

In summary, a CRM system places management information at your fingertips, equipping you to take informed decisions for your business.

SugarCRM showing Sales Outcome by Month" title="SugarCRM Sales Outcome by Month screen shot" border="0">

Summary of the Benefits

CRM is about managing your relationship with the customer...better.

A CRM system, such as SugarCRM, archives this by:

• Effectively managing your sales process, ensuring every lead counts, from every potential source
• Organising and distributing the workload around your organisation
• Managing and tracking every activity
• Providing a holistic view of each and every customer
• Effective management reporting and forecasting

The result is that you server your customers better, that you understand your customers better and that you can react faster to customer demands.

Installing SugarCRM Upgrade

This is a GREAT step-by-step explanation to this process. Thanks SugarCRM!

Upgrading Sugar

This document describes how to upgrade from Sugar versions 5.0 and 5.1 to version 5.2.

In order to upgrade your Sugar application, you need to download the appropriate Upgrade zip file from the Sugar Website to your local machine. For Sugar Enterprise and Sugar Professional, you can obtain the Upgrade zip file from the Sugar Support Portal at https://www.sugarcrm.com/crm/support and upload it to your local machine. For Sugar Community Edition, you can upload the Upgrade zip file from the SugarCRM Web site to your local machine.

To use the Upgrade Wizard, you need to log into the Sugar application. To use the Silent Upgrader, you need to run a PHP script from the command line on the server where the Sugar instance is installed.

CAUTION:

It is strongly recommended that you run the upgrade process on a copy of your production system.

If you are using Zend Core 2.0, you will need to increase the default value of the parameters listed below before you begin the upgrade process:

a.	Navigate to C:\Program Files\Zend\Core\etc\fastcgi.conf and increase the default value for ConnectionTimeout to 3000 and RequestTimeout to 6000.

b.	Navigate to the php.ini file and increase the default value of max_execution_time to 6000.

Compatibility Matrix for Upgrade

PHP versions	5.1 and higher
Databases	MySQL, MSSQL, and Oracle (Oracle is supported only for Sugar Enterprise)
Operating systems	Windows, Linux

Important Upgrade Information

•	Backup your system before beginning the upgrade process. It is imperative to backup your current Sugar directory and database.

•	Because the upgrade files are large, do the following:

a.	In the Advanced section of the System Settings page of your current Sugar installation, modify and save the value of Maximum upload size to 21000000 (20MB).

b.	Navigate to the php.ini file on your Web Server and configure the parameters listed below as follows:

•	Set post_max_size to more than 20MB.

•	Set upload_max_filesize settings to more than 20MB.

•	Set max_input_time to a large number.

Restart the Web Server and then begin the upgrade process.

•	If you are using an Apache Web Server and if you have set LimitRequestBody in the httpd.conf file, then ensure that you set it to a large number or use the default value of 2GB. Restart Apache and then begin the upgrade process.

•

Ensure that the Webserver user has Write permissions to the Sugar database. The upgrade to Sugar 5.2 will add and replace files in several locations including the sugar root directory. The Webserver user must have Write permissions for the root folder and all sub-directories during the upgrade process.

•	The process of upgrading can take up to 30 minutes. If you are using the IIS Web server, you need to ensure that the CGI application does not time out. To do this, on IIS, set the CGI script timeout to more than 300 seconds, which is the default value.

•	If you have customized any module’s PHP file, for example, accounts.php, we strongly recommend that you save it in the Customs directory and not within the main module. This is because, during upgrade, any customizations that you have made may be overridden by changes that Sugar has made for 5.2.

•	Some entry points were changed in Sugar 5.1. Hence, unless you manually updated custom files that were created in 5.0 with the new entry points in 5.1, they may fail in 5.2 with the error message “Not a valid entry point”.

For example, if you have customized vCard, navigate to custom\modules\\metadata\detailviewdefs.php and replace <name="vcard" action="vCard.php>"

with the following:

<name="vcard" action="index.php">

Using the Upgrade Wizard

The Upgrade Wizard provides a quick way to upgrade to the latest version of the Sugar application. The Upgrade Wizard includes critical upgrade logic as well as the SQL commands needed to upgrade the application.

Before using the Upgrade Wizard, ensure that the config.php file for your installation is writable.

Note:

Attempting to manually upgrade by simply replacing files and running the upgrade SQL is not supported.

To upgrade Sugar using the Upgrade Wizard

1.	Download the appropriate Sugar Upgrade zip file from the Sugar Website to your local machine. For example, to upgrade Sugar Professional from version 5.0 to 5.2, you need to download the SugarPro-Upgrade-5.0.0-to-5.2.0.zip.

2.	Log into your existing Sugar application as the administrator and click admin on the right-hand corner of the page.

3.	In the Systems panel of the Administration Home page, click Upgrade Wizard.

The Upgrade Wizard screen displays on the page.

4.	Click Next.

The System Checks screen displays on the page.

5.	Click Next.

The Upload an Upgrade screen displays on the page.

6.	Click Browse, navigate to the location of the Upgrade zip file, and select it.

The path to the file displays in the Upload an upgrade field.

7.	Click Upload Upgrade to upload the package to the Sugar application.

The system uploads the package and displays it on the page.

Click Next.

The Preflight Check screen displays on the page.

By default, the Upgrade Wizard Runs SQL option is selected as the database update method. If you ran the SQL queries manually, select Manual SQL Queries from the Database Update Method drop-down list and select the Check when SQL has been manually run box.

8.	Click Next.

The Commit Upgrade screen displays on the page.

Optionally, you can click Show to see a list of files that were copied and the rebuild results.

9.	Click Next.

The Debrief screen confirms that the upgrade has been installed.

10.	Click Done.

The upgrade is now complete.

11.	In the Systems panel of the Administration Home page, click Repair and select the Rebuild Relationship and Rebuild Extensions options to perform these actions. For more information, see the Installation and Administration Guide that is appropriate to your Sugar application.

12.	If you unchecked any files to prevent the Upgrade Wizard from overwriting then manually merge the files by extracting the skipped file from the patch zip file. Merge the file that was installed in the Sugar application directory.

Note:

If your attempt to upgrade Sugar is unsuccessful, check the upgradeWizard.log file in the Sugar folder for information.

Using the Sugar Silent Upgrader

The Silent Upgrader enables you to avoid some of the limitations that the Web application environment may have that prevents the Upgrade Wizard from completing the upgrade. The upload size limit (by PHP and sometimes even by Web server), the CGI (or equivalent) timeout limit, and the MySQL (or equivalent) session timeout limit are some of the challenges people run into when upgrading to Sugar 5.2. The Silent Upgrader either avoids the limitations or better controls the settings in its stand-alone execution environment.

Note:

The silentUpgrade.php script creates new files for the user who is running it. For example, for the root user it create files as user/group root. Because Apache cannot read this, you must ensure that the Web server user has the permissions to read and write the script.

To upgrade Sugar using the Silent Upgrader

1.	From the command line on the server where the Sugar instance is installed, execute the silentupgrade.php script as follows:

php.exe -f silentUpgrade.php [upgradeZipFile] [logFile] [pathToSugarInstance] [adminUser]

where:

upgradeZipFile is the full path to the upgrade zip file. For example, SugarCE-Upgrade-5.1.0-to-5.2.0.zip

logFile is the full path to an alternate log file.

pathToSugarInstance is the full path to the instance being upgraded.

adminUser is a valid admin user name.

Note:

After upgrading to Sugar 5.2.0, you will need to rebuild the relationship metadata. To do this, log into Sugar as the administrator. On the Administration Home page, select the Repair option in the Systems sub-panel and click Rebuild Relationships.

Locking Down the Upgrade Wizard

If you are managing multiple instances of the Sugar application and you want to maintain complete control over the Sugar instances, you can lock down the Upgrade Wizard to ensure that no user with administrative privileges can upgrade any of them. To lock down functions on the Administration page

1.	Navigate to the config.php file in the Sugar root directory.

2.	Set the following parameter to true as below:

$sugar_config['admin_access_control']=true

3.	Save the file.