jump to navigation

Where are my CALS? June 13, 2009

Posted by Gomez in IT, Microsoft, Network Services.
Tags: , , ,
1 comment so far

For all my fellow Small Business Server users, this week I was greeted with an issue with one of my client’s informing me that they are not able to access the mapped network drives “Connection to resource has exceeded maximum connections” After extensive searching in Event Viewer > System logs, I came across the following entry;

Event Type:        Error
Event Source:    SBCore
Event Category:     None
Event ID:              1023
Date:                     6/11/2009
Time:                     7:08:27 PM
User:                     N/A
Computer:          XXXXXX
The license store for the client access licenses is not valid. Only the minimum number of client access licenses will be available until a valid license store is restored. For more information, see Help in the Licensing snap-in.

 Open Server Management > Licenses, found that  installed CALs (50 Client access licenses) disappeared leaving only the default “5”. 

There are three main methods for restoring the License Store.

Method 1: If you had previously exported the license store after entering the CALS and activating them, you can simply restore that file.

Method 2: If you have the actual CAL codes you can re-enter and activate the CALS.

Method 3: If you have a backup of your system drive you can locate the file licstr.cpa which is located in %systemroot%/system32  folder. Simply replace this file on your affected system with the previously backed up licstr.cpa.  (This method was the one that worked in my situation)

Now after you have restored the licstr.cpa file in its original location, be sure to restart the license logging service.

Word of caution for those who have not experience this issue, take a backup of your license store!


HTTP/1.1 503 Service Unavailable April 9, 2009

Posted by Gomez in E-Mail, IT, Microsoft, Network Services.
Tags: , , ,

After typing http://Server-name/exchange
You get the login box, after entering the correct user info you get the dreaded
HTTP/1.1 503 Service Unavailable, after searching the web for months and tried almost all available tutorials I finally found the solution. This problem (the scenario I experienced) it relates to permissions in the windows registry. Follow the steps below to get OWA working as normal.

1. Open regedit from the command prompt, ensure you take a backup of your current registry configuration. To export, on the file menu in registry editor click export  and choose save destination

2. Locate and Right Click HKEY_CLASSES_ROOT hive and select Permissions

3. Click the Advanced button on the Permissions dialog box

4. Highlight CREATOR OWNER – make sure this is the user selected

5. Tick the box for Replace permission entries on all child objects

6. Click OK twice

7. Its best to restart the server, but if you are anxious just restart all exchange services

8. Finally Test 


Microsoft 2003 DHCP and DNS (Active Directory Integrated) LEASE ISSUE April 1, 2008

Posted by daakeung in IT, Microsoft, Network Services.
Tags: , , ,
1 comment so far

Currently I am running DNS integrated zones with secure updates, and DHCP. Problem is that DHCP has been giving out ip addresses before ttl for the ahost record expired. Which caused workstations trying to fail dns registration, since the workstation that used the ip previously had it’s computer account tied into the AHOST and PTR.

Now matching lease time and dns expiration would fix this problem, but I have clients outside of the enterprise coming and going.

So instead of the clients registering their own records, I configured the DHCP server to register the client record and remove them when lease expires. This helps non domain computers to register and to prevent DNS pollution.

You need to enable option 81, which requests the client to send it’s FQDN (Fully qualified domain name)

You do this by opening the properties for the server or scope in DHCP MMC. Then enable the following, it’s self explanator.

DHCP, Applying DNS settings

Now when doing that, all dns records created by the dhcp server, by default will have the dhcp server computer account tied to them. So in the event of a DHCP failure, the backup DHCP server would not be able to modify the DNS records that the primary DHCP server had created. So create a user for DHCP in active directory, and set on the DHCP server the credentials, this way you can have multiple DHCP servers sharing the same account.