Quota warning

 

Users don’t receive Mailbox Quota Warnings in Microsoft Exchange 2010 SP1/SP2 – Quota Warnings Aren’t Generated

This is a design update that Microsoft made in Exchange 2010 Service Pack 1. Prior to Service Pack 1, quota warning messages were generated automatically whenever the mail users hit the quota warning threshold. After Service Pack 1 that won’t be generated unless you:

EITHER

Set the “prohibit send” quota value. You can go to Microsoft site or do a Google search to find out more about how that works.

OR

Add a new Flag/Registry key:

Resolutions:

We are going to add the necessary flag.

Add the following registry key and restart the Information Store. Quota notification emails will start working, and people will start getting them once a day if they have exceeded the quota value.

Run Regedit, and go to the following:

HKEY_LOCAL_MACHINE\System\CCS\Services\MsExchangeIS\ParametersSystem

Create a New DWORD Value.

Type CheckWarningQuota , and then press Enter.

Right-click CheckWarningQuota, and then click Modify.

In the Value data box, type 1, and then click OK.

Exit the Registry and restart the Information Store.

If you find this article helpful, please send us a note to Mike@bostonIT.com so we can keep on adding more hands-on Knowledgebase articles.

Disable Open File warning

How to Disable Open File Security Warning in Windows 7 When Openning Files on the Local or Network Drives:

 

Click Start –> Search or Run,

Type
gpedit.msc and hit enter

In the left pane, click on to expand User Configuration, Administrative Templates, Windows Components, and Attachment Manager.

In the right pane, double click on Inclusion list for low file types.

Enable it and type the kind/extension of file that you would like to disable the security warning for (if it is an EXE file, then type .exe). If you have multiple files (like bat, dba and xls, then seperate them with semicolon (;)
This is how that would look like:
.bat;.dba;.xls

If you find this article helpful, please send us a note to Mike@bostonIT.com so I can keep on adding quality hands-on articles.

Remote Web Access is not allowed

Remote Web Access is not allowed for your user account. Contact the person who manages your server.

Scenario:

We were hired by a customer to help troubleshoot an issue with Remote Web Access (RWA) after they had already migrated to Windows SBS 2011 Essential from Windows Server 2003 SBS. When people go to the RWA URL site, type username and password and hit login they get:

“Remote Web Access is not allowed for your user account. Contact the person who manages your server.”

They were unable to login not even as domain administrators.

The following error was logged in “C:\ProgramData\Microsoft\Windows Server\Logs\Dashboard”

[38300] 130221.160506.6590: IDENTITY: Add Group:RemoteAccess failed with ErrorCode:8ac

The following error was logged in “C:\ProgramData\Microsoft\Windows Server\Logs\WebApps\RemoteAccess.log”

[33088] 130220.211827.8285: RemoteAccess: [Identity] User validate passed but not permitted to enter.

Resolution:

It turned out that when the Windows server 2011 SBS Essential was migrated to from Windows Server 2003, a few steps were skipped in the process of migration! Here are the steps that are pertinent to the issue and that have fixed it for me.

1- Go to “Active Directory Users and Computers” and look for the security groups mentioned below, if you don’t find them then you must create them manually. To create those groups in Active Directory Users and Computers,, expand My Business, expand Users, and then expand SBSUsers. Right-click and click Create New Group. Create the group names below, click Security Group and for the scope for each group to Global, and then click Create. Repeat this step to create the remainder of the below security groups. (in short you need to create new security groups in Active Directory Users and Groups that didn’t migrated over – listed below – it could be anywhere in ADUC – nothing is special about that…). The groups are:

  • RA_AllowAddInAccess
  • RA_AllowComputerAccess
  • RA_AllowDashboardAccess
  • RA_AllowHomePageLinks
  • RA_AllowNetworkAlertAccess
  • RA_AllowRemoteAccess
  • RA_AllowShareAccess
  • WSSUsers

2- In “Active Directory Users and Computers” you also must add the “Authenticated Users” group to the “Pre-Windows 2000 Compatible Access” group.

In the navigation pane of Active Directory Users and Computers expand “YourDomainName”, and then click the Builtin folder. In the details pane, right-click the Pre-Windows 2000 Compatible Access group, and then click Properties. On the Members tab, click Add. Type Authenticated Users, and then click OK.

3- Now, because some accounts were migrated from the Windows 2003 Server, by default it does not have memberships to those Windows SBS 2011 Essentials security groups. To add group memberships to the accounts that you are using for migration, do the following:

Click Start, click Administrative Tools, and then click Active Directory Users and Computers. In the navigation pane, expand YourDomainName, expand My Business, expand Users, and then expand SBSUsers. Open the administrator account or accounts to which you want to assign membership. Click the tab Member of and add all the “RA_…..” security groups above.

4- When creating new users account, use the Windows Small Business Server 2011 Dashboard instead of Active Directory Users and Computers.

5- If there is a user in Active Directory that you don’t see in the Dashboard, use the following steps to add it to the Dashboard:

Go to command line

cd “c:\Program Files\Windows Server\Bin”
Type WssPowerShell.exe
Type Import-WssUser -Name 

If you find this article helpful, please send me a note to Mike@bostonIT.com so I can keep on adding more hands-on knowledgebase articles.

Enable ZIP Extension for PHP

How to Enable ZIP Extension for PHP on Linux – Ubuntu – ZIP.SO – PHP.INI – Efront – XAMPP/LAMPP

Download XAMMP from:
http://www.apachefriends.org/en/xampp-linux.html

That contains Apache 2.4.3, MySQL 5.5.27, and PHP 5.4.7.

Follow instructions on the site (All it takes is just download and unzip into /opt/lampp. It’s pre-compiled).

For Apache, you might want to update the root directory of the http server to “/opt/lampp” (edit /opt/lampp/etc/httpd.conf and make sure the following path in the file is correct ServerRoot “/opt/lampp”).

Enable zip extension for php with apache by:

1- Un-commenting zip.so in /opt/lampp/etc/php.ini. (The latest version of XAMPP, as of this article, is compiled with zip support for PHP but you need to follow the few steps mentioned here to enable it and make it work).

2- Un-commenting and updating the path of the extension_dir in php.ini (extension_dir = “/opt/lampp/lib/php/extensions/no-debug-non-zts-20100525”)

3- Downloading zip.so into the Extension Dir.

You can download the modified php.ini, httpd.conf and the zip.so described above here:

Download php.ini
Download zip.so 
Download http.conf file

Clear browser cache.

Stop and start XAMPP
/opt/lampp/lampp stop
/opt/lampp/lampp start

Now you can download efront and unzip into /opt/lampp/efront..

If you find this section helpful, please send us a note to Mike@bostonIT.com so I can keep on adding quality hands-on articles.