Continue reading »]]> For Windows 7

Open an Windows Command Prompt and enter the following to disable: - 

sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled

To enabled, enter the following: -

sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc config mrxsmb20 start= auto

For Windows Server 2008

Run "regedit" on Windows Server 2008 based computer.

Expand and locate the sub tree as follows.

HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters

Add a new REG_DWORD key with the name of "Smb2" (without quotation mark)

Value name: Smb2
Value type: REG_DWORD
0 = disabled
1 = enabled

Set the value to 0 to disable SMB 2.0, or set it to 1 to re-enable SMB 2.0.

Reboot the server.

Continue reading »]]> There’s a few places to change this and that’s global settings as well as the connectors.

To adjust your transport send/receive limits.

Global Settings
Organization Configuration->Hub Transport->Global Settings->Properties of Transport Settings

Then you must modify the connectors found here:

Send Connector
Organization Configuration->Hub Transport->Send Connectors->Properties of Default Send
Here you can adjust your send connectors default maximum message size

Receive Connector
Server Configuration->Hub Transport->Receive Connectors Pane->Properties of Default

Continue reading »]]> This can be achieved by running the Office OSPPREARM which is located in the Program Files folder.   Running this will command the Trial will be extended by 30 days, it can be run five times.

How to extend the Office 2010 Trial period

1.  Open a Command Prompt  as Administrator (Quickest method is to the CMD in Windows 7 start menu search and hit return)

2.  You need to navigate to one of the following paths:

64 Bit Office 2010, 64 Bit Windows

c:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform

32 Bit Office 2010, 64 Bit Windows

c:\Program Files (x86)\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform

3. Now run the OSPPREARM.exe file located in one of the above folders and you should received a “Microsoft Office rearm successful” message if you receive “Error: 0xc004d307 On a computer running Microsoft Windows non-core edition, run ‘slui.exe 0x2a 0xc004d307’ to display the error text.”  This happens because all of the 5 rearms have been used.

Continue reading »]]> I came across this 158530 Microsoft Knowledge base some time ago and have only just got around to posting, I have republished here for easier reading.

]]> http://ramblinggeek.co.uk/2011/07/build-numbers-and-release-dates-for-exchange-server/feed/ 0 http://ramblinggeek.co.uk/2011/04/solution-to-the-windows-exception-the-security-database-on-the-server-does-not-have-a-computer-account-for-this-workstation-trust-relationship/ http://ramblinggeek.co.uk/2011/04/solution-to-the-windows-exception-the-security-database-on-the-server-does-not-have-a-computer-account-for-this-workstation-trust-relationship/#comments Thu, 14 Apr 2011 13:58:31 +0000 Wayne http://ramblinggeek.co.uk/2011/04/solution-to-the-windows-exception-the-security-database-on-the-server-does-not-have-a-computer-account-for-this-workstation-trust-relationship/

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.