Renew a self-signed SSL Certificate in SBS 2003
If you have an expired SSL Certificate, you would want to renew it. This is done in the CEICW ( Configure E-mail and Internet Conection Wizard) in the SBS Console. Open Server Management -> Internet and Email -> Connect to Internet. Go through the wizard and don’t change anything until you reach this state of the wizard.
When you issue a new certificate choose Web server name to be the domain name of the company which corresponds to the MX Record. For example domain.com have an MX Record of mail.domain.com. Therefore type mail.domain.com for a Web Server name in the CEICW wizard. Once the Wizard Finishes the certificate is renewed.
Restore Missing SBS 2003 CALs
Restore Missing SBS 2003 CALs. At times the SBS License store might revert back to the initial 5 CALs, therefore users will experience disconnects from the server expressed in unable to dial a VPN, make a remote session or open shared documents. The process of dealing with this is the following :
- Confirm there is a license problems by checking the Event Viewer on the server. Events 221 and 222 from source: LicenseService should be logged stating : “License usage for product <product> is nearing the maximum number of per server licenses purchased. Consult License Manager from the Administrative Tools folder for more information.
- Go to the SBS Console and check the Licensing tab for liceneses purchased and max usage statistics
Installed Licenses: 5 Maximum Usage: 15
According to Microsoft there are 3 ways to restore the CALs:
Re-enter the CALs
Restore the Whole C:/Windows folder
Restore the Licenses if ever backed up ( here is how )
Here is the Microsoft KB Article on how to restore them :
The number of client access licenses may be reset to five in Windows Small Business Server 2003
Important ! However these solutions are mostly too critical to action. So there is another solution to the problem. SBS2003 licenses are kept in a file – Windows\system32 called lisctr.cpa. Microsoft actually keep an automatic backup of this file in another file called – autolicstr.cpa. Stop the License Logging service, rename licstr.cpa to licstr.cpa.old, copy autolicstr.cpa and rename it to licstr.cpa. Start the License Logging service and see check if the Licenses are restored.
Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporary unavailable.
Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporary unavailable. You might have this error all of a sudden when trying to connect to your SBS Server through Remote Web Workplace. It may appear sudden but it’s not at all. The issue is connected to your IIS Application pool settings. For example if you install some third-party web application, it may have
changed the 32/64 bit feature on your Application pool. So what to do :
1) Go to IIS -> Application Pools -> DefaultAppPool -> Advanced Settings -> Enable 32-Bit Application – > if it’s True , change it to False
2) Check other relevant application pools for the same setting – > SBS Web Workplace AppPool or SBS Web Applications application poool
All of the pools should run with Enable 32-Bit – False
Here is a technet forum link : http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/901d761e-773a-4dd0-a122-59d554fc63d8
The client could not connect to the remote computer by using Remote Web Workplace in Windows Small Business Server 2003
If you have ever received this error when trying to connect to a computer via RWW 2003 –
“The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection. Please try connecting again later. If the problem continues to occur, contact your administrator.”
There are two possible issues related to it.
1) You have not port forwarded port 4125 ( RWW ) on your router/firewall to the SBS Server.
2) If you have already done that and you still experience the issue, it means that something else might be listening on that same port internally on your server. As Microsoft suggests it might be the Microsoft Exchange System Attendant Service. To find out, use the the netstat command – netstat -aon | find “:4125”. This will show you what is listening on that port. If the command does not print anything, you better check if your router/firewall is really forwarding 4125 and to the right place.