RED HERRING AWARDS IYOGI FOR THE 2008 RED HERRING ASIA AMERICA 100

Monday, December 15, 2008

Award Recognizes the 100 “Most Promising” Asian Companies Driving the Future of Technology

Silicon Valley, CA, Dec 9th, 2008— Red Herring today announced that iYogi is a winner of the Red Herring 100 Award, a selection of the 100 most innovative private technology companies based in Asia.

IYogi delivers technical support services directly to consumers and small businesses and is the first, global, technical support brand based out of India with more than 50,000 customers. The company offers consumers an unlimited, annual subscription service for $119.99 per desktop that includes support for a wide range of technologies, including PC hardware, Microsoft Products Support, Windows Operating systems, Computer Support, Software applications, MP3 players, Networking devices, Digital camera, Printers and scanners etc.

The Red Herring editorial board diligently surveyed the entrepreneurial scene throughout Asia and identified the top 100 out of more than 1,000 closely evaluated companies that are leading the next wave of innovation.

“Our winners and Finalists demonstrate that Asia is increasingly becoming a leader in innovation, contrary to common stereotypes", said Joel Dreyfuss, editor-in-chief of Red Herring. " It was tough to choose just the top 100 finalists from such a large list of excellent contenders, and we are very happy with the quality of the companies we selected as finalists."

“We believe consumers and small business owners should have low-cost access to the highest quality support available on the planet", said Uday Challu, CEO of iYogi. “We are thrilled that our innovative approach to solving everyday technology problems for consumers and our managed services for small businesses has been recognized by Red Herring’s keen-eyed leadership. We are continuously innovating in adding new services that includes PC recovery, anti-virus, anti-spyware, data back-up and PC optimization in providing the best tech support experience for our customers”, adds Uday.

The 100 winning companies have been announced at the Red Herring Asia event in Hong Kong. The CEOs of the winning start ups presented their innovative ideas and technologies to an audience of leading entrepreneurs, financiers, and corporate strategists at the event at the Hong Kong, JW Marriott Hotel earlier this week.

About iYogi

iYogi is the first direct-to-consumer and small business technical support service from India. Providing an annual unlimited subscription to technical support, iYogi now boasts of more than 50,000 customers. The company employs 600 professionals servicing customers in the US, UK, Canada, Australia and fast expanding to 12 new geographies across the globe. iYogi’s resolution rate of 87 percent and customer satisfaction rate of 93 percent are amongst the highest published benchmarks in the industry. For further information, please visit www.iyogi.net.

iYogi Contact

Vishal Dhar
President Marketing, iYogi Inc.
Phone: 212 229 0901
Email: vishal@iyogi.net

Problem exporting multi-line contact street addresses in Outlook

Monday, November 17, 2008

When you export Microsoft Outlook Contacts in either a comma or tab separated values format, any street addresses that contain more than one line are exported with carriage returns separating the multiple lines. This may result in a skewed output file containing multiple records for those contacts containing multi-line street addresses. In a comma or tab delimited file, carriage returns are interpreted as record delimiters. For troubleshoot this problems get Outlook support and follow the below given steps:

You can trouubleshoot using two method

Use CSV Format
Export the file in comma separated values (CSV) format; then open the file in Microsoft Excel. The file will import correctly with one record per contact and the multi-line street address in one cell. You may need to change the row height in order to see the second line of the address.

Manipulate the file in Microsoft Word
Export the file in either a comma separated values or tab separated values format, and then open the output file in Word. Then, manipulate the data as follows:
1. On the Edit menu, click Replace. If the Special button does not appear, click More to expand the dialog box.
2. In the Find What box, type a double quotation mark ("). Then click Special and click Paragraph Mark.
3. In the Replace With box, type any special character not found in your data, such as a pound sign (#).
4. Click Replace All.
5. In the Find What box, click Special and click Paragraph Mark.
6. In the Replace With box, type whatever character you would like to use to separate the multiple street address lines, such as a percent sign (%).
7. Click Replace All.
8. In the Find What box, type the special character used in step 3.
9. In the Replace With box, click Special and click Paragraph Mark.
10. Click Replace All.
After completing this procedure, your file will have one record for each contact. The multi-line street address will be in one field, surrounded by quotation marks. Each street address line will be separated with the character chosen in step 6.

Rule For Forwarding To Internet Address Does Not Work

Monday, November 10, 2008

The Inbox Assistant or Rules Wizard rule for forwarding messages to Internet addresses does not work after upgrading to Microsoft Exchange Server 5.5. The Exchange Server 5.5 "Automatic Replies to the Internet" option may be disabled by default in the Internet Mail Service.
Tips for Solution:

Enable the "Automatic Replies to the Internet" option by performing the following steps:

1. Open the Internet Mail Service object in the Exchange Administrator program.
2. Go to Internet Mail tab.
3. Click the Advanced options button.
4. Clear the checkbox for "Disable Automatic Replies to the Internet."
5. Stop and restart the Internet Mail Service in Control Panel Services.

his Steps Succsess to troubleshoot this problems, so i think it provides best outlook Support for troubleshooting Outlook Problems.

How to Verify That the Client Can Contact Backend Ports

Wednesday, November 5, 2008

By default, the RPC Proxy server does not publish the EPM port location. Therefore, you cannot ping the EPM from outside your intranet or use the UUID of the service.

However, you can specify the backend port that you want to test. By default, the store is on port 6001 and DsProxy is on port 6004. If these locations have been changed, the ports can be verified by using the RpcDump utility. The RpcDump utility is available from the Microsoft Windows Server 2003 Resource Kit package. Additionally, Microsoft does not recommend publishing the global catalog Directory Service or the Exchange referral service.

The following RPC Ping Utility examples are typed in at the command prompt. To access the command prompt, click Start, point to All Programs, point to Accessories, and then click Command Prompt.
How to Use Basic Authentication and SSL to Connect to the Store’s Port
Syntax:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 1 –F 3 –a connect –u 10 –v 3 –e 6001
How to Use Basic Authentication, SSL, and Mutual Authentication to Connect to the Store’s Port
Syntax:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 1 –F 3 –a connect –u 10 –v 3 –e 6001 –B msstd:server_certificate_subject
How to use NTLM Authentication and Non-SSL to Connect to DsProxy Service
Syntax :
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 2 –F 2 –a connect –u 10 –v 3 –e 6004

Duplicate junk e-mail messages appear in the Junk E-mail folder in Outlook 2003

Monday, November 3, 2008

This problem occurs because Outlook 2003 has the junk e-mail protection level set to Safe Lists Only.

When you create a junk e-mail rule in Outlook 2003 with the junk e-mail protection level set to Safe Lists Only, the restriction structure (SRestriction) causes an Exchange Server that is running without junk e-mail filtering to decide if an e-mail message is junk e-mail or if it is not junk e-mail. Outlook 2003 then processes all the junk e-mail messages on the client side. If there is more than one instance of Outlook 2003 running, multiple copies of the same junk e-mail message can be moved from the Inbox to the Junk Mail folder while duplicates of the junk e-mail messages are created in the Junk E-mail folder.


You receive duplicate e-mail messages in your Junk E-mail folder in Microsoft Office Outlook 2003 when all the following conditions are true:
• You have more than one instance of Outlook 2003 running on different computers, and all the instances are configured with the same Microsoft Exchange Server e-mail account.
• The junk e-mail protection level for your e-mail account is set to Safe Lists Only in Outlook 2003.
• Your Exchange Server does not filter incoming e-mail messages.
• All instances of Outlook 2003 use an Exchange Server e-mail account in Cached Exchange Mode.
• The sender of the e-mail message is not in your Safe Senders list in Outlook 2003.
• The sender of the e-mail message is not in your Contacts in Outlook 2003.
• The sender of the e-mail message is not in your Blocked Senders list in Outlook 2003.
• None of the recipients of the e-mail message are in your Trusted Recipients list in Outlook 2003.


RESOLUTION

This problem was first fixed in a hotfix that is now contained in a service pack. If you installed the latest Microsoft Office 2003 service pack, you do not have to install the hotfix.

You cannot connect over the Internet to Exchange Server 2003 from Outlook 2007 or from Outlook 2003

Thursday, October 23, 2008

SYMPTOMS
When you try to use Microsoft Office Outlook 2007 or Microsoft Office Outlook 2003 to connect over the Internet to your mailbox on a Microsoft Exchange Server 2003 based-computer, you are prompted for your logon credentials many times, and you do not connect to Exchange Server 2003.

CAUSE
This behavior occurs if an outbound proxy authentication is required, and if you use Remote Procedure Call (RPC) over HTTP to connect to an Exchange Server 2003 account. When Outlook is using RPC over HTTP, the default timeout is 45 seconds. If RPC over HTTP takes longer than 45 seconds to connect, the connection is not successful.

RESOLUTION
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows


To resolve this behavior, you can add the ConnectTimeout, the ConnectTimeoutLow, and the RFRTimeoutDWORD values to the RPC registry key. To do this, follow these steps.

Note All the "connect timeout" registry values that are mentioned in the following steps are expressed in milliseconds (ms).
1. Click Start, and then click Run.
2. In the Open box, type Regedit, and then click OK.
3. Expand the following registry key:

Outlook 2003
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\RPC
Outlook 2007
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\RPC
4. Right-click RPC, point to New, and then click DWORD Value.
5. Type ConnectTimeout, and then press ENTER to name the new value.
6. Double-click ConnectTimeout.
7. In the Value data box, type 000493e0, and the click OK.
8. Right-click RPC, point to New, and then click DWORD Value.
9. Type ConnectTimeoutLow, and then press ENTER to name the new value.
10. Double-click ConnectTimeoutLow.
11. In the Value data box, type 000493e0, and the click OK.
12. Right-click RPC, point to New, and then click DWORD Value.
13. Type RFRTimeout, and then press ENTER to name the new value.
14. Double-click RFRTimeout.
15. In the Value data box, type 000493e0, and the click OK.
16. Exit Registry Editor.


MORE INFORMATION
When Outlook tries to connect to each server type, Outlook uses the registry values that you added in the Resolution section to determine how long to wait before the connection is considered a failed connection (a time-out connection) and the connection is dropped.
• Outlook uses the ConnectTimeout registry value when it detects connections that use a network adaptor that is functioning at greater than 128 kbps.
• Outlook uses the ConnectTimeoutLow registry value when it detects connections that use a network adaptor that is functioning at less than 128 kbps.
• Outlook uses the RFRTimeout registry value for a server referral. For example, Outlook uses this value when it asks the Exchange store for a referral to the global catalog server, to another user’s mailbox, or to a public folder. Outlook uses this registry value for all network adaptor speeds that are detected.
Outlook uses these registry values to determine how long to wait for a connection to succeed before Outlook times out and the connection fails.


APPLIES TO
• Microsoft Office Outlook 2003, when used with:
-------Microsoft Exchange Server 2003 Enterprise Edition
-------Microsoft Exchange Server 2003 Standard Edition
• Microsoft Office Outlook 2007

The body of the e-mail message appears empty when you open an encrypted or a digitally signed e-mail message in Outlook 2003

Wednesday, October 15, 2008

SYMPTOMS
If you open an encrypted or a digitally signed e-mail message in Microsoft Office Outlook 2003, the body of the e-mail message appears to be empty. This problem occurs when you use Outlook 2003 in Cached Exchange Mode. If you use Outlook 2003 in online mode, the content in the body of the e-mail message appears as expected.

CAUSE
This problem may occur if both of the following conditions are true:
• You use the CryptoEx Outlook security add-in program. This third-party software is made by the Glück & Kanja Group. It is used to encrypt or to digitally sign e-mail messages.
• Outlook 2003 is configured to use Cached Exchange Mode.
When the CryptoEx Outlook security add-in program tries to replace the original encrypted or signed e-mail message body with the decrypted content, the call is unsuccessful, and the e-mail message body appears to be empty.

RESOLUTION
This problem was first fixed in a hotfix that is now contained in a service pack. If you installed the latest Microsoft Office 2003 service pack, you do not have to install the hotfix.

Service pack information
This problem is corrected in Microsoft Office 2003 Service Pack 1.

To resolve this problem, obtain the latest service pack for Microsoft Office 2003. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
870924 How to obtain the latest service pack for Office 2003

How to obtain the hotfix
This issue is fixed in the Outlook 2003 Hotfix Package that is dated December 17, 2003. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
830003 Outlook 2003 hotfix package: December 17, 2003

WORKAROUND
To work around this problem, do not use Outlook 2003 in Cached Exchange Mode when you use Outlook 2003 with Microsoft Exchange 2000 Server or with Microsoft Exchange Server 2003. To turn off the Cached Exchange Mode feature, follow these steps:
1. Start Outlook 2003.
2. On the Tools menu, click E-mail Accounts.
3. Click View or change existing e-mail accounts, and then click Next.
4. Under the Name column, click the account that you want to modify, and then click Change.
5. Click to clear the Use Cached Exchange Mode check box.
6. Click Next, click OK, and then click Finish.
7. Quit and then restart Outlook 2003.

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Office 2003 Service Pack 1.

MORE INFORMATION

For additional information about the standard terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.