Continue reading »]]> I came across this issue today and found this solution. 

Got this error when logging into a machine that I hadn’t touched in months:

"the security database on the server does not have a computer account for this workstation trust relationship"

Not exactly sure why, but changing from a FQDN to a short name resolved the issue.

1. Login on to your computer with an account that has Administrator privileges.
2. Change domain from FQDN (in my case Redmond.corp.microsoft.com) to the short name (in my case Redmond)
3. Logout and log back in as the domain user.

Link to original post.

Continue reading »]]>  

I’ve spent a little time looking at Microsoft Forefront as Microsoft Security Essentials is so good I wanted to know what the “professional” tools brought…

The management software has very odd requirements:-

• Needs to be Windows Server 2008 R2
• Not a Domain Controller
• Configuration Manager 2007

Which is great for enterprise but doesn’t fit Microsoft Small Business Product in anyway, where’s forefront for SBS?

Here’s a screen grab from Microsoft Security Essentials.

Here’s a screen grab from Forefront Client.

Spot the difference, the name.  This is great because the free MSE client is so good it means forefront is just as good.   They downside is requirements for management are to high for small businesses, which is a shame because this could be a killer product.

Continue reading »]]> A clients Terminal Server/Remote Desktop Server failed.   We installed Windows Server 2008 R2 and configured it as a Remote Desktop Server.  But it didn’t appear in the RWW as a 2003 Terminal server would have normally.  As the image below demonstrates.

Thanks to Philip Elder, http://blog.mpecsinc.ca/2008/08/terminal-server-not-showing-up-in.html for the following fix.  Which I have posted here for connivance.

“This one is via the SBSC SBS Newsgroup: After setting up a new Terminal Server on the SBS2K3 network, the “Connect to my Application Server” link is not appearing in RWW.
Remotely edit the SBS and Terminal Server’s registry and look for the keys:

• On SBS:
  • HKLM\Software\Microsoft\SmallBusinessServer\RemoteUserProtal\
    KWLinks\AppTS=1 (wrapped on purpose)
• On the TS:
  • HKLM\System\CurrentControlSet\Control\Terminal Server\TSEnabled = 1
  • HKLM\System\CurrentControlSet\Control\Terminal Server\TSAppCompat = 1

If one or both of the keys are not present, create them with the values indicated. If the value for the key is anything but “1″, then edit the key to change that value.
We need to make sure that the Remote Registry service on the TS box is running, and that the firewall has the appropriate ports open to serve TS or the firewall is off altogether.”

This worked a treat for us.

Continue reading »]]>  

This has happened to me on a number of SBS boxes whit low hard drive space, generally on drive C:

SBS resets the cal count to 5!

We have just had a customer call and this has happened to.  Normally we backup the CALS using the built in backup utility within SBS Console.

Found this MS KB 888818, which isn’t really much help.

Te SBS2003 licenses are kept in the licstr.cpa file in the WINDOWS\system32 folder.

• Microsoft keep an automatic backup of this in autolicstr.cpa.  
• Stop the License Logging Service.
• Rename licstr.cpa to licstr.cpa.old.
• Copy autolicstr.cpa to licstr.cpa. 
• Start License Logging Service
• Open Server Management to confirm that the licenses had been restored.

Then found post on Knight-Time Ramblings which worked!

Continue reading »]]> It would be cool when you logged into RWW and clicked on the Connect to my computer at work that as well as showing you the computer name it displayed the computer description, also weather a user was logged in, if the PC was powered down this was displayed via a icon, which could be clicked on to start the PC up via a Wake-on-LAN command.

 Typing this has got me thinking if I could amend the page myself…….