So the hacker d00d by the name of "Untermench" was kind enought to schlap together a patcher for exactly that problem!

You can find it here: http://www.multiupload.com/Q2UUOYW0Y6

I've just moved to my new flat, server set up and everything is ready to go!

Got all services running (even got my MineCraft server running. See other post for info on Minecraft).

Probably putting in a couple of 2TB disks in the server for extending my media library aswell.

Next step in converting the new flat to a geek-fortress is to buy a roll of CAT6 cable, some heads, a networking plier and cable the shit out of the place!

Trying to update the blog more often! Keep checking!

In Windows Vista, Credential Manager can roam stored user names and passwords between multiple computers in an Active Directory domain. For example, if a user logs on to a computer and connects to a password protected web server and selects “Remember My Password” checkbox. This information will be saved within the Credential Manager. When the user logs on to a different computer and connects to the same server, Internet Explorer will provide the password. So, the user is not supposed to type it again. Earlier versions of Windows cannot access the stored credentials.

Those who use HP / Compaq line of desktops and laptops, you can find all of a sudden that can no longer access the system by displaying the following message: “The system could not access the Credential Manager Server“. The problem is not for the Windows Vista operating system, but certainly one of the software pre-installed by the manufacturer that for most will never be used and that encumbers the eroding precious memory.

“The system could not access the Credential Manager Server” error occurs due to a software “HP ProtectTools Security Manager”,which can be configured to prevent unauthorized access using Smart Cards, TPM Embedded security chips, USB sticks.

There are two ways to solve the problem:

First solution:

Reboot the PC. While it is being restarted by pressing the F8 function key. On the screen will display a different kind of start (If we do not even get the pc reboot and press the F8 function key faster;)
Select “Start in Safe mode”
When you are prompted to log in using the local administrator account
Go to services and DISABLE everything that starts with HP
Reboot the system. Hit f10 while it’s starting and disable the security settings (the second colum halfway down). You’ll have to configure a password to do it for some reason.
When you are prompted to log in using the local administrator account
Go to Start / all program / HP ProtectTool Security Manager FOR ADMINISTRATORS
Click on Credential Manager and then click Settings
Deselect the checkbox in the General tab “Use credential manager to log on to Windows”
You need to logoff
Select “Logon as a different user” and use a standard domain account.
Second Solution:

At the Windows Vista login screen, do the following:

Choose “log in as different user”
Click “log on with Wizard”.This will bring up a new login window where you can specify you username, Domain, and password.
In the bottom left corner of this window is a button labeled “More” Click it, and check the box labeled “Do not logon to Credential Manager”
Write your username, password and domain in the respective places and log on.
After successful logon, UNINSTALL CREDENTIAL MANAGER!
If you don’t, you will have to repeat the procedure next time you start up your PC again!

Sometimes this solution will works fine:

Start in safe mode and log on as a local admin
Start device manager and look under ‘Security Devices’ for ‘TrustedbPlatform Module’ – Right click and select uninstall
Reboot and allow the module to auto-reinstall itself
You should now be able to logon to Windows Vista without receiving a credential manager error. Depending on the versions of Windows Vista and TPM you are running you might have to re-register any finger scans you had stored. The problem is the driver becomes corrupted.

When you try to activate a Terminal Services license server on a computer that is running Microsoft Windows 2000 Server or Microsoft Windows Server 2003, the Terminal Services Licensing service starts, but the license server is not activated.

When you view the System log in Event Viewer, you see an event that is similar to the following:

Type: Error
Date: Date
Time: Time
Event ID: 38
Source: TermServLicensing
User: N/A
Computer:
Details: Can't generate a license for client because of error "Can't add certificate to store, error c0010020".

Resolution:

NOTE: Have your licensing information ready to go, as you will need to call your nearest Microsoft Clearinghouse for re-activation of the licenses.

To resolve this problem, remove the Terminal Services Licensing program, and then reinstall it. To do this, follow these steps:

1. Click Start, point to Programs, point to Administrative Tools, and then clickServices. In the right pane, right-click Terminal Services Licensing, and then clickStop. After the Terminal Services Licensing service stops, close Services.
2. Click Start, click Run, type cmd, and then click OK.
3. At the command prompt, type the following commands. Press ENTER after each command.
   cd %systemroot%system32
   ren LServer LServerOLD
4. Type exit to close the commmand prompt window.
5. Click Start, point to Settings, and then click Control Panel.
6. Double-click Add/Remove Programs, and then click Add/Remove Windows Components.
7. In the Components list, click to clear the Terminal Services Licensing check box, and then click Next.
8. On the Terminal Services Setup page, click Next, and then click Finish.
9. Restart your computer.
10. Click Start, point to Settings, and then click Control Panel.
11. Double-click Add/Remove Programs, and then click Add/Remove Windows Components.
12. In the Components list, click to select the Terminal Services Licensing check box, and then click Next.
13. On the Terminal Services Setup page, click Application server mode, and then click Next.
14. On the Terminal Services Licensing Setup page, click the option you want to use, type the path of your license server database in the Install license server database at this location box, and then click Next.
15. Click Finish, close Add/Remove Programs, and then close Control Panel.
16. Click Start, point to Programs, point to Administrative Tools, and then click Event Viewer.
17. In the System log, verify the existence of two events that are similar to the following:

    Event Type: Information 
    Event Source: TermServLicensing 
    Event Category: None 
    Event ID: 5 
    Date: Date
    Time: Time
    User: N/A 
    Computer: Computer_Name
    Description: Policy Module %SystemRoot%system32File_Name.dll for companyCompany_Name has been loaded.

    Event Type: Information 
    Event Source: TermServLicensing 
    Event Category: None 
    Event ID: 0 
    Date: Date
    Time: Time
    User: N/A 
    Computer: Computer_Name
    Description: Terminal Services Licensing was started.

18. Start Windows Explorer.
19. Expand the %systemroot%System32 folder, and verify that the LServer folder has been created.
20. Click Start, point to Programs, point to Administrative Tools, and then clickTerminal Services Licensing.
21. Right-click the name of your license server, and then click Activate.
22. Follow the steps in the Licensing Wizard to activate your license server.

The following parts describe how to configure the SNMP service (set community names and other tasks). You can manage the SNMP service through the properties for the SNMP service. You can access the service through the Services console in theAdministrative Tools folder or through the Services snap-inin the Computer Management console.

Configuring agent properties

After installing the SNMP service, you need to configure agent properties, which contains general information such as who is responsible for managing the agent host and the types of services with which the agent will interact on the computer.

Right-click the SNMP service in the Services console and choose Properties to open the properties for the SNMP Service, or select the service and choose Action and then Properties to display the service’s property sheet. The General, Log On, Recovery, and Dependencies pages are the same as for other services. Click the Agent tab to configure the following agent properties:

1) Contact: Specify the name of the person responsible for managing the host computer.
2) Location: Specify the physical location of the computer or the contact’s location or other information (phone number, extension, and so on).
3) Physical: Select this option if the agent host manages physical hardware such as hard disk partitions.
4) Applications: Select this option if the agent uses any applications that transmit data using the TCP/IP protocol.
5) Datalink and Subnetwork: Select this option if the agent host manages a bridge.
6) Internet: Select this option if the agent host is an Internet gateway.
7) End-to-End: Select this option if the host uses IP. This option should always be selected.

Configuring traps

Use the Traps tab of the SNMP service to configure computers to which the SNMP service sends traps. From the Community Name drop-down list, select the community for which you want to assign a trap destination. If you have no communities set yet, type the community name in the combo box and click Add to List. Then, click Add to display a simple dialog box in which you can specify the host name, IP address, or IPX address of the remote computer to receive the trap notification. Repeat the process to add other trap destinations as needed.

Configuring security

Use the Security tab of the SNMP Service’s properties to configure the communities in which the agent participates and optionally a list of hosts from which the agent accepts SNMP packets. By default, the agent accepts packets from all hosts. This presents a security risk, however, so take care to configure security settings to permit SNMP traffic only from authorized hosts. The Security page includes the following options:

1. Send Authentication Trap: Select this option to have the agent send a message to all trap destinations if the agent receives an SNMP request from a host or community not listed in the ‘‘Accepted community names’’ list or the ‘‘Accept SNMP packets from these hosts’’ list. The message is sent to all hosts in the trap destination list on the Traps property page to indicate that a remote management system failed authentication (potentially indicating an unauthorized access attempt).

2. Accepted Community Names: Use this list and the related buttons to alter the list of communities in which the agent participates and the community rights for each. You can select from the following rights:

a) None: This option prevents the agent host from processing any SNMP requests from the specified community. For instance, you may configure None for the Public community for enhanced security.

b) Notify: Select this option to permit the agent host to send traps only to the selected community.

c) Read Only: Use this option to permit remote consoles to view data in the local MIB but not change it. This option prevents the agent from processing SNMP SET requests.

d) Read Write: Use this option to permit remote consoles to make changes on the managed system. This option allows the agent to process SNMP SET requests.

e) Read Create: Use this option to permit the agent to create new entries in the SNMP tables.

3. Accept SNMP Packets from Any Host: Select this option to permit the agent to process requests from all hosts in the ‘‘Accepted community names’’ list.

4. Accept SNMP PACKETS from These Hosts: Select this option to define a specific list of hosts from which the agent will process SNMP requests.

After first installing IIS7 on the 2008 server, I added the virtual directory to the root of the Site.
Then when trying to browse it, it only gave me a "500 - Internal Server Error". Nice.

So, i read up on the subject and figured out I had to enable "Directory Browsing" for this to work:

OK so when I tried browsing it now, it still gave the dreaded "500 - Internal Server Error" !!

Well, turns out I have to give the IIS itself access to the Virtual Directory in question!
This is done by granting the "Network Service" user access to the virtual directory:

OK, now we're getting somewhere! Now when browsing, it gave me a "401 - Unauthorized access" !!

Last thing we need to do is enable the "Anonymous Authentication" as "Application Pool Identity" or the network service user so to speak.

And there we go!!

I can almost promise you will like this!

Get it Here!

http://www.pctools.com/free-antivirus/ <- Free, and works for 2003 server

http://www.clamav.net/ <- Also free and used as a secondary AV

=)

Im testing a post from my HTC Hero phone with an Android app for wordpress. Seems to e working just fine

Get-ExchangeCertificate | fl

Note the services the certificate is enabled for (by default: POP, IMAP, IIS, SMTP on CAS + HT servers). Copy the thumbprint of the certificate.

Get a new certificate with a new expiration date:

Get-ExchangeCertificate -thumbprint "C5DD5B60949267AD624618D8492C4C5281FDD10F" | New-ExchangeCertificate

If the existing certificate is being used for SMTP, you will get the following prompt:

Type Y to continue. A new certificate is generated.

The new certificate is generated and enabled. Examine the new certificate:

Get-ExchangeCertificate -thumbprint "3DA55740509DBA19D1A43A9C7161ED2D0B3B9E3E" | fl

2 The old certificate is enabled for IIS, POP, IMAP and SMTP. The new certificate generated using the above command is enabled only for POP, IMAP and SMTP - IIS is missing.

To enable the certificate for IIS:

Enable-ExchangeCertificate -thumbprint "3DA55740509DBA19D1A43A9C7161ED2D0B3B9E3E" -services IIS

This enables the certificate for IIS (in addition to any other services it may already be enabled for - it adds to existing values of the services property).

Test services are working with the new certificate. If it works as expected, the old certificate can be removed:

Remove-ExchangeCertificate -thumbprint "C5DD5B60949267AD624618D8492C4C5281FDD10F"