Problem with COSBI OpenSource Mark

If the workload does not work, it's usually a problem related to the fact that COSBI cannot write the .ini file.

The problem is associated to missing drivers. Install all the drivers needed, and all will work fine :)

Repair SQL Server Database marked as Suspect or Corrupted

EXEC sp_resetstatus 'real_set_2'

ALTER DATABASE real_set_2 SET EMERGENCY

DBCC CheckDB ('real_set_2')

ALTER DATABASE real_set_2 SET SINGLE_USER WITH ROLLBACK IMMEDIATE

DBCC CheckDB ('real_set_2', REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE real_set_2 SET MULTI_USER

(source: http://www.sqlservercurry.com/2011/03/repair-sql-server-database-marked-as.html)

Windows XP Activation LOOP

To solve the loop, while we are trying to activate, press Windows Key + U, then in the window that pops up press the link to the Microsoft Website, and you will have a nice browser that will fulfill your desires :)

(source: http://www.thetomorrowtimes.com/2006/12/how-to-login-to-expired-windows.html)

(Windows) NTP server for a private network

Need to have a NTP server for your private network?

You have machines that cannot access the Internet, but you need them to be time sync-ed?

I had this problem, and I solved it letting my "gateway" machine (i.e. Controller) become a NTP server.

First of all, activate the Windows Time service in Control Panel -> Administration Tools -> Services.

Then, modify the registry entry using regedit.exe in this way:

System Key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
Value Name: LocalNTP
Data Type: REG_DWORD (DWORD Value)
Value Data: (0 = disabled, 1 = enabled)

(source: http://www.pctools.com/guides/registry/detail/1117/)

Unfortuately, this solution doesn't work (at least for me).

On the other hand, this other solution I found here (http://www.techrepublic.com/blog/datacenter/configure-a-standalone-ntp-server-in-windows-server/3869) works fine ^_^

System Key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NTPServer]
Value Name: Enable
Value Data: (0 = disabled, 1 = enabled)

Putting the data value to 1 enables the current machine to become a NTP server.

Then, in a command shell update the configuration of the Windows Time service:

> w32tm /config /update

and visualize the new configuration with:

> w32tm /query /configuration

The output should appear like the one in the image

(source: http://www.techrepublic.com/blog/datacenter/configure-a-standalone-ntp-server-in-windows-server/3869)

Last step, update the new server machine using a NTP server on the Internet. If you don't do it, you can incurr in some synchronization problem on the clients, like this:

"Error (...) Peer's stratum is less than Host's stratum"

that practically means that the client doesn't trust the new NTP server, as it did not take time from anywhere.

Different thing is if you want to define your machine as a "standalone, trustable NTP server". In that case you need a Knowledge Base from Microsoft that alows to your machine to take the time only from the CMOS clock of your machine.